In the following a documentation of all class methods. To get an instance xbeeAPI of the XBeeAPI class: 0xA5: Join Notification Status (ZigBee)Įnabling encryption with series 1 XBees / 802.15.4 devices causes some inexplicable problems - see Issue #12.0xA4: Register Joining Device Status (ZigBee).0xA3: Many-to-One Route Request Indicator (ZigBee).0xA2: Device Authenticated Indicator (ZigBee).0xA0: Over-the-Air Firmware Update Status (ZigBee).These (more esoteric) frame types have not been implemented yet, Open a new issue if you need something in particular: 0x95: Node Identification Indicator (AO=0) (ZNet, ZigBee).0x94: XBee Sensor Read Indicator (AO=0) (ZNet, ZigBee).0x92: ZigBee IO Data Sample Rx Indicator (ZNet, ZigBee).0x91: ZigBee Explicit Rx Indicator (AO=1) (ZNet, ZigBee).0x90: ZigBee Receive Packet (AO=0) (ZNet, ZigBee).0x8B: ZigBee Transmit Status (ZNet, ZigBee).0x11: Explicit Addressing ZigBee Command Frame (ZNet, ZigBee).0x10: ZigBee Transmit Request (ZNet, ZigBee).0x97: Remote Command Response (802.15.4, ZNet, ZigBee).0x17: Remote Command Request (802.15.4, ZNet, ZigBee).0x09: AT Command Queue Parameter Value (802.15.4, ZNet, ZigBee).The following frame types are implemented: Since ZigBee is more robust and offers more features than ZNet (none of which are yet implemented here, though!), you might be interested in upgrading your Series 2 modules from ZNet 2.5 to ZigBee: upgradingfromznettozb.pdf. Both AP=1 (without escaping) and AP=2 (with escaping) modes are supported (set the api_mode parameter accordingly). Be sure to use the correct ones for your module (as described in the documents and the list below). Some frame types are 802.15.4, ZNet or ZigBee specific. These documents are used as reference: 90000976.pdf (for Series 2) andĩ0000982.pdf (for Series 1). This module supports the 802.15.4 and ZigBee (including ZNet) protocol stacks.įrom the XBee family, Series 1 (802.15.4) and Series 2 (ZNet 2.5 and ZigBee) modules are supported, since they come with firmwares talking either one of these stacks. You might want to spend some time reading through the Zigbee Cluster Library specification to understand the concept of endpoints, clusters and attributes, which may help you to understand the tables you need to set up in your program to implement them.See the Examples section for more useful/practical examples! SUPPORTED FIRMWARES AND DEVICES You can use that sample to validate the endpoint/cluster/attribute table that you've set up in a particular program. The Zigbee Walker sample shows how to use ZDO/ZDP queries to enumerate endpoints, and then ZCL queries to enumerate clusters and attributes. Perhaps look at include/zigbee/zcl_basic_attributes.h and samples/common/_zigbee_walker.c on how to set up the endpoint table with a Basic cluster and its attributes. You might want to look at zcl_comm_startup_attributes and zcl_comm_startup_attribute_tree in src/zigbee/zcl_commissioning.c to see how you can set up an attribute tree for your cluster. The Commissioning Cluster is a part of the Zigbee spec. The Commissioning Client and Server samples are overkill for just getting started, but they are used for "something real".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |