BlueTree Wireless Product Group BlueTree Modems Firmware Release Notes Version 3.8.0 December 18, 2009 Related Products This release applies to the following products: BT‐4200, BT‐5200 BT‐4400, BT‐5400 BT‐4600, BT‐4600A, BT‐5600, BT‐5600A BT‐5600v2, BT‐5800v2 BT‐6401, BT‐6401EB, BT‐6421 BT‐6600, BT‐6601, BT‐6601EB, BT‐6621 BT‐6800, BT‐6801, BT‐6801EB, BT‐6821 Disclaimer: This document is provided for informational purposes only; and does not constitute a binding legal document unless specifically incorporated by reference into a binding legal agreement between you and BlueTree Wireless Data Inc. (BlueTree). In the event that you enter into a binding legal agreement with BlueTree, all provisions contained in such binding legal agreement shall apply; regardless of whether such provisions conflict with information contained herein. BlueTree assumes no responsibility for any typographical, technical or other inaccuracies in this document. BlueTree reserves the right to periodically change information that is contained in this document; however, BlueTree makes no commitment to provide any such changes, updates, enhancements or other additions to this document to you in a timely manner or at all. SOLUTIONS FOR YOUR INDUSTRIAL NETWORKING CHALLENGES BlueTree Wireless Product Group y 2425 46th Avenue y Montréal, Québec H8T 3C9 y Canada +1 514.422.9110 y Fax +1 514.422.3338 y www.bluetreewireless.com BlueTree_FirmwareReleaseNotes_v3.8.0_2009-12-18.doc December 18, 2009 Page 2 of 5 Table of Contents Upgrade Instructions .................................................................................................................................................... 3 Version 3.8.0 – Release Notes – December 18, 2009 ................................................................................................... 3 Dependencies .................................................................................................................................................................... 3 Important Notes ................................................................................................................................................................ 3 New Features & Improvements......................................................................................................................................... 4 Fixed Issues ........................................................................................................................................................................ 4 Known Issues ..................................................................................................................................................................... 5 BlueTree_FirmwareReleaseNotes_v3.8.0_2009-12-18.doc December 18, 2009 Page 3 of 5 Upgrade Instructions Table 1, below, provides a summary of the update procedure to follow depending on the firmware which currently resides in the modem (i.e. is being upgraded from). Model Normal update Advanced update Advanced update required for IPsec support 1 4000 or 5000 (non‐v2) series >= 3.x <= 2.x N/A 6000 or 5000v2 series >= 3.6.0 <= 3.4.9 <= 3.6.1 Table 1 ‐ Upgrade Process Matrix Normal update 1. Use a crossover cable or USB to connect modem and PC 2. Start BlueVue Device Manager and Click "Change connection type" and make sure it is "Modem IP". 3. Type the modem IP address in the related field if needed a. For USB connection, default Modem IP is 192.168.111.1 b. For Ethernet connection default Modem IP is 192.168.0.1 4. After the modem is detected, click File > Configuration and click "Firmware" tab 5. Select the update file you want to use, then click "Upgrade" 6. Wait for the firmware update to end and the modem to restart Advanced update Download the Advanced Update Package from the BlueTree Wireless website and follow the instructions in the “Advanced Firmware Update & Recovery Guide”. Version 3.8.0 – Release Notes – December 18, 2009 Dependencies Kernel Boot Loader File System BT‐4000 / BT‐5000 Series Current Minimum Versions Versions 2.6.15.1bt5 2.6.15.1bt5 1.1.3bt10 1.1.3bt8 3.0.0 2.0.0 BT‐5000v2 / BT‐6000 Series Current Versions 2.6.21 #btw06 1.2.0‐btw04 3.0.0 Minimum Versions 2.6.21 #btw02 2 1.2.0‐btw02 3.0.0 Important Notes Release 3.6.2 added IPsec functionality to the BT‐5000v2 and BT‐6000 series modems. If upgrading from a version prior to 3.6.2, an advanced upgrade is necessary to enable IPsec support. 1 In this case, an advanced upgrade is necessary to gain IPsec support. IPsec functionality is optional, so if IPsec support is not required, a basic upgrade can be performed instead, assuming that the minimum release is met as per the “Advanced update required” column. 2 The “minimum” kernel version of 2.6.21 #btw02 does not support IPsec. If IPsec is required, an advanced upgrade should be performed to upgrade the kernel to 2.6.21 #btw04 or above. BlueTree_FirmwareReleaseNotes_v3.8.0_2009-12-18.doc December 18, 2009 Page 4 of 5 New Features & Improvements ID 674 Subject Firmware upgrade 1014 Events 1015 Events 1017 Events 1018 Events 1019 Events 1027 GPS Description Modem initiated upgrade package download The AT+BWGET can be used to download an upgrade package from an FTP or HTTP site. WAN event added to BEP The WAN event (see AT+BEVENT) can be used to signal when the modem has a WAN IP address and when it changes. Modem Originated Management Destination type 3 (MOM) can now be used to initiate management action from the modem. See AT+BRPRDS/AT+BEVRPR/AT+BEVENT. This feature is meant to operate with BlueVue Group (release 2.1.80) Add new BEP payloads: MI2, MI3, RF2, IP1 Those new message payloads can be used to report status information to a management server. Add new BEP payload: AU1 This new BEP payload can be used authenticate BEP messages. Add new BEP payload: AC1 This new BEP payload can be used to exchange AT commands and responses between a management server (BVG) and the modem. Synchronize modem time on GPS: AT+BGPSDT Fixed Issues ID 1028 1035 1040 1054 1055 Subject Serial IP IPSEC RF FTP DHCP 1056 GPS/Events 1057 1073 1077 1079 1080 RF AT GPS UDP RF Description Modem fails to transfer file via Serial IP AT+BIPSSN? does not display the remote subnet configuration RF diagnostic pass‐through via serial fails The FTP server was failing when enabled multiple times. In IP pass‐through, the DHCP lease time is reduced to 30 seconds until the WAN IP is available and assigned to the local interface. The configured DHCP lease time is then used. GPS/BEP UDP destinations connects/disconnects every 30 seconds This occurred when +BSYNC was used and no ACK messages were received. High latency and lost ping packets AT+BIPINF returns ERROR GPS fix not reported High latency and loss of UDP packets HSPA: MCC reported instead of MNC BlueTree_FirmwareReleaseNotes_v3.8.0_2009-12-18.doc December 18, 2009 Page 5 of 5 Known Issues ID 917 Subject Activation 880 Activation 966 WAN LED Description New modems on Sprint now utilize OMA‐DM instead of IOTA for provisioning, resulting in an error when the AT!IOTASTART command is issued. OMA‐DM can be started with AT!dmdc=2 instead. This change requires BlueVue Device Manager 1.7.9 for automatic activation. A bug in the Sierra Wireless MC5727 module returns ERROR during activation when in fact the activation may have been successful. A workaround is available in BlueVue Device Manager 1.7.9. The WAN LED on BT‐5800v2 and BT‐6800 series may not indicate the connection status when the RF Transmit has been disabled and then re‐enabled using AT+BRFPON. This issue only exists with RF module firmware: K1_0_2_8AP.