Elekdra Configuration

`<zn.zlv_over_tcp>`

Configuration of a communication link to a TCP server

Description

Normally this has to be configured once for the server that emulates the single ZLV bus. The implementation is prepared to support more than a single ZLV bus, mainly as a preparation for tunneling ZLV bus over the block line as configured with <zn.open_track_fields><zlvoverblock>#zlvoverblock. For protocol information see this website

Example

This configures for a server that runs on the same maschine as this elekdra instance, using the old server protocol. Port number is not configured, the default is used.

<zn.zlv_over_tcp>
	<protocol>plain</protocol>
	<host>localhost</host>
</zn.zlv_over_tcp>

Sub tags

Tag Description
<protocol>
Type: EProtocol
Cardinality: once
Protocol on top of TCP

Choose the protocol that is used between TCP and ZLV bus telgrams. If this is plain than <host> is mandatory.

Example

Using the new protocol with automatic configuration of the host and port.
<zn.zlv_over_tcp>
	<protocol>multi</protocol>
</zn.zlv_over_tcp>
<host>
Type: String
Cardinality: optional [0..1]
host name or IP address

DNS style host name or IP address.

Example

IPv4 addresses are four numbers with dot in between:
<host>192.168.178.21</host>
<port>
Type: Integer
Cardinality: optional [0..1]
TCP port number

This is an integer that identifies the server process on the computer identified by the <host> config. Default for old protocol is 50099, default for new protocol is 50100.

Example

TCP port number is a positive integer:
<port>50099</port>
<bus>
Type: String
Cardinality: once Name of ZLV-Bus

All ZLV bus interfaces (like this TCP connection to a ZLV-over-TCP server) need to be associated to a logical 'bus' in elekdra. In the easiest case only this 'interface' exists and the configuration of a bus name may be omitted. But if more interfaces exist (e.g. <zn.open_track_fields><zlvoverblock>#zlvoverblock), you must associate the interfaces to busses in order to define wether ZLV bus telegrams that are received on one interface shall be forwarded to another interface.

Tag	Description
`<protocol>` Type: EProtocol Cardinality: once	Protocol on top of TCP Choose the protocol that is used between TCP and ZLV bus telgrams. If this is `plain` than `<host>` is mandatory. Example Using the new protocol with automatic configuration of the host and port. `<zn.zlv_over_tcp> <protocol>multi</protocol> </zn.zlv_over_tcp>`
`<host>` Type: String Cardinality: optional [0..1]	host name or IP address DNS style host name or IP address. Example IPv4 addresses are four numbers with dot in between: `<host>192.168.178.21</host>`
`<port>` Type: Integer Cardinality: optional [0..1]	TCP port number This is an integer that identifies the server process on the computer identified by the `<host>` config. Default for old protocol is 50099, default for new protocol is 50100. Example TCP port number is a positive integer: `<port>50099</port>`
`<bus>` Type: String Cardinality: once	Name of ZLV-Bus All ZLV bus interfaces (like this TCP connection to a ZLV-over-TCP server) need to be associated to a logical 'bus' in elekdra. In the easiest case only this 'interface' exists and the configuration of a bus name may be omitted. But if more interfaces exist (e.g. `<zn.open_track_fields><zlvoverblock>`#zlvoverblock), you must associate the interfaces to busses in order to define wether ZLV bus telegrams that are received on one interface shall be forwarded to another interface.

Generated by ConfigFileDocumentationGenerator