General Information

This Release Note describes changes included in SCADAPack 32 firmware version 2.00, released on May 6, 2008.

Software and Hardware Relevant to this Release

  • Firmware Loader version 2.50 Firmware Loader version 2.45 contains this version of the firmware.
  • TelePACE Version 3.30 is the currently released version of TelePACE.
  • ISaGRAF Version 2.40 is the currently released version of ISaGRAF.
  • RealFLO version 6.51 (Application and Flow Computer) is the currently released version of RealFLO.

New Features in SCADAPack 32 Firmware 2.00

  • Support for 5607 I/O Module is added.
  • Support for 5414 16-Point Digital Input Module is added.
  • Support for 5415 12-Point Digital Output Module is added.

Issues Resolved from SCADAPack32 Firmware 1.92

The following issues identified in the SCADAPack 32 firmware version 1.92 have been resolved in the current release.

  • Checking of DNP memory allocation for master controllers is improved. DNP configurations containing a master poll table could be loaded into a controller and result in not enough memory for the configuration. The configuration is now checked and a message is displayed if the controller does not have enough memory for the configuration.
  • An error is corrected where the Ladder Logic table is shifted during an online edit but the Ladder Logic history table was not updated. The effect of this was that Ladder Logic function blocks that detect a rising edge or falling edge transition on the inputs would falsely detect a transition if On Line editing was done in a network before the function block.
  • Affected Ladder Logic function blocks were: One Shot Coil, OVER, UCTR, DCTR, PULS, PULM, MSTR, MSIP (in 32 bit controllers), PID, PIDA, PIDD, DIAL, INIM, HART, FLOW, DLOG, GETL, SCAL, TOTL, DEVT and DUNS.
  • The rxstring function in ISaGRAF did not properly handle 0xFF characters. This has been corrected and the characters are now properly handled.
  • DNP operation is corrected to ensure responses to master station messages do not get out of synchronization. It was possible for a message to be flagged as failed but remain in the receiver buffer. The failed message would get processed and responded to as soon as another message was received. The outstation could remain in this out of synchronization state until the controller was restarted.
  • DNP master operation now uses the Direct Operate function code to write binary and analog output points to an outstation.
  • DNP operation is corrected to ensure responses to master station messages do not get out of synchronization. It was possible for a message to be flagged as failed but remain in the receiver buffer. The failed message would get processed and responded to as soon as another message was received. The outstation could remain in this out of synchronization state until the controller was restarted.
  • DNP Master Polling is corrected to ensure that sequencing of master poll messages does not result in outstations not being polled as configured in the master poll table. Previously a master station could, in rare situations, get hung up sending polls to one outstation and ignore other outstations.
  • Store and Forward operation is improved to ensure that simultaneous Store and Forward communication, i.e. when using Ethernet, with multiple slave devices does not fail. When a message is forwarded the expected station number for the response is saved internally. This ensures that all store and forward messages processed without failure.