Digi Connect Release Notes Part Number 93000608_K For Digi Connect Firmware Version 2.8.2.6 Release K September 22, 2008 INTRODUCTION This is a production release of firmware for a limited group of the Digi Connect family of wired and wireless products. The Digi Connect embedded and stand-alone device servers allow you to add web-enabled networking using a variety of connectivity options. The Digi Connect device servers provide powerful "plug-and-play", customizable and future-safe features, and performance in one of the smallest solutions available. SUPPORTED PRODUCTS 82000908_K Digi Connect SP Digi Connect SP RS232 Digi Connect SP 2-port MEI Digi Connect SP 2-port RS232 82000977_K Digi Connect Wi-ME Digi Connect Wi-ME CLI 82000983_K Digi Connect Wi-EM 82001116_K Digi Connect ME (2 MB) Digi Connect ME (2 MB) CLI 82001118_K Digi Connect EM 82001120_K Digi Connect ME 4 Digi Connect ME CLI Digi Connect N2S-170 82001220_K Digi Connect Wi-SP Digi Connect Wi-SP 2-port MEI Digi Connect Wi-SP 2-port RS232 82001607_K Digi Connect ME-9210 (4 MB) KNOWN ISSUES With encryption set to AES on a wireless device, serial throughput will be lower than usual. The unit must be power cycled for new port sharing settings to take affect. It is not currently possible to configure the escape characters used by client applications (connect, telnet, and rlogin). If the standard web service (HTTP) is disabled, the encrypted web service (HTTPS) stops operating. They will be made independently selectable in a future release. When attempting to upgrade the firmware on a unit which has password authentication enabled, the initial release of the firmware would fail. This current release includes a workaround to this behavior by allowing the user to disable passwords during the time period of the firmware upgrade. In order to clear the persistent configuration storage from the CLI one can execute the "boot action=factory" command. The only web accessible method for clearing the storage is available via the reset functionality in the administrative pages at "admin/factory_defaults.htm". When attempting to replace files in the file system, simply overwrite the existing version of the file rather than deleting the file first. Attempting to delete the file first defeats the internal file versioning maintained by the firmware, and can confuse your browser's cache. For the most consistent experience with the user interface, it is suggested that you clear your Internet cache. Microsoft Internet Explorer 6 Service Pack 1 (SP1) has a known problem where it displays the error message "Internet Explorer Cannot Open" when you use an HTTPS URL to access this Digi product. The following Microsoft article explains the problem: http://support.microsoft.com/default.aspx?kbid=812935 Digi devices do not support SSL renegotiation. This can cause problems with some Open SSL applications that do not correctly handle this situation. To work around this problem, use the "openssl -quiet" option. There is no IPV6 support for IA (Industrial Automation) or Modem Emulation. TFTP using IPv6 addresses is not supported. Backup using IPv6 addresses is supported using the Web UI but not CLI. Downgrading a unit from an IPv6-enabled EOS to an IPv4-only EOS will result in the loss of some IP address settings. To insure that settings are not lost in this situation, a user is advised to do a back-up of their device prior to upgrading it to an IPv6-enabled EOS. If, after upgrading, a user wishes to go back to an IPv4-only EOS, they should: o Upload the IPv4-only EOS to the device o Revert the device to factory defaults o Resore the device using the saved backup configuration The Me 4 does not have an IPv4-only EOS release. For the Wi-ME, the IPv4-only releases are Release H and earlier. The IPv6-enabled releases are Release H1 and later. The IA route option "set ia route connect={active|passive}" is not supported in this release. Contrary to what is stated in the Command Reference manual, connect cannot be set to active. Setting the Serial Profile to Industrial Automation only works smoothly if you have NOT set IA parameters manually by Telnet or command line. Use one method only - either Web UI or Telnet. CONNECTING TO THE WIRELESS DEVICE The device can only be configured over the wireless link with an access point. In order to establish a wireless link the access point must have authentication and encryption disabled. Furthermore to ensure that the Connect wireless device establishes a link with the correct access point the access point should use the SSID of "Connect". By factory default our device scans through each wireless channel and generates a list of access points. It then associates with the access point with the strongest signal strength. However it will choose to associate with an access point with SSID of "Connect" over another access point that has a different SSID regardless of which access point has the stronger signal strength. When the device successfully associates with an access point its link LED will go solid. RESETTING THE UNIT Digi Connect device server firmware has an enhanced ability to be both soft reset as well as reset to its factory defaults. Both functions may be invoked on the ME and the Wi-ME via manipulation of pin 20 on the module's header: * If the module is running (i.e. more than a few seconds after power on), holding pin 20 low for a second and then raising it will soft reset the unit * If pin 20 is held low for more than 10 seconds from the power on or release from hard reset of the unit, and then raised, it will reset the unit to its factory default state For all devices, the action takes effect when reset is released. ADDITIONAL INFORMATION On initial boot of this device, it will generate encryption key material: an RSA key for SSL/TLS operations, and a DSA key for SSH operations. 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. USING MODBUS BRIDGE This image includes a Modbus protocol bridge. Modbus is one of the most common "third party" interfaces for industrial equipment. The full protocol specification can be found at www.modbus.org The Modbus Bridge functionality enables Masters and Slave to communicate using any combination of the 3 official dialects: - Modbus/TCP transported by TCP/IP or UDP/IP - Modbus/RTU transported by serial, TCP/IP, or UDP/IP - Modbus/ASCII transported by serial, TCP/IP, or UDP/IP One-serial port bridges are defined by the role of the attached serial device. Selecting the "Industrial Automation" serial port profile enable you to define either: 1) Serial Modbus master accessing remote IP-based Modbus slaves 2) Remote Modbus masters sharing a serial Modbus slave(s). See Digi Support Document 90000638 for more details on various ways to setup and use a Modbus Protocol Bridge: http://ftp1.digi.com/support/documentation/90000638_a.pdf See Digi Support Document 90000649 for more details on how the message queuing and processing works within a Modbus Bridge: http://ftp1.digi.com/support/documentation/90000649_a.pdf