XBee®/XBee‐PRO® ZB SMT RF Modules
In the above example, the Frame Control field (offset 23) was constructed as follows:
Name
Frame Type
Bits Example Value Description
0-1
2
00 - Command acts across the entire profile
Manufacturer Specific
Direction
0 - The manufacturer code field is omitted from the ZCL Frame Header.
0 - The command is being sent from the client side to the server side.
0 - Default response not disabled
3
Disable Default Response
Reserved
4
5-7
Set to 0.
See the ZigBee Cluster Library specification for details.
Sending Public Profile Commands with the API
Commands in public profiles such as Smart Energy and Home Automation can be sent with the XBee API using the
Explicit Transmit API frame (0x11). Sending public profile commands with the Explicit Transmit API frame requires
some formatting of the data payload field. Most of the public profile commands fit into the ZigBee Cluster Library
(ZCL) architecture as described in the previous section.
The following table shows how the Explicit API frame can be used to send a demand response and load control
message (cluster ID 0x701) in the smart energy profile (profile ID 0x0109) in the revision 14 Smart Energy
specification. The message will be a "Load Control Event" (command ID 0x00) and will be sent to a device with 64-
bit address of 0x0013A200 40401234 with a 16-bit address of 0x5678. The event will start a load control event for
water heaters and smart appliances, for a duration of 1 minute, starting immediately.
Note: When sending public profile commands, the AO command should be set to 1 to enable the explicit receive API
frame. This will provide indication of the source 64- and 16-bit addresses, cluster ID, profile ID, and endpoint
information for each received packet. This information is required to properly decode received data.
© 2010 Digi International, Inc.
123