---------------------- New in application firmware 4.14.011 for both WiFi and Ethernet 2011/03/19 Summary: Added reset to defaults for web user, password, and port with the "Service App" button on bootup. Changed the reset IP address/port to defaults to be only the "Service Router" button on bootup. Holding both "Service Router" and "Service App" buttons on bootup resets both the IP address/port and the web user/password/port. Recommendations: Install this update if desire the new functionality for resetting web user/password/port to defaults Detailed Changes An earlier version of the reset to defaults reset all information to factory defaults by clearing the flash configuration, but took a long time. This was made quicker by only resetting the IP information but lost the ability to reset the web information. This update restores the ability to reset either or both the IP and web information without adding additional delay. Outstanding Issues: i.Lon Config Server (ILCS) bug. When using the ILCS where both GRouter4's and i.LON 600's are on the same channel, and there are more than two or three GR4 devices before the i.LON 600's in the channel list, the ILCS will time out waiting for the i.LON 600 channel routing packets before completing channel configuration and restart the channel configuration. This never allows the channel to complete configuration. This is a bug in transaction handing of the ILCS as an 852 compliant configuration server should never time out of a transaction. When the GRouter4's occur before the i.LON 600 in the channel list the i.LON 600 has to process the channel routing requests from the GRouter4's first which delays its response to the ILCS. The workaround is add the i.LON 600's to the channel before the GRouter4's. A compatibility mode will be added to a later version of the GR4 firmware. ---------------------- New in application firmware 4.13.002 for both WiFi and Ethernet 2011/01/26 Summary: Restored support for LNS 3.1 and LonMaker 3.1. Recommendations: The only difference between this version and the previous version 4.12.058 is backwards support for LNS 3.1. If using LNS 3.2 or later there is no reason to upgrade. If upgrading also upgrade the bootloader to the latest version, 4.12.048.C for Ethernet and 4.12.053.D for WiFi. Detailed Changes The 852 (VNI) interface in LNS 3.1 (LonMaker 3.1) uses an invalid protocol version = 0 when sending 852 Data packets. The correct version number for 852, 852-A and 852-B is version = 1. A check for version number was added to prepare for the upcoming 852.1 protocol which uses a higher version number. The fix was to accept version = 0 and version = 1. Outstanding Issues: i.Lon Config Server (ILCS) bug. When using the ILCS where both GRouter4's and i.LON 600's are on the same channel, and there are more than two or three GR4 devices before the i.LON 600's in the channel list, the ILCS will time out waiting for the i.LON 600 channel routing packets before completing channel configuration and restart the channel configuration. This never allows the channel to complete configuration. This is a bug in transaction handing of the ILCS as an 852 compliant configuration server should never time out of a transaction. When the GRouter4's occur before the i.LON 600 in the channel list the i.LON 600 has to process the channel routing requests from the GRouter4's first which delays its response to the ILCS. The workaround is add the i.LON 600's to the channel before the GRouter4's. A compatibility mode will be added to a later version of the GR4 firmware. ---------------------- New in application firmware 4.12.058 both WiFi and Ethernet 2011/01/19 Summary: Fixed a problem where the default IP parameters were not always forcing the IP stack to use the static IP interface. Under some circumstances could use the Auto IP interface. Recommendations: This upgrade is recommended for all units except those being used with LNS 3.1 or earlier. The recommended upgrade includes application firmware 4.12.058 for both WiFi and Ethernet and bootloader 4.12.053.D for WiFi and bootloader 4.12.048.C for Ethernet. Support for LNS 3.1 will be fixed in a later release. Detailed Changes Outstanding Issues: See notes for prior application firmware release ---------------------- New in WiFi application firmware 4.12.053 and wifi bootloader 4.12.053.D 2011/01/17 Summary: Fixed a problem where resetting to factory defaults for the WiFi version would not reset the wifi channel mode to search. Now resets the WiFi parameters correctly. Added in a serial recovery mode to the WiFi bootloader to enable recovery in the case the original application is misloaded. This is primarily intended for use by Adept either during initial loading of fresh units or for units that have been returned. This is a replacement for bootloader 4.12.048.C wifi. Recommendations: This upgrade is recommended for all wifi units except those being used with LNS 3.1 or earlier. The recommended upgrade includes both firmware 4.12.053 and bootloader 4.12.053.D Support for LNS 3.1 will be fixed in a later release. Detailed Changes Outstanding Issues: See notes for prior application firmware release ---------------------- New in application firware 4.12.050 and bootloader 4.12.048.C Summary: Major improvements to the bootup process including faster bootup time and significantly improved stability and reliability when dealing with corruption of the configuration information stored in flash due to inadvertent power cycles. The stability of the reset IP parameters to factory defaults by holding down the service pin upon bootup has been improved and the time to write default parameters is faster. Changes to the 709.1 page in manual mode now propagate automatically to other routers in the channel. The new application firmware now allows ftp upgrade of the bootloader. The main status page now shows the Bootloader and BSP versions as well as the applicaton firmware version. Recommendations: This upgrade is recommended for all units except those being used with LNS 3.1 or earlier. The recommended upgrade includes both firmware 4.12.050 and bootloader 4.12.048.C Support for LNS 3.1 will be fixed in a later release. Detailed Changes -- The configuration parameters are stored redundantly in flash. Upon bootup a CRC check is made of flash to see if the primary copy has been corrupted. If so the backup copy is used if it is not corrupted. If both are corrupted, default parameters are used. In some rare corner conditions this process would fail and the unit would fail to boot and would require reflashing. These conditions have all been resolved. One of the contributing factors was a problem with the bootloader. This has been fixed in the new bootloader included in this release. -- When changing the IP address and then immediately hitting the reboot button, especially if other configuration changes had been made, sometimes the reboot would happen before the IP address was written to flash. This has been fixed. -- Manual configuration of the routing tables or other info on the 709.1 web page when in Manual Mode did not always result in automatic propagation of the changes to the other routers. This is now fixed. -- The GRouter4 has a recovery procedure in the bootloader that allows reflashing using tftp. However in some cases if the IP parameters were corrupted the tftp procedure would fail. This has been fixed in the new bootloader 4.12.048.C. Outstanding Issues: - i.Lon Config Server (ILCS) bug. When using the ILCS where both GRouter4's and i.LON 600's are on the same channel, and there are more than two or three GR4 devices before the i.LON 600's in the channel list, the ILCS will time out waiting for the i.LON 600 channel routing packets before completing channel configuration and restart the channel configuration. This never allows the channel to complete configuration. This is a bug in transaction handing of the ILCS as an 852 compliant configuration server should never time out of a transaction. When the GRouter4's occur before the i.LON 600 in the channel list the i.LON 600 has to process the channel routing requests from the GRouter4's first which delays its response to the ILCS. The workaround is add the i.LON 600's to the channel before the GRouter4's. - Problems with LNS 3.1 or earlier. Use firmware 4.09n ----------------------- New in 4.11.11 Summary: Now works with Firef0x 3.x and Internet Explorer 8. Verified that it works with Opera 10.x, and Chrome 3.x, as well as Safari 4.x. Improved stability when making lots of configuration changes. Fixes problem switching back from 852 to 852 bridge mode. Recommendations: Earlier versions should be upgraded to 4.11.011 if the device is to be reconfigured Êor used on a different network with LNS Turbo 3.2 or later. Version 4.08 and later do not need to be upgraded on existing installed and operational networks. If using LNS 3.1 or earlier down grade to firmware 4.09n. Changes - Some web browsers were holding the web connection open for long periods of time (two minutes). This could cause the web server watchdog to timeout while waiting for connection. Made watchdog connection non-blocking and extended the web server watchdog timeout to 30 minutes. - Watchdog flags not being set correctly when switching back from 852 to 852 bridge mode there by causing spurious watchdog timeout. Outstanding Issues: - i.Lon Config Server (ILCS) and i.LON 600 configuration problem. When using the ILCS both GRouter4's and i.LON 600's are on the same channel, add the i.LON 600's to the channel before the GRouter4's. When there are more than two or three devices before the i.LON 600's in the channel list, the ILCS will time out waiting for the i.LON 600 channel routing packets before completing channel configuration and restart the channel configuration. This never allows the channel to complete configuration. This is a bug in transaction handing of the ILCS as an 852 compliant configuration server should never time out of a transaction. When the GRouter4's occur before the i.LON 600 in the channel list the i.LON 600 has to process the channel routing requests from the GRouter4's first which delays its response to the ILCS. - Manual configuration of the routing tables or other info on the 709.1 web page when in Manual Mode does not always result in automatic propagation of the changes to the other routers. Work around is to click the "Send Membership List" button or to reboot after changes. This is not a problem if a network management tool configures the router while in manual mode as in this case the changes are propagated automatically. - Problems with LNS 3.1 or earlier. Use firmware 4.09n ------------------------------------ New in 4.10.038 Summary: Now supports LoyTec Config Server and GesyTec 852 IP devices. Better interoperability with i.LON Config Server and LNS. Improved performance and stability. Recommendations: Earlier versions should be upgraded to 4.10.038 if the device is to be reconfigured or used on a different network. Version 4.08 and 4.09 do not need to be upgraded on existing installed and operational networks. Changes: - Adopted new firmware version numbering convention. The new convention is MM.mm.bbb where MM is the major release number, mm is the minor release number and bbb is the build number. This allows better tracking of code builds in the development process - Now works with LoyTec configuration server (LCS). Fixed interoperability problem where LCS was refusing to add GR4 to channel if GR4 was not yet configured because of differing interpretation of 852 specification. - Now works with GesyTec IP 852 devices. Added workaround to problem with GesyTec providing malformed channel routing packet - Fix bug induced by LNS Object Browser. LNS Object browser sends illegal op code for Network Management message for far side router. The bug only occurs if a router is commissioned, decommissioned, and then recommissioned. This bug triggered a bug in the GR4 code where the GR4 would nack with the wrong nack type to the illegal op code. 4.10 now sends the correct NACK. HMIs built on LNS probably see this bug. LonMaker does not have the bug. - Added workaround to ILCS bug where ILCS sends updated DateTime for send list packet in Channel Membership packet but does not respond or nack the ensuing request from the GR4 for a new send list. This was imparing the correct updating of the channel routing information. GR4 now ignores the SendList datetime in the channel membership packet. - Improved selective forwarding algorithm to be more optimal in terms of forwarding traffic. This should reduce IP side traffic load when routers are configured - Improved handling of vendor specific packets - Now correctly marks Adept vendor specific packets - Upgraded MAC layer chip firmware to 1.06 with better handling of Brownouts Outstanding Issues: - i.Lon Config Server (ILCS) and i.LON 600 configuration problem. When using the ILCS both GRouter4's and i.LON 600's are on the same channel, add the i.LON 600's to the channel before the GRouter4's. When there are more than two or three devices before the i.LON 600's in the channel list, the ILCS will time out waiting for the i.LON 600 channel routing packets before completing channel configuration and restart the channel configuration. This never allows the channel to complete configuration. This is a bug in transaction handing of the ILCS as an 852 compliant configuration server should never time out of a transaction. When the GRouter4's occur before the i.LON 600 in the channel list the i.LON 600 has to process the channel routing requests from the GRouter4's first which delays its response to the ILCS. - Incompatibility with FireFox 3.0x and later and Internet Explorer 8.x. When using the web interface with these versions of the browsers, submit changes can cause the unit to reboot, thereby losing the changes. This will be fixed in a future release. Firefox 2.x or earlier, Internet Explorer 7.x or earlier, and all versions of Safari do not have this problem - Change the IP address separately from other configurations changes. Do not change configuration information on other pages on the same flash write reboot cycle. - Manual mode, manual configuration of the routing tables or other info on the 709.1 web page does not always result in automatic propagation of the changes to the other routers. Work around is to reboot after changes or send membership list. This is not a problem if a network management tool configures the router while in manual mode as in this case the changes are propagated automatically. ---------------------------------------------- New in 4.09n Recommendations: All versions 4.07 or earlier should be upgraded to 4.09. There is no need to upgrade 4.08 to 4.09 unless the new features introduced in 4.09 are desirable. Known Issues: - Discovered incompatibility with FireFox version 3.0x and all versions of the GR4 firmware. When using the web interface from FireFox 3.0x, Submit Changes can cause the web server on the GR4 to crash, thereby causing the router to reboot. This will be fixed in a future release. FireFox version 2.x or earlier, Internet Explorer 7.x or earlier and all versions of Safari do not have this problem. - It is recommended that when changing to IP address to do it separately from other configurations changes. In other words, change the IP address and reboot. Do not change configuration information on other pages on the same flash write reboot cycle. New in version 4.09n from 4.08 - the "i.Lon CS compatibility mode" has been renamed to "backwards compatibility" mode to match how the latest version of the i.Lon CS names it. - Cleaned up the boot code so it boots a few seconds faster. - Fixed a problem with the 709.1 phy chip that would cause it to not boot in rare cases due to component variability in the power supply and GRouter. This would prevent the main computer from reading the EEPROM on the PHY which stores the activation keys. The web page would display a warning that the unit was not activated. The problem had to do with improper brown out detection settings. - Reset to factory defaults procedure has changed. It is now much easier and more reliable. Detailed instructions are in the 4.09 User Guide but a summary is provided here. 1) Reset the router. It will take about 30 seconds for the router to load its firmware. Firmware load completed is indicated by the yellow light flashing off and back on and the green light going from solid to flashing. About 10 -15 seconds later the router will read the service button state to determine if a reset to defaults is indicated. 2) Once the yellow light blinks off, hold down (for about 10 - 15 seconds ) either the Service App or Service Router button until the Tx Rx and Srv lights all come on solid. If after holding down the button for 20 seconds the Tx Rx and Srv lights don't come on then try again from the start. These lights will stay on for 3 seconds then go off. 3) After about another minute the router will go into reset. Another minute later it will boot up with all the IP and Web parameters set to factory defaults. New in 4.08 from 4.07 - Fixed problem where watchdog timeout could interrupt flash write when changing the IP address or time zone information. This would sometimes corrupt the firmware causing the unit to not boot and requiring a factory reflash of the firmware. - Added prepare to power down button to Router setup page that checks if any flash writes are pending. It displays a page with a countdown timer to inform the userwhen the flash write is completed or if no flash writes pending displays a page that informs the user that its ok to power down. - Updated the reboot buttons so that they check for pending flash writes and if pending display countdown timer to inform user when the flash write will complete and reboot begin. - Update web pages so all parameters the require reboot for activation are marked with asterisk and added reboot buttons to all pages that have parameters that require reboot. New in 4.07 from from 4.06 - Added manual mode channel list send feature. Enables any device in channel list of another device to send the other device an updated channel list. This reduces the amount of effort required to manually configure a large channel - Fixed problem where web interface did not update second domain subnet/node address when manually configuring the 709.1 information New in 4.06 from 4.05 -Changed flash write sequencing code reduce chances of bricking unit if flash write interrupted prematurely. New in 4.05 from 4.04 -Fixed a bug that caused 709.1 packets shorter than 10 bytes to be dropped. This caused network discovery not to work properly -Added in a fail safe so that if a router has trouble reading data from the 709.1 interface chip it will make several retrys and if it still fails the router will reboot. Changes from 4.03 -Added back in beacon checking for wifi driver to allow for redundant access points, but upped timeout from 3 to 15 beacons -Added 852 out of order packet detection and reordering of out of order packets. -Changed the spi access algorithm of the RTC to match that of the AVR so that there will not be conflicts with the spi clock state. Changes from 4.02 -A Few minor interface changes were made -The NetOS Wifi driver was enhanced to be more reliable when the wifi units are running using infastructure mode. -Added support for routing of packets when a network is configured in a domain with domain length being 0 Changes from 4.02b2 -Added MD5 Authentication for the 852 channels as per the 852 specification. -Changed a few more refrences to the two sides of the router so that they display appropriatly in bridgeing mode. Changes from 4.02b1 -Added enhancement to Router to enable 852 configuraion to be serialized and throttled. This can be used in situations where there is a very low bandwidth link between routers. -Fixed the Clear Routing Config button so that it no longer sets the IP configuration back to defaults. Changes from 4.01 -Added enhancment to bridging mode that allows the two sides of the bridge to operate in independant modes, one manual and one normal -Changed refrences to sides of the router from near side far side to Side A Side B. Changes from 4.00b5 -Fixed the LonMark ProgramID to report tranceiver types correctly -Combined CNS and Adept Versions of firmware into one version -Added button to Clear bootup log on diagnostics page -Added button to Clear router configuration on RouterSetup page -Moved Node ID storage to AVR eeprom instead of ME Flash -Fixed an issue where the router would send out 852 channel Registration messages when configured in manual mode. Changes from 4.00b4 -Added RTC time read out to main webpage and ability to set time -Added Visablity of Device Code -Enabled functionality of optional features via keys -Added Bootup Log in diagnostics page -Changed Procedure for Resetting node to defaults -Fixed a bug that could cause node to reset to defaults under high traffic load -Made the pressing of service pins more reliable when the unit is transmitting on the 709.1 side Changes From 4.00b3 -Combined two packet status flags to one flag to prevent possible lockup of transmissions. Changes from 4.00b2 -This code has all the varius changes we made to the MAC and Interrupts to stabalize the over all performance and fix the problem we had with 400b1 where we sent out bad packets(two packets pended together)