| H0-ECOM100 Firmware Revision History | ||||
| Firmware Version | Boot Loader Version | Date | Only Applies to: | Description of Problems / Additions / Changes | 
| 5.0.170 | 5.0.64 | 13-Sep-2022 | Rev 9A H/W Rev 11A H/W | 
	Initial release of the Rev 11A Hardware.
    
	This is the minimum firmware and boot loader versions required for 
	H0-ECOM100 with Rev 11A hardware.
	 Requires the use of
	
	NetEdit v3.17h or later. | 
| 5.0.156 | 29-Aug-2022 | Rev 9A H/W | 
	Fixed a very specific, extremely rare issue that could cause the H0-ECOM100 to become 
	temporarily unresponsive. | |
| 5.0.54 | 22-Apr-2022 | Rev 9A H/W | 
	Fixed a problem where the firmware could not be updated if the DIP switches 
	are being used to set the Module ID to an address above 31; the boot loader 
	was acting as if DIP switch 5 has put the unit into 'write protect mode'. | |
| 5.0.155 | 2-Dec-2020 | Rev 9A H/W | 
	Fixed a problem that prevented EMail from working. | |
| 5.0.53 | 28-Sep-2020 | Rev 9A H/W | 
	Fixed a problem in the boot loader that caused the H0-ECOM100 to incorrectly report itself 
	as an H2-ECOM100 if an attempt to update the boot loader ever failed. | |
| 4.1.113 | 19-Mar-2020 | . | 
	Fixed a problem where the Advanced settings were not correctly updated 
	after a Return to Factory Defaults was executed. | |
| 5.0.149 | 18-Mar-2019 | Rev 9A H/W | 
	Fixed a problem where the Advanced settings were not correctly updated 
	after a Return to Factory Defaults was executed. | |
| 5.0.146 | 5.0.52 | 15-Feb-2019 | Rev 9A H/W | 
	Initial release of the H0-ECOM100 with Rev 9A hardware.
    
	This is the minimum firmware and boot loader versions required for 
	H0-ECOM100 with Rev 9A hardware Requires the use of
	
	NetEdit v3.17a or later. | 
| 4.1.108 | 23-May-2018 | Added ability to disable using port 502 for Modbus/TCP and specify a range of alternate port numbers to use for Modbus/TCP. 
	Configuring this option requires the use of
	
	NetEdit v3.16 or later. | ||
| 4.1.107 | 4.1.10 | 2 Apr-2017 | 
	Initial release of the H0-ECOM100 with Rev 7A 
	hardware. This firmware and boot loader 
    
	This is the minimum firmware and boot loader versions required for Rev7A 
	with will work in previous hardware 
	versions, but is required for all hardware versions later than 7A. | |
| 4.0.348 | 04-Dec-2014 | Added a field for the Time Zone Offset to the Email Configuration ( only available through the web browser interface ). | ||
| 4.0.347 | 05-Sept-2014 | 
    
	Fixed a problem where the H0-ECOM100 was not always using a two-digit value for 
	the hours, minutes and seconds of the time stamp when sending an email. | ||
| 4.0.337 | 16-Oct-2013 | Fixed a problem where the Ethernet chip was not set to full-duplex mode. 
	When the H0-ECOM100 is sending an Email, "-0000" is added to the SMTP DATE. The 
	characters "-0000" mean "unknown TimeZone", which tells the SMTP server to 
	use the current Time of the Server when handling the Email. | ||
| 4.0.334 | 10-Sept-2012 | Allow user to enter multiple email addresses on the Email setup web page. Added more on-screen information on the PEERLINK setup page. Refer to ECOM FAQ0120 for information on the PEERLINK network feature of the H0-ECOM100. 
	H0-ECOM100 now generates a unique transaction ID for Modbus requests so that 
	the H0-ECOM100 can know when an out-of-sync response has been received from a 
	misbehaving Modbus Server. | ||
| 4.0.326 | 26-Mar-2012 | Additional security enhancements to further mitigate undesired access to the PLC over Ethernet. Note: this update changes the default state of the web configuration page to be disabled. NetEdit v3.9a (or later) is required to re-enable this ability to configure theH0-ECOM100 with a web browser.” Added a PLC password lockout: three failed attempts at entering the PLC password within a 5 minute period will cause the H0-ECOM100 to lock out further attempts to enter the password for the next 5 minutes. During this lock out time, the Module Type will be displayed in NetEdit with the suffix “-LOCKED”, and "Device LOCKED" if accessed with a web browser. 
	Added PEERLINK support for integration with Do-more PLCs. PEERLINK is 
	enabled and configured only through the web config page, it cannot be 
	configured with NetEdit. | ||
| 4.0.320 | 31-Jan-2012 | Can now be targeted by a C-More panel that is using the 'Automationdirect Do-more Ethernet' communication driver. 
	Enable ARP queuing to fix a problem 
		that was seen when using the H0-ECOM100 in some RBE (Report-by-Exception) 
		configurations. | ||
| 4.0.269 | 10-Aug-2010 | Enabled ARP Queuing to the 
	TCP/IP stack. This was done to help reduce the number of retries for 
	applications using the Report-by-Exception method on Ethernet networks with 
	a large number of 
	network devices. Fixed a problem where Modbus/TCP packets which contain multiple Modbus requests were not handled properly if the final Modbus request is split across two successive TCP/IP packets. | ||
| 4.0.227 | 5-Mar-2010 | Added the following to the 
	HTML configuration page: 
 These options were formerly only available using
	NetEdit 3.7c. | ||
| 4.0.226 | 3-Feb-2010 | Fixed a problem in the requests for data 
	across the backplane that may cause the H0-ECOM and H0-ECOM100 to stop 
	communicating. | ||
| 4.0.225 | 12-Jan-2010 | The H0-ECOM100 now split out the Ethernet errors (as seen from NetEdit) as follows: 
 | ||
| 4.0.224 | 13-Jun-2008 | Fixed a problem that 
		prevented the EmailTrace option from working. | ||
| 4.0.222 | 23-Apr-2008 | Fixed a problem 
		which could cause the H0-ECOM100 to crash (RED ERR LED) if it is being 
		used as a Modbus/TCP slave with multiple Modbus/TCP connections. If 
		those connections are interrupted for more than 20 seconds - like if the 
		cable were unplugged, or if the radio modem lost it's connection - the 
		H0-ECOM100 begins the process of closing these timed-out connections so 
		that new connections can be established. The problem was in the code 
		that closes the connections and cleans up the memory the connections 
		use. | ||
| 4.0.218 | 09-Apr-2008 | Fixed a problem with 
		using the H0-ECOM100 as a Modbus TCP/IP master that would sometimes cause 
		it to crash if the communication was interrupted; for example, if you unplugged 
		the cable. This problem could show up as a hardware crash (the ERR LED would be on). This problem could also show up as the network read & write instructions 
		would stop functioning (the slot's BUSY bit would be ON constantly). In 
		this failure mode, theH0-ECOM100 will continue to work with DirectSOFT and 
		NetEdit, only the network read and write instructions fail to operate. | ||
| 4.0.210 | 04-Oct-2007 | Added Email Authentication to the web browser configuration page - you cannot access this feature via NetEdit3 or the ECEMSUP IBox at this time, those will be added later. To access this feature, use a web browser to bring up the H0-ECOM100's web configuration page, go to the Email Setup page, click 'Enable Authentication' and enter the username and password in the fields provided. The H0-ECOM100 will now use the DATE and TIME from the PLC when sending a Email. Increased number of concurrent open Modbus TCP/IP connections from 4 to 12. TheH0-ECOM100 can now 
		correctly handle having a Gateway Address that is unreachable. In previous 
		firmware versions, H0-ECOM100 configured with an unreachable Gateway Address would get stuck in 
		very long timeout sessions (about 2.5 minutes). | ||
| 4.0.173 | 01-Jun-2007 | Added 'ECOM Advanced Settings' page to the Web browser configuration page. In previous firmware versions you could only adjust these settings via NetEdit3. Fixed a problem with the Web browser configuration page where sometimes only a portion of the page would show up in the Web browser. Added favicons to the Web browser configuration page. If the H0-ECOM100 receives a Modbus/TCP request for a value that is at either endpoint of the PLC's memory mapped ranges, the H0-ECOM100 would erroneously report the value was out of range. If theH0-ECOM100 is 
		operating as a Modbus/TCP server, the H0-ECOM100 would not report the 
		correct error value for a watchdog timeout error from one of it's 
		clients. | ||
| 4.0.169 | 08-Mar-2007 | Fixed a problem 
		where the H0-ECOM100 would not properly read and write S (stage) bits, T (timer) 
		and CT (counter) bits via Modbus TCP/IP protocol. | ||
| 4.0.167 | 21-Feb-2007 | The H0-ECOM100 now support a 'Test Email' from NetEdit. Access to this feature requires that you use NetEdit v3.7 or later. Added more information to the test email that is sent via the 'Test Email' function. H0-ECOM100 firmware now sets the DATE field to a fixed value in the email header to address a problem in some Email servers that have enabled more restrictive checking of the Email contents. Since there's no clock in the H0-ECOM100 to provide the current date information, the DATE field is fixed at 1/1/2000 00:00:00. Without the DATE field set, our Email server (MDaemon v9.5.2) returns "Error 554 - message does not conform to standards". The following changes were made to address potential configuration problems when trying to configure the H0-ECOM100 under Windows Vista operating system. The problem we have is that MS Vista does not have built-in support for IPX protocol, so we must be able to locate and configure our devices using only TCP/IP protocol. 
 | ||
| 4.0.154 | 15-Jan-2007 | 
	The H0-ECOM100 now supports 
		changing the Modbus Slave Timeout, which is used to close Modbus 
		slave connections that have not been accessed within the timeout value.
	Access to this feature requires 
		that you use NetEdit v3.6d or later. | ||
| 4.0.145 | 14-Nov-2006 | The H0-ECOM100 now supports 
		4 concurrent sessions when operating as a Modbus TCP/IP client (earlier 
		versions only supported one active TCP/IP session). | ||
| 4.0.144 | 16-Oct-2006 | The H0-ECOM100 will no longer attempt to process a Modbus/TCP request before it's internal memory map is configured. This was causing the H0-ECOM100 to crash, which was turning on the red ERR led. The details: on power-up, the H0-ECOM100 reads the CPU type and sets up some internal memory map information so that it can tell if a Modbus TCP/IP request is valid for the CPU. If the H0-ECOM100 received a Modbus TCP/IP request before it could read the CPU type and get the memory map values setup, the H0-ECOM100 to process the request with an invalid set of memory ranges. The H0-ECOM100 was returning the function number instead of the error code after a failed RX or WX instruction. It now returns the error code. Maintenance updates 
		to the stack.  | ||
| 4.0.137 | 24 Aug-2006 | Corrected issue with H0-ECOM100 that caused 
		them to crash - the red ERR LED would come ON - if certain system 
		functions like 'set the IP address' or 'set Module ID' were sent to the 
		modules via a broadcast packet. Details: If the H0-ECOM100 receives a network broadcast packet that contains a request to perform a device management function like set the IP Address, set the Module ID, etc., the H0-ECOM100 will not process the request. These device management functions must be sent to the H0-ECOM100 in a point-to-point packet or in a directed broadcast packet. | ||
| 4.0.135 | 17-Jul-2006 | When the H0-ECOM100 is configured as a network master 
		(using RX and WX instructions), fixed a problem that caused the 
	H0-ECOM100 to stop processing Modbus TCP/IP requests if the Modbus 
		Timeout value (configured via NetEdit3, on the Advanced dialog) was set 
		to a value lower than 500ms. The value can now be set to a minimum of 
		100ms. Enhanced the garbage collection of "abandoned" 
		packets to prevent the H0-ECOM100 from running out of available TCP/IP 
		connections. Abandoned packets are typically a byproduct of using 
		Ethernet radio modems, which tend to produce out-of-order packets 
		whenever they get transmission errors. | ||
| 4.0.124 | 2-May-2006 | Updated to latest version of TCP stack (v1.1.1). Fixed a problem where the Modbus TCP/IP Unit ID wasn't 
		being properly handled. The H0-ECOM100 was sending the same Unit ID (the 
		first in the table) for every device listed in the Peer-to-Peer 
		Configuration table. | ||
| 4.0.122 | 20-Mar-2006 | Fixed a problem that prevented the H0-ECOM100 from 
		working with a link configured to use IPX protocol with the IP Address. | ||
| 4.0.121 | 15-Mar-2006 | Fixed a problem that prevented a Modbus TCP/IP client 
		from accessing the PLC's 
		V-Memory after a power-cycle if the PLC has a password (either normal or 
		multi-level password). | ||
| 4.0.119 | 25-Jan-2006 | Fixed a problem in the H0-ECOM100 that prevented them from working with DataWorx PLC software. Enabled the ability to configure the Email Setup parameters via a web browser. Added a gratuitous ARP request every 60 seconds which 
		could help with some wireless networking issues. | ||
| 4.0.73 | 12-Jan-2006 | Fixed a problem in the H0-ECOM100 that prevented the 
		D0-DEVNETS from working in the same DL06 as the H0-ECOM100. | ||
| 4.0.56 | 14-Dec-2005 | Updated the TCP/IP stack to the latest version. | ||
| 4.0.54 | 30-Nov-2005 | Removed some debug strings that were inadvertently 
		left from the last firmware update. | ||
| 4.0.52 | 10-Nov-2005 | Fix problem that occurs if you have H0-ECOM100 in a peer-to-peer network using Modbus TCP/IP protocol, the write operations (WX instructions) would stop working. When using Modbus TCP/IP, if the H0-ECOM100 receives additional read or write requests from the same client before it has a chance to respond to the first request, then those intervening requests could be ignored. Fix problem where H0-ECOM100 would not communicate to the GS-EDRV using Modbus TCP/IP protocol. Fixed problem where the H0-ECOM100 was terminating Modbus TCP/IP connections after a 250ms timeout regardless of the Modbus Timeout value. Added the ability to force the RX and WX instructions to read from and write to the 30001 range instead of their normal 40001 range by specifying an odd numbered length instead of the normal even numbered length.The details: Normally when using the RX/WX instructions in the PLC, you have to specify a data length. Since this data length is always an even number when specifying the "V" data type (Holding Registers in 40001+ range), then all you have to do is specify an odd number for the length. This beta firmware recognizes the odd number and uses that to "know" that you want to read not from the 40001+ Holding Register range, but rather that you want to read from the 30001+ Input Register range. Refer to the ladder example below where the OR-DOUBLE K1 instruction is used to add a value of 1 to the length field, making it an odd value: | ||
| 4.0.49 | 4.0.165 | 11-Feb-2005 | Initial release of H0-ECOM100. | |