Tag |
Description |
<name>
Type: String
Cardinality: once
|
Name of the route for reference
This is used to reference base routes from normal routes or normal routes from macro routes.
|
<type>
Type: ERouteType
Cardinality: once
|
Type of this route definition
The folowing route types are possible: Name | Description | zs | Train Route (check for free track, use mandatory signals) | v | Shunting Route (normally no safeway used) | b | Base route (v and zs can be composed of these) |
|
<znstart>
Type: String
Cardinality: once
|
Start Track for shifting Train Number
When a mandatory signal goes red, the train number is moved from the train location referenced by this tag to the train locationreferenced by znend. This references a definition of <zn.own_field>
|
<znend>
Type: String
Cardinality: once
|
Target Track for shifting Train Number
This references a definition of <zn.own_field>
Example
Train jumps from location 3 to location 42 when signal goes STOP
<znstart>3</znstart>
<znend>42</znend>
|
<startelement>
Type: String[]
Cardinality: at least once [1..N]
|
Starting point(s) for route
This is the element that can be used as start location for selecting the route with the mouse in ELUI. If more than one startelement and/or more than one endelement tag is configured, all combinations of to one startelement and any one endelement is a valid way to select the route with mouse.
|
<endelement>
Type: String[]
Cardinality: at least once [1..N]
|
End point(s) for route
This is the element that can be used as end location for selecting the route with the mouse in ELUI.
Example
This enables selction by a → x, a → y, b → x, b → y
<startelement>a</startelement>
<startelement>b</startelement>
<endelement>x</endelement>
<endelement>y</endelement>
|
<clearrule>
Type: ERule
Cardinality: once
|
Clearing routes in sections
Not yet implemented
|
<subrouterule>
Type: ERule
Cardinality: once
|
Clearing macro route
Not yet implemented
|
<subroute>
Type: String[]
Cardinality: at least once [1..N]
|
Set of sub routes for a macro route
If this is configured, this route becomes a route macro. When this macro route is selected, these sub routes are selected. When this macro route is fixed, these sub routes are fixed and the macro route is cleared. The sub routes are independent routes that are managed and cleared individually
|
<baseroute>
Type: String[]
Cardinality: at least once [1..N]
|
Set of base routes for this route
All elements in these base routes are copied into this route on startup of Elekdra. The base routes do not live for themselfes after startup. This concept is intended to be used for sets of elements that are part of several routes. You define that set once as base route and refernce the base route in every route that would otherwise have to enumerate all the elements that are combined in the base route.
|
<routeable>
Type: Reference[]
Cardinality: at least once [1..N]
|
Elements that are controlled by this route
This references all elements that are touched by this route
|
<distantsignal>
Type: Reference[]
Cardinality: at least once [1..N]
|
Distant signal controlled by this route
This references <elekdra.distantsignal> that need an assignment that is only valid as long as this route is active
|
<distantsignalForBlock>
Type: String[]
Cardinality: at least once [1..N]
|
Distant signal to listen for Block
This references <elekdra.distantsignal> that need an assignment that is only valid as long as this route is active
|
<safeway>
Type: Reference[]
Cardinality: at least once [1..N]
|
Elements that are needed as safe way by this route
This is a feature intended only for train routes. For <elekdra.turnout> this means the turnout is set to a certain direction, but it does not have to be free, it even can be used by another route, if the requested direction is not in conflict.
|
<myFile>
Type: File
Cardinality: once
|
|
<identifyableKey>
Type: String
Cardinality: once
|
|