Revision as of 12:54, 20 December 2022

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 1 Application 1: Fixed Signals 2 Application 2: Halt Before Clear 3 Trainz Wiki

In Summary: Signals can be controlled by Session Rules during the running of a Session The level of control can involve:- locking selected signals in a set state setting signals according to the actions of users

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

Application 1: Fixed Signals

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.

Rules Used:

• Ordered List Rule creates a "container" for all the Set Signal Extended rules.
• Set Signal Extended Rule to set signals to the required state. This rule can only set a single signal at a time.

Session Editor Screenshot:

Description:

• Line 1: Ordered List Not absolutely necessary but it places all the Set Signal Extended rules in a single container
  • 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.

When the Set Signal Extended Rule is opened for editing (shown left):- Steps: Select the signal name from the session list Select the signal state from the list of available states Click the icon The state selected for the signal must be supported on that particular signal otherwise no change will occur.

Application 2: Halt Before Clear

The Scenario:

A train approaching a signal must come to a complete stop before the signal is changed from STOP to PROCEED.

Preconditions:

• Set Signal Extended Rule to initially set the signal to STOP.
• 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.
  

Rules Used:

• Directional Trigger Check Rule to trigger the event for trains approaching the signal.
• Wait on Train Stop/Start Rule to trigger an event when the consist stops moving.
• Wait Rule to wait a set time interval.
• Set Signal Extended Rule to clear the signal after the train has stopped.

Session Editor Screenshot:

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 Signal Passed at Danger Rule can be used to deal with the situation.

Trainz Wiki

More Tutorials and Guides to Using Trainz How to Guides Driver Commands List Session Rules List (Alphabetical) with Parameters Session Rules List (Categories) With Parameters

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