How to Control Signals in Sessions

From TrainzOnline
Revision as of 22:00, 23 November 2023 by Pware (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

The information in this Wiki Page applies to TANE, TRS19, Trainz Plus and TRS22. It gives examples of how signals can be controlled using Session Rules.

Contents

BlueDot10x10.png Signals can be controlled by Session Rules during the running of a Session
BlueDot10x10.png The level of control includes:-
BlackDot10x10.png locking selected signals in a set state
BlackDot10x10.png setting signals according to the actions of users


The following applications give examples of using Session Rules to control signals.

Application 1: Fixed Signals

    Top   Next Down Bottom
Magnifier.png The Scenario:
It is after hours and all the signal staff on a single track branch line have clocked off for the night. All approach and depart signals on the line are locked at PROCEED and safe working is now the responsibility of the train crew. The signals will not reset to STOP when passed by a train.
RulesWiki.PNG Rules Used:
DotPoint.JPG Ordered List Rule creates a "container" for all the Set Signal Extended rules
DotPoint.JPG Set Signal Extended Rule to set signals to the required state. This rule can only set a single signal at a time so multiple copies of the rule are needed to set multiple signals
Screenshot.PNG Session Editor Screenshot:
SetFixedSignals.JPG
Explanation.PNG Description:
Line  1 : Ordered List Not absolutely necessary but it places all the Set Signal Extended rules in a single container which makes them easier to manage
Line  2 : Set Signal Extended The first signal along the route is fixed at PROCEED
Line  3 : Set Signal Extended The next signal along the route is fixed at PROCEED
...and this is repeated for all the signals along the route.
SetSignalProceed.JPG

When the Set Signal Extended Rule is opened for editing (shown left):-

Steps: To set a signal state:-
DotPoint1.JPG select the signal name from the session list
DotPoint2.JPG select the signal state from the list of available states
DotPoint3.JPG Left Click the Tick.PNG icon
Stop.PNG The state selected for the signal must be supported on that particular signal otherwise no change will occur.


Application 2: Halt Before Clear

Top Next Up   Bottom
Magnifier.png The Scenario:
A train approaching a signal must come to a complete stop before the signal is changed from STOP to PROCEED
Conditions.PNG Preconditions:
DotPoint.JPG Use the Set Signal Extended Rule to initially set the signal to STOP
DotPoint.JPG This scenario uses the Directional Trigger from the DLS (<kuid:76656:70010> shown below) to make sure that only trains approaching the facing signal will trigger the rule. Trains travelling in the opposite direction will not trigger the rule.
DirectionalTriggerObject.JPG


RulesWiki.PNG Rules Used:
DotPoint.JPG Set Signal Extended Rule to initially set the signal to STOP (in Preconditions above) and to clear the signal after the train has stopped
DotPoint.JPG Directional Trigger Check Rule to trigger the event for trains approaching the signal
DotPoint.JPG Wait on Train Stop/Start Rule to trigger an event when the consist stops moving
DotPoint.JPG Wait Rule to wait a set time interval
Screenshot.PNG Session Editor Screenshot:
DirectionalTriggerSession.JPG
Explanation.PNG Description:
Line  1 : Directional Trigger Check set to trigger when a train approaches the signal from the facing direction
Line  2 Wait on Train Stop/Start set to trigger when the train stops moving
Line  3  Wait for 10 seconds
Line  4  Set Signal Extended sets the signal to AUTOMATIC or PROCEED
If the train passes the signal without stopping then the WikiLink.PNG Signal Passed at Danger Rule can be used to deal with the situation.


  Top Next Up    


Trainz Wiki

TrainzWiki.png

More Tutorials and Guides to Using Trainz

LinkWiki.PNG

Related Links


This page was created by Trainz user pware in May 2018 and was last updated as shown below.


Personal tools