solicoupon.blogg.se - Loxone tree extension

Loxone tree extension serial number#
Loxone tree extension Offline#

The CAN Diagnostics and CAN Errors commands contain a field in val16 to allow defining one of the 3 CAN busses of the Tree Bus Extension:

The Tree Base Extensions listens to 3 additional commands, besides the device detection commands: As a special case after a NAT offer confirm command, after sending the Start command to the Miniserver, it also sends the current CAN Error status for both branches. after a reboot or on power-on, it sends a NAT offer request at a random interval between 1-1.5s.

Loxone tree extension Offline#

If the Tree extension is in the offline state, e.g. The Tree Base Extension sends the CAN Error reply whenever a the error count on one of the Tree branches changes, but only once per second. The Tree Extension has to be at the end of the Tree branches as well. extensions, but the protocol is otherwise identical, instead of 0x10 in the top 5 bits of the object identifier for NAT messages on the Loxone Link bus, the value is 0x11 for Tree branches. There is also a minimal change in the address of Tree devices vs. The Loxone Tree Extension uses two additional independent CAN 2.0B busses (driven by two MCP2515 CAN controllers), but are clocked at 50kHz (which allows up to 1km of cable length).

Multiple Tree Base Extensions on the Loxone Link are also possible. devices which are outside of the building and could allow listening and/or controlling devices on the bus. This allows isolating two branches, which can be used for increased security, because devices on one Tree branch never see commands from devices on other Tree branches. The Tree Base Extension is a gateway from Loxone Link to two Tree branches.

0x81…0xFE - NAT with bit 7 set defines the extension to be parked (it has not been added in the Loxone Config file).

0x7F - reserved, because 0x7F parked would be 0xFF, which is used for broadcast.

The NAT are a single bytes, which can have the following values: There are two NATs: one for Loxone Link extensions and one for devices behind a NAT extension, like the Tree Base Extension.

Loxone tree extension serial number#

The NATs are a replacement for the serial number of the extension/device to allow the Miniserver to send messages to a specific extension or device. This is different to the legacy protocol, where fragmented packages have their own unique commands and actually makes it a bit simpler. The DI Extension doesn't have devices behind it, in this case the device ID is 0x00.įragmented packages share the same commands with simple packages. 0xFF is again used to broadcast to all devices behind an extension. This allows to run many devices behind the an extension. This frees up the first byte in the 8 byte data package.

l package type: 0 = regular package, 1 = fragmented package.

dd is a direction/type of the command: 00 = sent from a extension/device, 10 = from a extension/device, when sending a shortcut messages back to the Miniserver, 11 = sent from the Miniserver.

Bit 7 is set for parked extensions, which have been detected by the Miniserver, but are not configured in Loxone Config. A NAT of 0xFF is a broadcast to all extensions.

nnnnnnnn is the NAT ( 0x01…0x7E), which is the id of the extension on the Loxone Link bus.