Weidmuller WI-I/O-9-U2: Wireless Mesh I/O & Gateway User Manual V1.2.2 - Manual (Page 44)

43
General purpose digital registers 10501 to 10595 will indicate a communication fail for
the corresponding remote radio address.
E.g. Address 10505 will indicate a communication fail for remote address # 5
Address 10590 will indicate a communications failure for remote address # 90.
Note: Radio must have a valid mapping for the remote address and the mapping
must have the ‘ACK’ enabled.
3.3.7 Testing and Commissioning
We recommend that that the system is fully tested on the bench before installation. It is
much easier to find configuration problems on the bench when the modules are next to
each other as opposed to being miles apart.
When the system is configured and you are happy that it all works, backup the
configurations of all the modules.
After installation, record the radio signal strength and background noise level for each
radio link. See section 5.4
“Neighbour RSSI” for details on this. If there are future
communications problems, you can compare the present measurements to the as-
commissioned values. This is an effective way of finding problems with antennas,
cables, and changes in the radio path (for example, the erection of new buildings).
3.4 WIBMesh
The WEIDMULLER WIBMesh protocol is based on the “Ad hoc On-demand Distance
Vector” (AODV) routing algorithm which is a routing protocol designed for ad hoc
networks.
AODV is capable of unicast (single addressed message) routing and is an “on-demand”
protocol, meaning that it builds and maintains these routes only as long as they are
needed by the source devices. In other words the network is silent until a connection is
needed. The Protocol creates a table, which shows the connection routes to other
device in the system and uses sequence numbers to ensure the routes are kept as
current as possible.
When a module in a network needs to make a connection to another module it
broadcasts a request for connection. Other modules forward this message, and record
the module address that they heard it from, creating a table of temporary routes back to
the starting module. If a module receives a request and it already has an existing route
to the request destination, it will send a message backwards through the temporary
route to the requesting module.
Each request for a route has a sequence number. Modules use this sequence number
so that they do not repeat route requests that they have already passed on. Another
such feature is that the route requests have a "time to live" number that limits how many
times they can be retransmitted. Another such feature is that if a route request fails,
another route request may not be sent until twice as much time has passed as the
timeout of the previous route request.