Activate bluetooth on the LumenRadio W-BACnet or W-Modbus device by pressing the button three times. The device will confirm by flashing the mid LED blue twice. Bluetooth will be active for 1 min.  

You press the button three times. The Device will confirm by flashing the mid led blue twice. The Bluetooth beacon will be active for one minute.

The first time you see this is when you updated to 3.0.0 or above. This is the new FOTA behavior indicating that the node is comparing it's firmware with the gateway. Once the node have received the latest gateway firmware it will indicate green every 5 second on the mid LED. You will also see the nodes switch from green to yellow if you are doing a new firmware upgrade from 3.0.0 to a higher version on the gateway. This indicates that FOTA is in progress. Once the node have received the firmware it will indicate green again. The network will reboot when all nodes are green or after 2h what ever occurs first.

New features

Firmware of an entire network can now be updated via FOTA from the gateway node.

Changes

Reserved modbus addresses 248 through 255 are now handled as any other address to accommodate

certain applications in the solar industry.

Fixes

Fixed an issue affecting Modbus PRO units which may miss responses from devices with consecutive

addresses.

Common questions

What is FOTA?

FOTA, Firmware over the Air, is a way to distribute firmware updates over the wireless network by

performing a single update on the gateway. The system is completely automated, and significantly

simplifies firmware updates in established networks.

What do I need to do?

For the initial update, each mesh and gateway node will have to be manually updated to version 3.0

in the exact same way as before. Any future update past 3.0 can then simply be deployed on the

gateway node, the update will then automatically be distributed and applied to all mesh nodes in the

network.

What happens if I don't or can't update every single node?

Nodes that are not updated will still function as before without any breaking changes, however these

nodes will not receive new firmware until they are manually updated to at least 3.0. Nodes that

have been updated to 3.0 will still receive new firmware from the gateway, provided their connection

to the gateway is not via a node that has not been updated.

How long does an update take?

The time required depends on a lot of factors. As a general rule, allow for ca 5 minutes per node in

the network. Our largest test network consists of 100 nodes and takes ca 5 hours to fully upgrade.

Is Modbus or BACnet unavailable while firmware is updating?

No. The system is designed to be as unintrusive as possible and bus traffic will continue to operate

while firmware is being distributed over the network. You will be seeing a temporary outage in

service when the nodes are restarting with the new firmware. The restart is synchronized over the

entire network in order to minimize disruptions.

For normal operations you will be seeing a single outage for a few minutes while the network

rebuilds itself. For large (>50 devices)you may see two or more (based on the size of an update) outages.

Can I still update my network manually?

If you wish to speed up firmware updates of smaller networks by updating manually, you can still do

so by following the regular process from before 3.0. Make sure you update your gateway node first,

then update the mesh nodes.

The Module have a SPI Slave interface for configuration, please see the development documentation for further information.

Yes, UART is used for all communication between thes Module and the BACnet device. It is also support for using a RS485 driver.