![]() ![]() Disable these temporarily, and try assigning the address again. If this does not work, the connection may have been blocked by a virus scanner or firewall. The Miniserver restarts and can then be reached at the new assigned IP address. (You can get the DNS server addresses either from the ISP, or you can search the Internet for alternatives). Add the subnet mask, gateway (usually the IP address of the router/modem) and the addresses of the DNS servers. Enter a valid IP address for the Miniserver that is outside of the DHCP range of the router.You can find it on the label on the back of the device. blank document), then enter the MAC address (serial number) of the Miniserver. The MAC address (serial number) of the Miniserver is copied from the current document.Then click the Configure Device button in the menu bar and select Miniserver as the device.First click on the Miniserver in the Periphery tree. ![]() Open the configuration software Loxone Config and follow the steps below: Use this function to establish the connection afterwards. While Loxone doesn't do it, it is easily possible to have a device on the Loxone Link bus, which acts as several extensions at once.Assigning an IP address via Configure Device is also possible when the Miniserver is in a different IP range and it is not possible to establish a connection. This is important for sensors or keypads to report their updated status. This is used to configure extensions and heavily by the Air Base Extension to send messages to Air devices.Įxtensions can send data to the bus at any time to inform the server. There are also fragmented packages possible, which allow transmitting more than 7 bytes to/from a device. The only exception of this rule is the firmware update case for legacy extension. ![]() The 8 byte package contains a single byte, which is either a command (in the legacy protocol) or a device NAT (in the NAT protocol) plus a 7 byte payload. The Air devices are using a special container format for their packages. The Air Base extension and other gateway extensions are still using the legacy protocol to forward packages to Miniserver. All Tree devices are always using the newer NAT protocol. An extension either implements the legacy protocol or the new one, never both. Besides the Miniserver having to able to deal with both protocols, they are completely different. The newly introduced NAT protocol does not interfere with existing extensions, but required a server update for support. With more extensions arriving and also extensions with devices behind them, Loxone ran out of space and flexibility with that scheme. This is now called the "legacy protocol". The Miniserver can either multicast to all extensions of a specific type (used in the update case) or to one extension via direct commands.įor the first years Loxone stored the serial number and extensions type in the CAN object identifier. Extensions never talk to each other (with the obvious exception of device bridges, like the Tree Extension and the Air Base Extension – but even in this case: the bridge is almost 100% transparent between the device and the server). The Miniserver sends data to the extensions, the extensions send data to the bus. The Loxone Link bus is a strict server-client bus. Any CAN bus monitor hardware will work just fine with the Loxone Link bus and the Tree Bus as well. The data packages are always 8 bytes long. Packages are always using the extended frame format, therefore the object identifier is 29-bit ( 0x00000000…0x1FFFFFFF). The Tree Extension has to be at the end of the Tree busses as well. extensions, but the protocol is otherwise identical. There is also a minimal change in the address of Tree devices vs. The Loxone Tree Extension uses two additional CAN 2.0B busses (driven by two MCP2515 CAN controllers), but are clocked at 50kHz (which allows up to 1km of cable length) via a prescaler of 10. It doesn't use automatic retransmission and uses a sample point of 68.75% (1-10-5 time quantum) with a prescaler of 4 (at 8MHz clock rate), I do not expect this to be critical. The Miniserver has a build-in 120Ω resistor, so the Miniserver has to be at one end of the bus. Loxone Link (in the past also called the "LoxBUS") is using a standard CAN 2.0B bus, clocked at 125kHz (which allows up to 500m of cable length).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |