Release Notes - ISaGRAF 6.1
---------------
New Features
---------------
Migration to Visual Studio 2010 Shell
======================================
The ISaGRAF 6 workbench has migrated to the Microsoft Visual Studio 2010 shell. Solution files (.isasln) are automatically converted to this platform. Before opening your solution in the current ISaGRAF 6 workbench, you should make a backup copy to enable rolling back to the ISaGRAF 6.0 workbench version.
CAM3
====
Enables importing and creating ISaGRAF 3 projects in the ISaGRAF 6 Workbench.
- Libraries can be imported but you can only modify functions and function blocks
- POUs can be programmed using the FBD, ST, and LD languages
Integration of the IEC 61499 Programming Language
==================================================
The ISaGRAF 6 workbench supports the IEC 61499 programming language.
Version Source Control
=======================
A version source control enables managing the changing versions of ISaGRAF elements such as solutions, projects, devices, resources, programs, and ISaVIEW screens. This source control is based on the Subversion AnkhSVN source control plug-in for Visual Studio developed by * CollabNet (http://www.Collab.Net/).
Failover mechanism
===================
A failover mechanism provides a redundancy scheme for projects developed in the workbench.
Interrupt
==========
The ISaGRAF 6 workbench enables the use of interrupts for managing program execution.
Dependency Tree
================
The dependency tree enables viewing all ascending and descending dependencies of a variable on other variables within an application. Dependencies are available after having built the cross references for a project.
Block Library
==============
A block library graphically displays all available functions and function blocks for direct insertion in FBD POUs. You can also sort the blocks by alphabetical order, scope, or category.
Parameters View
================
The parameters view provides a graphical display of the defined parameters for a block. This view enables adding and removing inputs, outputs, or variables from blocks.
--------------------------------------------------------------------------------------------------------
Release Notes - ISaGRAF 6.0.3
---------------
New Features
---------------
SFC Editor
==========
The SFC Editor is available and follows IEC 61131-3 recommendations while supporting the following features:
- Display of level1 and level2
- Possibility to split level1 and level2 horizontally or vertically and to swap
- Possibility to view all actions and transitions of an SFC POU within the same level2
- Programming of actions and transitions available in LD and ST
- Full support of keyboard shortcuts and mouse controls
- Unlimited undo/redo
- Zooming into POUs
- Support breakpoints on activation and deactivation
- Forcing transition
- Possibility to debug level2
Device View
===========
Device view provides an alternative to the Solution Explorer by enabling a graphical navigation through the devices of any project. The Device view supports the following features:
- Display device target features
- Display device target supported C function blocks
- Display device target supported IO devices
- Provide same commands as the Solution Explorer
- Enables creating parameters for function blocks (modification of parameters is performed via properties)
- Provides a Windows 7 breadcrumb control
- Available for use with Navigation Windows
Document Generator
==================
Enables generating MS Word document of a selected item (context from Solution Explorer or Device View)
Enables selecting portrait or landscape orientation and scaling image to fit to page
The current version is basic and several enhancements are planned for future releases.
Description Windows
====================
Plug-ins displaying all descriptions for projects, devices, resources, programs, and comments within LD and FBD programs in a RTF format. These windows enable insert hyperlinks, images, and foreign language fonts.
------------
Improvements
------------
Spy List
========
Selecting spy list for which to add new variables
Binding Editor
==============
Automatically generate bindings between tables
--------------------------------------------------------------------------------------------------------
Release Notes - ISaGRAF 6.0.2
Localization
============
Localization of the user interface (UI) is included for the following languages: English, French, Italian, Spanish, German, Chinese Simplified, Chinese Traditional, and Japanese. To make all languages available, you need to install all different languages using the language pack in the installation.
Once installed, users can change the UI localization from the command "Tools/Option/Environment/International setting" then restarting the Workbench.
To localize the Workbench for a specific language, the prerequisite (isolated shell) and the workbench must be installed for that same language. Otherwise, known anomalies for the Visual Studio shell will cause the menu items to display in another language (usually the language of the first installed isolated shell).
Binding Editor
==============
A binding editor enables the creation of producer and consumer groups for individual resources of a project. All bindings in ISaGRAF 6.0 are considered as external bindings.
Users are then able to create producer groups without knowing in advance who will consume these.
Bindings can be defined locally within a solution or between different solutions.
The next version release will include some minor adjustments in regards to bindings between resources within a given device where users need to manually select HSD networking.
Password-Protection
===================
Password protection where users can specify a password for projects, devices, resources, and POUs.
Setting a password on a POU prevents other users from visualizing the source code and encrypts the file.
Setting a password on a device prevents users from accessing the controller for downloading, debugging, and uploading purposes.
The next version release will include a correction for a known issue regarding a limitation when setting passwords for resources does not encrypt all the POU attached to it.
Libraries
=========
Libraries are available for use with CAM5 projects. The concept remains the same as that of ISaGRAF 5 library usage. User can create multiple library projects (using the library template). All of these libraries become accessible for a project from the Dependencies interface. This interface enables searching, browsing, clearing, and viewing most used libraries.
Spy List
========
Spy lists enable debugging groups of variables. Users can create multiple spy lists which can be fully customized (refresh rate, colors, columns, filter, etc. ...)
In addition to selecting variables in the spy list, users can also drag and drop variables from the dictionary. From the editor, users can add any variable to the spylist.
Import-Export to Excel
======================
An Import/Export plug-in enables importing and exporting variables to/from an Excel spread sheet.
This plug-in is CAM-independent and displays all properties for the variables to export or import.
A future release will support other import/export formats such as CSV or XML.
Forcing Variables
=================
While running on-line or simulating, a new interface enables writing to variables. This interface provides specific filters depending on the type of variables.
To facilitate entering the correct value, the Workbench includes some controls such as a date picker and a push button for Boolean variables.
Users can access this interface while running on-line or simulation by double-clicking a variable in the editors (Languages Editor and Grid).
Debugging Function Block Instances
==================================
The Workbench enables debugging individual instances of function blocks.
All instances including nested function blocks are debuggable. When applicable (ST and LD), users can insert breakpoint.
To enable debugging a function block instance, users double-click the instance in the editor.
Instruction Block bitmaps
=========================
ISaGRAF 6.0 enables OEMs and users to add images to a blocks (operator, functions, and function blocks).
All images are located in directory ..\ISaGRAF\ISaGRAF\6.0\ACP\1.0\PackagesToLoad\Images and supported format are: Bitmaps, JPEG and PNG.
The association between blocks and images are defined in the MLGEsettings.xml file located in the user directory.
C:\ProgramData\ISaGRAF\ACP\1.0 (Under windows 7)
C:\Documents and Settings\All Users\Application Data\ISaGRAF\ACP\1.0 (under Windows XP)
In the POU info section, the following information must be defined
POUName = Name of the operator, function or function block that appears in the MDB database of the project
DisplayName= Name displayed in the graphical editor such as FBD, SAMA, and LD
Image= Image to include in the block
Anchor= Relative location in which to display image. Possible values are TOP, MIDDLE, or BOTTOM
...
Example
--------------------------------------------------------------------------------------------------------
Release Notes - ISaGRAF 6.0.1
Tips
====
A tutorial has been added which is accessible from the Startup page or directly in the ISaGRAF installation.
The free version license has the following limitations:
- ISaFREE template only
- ISaFREE-TGT run-time is provided in the CAM directory
- Creating/opening of projects using the ISaFREE Target (Only)
- Importing target definitions is unavailable
- Downloading only to IsaFREE targets
- Compiler limits the TIC code size to 3K for ISaFREE targets
- Free version has unlimited time usage
- All other features are available
--------------------------------------------------------------------------------------------------------
Release Notes - ISaGRAF 6.0
Users of previous versions
==========================
For details on differences with previous ISaGRAF versions, consult the Getting Started documentation, included in the online help.
Internal bindings are converted to external bindings.
Before importing a project from a previous ISaGRAF version into the ACP (Automation Collaborative Platform), remove all project and POU passwords from the project. Also, make sure to back up your project since changes following importation cancel the ability to reopen with ISaGRAF 5.22 or earlier.
The import/export file (embedded zip source) produced by the ACP is not compatible with ISaGRAF 5.
In the Properties window, the "Enhanced Target" property for devices must match the target capability: True for the ISaGRAF 5.23 target and False for earlier target versions.
Tips
====
ISaGRAF is only available in English.
This ISaGRAF version is limited to run up to December 31st 2010. Make sure to set the correct date on the computer before installing.
Before installing ISaGRAF, make sure to install all Windows updates.
The ACP requires using an administrator account for the operating system.
You can reset the toolbox to display language editor elements or to recover deleted elements.
You can only simulate one project at a time.
When running a target locally, you need to define an ETCP network with an IP address defined as 127.0.0.1. The ACP does not support the HSD network.
To recover the ACP installation following an error such as "package load feature", use the following command:
:\Program Files\ISaGRAF\ISaGRAF\6.0\ACP\1.0\ISaGRAF.Acf.Core.Shell.VsStub.exe /setup
The Output window displays all errors; Errors are not always displayed in the Error window. Always check for ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ========== to ensure correct results.
You can reset the layout of the ACP from the Import and Export Settings Wizard using the Reset all settings option, available from the Tools menu.
You can improve the layout of the FBD editor using the Layout Diagram command from the Edit menu.
When running a target locally, you need to define an ETCP network with an IP address defined as 127.0.0.1. The ACP does not support the HSD network.
The ACP produces various log files providing diagnostic information in the following directories:
:\Documents and Settings\All Users\Application Data\ISaGRAF\
If you encountered issues, zip this entire folder and your project, then send these to ISaGRAF.
To monitor the state of a function block, create a manual instance of the block and monitor its state from the dictionary.
Closing all documents may accelerate stopping the debugging process.
Known Issues
============
Using the ACP on a 64-bit operating system is unstable.
The ACP does not ISaGRAF 3 targets.
The ACP does not support libraries.
The SFC, IL, FC and IEC 61499 programming languages are not yet implemented. Opening such POUs presents an empty document.
The ISaGRAF 5 equivalents for ISaView, Document Generator and source control are not yet available.
You cannot currently perform step-by-step debugging and monitoring in instances of function block POU bodies.
Open projects from the Open Project\Solution command from the File menu; Opening projects by double-clicking the *.isasln or *.isaproj files in Windows Explorer may produce an incorrect result.
Save projects regularly when editing. The ACP sometimes stops unexpectedly and all changes are lost.
Run single instances of the ACP (Automation Collaborative Platform); Running multiple instances has not been fully tested.
You can currently only wire simple variables in the I/O wiring tool; you cannot wire arrays.
When IXL communication with a target fails, do the following:
a) Test with the simulator (i.e., start simulation from the toolbar).
b) Make sure that "OPC Core components redistributable" item is installed (from the Windows Add/Remove Programs feature).
c) 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.0\CAM ISaGRAF 5\1.0\Win32_Large\isagraf.ini".
d) When running ISaGRAF runtime on a quad core computer system, set the CPU affinity to one core.
When the ACP produces an error or exception, close and reopen the solution. The ACP may become unstable. In such a case, send the diagnostic files previously mentioned to ISaGRAF.
The online change feature is currently unstable; Improvements to come soon. Cleaning a project cancels the ability to perform online changes .
Avoid creating elements in the Solution Explorer that can produce file paths having more than 255 characters. The verification process is not yet implemented.
Perform builds and downloads from the Solution Explorer. Avoid using toolbar commands since these are possibly defined with an incorrect context.
When setting a new name in the Save As project command, retain the acfprog suffix.
Monitoring structures at level 3 and over is not yet functional.
Contacting Us
Visit our web site at http://www.isagraf.com or contact our location nearest you:
North America
=============
- Send an e-mail to isagraf6support@isagraf.com
- Send a fax to +1 450 445-3426
- Call +1 450 445-3353, press 9 for service in French
- Call toll free +1 877 868-4746, press 9 for service in French
Europe
======
- Send an e-mail to isagraf6support@isagraf.com
- Send a fax to +33 (0)4 76 41 35 61
- Call +33 (0)4 76 04 81 75