Page 1 of 1
| Shunt Signal CC534 21/04/2010 at 16:57 #1153 | |
UKTrainMan
1803 posts |
During the conclusion of TRC666's CScot game last night I was working Duty 1 / Cowlairs 1 and had to deal with the usual ECS workings out of Glasgow Queen Street to Eastfield TMD. I'd signalled one of these out of GQS via the normal line and within a few seconds afterwards I had to signal another one out so I decided to use the bidirectional signalling and have the trains playing Wacky Races with each other up to just before Cowlairs West Junction (Signals CC52 & CC238 respectively). The first train out of GQS arrived at Signal CC52 first (as you might have expected) and so I signalled this into Eastfield TMD as per normal via Shunt Signals CC534 & CC532 - nothing wrong there. The second train out of GQS arrived at Signal CC238 so I waiting for the route to become available then signalled this train onwards from CC238 to Shunt Signal CC534 then to CC532 and into Eastfield TMD however the train in question stopped at CC534 and called me up challenging the route, saying something about it being a goods line so it wouldn't accept the route as per normal - I had to tell it to accept the route onto the goods line, which the driver did without any further objections. Surely the driver shouldn't be challenging it as a goods route, if a train via the normal route (from Signal CC52 to Shunt Signals CC534 & CC532) didn't challenge the route then why does a train via the other route challenge it, despite both of them using the same signal. I can only assume that this is a minor bug or error in the coding? Low-Quality Screenshots;  The 'Normal' Route, with the offending signal pointed to.  The 'alternative' route, with the offending signal pointed to. Just to clarify, the first train I signalled went via "The 'Normal' Route" and the second train I signalled went via "The 'Alternative' Route". Replies welcomed/appreciated - thanks in advance. Any views and / or opinions expressed by myself are from me personally and do not represent those of any company I either work for or am a consultant for. Log in to reply |
| Shunt Signal CC534 21/04/2010 at 16:57 #8700 | |
|
UKTrainMan
1803 posts |
During the conclusion of TRC666's CScot game last night I was working Duty 1 / Cowlairs 1 and had to deal with the usual ECS workings out of Glasgow Queen Street to Eastfield TMD. I'd signalled one of these out of GQS via the normal line and within a few seconds afterwards I had to signal another one out so I decided to use the bidirectional signalling and have the trains playing Wacky Races with each other up to just before Cowlairs West Junction (Signals CC52 & CC238 respectively). The first train out of GQS arrived at Signal CC52 first (as you might have expected) and so I signalled this into Eastfield TMD as per normal via Shunt Signals CC534 & CC532 - nothing wrong there. The second train out of GQS arrived at Signal CC238 so I waiting for the route to become available then signalled this train onwards from CC238 to Shunt Signal CC534 then to CC532 and into Eastfield TMD however the train in question stopped at CC534 and called me up challenging the route, saying something about it being a goods line so it wouldn't accept the route as per normal - I had to tell it to accept the route onto the goods line, which the driver did without any further objections. Surely the driver shouldn't be challenging it as a goods route, if a train via the normal route (from Signal CC52 to Shunt Signals CC534 & CC532) didn't challenge the route then why does a train via the other route challenge it, despite both of them using the same signal. I can only assume that this is a minor bug or error in the coding? Low-Quality Screenshots; The 'Normal' Route, with the offending signal pointed to. The 'alternative' route, with the offending signal pointed to. Just to clarify, the first train I signalled went via "The 'Normal' Route" and the second train I signalled went via "The 'Alternative' Route". Replies welcomed/appreciated - thanks in advance. Any views and / or opinions expressed by myself are from me personally and do not represent those of any company I either work for or am a consultant for. Log in to reply |
| Shunt Signal CC534 21/04/2010 at 17:40 #8703 | |
|
clive
2789 posts |
Sounds to me like the train didn't think it was an ECS working - how it got to the signal doesn't affect the "goods line" test. Was it still running with a 1 or 2 headcode, rather than a 3 or 5?
Log in to reply |
| Shunt Signal CC534 21/04/2010 at 18:26 #8708 | |
|
UKTrainMan
1803 posts |
It was definitely a Class 5 (ECS) headcode, I'm 99.99% certain. I did mean to take a note of the actual headcode for the train involved but seemingly forgot in all the excitement at finishing a timetable off fully. I'll try and find out / work out the headcode if I can but no promises. Any views and / or opinions expressed by myself are from me personally and do not represent those of any company I either work for or am a consultant for. Log in to reply |
| Shunt Signal CC534 21/04/2010 at 18:41 #8709 | |
|
UKTrainMan
1803 posts |
Right I've had a look at the TT and it has reminded me that the train in question was for Eastfield TMD #3 (Road 3?) so it's either 5J87-4 or 5R09-3.
Any views and / or opinions expressed by myself are from me personally and do not represent those of any company I either work for or am a consultant for. Log in to reply |
| Shunt Signal CC534 21/04/2010 at 19:20 #8710 | |
Peter Bennet
5402 posts |
The goods line code is within the route from 534 to 532 and there is only one route from 534 to 532 so train behaviour should be identical for identical classes of train. If one passed and one did not then we need to call Mystery Inc. methinks. Peter I identify as half man half biscuit - crumbs! Log in to reply |