XBee/XBee-PRO Series 1 ZigBee Module Firmware Revision History

ZigBee firmware revision history for the XBee/XBee-PRO radio modems.

10/25/2007 - MaxStream/Digi is canceling the ZigBee Beta firmware offering for our XBee/XBee-PRO Series 1 modules. Due to some necessary hardware changes we unfortunately will not be able to support the ZigBee Beta firmware on our XBee/XBee-PRO Series 1 modules moving forward. This includes firmware versions 8x13, 8x14 and 8x17.

The latest hardware revision of XBee Series 1 modules is incompatible with and will not load the ZigBee beta firmware. This latest hardware revision is labeled "Rev-B" on the white sticker on each XBee module, and is currently shipping. XBee-PRO modules will have the same hardware change in the next few months. Older hardware versions will load the ZigBee beta firmware, but support from our Support and Engineering departments will diminish. We have no plans to officially release the ZigBee beta firmware.

Please know that we have long-term plans to continue to offer the XBee/XBee-PRO Series 1 modules. The successful 802.15.4 firmware versions (1x8x, 1xAx, 1xCx) will still be available for reliable, wireless peer-to-peer, point-to-point and point-to-multipoint applications. We are only ending the XBee Series 1 ZigBee beta firmware offering.

We also offer code development directly on the XBee Series 1 modules. This option allows customers the option of using MaxStream/Digis XBee hardware while developing their own software based on Freescales SMAC, 802.15.4, or BeeStack (ZigBee 2006) software stacks.

Customers interested in mesh networking applications without code development are encouraged to develop with our XBee Series 2 modules, which feature low-power end devices, ADC and Digital I/O, and encryption. The XBee Series 2 ZigBee module is based on the same software API and hardware design as the XBee Series 1, so migration from Series 1 to Series 2 should be simple.

Please feel free to contact us with any questions or comments.

XBee ZigBee Module Firmware Versions

XBee version numbers will have 4 significant digits. A version number is reported by ATVR with 3 or 4 numbers. All numbers are hexadecimal and can have a range from 0-0xF. A version can be reported as "ABC" or "ABCD". Digits ABC are the main release number and D is the revision number from the main release. "B" is a variant designator. The following variants exist:

  • "0" - ZigBee Coordinator Code, AT Command Mode (AP=0)
  • "1" - ZigBee Coordinator Code, API Mode (AP=1,2)
  • "2" - ZigBee Router Code, AT Command Mode (AP=0)
  • "3" - ZigBee Router Code, API Mode (AP=1,2)
  • "4" - ZigBee End Device Code, AT Command Mode (AP=0)
  • "5" - ZigBee End Device Code, API Mode (AP=1,2)

All releases will have an even number for C. All internal development will have an odd number for C. Field D is always present, even when D is 0.

ZigBee firmware releases will start with 0x8000, and the 802.15.4 firmware releases started with 0x1000. Information regarding the 802.15.4 firmware can be seen here.

Table of Contents

Version 8.x.1.7
Version 8.x.1.4
Version 8.x.1.3




Beta ZigBee firmware versions are available for limited release only. To request firmware for Beta testing, please contact MaxStream support at support@maxstream.net.

Version 8.x.1.7


  • Firmware version 8x17 (beta) is incompatible with beta version 8x14.
  • Fixed rare problem where WR would not save command values correctly.
  • Broadcast data transmissions are given 4 seconds to propagate through the network.
  • MP commands added to Router firmware.
  • When a router joins a PAN, it saves the join information to non-volatile memory immediately.
  • DN response returns network address, then 64-bit address to follow the same order as the ND command response format.
  • DN response in API firmware versions returns the network address and 64-bit address of the remote in a single API frame, instead of returning an API response frame for each address.
  • API ZigBee Transmit Request ID value changed from 0x02 to 0x10.
  • API ZigBee Receive Packet ID value changed from 0x82 to 0x90.
  • API ZigBee Transmit Request frame includes a new broadcast radius field to specify the maximum radius the broadcast should travel.
  • AT firmware includes a new BH command to set the broadcast radius

Version 8.x.1.4


  • This release is incompatible with the v8x13 Beta
  • Added - Support Coordinator Network Address 0x0000 - Set DH & DL=0 on module to transmit to Coordinator.
  • Added - Default DH=0, Default DL=0xFFFF(Coordinator), DL=0x0000(Router).
  • Added - NJ time measured in seconds, range 0 - 0x40, 0xFF-always allow joining.
  • Added - Serial Parity support (NB).
  • Fix - ZigBee Tx Status API, Status values changed from 21-26 (decimal) to 0x21-0x26 (hex)
  • Fix - CTS de-asserts when 17 bytes space left (not 7), reasserts when at least 34 bytes left (not 24).
  • Fix - Stack Profile changed from Home Controls Stack profile (0x01) to Network Specific Stack profile (0x00).
  • Fix - Expanded Route Table size=34, & Network Address Table size=14.

Version 8.x.1.3


  • Use extended addressing to address nodes.
  • Use NI String to address nodes (DN and ND commands).
  • Router supports DN command.
  • API Support (Modem Status, ZigBee-TX Status, TX-ZigBee, RX-ZigBee, AT Commands).
  • Removed ATDB command, RSSI removed from ND Command and RX-ZigBee frames.
  • Fix- If ID=0xFFFF, it will join to a Coordinator. The ID value is updated, but not stored to Non-Volatile until a node joins to that node, or if the user issues WR. When we join, check if ID=0xFFFF -if so, write new ID to Non-Volitile when join succeeds.


Released ZigBee firmware versions are available from the X-CTU program for general download. To download released versions:

  1. Go to the ''''Modem Configuration'''' page in X-CTU.
  2. Click on ''''Download New Versions'''' and select ''''Web''''.
  3. You may need to disable your firewall in order to download new versions.
There are no production release versions at this time. 
Last updated: Aug 08, 2017

Recently Viewed

No recently viewed articles

Did you find this article helpful?