Release Notes - ISaGRAF 6.5

System Requirements

Hardware Requirements

• Processor: 2.2 Ghz or higher CPU is recommended.
• RAM: For x86 operating systems, a minimum of 1 GB of RAM is required. For x64 operating systems, a minimum of 2 GB of RAM is required. For a virtual machine, an additional 512MB of RAM is necessary.
• Hard Disk Space: A minimum of 4 GB of available space is required.
• Hard Disk Drive: A minimum of 5400 RPM is required; 7200 RPM or higher is recommended.
• Display Resolution: At minimum, a DirectX 9 capable video card running at 1024 x 768; a 1280 x 1024 or higher display resolution is recommended.

Software Requirements

• Windows 7 (x86 and x64) with latest updates
• Windows 8 (x86 and x64) with latest updates
• Windows 8.1 (x86 and x64) with latest updates
• Windows 10 (x86 and x64) with latest updates

• OPC Core Components, version 105
• Microsoft Visual C++ 2008 SP1 Redistributable Package
• Microsoft Visual C++ 2013 Redistributable Package
• Microsoft Visual Studio 2013 Isolated Shell

Supplementary Software

• [Optional] To view project documentation, install the Word document viewer by installing "Microsoft Office Word Viewer", then "Microsoft Office Compatibility Pack".

New Features

• For integer variables, arrays, structures, and outputs of function block instances, you can access individual bits using indirect addressing syntax for ISaGRAF 5.70 targets or later.
• CAM 3 supports SFC 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.

Enhanced Features

• Migration to the Microsoft Visual Studio 2013 isolated shell:
  • The Solution Explorer includes new capabilities:
    • 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 Options dialog (from the Tools menu) enables performing searches in the table of contents entries.
• 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:
  • Supports searches for CAM 3 cross references
  • Enables improved filtering options
  • Improved visibility of results including highlighting variable, block, or defined word search results and displaying locations for cross references

Anomalies

Known Anomalies

All CAMs

• The Workbench has not received any further localization.
• The find and replace feature only enables using the "Find Next" and "Replace" commands with the Current Document option for POUs. Therefore, make sure to perform searches and replacements for a selected POU body by clicking Ctrl+F, then setting the Look In field to Current Document and using only the "Find Next" or "Replace" commands.
• When cancelling the importation of an exchange file, the Workbench displays an incorrect message while the cancellation is successful. [24329]
• The Workbench does not enable dragging POU body elements between different programming language containers. Attempting such manipulations may cause an unexpected behavior in the Workbench. [23163]
• The dictionary displays the incorrect lock status of variable members. You can view the correct lock status for variable members in the Locked Variables viewer. [23116]
• When using the Documentation Generator, the generated document is dependent on the zoom level of the open FBD POU. [23143]
  Workaround: Close all POUs before generating the document.
• Using the Document Overview for an FBD POU may cause an unexpected behavior in the Workbench. [15329]
• 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 the Workbench. [26106]

CAM 5

• When attempting to debug or simulate a project having a number of variables exceeding 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. At this time, the debugging or simulation process terminates and the Workbench returns to the project editing mode. [34624]
• For SFC and IEC 61499 projects, avoid importing exchange files and using the version source control feature. [13338/24334]
• When updating a solution or resource from an exchange file or from a repository, the variables are missing from the variable groups. [24302]
• When editing the properties of a POU body, make sure to click elsewhere in the editor workspace before proceeding. [23699]
• When the parent of an ISaVIEW screen is encrypted, retrieving the screen from a repository may cause an unexpected behavior. [23908]
• 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. 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 [17814]
  • For networks having a loop, replace the loop with variables [4439, 19974]
• Loops in FBD networks may produce unexpected execution order results. [13734]
  Workaround: When placing loops in FBD networks, verify that the execution order follows your intended results.
• Resolving the logic of FBD POUS having a manual execution order may require additional kernel execution cycles compared to the automatic execution. [23702]
• The Workbench does not support arrays of function block instances. [4749]
• For variables using library-defined structure types with initial values, build errors occur after modifying the data types of the structure members since 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 and then back to the original data type. [38311]
• When importing resources having bindings, these must be imported at the same time to maintain the bindings. For resources belonging to the same device, import the device. For resources belonging to different devices, import the project. [23533]
• Importing a project having bindings linked to a different project displays a message stating that the ACP has encountered a problem. The window can be ignored and no Workbench restart is necessary. [22582]
  Workaround: From the Bindings window, right-click the Consuming Group, and then click Properties. From the Properties window, redefine the Project Path to point to the producer project.
• When downloading a new IEC application where the virtual addresses and sizes of retained variables remain the same, previously retained values for such variables may be reused. [21077]
  Workaround: Avoid downloading multiple applications having the same name and virtual addresses for retained variables.
• I/O variable values are not updated when the I/O Device window is docked. [23479]
  Workaround: Force a refresh in the window by clicking on another IO device instance.
• Copying programs having wired array variables may cause an unexpected behavior in the Workbench. [23489]
  Workaround: In the copied program, delete the array variables.
• Copying FBD POUs from programs to function blocks may cause an unexpected behavior in the Workbench. [23175]
  Workaround: Copy subsets of the POU body between the sections.
• When opening an FBD POU while monitoring an application, tooltips are incorrectly displayed with the __MO_ prefix. [12990]
• 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. [23674]
  Workaround: Open all FBD POUs containing user-defined functions before debugging.
• When attempting to rename an IEC 61499 program to the same name as another existing program, an incorrect error message is displayed. [15283]
• You cannot monitor the values of arrays having a variable as index. [13775]
• When using ISaVIEW documents, you cannot access individual integer bits. [21097]
• When IXL communication with a target fails, do the following:
1. Test with the simulator (i.e., start simulation from the toolbar).
2. Make sure that "OPC Core components redistributable" item is installed (from the Windows Add/Remove Programs feature).
3. Add the DWORD "PortNumber" (e.g. 30000) value in the following registry [HKEY_LOCAL_MACHINE\SOFTWARE\ISaGRAF\CAMOPCServer], then set your target accordingly, i.e. ":\Program Files\ISaGRAF\ISaGRAF\6.X\CAM ISaGRAF 5\1.0\Win32_Large\isagraf.ini".
4. When running ISaGRAF runtime on a quad core computer system, set the CPU affinity to one core.

CAM 3

• Support for imported Instruction List (IL) programming in SFC may be incomplete. This programming is displayed in steps with header and footer delimeters as in ISaGRAF 3. [32780]
• After modifying an SFC program having SFC children, make sure to clean the project. [38297]
• When copying an SFC POU calling 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. [38344]
• For SFC steps and transitions, the renumbering feature applies the Sx and Tx naming convention used for CAM 5 SFC. [38136]
• When the data value for defined words exceeds the possible value range, the compiler may not specify an out-of-range error. [23568]
• Unloading then reloading a CAM3 library project is not recommended since this may cause an unexpected behavior in the Workbench. [23436]
  Workaround: Unload the library project, close the solution, re-open the solution, and then reload the library project.
• After running a project having a POU, then deleting this POU, the Workbench may not prompt to rebuild when restarting simulation. [23492]
• The compiler optimization options produce unstable results; avoid applying these options. [8311]
• When importing variables for a function, an extra variable named 'NewVariable' is also added. [38310]
  Workaround: Delete the extra NewVariable variable.

Corrected Anomalies

• CAM5 compiler throws an "Internal Error" when compiling the project (cause of crash unknown) [28557]
• Compiler error message does not correspond with the error when action names in SFC use a function block name [28572]
• "Unable to start debugging without first completing a successful build" even though build is up to date [30401]
• Syntax of the complex (initial) | (write allow) of value INSTANCE is incorrect [32216]
• Cannot enter simulation mode if Workbench (SPW -ScadaPack Workbench) is opened via Windows Explorer [34532]
• Variable object in the SAMA editor has lost its label reference "M" for (Monitored Variable) and "A" for (Alarm Signal) [37073]
• Different behavior between ISaGRAF 3(CAM3) and ISaGRAF 6(CAM3). User is unable to set a password for its application at any level (Project, POU, variables, Resource, ...) [25899]
• Field "Order" in I/O devices is empty [26108]
• ISaVIEW Page displays lookas if it is online while performing a download [26131]
• Cycle Timing toolbar refresh problems when going online [26149]
• Changing the "Order" value on the I/O Complex Equipment "Info" tab changes the UI focus (collapses the I/O board) [26151]
• Problem entering the FLOAT OEM parameter in the I/O board [26468]
• TicDasm generates the wrong constant number causing the CVT tool to declare a Warning, mismatch(s) detected in device* kernel* prog* [26955]
• Message pops up: "project data corrupted" after an attempt of import a project from ISaGRAF 5.13/5.22 to ISaGRAF 6.2/6.4 [27537]
• Russian Workbench crashes when the library is added as a dependency [29726]
• CAM3 or CAM5 projects build with ERROR if the number of parameters of a function block (Input + Output + Internal) is greater than 128 [30620]
• DBR crashes only when the browsing information has been generated and doing second time browsing [30870]
• Often, unexpected (and annoying) "failed to release restricted access" at the end of download/update [34622]

Functional Changes

• When installing the ISaGRAF 6.5 Workbench on a computer having a previous licensed version, the Workbench requires a new license activation. The installation process displays a message stating that the Workbench is running the free version. To activate ISaGRAF 6.5, please contact customer support.
• When installing a new version of ISaGRAF, the new communication settings defined in the OpcConfig.xml file are applied to the Workbench. If you experience communication issues, you are recommended to update the OpcConfig.xml file to the IxlTimeoutMultiFactor, ConnectRetryTimeInterval, and ConnectNoResponseTimeOut values defined in the previous Workbench version. [34411]
• When installing a new version of ISaGRAF, make sure to reset all Visual Studio settings by pointing to Tools, clicking "Import and Export Settings", then proceeding with the Reset all settings option in the Import and Export Settings wizard. [23937]
• The Controller Status feature is no longer available.
• The IL and FC programming languages are not implemented. You cannot open such POUs. [7661]
• When migrating to a more recent version of ISaGRAF, you need to retrieve new working copies of solutions from the repository. The Workbench displays messages stating the requirement for a source control upgrade for working copies from previous versions and does not allow opening such local working copies. [24253]
• For POUs created in ISaGRAF 6.3 or previous, you need to open a local copy, make a change, and save the POUs to ensure updating the XML files to the current Workbench version. ISaGRAF 6.3 or previous projects cannot be opened from a repository. [23951/24310]
• When using previous target versions, make sure not to use data types only available for these versions. The BYTE, USINT, INT, UINT, WORD, UDINT, DWORD, LINT, ULINT, LWORD, LREAL, and DATE data types are available for targets from version 5.0. [19473]
• From target version 5.60, the behavior of the LIMIT function has been modified to comply with the IEC 61131-3 standard. For example, where the minimum value is greater than the maximum value, the resulting output value is always the maximum value. For more details, refer to the online documentation for the function. [25573]
• From target version 5.23, the behavior of SFC steps having non-stored (N) action qualifiers has been modified to comply with the IEC 61131-3 standard indicating that such steps are executed while active and at deactivation (during final scan). In previous target versions, non-stored (N) action qualifiers were not executed at step deactivation. [23423/23696]
  Workaround: For applications having non-stored (N) action qualifiers in SFC steps not requiring the final scan execution for the action, you need to define the action code as conditional using the code condition of the following transition to eliminate the final scan of the step.
• The Matrix function block is incompatible with the failover runtime. A protection mechanism prevents using the Matrix block with the failover. When calling the Matrix block on a failover system, the protection mechanism returns error code 11 and nothing is performed. [RFS8717]
  Workaround: The Matrix2 function block is compatible with the failover runtime.

Application Notes

Installation

1. Make sure to have all hardware and software requirements on your computer.
2. Execute Setup.exe, then follow the on-screen instructions.
3. After installing the product, make sure to install the latest Windows updates.

All CAMs

• The current ISaGRAF Workbench is compatible with TortoiseSVN-1.8 and earlier versions. [16668]
• The following issues are corrected by installing the Visual Studio 2013 Update 5 available at "https://www.microsoft.com/en-ca/download/details.aspx?id=48129": [10559]
• The incomplete display of some or all toolbox items upon resetting for FBD, LD, SFC, or ST programming languages.
  Workaround: Without installing the update, close and reopen the Workbench.
• For the online help, hypertext links jumping to the top of the page rather than in the specific paragraphs within the same page.
• The inability to set the Workbench's all uppercase menu to mixed case.
• The wrongful inclusion of the non-implemented "Order Help on DVD" menu item from the Help menu.
• In the Customize dialog box for menu bar, toolbar, and context menu items, avoid applying the "Reset All" command since this operation may cause an unexpected behavior.
  Workaround: To remove effects from having applied the "Reset All" command, you can reset all environment settings to the default by choosing the "Reset all settings" option for the "Import and Export Settings" feature from the Tools menu. [27178]
• When the Workbench displays a message stating that the ACP has encountered a problem, please take the time to generate a report to help us improve the quality of our product. When generating a report, you can choose to capture and attach a screenshot. Upon generation, a dialogue box indicates the location and name of the report where you can choose to send the file to our support team. For such problems, make sure to close the Workbench without saving changes to your project and restart the Workbench to avoid corrupting files. [16503]
• When performing searches from the Solution Explorer to locate specific items within the tree structure, searches are case-insensitive for lowercase text in the search field. However, searches become case-sensitive upon entering uppercase text in the field. Microsoft claims this behavior is as designed: https://connect.microsoft.com/VisualStudio/feedback/details/1078288/solution-explorer-search-filter-is-case-sensitive-it-should-be-case-insensitive
• The Windows 8.1 x64 Russian operating system does not support the Visual Studio Isolated shell for the Russian language. Upon attempting to install the Russian bundle (web or full), the installation will be aborted. Please choose another language to proceed. [23464]
• Run single instances of the ACP (Automation Collaborative Platform); Running multiple instances has not been fully tested. Attempting such manipulations may cause an unexpected behavior in the Workbench. [1009]
• Solutions should only contain projects based on the same CAM type: CAM 3 or CAM 5. Mixing project types may cause an unexpected behavior in the Workbench. [23388]
• Toolbox icons are incompletely displayed when using a Windows display setting other than 100%.

CAM 5

• For the ISaGRAF Free Runtime on Windows 8 or Windows 10, the Workbench uses the following directories:
• Installing executable files (including ISaGRAF.exe):
  %PROGRAMFILES%\ISaGRAF\6.5\CAM ISaGRAF 5\5.3\ISaGRAF Free RunTime
• Downloading application files:
  %LOCALAPPDATA%\VirtualStore\Program Files (x86)\ISaGRAF\6.5\CAM ISaGRAF 5\5.3\ISaGRAF Free RunTime
• On Windows 8.1, you need to start the ISaGRAF Free runtime with administrator privileges: [23558]
1. From the Start menu, locate and right-click Start ISaGRAF Free Runtime.
2. In the contextual menu, choose Run as administrator.
• When opening a solution file (*.isasln) for the first time following the initial check in to a repository, the file is displayed in the Pending Changes window since the Workbench converts the solution file from UTF8 to Unicode format. [24462]
• All users of a same solution from a repository must use the same Workbench localization. Also, these users must not delete a network from the target definition (*.tdb) file. [24303/24335]
• Before committing changes, make sure to save all changes; committing is performed from the files on disk. [23805]
• Avoid renaming and deleting devices and resources using version source control. [23366]
• Avoid applying passwords to projects, devices, and resources using version source control. [24292/24297]
• When working with solutions using version source control, avoid deleting or renaming elements when importing exchange files. Only add new elements by importing. The importation process does not inform the repository of certain changes. [23626/23629]
• Before updating solutions from an exchange file or from a repository, make sure to close the I/O wiring view. [23965]
• Due to design changes between ISaGRAF 6.2 and ISaGRAF 6.4, the custom settings for POUs were integrated in the *.Isaxml files for the individual POUs rather than in a separate *.acfmlge file. A project is automatically updated upon opening in the current version. [23087]
• When performing a get latest or get specific operation for a solution where another user has deleted elements, these elements may be displayed in the Pending Changes window. To clear the deleted elements from this window, close and reopen the solution. [24304]
• When using version source control, make sure to perform operations using the following good practices: [23384]
• Synchronize your current working copy with the repository version by always getting the latest revision from the solution root element.
• When adding elements to the Solution Explorer, save all and commit elements while including meaningful comments via the Pending Changes window. Only use the workbench to manipulate the repository; do not use external tools.
• In Windows explorer, only double-click solution files to open the solution. Do not double-click other file types.
• Use the Update to Specific Version command only to update element versions of functions, function blocks, programs (other than SFC having children), and ISaVIEW screens
• Avoid using the External Merge tool
• To prevent stealing locks from other users, clear the "Automatically lock files on change without user confirmation" option. Avoid stealing locks except when absolutely required, for instance, when a user having the elements checked out is no longer available.
• When creating elements, avoid applying names having more than 32 characters since this may cause to exceed the maximum path names supported by the Microsoft Windows operating systems.

CAM 3

• For the ISaGRAF 3 target on Windows 8 or Windows 10, the Workbench uses the following directories:
• Installing executable files (including start tcp.cmd):
  %PROGRAMFILES%\ISaGRAF\6.5\CAM ISaGRAF 3\Simul
• Downloading application files:
  %LOCALAPPDATA%\VirtualStore\Program Files (x86)\ISaGRAF\6.5\CAM ISaGRAF 3\Simul
• The Workbench cannot load projects having invalid names. Valid project names must begin with letters followed by letters, digits, and single underscore characters. Names cannot be reserved words or data types (i.e., defined words or arrays). [26526]
• SFC POUs can only be viewed in read-only mode; such POUs cannot be edited. [26061]
• The Workbench does not support projects having SFC macro steps (macro beginning steps, macro steps, and macro ending steps). [26361]
• The Cross References Browser does not display cross references for CAM 3 SFC POUs.
• When importing ISaGRAF 3 projects, you need to choose a folder other than where the *.hie file is located. Attempting such manipulations may cause an unexpected behavior in the Workbench. [23358] Before importing, make sure your ISaGRAF 3 project folder has a maximum of eight characters. Device names having more than eight characters cause unknown compilation errors. [23435]
• The values of unused variables are displayed as Offline. [23491]
• Column headers for local and global variables are not localized for product language versions other than English. [19446]
• To enable simulating CAM 3 projects, you need to run the Workbench with administrator privileges: [9294]
• From the Start menu, locate and right-click the ISaGRAF Workbench, and then click Run as administrator.

Contacting Us

• Visit our website www.isagraf.com
• Send an e-mail to isagraf_support@ra.rockwell.com
• Send a fax to +1 450 445-3426
• Call +1 450 445-3353
• Call toll free +1 877 868-4746