|ERM Workbench Revision History|
|Version||Date||Description of Problems / Additions / Changes|
|2.4.0 (Build 4)||10-Nov-2022||
Better handling of clearing, reading, and writing the ERM
/ ERM100's configuration.
Added support for D4-454 CPU.
Added support for D2-262 CPU.
|2.0 (Build 6)||6-Sept-2012||
Added ability to support Do-more CPUs; the ERM / ERM100s will publish their data to DLX, DLY, DLC, and DLV memory blocks.
Removed firmware update ability from the ERM Workbench (all firmware updates are done with NetEdit3).
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.
Removed Global (GX/GY) memory range from the PLC Memory Map help text for the 250.
|1.1 (Build 27)||12-Aug-2004||
Fix a bug that caused a sporadic crash during IP download.
|1.1 (Build 26)||14-Apr-2004||
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:
|1.1 (Build 25)||08-Jan-2004||
In the ERM Configuration Wizard, the 'Write to ERM' function will try both IP and IPX protocols before it reports an 'ERM not Found'
|1.1 (Build 23)||12-May-2003||
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.
Fixed a 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.