Following configurations can be used to fine tune the behavior of MiWi(TM) mesh networking protocol.
Macros
|
|
Name |
Description |
 |
When broadcasting to a sleeping device is enabled, it is hard for a parent node to track which end device has received the broadcast message. However, if no tracking is provided, the end device may receive the same broadcast multiple times. MiWi PRO solves this problem by tracking the broadcast message on sleeping device side. INDIRECT_MESSAGE_TIMEOUT_CYCLE defines the total number of messages receives before the broadcast record times out. It is hard for a sleeping node to track timing, so tracking the number of message received is a simpler way. | |
|
|
MAX_ROUTING_FAILURE is the number of failures of routing between coordinators before such route is disabled in the decision of message route. Proper definition of this parameter helps to update the available routes dynamically. This definition is only valid for a coordinator. | |
|
|
For a sleeping device, when establishing an indirect connection (socket), it may not be desirable to poll the data at the normal interval, which can be longer than OPEN_SOCKET_TIMEOUT, the solution is to poll the data at a fast rate, lower than OPEN_SOCKET_TIMEOUT. OPEN_SOCKET_POLL_INTERVAL is the polling interval in symbols for a sleeping device to acquire data from its parent in the process of establishing indirect (socket) connection. This parameter is only valid for sleeping device. | |
|
|
OPEN_SOCKET_TIMEOUT is the timeout period in symbols for a node to abandon attempt to establish a socket connection, or in MiApp term, an indrect connection |
Topics
|
Name |
Description |
|
| |
|
|