MovementOrders

The MovementOrders table defines all the scheduled movement orders.

General information

ID: (int); Automatically increments.

MovementType: (int); Indicates the type of movement order being defined.

  0: Renumber
  1: Turnaround (Change Cab)
  2: Couple
  3: Uncouple
  4: Call
  5: Change Driver
  6: TimetableAssignment
  7: Pull Up
  8: Stop Short
  9: Stop Ahead
 10: Take Switch Lock
 11: Take Spur
 12: RESERVED
 13: Stable Cars
 14: Spot Cars
 15: RESERVED
 16: Move To
 17: RunAround
 18: Content Changes (freight/passenger car load/unload)
 19: Relinquish Control (hand over train to a freight yard)
 20: Stable Train
 21: Change Staff
 22: Limit Speed

Train_ID_SOFT: (string); Train number of the train for which this order applies.

Train_ID_HARD: (int); Database ID of train in Timetable table for which this order applies. If the train does not exist in the Timetable table, then this can be left empty. This allows for orders to be defined for trains that are created through other movement orders.

Predecessor_ID: (int); Database ID within the MovementOrders table of the previous movement order. Is -1 if the order is the first in the list. This allows the simulation to properly sort the orders in the proper sequence.

OrderTrack: (string); Name of the track where the order is to occur. This can be left empty.

OrderLocation: (string); Name of the location (station) where the order is to occur. This cannot be left empty.

RenumberID: (string); Train ID to renumber to. Applies to renumbering orders only.

RenumberUpdatesTNV: (bool); True when the new train ID is automatically entered into the train number display (TNV) system.

UncoupleLeftID: (string); Used when the order is an uncouple order. Defines the new name of the consist on the left side of the uncouple point.

UncoupleRightID: (string); Used when the order is an uncouple order. Defines the new name of the consist on the right side of the uncouple point.

UncoupleIndex: (int); Indicates where to uncouple, relative to the front of the train.

UncoupleLeftDirection: (int); Indicates the new direction of the left portion of the split train. 0 = left, 1 = right.

UncoupleRightDirection: (int); Indicates the new direction of the right portion of the split train. 0 = left, 1 = right.

UncoupleLeftCallsIn: (bool); If the driver of the new left train should call the dispatcher after uncoupling, then this value should be true.

UncoupleRightCallsIn: (bool); If the driver of the new right train should call the dispatcher after uncoupling, then this value should be true.

CoupleID_Partner: (string); Defines the train ID of the train to couple with.

CoupleNewID: (string); Defines the train ID of the train after coupling.

CoupleCallInForDeparture: (bool); True when the driver of the newly coupled train calls the dispatcher.

NewDriverPrepTime: (date); Time of day that a new driver should arrive at a train.

NewDriverType: (int); Type of the new driver, as defined in the DriverTypes table.

 0 = Train driver
 1 = Shunt driver
 2 = Engineering driver
 3 = No driver

StopShortDistance: (int); Distance, in metres, that a train should stop before a signal. Used when the movement order is a stop short order.

FreeShuntRegion: (string); Name of the free shunting region where this order should be defined.

FreeShuntSequence: (int); Sequence number to use when doing free shunting orders.

FreeShuntSpotCarsNewID: (string); Train ID of the new train after spotting cars.

FreeShuntSpotCarsNewDirection: (int); Direction of the train after spotting cars in a free shunting order, 0 = left, 1 = right.

SpurName: (string); The name of the spur to take.

ContentChanges: (string); Defines the values to use when executing a Vehicle Contents movement order (type# 18).

Speed: (float); For order type #22 - Speed Limit - defines the speed, in KMH, that a train should move while on a track.

PeriodStart: (date); Date from which the movement order is valid. (you better copy a train and attach the movement orders to that periodic train)

PeriodEnd: (date); Date at which the movement order no longer valid.

RunAround order (type #17)

The type number for these orders is type #17. Here's what you need in order for such an order to be loaded and executed:

Required fields

OrderLocation             - Name of the location (station) where the order is to occur. (mandatory)
OrderTrack               - Name of the track where the order is to occur. (optional)
UncoupleLeftID           - the name of the resulting train on the left of the splitting point (mandatory)
UncoupleRightID          - the name of the resulting train on the right of the splitting point (mandatory)
CoupleNewID              - the name of the train after re-coupling (mandatory)
PickOffPoint             - splitting index as measured from the FRONT of the train. Typically, this will be 0 if you're just pulling off the first vehicle
RunAroundTime            - time, in seconds, it takes for a loco to run around. If you enter 0, a value will be guessed but it might not be realistic.
CoupleCallInForDeparture - set to True if you want the driver to call after recoupling.

This order only works in Dark Territory.

The train must fully occupy the track on which the order is carried out (that is, the train can only be on 1 track). Train must be stopped, and the splitting index must be correct :you can't pull off more cars than there are in the consist. If there are N cars, you can pull off up to and including N+1 cars, although this would be unusual.

Once the order begins to execute, the consist goes into "timeout" mode where it does not update at all, and no communication is possible. When the loco recouples, I include time for brake testing (similar to a normal couple order) that is dependent on the length and type of train.

Be aware that the direction of the train does NOT change with this order. This means that if the train is going rightwards when the order executes, and the front loco comes off, then the resulting train will be propelled, unless you either:

change direction first, and THEN run around loco
change direction after recoupling

Relinquish Control (type #19)

"Relinquish Control" is a special order used to effectively dispose of a train if it's in a service/freight yard. This makes it easier for the schedule planner as he/she does not need to worry about spawn tracks and deadlocks and such. A few rules, for this to work:

A train must be in a freight yard/service yard.
A train must be stopped.
A train must only occupy a single track (not straddling any insulation joints).

Once the conditions are satisfied, the train will disappear completely as though it has exited via a spawn track.

OrderLocation            - Name of the location (station) where the order is to occur. (mandatory)
OrderTrack               - Name of the track where the order is to occur. (optional)

Change Staff (type #21)

(Not fully implemented yet, so this behaviour might change.)

"Change Staff" is an order used to simulate the effect of a driver handing over control of a new, different driver.

If a train has this order, a new "relieving" driver will call the dispatcher approximately 30 minutes before the train is due to arrive. The new driver announces his/her intentions to relieve the driver of a specific train (giving the train number) and it's up the the dispatcher (the user) to determine the most appropriate location for this meeting to happen. The user can choose a location area within the communication window (something like 'Platforms' or 'Platforms-West' or whatever areas are defined in the given sim) and this choice is then given to the new relieving driver.

The relieving driver, inside the simulation, will contact the driver-to-be-relieved and they will agree on where to meet. Therefore, the dispatcher does not need to call the driver.

It is important that the dispatcher sends the train to the area where the staff change will occur. If the user does it wrongly, then it's possible the driver might refuse to move until his replacement arrives.

OrderLocation            - Name of the location (station) where the order is to occur. (mandatory)
OrderTrack               - Name of the track where the order is to occur. (optional - if defined, the sim doesn't really do anything with it at this time)

Limit Speed (type #22)

The "Limit Speed" order is designed to tell a train that on certain tracks, it may not exceed a certain speed.

OrderLocation            - Name of the location (station) where the order is to occur. (mandatory)
OrderTrack               - Name of the track where the order is to occur. (optional - if defined, the speed limit applies to only this track.)
Speed                    - Speed, in KMH, that the train may not exceed while on the track or in the location.