Master will run an evented simulation of the trains location. It will know the trains location at all times, be able to factor in acceleration, and calculate when to change train speeds for short moves. The simulation will run independent of the sensor feedback and only use sensor feedback to correct train positioning in the simulation.
Blaster will merge train control and the dumber parts of train driver into one task. Given that we use delay couriers now, it makes very little sense to separate the train driver from the control and then also have the master running. It is too complicated given its purpose and just adds a lot of duplicated logic to the system.
Blaster will notify Master when user input has changed the speed of the trains (including reverse), and will take speed change commands from Master.
Master will run an evented simulation of the trains location. It will know the trains location at all times, be able to factor in acceleration, and calculate when to change train speeds for short moves. The simulation will run independent of the sensor feedback and only use sensor feedback to correct train positioning in the simulation.
Blaster will merge train control and the dumber parts of train driver into one task. Given that we use delay couriers now, it makes very little sense to separate the train driver from the control and then also have the master running. It is too complicated given its purpose and just adds a lot of duplicated logic to the system.
Blaster will notify Master when user input has changed the speed of the trains (including reverse), and will take speed change commands from Master.
https://www.youtube.com/watch?v=Hgq4w4dqKsU