<zn.open_track_fields>

Train number field definition for open track

Description

This adds train number handling on a single track between stations. Dual track lines need two of these configurations.
You may not define a <zn.own_field> for the same track.
This configuration must be paired with a definition of <zn.foreign_open_track_fields>, that configures the names of the same track/offer/notify field but with the field names as known by the neighboring station. This is needed in order to leave the field names of one station the same for different layouts. In order to be interoperative on the border between stations, the fields that are overlapping become a name from both sides and both stations know both names. Every station sends information with 'its' name and can recognize the name of the neighbor to refer to the same field.

Example

This adds a train number field with name '42' for a single track line - that implies we need an offer field ('142') but no notify field. Block on this line is referenced as 'BL42' can be used for automatic configuration and propagation of ZLV-Bus telegrams.

<zn.open_track_fields>
	<name>42</name>
	<offer>142</offer>
	<block>BL42</block>
	<plugandplay>auto</plugandplay>
	<zlvoverblock>forward</zlvoverblock>
</zn.open_track_fields>

Sub tags

Tag	Description
<name> Type: String Cardinality: once	Name of train number field for the open track The name of the track in ZLV bus compatible notation. This may be equal to the name of the <elekdra.track>, but does not have to be. Example ZLV bus uses numerical field names <name>4711</name>
<offer> Type: String Cardinality: optional [0..1]	Offer field Name of offer field. This is used for offering/accepting/rejecting train movements on a single track or on one track of a double track line when a train shall run against the normal direction of travel but secured by the block (Germany: Gleiswechselbetrieb).
<notify> Type: String Cardinality: optional [0..1]	Notify field Name of notify field. This is used for anouncement of a train before it entered the track between the stations. This is used on double track lines for trains that use the regular direction of travel. Notify fields are only for incoming information, so it has to be defined for that track where trains normally arrive at the given station.
<block> Type: String Cardinality: optional [0..1]	Block for this track Reference to the block for this open track. This can be used to exchange configuration automagically, see configuration plugandplay#plugandplay below. Also tunneling of ZLV bus information over this block line can be configured with zlvoverblock#zlvoverblock. This configuration may only be omitted, both usages of the block line are configured to EPnpConfiguration.off#off and no zlvoverblock#zlvoverblock.
<plugandplay> Type: EPnpConfiguration Cardinality: optional [0..1]	Do not use this!!! Not yet implemented Enable/disable Plug&pray configuration This automates the configuration of <zn.foreign_open_track_fields>, if the neighbor station supports it. In case this is not configured, the default is EPnpConfiguration.off#off for now.
<zlvoverblock> Type: String Cardinality: optional [0..1]	Do not use this!!! Not yet implemented Train numbers over block line Tunneling of ZLV-Bus telegrams over the block line referenced with block#block. If this is not configure, the feature is switched off for this block interface. If it is configured, it names the ZLV bus that this interface connects to. Other interfaces (e.g. <zn.zlv_over_tcp>) may reference the same bus in order to enable forwarding of telegrams between this and the other interface.