General Information

This technical notice describes the new features, changes and issues resolved in the new release of ISaGRAF Extensions version 2.10. The expected availability for ISaGRAF Extension 2.10 is March 10, 2006.

New Features added to ISaGRAF Extension 2.10

  • Support for SCADAPack2 controller.
  • Support for SCADAPack E Series Controllers.
  • Automatic adjustment of communication settings.
  • Modbus/USB communication component.
  • .NET installation is automatically performed by the ISaGRAF installer.
  • Discontinued support for Windows 98 and Windows ME.

Issues Resolved from ISaGRAF Extension 2.00

  • Configuration will be written to controller even if controller IP address (in the case of SCADAPack32 or SCADAPack 2) is 0.0.0.0. However, a warning dialog is presented when a user attempts to write configuration changes to the controller with this default IP address of 0.0.0.0.
  • When communicating with a controller, the communication progress bar presents the station number, IP address, access path and outstation set where applicable.
  • C/C++ program loader now presents a more descriptive error message when a user attempts to download an additional program when controller memory is full.
  • DNP communication issues resulting from an improper application and data link timeout entries will now be prevented. Users are now prompted with a warning dialog if the application layer timeout is less than the data link timeout * (data link retries + 1). Note that the data link timeout can be specified in the data link layer or routing sections of the DNP configuration panel.
  • Issue causing the intermittent return of inaccurate outputs from the pow() function has been resolved.
  • Issue causing ISaGRAF 3.32 to randomly switch communication between a serial and Ethernet connection in the debugger has been resolved.
  • Issue causing the default dialing prefix of &F0 &K0 S0=1 &W0 &Y0 to be sent regardless of what is typed into the 'Dialing Prefix' field of the PC Communication Settings dialog has been resolved.
  • Dial Up communication dialog now allows a null string as a dialing prefix. A related issue with corrupted dialing prefixes being sent to a dialup modem has also been resolved.
  • Issue causing the abnormal program termination when closing either the debugger or I/O simulator windows has been resolved.
  • Port type selection of 'RS-232' now applies for both RS-232 and RS-485 wired operation on COM1 of a SCADAPack 100 controller.

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

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

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, an 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.10

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

  • TelePACE or ISaGRAF firmware 2.30 for SCADAPack controllers
  • TelePACE or ISaGRAF firmware 1.70 for SCADAPack32 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.11

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.