User's Manual

XBee®/XBee‐PRO®ZBRFModules
©2009DigiInternational,Inc. 26
Routers and end devices are typically configured to join a network with any 16-bit PAN ID as long
as the 64-bit PAN ID is valid. Coordinators typically select a random 16-bit PAN ID for their
network.
Since the 16-bit PAN ID only allows up to 65,535 unique values, and since the 16-bit PAN ID is
randomly selected, provisions exist in ZigBee to detect if two networks (with different 64-bit PAN
IDs) are operating on the same 16-bit PAN ID. If such a conflict is detected, the ZigBee stack can
perform PAN ID conflict resolution to change the 16-bit PAN ID of the network in order to resolve
the conflict. See the ZigBee specification for details.
To summarize, ZigBee routers and end devices should be configured with the 64-bit PAN ID of the
network they want to join. They typically acquire the 16-bit PAN ID when they join a network.
Operating Channel
ZigBee utilizes direct-sequence spread spectrum modulation and operates on a fixed channel. The
802.15.4 PHY defines 16 operating channels in the 2.4 GHz frequency band. XBee modules
support all 16 channels and XBee-PRO modules support 14 of the 16 channels.
ZigBee Application Layers: In Depth
This section provides a more in-depth look at the ZigBee application stack layers (APS, ZDO)
including a discussion on ZigBee endpoints, clusters, and profiles. Much of the material in this
section can introduce unnecessary details of the ZigBee stack that are not required in many cases.
Skip this section if
• The XBee does not need to interoperate or talk to non-Digi ZigBee devices
• The XBee simply needs to send data between devices.
Read this section if
• The XBee may talk to non-Digi ZigBee devices
• The XBee requires network management and discovery capabilities of the ZDO layer
• The XBee needs to operate in a public application profile (smart energy, home automation,
etc.)
Application Support Sublayer (APS)
The APS layer in ZigBee adds support for application profiles, cluster IDs, and endpoints.
Application Profiles
Application profiles specify various device descriptions including required functionality for various
devices. The collection of device descriptions forms an application profile. Application profiles can
be defined as "Public" or "Private" profiles. Private profiles are defined by a manufacturer whereas
public profiles are defined, developed, and maintained by the ZigBee Alliance. Each application
profile has a unique profile identifier assigned by the ZigBee Alliance.
Examples of public profiles include:
• Home Automation
• Smart Energy
• Commercial Building Automation
The Smart Energy profile, for example, defines various device types including an energy service
portal, load controller, thermostat, in-home display, etc. The Smart Energy profile defines required
functionality for each device type. For example, a load controller must respond to a defined
command to turn a load on or off. By defining standard communication protocols and device
functionality, public profiles allow interoperable ZigBee solutions to be developed by independent
manufacturers.
Digi XBee ZB firmware operates on a private profile called the Digi Drop-In Networking profile.
However, the API firmware in the module can be used in many cases to talk to devices in public
profiles or non-Digi private profiles. See the API Operations chapter for details.