class KNX::ConnectStateRequest

Overview

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.

Direct Known Subclasses

Defined in:

knx/connection/connect_state_request.cr

Constant Summary

AFTER_DESERIALIZE = [] of Nil

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.

BEFORE_SERIALIZE = [] of Nil

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.

ENDIAN = ["big"]

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.

KLASS_NAME = [KNX::ConnectStateRequest]

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.

PARTS = [{type: "basic", name: header, cls: KNX::Header, onlyif: nil, verify: nil, value: nil}, {type: "basic", name: channel_id, cls: UInt8, onlyif: nil, verify: nil, value: nil, endian: nil}, {type: "enum", name: status, cls: typeof(ConnectionError::NoError.value), onlyif: nil, verify: nil, value: nil, encoding: nil, enum_type: KNX::ConnectionError}, {type: "basic", name: control_endpoint, cls: KNX::HPAI, onlyif: nil, verify: nil, value: nil}] of Nil

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.

REMAINING = [] of Nil

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 Method Summary

Macro Summary

Instance Method Summary

Constructor Detail

def self.new(channel_id : Int, control : Socket::IPAddress, protocol : ProtocolType = ProtocolType::IPv4UDP) #

[View source]

Class Method Detail

def self.bit_fields #

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.


[View source]

Macro Detail

macro knx_address(name, onlyif = nil, verify = nil, value = nil) #

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.


[View source]
macro knx_cemi(name, onlyif = nil, verify = nil, value = nil) #

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.


[View source]
macro knx_connect_request(name, onlyif = nil, verify = nil, value = nil) #

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.


[View source]
macro knx_connect_response(name, onlyif = nil, verify = nil, value = nil) #

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.


[View source]
macro knx_connect_state_request(name, onlyif = nil, verify = nil, value = nil) #

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.


[View source]
macro knx_crd(name, onlyif = nil, verify = nil, value = nil) #

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.


[View source]
macro knx_cri(name, onlyif = nil, verify = nil, value = nil) #

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.


[View source]
macro knx_device_info(name, onlyif = nil, verify = nil, value = nil) #

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.


[View source]
macro knx_dib(name, onlyif = nil, verify = nil, value = nil) #

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.


[View source]
macro knx_group_address(name, onlyif = nil, verify = nil, value = nil) #

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.


[View source]
macro knx_group_address2_level(name, onlyif = nil, verify = nil, value = nil) #

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.


[View source]
macro knx_header(name, onlyif = nil, verify = nil, value = nil) #

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.


[View source]
macro knx_header_timer(name, onlyif = nil, verify = nil, value = nil) #

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.


[View source]
macro knx_header_wrapper(name, onlyif = nil, verify = nil, value = nil) #

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.


[View source]
macro knx_hpai(name, onlyif = nil, verify = nil, value = nil) #

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.


[View source]
macro knx_individual_address(name, onlyif = nil, verify = nil, value = nil) #

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.


[View source]
macro knx_information_block(name, onlyif = nil, verify = nil, value = nil) #

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.


[View source]
macro knx_search_request(name, onlyif = nil, verify = nil, value = nil) #

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.


[View source]
macro knx_search_response(name, onlyif = nil, verify = nil, value = nil) #

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.


[View source]
macro knx_service_family(name, onlyif = nil, verify = nil, value = nil) #

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.


[View source]
macro knx_supported_services(name, onlyif = nil, verify = nil, value = nil) #

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.


[View source]

Instance Method Detail

def __format__ : IO::ByteFormat #

[View source]
def channel_id : UInt8 #

def channel_id=(channel_id : UInt8) #

def control_endpoint : HPAI #

def control_endpoint=(control_endpoint : HPAI) #

def header : Header #

def header=(header : Header) #

def status : ConnectionError #

def status=(status : ConnectionError) #