ATLS Trigger Not Working

[AdvancedApproach]

I have an advanced ATLS Crossing setup. Eight triggers in total, four on each track, all are set to the appropriate channel. I have the triggers set up to a two-way four trigger system. The ATLS Controller and Slave are active and set up properly a too. Yet the crossings don't activate until a train is right on that crossing. How do I fix this? It's happening with only one of the crossings.

 

[AdvancedApproach]

 

[stagecoach]

It depends on the speed of the train and the distance the first trigger is away from the crossing. You can use more than 4 triggers on a track.
First trigger set half a mile away, set for priority 1 only. All fast trains using priority 1 will trigger the crossing. Second trigger 1/4 miles away, set for priority 2 only. All trains using priority 2 will pass the first trigger and only trigger the crossing at the second trigger. The third trigger on the crossing set for all priority trains.
Set up
Trigger 1 = Priority 1 Fast train
Trigger 2 = Priority 2 Normal train
Trigger 3 = Priority 3 Slow train
Trigger 4 = On the crossing set for all 3 priorities
So a total of 8 triggers could be used on one track, depending on train speed.

 

[AdvancedApproach]

It depends on the speed of the train and the distance the first trigger is away from the crossing. You can use more than 4 triggers on a track.
First trigger set half a mile away, set for priority 1 only. All fast trains using priority 1 will trigger the crossing. Second trigger 1/4 miles away, set for priority 2 only. All trains using priority 2 will pass the first trigger and only trigger the crossing at the second trigger. The third trigger on the crossing set for all priority trains.
Set up
Trigger 1 = Priority 1 Fast train
Trigger 2 = Priority 2 Normal train
Trigger 3 = Priority 3 Slow train
Trigger 4 = On the crossing set for all 3 priorities
So a total of 8 triggers could be used on one track, depending on train speed.

Upon further review it was determined that for some reason unbeknownst to me, the ATLS Trigger was assigned a channel number on route layer but not for my session. The problem has been fixed.

 

[AdvancedApproach]

@n3vgames still not working. I need answers.

 

[Firefighterdan]

Delete all the invisible tracks and start over. Go from the slave to the crossing gate, then to the traffic stopper, then to the second gate. In your screenshot, it looks like the crossing gates and the traffic stopper are not connected to the slave.

 

[bolivar]

You need to add brackets with a..b..c..etc for each trigger . Otherwise they do not function. Example : ATLS28[0,4](a), then ATLS28[0,4](b) and so on..

 

[AdvancedApproach]

Delete all the invisible tracks and start over. Go from the slave to the crossing gate, then to the traffic stopper, then to the second gate. In your screenshot, it looks like the crossing gates and the traffic stopper are not connected to the slave.

They're attached to the slave. When I deleted and readded the ATLS Controller everything was working fine. Not sure what's causing these issues but very irritating.

 

[JCitron]

They're attached to the slave. When I deleted and readded the ATLS Controller everything was working fine. Not sure what's causing these issues but very irritating.

I had that occur after the components were updated. What's interesting is that happened only on some crossings but not others and I have a lot of ATLS crossings on my big route.

 

[AdvancedApproach]

Alright, how do I fix this? The crossings activate and won't shut off even after clearing all four ATLS triggers. What can I do to fix this?

 

[stagecoach]

Why have you got a Route 3? Route 3 is all red, so it will always be a stop. The slave on the crossing would be LCM, or both selections on route 3 should be green. Triggers only activate the SPL in the controller, which then overrides the other settings. The road across the junction (route 1) could have the SPL set to green as it would not affect the road from the track crossing.

Your earlier question shows 5 triggers.

 

[AdvancedApproach]

Why have you got a Route 3? Route 3 is all red, so it will always be a stop. The slave on the crossing would be LCM, or both selections on route 3 should be green. Triggers only activate the SPL in the controller, which then overrides the other settings. The road across the junction (route 1) could have the SPL set to green as it would not affect the road from the track crossing.

Your earlier question shows 5 triggers.

Oddly enough my original route has the exact same setup but with the TF legacy version of the ATLS Slave and everything works normal.

 

[stagecoach]

The slaves operate in a different way. The old slave used an invisible train to control the crossings, while the new one only uses commands. The old system still works in TRS22 and is my preferred option.

 

[AdvancedApproach]

The slaves operate in a different way. The old slave used an invisible train to control the crossings, while the new one only uses commands. The old system still works in TRS22 and is my preferred option.

The problem is the old system sometimes won't remove the invisible train. I've dealt with this myself. On the other hand, the newer system doesn't seem to mesh well with the setup included here. When I used the system everything works perfectly fine. The same can't be said for the newer system.