Page 1 of 1
| SPAD at CN12 does not activate OTW indicator 08/01/2021 at 15:55 #136097 | |
Dionysusnu
575 posts 
|
A train told to SPAD past CN12 to proceed to Eggesford will not activate the OTW indicator. To avoid trains getting stuck at CN12, maybe a wrong-route call could be added for the CN4-CN12 shunt route, if the train is booked via Eggesford? Log in to reply |
| SPAD at CN12 does not activate OTW indicator 08/01/2021 at 16:44 #136112 | |
jc92
3629 posts |
Confirmed and Mantis 32741. The issue is less about wrong route calls, and more about the section failing to show occupied. In real life its token worked and the driver would have possession of it before passing CN12 "We don't stop camborne wednesdays" Log in to reply |
| SPAD at CN12 does not activate OTW indicator 08/01/2021 at 17:33 #136116 | |
|
Dionysusnu
575 posts
|
Yes, the wrong route was meant separately from the OTW issue. But it is a common mistake with no really good solution after you've made it. I think a wrong route would be helpful, not to mention more realistic. A driver in real life would notice the shunt route and call to inform that he's not planning to shunt there.
Log in to reply |
| SPAD at CN12 does not activate OTW indicator 08/01/2021 at 17:36 #136117 | |
headshot119
4869 posts |
Dionysusnu in post 136116 said:Yes, the wrong route was meant separately from the OTW issue. But it is a common mistake with no really good solution after you've made it. I think a wrong route would be helpful, not to mention more realistic. A driver in real life would notice the shunt route and call to inform that he's not planning to shunt there.Generally wrong route code isn't added where a different class of route will get the train to the same place. There are also circumstances where you would clear a sub, instead of a main allowed for in the rules. "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 |