User's Guide

- 23 of 42 –
neo.
cortec
.
The node(s) which is targeted for the wake up, shall be within radio range of the node
who sends the Wake-Up Burst.
3.3.9.2 Local Wake-Up
The application layer at a Node can command the node to transmit a Wake-Up Burst.
This will only wake nodes which are within radio range. See integration manual for
details on how to send Wake-Up Bursts.
3.3.9.3 Global Wake-Up
A node can be configured to automatically transmit Wake-Up Burst depending on a set
of configurable parameters.
Automatic Wake-Up Bursts are always of type 1 according to section 3.3.9.1, where the
Network ID is same as the Node who sends the Wake-Up Burst.
Automatic Wake-Up Bursts can be send always when the node is in active mode.
Alternatively it can send the bursts when the ACM (see section 3.3.10) node is present in
the network.
3.3.10 Alternate Configuration Mode
In some applications it is desirable to operate the network in two different modes
depending on an external situation. This could for instance be in a setup or debug
situation, where a technician need rapid information about the network health and
integrity.
The mode of the network (alternate vs. normal) is controlled from a single node –
Alternative Configuration Master (ACM) Node. This node will as part of the normal
operation, broadcast the mode setting into the entire network. This can be done at no
additional overhead in terms of network throughput or current consumption. The ACM
node will typically be a gateway node, but does not need to be.
The application layer at the ACM node, can control the mode through the UART API
interface (see Integration Manual for details).
Each node in the network needs to be configured with the Node ID of the Alternative
Configuration Master Node (see section 0 for details on configuration)
In the alternate configuration, it is possible to define the following parameters:
1. Scheduled Data Rate
2. Generic application settings
3. Hibernation behaviour