I have a level crossing where the train has to stop to set it (using ATLS commands) but it clears automatically with trigger. Because it takes some time to get that process running, I want to make sure there is time for traffic to cross between trains. Essentially, what I need is a way to make a segment of track look blocked to the AI for about 5 minutes after the crossing is cleared, then become available after the 5 minutes is over. What is the easiest way to do this? I tried using an invisible train as a 'relay' of sorts, but I could never get it to work out properly.
Restrict track access for a set time
- Thread starter REISCOOL
- Start date
Well, I did some experimenting and here's where I'm at:
I've set up a list of rules like so:
('>' stands for a indented rule, 2 for 2 indentations,etc.)
Reset list
>Set Signal Extended Rule - Sets the WB signal to proceed (The signals merely protect the crossing. the line is set for single line token running, so having 2 proceeds facing each other is ok)
>Set Signal Extended Rule - Sets the EB signal to proceed
>Check Trackside - waits for any train to enter the trigger that clears the crossing
>>Set Signal Extended Rule - Sets the WB signal to stop
>>Set Signal Extended Rule - Sets the EB signal to stop
>>Check Trackside - waits for any train to leave the trigger that clears the crossing
>>>Wait - 150 seconds (I decided that 5 mins was far too long)
This seems to work up until it gets to the 'Wait' rule. If my setup is right, shouldn't it reset the list and stat back to where it sets the signals to proceed?
EDIT: I think the problem lies in the Set Signal Extended rule. Since a reset list needs all child rules to complete before resetting, and I've made sure that the Check Tracksides are not set to auto-reset, it must be that the Set Signal Extendeds are still 'running'. Is this (manually setting a signal state) a process that has to keep running, or does the signal system just say X signal go to Y state and then shuts down?
I've set up a list of rules like so:
('>' stands for a indented rule, 2 for 2 indentations,etc.)
Reset list
>Set Signal Extended Rule - Sets the WB signal to proceed (The signals merely protect the crossing. the line is set for single line token running, so having 2 proceeds facing each other is ok)
>Set Signal Extended Rule - Sets the EB signal to proceed
>Check Trackside - waits for any train to enter the trigger that clears the crossing
>>Set Signal Extended Rule - Sets the WB signal to stop
>>Set Signal Extended Rule - Sets the EB signal to stop
>>Check Trackside - waits for any train to leave the trigger that clears the crossing
>>>Wait - 150 seconds (I decided that 5 mins was far too long)
This seems to work up until it gets to the 'Wait' rule. If my setup is right, shouldn't it reset the list and stat back to where it sets the signals to proceed?
EDIT: I think the problem lies in the Set Signal Extended rule. Since a reset list needs all child rules to complete before resetting, and I've made sure that the Check Tracksides are not set to auto-reset, it must be that the Set Signal Extendeds are still 'running'. Is this (manually setting a signal state) a process that has to keep running, or does the signal system just say X signal go to Y state and then shuts down?
Last edited:
Zec,
This is what I do to protect my yard throat. This allows the freight cars to sit on the sidings without stopping the traffic on the road. When I'm ready to move a train, I have to remember to switch the lever since my method is more manual, but it would be that way in a yard if you think about it.
John
shaneturner12
Tutorial Creator
I would advise you check what you have your Wait rule set to do - it's [seconds] +/- [leeway seconds].
Shane
I've got it to work. For anyone who wants it, here's what I've got:
(again, each '>' stands for 1 indention)
Ordered List - Set to repeat forever
>Set Signal Extended Rule - Set EB signal to Proceed
>Set Signal Extended Rule - Set WB signal to Proceed
>Check Trackside - Wait for any vehicle to enter crossing trigger
>>Set Signal Extended Rule - Set EB signal to Stop
>>Set Signal Extended Rule - Set WB signal to Stop
>>Check Trackside - Wait for any vehicle to leave crossing trigger
>>>Wait - 150 seconds plus/minus 0
Driver commands for each train going to the crossing
Navigate to trackmark > Crossing Wait Point (WB or EB depending on direction)
Wait until not red (Keeps the crossing from being activated in the 2.5 minute waiting period)
Wait for 1 minute (The crewman has to walk up to the electrical box at the crossing to turn it on. This simulates that walk)
ATLS trigger command (Actually turns on the crossing)
Wait for 1 minute (walking back to the engine)
-Some driving command here. The crossing clears automatically, so this is just the continuation of the train's schedule-
Now all I need to do is make a proper signal for it. For testing I used a simple red/green 2 aspect signal, and it looks concerning when a train stops dead at a green signal
.
(again, each '>' stands for 1 indention)
Ordered List - Set to repeat forever
>Set Signal Extended Rule - Set EB signal to Proceed
>Set Signal Extended Rule - Set WB signal to Proceed
>Check Trackside - Wait for any vehicle to enter crossing trigger
>>Set Signal Extended Rule - Set EB signal to Stop
>>Set Signal Extended Rule - Set WB signal to Stop
>>Check Trackside - Wait for any vehicle to leave crossing trigger
>>>Wait - 150 seconds plus/minus 0
Driver commands for each train going to the crossing
Navigate to trackmark > Crossing Wait Point (WB or EB depending on direction)
Wait until not red (Keeps the crossing from being activated in the 2.5 minute waiting period)
Wait for 1 minute (The crewman has to walk up to the electrical box at the crossing to turn it on. This simulates that walk)
ATLS trigger command (Actually turns on the crossing)
Wait for 1 minute (walking back to the engine)
-Some driving command here. The crossing clears automatically, so this is just the continuation of the train's schedule-
Now all I need to do is make a proper signal for it. For testing I used a simple red/green 2 aspect signal, and it looks concerning when a train stops dead at a green signal
.shaneturner12
Tutorial Creator
A slight adjustment I would make -if Set Signal Extended supports it, set it to Automatic rather than Proceed (apologies if you've already done this)
Shane
Shane
The line is set for Token operation. The only occupancy signals are at passing loops and are invisible. These signals merely protect the crossing timer, so the only thing that setting them to automatic would do is make the opposite signal red when a train approaches, which is a waste because if there is an oncoming train, it's waiting in the passing loop. Set Signal Extended does support automatic, though.
shaneturner12
Tutorial Creator
Reason I suggested that is because AI trains have problems with non-automatic signals.
Shane
Shane
stagecoach
75377
Dont use ATLS triggers on approach, instead drive to TM, wait 3.5min, ATLS driver command, wait 1min, drivet to? Use the sen city signals as these are ATLS operated and should show red until the ATLS has been activated. You will need a trigger to reset the crossing after the train passes. If this is a single track then you need a trigger on both sides but set them with different priorities and set the train priority to match. This can be done on a temporary measure while using the crossing.
norfolksouthern37
what's a normal map?
this is not really true. there is no difference in setting a signal to proceed and letting the automatic code set it to proceed. the states are the same internally. it is when you set a signal to a state undefined in the native code that the ai will not understand it, and without a custom signal script, that usually is not possible since the code would determine the nearest display state in the signal's config.