How to Control Signals in Sessions

From TrainzOnline
Revision as of 00:01, 23 May 2018 by Pware (talk | contribs) (Created page with "The screenshots shown below give examples of how signals can be controlled in sessions. ==='''Application 1: Fixed Signals'''=== '''1. The Scenario:''' It is after hours an...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

The screenshots shown below give examples of how signals can be controlled in sessions.

Application 1: Fixed Signals

1. 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.

2. Rules Used:

3. Session Rules Screenshot:

4. Example Explanation:

  • 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):-

  • Select the signal name from the session list
  • Select the signal state from the list of available states


Note:
The state selected for the signal must be supported on that particular signal otherwise no change will occur.

Application 2:

1. The Scenario:

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

2. Preconditions:

3. Rules Used:

4. Session Rules Screenshot:

5. Example Explanation: