Page 1 of 1
Train held NK466 01/08/2022 at 21:03 #147431 | |
9pN1SEAp
![]() 1140 posts ![]() |
Hi, I have a TCF in advance of NK464 (UNK Higham) causing the signal to be fixed On. This is 2015 era so NJ interlocking isn't visible. However the Strood signaller is holding a train at NK466. Presumably this is RR protected to avoid a tunnel stop. If so it might be worth adding to the manual? Thanks Jamie Jamie S (JAMS) Log in to reply |
Train held NK466 01/08/2022 at 21:20 #147434 | |
headshot119
![]() 4869 posts |
Mantis 36512
"Passengers for New Lane, should be seated in the rear coach of the train " - Opinions are my own and not those of my employer Log in to reply The following user said thank you: 9pN1SEAp |
Train held NK466 01/08/2022 at 22:31 #147437 | |
9pN1SEAp
![]() 1140 posts ![]() |
Further to the above, I have discovered that NK466 is only set back when NK464 emergency replacement is activated. I had NK464 on red, hit the R and immediately got ACoA on 466!! That's definitely worng :) Thanks Jamie Jamie S (JAMS) Log in to reply |
Train held NK466 02/08/2022 at 12:05 #147441 | |
clive
![]() 2766 posts |
9pN1SEAp in post 147437 said:Further to the above, I have discovered that NK466 is only set back when NK464 emergency replacement is activated.That depends on how the double-blocking is implemented. I'm assuming the failure occurred with NK464 off, putting NK466 back to red. Sometimes a double block is latching, so that putting one signal back to red doesn't put the other one back, and sometimes it's unconditional (I can remember notes on Peterborough panel saying that putting back signal X would put back signal Y). This sounds like a hybrid, which sounds like a bug to me. Log in to reply |
Train held NK466 02/08/2022 at 18:11 #147448 | |
GeoffM
![]() 6344 posts |
clive in post 147441 said:9pN1SEAp in post 147437 said:Tunnel controls, not double blocking. Slightly different, and yes it's quite possible for them to not operate exactly how you'd expect. So we'll let Paul work out if it's a bug or not.Further to the above, I have discovered that NK466 is only set back when NK464 emergency replacement is activated.That depends on how the double-blocking is implemented. I'm assuming the failure occurred with NK464 off, putting NK466 back to red. Sometimes a double block is latching, so that putting one signal back to red doesn't put the other one back, and sometimes it's unconditional (I can remember notes on Peterborough panel saying that putting back signal X would put back signal Y). This sounds like a hybrid, which sounds like a bug to me. SimSig Boss Log in to reply |