**************************************************************************************
Firmware Version: 2005
Stack version:    20588809 
Release Date: Nov 29, 2012

Initial release of XB2B-WF (S6B) module


Notable Differences from XB24-WF (S6) module:
1. Supports OTA firmware updates.

2. OTA frames to and from 0x0BEE port are not compatible between S6 and S6B.

3. Max transmission frame size is 1392 bytes rather than 1398 bytes on port 0x0BEE.

4. Wakeup time from deep sleep is instantaneous such that frames can be
   sent as soon as the serial port is up rather than waiting for a new
   association to access point.  Also, the module will not output modem status
   messages on each sleep/wake cycle like it did on S6.

5. In associated cyclic sleep mode, the sleep time is determined by SP rather
   than by the DTIM interval.

6. Minimum baud rate is 2400 baud rather than 1200 baud. (BD0 is disabled.)



Known issues:
1. Single byte TCP transmissions are often delayed by about 6 or 7 seconds.
   This is seen when using a keyboard in the terminal window of X-CTU to send
   data between two XBee modules connected to the same access point.

2. Streaming large TCP packets can result in one of these problems:
   a. Partial duplicate packets.  (The full packet will be received followed by
      a portion of the same packet repeated.)
   b. Sometimes the data is dropped for no apparent reason without sending
      the data.  This can happen even though the status reports success.

3. TCP transmission attempts often fail with resource errors due to a lack
   of available TCP sockets.  This is because the XBee module in API mode cannot
   support more than one TCP connection at a time.  (To alleviate this problem,
   it is recommended that the ATTM parameter be configured to be long enough
   to not timeout and close the socket between transmissions.  After a timeout,
   it usually takes ten seconds before a new socket connection can be made
   for the next connection.)

4. Sometimes a TCP socket does not close properly such that all transmissions
   fail with resource errors.  When this condition occurs a watch dog reset is
   forced so that the module can be recovered without manual intervention.

5. AdHoc mode allows association between two modules, but does not allow
   transmissions.