Release Notes PN 93000689_A1

                   ConnectPort X2 for Smart Energy

                           82002458_A1 EOS

                          February 23, 2011


INTRODUCTION

    This is a specialized production release of firmware for Digi's
    ConnectPort X2 gateway.  This image provides a platform for
    execution of Digi applications implementing Zigbee Smart Energy
    devices.

    This firmware is intended solely for Digi Smart Energy devices.
    For more details, visit the Digi Support website.

SUPPORTED PRODUCTS

    ConnectPort X2 Ethernet

ENHANCEMENTS

    Enable the telnet client command in the command-line interface (CLI).

    Enable "file hashing" via RCI to help with file version verification.
    This extends the file system "ls" command in RCI to request that a hash
    value be returned for files in the listing. The supported hash methods
    are "none" (the default) and "crc32".

BUG FIXES

    Fix a bug that caused XBee early request timeout and retries resulting
    from a race condition. (37735)

    Fix a bug that may result in a memory leak when a fully qualified domain
    name (FQDN) is configured for a SNTP Server as a time source in the
    Date and Time Settings. (37807)

KNOWN ISSUES

    The Web User Interface (WebUI) is removed with this firmware.
    Configuration must be performed from the Command Line Interface (CLI)
    or the iDigi Platform instead.

    Although multiple SNTP Server entries may be configured as time sources in
    the Date and Time Settings, it is recommended that only one is configured.

DOCUMENTATION ERRATA

    None.

ADDITIONAL INFORMATION

    On initial boot of this device, it will generate some encryption key
    material. This process can take as long as 40 minutes to complete.
    Until the corresponding key is generated, the device will be unable to
    initiate or accept that type of encrypted connection.  It will also
    report itself as 100% busy, but, since key generation takes place at a
    low priority, the device will still function normally.  On subsequent
    reboots, the device will use its existing keys and will not need to
    generate another unless a reset to factory defaults is done, which will
    cause a new key to be generated on the next reboot.

HISTORY

  82002458_A1 (2.10.0.3) - February 23, 2011

    See ENHANCEMENTS and BUG FIXES information above.

  82002458_A (2.10.0.3) - May 25, 2010

    Initial release.