Upcoming Games

(UTC times)


Full list
Add a game

Upcoming Events

No events to display

Three Bridges ACI

You are here: Home > Forum > Simulations > Timetables > Three Bridges > Three Bridges ACI

Page 1 of 1

Three Bridges ACI Today at 13:22 #160829
DaveHarries
Avatar
1294 posts
Greetings,

I continue work on my Three Bridges TT of 08th May 2022. One query regarding the ACI (Automatic Code Insertion, where - if there is a following working - a train headcode changes automatically on terminating) though.

I am putting together a separate file of additional trains which will be added to this timetable as a midnight seed group at a later date if all goes well. In the current 03:55 seed group I have a train in the Up Siding North at Three Bridges, train ID 5A89 (0701 Three Bridges USN - Three Bridges) which is a 4-car Class 377 that merges with 1A91 (06:37 Brighton - London Victoria) to form an 8-car train.

The fun arises, however, because the 0701 Three Bridges USN - Three Bridges is not the only 5A89 in the timetable: there is a second 5A89 which is the 0508 Lovers Walk T&RSMD - Brighton, an 8-car Class 377 formation which then forms 1A89 (0534 Brighton - London Victoria).

The 5A89 movement at Three Bridges has its own UID - SN5A89_0701TBD - as does the 0508 ECS movement from Lovers Walk T&RSMD - SN5A89_0508BTN - but I can't help wondering if, in the event of the ACI not applying to the Up Siding North at Three Bridges, interposing of the code by the person doing the panel might bring up the wrong 5A89.

If, as I know I need to do, I insert the correct subsequent working from the list of trains would the code automatically switch over when 5C71 arrives at Three Bridges USN or would the person working the panel need to change it over themselves?

Thanks,
Dave

(As an aside, the duplicating of train headcodes isn't my choice: it is the way things ran on the day and neither of them were cancelled. Also this is not the only duplicating of train codes: services on the Sutton line, along with some of the Thameslink-operated 9Txx services, have duplicating train numbers too hence the format of train UID used earlier as a means of distinguishing the workings! I hope it works - I couldn't think of a better solution!

Last edited: Today at 13:24 by DaveHarries
Reason: None given

Log in to reply