User's Guide

- 21 of 42 –
neo.
cortec
.
The WES server node will then send a message to the application layer (through the
application API) with the UID such that the application can decide if the node who wants
to be setup is allowed or not. If the application decides to allow the node to join, it shall
provide the Node ID, which the joining node is supposed to have. This means that the
application layer needs to make sure the nodes inside the network has unique Node
ID’s.
Once the application sends the Node ID to the WES server, the WES server will send the
full set of configuration parameters to the joining node. Hereafter the unconfigured
node will write the parameters to the non-volatile memory, reboot and become part of
the network.
3.3.7.1 Remote WES Client activation
The Wireless Encrypted Setup client mode is enabled when the node has 0xFFFF as its
Node ID. This can be programmed directly through the system API, or by activating the
nWES pin on the module.
Remote WES activation allow WES mode to be enabled remotely, by sending a package
to the node through the mesh network. When the target node receives the package, it
will correspond to activating the nWES pin.
This is particularly useful in situations where it is required that nodes can be removed
from a network, and reassigned to a new network.
The remote WES activation is done through the Application API. See Integration Manual
for further details.
3.3.8 Power Consumption
As mentioned previously, the NeoMesh wireless network operates as a time
synchronized network, where all nodes are in sleep mode most of the time, and wakes
up periodically to communicate with the neighbouring nodes. Depending on the
settings, this allow for very low average current consumption for all the nodes in the
network.
The NEOCORTEC Config Application can be used to calculate the expected average
current consumption based on the actual configuration for the node.
3.3.9 Hibernation
In some applications of the NeoMesh network technology, it is desirable to configure a
node such that it can hibernate until a user wakes the node up. In hibernation mode, it is
understood that the node will consume current at a level lower than any active mode
allowing extended battery life in situations where the active network operation is not
required.