"Train Activities" relates to extra activities that a train may undertake at a particular stopping location. They are also termed Train Associations in real life. They are to be found in the Activities column of the train's timetable (abbreviated to TT). (Display the TT by either (1) clicking the train's headcode on the layout to bring up the Show Timetable window, or (2) from the Train List (hotkey F2), select the train, right-click to open the context menu, then select Timetable Options > Edit Timetable > Location List.)
N:1A01 - New The train takes up the new timetable and proceeds in accordance with it.
This activity is associated with the last entry on the TT as it signifies that the train will change its headcode to become a new train. Each headcode requires a separate TT; you cannot change a train's headcode in the middle of its TT! For example, the last line in train 5A01's TT might read [location] ROYSTON ... [Activities] N:1A01. This tells you that train 5A01 is an empty train (headcodes starting with 5 signify empty coaching stock, abbreviated to ECS) which on arriving at Royston station is ready to take on passengers, changing its headcode to 1A01 (headcodes starting with 1 signify high speed passenger trains). The simulation will reverse the direction of the train on arrival at the platform if necessary.
The N prefix may be thought of as standing for New or Next (Next Working). To change the headcode, right-click on the current headcode displayed on the layout and select Interpose. Type in the new headcode, click OK and close the Interpose window. Clicking the new headcode on the layout will refresh the Show Timetable window to show the new TT.
J:1B01 - Join with 1B01 - the current train is to join with 1B01, which may or may not have arrived yet.
The united train can assume a new TD eg J:1B01 N:1C01, or retain its TD eg if a light loco joins onto the train.
Both the joining trains have to be next to each other at the location as specified for the join (but do not have to be in any specified platform)for the join to commence.
DF:1A01 - Divide Front - Part of the train divides off the front of the original train and becomes 1A01.
DR:1A01 - Divide Rear - Part of the train divides off the rear of the original train and becomes 1A01.
Usually the remaining part of the original train also takes up a new TD, this is shown as DR:1A01 N:1B01.
DEF:0A01 - Detach Front - Part of the train divides off the front of the original train and becomes 0A01.
DER:0A01 - Detach Rear - Part of the train divides off the rear of the original train and becomes 0A01.
The distinction with 'Detach' is that the power type is retained on the detached part, but the remaining original train is left with no power. A typical application is for a loco detaching off a train to run-round and reattach at the other end.
DCF:5A01 - Drop Coaches Front - The front part of the train separates and becomes 5A01. The remainder of the train retains the original headcode.
DCR:5A01 - Drop Coaches Rear - The rear part of the train (usually consisting of coaches alone) separates from the front and becomes 5A01.
Drop coaches is the reverse of 'Detach Engine'- the original portion of the train is still powered, and the detached portion has no power.
PS:1A01 - Platform Share - This train will platform share (double dock) with the specified train. If the specified train isn't in the platform it doesn't matter: it's simply a hint that if it is there then this train can be platformed on top of it. Beware of last minute stock changes resulting in the trains being too long for the platform (yes, it happens in real life too). In an ARS simulation, this hint gives ARS permission to set a call-on route on top of the specified train, if the call-on route is ARS-enabled. Again, for ARS, it does not require that the specified train is in the platform, only that it can set route on top if it is there. The activity order isn't important but it is suggested that share activities are specified after other activities as those are more important than shares. Only available in core code versions 3.242 and later
Last edited by GeoffM on 15/09/2016 at 03:00