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.  

No it can not. Typical usage of the product is that the product is end of line.

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.

It can be many reasons why an W-Modbus installation is not working correctly. We have listed the most common once in this FAQ.

1. The Gateway and node is placed next to wrong device.
   In an solar installation you should connect the gateway to the Modbus Master and the node to the slave. The smart energy meter is typically the slave and should therefor be connected to the node while the master is often the inverter or, if your system have one, the smartlogger.
   
   Gateway next to inverter and node next to smart meter
   
2. You have used the other polarity. The third led (bottom on wall mount and most right on DIN rail) will be flashing red every 5 seconds. See our user manual how you should connect.
   
3. The smart meter is not configured with the right baud rate. The third led (bottom on wall mount and most right on DIN rail) will be flashing red every 5 seconds.
   
   Set the Dip switch into local mode (dip switch 5) and adjust dip switch 1-4 according to smart meter. See our user manual how you change settings
   
4. The smart meter is not speaking Modbus RTU. Start by updating your W-Modbus devices to 3.0.0 or above. This update allows some illegal Modbus behaviors such as adress 254. You find how to update your device on this support page. You need to consult with the smart meter manual if this still does not work but most common issue is then that it speaks other protocols such as DL/T 645 or EQ-bus or M-bus. It is often easily fixed on the smart meter. The LumenRadio node will indicate red on the third led (bottom on wall mount and most right on DIN rail) if something is wrong on the RS485 bus.
   
   If you do belive that your smart meter is speaking modbus and it is still not working with our solution, please write a support ticket. We want to solve it!
   
5. The inverter is not speaking Modbus RTU. It can be hard to know if the inverter you have speak a dialect of modbus or not even modbus. Our experience is that some manufacturers uses another dialect in order to lock in customers to their product set-up (mainly use a modified version of a Smart meter that they have modified to speak their dialect. In some cases the issue can be resolved by adding the inverter manufacturers smart logger. This is a separate device used typically in larger solar installations for daisy chaining inverters as well as adding BMS functionality.
   
   We understand that this might be confusing. If you do believe that your Inverter is speaking modbus and it is still not working with our solution, please write a support ticket. We want to solve it!
   

Yes, as long as you install one network at a time each network gets their own network key.

This is possible on the W-Modbus Wall mount PRO unit.

It is possible to have 100 Servers (slaves) connected to one Client (master).

The W-Modbus unit do not need any Modbus ID. It will proxy it's Modbus server (slave) ID. The third LED (bottom on Wall mount and right on DIN rail) will flash green every five seconds if the W-Modbus node fins an modbus id on the bus with a correct baud rate. It will flash red otherwise.

The W-Modbus units transfer Modbus RTU signals and not Modbus TCP.

Yes, all communication in the W-Modbus Network is encrypted with AES128.