Authorising trains to pass Signal 116 at danger

You are here: Home > Forum > Simulations > Released > Euston PSB > Authorising trains to pass Signal 116 at danger

Page 1 of 1

Authorising trains to pass Signal 116 at danger 21/01/2012 at 06:21 #27843
UKTrainMan
Avatar
1803 posts
Earlier on in my solo game of the 2012 timetable, Track Circuit T140, which is the overlap TC for Signal 111, failed. Luckily for me I found there was enough gaps available to allow me to route trains around it via the Up Slow, which I did without a problem for a while. Unfortunately, there came the perhaps inevitable time when I needed to send a train via the Up Fast, over the TCF. Once the train on the Up Fast had passed Signal 141, I used F11 Incident Control Panel -> Trains tab and, for something a little different, selected the Stop at next signal and report to signalbox option. I already had both points at Camden South Jn 'keyed' and 'locked' (reminder applied). As the train occupies TC T202, the train comes to a halt (basically stopping over Camden South Jn). Checking F2, it flits between "Run out of valid track/Moving at 0mph/Stopped at signal", and just stays doing that.

Issue is easily resolved, no problems there (just change the option to Keep going and milliseconds later the train will occupy TC T139 as per normal and continue on it's merry way into Euston.

I note the fact that the train fills/occupies TC T202 different to how it fills/occupies TC T201 - with T202 it seems to fills/occupies the whole of it, but with T201 it only fills/occupies the route it is taking.

Bug?

Thanks in advance for reply/replies.

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
Re: Authorising trains to pass Signal 116 at danger 21/01/2012 at 08:44 #27846
Firefly
Avatar
521 posts
Quote:
I note the fact that the train fills/occupies TC T202 different to how it fills/occupies TC T201 - with T202 it seems to fills/occupies the whole of it, but with T201 it only fills/occupies the route it is taking.
It's known as track flooding and it's completely correct.

If there's a route set over a set of points only the sections of track within the route will light, if however there's no route set the system has no way of knowing which sections of track should be illuminated so it floods the whole lot.

This should also happen in overlap track circuits if a train SPAD's despite the fact that you have route lights lit.

You can play around with this to see for yourself.

Occupy and track and it will flood.



Then set a route over it and only the section in the line of route shows occupied.


Post has attachments. Log in to view them.
Last edited: 21/01/2012 at 08:46 by Firefly
Log in to reply
Re: Authorising trains to pass Signal 116 at danger 21/01/2012 at 09:05 #27848
Peter Bennet
Avatar
5360 posts
When we were at Doncaster box we noticed that the Newark crossing, I think it was, floods as a matter of course whenever a train crossed.

Peter

I identify as half man half biscuit - crumbs!
Log in to reply
Re: Authorising trains to pass Signal 116 at danger 21/01/2012 at 09:08 #27849
Late Turn
Avatar
696 posts
Online
" said:
This should also happen in overlap track circuits if a train SPAD's despite the fact that you have route lights lit.

Just recreated the circumstances described by UKTM, and 201 does indeed illuminate normally despite having no route set through it - just the overlap from the signal in rear. The following TC, 202, is beyond the end of the overlap and floods as expected and described.

Log in to reply
Re: Authorising trains to pass Signal 116 at danger 21/01/2012 at 12:58 #27867
clive
Avatar
2738 posts
" said:
As the train occupies TC T202, the train comes to a halt (basically stopping over Camden South Jn). Checking F2, it flits between "Run out of valid track/Moving at 0mph/Stopped at signal", and just stays doing that.
It's not a Euston bug, it's in the core code. I can see the code doing the wrong thing in this case, but figuring out the right thing will be a bit harder.

Log in to reply
Re: Authorising trains to pass Signal 116 at danger 21/01/2012 at 13:08 #27869
clive
Avatar
2738 posts
" said:
When we were at Doncaster box we noticed that the Newark crossing, I think it was, floods as a matter of course whenever a train crossed.

Peter
My photos don't show it, but my memory is that there was a quick flicker of the ECML track circuit indication when a train went across on the Castle line, but no flicker on there when a train went along the ECML. Each of the four tracks has a single track circuit shown covering the entire crossing, but I believe that one of the two lines actually uses axle counters. The Up ECML TC extends back to signal 96; the down ECML one extends back to the SPADI, and includes the trailing crossover.

Log in to reply
Re: Authorising trains to pass Signal 116 at danger 21/01/2012 at 15:06 #27877
Stephen Fulcher
Avatar
2026 posts
To track circuit that crossing using conventional DC track circuits on all four lines would be extremely complicated. I am surprised they have not got axle counters on all four roads now.
Log in to reply
Re: Authorising trains to pass Signal 116 at danger 21/01/2012 at 15:46 #27889
Firefly
Avatar
521 posts
Quote:
Firefly wrote:
This should also happen in overlap track circuits if a train SPAD's despite the fact that you have route lights lit.

Just recreated the circumstances described by UKTM, and 201 does indeed illuminate normally despite having no route set through it - just the overlap from the signal in rear. The following TC, 202, is beyond the end of the overlap and floods as expected and described.
Yep in the real world TC 201 would also flood because there's no route set through it.

Log in to reply
Re: Authorising trains to pass Signal 116 at danger 21/01/2012 at 19:40 #27911
Josie
Avatar
310 posts
" said:
" said:
As the train occupies TC T202, the train comes to a halt (basically stopping over Camden South Jn). Checking F2, it flits between "Run out of valid track/Moving at 0mph/Stopped at signal", and just stays doing that.
It's not a Euston bug, it's in the core code. I can see the code doing the wrong thing in this case, but figuring out the right thing will be a bit harder.
Is this the same/similar problem with 'pass next signal' as I've mentioned before? (I can't remember which of the three options I'd chosen in that case.)

Log in to reply