Approach_Medium
Trainz Addict
Hi all;
I have some intriguing problems with my signals.
I am building a large route, and have set up some single track with passing tracks.
I have placed signals at each end of the passing tracks, and intermediate signals between the interlockings on the single track.
I have included a track diagram below.
The signals I am using are:
Safetran Clight Signal 08 Interlocking for the interlockings
Safetran Clight Signal 05 for the intermediates.
Problem #1
In a particular stretch of single track that lies between interlockings, I have 4 intermediate signals, and 3 industry sidings located close to one of the interlockings.
The problem I have is that when there are two trains heading towards each other from the interlockings onto single track, it is possible for both trains to enter the single track at the same time.
Note that the diagrams below are captured from Train Dispatcher 3, a CTC simulation
I have not aligned the interlocking at CP10, because I wanted to show what happens in TS when both interlockings are lined to the same section of single track.
This CTC simulation will not allow me to do this, thus I cannot actually show it in the diagram.
Fig 1
Train at CP22 (right) is going to get the railroad while train at CP10 (left) is going to wait until the southbound clears the interlocking.
Fig 2
Train at CP22 has proceeded onto the single track, but at this point, the train waiting at CP10 still has a green light (switch is lined for that train onto the single track as well. This is not allowed on a CTC system, but it is allowed in Trainz.
The northbound signal at CP10 will not change to red until the southbound train is south of the switch for industry G1.
Fig 3.
Southbound train has passed the siding at G1, and northbound signal at CP10 turns red.
I understand why this happens.
TS signals search for trains approaching, but only until they reach a junction. When that happens without finding a train approaching, the search ends, and the signal initiating the search displays according to the next signal.
The approaching southbound is still not detected by CP10 northbound because the junction G1, G2, and G3 (actually, it's the first junction that really matters) lies between the starting signal and the train.
If the scenario is reversed, where the northbound train gets the railroad and the southbound is waiting at CP22, things are different.
As soon as the northbound train goes north of the CP10 interlocking, the southbound signal at CP22 turns red.
This happens because the block up to the first industry, G1 is now considered occupied, and since there are no signals between that point and CP22, the home signal is also red. If there were one more signal between those points, then the home signal at CP22 woudl be yellow (approach).
What I need is a way to tell TS that the industry junctions should be ignored, and the search should continue until it reaches the next interlocking, or home signal (or it finds an approaching train).
I tried adding direction markers to each siding, pointing out, thinking that the search would hit those and ignore the junction, but that did not work.
Short of modifying the signal’s script, I really don’t know what to do.
I don’t know whether modifying the Safetran’s script would even help, since I have also tried this scenario with TS built-in USA 01 (unscripted) signals, and got the same results.
--------------------------------------------------------------------------
Problem #2
There is yet another strange problem, and this one may explain why some TS players have problems when AI is running on signaled track.
If there is a train approaching a home signal, that signal will always be red, to prevent another train from occupying the same track in opposite direction.
If that approaching train is stopped, then reversed, the home signal will change, reflecting the fact that the train ahead is no longer approaching, but moving away.
When I first started my signals testing on a separate route I built for this purpose, I found that sometimes the home signal would change (from stop) to a less restrictive aspect after the approaching train had come to a stop.
I could not figure out what was happening at first, but then I realized that because I was running in DCC mode, the train’s brakes were not being applied properly, and when the train came to a stop, the train would “bounce” backwards just a hair because the train’s brakes were off.
This happens in DCC, because it is a simple way of stopping the train.
The problem is that this is the way that AI runs trains. I confirmed this by setting up a couple of track markers, and added wait commands to have trains stop, then start again along the way.
The result was that sometimes the back-bounce would occur.
When I switched to cab mode, and controlled the train myself, using proper braking procedures, I prevented this backwards bounce, and thus the signal issue.
Anyone have any ideas on problem #1?
Thanks
FW
I have some intriguing problems with my signals.
I am building a large route, and have set up some single track with passing tracks.
I have placed signals at each end of the passing tracks, and intermediate signals between the interlockings on the single track.
I have included a track diagram below.
The signals I am using are:
Safetran Clight Signal 08 Interlocking for the interlockings
Safetran Clight Signal 05 for the intermediates.
Problem #1
In a particular stretch of single track that lies between interlockings, I have 4 intermediate signals, and 3 industry sidings located close to one of the interlockings.
The problem I have is that when there are two trains heading towards each other from the interlockings onto single track, it is possible for both trains to enter the single track at the same time.
Note that the diagrams below are captured from Train Dispatcher 3, a CTC simulation
I have not aligned the interlocking at CP10, because I wanted to show what happens in TS when both interlockings are lined to the same section of single track.
This CTC simulation will not allow me to do this, thus I cannot actually show it in the diagram.
Fig 1
Train at CP22 (right) is going to get the railroad while train at CP10 (left) is going to wait until the southbound clears the interlocking.
Fig 2
Train at CP22 has proceeded onto the single track, but at this point, the train waiting at CP10 still has a green light (switch is lined for that train onto the single track as well. This is not allowed on a CTC system, but it is allowed in Trainz.
The northbound signal at CP10 will not change to red until the southbound train is south of the switch for industry G1.
Fig 3.
Southbound train has passed the siding at G1, and northbound signal at CP10 turns red.
I understand why this happens.
TS signals search for trains approaching, but only until they reach a junction. When that happens without finding a train approaching, the search ends, and the signal initiating the search displays according to the next signal.
The approaching southbound is still not detected by CP10 northbound because the junction G1, G2, and G3 (actually, it's the first junction that really matters) lies between the starting signal and the train.
If the scenario is reversed, where the northbound train gets the railroad and the southbound is waiting at CP22, things are different.
As soon as the northbound train goes north of the CP10 interlocking, the southbound signal at CP22 turns red.
This happens because the block up to the first industry, G1 is now considered occupied, and since there are no signals between that point and CP22, the home signal is also red. If there were one more signal between those points, then the home signal at CP22 woudl be yellow (approach).
What I need is a way to tell TS that the industry junctions should be ignored, and the search should continue until it reaches the next interlocking, or home signal (or it finds an approaching train).
I tried adding direction markers to each siding, pointing out, thinking that the search would hit those and ignore the junction, but that did not work.
Short of modifying the signal’s script, I really don’t know what to do.
I don’t know whether modifying the Safetran’s script would even help, since I have also tried this scenario with TS built-in USA 01 (unscripted) signals, and got the same results.
--------------------------------------------------------------------------
Problem #2
There is yet another strange problem, and this one may explain why some TS players have problems when AI is running on signaled track.
If there is a train approaching a home signal, that signal will always be red, to prevent another train from occupying the same track in opposite direction.
If that approaching train is stopped, then reversed, the home signal will change, reflecting the fact that the train ahead is no longer approaching, but moving away.
When I first started my signals testing on a separate route I built for this purpose, I found that sometimes the home signal would change (from stop) to a less restrictive aspect after the approaching train had come to a stop.
I could not figure out what was happening at first, but then I realized that because I was running in DCC mode, the train’s brakes were not being applied properly, and when the train came to a stop, the train would “bounce” backwards just a hair because the train’s brakes were off.
This happens in DCC, because it is a simple way of stopping the train.
The problem is that this is the way that AI runs trains. I confirmed this by setting up a couple of track markers, and added wait commands to have trains stop, then start again along the way.
The result was that sometimes the back-bounce would occur.
When I switched to cab mode, and controlled the train myself, using proper braking procedures, I prevented this backwards bounce, and thus the signal issue.
Anyone have any ideas on problem #1?
Thanks
FW
Last edited:
}
i will get a new batch to you in the morning.