All ERM, ERM-F Revision History
Firmware
Version		 Boot Loader
Version		 Date Applies To: Description of Problems / Additions / Changes
1.1.24   03-Sept-2012 H2-ERM
H2-ERM-F
H4-ERM
H4-ERM-F

Extended the previous fix to handle 1160 bytes.
1.1.21   07-Nov-2011 H2-ERM
H2-ERM-F
H4-ERM
H4-ERM-F

Fixed a problem where the ERMs would lose the ability to correctly read the RUN / PGM mode status of the CPU. This problem appears when the amount of I/O data to be written to a single slave, or read from a single slave exceeds 1024 bytes.
 
  3.0.157 31-Jan-2011 H2-ERM
H2-ERM-F		 Fixed a power up issue in the boot loader of the H2-ERM with MAC addresses above 00.E0.62.21.00.00 that caused the PLC to erroneously allocate a huge number of I/O points. We've seen the problem show up in these two ways:

1. A System Error "E262 - I/O out of range"

2. Huge Input and Output count values shown in DirectSOFT's PLC->Config I/O dialog for the slot the ERM is installed in (usually in the 1000+ range).

This latest change extends the change applied in v3.0.139 to handle MAC addresses above 20.FF.FF for H2-ERMs and above 30.Ff.FF for H2-ERM-Fs.
 
1.1.19   01-Oct-2008 H2-ERM
H2-ERM-F
H4-ERM
H4-ERM-F

Fixed a problem where the H2-ERMs and H4-ERMs would not properly report the Slave Disabled feedback bit.
1.1.18   11-Apr-2007 H2-ERM
H2-ERM-F
H4-ERM
H4-ERM-F

Fixed a problem where the H2-ERMs and H4-ERMs would not properly detect the PLC's mode. This condition leaves the ERMs in a state where it can no longer "follow" the PLC mode, nor can you change the ERM's mode manually with ERM Workbench.
1.1.17   09-Jan-2007 H2-ERM
H2-ERM-F
H4-ERM
H4-ERM-F

H4-ERMs and H4-ERM-F will no longer clear the first 8 bytes of it's shared RAM to prevent clearing the PLC mode value (PGM, RUN, TEST, etc.).

The details: As part of it's power procedure the Hx-ERMs initialize their shared RMA to all zeros. They then initialize the first seven bytes with values to describe themselves to the PLC CPU. At power-up and at each mode change, the PLC CPU writes the current mode (PGM, RUN, TEST, etc.) to the eighth byte of the Hx-ERMs shared RAM.

The problem arose if the PLC CPU ever wrote the mode value before the Hx-ERM initialized it's shared RAM. This created the potential power-up situation where the PLC would end up in RUN mode and the H4-ERM in PGM mode.

Since the PLC mode value would be written to the H4-ERM at the next PLC mode change, the problem would go away after a mode change. This issue only shows up during power-up.
 
1.1.16   24-Aug-2006 H2-ERM
H2-ERM-F
H4-ERM
H4-ERM-F

Hx-ERMs will no longer process certain management functions (e.g. set the IP Address, set the Module ID, etc.),  if that function is in a network broadcast packet (directed broadcast packets are still fine).
1.1.11   1-Aug-2005 H2-ERM
H2-ERM-F
H4-ERM
H4-ERM-F

When the H2-ERM is being used with a WinPLC, we changed the method of verifying that the configured EBCs are present. The original method would prevent the EBCs watchdog timer from firing if the H2-ERM went offline for any reason.

This change does not affect the H2-ERM when used with a PLC or the H4-ERM.
  3.0.154 20-Jul-2005 H4-ERM
H4-ERM-F		 Fixed a power up issue in the ERM that caused the PLC to erroneously allocate a huge number of I/O points. We've seen the problem show up in these two ways::
1. A System Error "E262 - I/O out of range"
2. Huge Input and Output count values shown in DirectSOFT's PLC->Config I/O dialog for the slot the ERM is installed in (usually in the 1000+ range).

The details: as part of its power up procedure, the PLC CPU scans the backplane and uses the values it finds in the ERM's Shared RAM to allocate memory for the module's I/O. To ensure that these values are in place when the PLC CPU scans the backplane, the values are now initialized by the boot loader instead of the firmware.
 
  3.0.139 26-Apr-2005 H2-ERM
H2-ERM-F		 Fixed a power up issue in the ERM that caused the PLC to erroneously allocate a huge number of I/O points. We've seen the problem show up in these two ways::
1. A System Error "E262 - I/O out of range"
2. Huge Input and Output count values shown in DirectSOFT's PLC->Config I/O dialog for the slot the ERM is installed in (usually in the 1000+ range).

The Details: as part of its power up procedure, the PLC CPU scans the backplane and uses the values it finds in the ERM's Shared RAM to allocate memory for the module's I/O. To ensure that these values are in place when the PLC CPU scans the backplane, the values are now initialized by the boot loader instead of the firmware.
 
  3.0.121 14-Apr-2004 H4-ERM
H4-ERM-F		 Decrease the delay time in the boot loader so that a D4-440 using a D4-RAM-1 memory cartridge would correctly identify the H4-ECOM. Before this change, the H4-ECOM would be detected as an SF MODULE.
 
1.1.10   17-Feb-2004 H2-ERM
H2-ERM-F
H4-ERM
H4-ERM-F		 Fixed a problem where the DWORD and WORD data blocks were reversed when mapped into the PLC's V-memory.

This problem was present if you had an ERM->EBC->CTRIO configuration and you tried to use any of the pulse output features of the CTRIO. Since the DWORD and WORD data blocks were reversed in the PLC's memory, the I/O mapping was incorrect.
 
1.1.9   23-Oct-2003 H2-ERM
H2-ERM-F
H4-ERM
H4-ERM-F		 H2-ERM and H4-ERM now clears it's internal variable Last ERM Error when the user selects Clear ERM Stats.
1.1.8   13-Jun-2003 H2-ERM
H2-ERM-F
H4-ERM
H4-ERM-F		 H2-ERM and H4-ERM now report all of the channels that are in error at one time. There is a bit-per-channel for each of the 16 channels.
1.1.7   12-Jun-2003 H2-ERM
H2-ERM-F
H4-ERM
H4-ERM-F		 H2-ERM and H4-ERM now report the first channel of a Terminator I/O analog module that has an error, like a broken transmitter. There's only room in the memory map to display one channel's worth of information, so, if you have multiple channels that are in error, only the first channel's error will be reported. Once that error has been fixed, the next channel in error will be displayed.

The error will be reported as follows: The BYTE of the error code will be the channel number ( 0 based) and the BYTE will be the error code.
 
1.1.6   22-Nov-2002 H2-ERM
H2-ERM-F
H4-ERM
H4-ERM-F		 H2-ERM-F and H4-ERM-F now correctly report themselves as the fiber optic versions.
1.1.4   22-May-2002 H2-ERM
H2-ERM-F
H4-ERM
H4-ERM-F		 Correctly report extended error information for Terminator I/O slaves

Force a rewrite of the output data on recovery from a communication error.
 
1.1.1   02-Aug-2001 H2-ERM
H2-ERM-F
H4-ERM
H4-ERM-F		 Initial Release