KNX::ConnectStateRequest
Inherits BinData < Reference < Object
Connection state request / response can be considered as a heartbeat mechanism. It enables KNXnet/IP client to ping the server in regular intervals (every 60 seconds) After a while (120 seconds) server will conclude that the client is not available and it will terminate the tunnelling connection if the client fails to send the Connection State request.
Constants
Connection state request / response can be considered as a heartbeat mechanism. It enables KNXnet/IP client to ping the server in regular intervals (every 60 seconds) After a while (120 seconds) server will conclude that the client is not available and it will terminate the tunnelling connection if the client fails to send the Connection State request.
Connection state request / response can be considered as a heartbeat mechanism. It enables KNXnet/IP client to ping the server in regular intervals (every 60 seconds) After a while (120 seconds) server will conclude that the client is not available and it will terminate the tunnelling connection if the client fails to send the Connection State request.
Connection state request / response can be considered as a heartbeat mechanism. It enables KNXnet/IP client to ping the server in regular intervals (every 60 seconds) After a while (120 seconds) server will conclude that the client is not available and it will terminate the tunnelling connection if the client fails to send the Connection State request.
Connection state request / response can be considered as a heartbeat mechanism. It enables KNXnet/IP client to ping the server in regular intervals (every 60 seconds) After a while (120 seconds) server will conclude that the client is not available and it will terminate the tunnelling connection if the client fails to send the Connection State request.
Connection state request / response can be considered as a heartbeat mechanism. It enables KNXnet/IP client to ping the server in regular intervals (every 60 seconds) After a while (120 seconds) server will conclude that the client is not available and it will terminate the tunnelling connection if the client fails to send the Connection State request.
Connection state request / response can be considered as a heartbeat mechanism. It enables KNXnet/IP client to ping the server in regular intervals (every 60 seconds) After a while (120 seconds) server will conclude that the client is not available and it will terminate the tunnelling connection if the client fails to send the Connection State request.
Constructors
Class methods
Connection state request / response can be considered as a heartbeat mechanism. It enables KNXnet/IP client to ping the server in regular intervals (every 60 seconds) After a while (120 seconds) server will conclude that the client is not available and it will terminate the tunnelling connection if the client fails to send the Connection State request.
Instance methods
A group or bit_field captures the endianness at its declaration point, so
declaring endian after one would silently leave it system-endian. Fail loudly.