All ERM, ERM100 and ERM Workbench Revision History

Fixed a problem where the H2-ERMs and H4-ERMs would not properly report the Slave Disabled feedback bit.

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.

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.

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).

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.

All ERM, and ERM Workbench Revision History
Firmware Version	Boot Loader Version	Date	Applies To:	Description of Problem(s) / Addition(s) / Change(s)
1.1.19		01-Oct-2008	H2-ERM H4-ERM	Fixed a problem where the H2-ERMs and H4-ERMs would not properly report the Slave Disabled feedback bit.
1.2.2		17-Jul-2007	ERM Workbench	Fixed a bug that prevented ERM Workbench from displaying I/O errors from the remote CPU slot. Added Error 68 - Watchdog Timer Exceeded message to the Slave Error List.
1.1.18		11-Apr-2007	H2-ERM H4-ERM	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 H4-ERM	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 H4-ERM	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 H4-ERM	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	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	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.
1.1 (Build 27)		12-Aug-2004	ERM Workbench	Fix a bug that caused a sporadic crash during IP download. Add T1H-EBC100 support.
	3.0.121	14-Apr-2004	H4-ERM	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 (Build 26)		14-Apr-2004	ERM Workbench	If you are using IP protocol and attempt to download a configuration to an ERM that has not been assigned an IP address, you will get the following error message: "The device's IP address has not been set. In order to download using IP protocol, the ERM must have a valid IP address. Use NetEdit to configure the ERM's IP address."
1.1.10		17-Feb-2004	H2-ERM H4-ERM	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 (Build 25)		08-Jan-2004	ERM Workbench	In the ERM Configuration Wizard, the 'Write to ERM' function will try both IP and IPX protocols before it reports an 'ERM not Found' error message.
1.1.9		23-Oct-2003	H2-ERM H4-ERM	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 H4-ERM	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 H4-ERM	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 (Build 23)		12-May-2003	ERM Workbench	When downloading to an ERM that is already configured, ERM workbench will turnoff the I/O update to the CPU until the new configuration download has completed. Changed error 144 (Drive not Found or Initialized) from Internal only to Internal/External.
1.1.6		22-Nov-2002	H2-ERM H4-ERM	H2-ERM-F and H4-ERM-F now correctly report themselves as the fiber optic versions.
1.1.5		05-Sep-2002	Workbench	Fixed problem that occurred when saving configurations to DISK that contained I/O padding for possible I/O expansion. This caused a necessary change in the ".ERM" data file format. Release 1.1 software can read Release 1.0 and Release 1.1 files, but the old version cannot read the new file format. Release 1.0 .ERM files are valid as long as the configuration does not contain any I/O configuration pad bytes. Added extended slave error diagnostic capabilities, along with a dialog box that shows a list of possible error codes. Added feature to Clear the ERM configuration, via the toolbar or File->Clear ERM menu item. Added 260 memory map support. Added smart refresh of slave's base definition within ERM workbench: when you add the slave to the ERM's slave list, when you return from NetEdit (possible 405 analog configuration), and after you upgrade firmware. This is helpful if you are swapping I/O modules in your slaves while you are configuring your ERM. Disables any Ethernet protocols that are not available (UDP/IP or IPX). Added feature to change the PLC Scan Timeout for ERM If a PLC ever does have a long PLC scan time (anything around 100ms), this will be beneficial. This is a timeout setting and does not need to be tweaked, just leave it at 100ms unless above situation is true. If the PLC scan time is greater than 50-99ms, make it 2x the maximum PLC scan time. Changed the ERM Workbench Toolbar. It includes the new Clear ERM and Error List buttons, and eliminates the copy/cut/paste buttons which were unused.
1.1.4		22-May-2002	H2-ERM H4-ERM	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 H4-ERM	Initial Release