creating Track Circuit Failures?

[tubemad]

Hello All,

I have been trying (and failing) to come up with a new idea for activities, and that is to try an simulate Track Circuit Failures (TCF for short). For those who don't know, a TCF is where a track circuit is de-energized and hasn't re-renergized when the last train left the block, so it thinks there is a train still in the section. This would mean the signal prior to the affected section would remain red.

I have tried setting up a blocker, having it stop in the block ahead and then tried to pass the signal at red, but the signaller says no. I've tried various places and directions to hold the blocker, but it still won't work. I know this is MSTS and to the American system, a TCF is probably un-heard of anyway (much like TPWS, AWS etc).

9/10 there is usually a way around this brick wall, but at the moment there isn't one. Does anyone have any idea's on how to simulate a TCF? It is becoming a tough puzzle but I would be interested in hearing ideas.
Maybe this could be something implemented into OpenRails if not?


Cheers,

James.

[borthstation]

Hi, James,
I may be misunderstanding this, but I imagine that you're trying to get a stop at a red and then pass it by contacting the signalman? if so, then simply set the signal to "failed" on the AE map. You will now need a TAB to pass the signal. You can do this on the move, if you want, and unfairly get clearance. To force the stop, try setting a location event that coincides with the signal - you can also get it to display a "Contacting signalman" message if you want. Set a "speed must be zero" situation. The outcomes will be to proceed if speed = zero and to display SPAD message if train did not stop. I haven't got my own computer in front of me at present to say exactly what to do - but I did an activity in snow on the S&C ages ago where a signal had failed and you were forced into stopping and then got a message from the signalman. This will be similar, i think.
Give it a play about and see what you come up with - signal set to failure + coinciding location event.
Good luck,
Chris.

[tubemad]

Hello Chris,

I know what you mean and have used this failed signal thing before (and had to use messages on short block sections as it, annoyingly, shows green before the failed signal!)

I am trying to do it a bit different. In reality, the signal would show an aspect of red rather than a blank aspect (as this would be a signal failure) but the signal has not failed, the circuit in the track has. The reason it remains red is because it 'thinks' there's a train in the section, but there isn't.

Drivers must then call up and ask to pass the signal at danger, and then proceed at the caution limit until the next signal. If you are the first train to pass the signal at red, you have to examine the line (driving slowly) and then call up at the next signal to confirm the section is clear.

It's a matter of wondering if there is a way of keeping a signal at red and being able to pass it...currently I think I am defeated here, but if anyone knows a good old trick, I would like to hear it!


Cheers,

James.

[borthstation]

Hi James,
I understand more clearly now. I can't personally think of any way of passing a red within what is available as standard on MSTS. There is a theoretical way - especially if you wanted to limit it to one signal - that would involve probably creating a new signal with a revised signal script file to cope with the situation, but it might be rather a challenge! Maybe one of the signal designers would know if it was possible?
Good luck!
Chris.

[jimmyladd]

Try applying a reverse point just after the signal, and another just before it. If my theory is right, you'll get ambers before the signal, and by asking the signal man to tab passed the red signal the reverse points should dissapear as you roll passed, and your next signal will be green providing the path is clear.

[krausyao]

If there is a switch in the track segment the following technique will simulate a track circuit failure. Place a loose consist on the diverging side of a switch closer than the clearance distance and not on the path of the player train. For the loose consist choose an invisible wagon with a narrow bounding box to avoid collision with the player train. With the loose consist closer than the clearance distance both tracks on the diverging side will show occupied. The player train can request clearance to pass the stop signal. Traffic trains will not request clearance and will not pass the signal. Both player and traffic trains will pass the signal in Acticity Editor due to the difference in function block_state and loose consists.