Management of a Websocket connection to the Miniserver and updating Thing status accordingly.Tagging of channels and items (opens new window) with tags that can be recognized by Alexa (opens new window) openHAB skill (opens new window), so voice can be used to command Loxone controls.Creation of channels for Loxone controls that are exposed in the Loxone UI (opens new window).Discovery (opens new window) of Miniservers available on the local network.The following features are currently supported: Miniserver controls, that are visible in the Loxone UI (opens new window), are exposed as openHAB channels. Miniserver is represented as a Thing (opens new window). If a single 16-bit register is read (bit 13 is cleared), then a 16-bit from pkt is read and only the byte order (bit 15) need to be applied.This binding integrates Loxone Miniserver (opens new window) with openHAB (opens new window). If the register order (bit 14) is set, then the upper/lower 16-bit are swapped. read holding registers (3), read input register (4) checks if combine two registers (bit 13) is set.read coils (1), read discrete inputs (2) simply return pkt.pkt is the received Modbus package as specified in the Modbus documentation. The value is send as a 32-bit value, it is extracted from the Modbus package in this way. The non-error reply contains the requested 32-bit value TX queue overrun (not sure if this one can happen) from a different Modbus device or just garbage with a correct CRC If an error occurs, an error command is reported back: CommandĬonfirmation from a write function (Write Single Coil, Write Single Register, Write Multiple Coils, Write Multiple Registers) with the new value
Loxone modbus code#
The reply is parsed (based on the function code and the bits in the polling cycle flags) and send back to the Miniserver. `address` `function code` `MSB register number` `LSB register number` CRC16-Modbus The send request is created from the entry table as follows:įor read coils (1) and read discrete inputs (2): With the configuration uploaded and the extension not muted, the Modbus extension will send all polling requests based on the timing, but only one per 2ms. A custom Modbus extension may not enforce it. The Modbus extension enforces a minimal 5s polling interval. The 32-bit value is a bit complex: Bit(s)Ġ:100ms, 1:1000ms factor for the polling cycle to have the delay in ms Timing timeout, default: 1000ms for a responseĭescription of a single 8-byte entry: Offsetġ…255: Address of the Modbus device (0 would be broadcast) Timing pause, default: 10ms between packages Parity (0=no parity, not in the Modbus specification, but very common) OffsetĠxFEEDFEED = magic to detect that the package is validĠ:automatic timing (based on the baudrate), !=0:manual timing flag (timing pause and timing timeout are used)īaudrate (2400,4800,9600 or 19200 are typical) The configuration is 0x810 bytes large and always version 1. This is done by uploading the configuration via a fragmented package of type 0x06 (config). The Modbus extension calls the Modbus read function automatically and sends the values back to the Miniserver. Loxone uses LSB for 16-bit, but Modbus MSB.
The commands are converted into the following Modbus functions.
The parameters are as such: B0=1, B1/B2 the 16-bit register number. The extension listens to 0x5D.0圆2, which are all used to control actuators (= setting registers on the Modbus). Because of that, I have simply listed them all, which is much easier to read than trying to understand the Loxone documentation.
The Modbus Extension only supports a limited number of write functions. However it does encode and decode the Modbus protocol. This extension is from the hardware standpoint identical to the RS485 extension, because Modbus is just an RS485 bus anyway.
0 kommentar(er)
