How to Control Signals in Sessions
From TrainzOnline
(Difference between revisions)
(→Explanation) |
|||
| Line 12: | Line 12: | ||
='''Application 1: Fixed Signals'''= | ='''Application 1: Fixed Signals'''= | ||
| − | == | + | <table cellpadding="4" bgcolor=#ffffff> |
| − | + | <tr valign="top"> | |
| + | <td>[[file:binoculars.PNG]]</td> | ||
| + | <td><font size="3">'''The Scenario:'''</font></td> | ||
| + | </tr> | ||
| + | </table> | ||
| + | ---- | ||
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. | 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. | ||
| − | + | <br><br> | |
| − | == | + | <table cellpadding="4" bgcolor=#ffffff> |
| − | + | <tr valign="top"> | |
| + | <td>[[file:Gears.PNG]]</td> | ||
| + | <td><font size="3">'''Rules Used:'''</font></td> | ||
| + | </tr> | ||
| + | </table> | ||
| + | ---- | ||
*'''[[Session_Rule_List_with_Parameters#Ordered_List_Rule|Ordered List Rule]]''' creates a "container" for all the '''Set Signal Extended''' rules. | *'''[[Session_Rule_List_with_Parameters#Ordered_List_Rule|Ordered List Rule]]''' creates a "container" for all the '''Set Signal Extended''' rules. | ||
*'''[[Session_Rule_List_with_Parameters#Set_Signal_Extended_Rule|Set Signal Extended Rule]]''' to set signals to the required state. This rule can only set a single signal at a time. | *'''[[Session_Rule_List_with_Parameters#Set_Signal_Extended_Rule|Set Signal Extended Rule]]''' to set signals to the required state. This rule can only set a single signal at a time. | ||
| − | + | <br> | |
| − | == | + | <table cellpadding="4" bgcolor=#ffffff> |
| + | <tr valign="top"> | ||
| + | <td>[[file:screenshot.PNG]]</td> | ||
| + | <td><font size="3">'''Session Editor Screenshot:'''</font></td> | ||
| + | </tr> | ||
| + | </table> | ||
| + | ---- | ||
<table> | <table> | ||
<tr> | <tr> | ||
| Line 27: | Line 43: | ||
</tr> | </tr> | ||
</table> | </table> | ||
| − | + | <br> | |
| − | == | + | <table cellpadding="4" bgcolor=#ffffff> |
| − | + | <tr valign="top"> | |
| + | <td>[[file:explanation.PNG]]</td> | ||
| + | <td><font size="3">'''Description:'''</font></td> | ||
| + | </tr> | ||
| + | </table> | ||
| + | ---- | ||
*'''Line 1: Ordered List''' Not absolutely necessary but it places all the '''Set Signal Extended''' rules in a single container | *'''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 2: Set Signal Extended''' The first signal along the route is fixed at '''PROCEED''' | ||
| Line 60: | Line 81: | ||
</table> | </table> | ||
<br> | <br> | ||
| − | |||
='''Application 2: Halt Before Clear'''= | ='''Application 2: Halt Before Clear'''= | ||
| − | == | + | <table cellpadding="4" bgcolor=#ffffff> |
| − | + | <tr valign="top"> | |
| + | <td>[[file:binoculars.PNG]]</td> | ||
| + | <td><font size="3">'''The Scenario:'''</font></td> | ||
| + | </tr> | ||
| + | </table> | ||
| + | ---- | ||
A train approaching a signal must come to a complete stop before the signal is changed from '''STOP''' to '''PROCEED'''. | A train approaching a signal must come to a complete stop before the signal is changed from '''STOP''' to '''PROCEED'''. | ||
| − | + | <br><br> | |
| − | == | + | <table cellpadding="4" bgcolor=#ffffff> |
| − | + | <tr valign="top"> | |
| + | <td>[[file:conditions.PNG]]</td> | ||
| + | <td><font size="3">'''Preconditions:'''</font></td> | ||
| + | </tr> | ||
| + | </table> | ||
| + | ---- | ||
*'''[[Session_Rule_List_with_Parameters#Set_Signal_Extended_Rule|Set Signal Extended Rule]]''' to initially set the signal to '''STOP'''. | *'''[[Session_Rule_List_with_Parameters#Set_Signal_Extended_Rule|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.<br> | *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.<br> | ||
| Line 76: | Line 106: | ||
</tr> | </tr> | ||
</table> | </table> | ||
| − | + | <br> | |
| − | == | + | <table cellpadding="4" bgcolor=#ffffff> |
| − | + | <tr valign="top"> | |
| + | <td>[[file:Gears.PNG]]</td> | ||
| + | <td><font size="3">'''Rules Used:'''</font></td> | ||
| + | </tr> | ||
| + | </table> | ||
| + | ---- | ||
*'''[[Session_Rule_List_with_Parameters#Directional_Trigger_Check_Rule|Directional Trigger Check Rule]]''' to trigger the event for trains approaching the signal. | *'''[[Session_Rule_List_with_Parameters#Directional_Trigger_Check_Rule|Directional Trigger Check Rule]]''' to trigger the event for trains approaching the signal. | ||
*'''[[Session_Rule_List_with_Parameters#Wait_on_Train_Stop/Start_Rule|Wait on Train Stop/Start Rule]]''' to trigger an event when the consist stops moving. | *'''[[Session_Rule_List_with_Parameters#Wait_on_Train_Stop/Start_Rule|Wait on Train Stop/Start Rule]]''' to trigger an event when the consist stops moving. | ||
*'''[[Session_Rule_List_with_Parameters#Wait_Rule|Wait Rule]]''' to wait a set time interval. | *'''[[Session_Rule_List_with_Parameters#Wait_Rule|Wait Rule]]''' to wait a set time interval. | ||
*'''[[Session_Rule_List_with_Parameters#Set_Signal_Extended_Rule|Set Signal Extended Rule]]''' to clear the signal after the train has stopped. | *'''[[Session_Rule_List_with_Parameters#Set_Signal_Extended_Rule|Set Signal Extended Rule]]''' to clear the signal after the train has stopped. | ||
| − | + | <br> | |
| − | == | + | <table cellpadding="4" bgcolor=#ffffff> |
| + | <tr valign="top"> | ||
| + | <td>[[file:screenshot.PNG]]</td> | ||
| + | <td><font size="3">'''Session Editor Screenshot:'''</font></td> | ||
| + | </tr> | ||
| + | </table> | ||
| + | ---- | ||
<table> | <table> | ||
<tr> | <tr> | ||
| Line 90: | Line 131: | ||
</tr> | </tr> | ||
</table> | </table> | ||
| − | + | <br> | |
| − | == | + | <table cellpadding="4" bgcolor=#ffffff> |
| − | + | <tr valign="top"> | |
| + | <td>[[file:explanation.PNG]]</td> | ||
| + | <td><font size="3">'''Description:'''</font></td> | ||
| + | </tr> | ||
| + | </table> | ||
| + | ---- | ||
*'''Line 1: Directional Trigger Check''' set to trigger when a train approaches the signal from the facing direction. | *'''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 2: Wait on Train Stop/Start''' set to trigger when the train stops moving. | ||
Revision as of 21:58, 11 July 2018
Contents |
 |
Signals can be controlled by Session Rules during the running of a Session. |
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):-
|
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.
- Line 3: Wait for 10 seconds.
- Line 2: Wait on Train Stop/Start set to trigger when the train stops moving.
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
- How to Guides
- Session Rules List (Alphabetical) with Parameters
- Session Rules List (Categories) With Parameters
Route Creation Tutorials:
Session Creation Tutorials:
- Adding Message Popups
- Adding Message Popups - Applications
- Adding Navigation Points
- Adding Navigation Points - Applications
- Configuring the Driver Setup Rule
- Controlling Junctions in Sessions
- Creating a HTML Asset (Session Introduction Page and In Game Messages)
- List of Parent Rules
- Parent and Child Rules
- Using Track Triggers
- Using Variables in Sessions - Examples
