General Information

This technical notice describes the changes included in 6.5.0

Application Version

The SCADAPack Workbench application version is 6.5.0 (build 6.5.2146).

Firmware Versions

  • The latest SCADAPack firmware at the time of release is:
    • 1.75 for SCADAPack 314, SCADAPack 330, SCADAPack 334, SCADAPack 350, and SCADAPack 357 controllers
    • 1.63 for SCADAPack 4203 controllers
    • 2.23 for SCADAPack 32 and SCADAPack 32P controllers
    • 2.50 for SCADAPack 100 controllers  
    • 1.75 for NOCT60
  • The latest SCADAPack E firmware at the time of release is 8.13.1 for SCADAPack E remote Programmable Automation Controllers (rPACs) and Remote Terminal Units (RTUs).

New Features and Enhancements (6.5.0)

  • Windows 10 (32-bit and 64-bit) support.
  • SCADAPack Target 3 supports Sequential Function Chart (SFC) Programmable Organization Units (POUs) with some limitations:
    • Monitoring is not available while in simulation or running mode.
    • SFC macro steps (macro beginning steps, macro steps, and macro ending steps) are not supported.
  • A Diagnostic view provides real-time statistical information about Target 3 and Target 5 applications.
  • SCADAPack ES/ER templates for firmware versions 8.12.5+ include 8 new function blocks:
    • MODBUS_SETUP_RD_BOOL
    • MODBUS_SETUP_RD_REAL
    • MODBUS_SETUP_RD_UDINT
    • MODBUS_SETUP_RD_UINT
    • MODBUS_SETUP_WR_BOOL
    • MODBUS_SETUP_WR_REAL
    • MODBUS_SETUP_WR_UDINT
    • MODBUS_SETUP_WR_UINT
  • SCADAPack sp350v1 and sp357v1 templates have been created for Target 3 projects that provide default I/O for 5 V/20  mA boards.

Improvements (6.5.0)

  • Migration to the Microsoft Visual Studio 2013 isolated shell:
    • The Solution Explorer provides new capabilities, including:
      • Searching the contents of the tree structure.
      • Collapsing and expanding tree structure views.
      • Scoping a specific element of the tree structure.
      • Passing from the default tree structure view to the previous or next view.
  • The LD language editor includes the following improvements:
    • While dragging rungs, blocks, coils, contacts, jumps, returns, and branches, the language editor displays the possible drop points.
    • While debugging, the Ctrl-T keyboard shortcut toggles the Boolean logical value of a selected contact, coil, or block input.
    • Improved ability to select rungs using Control and Shift keys with a left-mouse click.
    • Improved keyboard navigation using the arrow keys.
  • The Cross References Browser includes the following improvements:
    • Searches for Target 3 cross references.
    • Improved filtering options.
    • Improved visibility of results including highlighting variable, block, or defined word search results and displaying locations for cross references.

Functional Changes (6.5.0)

  • When installing SCADAPack Workbench 6.5.0 on a computer that was running a previously licensed version, a message states that the free version is running. This means you need to activate the SCADAPack Workbench 6.5.0 license. To obtain new license registration keys, contact Schneider Electric customer support at ordersTRSS@schneider-electric.com.
  • When installing SCADAPack Workbench 6.5.0, the new communication settings defined in C:\ProgramData\Schneider Electric\6.5\Schneider Electric Gateway\OpcConfig.xml file are applied to SCADAPack Workbench. If you were running a previous version of SCADAPack Workbench and now experience communication issues, revert the IxlTimeoutMultiFactor, ConnectRetryTimeInterval, and ConnectNoResponseTimeOut values in the OpcConfig.xml file to their previous values.
  • For POUs created in SCADAPack Workbench 6.3.0 or earlier, you need to open a local copy of the POU, make a change, then save the POU to ensure the XML files are updated to the current SCADAPack Workbench version.
  • SCADAPack Workbench cannot load projects with an invalid name. Valid project names begin with letters followed by letters, digits, and single underscore characters. Names cannot be reserved words or data types (defined words or arrays).

Fixed Issues (6.5.0)

Target 3 and Target 5

  • Issue: A defined word name could exceed the 252 maximum character length, causing unexpected behavior in SCADAPack Workbench.

Fix: The defined word name is properly validated to prevent unexpected behavior.

Engineering Reference: IES6-1087

  • Issue: ISaVIEW projects could not be exported as templates using the “Export as Template” feature.

Fix: The “Export as Template” functionality for ISaVIEW projects has been corrected.

Engineering Reference: IES6-1094

  • Issue: Focusing on an ISaVIEW window during a download caused unexpected behavior in SCADAPack Workbench.

Fix: Display and focus issues on ISaVIEW pages have been corrected.

Engineering Reference: IES6-1097

  • Issue: The Document Viewer sometimes caused unexpected behavior in SCADAPack Workbench.  Fix: The Document Viewer is now more stable and no longer causes SCADAPack Workbench to crash if its position is changed.

Engineering Reference: IES6-1099

  • Issue: Tag names on the LD canvas were truncated in a way that made them difficult to read.

Fix: Long tag names are truncated in the middle using "...", and a tooltip is provided to indicate the full tag name when hovering over a variable.

Engineering Reference: IES6-1170

Target 5 Only

  • Issue: The controller status was reported as "not alive" on the first download attempt if a program was already running in the RTU.

Fix: The Target 5 download mechanism has been improved and no longer reports “not alive” on download if a program already exists and is running.

Engineering Reference: IES6-837

  • Issue: SCADAPack Workbench becomes unresponsive after attempting to access a variable after communication is lost.

Fix: Target 5 communication is now more robust to help prevent SCADAPack Workbench from becoming unresponsive.

Engineering Reference: IES6-941

  • Issue: The Modbus Master function block documentation was incomplete.

Fix: The Modbus Master function block documentation has been improved.

Engineering Reference: IES6-1150, IES6-1178

  • Issue: Documentation did not state that the Windows Runtime Modules are not supported on SCADAPack firmware.

Fix: The Migrating ISaGRAF 3 Workbench Projects to SCADAPack Workbench documentation now includes a more detailed list of unsupported features.

Engineering Reference: IES6-1175

Target 3 Only

  • Issue: The “IsRetained” checkbox did not properly display in the variable table, although the value was correct.

Fix: The control window is now refreshed as expected.

Engineering Reference: IES6-844

  • Issue: An "Application stopped" message was displayed in the output window after a download, even though the application was running in the device.

Fix: The Output window is now cleared after the download is complete.

Engineering Reference: IES6-846

  • Issue: The Cross Reference browser did not find all references of the object.

Fix: The Cross Reference browser now retrieves all expected results.

Engineering Reference: IES6-944

  • Issue: Users could not enter simulation mode if SCADAPack Workbench was opened via an *.acfproj or *.isasln file in Windows Explorer.

Fix: The working directory for the SCADAPack Workbench project is correctly defined and projects that are opened from Windows Explorer can be debugged using the Simulator.

Engineering Reference: IES6-1102

  • Issue: The Cycle Timing value was not reset when a new debug instance was initialized.

Fix: The Cycle Timing value is cleared and applied as expected.

Engineering Reference: IES6-1124

  • Issue: Documentation for Modbus Setup blocks was incorrect.

Fix: The documentation has been improved.

Engineering Reference: IES6-1143

  • Issue: Variable instances were not recognized in the Spy List when adding the “Add to Spylist” option from the context menu.

Fix: The Spy List functionality has been improved.

Engineering Reference: IES6-1169

  • Issue: Target 3 projects were sometimes automatically rebuilt when attempting to enter debug mode, causing a version mismatch between the rPAC and SCADAPack Workbench.

Fix: Projects are no longer automatically rebuilt when entering a debug session.

Engineering Reference: IES6-1190

For a list of every item addressed, see the file AcpResolvedIssues.txt in C:\Program Files (x86)\Schneider Electric\SCADAPack Workbench\SCADAPack Workbench.

Known Issues/Known Customer Difficulties (6.5.0)

Target 3 and Target 5

  • Issue: Attempting to run multiple instances of SCADAPack Workbench may cause unexpected behavior.

Workaround: Run a single instance of SCADAPack Workbench.

Engineering Reference: N/A

  • Issue: The Instruction List (IL) programming language is not implemented. You cannot open Program Organization Units (POUs) written in this language.

Workaround: N/A

Engineering Reference: N/A

  • Issue: When creating elements, names with more than 32 characters can exceed the maximum path name length supported by Microsoft Windows operating systems.

Workaround: Avoid using names with more than 32 characters.

Engineering Reference: N/A

  • Issue: The “Find and Replace” feature’s "Find Next" and "Replace" commands are available only within the context of the ‘Current Document’ for POUs.

Workaround: Perform Search and Replace for a POU by clicking Ctrl+F, then setting the ‘Look In’ field to ‘Current Document’ and using only the “Find Next" or "Replace" commands.

Engineering Reference: ISE6-1153

  • Issue: Toolbox icons are not displayed properly when using a Windows display setting other than 100%.

Workaround: Use only Windows display settings of 100% when running SCADAPack Workbench.

Engineering Reference: N/A

  • Issue: You cannot drag POU body elements between different programming language containers. Trying to do so can cause unexpected behavior in SCADAPack Workbench.

Workaround: N/A

Engineering Reference: N/A

  • Issue: The dictionary displays an incorrect lock status for variables.

Workaround: Use the Locked Variables viewer to see the correct lock status for variables.

Engineering Reference: N/A

  • Issue: The Block Library or Variable Selector is not automatically displayed for Ladder Diagram (LD) POUs when you double-click on coils and contacts in the Toolbox.

Workaround: To display the Block Library or Variable Selector, insert coils and contacts in the Toolbox, then double-click on them.

Engineering Reference: N/A

  • Issue: Using the Document Overview for a Function Block Diagram (FBD) POU can cause unexpected behavior in SCADAPack Workbench.

Workaround: N/A

Engineering Reference: ISE6-1099

  • Issue: When using the Documentation Generator, the generated document is dependent on the zoom level of the open FBD POU.

Workaround: Close all POUs before generating the document.

Engineering Reference: N/A

  • Issue: When resetting the toolbox for FBD, LD, SFC, or ST programming languages, the icons for some or all elements may not display correctly.

Workaround: Close and reopen SCADAPack Workbench.

Engineering Reference: N/A

  • Issue: In the Customize dialog box for menu bar, toolbar, and context menu items, avoid applying the "Reset All" command since this operation may cause unexpected behavior.

Workaround: To remove the effects of the "Reset All" command, you can reset all environment settings to their defaults by choosing Tools > Import and Export Settings then selecting the "Reset all settings" option.

Engineering Reference: N/A

  • Issue: Real values are displayed as integers in ISaVIEW text variables.

Workaround: N/A

Engineering Reference: IES6-1114

  • Issue: Opening the Diagnostics window while offline may cause SCADAPack Workbench to become temporarily unresponsive.

Workaround: Avoid opening the Diagnostics window when not actively connected to a device.

Engineering Reference: IES6-1235

Target 5 Only

  • Issue: If you download a new IEC 61131-3 application with virtual addresses and retained variable sizes that are the same as an existing application, the existing values for these variables may be reused in the new application.

Workaround: Avoid downloading multiple applications that have the same names and sizes for retained variables.

Engineering Reference: N/A

  • Issue: I/O variable values are not updated when the I/O Device window is docked.

Workaround: To view updated values, click on another I/O Device instance to force the window to refresh.

Engineering Reference: N/A

  • Issue: A virtual address overlap occurs if you delete an IEC 61131-3 function with an anonymous array as a complex parameter and the function uses the complex parameter (usually the case).

Workaround: N/A

Engineering Reference: N/A

  • Issue: Copying programs with wired array variables can cause unexpected behavior in SCADAPack Workbench.

Workaround: Delete the array variables in the copied program.

Engineering Reference: N/A

  • Issue: Copying FBD POUs from programs to function blocks can cause unexpected behavior in SCADAPack Workbench.

Workaround: Copy subsets of the POU body between programs and function blocks.

Engineering Reference: N/A

  • Issue: You need to unwire wired variables before modifying the dimension.

Workaround: N/A

Engineering Reference: N/A

  • Issue: Running an application that contains non-instantiated Sequential Function Chart (SFC) function blocks with SFC child blocks can cause unexpected behavior on the target.

Workaround: N/A

Engineering Reference: N/A

  • Issue: Since the release of Target 5, the behavior of SFC steps with non-stored (N) action qualifiers has been modified to comply with the IEC 61131-3 standard.  SFC steps are now executed when they are activated and when they are deactivated.

Workaround:  If the action only needs to be executed once, replace the N qualifier with a P0 or a P1 qualifier in the action's properties in applications that have non-stored (N) action qualifiers in SFC Steps.

Engineering Reference: N/A

  • Issue: If you open an FBD POU while monitoring an application, tooltips are incorrectly displayed with the __MO_ prefix.

Workaround: N/A

Engineering Reference: N/A

  • Issue: You cannot monitor the values of arrays that have a variable as an index.

Workaround: N/A

Engineering Reference: N/A

  • Issue: When using ISaVIEW documents, you cannot access individual integer bits.

Workaround: N/A

Engineering Reference: N/A

  • Issue: ISaGRAF eXchange Layer (IXL) communication with a target may be unsuccessful.

Workaround:  Try the following:

  • Start simulation from the toolbar to test communications with the simulator.
  • Use the Windows Add/Remove Programs feature to verify that the "OPC Core components redistributable" item is installed.
  • If the SCADAPack Workbench runtime is installed on a quad-core computer, set the CPU affinity to one core.

Engineering Reference: N/A

  • Issue: Function block input and output labels are displayed using pin ids instead of full names. 

Workaround: View the full name of the input/output in the Block Selector view.

Engineering Reference: ISE6-692

  • Issue: When attempting to debug or simulate a project with a number of variables that exceed the available memory, the output window displays the "OPC server is unable to load project..." message and the "OutOfMemoryException: calling OPC Server shutdown" error message. The debugging or simulation process terminates and SCADAPack Workbench returns to project editing mode.

Workaround: N/A

Engineering Reference: N/A

  • Issue: When updating a solution or resource from an exchange file, the variables are missing from the variable groups.

Workaround: N/A

Engineering Reference: N/A

  • Issue: When editing the properties of a POU body, you need to click elsewhere in the editor workspace before proceeding.

Workaround: N/A

Engineering Reference: N/A

  • Issue: When the compiler is unable to produce TIC code for FBD networks, the error list displays a warning message stating that the element is part of a tree not producing any code.

Workaround: To enable the production of TIC code, you need to modify the network:

-          For rungs starting with a vertical bar, place a contact to the left on the rung.

-          For networks having a loop, replace the loop with variables.

Engineering Reference: N/A

  • Issue: Loops in FBD networks may produce unexpected execution order results.

Workaround: When placing loops in FBD networks, verify that the execution order follows your intended results.

Engineering Reference: N/A

  • Issue: Resolving the logic of FBD POUs with a manual execution order may require additional kernel execution cycles compared to using automatic execution.

Workaround: N/A

Engineering Reference: N/A

  • Issue: For variables using library-defined structure types with initial values, build errors occur after modifying the data types of the structure members because the initial values of these structure members are not reset after performing the modifications.

Workaround: To remove the incorrect initial values after modifying the data types of structure members, change the data type of the variable to any other type, then back to the original data type.

Engineering Reference: N/A

  • Issue: Starting debugging with closed FBD POUs containing user-defined functions causes the error icon to be displayed on the block either when the POU is opened during simulation or when simulation is stopped.

Workaround: Open all FBD POUs containing user-defined functions before debugging.

Engineering Reference: N/A

  • Issue: When using the document generator on a SFC program, embedded transitions where ST or LD are used do not get generated and are therefore not documented.

Workaround: N/A

Engineering Reference: ISE6-1201

Target 3 Only

  • Issue: Recursive folders may be created when importing ISaGRAF 3 Workbench projects into SCADAPack Workbench.

Workaround:

  • Choosing the folder where the *.hie file is stored can cause unexpected behavior in SCADAPack Workbench. Choose a different folder.
  • ISaGRAF 3 Workbench project folder names with more than eight characters can cause unexpected behavior in SCADAPack Workbench. Before importing, shorten the ISaGRAF 3 Workbench folder name if necessary.

Engineering Reference: ISE6-1033

  • Issue: Device names with more than 8 characters cause unknown compilation events.

Workaround: Avoid using device names with more than 8 characters.

Engineering Reference: N/A

  • Issue: After running a project with a POU, then deleting the POU, SCADAPack Workbench may not prompt you to rebuild the project before restarting simulation.

Workaround: N/A

Engineering Reference: N/A

  • Issue: The values of unused variables are displayed as Offline.

Workaround: N/A

Engineering Reference: ISE6-963

  • Issue: The compiler optimization options produce unstable results.

Workaround: Avoid applying these options.

Engineering Reference: N/A

  • Issue: Importing variables removes all I/O wiring connections.

Workaround: Rewire variables after importing.

Engineering Reference: ISE6-1013

  • Issue: Simulating Target 3 projects requires administrator privileges.

Workaround: Run SCADAPack Workbench with administrator privileges:

1.  Locate the SCADAPack Workbench application and right-click on it.

2.  Choose Run as administrator.

 Engineering Reference: N/A

  • Issue: The Cross References Browser does not display cross references for Target 3 SFC POUs.

Workaround: N/A

Engineering Reference: N/A

  • Issue: Support for imported Instruction List (IL) programming in SFC may be incomplete. This programming is displayed in steps with header and footer delimiters as in ISaGRAF 3.

Workaround: N/A

Engineering Reference: N/A

  • Issue: After modifying an SFC program with SFC children, the project needs to be cleaned.

Workaround: N/A

Engineering Reference: N/A

  • Issue: When copying an SFC POU that calls SFC children, the copied POU displays correctly in the Solution Explorer. However, the SFC actions calling the children are not copied; these actions are empty.

Workaround: N/A

Engineering Reference: N/A

  • Issue: For SFC steps and transitions, the renumbering feature applies the Sx and Tx naming convention used for Target 5 SFC

Workaround: N/A

Engineering Reference: N/A

  • Issue: When the data value for defined words exceeds the possible value range, the compiler may not specify an out-of-range error.

Workaround: N/A

Engineering Reference: N/A

  • Issue: Unloading then reloading a Target 3 library project is not recommended as this may cause unexpected behavior in SCADAPack Workbench.

Workaround: Unload the library project, close the solution, re-open the solution, then reload the library project.

Engineering Reference: N/A

  • Issue: When importing variables for a function, an extra variable named “NewVariable” is added.

Workaround: Delete the extra NewVariable variable.

Engineering Reference: N/A

  • Issue: The “Execution Order” feature is not implemented for Target 3 FBD POUs.

Workaround: N/A

Engineering Reference: IES6-1141

  • Issue: Local defined words cannot be selected from the variable selector in a POU.

Workaround: Do not use the Variable Selector popup that is accessed by double-clicking on a variable. Instead, use the quick access variable dropdown selector to assign a local defined word to a variable.

Engineering Reference: IES6-1155

  • Issue: Entering a negative “Cycle Timing” value causes unexpected behavior. 

Workaround: Do not enter negative values in the “Cycle Timing” control.

Engineering Reference: IES6-1122

  • Issue: Downloading a project while the I/O Wiring window is active may cause unexpected behavior in SCADAPack Workbench.

Workaround: Close the I/O Wiring window before downloading a project.

Engineering Reference: IES6-1129

  • Issue: Updating the communication settings after renaming a device may cause unexpected behavior.

Workaround: Avoid opening the Diagnostics window when not actively connected to a device.

Engineering Reference: IES6-1194

  • Issue: Variables may appear to retain their initial value after a clean or a rebuild.

Workaround: Close the variable (VAR) window and re-open it to force the user interface to refresh.

Engineering Reference: IES6-867

  • Issue: Cannot start debugging for a Target 3 program in the RTU.

Workaround: Erase the Target 3 program in the RTU, re-download it to the device, then try to start debugging again. If that doesn't work, create a new SCADAPack Workbench project, clean the solution, build it, download it to the RTU, then try to start debugging again.  

Engineering Reference: IES6-1242