Guidelines for Creating ZigBee Applications

Guidelines for Creating ZigBee Applications

So you've decided to create a ZigBee application, but you have some questions. What is critical in ZigBee development? What equipment do I require? What are the steps involved? How long will it take? What type of investment is needed? What are the unanticipated questions?

The advice offered here will not be able to address all of these questions for everyone, but it will serve as a guide for developing your ZigBee application.

The first, and maybe most crucial, step in building your application is determining if ZigBee is suitable for your device. The ZigBee radio standard has several benefits over other wireless technologies. Interoperability with other vendor devices is ensured through a public ZigBee profile and conformant platform. ZigBee was designed to have exceptionally low power consumption and relatively extended battery life. However, ZigBee data speeds are modest in comparison to other wireless solutions. While the ZigBee stack is far smaller than Bluetooth or 802.11/WiFi, it is not a simple piece of software. HTML5 Training Course is easily avaialble in Delhi for example you can go TGC India for that: https://www.tgcindia.com/course/html-5-course-in-delhi/

After selecting to create a ZigBee application, you must choose a ZigBee provider partner. The ZigBee stack software, as well as a radio chip and baseband microcontroller, will be provided by a ZigBee partner. Traditionally, they were two-chip solutions. However, suppliers have recently introduced single-chip ZigBee devices with a plethora of extra resources to enable your application code. A good ZigBee partner will also keep you up to current on the most latest features.

There are many ZigBee suppliers available, and each has spent many person-years developing their ZigBee solution. When selecting a partner, evaluate both technical (cost vs. capacity of their chipset, supported features) and commercial elements of the supplier (company history, licensing costs, technical support). The ZigBee suppliers will also want to know information about you, such as prior product development expertise and the number of devices you want to sell. When this information exchange is complete, you should be able to discover a ZigBee supplier eager to work on your application rather fast.

After selecting a ZigBee provider, you must decide whether to deploy the ZigBee radio as a module attached to the rest of the system or as a chip incorporated into your board's circuitry.

Using a ZigBee radio module has several benefits. A module often results in a quicker development cycle. You don't need to become an RF specialist since the RF design is already done for you. Furthermore, a module may be FCC Modular Approved, which means you won't have to go through the FCC's intentional radiator approval procedure.

One disadvantage of employing a ZigBee radio module rather than an integrated ZigBee chip is that the per-unit product cost is greater. A module design also necessitates more physical space inside the housing and places additional constraints on the product's industrial design. Furthermore, a module's antenna choices may be restricted, making it inappropriate for your product.

The last architectural step is to properly specify the structure of your ZigBee network. You may choose from a variety of topologies supported by the ZigBee standard. Mesh, star, and cluster tree network configurations are examples, as shown in Figure 1.

The standard ZigBee network design is made up of low-power, low-function endpoint devices known as sensors. The sensors connect with full-function network control devices, which manage packet routing throughout the network.

ZigBee radios may operate in a variety of RF bands. Those operating in the 2.4 - 2.48 GHz frequency are the most widespread since it is the only RF spectrum that may be used globally. In North America, 915 MHz is available for ZigBee radios, which has a few benefits over 2.4 GHz, including a significantly greater range. Because antennas are bigger and the over-the-air data throughput is lower, there are fewer chip suppliers that provide the lower frequency range. The ZigBee 868 MHz version also has useful capabilities, however, it is only accessible in Europe.

Now that you've finalized all of your architectural selections, it's time to access the development system given by your ZigBee partner and get started. Figure 2 depicts one example. The development system will provide an example application code for you to use. Because you will utilize the same Program Programming Interface (API) as the example, your finished application will most likely resemble it. It is also possible to utilize the same operating system, system calls, and interrupts. API calls such as "FormNetwork()," "JoinNetwork()," "SendMessage()," and "ZigBeeStackTick()" are common. Learn to love this API; you'll be using it for the next several months.

You will confront several design issues throughout the development period. Many will be standard embedded development difficulties, while others will come as a result of the addition of a new design element - the ZigBee stack.

ZigBee claims ultra-low power consumption. This is fantastic for the radio, but you must extend it to cover your full system architecture. To completely optimize power use and battery life, the firmware, electrical, and RF teams must commit significant attention to power consumption optimization. Microcontroller sleep modes must be specified and implemented as part of this endeavor. Be careful that when the machine is in sleep mode, your development system may not function correctly. Debug methods such as "GPIO toggling and scope tracing" may be required.

If your system will be powered by batteries, keep in mind that ZigBee radios do not violate physical laws. ZigBee radios utilize the current necessary to transmit at the chosen power level, which is often in the 20-50 mA range. The use situation has a big impact on achieving multi-year battery life. Pay close attention to how often the radio has to be awakened, how long it takes to awaken, and how much current it uses while sleeping. You may discover that the data sheets provided by a ZigBee provider are only useful to a limited extent in this area, and you will have to make your measurements of current consumption.

In general, the main tradeoff you must make is between data latency and battery life. It may seem contradictory, but since ZigBee transmissions are at low RF strength - in the milliwatt region - battery power utilization during transmit and receive modes is comparable. Don't assume that since a radio mode is mostly in receive mode, it will require minimal power.

Your first ZigBee development system will most likely not match your final hardware. This implies you'll be creating new interfaces for your gadgets, such as buttons, displays, memory, and so on. A communication connection to another system, such as a system monitor PC software, may also be required. This is when taking the time to completely grasp the API and the beginning point of your development system comes in handy since you will need to integrate these new interfaces with the rest of the current design. For angular js course in delhi related information visit here: https://www.tgcindia.com/course/adv-certification-in-angularjs-for-web-design/

To ensure your device's compatibility, you may need to swallow your pride and buy a competitor's product. Using another ZigBee-approved system during development may assist you in determining how to best improve the performance of your product. Another way to evaluate compatibility is to attend one of the ZigBee Alliance's quarterly interoperability events, known as ZigFests. To participate in a ZigFest, your firm must be a ZigBee Alliance Adopter class member. There are additional certification businesses that may offer a testing environment for pre-certification.

Remember that, unlike Bluetooth, the ZigBee radio is not a frequency hopper. The network coordinator searches the available channels to select the "clearest" one before forming the network. This automated frequency selection capability is normally included with the ZigBee stack you buy, but it is simple to construct if it is not. The network coordinator may then be designed to test the network regularly to see whether the chosen frequency is still the best choice. If this is not the case, the network coordinator may direct the network to a different channel without requiring operator participation. This ensures that the network operates at peak efficiency at all times.

If your application requires data security, ZigBee has solutions for effective data encryption. The 128-bit AES method is used to secure ZigBee data. If you use a public ZigBee profile, the security considerations have already been decided and are specified in the profile.

When developing a bespoke application that needs data security, you have two alternatives for implementing the security: in the application code or the lower levels of the ZigBee stack. Secure it in your application code if your application requires the highest level of security. In the lowest tiers of the ZigBee stack, optional security is defined, which may be utilized to check each data packet shared on your ZigBee network.

Your development will very certainly entail the creation of two ends of a system: the sensors, which may be low-function ZigBee end devices, and the devices with which they want to talk. Each system end will provide its own set of design issues. Power optimization is often the most important design challenge for sensors, whereas message handling is the most important for ZigBee routers.

Message handling is a critical component of the application code. Your application code will interact with the ZigBee stack by delivering messages to it through stack functions and receiving messages from it via callback functions. On top of its typical network management chores, the application code will most likely need to monitor these messages and may need to execute actions such as timing messages and discarding "lost" messages.

Include time to create test code as part of the application development planning process. During the integration phase, the test code will assist in identifying and validating the boundary conditions of the feature operations. During hardware compliance testing, specialized test code may be necessary to put the device in perpetual transmit mode. A correctly written test code at the factory can rapidly and completely validate the functionality of each device as it comes down the line.

The ZigBee RF sniffer/protocol analyzer is an essential tool for creating a ZigBee application. Even if your design has a ZigBee radio module and a public ZigBee profile, you will ultimately need to inspect orders as they are sent over the air. Many protocol sniffers are now available, with varying capabilities and prices. The sniffer you choose will be determined by your familiarity with protocol analyzers, the degree of protocol analyzing necessary, future ZigBee work predicted, and the cost of each device. The most reasonable approach is, to begin with, a simple unit and upgrade later if extra capabilities are required.

Time-to-Market

If the system's time-to-market is critical, the usage of a ZigBee radio module is nearly a certainty. The shortest development cycle will be provided via a module-based architecture.

Many projects need a quick time-to-market with a minimal number of devices to launch a new technology or product line. Higher volume manufacturing is often delayed. If this is the case, it may be feasible to develop in two phases: a "rapid" phase employing a ZigBee radio module, followed by a "cost-reduced" integrated design phase. During the cost-cutting phase, functionality from modules is often merged into a single circuit board. A two-phase method also makes sense in terms of time, since knowledge is created with the technology before integrating the radio chip on the circuit board. If you plan ahead of time, you will be able to achieve the best market rollout.

Your ZigBee application, like any other electronic product that is released to the public, must fulfill regulatory criteria. Because a ZigBee device is designed to be a radiator, it must fulfill worldwide standards. You will be responsible as the design owner for submitting the product for compliance testing, modifying the design as required to pass, and filing the final design with the proper agency. Plan for multiple rounds of testing as early in the design process as feasible. This comprises a preliminary screening test for radiated emissions.

Because the majority of ZigBee systems transmit at a low RF power of approximately one milliwatt, the basic RF emissions are unlikely to be a concern. However, emission level restrictions, especially the second and third harmonics that fall within FCC "restricted bands," must be closely monitored. You should also check for less technical compliance issues, such as product labeling regulations and antenna limits.

To market your product as ZigBee compatible, it must undergo ZigBee-approved product testing. Your firm must be a member of the ZigBee Alliance to submit the device for ZigBee testing. Joining the ZigBee Alliance is a low-cost option that should be taken advantage of right away since membership grants access to a wealth of ZigBee-related materials and debates. More information may be found at http://www.zigbee.org.

You will need to create a unique 802.15.4 MAC address for each ZigBee device. The 802.15.4 MAC address is a value of eight bytes (64 bits). The IEEE Standards Association licenses the first three bytes (the Organizationally Unique Identifier or "OUI") to your firm for an annual charge. Your organization is then free to allocate the remaining five bytes uniquely.

Finally, depending on the factory assembly and testing procedure, a software-based manufacturing test that provides the MAC address to put into each device may be useful. In this instance, your application code may be required to provide a non-violate memory write function that would not normally be required.

Conclusion

Although ZigBee is a well-defined and feature-rich radio standard, creating a ZigBee device is not a simple task. Many technical disciplines must collaborate to identify, architect, design, test, and market the finished product. Following the recommendations made in this debate will allow you to create a viable strategy for developing a ZigBee wireless application.