Page 1 of 1
Crewe UML calls 20/12/2023 at 09:54 #154779 | |
9pN1SEAp
1184 posts |
Hi, In the attached save, 6F58 is timed to regulate at Crewe Up Manchester Loop, but having been recessed is now complaining that it's stopped at CE152, the TT having stepped up automatically for next location CRE. This is 2016 era. Thanks Jamie Post has attachments. Log in to view them. Jamie S (JAMS) Log in to reply |
Crewe UML calls 20/12/2023 at 11:26 #154781 | |
HST125Scorton
1192 posts |
I'll add to this, any train that is recessed to time in Crewe Up Manchester Loop always complains that it's stopped at CE152. It seems it passes the location before stopping at the signal hence it says Crewe for the next timing point.
Aaron (AJRO) | Timetable Writer Log in to reply |
Crewe UML calls 21/12/2023 at 20:46 #154792 | |
9pN1SEAp
1184 posts |
Ditto for Up Potteries (CE196). Thanks Jamie Jamie S (JAMS) Log in to reply |
Crewe UML calls 21/12/2023 at 23:02 #154793 | |
eps125
145 posts |
This has already been reported as Mantis 38933. There is also a core code ticket logged to look at the underlying issue.
Log in to reply |