Digi International Inc. / Mbed 2 deprecated XBeeZB_power_mngmnt_pin_sleep

ZigBee Power Management using Pin Sleep example for mbed XBeeLib By Digi

Dependencies:   XBeeLib mbed

Description

This example characterizes a device that, after taking samples from some sensors and sending the information collected through the radio, does nothing for a long period of time that could range from several minutes to several hours.
In that long period of inactivity it is not expected to have communication with the coordinator, so the device will not be able to receive packets and can to save as much power as possible; so the radio is set into low power mode.

The example does the following cycle endlessly:

• Some sensor is read. For demonstration, a counter is incremented.
• A message containing the collected data is sent to the coordinator.
• After the data has been sent, the radio will go to sleep:
  
• First, the radio is requested to go to sleep. When radio finally sleeps, then the application waits for the time configured in the SLEEP_SECONDS macro. By default it is set to 40 seconds but it can be changed as desired.
• After that time, the application will awake the radio through the On/Sleep pin and another cycle starts.

Setup

Application

Define RADIO_SLEEP_REQ and RADIO_ON_SLEEP in config.h file according to the mbed micro-controller GPIOs that will be used to control the XBee module power.

Hardware

It is necessary to wire following connections from the mbed micro-controller to the XBee radio according to the configuration done in the application:

• From the mbed micro-controller RADIO_SLEEP_REQ to the XBee module SLEEP_RQ pin (pin 9 on THT modules, pin 10 on SMT modules) will allow the mbed micro-controller to request the radio to sleep or awake.
• From the mbed micro-controller RADIO_ON_SLEEP to XBee module ON/SLEEP# pin (pin 13 on THT modules, pin 26 on SMT modules) will allow the mbed micro-controller to know if the radio is awake or slept.

Firmware

In S2B modules, router firmware will not work for this example, because routers don't support sleep modes.
Make sure the XBee module has end-device firmware.
To flash a new firmware onto an XBee module, you need to use the XCTU software.

On S2C XBee modules, the SLEEP_RQ and ON/SLEEP# pins can be used not only for power management but also as a GPIO. To run this example they have to be configured as power management functionality (mode 1):

• SLEEP_RQ pin: "D8"=1
• ON/SLEEP# pin: "D9"=1

Network

Make sure the coordinator has the 'Cyclic Sleep Period' (SP) and at 'Number of Cyclic Sleep Periods' (SN) options values configured so that (3*SP*10*SN) is greater than the XBee module sleep time (in this example 40 s = 40000 ms).

If SP parameter in coordinator is pre-established for example to 0x1F4=500 based on other devices requirements, SN should be configured in coordinator for this example as:

• MaxPinSleepTime= 3 * SP * 10 * SN
• SN= MaxPinSleepTime / 3 / SP / 10
• SN = 40000 / 3 / 500 / 10 = 2.666 -> Rounding high -> 3 = 0x3

Remember to change this parameter in the coordinator if SLEEP_SECONDS is changed in the example.

Demo run

While the demo is running, you will see the frames sent by the XBee module through the serial console terminal.

Verify that the coordinator is receiving the frames by accessing the "Console" tab of the X-CTU.
If the frames are successfully sent, they will be displayed there. One message like the ones below should be seen every 40 seconds.

     Sensor sample: 0, next sample in 40 seconds
     Sensor sample: 1, next sample in 40 seconds