JMRI: Adding/Editing LRoutes
Author: Bob Jacobsen
Keywords: JMRI help LRoute Add Edit

# Adding/Editing LRoutes

There are four tabs for adding and editing LRoutes:

### Tab 1: Basic LRoute

The first thing you must do when creating an LRoute is to name it. In the box labeled "System Name" enter a unique name for your LRoute. The prefix "RTX" will be added to the System Name. You can optionally enter a more descriptive name in the "User Name" box.

Logix Route Type
  The radio buttons below the tab descriptions set the triggering mode for the "Veto" control variables (see below for an explanation of Veto). To emulate the behavior of Routes (as opposed to LRoutes) select the Old option. (Standard Routes do not not trigger when the Veto condition is removed.) If you want the LRoute to trigger when the Veto condition is removed, select the New option.

The buttons at the bottom of the LRoute Table:

Add Route
  Push this button to add a new Logix Route.
Cancel
  Push this button to cancel editing.

### Tab 2: Actions (output)

This tab contains a pick list of all the Sensors, Turnouts, Lights and Signal Heads that have been created. Click the checkbox in the Include column to select the device you want to include in the LRoute. Then choose the action you want the device to take when the LRoute is triggered from the drop down menu in the Set Action column.

The radio buttons allow you to limit the display of devices to only those you have already selected.

### Tab 3: Triggers/Controls (input)

This tab contains a pick list of all the Sensors, Turnouts, Lights and Signal Heads that have been created. Click the checkbox in the Include column to select the device you want to use to control in the LRoute. Then choose the state you want the device to use for triggering the LRoute from the drop down menu in the Trigger State column.

Devices selected with "non-veto" states are grouped as an "OR" clause. Triggers selected with a "veto" state are grouped as an "AND" clause. That is, when any "non-veto" state becomes True, the LRoute is able to trigger. However, if any of the "veto" states is True, the LRoute will not trigger.

On Tab 1, the Logix Route Type New will put the above logic into a single Logix Conditional. If the Old option is selected, each trigger with a "non-veto" state is put into a separate Conditional. The behavior for this option is: the LRoute will trigger whenever one of these device states becomes True - even when the logical expression as a whole is already True. Another difference when the Old option is specified, is that the "veto" variables are not enabled for triggering. This means the actions are not triggered when the vetoes are removed. Use the New option if you want actions to be triggered when the vetoes are removed. In summary, the Old option emulates a standard Route and the New option has the behavior of a standard Logix Conditional. Variations on these behaviors can be tuned with further editing in the Logix Table.

Note that control variables selected with "On Change" states need a separate Logix Conditional in order for the LRoute actions to trigger on every change of state of these variables.

The radio buttons allow you to limit the display of devices to only those you have selected.

### Tab 4: Alignment/Locks/Etc.

This tab contains a pick list of the Sensors that have been created. Click the checkbox in the Include column to select a Sensor you want to use for indicating completion of the LRoute actions. Then choose the type of action you want the Sensor to monitor from the drop down menu in the Alignment column. You may choose to have the Sensor indicate a particular type (Sensor, Turnout, Light, Signal Head or "All")

The radio buttons allow you to limit the display of devices to only those you have selected.

A sound file may be entered to play when the LRoute is triggered. Likewise a script file may be run when the LRoute is triggered.

Back to the LRoute Table help page.