<elekdra.block_post>

Remote controlled block post

Description

This configuration element enables access to one remote controlled block post on a track between our station and the neighboring station. This feature is based on these messages.
If there are two remote controlled block posts on the same track behind each other, two instances of this configuration block need to be defined. The block post that is defined further up in the config file gets the lower index and is nearer to the own station.
This configuration block implicitly defines a track, which shall not be defined via a <elekdra.track> and it implicitly defines two <elekdra.signal>, one for each direction of travel, independently of the actual existence of the signal, it is controllable in Elekdra. The train number field is also implicitly defined and shall not be defined via a <zn.own_field> entry, but you must define the zn_field tag for this to work.

Example

This example defines two block posts on the track that is controlled by the block named hugo. The implicitly configured elements can be accessed from a user interface like ELUI with the following names.

Element name	Element description	Post index
hugo:post0:SigIn	Signal, incomming direction	0, near to our station
hugo:post0:SigOut	Signal, outgoing direction
hugo:post0:Track	Track between the posts
hugo:post1:SigIn	Signal, incomming direction	1, near to neighboring station
hugo:post1:SigOut	Signal, outgoing direction
hugo:post1:Track	Track between post 1 and neighboring station

The following grafic shows the line with signals and tracks. The train number fields are written in red. The overlapping track between the stations that has two names – one for each station – is seen with the two red field numbers.

Neighbor Station					Our Station
Entry signal		hugo:post1:SigOut		hugo:post0:SigOut
O⊣	field 44	O⊣	field 43	O⊣	field 42
━━━━━━	[hugo:post1:Track]	━━━━━━━━━	[hugo:post0:Track]	━━━━━━━━━	[TrackToHugo]	━━━━━━
	UST 2, field 222	⊢O		⊢O		⊢O
		hugo:post1:SigIn		hugo:post0:SigIn		ESig

The section near to our station has the ZN field 43. Field 44 is further away or nearer to the neighboring station.

<elekdra.block_post>
	<block>hugo</block>
	<zn_field>43</zn_field>
</elekdra.block_post>
<elekdra.block_post>
	<block>hugo</block>
	<zn_field>44</zn_field>
</elekdra.block_post>

<zn.open_track_fields>
	<name>42</name>
	<offer>142</offer>
	<block>hugo</block>
</zn.open_track_fields>
<zn.foreign_open_track_fields>
	<our_name>42</our_name>
	<name>222</name>
	<offer>333</offer>
	<station_id>2</station_id>
	<station_short>JWD</station_short>
</zn.foreign_open_track_fields>

<elekdra.fieldblock>
	<name>hugo</name>
	<contact>SensorH</contact>
	<blockroute>false</blockroute>
	<sendperm>true</sendperm>
	<reqperm>false</reqperm>
	<signalin>ESig</signalin>
	<route_target>RT</route_target>
</elekdra.fieldblock>

Sub tags

Tag	Description
<block> Type: String Cardinality: once	Reference to block This references the block by its name. This is a reference to the name of e.g. a <elekdra.fieldblock> or <elekdra.axle_block>. The block posts are remote controlled over the block interface (<elekdra.blockrs232interface> or <elekdra.blocktcpinterface>) that is associated to this block name.
<zn_field> Type: String Cardinality: optional [0..1]	ZN field The train number field on the track between the block post and its neighbor is defined here. This implicitly defines a train number field similarly to what you would do with <zn.own_field> inside a station. Not defining this effectively disables train number propagation.