HDL interface configuration

Within this configuration file, the HDL Buspro interfaces connected to BMS server can be configured.

File location

<WorkspaceDirectory>\DataFiles\xio.Hdl.Interfaces.dat

Interface1;192.168.10.101;6000;254;254;192.168.10.250;6000;200;F;50;10;2
Interface2;192.168.10.101;6000;254;254;192.168.10.251;6000;200;F;50;10;2
' This is a comment


Each interface has its own row with the parameters separated by a semicolon. (CSV-format)

The interface configuration can be edited in the NETx Core Server Studio at Modules > HDL > Interface Definitions


Col#ParameterDescriptionScopeUnitDefault value
1NameName of the interface. Must be unique.stringNone
2Sender subnet idHDL Buspro subnet id of the NETx Server.0 - 254None
3Sender device idHDL Buspro device id of the NETx Server.0 - 254None
4Target IP addressIP address of the HDL Buspro interface.IP-AddressNone
5Target portUDP port of the HDL Buspro interface.Port numberNone6000
6Send intervalTime delay between sending two messages.integerms200
7Log messagesIf set to true, all received and sent messages are logged in <WorkspaceDirectory>\LogFiles\nxaHDL-<InterfaceName>_<Datecode>.logbooleanNoneFalse
8Ping after

Start pinging the interface after not receiving packets for this time period.

integers50
9Ping interval

Time between sending pings to the interface.

integers10
10Ping retries

Connection to the interface is considered lost after this amount of failed pings.

integerNone2

Send interval

The NETx Server has to request the current values of all devices on startup. This means a lot of requests will be sent at the same time. In order to avoid overloading of the bus, these messages are queued.

The send interval parameter sets the time delay between sending each of the queued messages. Write requests have a higher priority than get status requests.

The queue sizes can be monitored with the corresponding server items NETx\XIO\HDL\<InterfaceName>\Request queue size and NETx\XIO\HDL\<InterfaceName>\Write queue size.

Log messages

If enabled, all received and sent messages are logged. This can be useful for troubleshooting unintended behaviors. However, logging is disabled by default to save disk space.

Ping

The NETx Server is monitoring the connection to each interface.

  • If the NETx Server has not received any packets from the interface for the timespan set in "Ping after", it sends a ping packet to the interface.
  • When the NETx Server receives a response, the timer is reset.
  • If the NETx Server does not receive a response, it keeps sending ping packets after every "Ping interval" seconds.
  • If the NETx Server has sent the number of ping packets as set in "Ping retries" without a response, the connection to the interface is considered lost and the interface's GATEWAY item is set to False.
  • When the connection is reestablished (the NETx Server receives a ping response or any other packet), the GATEWAY item is set to True and the values of all devices/channels are requested from the bus.