<elekdra.blockautotcpinterface>

Block interface via TCP/IP with automatic configuration.

Description

This adds a communication interface for a block over TCP/IP. This can be useful between two PC based stations that are connected to a LAN e.g. for ZNF800 anyway. Elekdra first uses the configured remote server to set up a TCP server. Than Elekdra anounces over UDP broadcast that it awaits a connection on the respecitvie port and gives the station ID and track number as identification. The track is matched with the same method that is used by the ZNF800 sub system. A peer listening for this, would now establish the connection.

For documentation of this idea, see the website of auto IP block.

For manually configured TCP block see <elekdra.blocktcpinterface>

Example

This defines a server configuration on port 4711 for a track named with ZN field name '150' and Block 'Bl42'

<elekdra.blockautotcpinterface>
	<block>Bl42</block>
	<ownport>4711</ownport>
	<znTrackField>150</znTrackField>
</elekdra.blockautotcpinterface>

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 a <elekdra.fieldblock> or <elekdra.axle_block>
<ownport> Type: int Cardinality: once	Server port This is the TCP port number that Elekdra listens for incomming connections in server mode until a connectionis established either by a connection from a foreign hostor by initinating one ourselfes after receiving a UDP broadcast.
<znTrackField> Type: String Cardinality: once	ZN Field Of Track This is the name of the train number field of the track that runs to the foreign station and that is governed by the block. There must be a <zn.foreign_open_track_fields> configured for this track.