zigbee技术XBEE模块使用说明书

合集下载

XBEE模块中文说明书

The XBee and XBee-PRO OEM RF Modules were engineered to operate within the ZigBee protocol and support the unique needs of low-cost, low-power wireless sensor net-works. The modules require minimal power and provide reliable delivery of data between remote devices. Both modules operate within the ISM 2.4 GHz frequency band and are pin-for-pin compatible with each other.XBee和XBee - PRO OEM RF模块的设计，以ZigBee协议内运作，支持低成本的独特需求，低功耗无线传感器网络工程。

模块只需要最小的功率，就能提供远程设备之间的数据传输的可靠性。

这两个模块内运作的ISM 2.4 GHz频段，且引脚对引脚相互兼容。

1.1Key Features/主要特点XBee XBee-PROHigh Performance, Low Cost 高性能、低成本indoor/Urban: up to 100‟(30 m)outdoor line-of-sight: up to 300‟(100 m)transmit Power: 1 mW (0 dBm)receiver Sensitivity: -92 dBm室内/城市：距离100'（30米）户外线的视线：300'（100米）发射功率：1毫瓦（0 dBm时）接收灵敏度：-92 dBm的Indoor/Urban: up to 300‟(100 m)outdoor line-of-sight: up to 1 mile (1500m)transmit Power: 100 mW (20 dBm) EIRPreceiver Sensitivity: -100 dBmRF Data Rate: 250,000 bps室内/城市：300'（100米）户外线的视线：高达1英里（1500米）发射功率：100毫瓦（20 dBm的）的EIRP接收灵敏度：-100 dBm的射频数据传输速率：250,000个基点Lower power 低功率TX Current: 45 mA (@3.3 V)RX Current: 50 mA (@3.3 V)Power-down Current: < 10 μATX电流：45毫安（@ 3.3伏）RX电流：50毫安（@ 3.3伏）掉电电流：<10微安TX Current: 215 mA (@3.3 V)RX Current: 55 mA (@3.3 V)Power-down Current: < 10 μATX电流：215毫安（@ 3.3伏）RX电流：55毫安（@ 3.3伏）掉电电流：<10微安Advanced Networking & Security/先进的网络和安全Retries and Acknowledgements DSSS (Direct Sequence Spread Spectrum)Each direct sequence channel has over 65,000 unique network addresses available Point-to-point, point-to-multipoint and peer-to-peer topologies supported Self-routing, self-healing and fault-tolerant mesh networking重试和确认。

XBee模块说明书

XBIB-U-SS
Reference Guide
Programming Header Header used to program XBee Programmable modules
Self Power Module Advanced users only – will void warranty. R31 must be depopulated to power module using V+ and GND from J2 and J5. Sense lines can be connected to S+ and S- for sensing power supplies. CAUTION: Voltage not regulated. Applying incorrect voltage can cause fire and serious injury. See Note 1.
Current Testing Depopulating R31 allows a current probe to be inserted across P6 terminals. The current though P6/R31 powers the module only. Other supporting circuitry is powered by a different trace.
Test Points
Indicator LEDs DS5: ON/ SLEEP DS2: DIO12 DS3: DIO11 DS4: DIO4
SPI
SPI Power Connect to power board from 3.3V
Reset button
User Buttons Connected to DIO lines for user implementation

Xbee模块API指令技术文档(第1版by宋涛)

Xbee模块API指令技术文档——by 宋涛2008-11-19参数和固件烧录：xbee模块使用API指令必须先将Module烧录入API参数和固件（另一种为AT，在AT指令时烧录）。

方法为在X-CTU软件的Modem Configuration选项卡内的Modem项选中XB24-B，Fuction Set 内选中Znet 2.5 Coordinator API或者Znet 2.5 Router/End Device API选项（根据该module要扮演的角色决定，在烧录AT情况下，选择类似的选项。

），Version选项不用选择，会自动调整。

然后在Modem Parameters and Firmware下点击write进行烧录。

强烈建议在write 前先勾选中always update firmware选项。

注意：1.烧录完成前，如是模块状态是AT指令状态下，不能先勾选上PC settings 里面的Enable API。

如果模块状态是API指令状态下，必须先勾选上PC settings 里面的Enable API。

否则，烧录会失败。

2.烧录完成后，如果PC settings里面的Enable API项没有选中，必须勾选上，如果要使用逃脱字，则需要勾选上ATAP=2项。

3.当前烧录版本是针对当前实验室版本，如果版本变化，烧录过程会有部分调整。

4.Modem Configuration里面Read为读取当前module参数状况，主要用于调试中网络不通时，检查modules之间参数设置是否正确时使用。

Restore为重置module的状态为最近一次烧录入firmware后的初始状态。

API Operations:注意：1.xbee目前的各个版本之间的API Operation是有区别的，该文档以Znet2.5版本为准。

2.该文档对API Operation的讲述以在实验过程中常遇到的指令为主，若本文档中未包含的API frame，请参见《XBee™ ZNet 2.5/XBee-PRO™ ZNet 2.5 OEM RF Modules》。

XBee ZigBee 802.15.4 Modules 数据手册

The XBee family of ZigBee/802.15.4 RF modules is the premiere choice for OEMs looking for excellent wireless performance in a cost-effective, small form factor solution. Each XBee module comes in either a regular or long-range “–PRO” version*. All XBee modules are pin-for-pin compatible with the exception of a few varying I/O features, which provides a standard footprint for OEMs with multiple applications.XBee Series 1 is based on ZigBee/802.15.4 silicon from Freescale ®. Its 802.15.4 firmware feature set makes it ideal for point-to-point, peer-to-peer, and point-to-multipoint (star) topologies. The XBee Series 1 gives the user maximum control over network nodes and minimum latency. XBee Series 2 is based on ZigBee/802.15.4 silicon from Ember™. It features ZigBee firmware for creating ad-hoc mesh networks. The XBee Series 2 performs automatic route discoveries to create a self-healing network of full-function routers and low-power end devices. XBee Series 1and Series 2 modules do not communicate with one another.Known for ease of use, the XBee modules are ready to operate out of the box and offer simple AT commands or an API for advanced, user-settable configurations. XBee modules arerecognized worldwide for reliable wireless data communication in the license-free 2.4 GHz ISM band. Visit our website for a complete listing of countries that have approved the XBee as a certified, license-free RF module with no need for further testing.XBee modules are a part of Digi’s full line of Drop-in Networking products. ConnectPort X gateways and XBee device adapters, modules and extenders provide end-to-end wirelessconnectivity to commercial-grade electronic devices in locations where wired infrastructure does not exist or satisfy customer needs. To learn more about Drop-in Networking, visit /products/wirelessdropinnetworking.Part of Digi’s Drop-in Networking product family,XBee OEM RF modules provide reliable, wireless data communication over ZigBee/802.15.4 networks.Available in Series 1 or Series 2 models for point-to-multipoint or mesh topologies, they enable OEMs with excellent wireless performance in a cost-effective,small form factor solution.Features/Benefits•ZigBee/802.15.4 compatible RF modules • 2.4 GHz ISM band for use worldwide •Fully interoperable with other Digi Drop-in Networkingproducts, including gateways, device adapters and extenders •Available in Series 1 or Series 2 models for point-to-multipoint or mesh topologies •Pin-swappable regular and long-range –PRO versions •Low cost•Common footprint for a variety of Digi RF modules •Low-power sleep modes •Multiple antenna options •Industrial temperature (-40º C to 85º C)Central Facilities ManagementEthernetConnectPort ™ XGatewayGa a te wa w y Wireless Telco NetworkWarehouseInternet/Frame Relay/VPNMeterMeterMeterXBee ™ModuleZigBee/802.15.4Wireless Mesh Network2.4 GHz OEM RF ModulesProduct DatasheetOverviewXBee ™ZigBee®/802.15.4 ModulesSeries 1•Serial data rate:1200 - 250000 bps •(6) 10-bit ADC inputs,(8) Digital I/O Series 2•Serial data rate: 1200 – 1 Mbps •(4) 10-bit ADC inputs,(10) Digital I/O91001412A1/1007© 2006-2007 Digi International Inc.All rights reserved. Digi, Digi International, the Digi logo, the When Reliability Matters logo, ConnectPort, XBee, XBee-PRO and XStream are either trademarks or registered trademarks of Digi International Inc. in the United States and other countries worldwide. All other trademarks are the property of their respective holders.Digi Internationa l11001 Bren Road E.Minnetonka, MN 55343U.S.A.PH:877-912-3444952-912-3444FX:952-912-4952email:*************Digi Internationa l France31 rue des Poissonniers 92200 Neuilly sur Seine PH: +33-1-55-61-98-98 FX: +33-1-55-61-98-99www.digi.frDigi Internationa l KKNES Building South 8F 22-14 Sakuragaoka-cho,Shibuya-kuTokyo 150-0031, Japan PH: +81-3-5428-0261FX: +81-3-5428-0262www.digi-intl.co.jpDigi Internationa l (HK) LimitedSuite 1703-05, 17/F .,K Wah Centre 191 Java RoadNorth Point, Hong Kong PH:+852-2833-1008FX: +DIGI SERVICE AND SUPPORT - You can purchase with confidence knowing that Digi is hereto support you with expert technical support and a one-year warranty. /supportDigi International , the leader in device networking for business, develops reliable products and technologies to connect and securely manage local or remote electronic devices over the network or via the web. With over 20 million ports shipped worldwide since 1985, Digi offers the highest levels of performance, flexibility and quality.4214A-XBEEPRO•Europe (CE): ETSI / ETSI(max. tx power output: 10 mW)•Australia •JapanSeries 2 (XBee)•U.S. (FCC Part 15.247): OUR-XBEE2 •Canada (IC): 4214A-XBEE2•Europe (CE): ETSI •JapanPlease visit for part numbers.•Encryption: AES 128-bit •Reliable packet delivery: Retries/Acknowledgments •PAN ID, 64-bit IEEE MAC address, 16 channels(12 channels – XBee-PRO Series 1)N E T W O R K I N G A N D S E C U R I T Y1.087”(2.761)0.960”(2.438)•Transmit power output: 1 mW (0 dBm) / 60 mW (+18 dBm) -Note:In Europe XBeePRO modules must be set to 10 mW (10 dBm). In Japan XBP modules are calibrated to 10 mW (10 dBm).•Receiver sensitivity (1% PER):-92 dBm / -100 dBm Series 2 (XBee)•Indoor/Urban range: 133 ft (40 m)•Outdoor/RF line-of-sight range: 400 ft (120 m)•Transmit power output:1.25 mW (+1 dBm) (2 mW (+3 dBm) boost mode)•Receiver sensitivity (1% PER):-97 dBm (-98 dBm boost mode)XBee-PRO0.960”(2.438)1.297”(3.294)。

XBee ZNet 2.5 ZigBee Mesh 开发套包说明书

Getting Started GuideXBee ZNet 2.5 ZigBee® Mesh Development KitIntroductionRange Test Setup Node Discovery Create long-range wireless links in minutes!IntroductionThis Getting Started Guide provides step-by-step instruction on how to set up a networkand test the modules' ability to transport data over varying ranges and conditions. This guide illustrates how to discover all nodes in your network and set parameters to run a Range Test.Range Test SetupRequired Components(1) XBee ZNet 2.5 COORDINA TOR (XB24-BWIT-002)(At least 1) XBee ZNet 2.5 ROUTER/END DEVICE (XB[P]24-BxIT-004).(1) USB Interface Board* (XBIB-U-DEV) (for interfacing between an RF module & host PC)(1) RS-232 Interface Board (XBIB-R-DEV) (for looping data back to the base from a remote)(1) PC (Windows 2000 or XP) with an available USB (or RS-232*) port. Required installations:X-CTU Software & USB drivers.Accessories (1 USB Cable, 1 Serial Loopback Adapter [RED] & 1 power supply)* XBee ZNet 2.5 Development Kits (XB24-BPDK) contain three RS-232 interface boards. An RS-232 board (w/RS-232 cableand power supply) can be used in lieu of the USB board.Software Installations Install X-CTU SoftwareSelect the “Range Test” tab.Click the 'Start' button to begin the range test.COORDINATOR to nd the maximum range of the wireless link. The percentage of good/bad packets will be displayed in the "Percent" box. [Figure 5] 5. 4. 6. Move the ROUTER/END DEVICE (with red Serial Loopback Adapter) away from theyou are communicating with out of range of the COORDINATOR. Power anotherROUTER/END DEVICE between the COORDINATOR and the out of range ROUTER/END DEVICE to reestablish communications. Messages are now being routed through the new 7. Change the Loopback Adapter to any other ROUTER/END DEVICE and repeat steps 1-6 if desired.8. Mesh networking capabilities can be observed by moving the ROUTER/END DEVICE thatROUTER/END DEVICE.Contact Digi International(O ce hours are 8am – 5pm U.S. Mountain standard time)Range TestX-CTU is a stand-alone tool for con guring XBee modules. It is used to run the range test and is included in the Hardware and Software Setup CD. X-CTU can also be found on the website at /support/productdetl.jsp?pid=3352&osvid=57&tp=4&s=316.To install X-CTU:1. Insert the Hardware and Software Setup CD in the PC’s CD/DVD drive.2. On the Home page, click Modules, Sensors, & Adapters Documentation Software.3. Click XBee Module.4. Click Install X-CTU.5. When installation completes, start X-CTU by selecting: Start>Programs>Digi>X-CTU. The X-CTU interface is opened.address has been entered with the ATDH and ATDL parameters from the COORDINATOR. 3.The Serial Loopback Adapter should be placed on the ROUTER/END DEVICE whose 64-bit[Figure 4]* The 64-bit address is physically printed on each XBee module (see white label attached to the shield on the bottom).Run Range Test (continued)Toll-free phone U.S.A. & Canada: (866) 765-9885 Worldwide: (801) 765-9885Live chat: Online support: /support/eservice/login.jspFigure 5PN (1P): 90000862-88 B4a. (Optional) Check the “RSSI” checkbox to enable the Received Signal Strength Indicator.Software Installations (continued)Node DiscoveryDiscovery of All Nodes in a Network1. Mount XBee modules to theUSB & RS-232 development boards.The module mounted to the USBboard should be theCOORDINAThe modules mounted to theRS-232 boards are all ROUTER/END DEVICES (XB[P]24-BxIT-004).2.Connect the U.FL (snap-on) and RPSMA(threaded) antennas to the appropriateXBee modules.3.C onnect power supplies and poweron all other radios.4.Under the “PC Settings” tab select theCOM port to which yourCOORDINATOR is attached. Also selectBaud: 9600Flow Control: HardwareData Bits: 8Parity: NONEStop Bits: 1.NOTE: If the COORDINATOR is powered on, as the other radios are turned on,their red LEDs will blink at a rate of twice per second, indicating they have joined the network.Range TestUse the “Terminal” and “Range Test”tabs of the X-CTU Software to:• Set parameters on the COORDINATOR module to communicate with a speci c ROUTER/END DEVICE• Determine the range capabilities of the XBee ModulesThe USB interface board is a “plug-and-play” device that should be detected by the PC automatically. To interface between the USB interface board and a PC, two drivers must be installed: a USB driver and a virtualCOM port driver that makes the USB port look and perform like a physical COM port. After the modem is detected, a wizard for installing the USB driver is launched. The USB driver is includedon the Hardware and Software Setup CD.Use the following steps to install the two USB drivers:1. Connect the XBee to a PC using a USB cable. The Found New Hardware Wizarddialog box is displayed.2. Verify that the Hardware and Software Setup CD is inserted into the drive.3. Select Install from a speci c list or location (Advanced), and then click Next.4. Select Search for the best driver in these locations and search removable media(CD-ROM). Click Next. A Hardware Installation Windows Logo Testing alert box is displayed.5. Click Continue Anyway.6. Click Finish.7. You will be prompted to install another driver, the virtual COM port driver. Repeatsteps 3 through 6 to install this driver.TOR (XB24-BWIT-002).6. From X-CTU, while in command mode (command mode will automatically be exited with 10 secondsof inactivity), enter the ATND command followed by a carriage return. All powered ROUTERS/END DEVICES that have joined the network will respond with their device information.The second eld returned from the ATND parameter is the 64-bit address of each particularROUTER/END DEVICE. [Figure 2]1.Follow the directions in the previous example to perform a Node Discovery.2. Use the ATDH and ATDL commands to set the destination address high and the destinationaddress low of the COORDINATOR to match the 64-bit address of the particular ROUTER/END DEVICE with which you wish to communicate. Use ATDH for the upper 32 bits and ATDLfor the lower 32 bits of the 64-bit address. [Figure 3] The “Modem Con guration” tab can beused to do this as well.R un Range TestFigure 164-bit address(i.e., 8 bytes, 16 characters)Figure 2Upper and Lower 32 bitsof 64-bit addressFigure 3Install USB Drivers5. On the Terminal tab, enter command mode. This mode eliminates over-the-air communications for the XBee module, and allows internal communication with the XBee module parameters.If command mode is entered, an OK message is displayed. There is a one-second “guardtime” before and after entering command mode, and a ten-second timeout.To enter command mode, enter +++ with no carriage return. [Figure 1]。

zigbee模块的配置说明5-20

3
图 2-3 路由配置 API 方式 1
图 2-4 路由配置 API 方式 2 路由配置 AT 方式： 1、工作模式(Function Set)：ZIGBEE ROUTER AT； 4
2、 PAN ID：中国石油定义协议器的值，如指定油气田公司、工程代码，规定见 A11 标准附录 C，与同一井场协调器 PAN ID 保持一致；
3、 SC-Scan Channels:设定为 7FFF，由于现场使用不同家的模块，Xbee Pro 模块的为 FFFF，Xbee Pro S2 模块为 7FFF，Xbee Pro S2B 模块为 3FFF，为了统一设定为 3FFF，且与同一井场协调器 SC 参数保持一致；
4、其他参数默认； 5、配置完后读取 IO-Operationg 16-bit PAN ID，确保与协调器的一致，如 90B9；
北京安控：
API 方式
1
Zigbee
井口RTU
路由器（Router） AT 方式
西安安特：
API 方式
API 方式
贵州凯山：ຫໍສະໝຸດ API 方式API 方式
中油瑞飞：
API 方式
API 方式
长森：
API 方式
API 方式
说明：
北京安控的使用方式与其它各家不一样，北京安控 RTU 与 XBEE 模块之间采用 AT 指令集，使
图 2-5 路由配置 AT 方式：
5
现场 zigbee 模块配置说明
陕西星际电子科技发展有限公司 2014.3.9
1 测试设备
1.1井口 RTU
1.2 无线通信模块
长庆数字规范中规定无线通信模块是美国 DIGI 公司的 Xbee 模块与深圳华奥通的 Zigbee 模块。

Digi【ZigBee】XBee2详细技术资料

355 South 520 West, Suite 180Lindon, UT 84042Phone: (801) 765-9885Fax: (801) 765-9895rf-xperts@ (live chat support)XBee™ Series 2 OEM RF ModulesXBee Series 2 Series 2 OEM RF Modules ZigBee ™ Networks RF Module Operation RF Module Configuration AppendicesProduct Manual v1.x.2x - ZigBee ProtocolFor OEM RF Module Part Numbers:XB24-BxIT-00xZigBee OEM RF Modules by MaxStream, Inc. - a Digi International brand Firmware Versions:1.0xx - Coordinator , Transparent Operation 1.1xx - Coordinator , API Operation1.2xx - Router , End Device, Transparent Operation 1.3xx - Router , End Device, API Operation90000866_B 2007.07.019© 2007 Digi International, Inc. All rights reservedNo part of the contents of this manual may be transmitted or reproduced in any form or by any means without the written permission of Digi International, Inc. ZigBee® is a registered trademark of the ZigBee Alliance.XBee™ Series 2 is a trademark of Digi International, Inc.Technical Support: Phone: (801) 765‐9885Live Chat: E‐mail: rf‐xperts@Contents1. XBee Series 2 OEM RF Modules41.1. Key Features 41.1.1. Worldwide Acceptance 41.2. Specifications 51.3. Mechanical Drawings 61.4. Mounting Considerations 61.5. Pin Signals 71.6. Electrical Characteristics 82. RF Module Operation92.1. Serial Communications 92.1.1. UART Data Flow 92.1.2. Serial Buffers 92.1.3. Serial Flow Control 102.1.4. Transparent Operation 122.1.5. API Operation 122.2. Modes of Operation 132.2.1. Idle Mode 132.2.2. Transmit Mode 132.2.3. Receive Mode 142.2.4. Command Mode 142.2.5. Sleep Mode 153. ZigBee Networks173.1. ZigBee Network Formation 173.1.1. Starting a ZigBee Coordinator 173.1.2. Joining a Router 173.1.3. Joining an End Device 183.2. ZigBee Network Communications 193.2.1. ZigBee Device Addressing 193.2.2. ZigBee Application-layer Addressing 193.2.3. Data Transmission and Routing 204. XBee Series 2 Networks254.1. XBee Series 2 Network Formation 254.1.1. Starting an XBee Series 2 Coordinator 254.1.2. Joining an XBee Series 2 Router to an ex-isting PAN 254.1.3. Joining an XBee Series 2 End Device to anExisting PAN 254.1.4. Network Reset 264.2. XBee Series 2 Addressing 274.2.1. Device Addressing 274.2.2. Application-layer Addressing 294.2.3. XBee Series 2 Binding Table 294.2.4. XBee Series 2 Endpoint Table 314.3. Sleep Mode Operation 324.3.1. End Device Operation 324.3.2. Parent Operation 324.4. I/O Line Configuration 325. Advanced Features355.1. Device Discovery 355.2. Remote Configuration 355.3. Loopback Testing 355.3.1. AT Firmware 355.3.2. API Firmware 355.4. Join Indicators 355.5. Manual Device Identification 355.6. Battery Life Monitoring 366. XBee Series 2 Command Reference Tables377. API Operation437.0.1. API Frame Specifications 437.0.2. API Frames 448. Examples568.0.1. Starting an XBee Network 568.0.2. AT Command Programming Examples 578.0.3. API Programming Examples 579. Manufacturing Support599.1. Interoperability with other EM250 Devic-es 599.2. Customizing XBee Default Parameters599.3. XBee Series 2 Custom Bootloader 599.4. Programming XBee Series 2 Modules 599.5. XBee EM250 Pin Mappings 59 Definitions 61Agency Certifications 63Migrating from the 802.15.4 Protocol 67 Development Guide 68Additional Information 781. XBee Series 2 OEM RF ModulesThe XBee Series 2 OEM RF Modules were engineered to operate within the ZigBee protocol and support the unique needs of low-cost, low-power wireless sensor networks. The modules require minimal power and provide reliable delivery of data between remote devices.The modules operate within the ISM 2.4 GHz frequency band.1.1. Key Features1.1.1. Worldwide AcceptanceFCC Approval (USA) Refer to Appendix A [p50] for FCC Requirements.Systems that contain XBee Series 2 RF Modules inherit MaxStream Certifications.ISM (Industrial, Scientific & Medical) 2.4 GHz frequency band Manufactured underISO 9001:2000 registered standardsXBee Series 2 RF Modules are optimized for use in US , Canada , Australia, Israel and Europe (contact MaxStream for complete list of agency approvals).High Performance, Low Cost•Indoor/Urban: up to 133’ (40 m)•Outdoor line-of-sight: up to 400’ (120 m)•Transmit Power: 2 mW (+3 dBm)•Receiver Sensitivity: -96 dBm RF Data Rate: 250,000 bps Advanced Networking & Security Retries and AcknowledgementsDSSS (Direct Sequence Spread Spectrum)Each direct sequence channel has over65,000 unique network addresses available Point-to-point, point-to-multipoint and peer-to-peer topologies supported Self-routing, self-healing and fault-tolerant mesh networkingLow Power XBee Series 2•TX Current: 40 mA (@3.3 V)•RX Current: 40 mA (@3.3 V)•Power-down Current: < 1 µA @ 25o C Easy-to-UseNo configuration necessary for out-of box RF communicationsAT and API Command Modes for configuring module parameters Small form factor Extensive command setFree X-CTU Software(Testing and configuration software)Free & Unlimited Technical Support1.2. Specifications*The ranges specified are typical when using the integrated Whip (1.5 dBi) and Dipole (2.1 dBi) antennas. The Chipantenna option provides advantages in its form factor; however, it typically yields shorter range than the Whip and Dipole antenna options when transmitting outdoors. For more information, refer to the “XBee Series 2 Antenna” application note located on MaxStream’s web site/support/knowledgebase/article.php?kb=153Table 1‐01.Specifications of the XBee Series 2 OEM RF ModuleSpecification XBee Series 2Performance Indoor/Urban Range up to 133 ft. (40 m)*Outdoor RF line-of-sight Range up to 400 ft. (120 m)*Transmit Power Output (software selectable)2mW (+3dBm), boost mode enabled 1.25mW (+1dBm), boost mode disabled RF Data Rate250,000 bpsSerial Interface Data Rate (software selectable)1200 - 230400 bps(non-standard baud rates also supported)Receiver Sensitivity -96 dBm, boost mode enabled -95 dBm, boost mode disabledPower Requirements Supply Voltage2.1 -3.6 VOperating Current (Transmit, max output power)40mA (@ 3.3 V, boost mode enabled)35mA (@ 3.3 V, boost mode disabled)Operating Current (Receive))40mA (@ 3.3 V, boost mode enabled)38mA (@ 3.3 V, boost mode disabled) Idle Current (Receiver off) 15mA Power-down Current < 1 uA @ 25o C GeneralOperating Frequency Band ISM 2.4 GHzDimensions0.960” x 1.087” (2.438cm x 2.761cm)Operating Temperature -40 to 85º C (industrial)Antenna Options Integrated Whip, Chip, RPSMA, or U.FL Connector*Networking & Security Supported Network Topologies Point-to-point, Point-to-multipoint, Peer-to-peer & Mesh Number of Channels (software selectable)16 Direct Sequence ChannelsAddressing Options PAN ID and Addresses, Cluster IDs and Endpoints (optional)Agency ApprovalsUnited States (FCC Part 15.247)OUR-XBEE2Industry Canada (IC)4214A-XBEE2Europe (CE)ETSI1.3. Mechanical DrawingsFigure 1‐01.Mechanical drawings of the XBee Series 2 OEM RF Modules (antenna options not shown).1.4. Mounting ConsiderationsThe XBee Series 2 RF Module (through-hole) was designed to mount into a receptacle (socket) and therefore does not require any soldering when mounting it to a board. The XBee Series 2Development Kits contain RS-232 and USB interface boards which use two 20-pin receptacles to receive modules.Figure 1‐02.XBee Series 2 Module Mounting to an RS ‐232 Interface Board .The receptacles used on MaxStream development boards are manufactured by CenturyInterconnect. Several other manufacturers provide comparable mounting solutions; however , MaxStream currently uses the following receptacles:•Through-hole single-row receptacles -Samtec P/N: MMS-110-01-L-SV (or equivalent)•Surface-mount double-row receptacles -Century Interconnect P/N: CPRMSL20-D-0-1 (or equivalent)•Surface-mount single-row receptacles - Samtec P/N: SMM-110-02-SM-SMaxStream also recommends printing an outline of the module on the board to indicate the orientation the module should be mounted.XBee1.5. Pin SignalsFigure 1‐03.XBee Series 2 RF Module Pin Number (top sides shown ‐ shields on bottom)Design Notes:•Minimum connections: VCC, GND, DOUT & DIN•Minimum connections to support serial firmware upgrades: VCC, GND, DIN, DOUT , RTS & DTR •Signal Direction is specified with respect to the module •Module includes a 30k Ohm resistor attached to RESET•Several of the input pull-ups can be configured using the PR command •Unused pins should be left disconnectedTable 1‐02.Pin Assignments for the XBee Series 2 Modules(Low ‐asserted signals are distinguished with a horizontal line above signal name.)Pin #Name DirectionDescription 1VCC -Power supply 2DOUT Output UART Data Out 3DIN / CONFIG Input UART Data In 4DIO12Either Digital I/O 125RESET Input Module Reset (reset pulse must be at least 200 ns)6PWM0 / RSSI / DIO10Either PWM Output 0 / RX Signal Strength Indicator / Digital IO7PWM / DIO11Either Digital I/O 118[reserved]-Do not connect9DTR / SLEEP_RQ/ DIO8Either Pin Sleep Control Line or Digital IO 810GND -Ground 11DIO4Either Digital I/O 412CTS / DIO7Either Clear-to-Send Flow Control or Digital I/O 713ON / SLEEP / DIO9Output Module Status Indicator or Digital I/O 914[reserved]-Do not connect15Associate / DIO5Either Associated Indicator, Digital I/O 516RTS / DIO6 Either Request-to-Send Flow Control, Digital I/O 617AD3 / DIO3Either Analog Input 3 or Digital I/O 318AD2 / DIO2Either Analog Input 2 or Digital I/O 219AD1 / DIO1Either Analog Input 1 or Digital I/O 120AD0 / DIO0 / ID ButtonEitherAnalog Input 0, Digital I/O 0, or Node Identification1.6. Electrical CharacteristicsTable 1‐03.DC Characteristics of the XBee Series 2 (VCC = 2.8 ‐ 3.4 VDC)Symbol Parameter Condition Min Typical Max Units V IL Input Low Voltage All Digital Inputs-- 0.2 * VCC V V IH Input High Voltage All Digital Inputs0.8 * VCC- 0.18* VCC V V OL Output Low Voltage I OL = 2 mA, VCC >= 2.7 V--0.18*VCC V V OH Output High Voltage I OH = -2 mA, VCC >= 2.7 V0.82*VCC--V II IN Input Leakage Current V IN = VCC or GND, all inputs, per pin--0.5uA uA2. RF Module Operation2.1. Serial CommunicationsThe XBee Series 2 OEM RF Modules interface to a host device through a logic-level asynchronous serial port. Through its serial port, the module can communicate with any logic and voltage compatible UART; or through a level translator to any serial device (For example: Through a MaxStream proprietary RS-232 or USB interface board).2.1.1. UART Data FlowDevices that have a UART interface can connect directly to the pins of the RF module as shown in the figure below.Figure 2‐01.System Data Flow Diagram in a UART ‐interfaced environment(Low ‐asserted signals distinguished with horizontalline over signal name.)Serial DataData enters the module UART through the DIN (pin 3) as an asynchronous serial signal. The signal should idle high when no data is being transmitted.Each data byte consists of a start bit (low), 8 data bits (least significant bit first) and a stop bit (high). The following figure illustrates the serial bit pattern of data passing through the module.Figure 2‐02.UART data packet 0x1F (decimal number ʺ31ʺ) as transmitted through the RF moduleExample Data Format is 8‐N ‐1 (bits ‐ parity ‐ # of stop bits)The module UART performs tasks, such as timing and parity checking, that are needed for data communications. Serial communications depend on the two UARTs to be configured with compatible settings (baud rate, parity, start bits, stop bits, data bits).2.1.2. Serial BuffersThe XBee Series 2 modules maintain small buffers to collect received serial and RF data, which is illustrated in the figure below. The serial receive buffer collects incoming serial characters and holds them until they can be processed. The serial transmit buffer collects data that is received via the RF link that will be transmitted out the UART .DIN (data in)DIN (data in)DOUT (data out)DOUT (data out)XBee Series 2 OEM RF Modules ‐ ZigBee ‐ v1.x2x [2007.07.019]Chapter 2 ‐ RF Module Operation Figure 2‐03.Internal Data Flow DiagramSerial Receive BufferWhen serial data enters the RF module through the DIN Pin (pin 3), the data is stored in the serialreceive buffer until it can be processed. Under certain conditions, the module may not be able toprocess data in the serial receive buffer immediately. If large amounts of serial data are sent tothe module, CTS flow control may be required to avoid overflowing the serial receive buffer.Cases in which the serial receive buffer may become full and possibly overflow:1.If the module is receiving a continuous stream of RF data, the data in the serial receivebuffer will not be transmitted until the module is no longer receiving RF data.2.If the module is transmitting an RF data packet, the module may need to discover the des-tination address or establish a route to the destination. After transmitting the data, themodule may need to retransmit the data if an acknowledgment is not received, or if thetransmission is a broadcast. These issues could delay the processing of data in the serialreceive buffer.Serial Transmit BufferWhen RF data is received, the data is moved into the serial transmit buffer and is sent out theserial port. If the serial transmit buffer becomes full enough such that all data in a received RFpacket won’t fit in the serial transmit buffer, the entire RF data packet is dropped.Cases in which the serial transmit buffer may become full resulting in dropped RFpackets1. If the RF data rate is set higher than the interface data rate of the module, the modulecould receive data faster than it can send the data to the host.2. If the host does not allow the module to transmit data out from the serial transmit bufferbecause of being held off by hardware flow control.2.1.3. Serial Flow ControlThe RTS and CTS module pins can be used to provide RTS and/or CTS flow control. CTS flowcontrol provides an indication to the host to stop sending serial data to the module. RTS flowcontrol allows the host to signal the module to not send data in the serial transmit buffer out theuart. RTS and CTS flow control are enabled using the D6 and D7 commands.If CTS flow control is enabled (D7 command), when the serial receive buffer is 17 bytes awayfrom being full, the module de-asserts CTS (sets it high) to signal to the host device to stopsending serial data. CTS is re-asserted after the serial receive buffer has 34 bytes of space.If flow RTS control is enabled (D6 command), data in the serial transmit buffer will not be sent out the DOUT pin as long as RTS is de-asserted (set high). The host device should not de-assert RTS for long periods of time to avoid filling the serial transmit buffer. If an RF data packet is received, and the serial transmit buffer does not have enough space for all of the data bytes, the entire RF data packet will be discarded.2.1.4. Transparent OperationRF modules that contain the following firmware versions will support Transparent Mode:1.0xx (coordinator) and 1.2xx (router/end device).When operating in Transparent Mode, the modules act as a serial line replacement. All UART data received through the DIN pin is queued up for RF transmission. When RF data is received, the data is sent out the DOUT pin. The module configuration parameters are configured using the ATcommand mode interface. (See RF Module Operation --> Command Mode.)When RF data is received by a module, the data is sent out the DOUT pin.Serial-to-RF PacketizationData is buffered in the serial receive buffer until one of the following causes the data to bepacketized and transmitted:1. No serial characters are received for the amount of time determined by the RO (Packetiza-tion Timeout) parameter. If RO = 0, packetization begins when a character is received.2.Maximum number of characters that will fit (72) in an RF packet is received.3.The Command Mode Sequence (GT + CC + GT) is received. Any character buffered in theserial receive buffer before the sequence is transmitted.2.1.5. API OperationAPI (Application Programming Interface) Operation is an alternative to the default Transparent Operation. The frame-based API extends the level to which a host application can interact with the networking capabilities of the module. RF modules that contain the following firmware versions will support API operation: 1.1xx (coordinator) and 1.3xx (router/end device).When in API mode, all data entering and leaving the module is contained in frames that define operations or events within the module.Transmit Data Frames (received through the DIN pin (pin 3)) include:•RF Transmit Data Frame•Command Frame (equivalent to AT commands)Receive Data Frames (sent out the DOUT pin (pin 2)) include:•RF-received data frame•Command response•Event notifications such as reset, associate, disassociate, etc.The API provides alternative means of configuring modules and routing data at the hostapplication layer. A host application can send data frames to the module that contain address and payload information instead of using command mode to modify addresses. The module will send data frames to the application containing status packets; as well as source, and payloadinformation from received data packets.The API operation option facilitates many operations such as the examples cited below:->Transmitting data to multiple destinations without entering Command Mode->Receive success/failure status of each transmitted RF packet->Identify the source address of each received packetTo implement API operations, refer to the API Operation chapter 6.2.2. Modes of Operation2.2.1. Idle ModeWhen not receiving or transmitting data, the RF module is in Idle Mode. During Idle Mode, the RFmodule is also checking for valid RF data. The module shifts into the other modes of operationunder the following conditions:•Transmit Mode (Serial data in the serial receive buffer is ready to be packetized)•Receive Mode (Valid RF data is received through the antenna)•Sleep Mode (End Devices only)•Command Mode (Command Mode Sequence is issued)2.2.2. Transmit ModeWhen serial data is received and is ready for packetization, the RF module will exit Idle Mode andattempt to transmit the data. The destination address determines which node(s) will receive thedata.Prior to transmitting the data, the module ensures that a 16-bit network address and route to thedestination node have been established.If the 16-bit network address is not known, network address discovery will take place. If a route isnot known, route discovery will take place for the purpose of establishing a route to thedestination node. If a module with a matching network address is not discovered, the packet isdiscarded. The data will be transmitted once a route is established. If route discovery fails toestablish a route, the packet will be discarded.Figure 2‐04.Transmit Mode SequenceWhen data is transmitted from one node to another, a network-level acknowledgement istransmitted back across the established route to the source node. This acknowledgement packetindicates to the source node that the data packet was received by the destination node. If anetwork acknowledgement is not received, the source node will re-transmit the data. See DataTransmission and Routing in chapter 3 for more information.If a valid RF packet is received, the data is transferred to the serial transmit buffer2.2.4. Command ModeTo modify or read RF Module parameters, the module must first enter into Command Mode - astate in which incoming serial characters are interpreted as commands. Refer to the API Modesection for an alternate means of configuring modules.AT Command ModeTo Enter AT Command Mode:Default AT Command Mode Sequence (for transition to Command Mode):•No characters sent for one second [GT (Guard Times) parameter = 0x3E8]•Input three plus characters (“+++”) within one second [CC (Command Sequence Character) parameter = 0x2B.]•No characters sent for one second [GT (Guard Times) parameter = 0x3E8]All of the parameter values in the sequence can be modified to reflect user preferences.NOTE: Failure to enter AT Command Mode is most commonly due to baud rate mismatch. Ensure the ‘Baud’ setting on the “PC Settings” tab matches the interface data rate of the RF module. By default, the BD parameter = 3 (9600 bps).To Send AT Commands:Figure 2‐05. Syntax for sending AT CommandsTo read a parameter value stored in the RF module’s register, omit the parameter field.The preceding example would change the RF module Destination Address (Low) to “0x1F”. To storethe new value to non-volatile (long term) memory, subsequently send the WR (Write) command.For modified parameter values to persist in the module’s registry after a reset, changes must besaved to non-volatile memory using the WR (Write) Command. Otherwise, parameters arerestored to previously saved values after the module is reset.System Response. When a command is sent to the module, the module will parse and executethe command. Upon successful execution of a command, the module returns an “OK” message. Ifexecution of a command results in an error , the module returns an “ERROR” message.To Exit AT Command Mode:For an example of programming the RF module using AT Commands and descriptions of each configurable parameter, refer to the "Examples" and "XBee Series 2 Command Reference Tables" chapters.Send the 3-character command sequence “+++” and observe guard times before and after thecommand characters. [Refer to the “Default AT Command Mode Sequence” below.]Send AT commands and parameters using the syntax shown below.1. Send the ATCN (Exit Command Mode) command (followed by a carriage return).[OR]2. If no valid AT Commands are received within the time specified by CT (Command ModeTimeout) Command, the RF module automatically returns to Idle Mode.Sleep modes allow the RF module to enter states of low-power consumption when not in use. Toenter Sleep Mode, one of the following conditions must be met (in addition to the module having anon-zero SM parameter value):•Sleep_RQ (pin 9) is asserted•The module is idle (no data is transmitted or received) for the time defined by the ST (Time before Sleep) parameter .The SM command is central to setting Sleep Mode configurations. By default, sleep modes aredisabled (SM=0) and the module remains in Idle/Receive Mode. When in this state, the module isconstantly ready to respond to serial or RF activity.Zigbee Protocol: Sleep Modes Pin/Host Controlled Sleep Pin sleep puts the module to sleep and wakes it from sleep according to the state of Sleep_RQ(pin 9). When Sleep_RQ is asserted (high), the module will finish any transmit or receiveoperations, and then enter a low power state. The module will not respond to either serial or RFactivity while in sleep.To wake a module operating in pin sleep, de-assert Sleep_RQ (pin 9). The module will wake whenSleep_RQ is de-asserted and is ready to transmit or receive when the CTS line is low. When themodule wakes from pin sleep, it sends a transmission to its parent router or coordinator (called apoll request) to see if it has buffered any data packets for the end device. The module will continueto poll its parent for data while it remains awake. If the parent receives an RF data packet destinedfor one or more of its end device children, it will transmit the packet to the end device upon receiptof a poll request. See section 4.3, "Sleep Mode Operation" for more information.Cyclic SleepCyclic sleep allows modules to wake periodically to check for RF data and sleep when idle. Whenthe SM parameter is set to 4, the module is configured to sleep for the time specified by the SPparameter . After the SP time expires, the module will wake and check for RF or serial data. Tocheck for RF data, the module sends a transmission to its parent router or coordinator (called apoll request) to see if its parent has any buffered data packets for the end device. If the parenthas data for the module, the module will remain awake to receive the data. Otherwise, the modulewill return to sleep. (See section 4.3, "Sleep Mode Operation" for more information.)If serial or RF data is received, the module will start the ST timer and remain awake until the timerexpires. While the module is awake, it will continue to send poll request messages to its parent tocheck for additional data. The ST timer will be restarted anytime serial or RF activity occurs. Themodule will resume sleep when the ST timer expires.When the module wakes from sleep, it asserts On/Sleep (pin 13) to provide a wake indicator to ahost device. If a host device wishes to sleep longer than SP time or to wake only when RF dataarrives, the SN command can be used to prevent On/Sleep from asserting for a multiple of SPtime. For example, if SP = 20 seconds, and SN = 5, the On/Sleep pin will remain de-asserted(low) for up to 100 seconds.Table 2‐01.Sleep Mode Configurations (Router / End Device Firmware Only)Sleep ModeSettingTransition into Sleep Mode Transition out of Sleep Mode (wake)Characteristics Related Commands Power Consumption SM=1Assert (high)Sleep_RQ (pin 9)De-assert (0V) Sleep_RQ (pin 9)Pin/Host controlled SM < 1uA SM=4Automatictransition tosleep mode asdefined by theST parameter Transition occurs after the cyclic sleep time interval elapses. The time interval is defined by the SP (Cyclic Sleep Period)parameter. RF module wakes after a pre-determined time interval to detect if RF data is present. SM, ST, SP, SN < 1uAIn the ZigBee protocol, sleep modes are only supported on end devices. See section 4.3, "SleepMode Operation" for more information.If CTS flow control is enabled, CTS (pin 12) is asserted (0V) when the module wakes and de-asserted (high) when the module sleeps, allowing for communication initiated by the host if desired.3. ZigBee Networks3.1. ZigBee Network FormationA ZigBee Personal Area Network (PAN) consists of one coordinator and one or more routers and/orend devices. A ZigBee Personal Area Network (PAN) is created when a coordinator selects achannel and PAN ID to start on. Once the coordinator has started a PAN, it can allow router andend device nodes to join the PAN.When a router or end device joins a PAN, it receives a 16-bit network address and can transmitdata to or receive data from other devices in the PAN. Routers and the coordinator can allow otherdevices to join the PAN, and can assist in sending data through the network to ensure data isrouted correctly to the intended recipient device. When a router or coordinator allows an enddevice to join the PAN, the end device that joined becomes a child of the router or coordinator thatallowed the join.End devices, however can transmit or receive data but cannot route data from one node toanother, nor can they allow devices to join the PAN. End devices must always communicatedirectly to the parent they joined to. The parent router or coordinator can route data on behalf ofan end device child to ensure it reaches the correct destination. End devices are intended to bebattery powered and can support low power modes.Figure 3‐01.Node Types / Sample of a Basic ZigBee Network TopologyThe network address of the PAN coordinator is always 0. When a router joins a PAN, it can alsoallow other routers and end devices to join to it. Joining establishes a parent/child relationshipbetween two nodes. The node that allowed the join is the parent, and the node that joined is thechild. The parent/child relationship is not necessary for routing data.3.1.1. Starting a ZigBee CoordinatorWhen a coordinator first comes up, it performs an energy scan on multiple channels (frequencies)to select an unused channel to start the PAN. After removing channels with high detected energylevels, the coordinator issues an 802.15.4 beacon request command on the remaining, low energylevel channels. Nearby routers or coordinators that have already joined a PAN respond to thebeacon request frame with a small beacon transmission indicating the PAN identifier (PAN ID) thatthey are operating on, and whether or not they are allowing joining. The coordinator will attemptto start on an unused PAN ID and channel. After starting, the coordinator may allow other devicesto join its PAN.3.1.2. Joining a RouterWhen a router first comes up, it must locate and join a ZigBee PAN. To do this, it issues an802.15.4 beacon request command on multiple channels to locate nearby PANs. Nearby routersand coordinators that have already joined a PAN respond to the beacon request frame with a smallbeacon transmission, indicating which channel and PAN ID they are operating on. The routerlistens on each channel for these beacon frames. If a valid PAN is found from one of the receivedbeacons, the router issues a join request to the device that sent the beacon. If joining succeeds,the router will then receive a join confirmation from the device, indicating the join was successful.。

DIGI ZIGBEE 用户手册

Digi International Inc.11001 Bren Road East Minnetonka, MN 55343877 912-3444 or 952 912-3444XBee ®/XBee-PRO ® OEM RF ModulesXBee®/XBee-PRO® OEM RF Modules RF Module Operation RF Module Configuration AppendicesProduct Manual v1.xCx - 802.15.4 ProtocolFor OEM RF Module Part Numbers:XB24-...-001, XBP24-...-001IEEE ® 802.15.4 OEM RF Modules by Digi International90000982_A2008.09.04XBee®/XBee‐PRO® OEM RF Modules ‐ 802.15.4 ‐ v1.xCx [2008.09.04]© 2008 Digi International, Inc. All rights reservedThe contents of this manual may not be transmitted or reproduced in any form or by any means without the written permission of Digi, Inc.XBee® and XBee‐PRO® are registered trademarks of Digi, Inc.Phone: (801) 765‐9885Live Chat: Online Support: /supporteservice/eservicelogin.jspContentsXBee®/XBee‐PRO® OEM RF Modules ‐ 802.15.4 ‐ v1.xCx [2008.09.04]1. XBee®/XBee-PRO OEM RF Modules4Key Features 4Worldwide Acceptance 4Specifications 5Mechanical Drawings 6Mounting Considerations 6Pin Signals 7Electrical Characteristics 82. RF Module Operation9Serial Communications 9UART Data Flow 9Transparent Operation 10API Operation 10Flow Control 11ADC and Digital I/O Line Support 12 I/O Data Format 12API Support 13Sleep Support 13DIO Pin Change Detect 13Sample Rate (Interval) 13I/O Line Passing 14Configuration Example 14XBee®/XBee-PRO Networks 15Peer-to-Peer 15NonBeacon (w/ Coordinator) 15Association 16XBee®/XBee-PRO Addressing 19Unicast Mode 19Broadcast Mode 19Modes of Operation 20Idle Mode 20Transmit/Receive Modes 20Sleep Mode 22Command Mode 243. RF Module Configuration25Programming the RF Module 25Programming Examples 25Remote Configuration Commands 26 Sending a Remote Command 26Applying Changes on Remote 26Remote Command Responses 26 Command Reference Tables 26Command Descriptions 35API Operation 56API Frame Specifications 56API Types 574. Agency Certifications63United States (FCC) 63OEM Labeling Requirements 63FCC Notices 63FCC-Approved Antennas (2.4 GHz) 64 Europe (ETSI) 66OEM Labeling Requirements 66Restrictions 66Declarations of Conformity 66Approved Antennas 67Canada (IC) 67Labeling Requirements 67Japan 67Labeling Requirements 675. Additional Information681-Year Warranty 68Ordering Information 68Contact Digi 691. XBee®/XBee ‐PRO OEM RF ModulesThe XBee and XBee-PRO OEM RF Modules were engineered to meet IEEE 802.15.4 standards and support the unique needs of low-cost, low-power wireless sensor networks. The modules require minimal power and provide reliable delivery of data between devices.The modules operate within the ISM 2.4 GHz frequency band and are pin-for-pin compatible with each other .Key FeaturesWorldwide AcceptanceFCC Approval (USA) Refer to Appendix A [p63] for FCC Requirements.Systems that contain XBee®/XBee-PRO RF Modules inherit Digi Certifications.ISM (Industrial, Scientific & Medical) 2.4 GHz frequency band Manufactured under ISO 9001:2000 registered standardsXBee®/XBee-PRO RF Modules aare optimized for use in the United States, Canada, Australia,Israel, Japan, and Europe. Contact Digi for complete list of government agency approvals.Long Range Data Integrity XBee•Indoor/Urban: up to 100’ (30 m)•Outdoor line-of-sight: up to 300’ (90 m)•Transmit Power: 1 mW (0 dBm)•Receiver Sensitivity: -92 dBm XBee-PRO•Indoor/Urban: up to 300’ (90 m), 200' (60 m) for International variant•Outdoor line-of-sight: up to 1 mile (1600 m), 2500' (750 m) for International variant •Transmit Power: 63mW (18dBm), 10mW (10dBm) for International variant •Receiver Sensitivity: -100 dBm RF Data Rate: 250,000 bps Advanced Networking & Security Retries and AcknowledgementsDSSS (Direct Sequence Spread Spectrum)Each direct sequence channels has over 65,000 unique network addresses available Source/Destination Addressing Unicast & Broadcast Communications Point-to-point, point-to-multipoint and peer-to-peer topologies supportedLow Power XBee•TX Peak Current: 45 mA (@3.3 V)•RX Current: 50 mA (@3.3 V)•Power-down Current: < 10 µA XBee-PRO•TX Peak Current: 250mA (150mA for international variant)•TX Peak Current (RPSMA module only): 340mA (180mA for international variant •RX Current: 55 mA (@3.3 V)•Power-down Current: < 10 µA ADC and I/O line supportAnalog-to-digital conversion, Digital I/O I/O Line Passing Easy-to-UseNo configuration necessary for out-of box RF communicationsFree X-CTU Software(Testing and configuration software)AT and API Command Modes for configuring module parameters Extensive command set Small form factorSpecifications* When operating in Europe, XBee ‐PRO 802.15.4 modules must operate at or below a transmit power output level of 10dBm. Customers have two choices for transmitting at or below 10dBm:a. Order the standard XBee ‐PRO module and change the PL command to ʺ0ʺ (10dBm),b. Order the International variant of the XBee ‐PRO module, which has a maximum transmit output power of 10dBm (@ PL=4).Additionally, European regulations stipulate an EIRP power maximum of 12.86 dBm (19 mW) for the XBee ‐PRO and 12.11 dBm for the XBee when integrating antennas.** When operating in Japan, only the International variant of the XBee ‐PRO 802.15.4 module is approved for use.Antenna Options: The ranges specified are typical when using the integrated Whip (1.5 dBi) and Dipole (2.1 dBi) anten-nas. The Chip antenna option provides advantages in its form factor; however, it typically yields shorter range than theTable 1‐01.Specifications of the XBee®/XBee ‐PRO OEM RF ModulesSpecification XBeeXBee-PROPerformance Indoor/Urban Range Up to 100 ft (30 m) Up to 300 ft. (90 m), up to 200 ft (60 m) International variantOutdoor RF line-of-sight Range Up to 300 ft (90 m) Up to 1 mile (1600 m), up to 2500 ft (750 m) international variantTransmit Power Output (software selectable)1mW (0 dBm)63mW (18dBm)*10mW (10 dBm) for International variant RF Data Rate250,000 bps250,000 bpsSerial Interface Data Rate (software selectable)1200 bps - 250 kbps(non-standard baud rates also supported)1200 bps - 250 kbps(non-standard baud rates also supported)Receiver Sensitivity -92 dBm (1% packet error rate)-100 dBm (1% packet error rate)Power Requirements Supply Voltage 2.8 – 3.4 V 2.8 – 3.4 VTransmit Current (typical)45mA (@ 3.3 V)250mA (@3.3 V) (150mA for international variant) RPSMA module only: 340mA (@3.3 V) (180mA for international variant)Idle / Receive Current (typical)50mA (@ 3.3 V)55mA (@ 3.3 V)Power-down Current < 10 µA< 10 µAGeneralOperating Frequency ISM 2.4 GHzISM 2.4 GHzDimensions0.960” x 1.087” (2.438cm x 2.761cm)0.960” x 1.297” (2.438cm x 3.294cm)Operating Temperature -40 to 85º C (industrial)-40 to 85º C (industrial)Antenna Options Integrated Whip, Chip or U.FL Connector, RPSMA ConnectorIntegrated Whip, Chip or U.FL Connector, RPSMA ConnectorNetworking & Security Supported Network Topologies Point-to-point, Point-to-multipoint & Peer-to-peer Number of Channels (software selectable)16 Direct Sequence Channels 12 Direct Sequence Channels Addressing Options PAN ID, Channel and AddressesPAN ID, Channel and AddressesAgency ApprovalsUnited States (FCC Part 15.247)OUR-XBEE OUR-XBEEPRO Industry Canada (IC)4214A XBEE 4214A XBEEPROEurope (CE) ETSIETSI (Max. 10 dBm transmit power output)*Japan R201WW07215214R201WW08215111" (Max. 10 dBm transmit power output)**AustrailaC-Tick C-TickWhip and Dipole antenna options when transmitting outdoors.For more information, refer to the "XBee Antennas" Knowl-edgebase Article located on Digi's Support Web siteMechanical DrawingsFigure 1‐01.Mechanical drawings of the XBee®/XBee‐PRO OEM RF Modules (antenna options not shown)The XBee and XBee‐PRO RF Modules are pin‐for‐pin compatible.Mounting ConsiderationsThe XBee®/XBee-PRO RF Module was designed to mount into a receptacle (socket) and thereforedoes not require any soldering when mounting it to a board. The XBee Development Kits containRS-232 and USB interface boards which use two 20-pin receptacles to receive modules.Figure 1‐02.XBee Module Mounting to an RS‐232 Interface Board.The receptacles used on Digi development boards are manufactured by Century Interconnect.Several other manufacturers provide comparable mounting solutions; however, Digi currently usesthe following receptacles:•Through-hole single-row receptacles -Samtec P/N: MMS-110-01-L-SV (or equivalent)•Surface-mount double-row receptacles -Century Interconnect P/N: CPRMSL20-D-0-1 (or equivalent)•Surface-mount single-row receptacles -Samtec P/N: SMM-110-02-SM-SDigi also recommends printing an outline of the module on the board to indicate the orientation themodule should be mounted.Pin SignalsFigure 1‐03.XBee®/XBee ‐PRO RF Module PinNumbers (top sides shown ‐ shields on bottom)* Function is not supported at the time of this release Design Notes:•Minimum connections: VCC, GND, DOUT & DIN•Minimum connections for updating firmware: VCC, GND, DIN, DOUT , RTS & DTR •Signal Direction is specified with respect to the module •Module includes a 50k Ω pull-up resistor attached to RESET•Several of the input pull-ups can be configured using the PR command •Unused pins should be left disconnectedTable 1‐02.Pin Assignments for the XBee and XBee ‐PRO Modules(Low ‐asserted signals are distinguished with a horizontal line above signal name.)Pin #Name DirectionDescription 1VCC -Power supply 2DOUT Output UART Data Out 3DIN / CONFIGInput UART Data In 4DO8*Output Digital Output 85RESET Input Module Reset (reset pulse must be at least 200 ns)6PWM0 / RSSI Output PWM Output 0 / RX Signal Strength Indicator7PWM1Output PWM Output 18[reserved]-Do not connect9DTR / SLEEP_RQ / DI8Input Pin Sleep Control Line or Digital Input 810GND -Ground11AD4 / DIO4Either Analog Input 4 or Digital I/O 412CTS / DIO7Either Clear-to-Send Flow Control or Digital I/O 713ON / SLEEP Output Module Status Indicator 14VREFInput Voltage Reference for A/D Inputs15Associate / AD5 / DIO5Either Associated Indicator, Analog Input 5 or Digital I/O 516RTS / AD6 / DIO6Either Request-to-Send Flow Control, Analog Input 6 or Digital I/O 617AD3 / DIO3Either Analog Input 3 or Digital I/O 318AD2 / DIO2Either Analog Input 2 or Digital I/O 219AD1 / DIO1Either Analog Input 1 or Digital I/O 120AD0 / DIO0EitherAnalog Input 0 or Digital I/O 0Electrical CharacteristicsTable 1‐03.DC Characteristics (VCC = 2.8 ‐ 3.4 VDC)Symbol Characteristic ConditionMin Typical Max Unit V IL Input Low Voltage All Digital Inputs -- 0.35 * VCCV V IH Input High Voltage All Digital Inputs 0.7 * VCC- -V V OL Output Low Voltage I OL = 2 mA, VCC >= 2.7 V --0.5V V OH Output High Voltage I OH = -2 mA, VCC >= 2.7 V VCC - 0.5--V II IN Input Leakage CurrentV IN = VCC or GND, all inputs, per pin -0.0251µA II OZ High Impedance Leakage CurrentV IN = VCC or GND, all I/O High-Z, per pin-0.0251µA TX Transmit Current VCC = 3.3 V -45(XBee)215, 140(PRO,Int)-mA RX Receive Current VCC = 3.3 V -50(XBee)55(PRO)-mA PWR-DWN Power-down CurrentSM parameter = 1-< 10-µATable 1‐04.ADC Characteristics (Operating)Symbol CharacteristicConditionMin Typical Max Unit V REFH VREF - Analog-to-Digital converterreference range 2.08-V DDAD V I REF VREF - Reference Supply CurrentEnabled-200-µA Disabled or Sleep Mode-< 0.010.02µA V INDCAnalog Input Voltage 11.Maximum electrical operating range, not valid conversion range.V SSAD - 0.3-V DDAD + 0.3VTable 1‐05.ADC Timing/Performance Characteristics 11.All ACCURACY numbers are based on processor and system being in WAIT state (very little activity and no IO switching) and that adequate low ‐pass filtering is present on analog input pins (filter with 0.01 μF to 0.1 μF capacitor between analog input and VREFL). Failure to observe these guidelines may result in system or microcontroller noise causing accuracy errors which will vary based on board layout and the type and magnitude of the activity.Data transmission and reception during data conversion may cause some degradation of these specifications, depending on the number and timing of packets. It is advisable to test the ADCs in your installation if best accuracy is required.Symbol Characteristic Condition Min Typical MaxUnit R AS Source Impedance at Input 22.R AS is the real portion of the impedance of the network driving the analog input pin. Values greater than this amount may not fully charge the input circuitry of the ATD resulting in accuracy error.--10k V AIN Analog Input Voltage 33.Analog input must be between V REFL and V REFH for valid conversion. Values greater than V REFH will convert to $3FF.V REFLV REFH V RES Ideal Resolution (1 LSB)44.The resolution is the ideal step size or 1LSB = (V REFH –V REFL )/10242.08V < V DDAD <3.6V 2.031- 3.516mV DNL Differential Non-linearity 55.Differential non ‐linearity is the difference between the current code width and the ideal code width (1LSB). The current code width is the difference in the transition voltages to and from the current code.-±0.5±1.0LSB INL Integral Non-linearity 66.Integral non ‐linearity is the difference between the transition voltage to the current code and the adjusted ideal transition voltage for the current code. The adjusted ideal transition voltage is (Current Code–1/2)*(1/((V REFH +E FS )–(V REFL +E ZS ))).-±0.5±1.0LSB E ZS Zero-scale Error 77.Zero ‐scale error is the difference between the transition to the first valid code and the ideal transition to that code. The Ideal transition voltage to a given code is (Code–1/2)*(1/(V REFH –V REFL )).-±0.4±1.0LSB F FS Full-scale Error 88.Full ‐scale error is the difference between the transition to the last valid code and the ideal transition to that code. The ideal transition voltage to a given code is (Code–1/2)*(1/(V REFH –V REFL )).-±0.4±1.0LSB E IL Input Leakage Error99.Input leakage error is error due to input leakage across the real portion of the impedance of the network driving the analog pin. Reducing the impedance of the network reduces this error.-±0.05±5.0LSB E TUTotal Unadjusted Error 1010.Total unadjusted error is the difference between the transition voltage to the current code and the ideal straight ‐line trans ‐fer function. This measure of error includes inherent quantization error (1/2LSB) and circuit error (differential, integral, zero ‐scale, and full ‐scale) error. The specified value of E TU assumes zero E IL (no leakage or zero real source impedance).-±1.1±2.5LSB2. RF Module OperationSerial CommunicationsThe XBee®/XBee-PRO OEM RF Modules interface to a host device through a logic-level asynchro-nous serial port. Through its serial port, the module can communicate with any logic and voltagecompatible UART; or through a level translator to any serial device (For example: Through a Digiproprietary RS-232 or USB interface board).UART Data FlowDevices that have a UART interface can connect directly to the pins of the RF module as shown inthe figure below.Figure 2‐01.System Data Flow Diagram in a UART‐interfaced environment(Low‐asserted signals distinguished with horizontal line over signal name.)Serial DataData enters the module UART through the DI pin (pin 3) as an asynchronous serial signal. The sig-nal should idle high when no data is being transmitted.Each data byte consists of a start bit (low), 8 data bits (least significant bit first) and a stop bit(high). The following figure illustrates the serial bit pattern of data passing through the module.Figure 2‐02.UART data packet 0x1F (decimal number ʺ31ʺ) as transmitted through the RF moduleExample Data Format is 8‐N‐1 (bits ‐ parity ‐ # of stop bits)The module UART performs tasks, such as timing and parity checking, that are needed for datacommunications. Serial communications depend on the two UARTs to be configured with compati-ble settings (baud rate, parity, start bits, stop bits, data bits).XBee®/XBee‐PRO® OEM RF Modules ‐ 802.15.4 ‐ v1.xCx [2008.09.04]Transparent OperationBy default, XBee®/XBee-PRO RF Modules operate in Transparent Mode. When operating in thismode, the modules act as a serial line replacement - all UART data received through the DI pin isqueued up for RF transmission. When RF data is received, the data is sent out the DO pin.Serial-to-RF PacketizationData is buffered in the DI buffer until one of the following causes the data to be packetized andtransmitted:1. No serial characters are received for the amount of time determined by the RO (Packetiza-tion Timeout) parameter. If RO = 0, packetization begins when a character is received.2.The maximum number of characters that will fit in an RF packet (100) is received.3.The Command Mode Sequence (GT + CC + GT) is received. Any character buffered in theDI buffer before the sequence is transmitted.If the module cannot immediately transmit (for instance, if it is already receiving RF data), theserial data is stored in the DI Buffer. The data is packetized and sent at any RO timeout or when100 bytes (maximum packet size) are received.If the DI buffer becomes full, hardware or software flow control must be implemented in order toprevent overflow (loss of data between the host and module).API OperationAPI (Application Programming Interface) Operation is an alternative to the default TransparentOperation. The frame-based API extends the level to which a host application can interact with thenetworking capabilities of the module.When in API mode, all data entering and leaving the module is contained in frames that defineoperations or events within the module.Transmit Data Frames (received through the DI pin (pin 3)) include:•RF Transmit Data Frame•Command Frame (equivalent to AT commands)Receive Data Frames (sent out the DO pin (pin 2)) include:•RF-received data frame•Command response•Event notifications such as reset, associate, disassociate, etc.The API provides alternative means of configuring modules and routing data at the host applica-tion layer. A host application can send data frames to the module that contain address and payloadinformation instead of using command mode to modify addresses. The module will send dataframes to the application containing status packets; as well as source, RSSI and payload informa-tion from received data packets.The API operation option facilitates many operations such as the examples cited below:->Transmitting data to multiple destinations without entering Command Mode->Receive success/failure status of each transmitted RF packet->Identify the source address of each received packetTo implement API operations, refer to API sections [p56].Flow ControlFigure 2‐03.Internal Data Flow DiagramDI (Data In) BufferWhen serial data enters the RF module through the DI pin (pin 3), the data is stored in the DI Buffer until it can be processed.Hardware Flow Control (CTS). When the DI buffer is 17 bytes away from being full; by default, the module de-asserts CTS (high) to signal to the host device to stop sending data [refer to D7 (DIO7 Configuration) parameter]. CTS is re-asserted after the DI Buffer has 34 bytes of memory available.How to eliminate the need for flow control:Case in which the DI Buffer may become full and possibly overflow:Refer to the RO (Packetization Timeout), BD (Interface Data Rate) and D7 (DIO7 Configuration) com-mand descriptions for more information.DO (Data Out) BufferWhen RF data is received, the data enters the DO buffer and is sent out the serial port to a host device. Once the DO Buffer reaches capacity, any additional incoming RF data is lost.Hardware Flow Control (RTS). If RTS is enabled for flow control (D6 (DIO6 Configuration) Parameter = 1), data will not be sent out the DO Buffer as long as RTS (pin 16) is de-asserted.Two cases in which the DO Buffer may become full and possibly overflow:Refer to the D6 (DIO6 Configuration) command description for more information.1.Send messages that are smaller than the DI buffer size (202 bytes).2.Interface at a lower baud rate [BD (Interface Data Rate) parameter] than the throughputdata rate.If the module is receiving a continuous stream of RF data, any serial data that arrives on the DI pin is placed in the DI Buffer . The data in the DI buffer will be transmitted over-the-air when the module is no longer receiving RF data in the network.1. If the RF data rate is set higher than the interface data rate of the module, the module willreceive data from the transmitting module faster than it can send the data to the host.2. If the host does not allow the module to transmit data out from the DO buffer because ofbeing held off by hardware or software flow control.ADC and Digital I/O Line SupportThe XBee®/XBee-PRO RF Modules support ADC (Analog-to-digital conversion) and digital I/O linepassing. The following pins support multiple functions:Table 2‐01.Pin functions and their associated pin numbers and commandsAD = Analog‐to‐Digital Converter, DIO = Digital Input/OutputPin functions not applicable to this section are denoted within (parenthesis).Pin Function Pin#AT CommandAD0 / DIO020D0AD1 / DIO119D1AD2 / DIO218D2AD3 / DIO3 / (COORD_SEL)17D3AD4 / DIO411D4AD5 / DIO5 / (ASSOCIATE)15D5DIO6 / (RTS)16D6DIO7 / (CTS)12D7DI8 / (DTR) / (Sleep_RQ)9D8To enable ADC and DIO pin functions:For ADC Support: Set ATDn = 2For Digital Input support: Set ATDn = 3For Digital Output Low support:Set ATDn = 4For Digital Output High support:Set ATDn = 5I/O Data FormatI/O data begins with a header. The first byte of the header defines the number of samples forth-coming. The last 2 bytes of the header (Channel Indicator) define which inputs are active. Eachbit represents either a DIO line or ADC channel.Figure 2‐04.HeaderSample data follows the header and the channel indicator frame is used to determine how to readthe sample data. If any of the DIO lines are enabled, the first 2 bytes are the DIO sample. TheADC data follows. ADC channel data is represented as an unsigned 10-bit value right-justified ona 16- bit boundary.Figure 2‐05.Sample DataAPI SupportI/O data is sent out the UART using an API frame. All other data can be sent and received using Transparent Operation [refer to p10] or API framing if API mode is enabled (AP > 0).API Operations support two RX (Receive) frame identifiers for I/O data (set 16-bit address to0xFFFE and the module will do 64-bit addressing):•0x82 for RX (Receive) Packet: 64-bit address I/O•0x83 for RX (Receive) Packet: 16-bit address I/OThe API command header is the same as shown in the “RX (Receive) Packet: 64-bit Address” and “RX (Receive) Packet: 64-bit Address” API types [refer to p62]. RX data follows the formatdescribed in the I/O Data Format section [p12].Applicable Commands: AP (API Enable)Sleep SupportAutomatic wakeup sampling can be suppressed by setting SO bit 1.When an RF module wakes, it will always do a sample based on any active ADC or DIO lines. This allows sampling based on the sleep cycle whether it be Cyclic Sleep (SM parameter = 4 or 5) or Pin Sleep (SM = 1 or 2). Togather more samples when awake, set the IR (Sample Rate) parameter.For Cyclic Sleep modes: If the IR parameter is set, the module will stay awake until the IT (Sam-ples before TX) parameter is met. The module will stay awake for ST (Time before Sleep) time.Applicable Commands: IR (Sample Rate), IT (Samples before TX), SM (Sleep Mode), IC (DIO Change Detect), SO (Sleep Options)DIO Pin Change DetectWhen “DIO Change Detect” is enabled (using the IC command), DIO lines 0-7 are monitored.When a change is detected on a DIO line, the following will occur:1.An RF packet is sent with the updated DIO pin levels. This packet will not contain any ADCsamples.2.Any queued samples are transmitted before the change detect data. This may result inreceiving a packet with less than IT (Samples before TX) samples.Note: Change detect will not affect Pin Sleep wake-up. The D8 pin (DTR/Sleep_RQ/DI8) is the only line that will wake a module from Pin Sleep. If not all samples are collected, the module will still enter Sleep Mode after a change detect packet is sent.Applicable Commands: IC (DIO Change Detect), IT (Samples before TX)NOTE: Change detect is only supported when the Dx (DIOx Configuration) parameter equals 3,4 or 5. Sample Rate (Interval)The Sample Rate (Interval) feature allows enabled ADC and DIO pins to be read periodically on modules that are not configured to operate in Sleep Mode. When one of the Sleep Modes isenabled and the IR (Sample Rate) parameter is set, the module will stay awake until IT (Samples before TX) samples have been collected.Once a particular pin is enabled, the appropriate sample rate must be chosen. The maximum sam-ple rate that can be achieved while using one A/D line is 1 sample/ms or 1 KHz (Note that themodem will not be able to keep up with transmission when IR & IT are equal to “1” and that con-figuring the modem to sample at rates greater than once every 20ms is not recommended).Applicable Commands: IR (Sample Rate), IT (Samples before TX), SM (Sleep Mode)I/O Line PassingVirtual wires can be set up between XBee®/XBee-PRO Modules. When an RF data packet isreceived that contains I/O data, the receiving module can be setup to update any enabled outputs (PWM and DIO) based on the data it receives.Note that I/O lines are mapped in pairs. For example: AD0 can only update PWM0 and DI5 can only update DO5. The default setup is for outputs not to be updated, which results in the I/O data being sent out the UART (refer to the IU (Enable I/O Output) command). To enable the outputs to be updated, the IA (I/O Input Address) parameter must be setup with the address of the module that has the appropriate inputs enabled. This effectively binds the outputs to a particular module’s input. This does not affect the ability of the module to receive I/O line data from other modules - only its ability to update enabled outputs. The IA parameter can also be setup to accept I/O data for output changes from any module by setting the IA parameter to 0xFFFF .When outputs are changed from their non-active state, the module can be setup to return the out-put level to it non-active state. The timers are set using the Tn (Dn Output Timer) and PT (PWM Output Timeout) commands. The timers are reset every time a valid I/O packet (passed IA check) is received. The IC (Change Detect) and IR (Sample Rate) parameters can be setup to keep the output set to their active output if the system needs more time than the timers can handle.Note: DI8 cannot be used for I/O line passing.Applicable Commands: IA (I/O Input Address), Tn (Dn Output Timeout), P0 (PWM0 Configura-tion), P1 (PWM1 Configuration), M0 (PWM0 Output Level), M1 (PWM1 Output Level), PT (PWM Output Timeout), RP (RSSSI PWM Timer)Configuration ExampleAs an example for a simple A/D link, a pair of RF modules could be set as follows:These settings configure the remote module to sample AD0 and AD1 once each every 20 ms. It then buffers 5 samples each before sending them back to the base module. The base should then receive a 32-Byte transmission (20 Bytes data and 12 Bytes framing) every 100 ms.Remote ConfigurationDL = 0x1234MY = 0x5678D0 = 2D1 = 2IR = 0x14IT = 5Base Configuration DL = 0x5678MY = 0x1234P0 = 2P1 = 2IU = 1IA = 0x5678 (or 0xFFFF)。

1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。

XBee和XBee - PRO OEM RF模块的设计，以ZigBee协议内运作，支持低成本的独特需求，低功耗无线传感器网络工程。

模块只需要最小的功率，就能提供远程设备之间的数据传输的可靠性。

这两个模块内运作的ISM 2.4 GHz频段，且引脚对引脚相互兼容。

1.1 主要特点先进的网络和安全重试和确认。

DSSS（直接序列扩频）每一个序列频道，可使用超过65000个唯一的网络地址点至点，点对点，点对多点和点对点的对等拓扑支撑自行安排，自我修复和故障容错网络易于使用没有配置必要的外箱射频通信AT和API命令模式配置模块参数小尺寸广泛的命令集免费的X - CTU软件（测试和配置软件）免费及无限技术支持1.1.1. 全球认证FCC认证（美国）参见附录A [p34要求]。

系统包含的XBee / XBee-PRO射频模块继承MaxStream的认证。

ISM（工业，科学和医疗）2.4吉赫频带的ISO 9001:2000认证机构认证下制造的注册标准的XBee / XBee-PRO射频模块列表被优化用于在美国，加拿大，澳大利亚，以色列和欧洲。

1.2.描述表1-01，XBee/XBee‐PRO OEM RF 模块(简述)当在欧洲运用时：XBee - PRO RF模块必须被配置为运行在一个最大发射功率为10 dBm的输出水平。

电源输出级别设置使用PL 命令。

PL参数必须等于“0”（10 dBm）。

此外，欧洲法规规定，EIRP最高功率为12.86 dBm的（19毫瓦），对于XBee – PRO的12.11 dBm和XBee时高增益天线天线选项：指定的范围内使用时是典型的集成块（1.5 dBi的）和偶极子（2.1 dBi的）天线。

该芯片天线选项提供要素优势，它的形式，但它通常会产生更短的选择范围比带和偶极子天线发射时，在户外。

1.3.机械尺寸图1 - 01 XBee / XBee - PRO OEM RF模块的机械尺寸（天线选项未显示）The XBee and XBee‐PRO RF Modules are pin‐for‐pin compatible.XBee和XBee - 专业射频模块的引脚- 为- 引脚兼容。

XBee / XBee - Pro的射频模块的目的是要安装到一个插座（插座）因此安装时不需要任何焊接，开发套件包含的XBeeRS - 232和USB接口板的使用两个20针插座接收模块。

图1 - 02 XBee模块安装到一个RS - 232接口板。

通孔单排插座Samtec P/N: MMS-110-01-L-SV (或者相同的)表面贴装双排插座P/N: CPRMSL20-D-0-1 (或者相同的)表面贴装单排插座Samtec P/N: SMM-110-02-SM-SMaxStream的还建议对印刷电路板印上模块的轮廓，以指示方向便于安装。

1.5.引脚信号图1-03 XBee / XBee-PRO射频模块的引脚数（顶部显示–防护在底部）表1-02XBee和XBee - ‐PRO的引脚分配Pin# Name Direction Description1 VCC - 电源2 DOUT Output UART的数据输出3 DIN / CONFIG Input UART的数据输入4 DO8* Output Digital Output 8数据输出5 RESET Input 模块复位（复位脉冲必须至少为200纳秒）6 PWM0 / RSSI Output PWM输出0 / RX信号强度指示器7 [reserved] - 请勿连接8 [reserved] - 请勿连接9 DTR / SLEEP_RQ* / DI8 Input 睡眠引脚控制线或数字输入810 GND - 接地11 AD4* / DIO4* Either 模拟输入4或数字I / O 412 CTS / DIO7 Either 明确对发送流量控制或数字I / O 713 ON / SLEEP Output 模块状态指示灯14 VREF* Input 电压参考的A / D输入15 Associate / AD5* / DIO5* Either 相关的指标，模拟输入5或数字I / O五16 RTS* / AD6* / DIO6* Either 要求对发送的流量控制，模拟输入6或数字I / O 617 AD3* / DIO3* Either 模拟输入3或数字I / O 318 AD2* / DIO2* Either 模拟输入2或数字I / O 219 AD1* / DIO1* Either 模拟输入1或数字I / O 120 AD0* / DIO0* Either 模拟输入0或数字I / O 0设计注意:•最小连接：VCC，GND的，DOUT和DIN•最小连接更新固件VCC, GND, DIN, DOUT, RTS & DTR•信号方向是相对于指定的模块•模块包括一个50K的Ω上拉电阻连接到RESET•在输入几个拉电路可配置使用PE命令•未使用引脚应由断开1.6.电气特性表1-03Xbee和XBee‐PRO的直流特性的（VCC = 2.8 - 3.4伏）1.7.定义表1-4 术语和定义ZigBee协议PAN 个人区域网络-数据通信网络，其中包括一台协调器和一个或多个路由器/终端设备。

网络工作形成是由网络最大深度，最大子路由器和的最大的子终端设备加入PAN过程的一个节点的ZigBee成为一部分。

一个节点成为网络的一部分加入到一个网络连接到一个由协调器或路由器（即以前）。

在参与过程中，允许加入的节点（父）分配一个16位地址加入节点（子）。

网络最大深度协调器水平的后代从。

在一个MaxStreamPAN中，网络的最大深度为5。

最多子路由最大数量的路由器可以加入到一个节点。

最多6个子路由在MaxStream PAN中最多子设备该终端设备的最大数量可以加入到一个节点。

最多14个子终端设备在MaxStream PAN中网络地址16位地址分配给一个节点后，加入到另一个节点。

作业通道选定的频率为节点之间的数据通信。

经营渠道选择了协调器的权力。

能源扫描一个射频信道扫描，检测选定的能源渠道的数量目前在。

协调器使用能源扫描，以确定的工作频道。

路由请求广播传输由一台协调器或路由器在整个网络中的节点尝试建立一个路由到目的地。

路线回复单播传输送回请求发端的路线。

它是由一个节点开始时，收到一个路由请求分组和它的地址匹配路由请求分组的目的地址在。

路线发现建立一个路由到目标节点时，一个不存在于路由表的过程。

它是基于AODV路由协议（特设按需距离矢量路由）协议。

ZigBee堆栈ZigBee是一种规范的出版高层通信协议的规定，小，低功耗模块的使用。

在ZigBee协议栈提供了关于802.15.4规范顶层网络功能层。

例如，网和路由功能可用于ZigBee的解决方案是不存在的802.15.4协议2. ZigBee网络2.1. ZigBee网络的构成pan是一个ZigBee的协调器组成，节点加入到一个或一个先前加入路由器。

一旦协调器定义的经营渠道和PAN ID，它可以让路由器和终端设备加入到它。

当一个节点加入网络，它接收一个16位网络地址。

一旦路由器加入网络时，它也可以让其他节点加入到它。

加入成立的父/子关系的两个节点之间。

允许的节点联接是家长和加入的节点是孩子。

父/子关系并不路由需要，但它是必要的分配网络的形成和网络地址。

如果不存在一个协调器，一个网络不能形成。

一个节点不能发送或接收数据，直到它已加入了pan。

2.1.1.节点类型ZigBeepan由一台协调器和一个或多个路由器和/或终端设备。

参照协调器[p17]和路由器[p17]章节的“射频模块操作”为更多的类型信息就每个节点图2 - 01。

节点类型/样的一个基本ZigBee网络拓扑协调器每设立一个pan/组织了pan电源供电路由器可选能在PAN供电终端设备各自能在pan低功耗2.1.2. Network Limitations网络限制限制的以下范围：•最大子项-协调器和各参加路由器可以支持多达20台子项，其中6个可路由器（最多子项路由器）。

参考图2－02•网络最大深度-最大网络深度为5 -最大深度是指网络协调员水平的后代从。

参考图2－03。

请参阅定义表[P8的更多信息]的。

图2 - 02占子项父项的最大设备数量协调器（每个PAN）和路由器可以有6个路由器和终端设备14加入到他们。

图2-03。

最大的网络深度网络深度可以跨越5个级别深度2.2. ZigBee网络通信2.2.1. ZigBee的寻址802.15.4协议的ZigBee协议赖以建立指定两个地址类型：• 16位网络地址• 64位地址16位网络地址一个16位网络地址被分配到一个节点时，节点加入网络。

该网络地址是唯一的每个网络节点在。

但是，网络地址是不是静态的-它可以改变。

以下两个条件将导致一个节点收到一个新的网络地址：1.终端设备无法与它的母机进行通讯2. 路由器或终端设备，当它的权力周期，发送一个802.15.4孤儿的通知找到其父母。

如果父节点不响应，路由器或终端设备认为不加入了本身并重申了加入网络的进程。

一旦节点加入该网络，它和它的后代都将收到一个新的网络地址由于所有的ZigBee通信使用16位寻址，一个节点的16位地址必须知道的地方才可以通信64位地址每个节点包含一个唯一的64位地址。

64位地址唯一标识一个节点，是永久性的。

2.2.2. 路由网网状路由允许数据包遍历多个节点（啤酒花）在一个网络从源路由数据到一个目的地。

这条路线一包可以在一个网状网络是独立于父/子关系的建立过程中加入。

前转递数据包从源节点到目的地，必须建立一个路线。

路由发现是基于AODV路由协议（特设按需距离矢量路由）协议。

AODV协议（特设按需距离矢量）路由算法根据协议AODV的路由是使用节点表中每个节点存储目的地，在未来的来源和啤酒花（节点之间的中介目标节点）的。

如果下一跳不知道，路由发现必须进行，以便找到一个路径。

由于只有有限数量的路线可以被存储在路由器，路由发现会发生不同的节点之间往往有很多的沟通与大型网络。

当一个源节点必须找到一个路由到目标节点时，它发送一个广播路由请求命令。

这条路线请求命令包含源网络地址，网络地址和目标成本的路径字段（1质量指标衡量航线）。

由于路由请求命令是通过网络传播（指的是广播传输部分[P13的]），每个节点，重新广播的消息更新路径的成本领域，并创建一个临时表中发现入境航线。

当目标节点接收到路由请求，它比较针对以前收到路由请求命令'路径成本'字段。

如果路径成本要求存储在收到更好的途径是比任何以前，目标节点将发送一个路由应答包的节点起源路线的要求。