User's Manual
Table Of Contents
- 1. Overview
- 2. RF Module Operation
- 3. XBee ZigBee Networks
- Introduction to ZigBee
- ZigBee Stack Layers
- Networking Concepts
- ZigBee Application Layers: In Depth
- Coordinator Operation
- Router Operation
- End Device Operation
- Channel Scanning
- 4. Data Transmission, Addressing, and Routing
- 5. Security
- 6. Network Commissioning and Diagnostics
- 7. Managing End Devices
- 8. XBee Analog and Digital IO Lines
- 9. API Operation
- API Frame Specifications
- API UART Exchanges
- Supporting the API
- API Frames
- AT Command
- AT Command - Queue Parameter Value
- ZigBee Transmit Request
- Explicit Addressing ZigBee Command Frame
- Remote AT Command Request
- Create Source Route
- AT Command Response
- Modem Status
- ZigBee Transmit Status
- ZigBee Receive Packet
- ZigBee Explicit Rx Indicator
- ZigBee IO Data Sample Rx Indicator
- XBee Sensor Read Indicator
- Node Identification Indicator
- Remote Command Response
- Over-the-Air Firmware Update Status
- Route Record Indicator
- Many-to-One Route Request Indicator
- Sending ZigBee Device Objects (ZDO) Commands with the API
- Sending ZigBee Cluster Library (ZCL) Commands with the API
- Sending Public Profile Commands with the API
- 10. XBee Command Reference Tables
- 11. Module Support
- Appendix A: Definitions
- Appendix B: Agency Certifications
- United States FCC
- OEM Labeling Requirements
- FCC Notices
- FCC-Approved Antennas (2.4 GHz)
- Europe (ETSI)
- OEM Labeling Requirements
- Restrictions
- Declarations of Conformity
- Approved Antennas
- XBee RF Module
- XBee-PRO (S2) RF Module
- XBee-PRO (S2B) RF Module
- Canada (IC)
- Transmitters for Detachable Antennas
- Detachable Antenna
- Appendix C: Migrating from ZNet 2.5 to XBee ZB
- Appendix D: Additional Information
XBee®/XBee‐PRO®ZBRFModules
©2009DigiInternational,Inc. 78
DemonstrationofPinSleep
Parent and remote devices must be configured to buffer data correctly and to utilize adequate
transmission timeouts. See the XBee Router / Coordinator Configuration section in this chapter for
details.
Cyclic Sleep
Cyclic sleep allows the module to sleep for a specified time and wake for a short time to poll its
parent for any buffered data messages before returning to sleep again. Cyclic sleep mode is
enabled by setting the SM command to 4 or 5. SM5 is a slight variation of SM4 that allows the
module to be woken prematurely by asserting the Sleep_RQ pin (pin 9). In SM5, the XBee can
wake after the sleep period expires, or if a high-to-low transition occurs on the Sleep_RQ pin.
Setting SM to 4 disables the pin wake option.
In cyclic sleep, the module sleeps for a specified time, and then wakes and sends a poll request to
its parent to discover if the parent has any pending data for the end device. If the parent has
buffered data for the end device, or if serial data is received, the XBee will remain awake for a
time. Otherwise, it will enter sleep mode immediately.
The On/Sleep line is asserted (high) when the module wakes, and is de-asserted (low) when the
module sleeps. If hardware flow control is enabled (D7 command), the CTS pin will assert (low)
when the module wakes and can receive serial data, and de-assert (high) when the module sleeps.