General Information

This Release Note describes changes included in ISaGRAF Extensions version 2.20. The expected availability for ISaGRAF Extension 2.20 is August 8, 2006.

New Features in ISaGRAF Extensions 2.20

  • DNP/TCP communication component added.
  • DNP/UDP communication component added.

Issues Resolved from ISaGRAF Extensions 2.10

The following issues identified in ISaGRAF Extensions 2.10 have been resolved in the current release:

  • A communication progress window threading issue has been corrected.
  • An issue causing ISaGRAF to shut down, requiring a PC restart, when more than one project is opened at a time has been resolved.
  • The program loader has been modfied to provide accurate status of C program(s) running in the controller.
  • The error dialog that occurs when communication between ISaGRAF and a SCADAPack controller is lost, no longer remains in the foreground.
  • Downloading of C programs to SCADAPack controllers with firmware versions older than 1.40 is now supported.
  • A user is no longer able to change the duplex settings on COM1 of a SCADAPack LP controller.
  • An issue preventing the IC Lockout from functioning properly has been resolved.
  • The Modbus RTU in UDP communication driver no longer fails when a user cancels a request.
  • An issue causing the Modbus/RTU component to appear unresponsive after experiencing an unhandled exception has been corrected.
  • Opening two or more DNP Status windows, if possible, will not cause the ISaGRAF to lock up.
  • Sometimes, an unnecessary error message is displayed when changing the serial port settings on a controller using a ClearSCADA connection. This issue has been resolved.
  • Overriding a controller lock status now unlocks the controller, erases both the C program and Ladder logic program, and reset all settings to default values.
  • Display problems in the DNP Master status dialog have been corrected.
  • An issue causing the DNP status dialog to cause an abnormal program termination has been resolved.
  • An issue preventing a user from stopping a program from the C/C++ Loader has been corrected.
  • An issue causing ISaGRAF to lose focus after a DNP configuration windows is closed, has been resolved.
  • When writing with C/C++ Program Loader to a SCADAPack 2 , the operation generates an error message at the end, even though, closing an re-opening the dialog shows that the program file had been written correctly. This issue has been resolved.
  • A communication progress window display issue has been resolved.
  • The Modbus/RTU communication driver sometimes treats a particular 'Get Data Log Records' command as an unsolicited response, causing it to fail reading more than 500 logs from a SCADAPack controller. This issue has been resolved.
  • The proper error message is displayed when the DNP Status page loses communication.
  • An issue preventing the Modbus/TCP, Modbus/UDP, DNP/TCP, and DNP/UDP components from resetting their connections following a timeout error has been resolved.
  • When a transaction to write a C/C++ program to a controller is prematurely aborted, the same file can no longer be written to a SCADAPack controller. This issue has been resolved.
  • The DNP Status window no longer shows communication statistics for COM ports that do not exist.
  • Initializing the controller will now also clear the DNP configuration.
  • Tab key behaviour in the DNP Status and DNP Master Status windows has been improved.
  • User friendliness of the Program Status window has been improved.
  • An issue causing the SCADAPack 2 C/C++ Loader to incorrectly refresh when a C application overwrite is cancelled has been corrected.
  • COM1 of a SCADAPack100 or 4202GFC can no longer be configured for RS-232 dial-up modem.
  • Port type selection of 'RS-232' now applies for both RS-232 and RS-485 wired operation on COM1 of a SCADAPack 100 controller.
  • The option to erase ladder logic from the Controller| Initialize menu has been clarified to indicate that the register assignments will also be deleted.
  • An issue causing the Program Status command to fail over a Modbus in UDP connection has been resolved.
  • A spelling error in the C/C++ program loader error window has been corrected.

Upgrading from ISaGRAF 3.32 to ISaGRAF 3.5

To upgrade an installed version 3.32 of ISaGRAF to version 3.5 you may install overtop of the older version or choose to uninstall ISaGRAF first.

Installing Overtop of ISaGRAF 3.32

This is the better choice because it allows you to keep all your current projects restored.

  • Install ISaGRAF Workbench 3.5.
  • Install ISaGRAF Extensions. Even if the version of the ISaGRAF Extensions has not changed, it must be re-installed after installing the Workbench 3.5. Any version of the Extensions may be installed with ISaGRAF 3.5.
  • ISaGRAF will run in demo mode for 30 days. Select Licensing from the ISaGRAF 3.5 program group to enable a permanent license.

Note: Hardware Keys used with ISaGRAF 3.32 are not supported by ISaGRAF 3.5. A replacement Hardware Key or Software License must be obtained.

  • Existing projects and any restored projects must be recompiled completely:
  • Open the project and select Touch from the Make menu on the Programs dialog. This will select a full make the next time Make application is selected.
  • Select Make application from the Make menu.
Un-installing ISaGRAF 3.32

This choice requires that all projects be archived first. Note that archived projects cannot be restored with a Demo License in ISaGRAF 3.5. A permanent license is required to restore projects.

  • Archive all projects that you wish to keep by selecting Archive from the Tools menu on the Project Manager dialog.
  • Un-install ISaGRAF Extensions from the Control Panel.
  • Delete the directory C:\ISAWIN where ISaGRAF 3.32 was installed.
  • Install ISaGRAF Workbench 3.5.
  • Install ISaGRAF Extensions. Any version of the Extensions may be installed with ISaGRAF 3.5.
  • ISaGRAF will run in demo mode for 30 days. Select Licensing from the ISaGRAF 3.5 program group to Make application from the Make menu.

Restoring ISaGRAF 3.3 Projects into ISaGRAF 3.5

When upgrading to ISaGRAF 3.5 you may at some point need to restore into ISaGRAF 3.5 a project that was archived in ISaGRAF 3.32. If an attempt is made to enter Debug mode with a restored ISaGRAF 3.32 project, the following error message box is displayed:

The message indicates that he project must be recompiled. Once this is done the project can be downloaded and will then run correctly.
To re-make the entire project:

  • Open the project and select Touch from the Make menu on the Programs dialog. This will select a full make the next time Make application is selected.
  • Select Make application from the Make menu.
  • If there are no make errors, the restored project may now be downloaded to the controller.

Controller Firmware Updated for ISaGRAF Extension 2.20

To take advantage of the changes listed above you should upgrade the firmware in your controller to:

  • TelePACE or ISaGRAF firmware 2.31 for SCADAPack controllers
  • TelePACE or ISaGRAF firmware 1.79 for SCADAPack32 controllers.
  • TelePACE or ISaGRAF firmware 1.10 for SCADAPack 2 controllers.

If the firmware in your controller is either of the above, no action is necessary. Otherwise refer to the section below for instructions on how to upgrade your controller firmware.

Firmware Upgrade Procedure

To take advantage of the changes listed above you should upgrade the firmware in your controller. The following procedure will lead you through the steps to upgrade the firmware.
*Note: All application programs and data associated with the application programs are lost when the firmware is upgraded.
If you are planning to upgrade the firmware in your controller to take advantage of the features and changes described above, it is recommended that the following steps be used. If you have any questions or concerns regarding this procedure contact Control Microsystems Technical Support using the information in the footer of this document.

1. Obtain Firmware Loader 2.24

Send an email to INFOCenter@controlmicrosystems.com. You will be contacted with the information you need to obtain this release.

2. Save your Current Application

Installing new firmware in a controller completely removes any application programs that may be running in the controller.
If you do not have a copy of the application program running in the target controller you will need to read the application from the controller before installing new firmware.
Note: C and C++ programs cannot be read from a controller. You must have a copy of the program before installing new firmware.

Saving Your ISaGRAF Program:
  • In order for ISaGRAF programs to be uploaded from the controller the program must have been compiled with the Embed source code for upload option enabled.
  • From the File menu in the Project Management window select the Upload Project command.
  • Click the Setup button and configure the serial or Ethernet connection with the target controller.
  • Click the Run button to upload the program.

3. Install New Firmware in Target Controller

  • Open the Firmware Loader and establish a serial or Ethernet connection with the target controller.
  • Click the Update Firmware button and select C:\Program Files \ Firmware Loader \ Firmware in the Look in: entry box.
  • Select the firmware file, appropriate for the controller you are using, and with the version listed above and then click the OK button.
  • Read the Confirm Update dialog to ensure you are loading the desired firmware and then click the Yes button to complete the firmware installation.

4. Re-Load Your Application

Once the new firmware has been installed in the target controller you will need to reload the application program.

Re-Load Your ISaGRAF Program:
  • Open the ISaGRAF project saved in step 2 or the ISaGRAF project for the target controller that is saved on your PC.
  • Use the Link Setup command in the Debug menu to establish a serial or Ethernet connection with the target controller.
  • From the Make menu select Make Application to re-compile the program.
  • From the Debug menu select Debug to open the Debugger window. In this window select Download from the File menu to download the application to the target controller.
Re-Load Your C/C++ Applications:
  • For ISaGRAF applications open an ISaGRAF project and use the Link Setup command in the Debug menu to establish a serial or Ethernet connection with the target controller.
  • From the Tools menu select Controller and then select C/C++ Program Loader.
  • In the File window of the C\C++ Program Loader dialog browse to the location of your C/C++ application.
  • Click the Write button to write the application to the target controller.
  • Once the application has been written to the controller click the Run button to start the application running in the controller.