Messages and beacons that appear when a device joins a ZigBee Protocol network can reveal some interesting facts. The short range wireless networking market is set
click to enlarge
Figure 1: When you fire up the ZENA Wireless Network Analyzer, messages similar to these should appear when a device joins the network. The tool's screenshot reveals a lot of information about the state of the network.
For wireless designers, there are many Radio Frequency (RF) transceivers and ZigBee protocol stacks available today for implementing ZigBee protocol functionality into their applications. Regardless of transceiver and stack selection, design engineers should look at devices and tools that will enable them to evaluate and develop their ZigBee protocol applications quickly. Given the sophistication of the ZigBee protocol, it is also necessary that designers use the appropriate development tools to help them design and debug their applications. This article assumes that the reader has basic familiarity with the ZigBee protocol.
There are several wireless network analyzers, or sniffers available. Obtaining one when you first begin your wireless development is a critical investment, and will save you hours of frustration. Some analyzers have graphical interfaces, while others have a more text-based interface. Be sure to select an analyzer with an interface that is easy for you to read. In the examples below, we will be using Microchip's ZENA Wireless Network Analyzer, which displays messages in a graphical format. But no matter what analyzer you chose, being able to quickly decipher the key portions of the ZigBee protocol messages will enable you to develop and debug your system efficiently.
Network FormationThe messages that appear when a device joins a ZigBee protocol network tell us a lot about the network. When a device tries to join a network, it issues a beacon request. Nearby coordinators and routers will respond by issuing beacons. The new device will select a beacon and send that device an association request, asking to join
click to enlarge
Figure 2: Much of the ZigBee protocol reliability comes from the extensive acknowledgment feature. The three levels of acknowledgment can be used to troubleshoot the ZigBee protocol network.
The first message is from the new device, requesting beacons. The next two messages are beacons. We can tell some interesting things about the devices from these beacons. First, we can tell that the second beacon is from the coordinator, because the source address is 0x0000, and the depth specified in the beacon payload is 0. The first beacon is from a router, because its source address is nonzero. We can also tell that this router is joined to the network through the coordinator, because it is on the same network (the source PANs are identical), and the beacon payload Depth is 1. We also know that at the application layer, both of these devices are accepting new devices to join the network, because the superframe specification Assoc bits are set. However, if we look at the beacon payloads, we can see that the coordinator has no capacity for any additional routers or end devices, because the RtrCap and DevCap bits are both 0. The router, meanwhile, still has capacity for both routers and end devices.
In the fourth message, the new device has decided to try to join the network. By examining the destination address of the association request, we can tell what network device the new device is trying to join to the router. The association request tells us a lot about the new device. The critical elements are the Dev and RxOn bits. The Dev bit indicates that the device is trying to join as an end device. Also, we know that this device will always have its transceiver on, so its parent will not have to buffer messages for it.
This bit is critical for later communication. If RxOn is set to off, then the parent will assume that the new device keeps its transceiver off, and will buffer messages for it. If the new device never requests messages, then the parent will never send messages to it.
Finally, we can see that the association request was successful. We now have a new FFD (Full Function Device) end device on the network, with a short address of 0x1AF9.
Acknowledged TransmissionsThe ZigBee protocol is a highly acknowledged protocol. There are three levels of acknowledge: MAC (Medium Access Control), APS (Application Sub-support), and
The first message is the command to device 0x0000 to set an attribute. This is followed by a short MAC acknowledge. This acknowledge indicates that the transceiver of the receiving device correctly received the message. These are often generated automatically by the transceiver. The ZigBee protocol specifies that all messages must request a MAC acknowledge.
In the APS frame-control field of the first message, there is a bit that indicates whether or not an APS acknowledge is requested. If this bit is set, then the APS layer of the recipient's ZigBee stack will automatically generate an APS acknowledge, as indicated by the third message. This acknowledge indicates that the destination device's stack received the message. The APS acknowledge will generate another MAC acknowledge, as shown by the fourth message.
Looking at the transaction decoding of the first message, we see that the Set with Acknowledge command was used. This is an indication to the application layer that the application layer must acknowledge the command with a Set Response command, as indicated by the fifth message. This acknowledge indicates that the application layer received the message, and the transmitted error code will indicate if any problems occurred when setting the attribute to the requested value. The AF acknowledge will generate another MAC acknowledge, as shown by the sixth message. In addition, the AF acknowledge was sent with an APS acknowledge requested, which will generate the seventh and eighth messages.
These multiple layers of acknowledge generate quite a bit of air traffic, but also allow us to locate problems more easily if there is a break in the message train, as shown by Table 1.
Topology IssuesAfter a wirelessly networked system has been developed, a wireless network analyzer can assist with installation and topology analysis. Some wireless network analyzers,
click to enlarge
Table 1: Determining ZigBee Protocol Root-Cause Problem
Suppose we have a network with four devices: one coordinator, two routers and one FFD end device. Although all devices are full-function devices, we've seen through our packet analysis that messages between the FFD end device and one of the routers are being sent through the other router. If we open the Network Configuration Display window, load a descriptive bitmap, and drag the nodes to the location on the bitmap that describes their physical location, we can quickly see what is happening.
Figure 3 shows the Network Configuration Display window with the network traffic in question. We can see that the two devices are not within radio range of each other, most likely due to the walls within the building. The messages must be routed through another device to reach their destination. So, while the behavior might have originally been worrisome, we can now see that the system is behaving exactly as it should.
Note that a single sniffer may not be able to see all of the nodes on the network. In order to observe all network traffic, it may be necessary to obtain multiple message captures from different locations, or use multiple sniffers positioned in different locations.
ConclusionThe ZigBee protocol is simpler than many wireless protocols, but the right tools are still required to develop applications efficiently and effectively. From confirming that the correct data values are being sent, to understanding network behavior, a wireless network analyzer is an essential tool for anyone doing wireless network development.
About the Author
Kim Otten is a principal applications engineer for the Advanced Microcontroller Architecture Division of Microchip Technology Inc., 2355 W. Chandler Blvd., Chandler, AZ; (888) 628-6247.