<elekdra.blocktcpinterface>
Block interface via TCP/IP with manual configuration.
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 tries to initiate a connection in client mode to the configured remote server. If this runs into an error, the configured server port number is used to listen for an incomming connection.For manually configured TCP block see
<elekdra.blockautotcpinterface>
This defines a server configuration on port 4711 and a client configuration for remote host with IP address 1.2.3.4 on port 4712 for use by block 'Bl42'
<elekdra.blocktcpinterface> <block>Bl42</block> <ownport>4711</ownport> <foreignip>1.2.3.4</foreignip> <foreignport>4712</foreignport> </elekdra.blocktcpinterface>
Tag Description <block>
Type: String
Cardinality: onceReference 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: onceServer port
This is the TCP port number that Elekdra listens for incomming connections in server mode, if the client configuration of foreignip/foreignport did not render a connection possible.<foreignip>
Type: String
Cardinality: onceClient remote IP
This is the IP address or DNS name of the remote host that runs the interlocking for the neigiboring station.Example
If DNS names can be used, the name could be given symbolically, even though naked IP addresses are considered the more robust approach if static addresses are used on FREMO meetings.<foreignip>stw</foreignip>
<foreignport>
Type: int
Cardinality: onceClient remote port
TCP port number of the server that shall be listening on the host at foreignip.