Main route interactions
Main route setting interactionsZST+ZZT pressed
The collaboration diagrams, below shows the communication between components to achieve a main route settings.
The first diagram covers main route setting between an entrance signal and an exit signal. The messages and purpose of them between the components are:
- reqMainRoute:
Obtain CabNo - getMainRoute:
Check if route is clear.
Deliver CabNo to traction selectors.
Set target point route at turnouts. - setMainRoute:
Set route status at main signals.
Obtain aspect target main signal.
Enable traction at traction selectors.
Lock turnouts.
Obtain lowest maximum speed of points.
Set aspect at start distance and main signal.
The diagrams below shows the communication between components to achieve this main route setting.
Message 1: reqMainRoute
| Component | Prerequisite | Action |
|---|---|---|
| Component | Prerequisite | Action |
| R3 | ZST pressed (Start). Not blocked. Not locked. | |
| VR3 | Not blocked. Not locked. | Send message 1. |
| Massage reference: 1.1 | ||
Message 2: getMainRoute
| Component | Prerequisite | Action |
|---|---|---|
| Component | Prerequisite | Action |
| 3 | Not vacant. Cab number is set. | Add Cab number to message 2. Send message 2. |
| Massage reference: 2.1 | ||
| VR3 | Not locked. | |
| R3 | Not blocked. Not locked. | Pass message 2 through. |
| Massage reference: 2.2 | ||
| 103 | Vacant. Not locked | Enable traction from Cab number in massage 2. Pass message 2 through. |
| Massage reference: 2.3 | ||
| W2 | Vacant. Not locked. Not blocked. | Add maximum speed to message 2 for both directions. Send message 2 in both directions. |
| Massage reference: 2.4 and 2.5.1 | ||
| W1 | Vacant. Not locked. Not blocked. | Store direction message 2 came from. Add maximum speed to message 2. Send message 2. |
| Massage reference: 2.5.2 | ||
| V1 | Not locked. Not blocked. | Pass message 2 through. |
| Massage reference: 2.5.3 | ||
| 101 | Vacant. Not locked | Enable traction from Cab number in massage 2. Pass message 2 through |
| Massage reference: 2.5.4 | ||
| n.V1 | Vacant. Not locked | Pass message 2 through |
| Massage reference: 2.5.5 | ||
| h | ||
| A | ZZT pressed (Target). Vacant. Not blocked. Not locked. | Pass message 2 through |
| Massage reference: 2.5.6 | ||
Message 3: setMainRoute
| Component | Prerequisite | Action |
|---|---|---|
| Component | Prerequisite | Action |
| The last automatic block, here Jp21 | Vacant. Not Locked | Enable traction from Cab number in massage 2. Send message 3. |
| Massage reference: 3.1 | ||
| … | ![]() |
… |
The second diagram covers a route between a exit signal and running track. The messages between the components and purpose of them are:
- reqMainRoute:
Obtain CabNo - getMainRoute:
Check if route is clear.
Deliver CabNo to traction selectors.
Set target point route at turnouts. - getOverlap:
Check if overlap route is clear. - setMainRoute:
Set route status at main signals.
Enable traction at traction selectors.
Set and lock turnouts.
Obtain lowest maximum speed of points.
Set aspect at start main signal.
The diagrams below shows the communication between components to achieve this main route setting.

Shunting route settings interactionsVST+VZT pressed
The collaboration diagrams, below shows the communication between components to achieve a shunting route settings.
The first diagrams covers a shunting route between a shunting signal at an exit signal to a terminating track. The messages and purpose of them between the components are:
- getShuntingRoute:
Check if no route is set.
Set target point route at turnouts. - setShuntingRoute:
Enable shunting traction at traction selectors.
Lock turnouts.
Show shunting allowed aspect.
Message 1: getShuntingRoute
| Component | Prerequisite | Action |
|---|---|---|
| Component | Prerequisite | Action |
| VR3 | VST pressed (Start). Not locked. Not blokked. | Send message 1. |
| R3 | Not locked. | Pass message 1 through. |
| Massage reference: 1.1 ⇨ | ||
| 103 | Pass message 1 through | |
| Massage reference: 1.2 ⇨ | ||
| W2 | Not Locked. Not blocked. | Pass message 1 to both turnout directions |
| Massage reference: 1.3.2 ⇨ | ||
| V1 | Not Locked. Not blocked. | Pass message 1 through |
| Massage reference: 1.3.3 ⇨ | ||
| 3b | Pass message 1 through | |
Message 2: setShuntingRoute
| Component | Prerequisite | Action |
|---|---|---|
| Component | Prerequisite | Action |
| n.V1 | VZT pressed (Target). Not Locked. Not blocked. | Set lock Send message 2 |
| Massage reference: ⇦ 2.1 | ||
| 3b | Allow traction Pass message 2 through |
|
| Massage reference: ⇦ 2.2 | ||
| V1 | Set lock Pass message 2 through |
|
| Massage reference: ⇦ 2.3 | ||
| W2 | Set lock Pass message 2 through to entry point of turnout | |
| Massage reference: ⇦ 2.4 | ||
| 103 | Allow traction Pass message 2 through |
|
| Massage reference: ⇦ 2.5 | ||
| R3 | Set lock Pass message 2 through |
|
| VR3 | Set Lock Set shunting allowed signal aspect Pass message 2 through |
|
| Massage reference: ⇦ 2.6 | ||
| 3 | Allow traction | |
The second diagram covers a route from a shunting signal. The messages between the components and purpose of them are:
- getShuntingRoute:
Check if no route is set.
Set target point route at turnouts. - setShuntingRoute:
Enable shunting traction at traction selectors.
Lock turnouts.
Show shunting allowed aspect.
Message 1: 
| Component | Prerequisite | Action |
|---|---|---|
| Component | Prerequisite | Action |
| … | … | … |
| Massage reference: … | ||
| … | ![]() |
… |
Main route releasing interactionTrain detection
The collaboration diagrams, below shows the communication between components to achieve a main route releasing.
The first diagram covers main route releasing from an exit signal to a running track. The messages and purpose of them between the components are:
- nonVacant:
Sets previous signal at danger. - nonVacant:
Sets previous signal at danger. - nonVacant:
Sets previous signal at danger.
Message 1: 
| Component | Prerequisite | Action |
|---|---|---|
| Component | Prerequisite | Action |
| … | … | … |
| Massage reference: … | ||
| … | ![]() |
… |
The second diagram covers main route releasing between a entrance and exit signal. The messages between the components and purpose of them are:
- nonVacant:
Sets previous signal at danger. - nonVacant:
Sets previous signal at danger. - nonVacant:
Sets previous signal at danger. - relMainRoute:
releases mainRouteSet next main or intermediate signal. - relOverlapRoute:
Releases overlapped traction selector.
Unlocks overlapped turnout.
Message 1: 
| Component | Prerequisite | Action |
|---|---|---|
| Component | Prerequisite | Action |
| … | … | … |
| Massage reference: … | ||
| … | ![]() |
… |
Shunting route releasing interactionsTrain detection
The collaboration diagrams, below shows the communication between components to achieve a shunting route releasing.
The first diagram covers shunting route releasing from an exit signal to a running track. The messages and purpose of them between the components are:
- nonVacant:
Sets previous signal at danger. - nonVacant:
Sets previous signal at danger.
Message 1: 
| Component | Prerequisite | Action |
|---|---|---|
| Component | Prerequisite | Action |
| … | … | … |
| Massage reference: … | ||
| … | ![]() |
… |
The second diagram covers shunting route releasing between a entrance and exit signal. The messages between the components and purpose of them are:
- nonVacant:
Sets previous signal at danger. - nonVacant:
Sets previous signal at danger. - nonVacant:
Sets previous signal at danger.
Message 1: 
| Component | Prerequisite | Action |
|---|---|---|
| Component | Prerequisite | Action |
| … | … | … |
| Massage reference: … | ||
| … | ![]() |
… |
Main route cancelling interactionsZZT+FRT pressed
The collaboration diagrams, below shows the communication between components to achieve main route cancelling.
The first diagram covers main route cancelling between an exit and entrance signal. The messages and purpose of them between the components are:
- cancelBlock:
Disable traction of the traction selector at the adjacent block - cancelMainRoute:
Clear route set status at main signals.
Disable traction at traction selectors.
Unlock turnouts.
Message 1: 
| Component | Prerequisite | Action |
|---|---|---|
| Component | Prerequisite | Action |
| … | … | … |
| Massage reference: … | ||
| … | ![]() |
… |
The second diagram covers a route between a entrance and exit signal. The messages between the components and purpose of them are:
- cancelOverlap:
Disable traction of the traction selector of the overlap after the exit signal - cancelMainRoute:
Clear route set status at main signals.
Disable traction at traction selectors.
Unlock turnouts.
Message 1: 
| Component | Prerequisite | Action |
|---|---|---|
| Component | Prerequisite | Action |
| … | … | … |
| Massage reference: … | ||
| … | ![]() |
… |
Shunting route cancelling interactionsVZT+FRT pressed
The collaboration diagrams, below shows the communication between components to achieve main route cancelling.
The first diagram covers main route cancelling between an exit and entrance signal. The messages and purpose of them between the components are: cancelBlock: Disable traction of the traction selector at the adjacent block cancelMainRoute: Clear route set status at main signals. Disable traction at traction selectors. Unlock turnouts.
Message 1: 
| Component | Prerequisite | Action |
|---|---|---|
| Component | Prerequisite | Action |
| … | … | … |
| Massage reference: … | ||
| … | ![]() |
… |
The second diagram covers a route between a entrance and exit signal. The messages between the components and purpose of them are: cancelOverlap: Disable traction of the traction selector of the overlap after the exit signal cancelMainRoute: Clear route set status at main signals. Disable traction at traction selector
Message 1: 
| Component | Prerequisite | Action |
|---|---|---|
| Component | Prerequisite | Action |
| … | … | … |
| Massage reference: … | ||
| … | ![]() |
… |