Demystifying ZigBee and its Application
Wireless networks are becoming more ubiquitous and are implemented using a variety of protocols specifically designed for radio frequency systems. Some protocols that are in use are proprietary to individual vendors while others are industry standards, requiring varied amounts of system integration. There are differences between IEEE 802.15.4 and ZigBee, including....
Wireless networks are becoming more ubiquitous and are implemented using a variety of protocols specifically designed for radio frequency systems. Some protocols that are in use are proprietary to individual vendors while others are industry standards.
ONLINE Extra: link to more than 30 wireless resources, below.
Recently, a lot of attention has been given to 802.15.4 and ZigBee, but there is still some ambiguity as to what is different about them and what kind of networks or systems would benefit from these particular protocols.
What is IEEE 802.15.4?
IEEE 802.15.4 is a standard for wireless communication established by the Institute for Electrical and Electronics Engineers (IEEE). A few examples of wireless IEEE standards include the 802.11 standard which defines communication for wireless local area networks (LANs) and 802.16 that is used for broadband wireless communication in Metropolitan Area Networks.
At 2.4 GHz, communication occurs in one of sixteen 5 MHz channels ranging from 2.405 to 2.480 GHz.
This standard is designed specifically for communications in a point-to-point or a point-to-multipoint configuration with sleeping and security also being integral parts of the standard. A typical application involves a central coordinator that often acts as a data collector, with multiple remote nodes connecting back to this central host. While both 802.11 and 802.16 standards are concerned with higher bandwidth Internet access applications, 802.15.4 was developed with a lower data rate, simple connectivity, and battery-powered applications in mind. The 802.15.4 standard specifies that communication can occur in the 868.0-868.8 MHz, the 902-928 MHz or the 2.400-2.4835 GHz industrial scientific and medical (ISM) bands. The 868 MHz and 902 MHz bands offer the least amount of bandwidth under the specification, with 20 kHz and 40 kHz available, respectively, for each channel. While any of these bands can technically be used by 802.15.4 devices, the 2.4 GHz band seems to be most popular because it allows for data rates up to 250 kHz and this frequency is allowed by most countries worldwide for data communications. The 868 MHz band is specified primarily for European use, whereas the 902-928 MHz band can only be used in the United States, Canada, and a few other countries and territories that accept the FCC regulations.
The standard requires the use of direct sequence spread spectrum (DSSS) encoding, and offset quadrature phase shift keying (O-QPSK) modulation with half-sine pulse shaping in the 902-928 MHz band.
A typical IEEE 802.15.4 application involves a central coordinator that often acts as a data collector, with multiple remote nodes connecting back to this central host.
At 2.4 GHz, communication occurs in one of sixteen 5 MHz channels ranging from 2.405 to 2.480 GHz, with a maximum over-the-air data rate of 250 kbps and an address space of 65,535 nodes per every 802.15.4 personal area network (PAN).
The possible selection of one of 16 channels helps avoid interference with other 2.4 GHz networks that may be in the same area. Protocol overhead limits theoretical maximum throughput rate to speeds closer to 125 kHz, and only approximately 2 MHz of the channel is consumed with the specified 5 MHz occupied bandwidth.
If communication in a particular network is infrequent enough, there is no reason that a single PAN cannot support all 65,535 nodes. In many cases, the amount of data being sent and the frequency of those data required by the system end up limiting the number of nodes that can be supported below the maximum.
In essence, 802.15.4 defines PHY and MAC layers that are ideal for low-data rate, low-power applications.
What is ZigBee?
ZigBee is a protocol that uses the IEEE 802.15.4 standard as a baseline and adds an additional network layer to give the system routing and networking functionality. Since the ZigBee protocol uses the 802.15.4 standard to define the PHY and MAC layers, the frequency, signal bandwidth, and modulation techniques are identical.
The ZigBee protocol was developed by the ZigBee Alliance to allow companies to cooperate in developing a mesh network protocol that can be used in a variety of commercial and industrial low-data-rate applications. Mesh networking is useful in applications where the range between two points may be beyond the range of the two radios located at those points, but intermediate radios are in place that could forward any messages between them.
To transmit data from poing A to point B when the distance is too great for a single jump, the message could be transmitted through point C to reach the destination.
The ZigBee protocol is designed so that if a number of different radios were deployed in a given area, the radios would automatically form a network without user intervention. The ZigBee protocol within the radios will take care of retries, acknowledgements, and data message routing.
ZigBee also has the ability to self-heal the network. For example, if the radio at node C (intermediate between nodes A and B) was removed for some reason, a new path would be used to route messages from A to B.
The real advantages of mesh networks are that they improve data reliability by providing multiple redundant paths in areas where a lot of nodes are deployed. They are not designed, however, for every application. It takes time for paths to form and devices to associate. Additional system delays occur as messages must be forwarded on through the network. The 250 kHz of over-the-air bandwidth gets used up very quickly with overhead—making video, audio, and other high bandwidth applications are poor choices for mesh networks.
ZigBee devices can either be used as end devices, routers or coordinators. Routers can also be used as end devices, but the main difference is that end devices are allowed to “sleep” (modules and chipsets used to implement ZigBee have sleep currents down to a few microamps, so battery life can extend beyond several years).
Because ZigBee was designed for low-power applications, it fits well into systems that use small, low-power microcontrollers, and applications where reliability, battery life, and versatility are important but high bandwidth is not.
Some examples include networks for home automation, industrial monitoring, and control; pressure, temperature, moisture, and humidity sensors; commercial and industrial meter reading; home fitness machines, and water quality oxygen content monitoring.
ZigBee devices’ lower data rate allows better sensitivity and range, making IEEE 802.15.4 and ZigBee one of the longer range technologies that exist at 2.4 GHz. The comparison graphic illustrates the similarities between IEEE 802.15.4 and other popular wireless technologies.
Making the decision
Bandwidth, battery requirements, code space, frequency, and range are all factors that should be considered if designing a wireless version of a product is on your company’s roadmap.
If the application strictly needs to communicate in a point-to-point or a point-to-multipoint fashion, 802.15.4 can handle all the communications, and will be simpler to implement than a module or chipset with ZigBee firmware. ZigBee is necessary if you need to use repeating, mesh networking functionality in your system, or if you require the added robustness of a mesh network.
In any case, these protocols might be useful in any application where battery operation is required.
ZigBee & 802.15.4
Monitoring and Control
Wide area voice and data
up to 128k
Typical Range (meters)
Low power, Cost
Wireless Communications for Industry
Industrial Wireless Implementation Guide (With links to more than 30 wireless resources)
John Schwartz is technology strategist for Digi International. For more information, please visit
Case Study Database
Get more exposure for your case study by uploading it to the Plant Engineering case study database, where end-users can identify relevant solutions and explore what the experts are doing to effectively implement a variety of technology and productivity related projects.
These case studies provide examples of how knowledgeable solution providers have used technology, processes and people to create effective and successful implementations in real-world situations. Case studies can be completed by filling out a simple online form where you can outline the project title, abstract, and full story in 1500 words or less; upload photos, videos and a logo.
Click here to visit the Case Study Database and upload your case study.
2012 Salary Survey
In a year when manufacturing continued to lead the economic rebound, it makes sense that plant manager bonuses rebounded. Plant Engineering’s annual Salary Survey shows both wages and bonuses rose in 2012 after a retreat the year before.
Average salary across all job titles for plant floor management rose 3.5% to $95,446, and bonus compensation jumped to $15,162, a 4.2% increase from the 2010 level and double the 2011 total, which showed a sharp drop in bonus.