H2-EBC100 Revision History
Firmware
Version		 Booter
Version		 Release
Date		 Description of Problem(s) / Addition(s) / Change(s)
4.0.544   31-Jan-2012 Fixed a problem where the H2-EBC100 could not properly handle a broadcast packet that is larger than 1536 bytes.
 
4.0.520   12-Jan-2010

The H2-EBC100 now splits out the Ethernet errors (as seen from NetEdit) as follows:

  • Missed Fr - A count of the packets missed due to overruns, unavailable buffers or a disabled receiver.
     

  • TX Coll - A count of the packets which had a late collision while being received.
     

  • Lost Pkts - A count of the packets discarded because they were too long or too short.
     

  • Bad Pkts - A count of the packets which have bad CRC’s
     

  • Unknown - A count of the packets which contain invalid symbols, extra bits or resulted in a receiver overrun condition.
     

  • TX Errors - A count of the packets which could not be sent because the transmitter was unavailable for an extended period of time.
4.0.519   4-Jun-2008
4.0.518   23-Apr-2008 Fixed a problem which could cause the H2-EBC100 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 H2-EBC100 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.492   23-May-2007 Corrected an error in Module Status when reported via Modbus TCP/IP.
 
4.0.490   21-Feb-2007 The following changes were made to the H2-EBC100 firmware to address potential configuration problems when trying to configure the H2-EBC100 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.
  • If the H2-EBC100 is configured to 'obtain an IP address automatically' and no DHCP server is available to provide an IP address, NetEdit could not connect to the device. We fixed this by temporarily setting the IP address to 0.0.0.0 when the H2-EBC100 is looking for a DHCP server.
     
  • Excluded the following addresses from being used in the IP Address field:
    224.x.x.x through 255.x.x.x (Multi-cast range)
    x.x.x.255
    127.0.0.0 & 127.0.0.1
     
  • Added a Recovery-mode option. If the H2-EBC100 is powered up with DIP switch 6 ON, the TCP/IP addressing information (IP Address, Subnet Mask & Gateway Address) fields are reset to 0.0.0.0. The Status and Error LEDs blink so that you can visually recognize this mode. You can use NetEdit to configure the IP addressing information while the H2-EBC100 is in this mode, but you cannot access the I/O in this mode.
4.0.483   24 Aug-2006
  • Corrected issue with H2-EBC100 that caused it 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 module via a broadcast packet.

    Details: If the H2-EBC100 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 H2-EBC100 will not process the request. These device management functions must be sent to the H2-EBC100 in a point-to-point packet or in a directed broadcast packet.
4.0.482   25-Jul-2006
  • Updated the TCP/IP stack code to v1.1.1
     
  • Enhanced the garbage collection of "abandoned" packets to prevent the H2-EBC100 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.479   24-Jan-2006 Additional work in the TCP/IP stack so that it could correctly handle Modbus/TCP requests that come in very close together.
 
4.0.478   13-Jan-2006 Fixed a problem in the TCP/IP stack so that it could correctly handle Modbus/TCP requests that come in very close together.
 
4.0.465   14-Dec-2005 Updated the internal TCP/IP stack.
 
4.0.464   10-Nov-2005
  • If read requests for the I/O Module Status data are not on the 20-word boundaries, you get erroneous data. (see page 4-8 in the H2-EBC User Manual).
     
  • When using Modbus/TCP,  if the H2-EBC100 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.
4.0.457   26-Jul-2005 Fixed an I/O mapping problem that prevented the H2-CTRIO from working when used in an ERM->EBC configuration or with Entivity's ThinknDo. The DWord outputs were not being placed in the correct location within the H2-CTRIO's memory.
 
4.0.453   25-Apr-2005
  • Added support for the new F2-8AD4DA-1 and F2-8AD4DA-2 combination analog input / output modules.
  • Fixed an I/O mapping problem when the H2-CTRIO is used in an ERM->EBC configuration. The problem shows up as an I/O mapping discrepancy between what's displayed in CTRIO Workbench and the I/O Map displayed in ERM Workbench.

    NOTE: This change requires that you also use an updated version
    of     CTRIO Workbench (v2.1.10 or later) to configure the H4-CTRIO.

    Technically speaking, the H2-CTRIO module will now be reported as a Type 7 module instead of a Type 5 module.
4.0.449   14-Dec-2005 For Modbus/TCP connections, we increased the Idle Connection Timeout value from 5 seconds to 60 seconds. This value determines how frequently the Modbus/TCP master has to access the EBC100 to keep the socket connection open.
 
4.0.448   7-Dec-2004 The H2-EBC100 was incorrectly reporting the amount of I/O data for the H2-CTRIO. This firmware version is required to make the H2-EBC100 work with the KEPDirect I/O software.
 
4.0.447 4.0.165 30-Nov-2004 Initial release of the H2-EBC100