Specifications
©2009DigiInternational,Inc. 125
AppendixC:Migrating fromXBeeZBtoXBee
SE
The following list includes the significant differences in XBee SE compared to XBee ZB.
• API coordinator, router, and end device targets are supported, AT/Transparent targets are
not.
• Routers and end devices will perform key establishment after joining (if enabled with EO com-
mand). (ZB firmware does not support key establishment.)
• New AI codes in SE firmware indicate the progress of key establishment.
• Fragmentation in SE supports up to 128 byte payloads. (ZB supports up to 255 byte pay-
loads.)
• The coordinator and routers can have up to 6 end device children each, compared with 10 -
12 in ZB firmware.
• Routers and end devices perform up to 3 joining attempts. Joining attempts may be triggered
by a button press, reset, or AT command (CB). (In ZB firmware, the XBee regularly attempts
joining until successful.)
• Permit joining cannot be permanently enabled in SE firmware. Joining can be temporarily
enabled by a button press, changing the NJ value, or AT command (CB).
• The explicit transmit and receive frames are required (0x11 and 0x91). ZigBee transmit and
receive API frames (used in ZB) are not supported (0x10 and 0x90) in SE firmware.
The following ZB features are not supported in SE:
• IO sampling (IR, IS, IC)
• Analog and digital IO configuration (D1, D2, D3, D4, D5, D6, P0, P1, P2, RP, PR)
• Network discovery and diagnostics commands (NI, ND, DN, NR1, NW, JV)
• Remote AT commands (0x17 and 0x97 API frames)
• Loopback cluster ID
• Over-the-air firmware updates
• Some AT commands have been made read only (such as ZS and EE), and others have limited
parameter ranges. See the command table for details.
Manufacturers of end products that use SE firmware must do the following (see Appendix D):
• Be members of the ZigBee Alliance
• Obtain certificates for the product
• Certify the end product with a ZigBee test lab.