================================================================================ Release Notes PN 93009414 XBee 865/868LP Version 8074 ================================================================================ INTRODUCTION These release notes document changes made to the 80kbps firmware on the XBee 865/868LP radios. ENHANCEMENTS - None, but major performance enhancements, especially with sleeping routers BUG FIXES - Synchronized sleeping router nodes were locking up due to buffer depletions The serial port wouldn't accept input. - Sleep synchronization messages were not prioritized over data packets. - With route discoveries disabled, routes were being deleted. This should not happen because the whole point is to use previously learned routes. - MISO pin would not go high when configured as an output high - SPI interface was not functional - ED command issued in API mode was returning transparent data - RO setting of 0 would not allow transmissions to occur in transparent mode - Associate LED was not blinking at the right interval. Now, it only blinks in sleeping router mode. - Serial port was locking up when receiving data in API mode 2 at a high rate with CTS flow control ignored or not used. - Buffer resource efficiency was improved to only use the buffer size needed for a given transmission in API mode. This increases module data capacity - ATCB1 issued to a remote node was causing a watchdog reset - Fixed remote IS and ED commands when sent with a frame ID of 0 - Test Link response contained some invalid fields KNOWN LIMITATIONS - The serial port is non-responsive for approximately 70ms after a baud rate (ATBR) change is applied either by the ATAC command or by exiting command mode. To work around this issue the user should insert a 100ms delay after applying a baud rate change. HISTORY Version 8072 Version 8059 (Initial Release) KNOWN LIMITATIONS - Setting the ATIR parameter to sample faster than the module can transmit the samples will cause the module to not sleep when using ATSM4. - When sending a directed broadcast (0x80 on tx option), the transmit status frame will always indicate that a route discovery has taken place, (discovery status byte = 0x02).