Possible Errors

Physical

Shortcircuit (caused by manual Intervention)

When a shortcircuit occurs while a train is driving a route, the train might not stop at the destination signal.

Steps for reproducing:

1. Select one train (ex. cargo_db).
2. Select one route.
3. Start cargo_db.
4. Grab another train (ex. cargo_green).
5. Wait until cargo_db is nearly at the destination signal.
6. Cause a shortcircuit by putting cargo_green into a wrong switched point.

Expected Behaviour:
7. (Driving) cargo_db stops before reaching the destination if it is on the same partition as the shortcircuit.

Possible Error:
7.A1 (Driving) cargo_db continues to drive, i.e., the train doesn't stop at the destination signal.
7.A2 Controlling the cargo_db could be possible but not really stable reproducible until a complete system reboot (software restart) has be done.

Speed overwrite (Game Client)

When using the GameClient of the driver game, you can overwrite the emergency brake.

Steps for reproducing:

1. Open the game client.
2. Select a train for driving.
3. Select a destination.
4. Set speed (here you can change speed over time).
5. Don't stop the train in front of the destination signal (as one would usually do).
6. While arriving and driving past the destination signal, repeatedly press a speed button except for the stop button.

Expected Behaviour:
7. Trains stops triggered by the emergency breaks because the destination signal was driven past.

Possible Errors:
7.A1 Train keeps driving after passing the destination signal.

Notes:

• best replication method is a autoclicker with a interval of 15 ms.