Page 1 of 1
Unable to set route at Christian St Jn 31/05/2023 at 18:22 #151988 | |
9pN1SEAp
![]() 1140 posts ![]() |
Hi, 2D42 is stuck at signal 107, with main route R107 refusing to be called due to "Point(s) locked normal by another route". Driver was able to successfully run to next signal under caution. Not sure if this is an error in the control tables? Thanks Jamie Post has attachments. Log in to view them. Jamie S (JAMS) Last edited: 31/05/2023 at 18:27 by 9pN1SEAp Reason: None given Log in to reply |
Unable to set route at Christian St Jn 31/05/2023 at 19:11 #151989 | |
y10g9
![]() 895 posts |
I've had a look at your save, At some point you must have clicked on P2023 points as when I unoccupied the track circuit, the points were show as having been keyed reverse. If you click on the points in question (up main to up slow dierting points under the TCF) then you'll be able to set the route
Log in to reply |
Unable to set route at Christian St Jn 31/05/2023 at 21:38 #151994 | |
9pN1SEAp
![]() 1140 posts ![]() |
Ah yes, thanks. I saw the keying request (you can't tell from visuals or F11). But I have no idea why the state of 2023 points (up) should prevent the calling of a Down route! Jamie S (JAMS) Log in to reply |
Unable to set route at Christian St Jn 31/05/2023 at 21:51 #151996 | |
GeoffM
![]() 6344 posts |
9pN1SEAp in post 151994 said:But I have no idea why the state of 2023 points (up) should prevent the calling of a Down route!I think it was because the combination of the track down with subroutes locked with a reverse point call - ie the key request conflicted with the flank locking attempt. Yes, it didn't need flank locking, but it's always checking and found an inconsistent set of requests so it took the safe option (just as interlockings should). SimSig Boss Log in to reply |
Unable to set route at Christian St Jn 01/06/2023 at 13:28 #152015 | |
9pN1SEAp
![]() 1140 posts ![]() |
Ah! That makes sense. Thanks.
Jamie S (JAMS) Log in to reply |