Routes

Content → Objects → Blocks

• General | Signals | Details | Routes | Interface | Block permissions |

Note: The route tab will be disabled in case of a modular layout.

Select the route to setup the events for that route.

Specific routes are the routes listed by name in the topmost field of the dialogue. Routes all and all-reverse are unspecific routes in each case for one direction:
The all route can be used as a default for all From-To routes (Block enter side + with block side routes).
The all-reverse route is used for the opposite direction, thus can be used as a default for all To-From routes (block enter side - with block side routes).
If sensors and events are configured for both unspecific and specific routes the entries of the relevant specific route are used.

Unspecific routes greatly decrease the amount of sensors and events to be specified in case of several routes heading to the block.

Select the sensor ID to use from this combobox.

Select the event for the sensor.

• enter
• enter2pre
• enter2route
• enter2in
• enter2shortin
• pre2in
• in
• exit
• occupied
• ident
• shortin

For detailed explanation see chapter Sensors and Blocks

Trigger at the down flank of the pulse. Better do not use this unless you can make sure the pulse will not have any disturbance. By using the up and down flank you can use one sensor generating two events.

This option must be set, if the “Event timer 2” should used.

Overrules the optional loco event timer.

This is the delay between the enter and the in events when an enter-in event is specified for the block. In case of one sensor per block this is very useful to simulate two sensors: The enter event is sent immediately, but the in event comes after this period of time in ms.

Starting with revision 1670 this is also used for pre2in events.

This is the delay between the enter and the pre2in events when an enter2pre event is specified for the block. In case of two sensors per block this is very useful to simulate three sensors: The enter event is sent immediately, but the pre2in event comes after this period of time in ms.
If the timer is set too long the in event will get delayed.

Shows the properties dialog for the selected route.

With the Test button you can activate all switch and output commands for the selected route.

Rocrail revision 1573 or higher allows for fine tuning of the stopping point.

There are two event timers. This allows for asymmetrical stopping in the block when using the enter2in event. An example where this option is useful is a station block where the platform is not in the centre of the sensor section. By using this option different event timers and thus different stopping points can be used for trains entering the block from the right and from the left.
For every route the tickbox T2 determines if timer 1 (not ticked) or timer 2 (ticked) is used. The tickbox is only evaluated when the event is an enter2in, enter2pre or an in event. The in event, regardless when it comes from a real sensor or when it is generated by the enter2in sensor, is delayed by the selected event timer. The value of the event timers is specified in milliseconds.
In the loco properties Loc details fine tuning for the selected event timer due to differences in characteristics of different locos is possible.

Note: Contrary to previous revisions, the event timer is not only effective for the enter2in event, but also works for a real in sensor.
When using schedules, if an in delay is specified, this takes preference over the block event timer. Also, when an event timer is specified in the loc properties, this also takes preference over the block event timer, but not over the in delay in a schedule.