Release Notes - ISaGRAF version 5.22 Users of Previous Versions ========================== The Workbench does not support targets having the advanced options. To use the Advanced Options, you need to use ISaGRAF 5.12 with the 5.13 SP 2 patch or an earlier version. The WIN32-TGT and WIN32-TGT_L replace the NT-TARGET and NT-TARGET_L targets. The new targets support 64-bit data types such as LINT, ULINT, LWORD, and LREAL. Whereas, the NT-TARGET and NT-TARGET_L targets support up to 32-bit data types such as DINT, UDINT, DWORD, REAL, TIME, and DATE. To use the new targets supporting 64-bit data types in an existing project, you need to import the new target (WIN32-TGT.tdb or WIN32-TGT_L.tdb), then select it for use in the configurations properties. To update a custom-ported target to use the 64-bit data types, in addition to merging the changes between the target source code, you need to redo the alignment options for the target. If the alignment options results differ, you also need to use a different target name for compatibility reasons. Within an SFC POU, the names of steps and transitions must differ from those for variables. When using bindings with targets from previous versions, you need to add the following entry in the [Settings] section of the Workbench’s Diamond.ini file, located in the Bin folder: LegacyBindingsDefault=1 The default font used in Flow Chart diagrams is currently set to 16 points. To set the default font to a larger size, from the Options menu, choose Customize, then select the FC editor in the list and specify the point size, then click OK. RXF file version and workbench version must match to allow the RXF importation. When installing a more current version, previous templates are updated. When uninstalling and reinstalling the Workbench, demo projects are replaced. All drivers as well as all optional function and function block packs installed for previous versions must be reinstalled using the latest .v2k files. When choosing to update a Workbench project, a backup copy of the project, prjLibrary.bak, is automatically created in the project_name directory. Significant Enhancements ———————————————————————— Version 5.22 ===================== You can adjust the spacing above and below elements in the workspace for LD programs by increasing or decreasing the height of grid cells. These commands are available from the Options toolbar. The compiler options enable optimizing the generated TIC code. Optimization performs many tasks: removes unused temporary variables, replaces each constant expression with its result, replaces repeated expressions and sub-expressions with their equivalent values, suppresses unused and surplus target labels and null jumps, and simplifies arithmetic operations. In the Variable selector, you can specify a bit from a variable for use as a Boolean value. The PRDK enables adding custom project templates as available options when importing and converting ISaGRAF 3 projects. Version 5.21 ===================== For ISaGRAF 5.21 and later, only the *.PXF file format is supported when exporting. The Workbench, license manager, and OPC DA server are compatible with the Microsoft Windows Vista operating system. The ISaVIEW screenbuilder is included with the Workbench. Version source control is available for projects and libraries. The Workbench is available in Simplified Chinese. You can import ISaGRAF 3 projects into the Workbench. The compilation speed of ISaGRAF 3 projects is improved. You can export target definitions from the Workbench. You can import multiple POUs at the same time. You can import and export defined words using the comma-separated value (CSV) format. Furthermore, when importing using the CSV format, you can choose to replace variables and/or defined words. You can import global variables as sub-elements of resources. When importing sub-elements of resources, these elements are appended within the project, i.e., unique elements remain intact, duplicate elements are replaced, and new elements are added. For POUs, these can be replaced or appended. When exporting a project, you can export either the entire project or its defined words. For ST POUs, line numbers are displayed at the left of each programming line. The line numbers are also printed when printing documents. The cross references browser lists and enables locating all automatic and declared function block instances in a project. You can force the values of variables from the spy list. From the spy list, the lock status of variables is displayed. In the ST editor, basic coding is black while other syntax items are displayed using color: keywords are pink, numbers are brown, comments are green. The Propi implementation includes the ProChangeTarget , ProDisplayStatus, and ProUnlockRes functions. The ProHook library includes the ProhookAfterPrjLoad, ProHookBeforeTargetChange and ProHookBeforeDebugMode functions. When importing a project from within the Workbench, the ProHookAfterPrjLoad function is called. This function was previously only called after opening an existing or new project. Version 5.13 ===================== Compilation verification is currently available for FBD POUs where the POU STF file is compared with its TIC code. Errors are displayed in the output window. Version 5.12 ===================== For I/O wiring, you can specify the range of a simple device within a complex device when defined as such for a target. Such target definitions are configured using the Target Definition Builder. Tooltips displaying information such as data type and comments are available for variables and function blocks. While debugging or simulating, you can temporarily resize variables to enable viewing their output values; variables return to their original size upon returing to editing mode. The cross references browser provides the direction for variables. You can save version source control information to a repository using one of two modes: - file mode where you specify a path for a local or remote computer - client/server mode where you specify login information and server location You can also clear the version source control status for a project. Version 5.11 ===================== You can import an ISaGRAF 3 library into an ISaGRAF 5 project for use with ISaGRAF 3 configurations. You can import the I/O connections (wiring) from ISaGRAF 3 projects into an ISaGRAF 5 project. For ISaGRAF 3 configurations, only the available data types, functions, function blocks, programs, and password protections are displayed. Version 5.1 SP1 ===================== Online changes where bindings are involved support creating new links between resources, deleting existing links between resources, creating bindings between variables, and deleting bindings between variables. Online changes support wiring new I/O variables, unwiring existing I/O variables, and moving wired I/O variables where the following properties are not modified for these variables in the dictionary: type (scalar type for arrays), length (STRING variables only), dimension (array variables only), retain, and address. Note that modifying the I/O wiring causes the values of new and removed output I/O variables to be reinitialized. Also, virtual addresses are tied to channels; when wiring, unwiring, and moving an I/O variable, the virtual address for the channel is reassigned to the substitute I/O variable. Version 5.1 ================= ISaGRAF supports ISaGRAF 3 targets (Beta version). You can edit, build, download and debug an ISaGRAF 5 project on an ISaGRAF 3 target. Before starting such a project, make sure to read the differences.pdf file detailing the differences between ISaGRAF 3 and ISaGRAF 5 configurations. The Workbench supports IEC 61499 composite function blocks using the FBD language rather than ST. You can switch between user interface languages (English, French, Japanese, Russian, and Spanish) from within the Workbench. You switch between languages from the Customize dialog. You must restart the Workbench to apply language changes. POUs declared in a library can be debugged while debugging a project. You can choose whether to display comments under all variables and function blocks in the LD and FBD editors. You can create instances of function blocks (local variables, global variables, and function block parameters) directly in the Select Block dialog. The variable selector offers more filtering capabilities. Defined words values are displayed in LD and FBD diagrams while in debugging. The find and replace feature offers more scopes for searches. Floating licenses are available for the Workbench and Windows 32 run-time. New service interface function blocks are available for IXL and HOLOBLOC. The IXL_Service_Interface.pdf and Holobloc_Service_Interface.pdf files provide usage information. The PRDK includes a generic Openmodbus server and Openmodbus client TCP-IP generic I/O driver. The PRDK includes a QNX6 CANBUS driver. This driver has been developed for the ESD Electronics CAN-PCI/331 board with the driver V3.6 for QNX V6.2. Version 5.0 SP2 (5.00.004) ===================================== Licensing for ISaGRAF is available as floating licenses where multiple ISaGRAF instances can be installed on a network but only the number licensed can be in use at any given time. When using an advanced options target, the refresh rate of the OPC server is twice as fast. Version 5.0 ================ ISaGRAF supports the IEC 61499 distribution method. ISaGRAF supports many new IEC 61131 data types: USINT, BYTE, INT, UINT, WORD, UDINT, DWORD, LINT, ULINT, LWORD, LREAL, and DATE. ISaGRAF includes HiBeam 1.3 supporting the many new IEC 61131 data types Compilation speed improved by 100 percent since version 4.20 OPC server has improved speed A project contents navigator displays a project’s structure and enables accessing most aspects of the project. A distribution view enables overseeing the distribution of IEC 61499 programs across multiple resources of a project. You can customize the colors and fonts of many more items in the Workbench views and editors. You can also set preferences such as the number of recent files to display in the File menu and always prompting before saving changes to projects. You can replace the configuration representation in the hardware architecture view with a custom bitmap. Project documents generation is performed using Microsoft Word version 2000 (9.0) or later. For project items such as diagrams, you can print using the landscape orientation. You can also print on multiple pages. Simplification of SFC level 2 programming. The Workbench and editors offer a current look and feel. Linux targets run on the Linux 2.6 kernels for Intel and PowerPC processors. Known Issues ———————————— Installing ISaGRAF ====================== When installing, you may receive a message stating that the installation is unable to initialize Microsoft components (i.e., Jet, DAO). Click OK and proceed with the installation. When installing on Windows 2000 SP1 or Windows XP SP1, you need to manually install the Sentinel driver. When using the NT-TARGET_L target, make sure the target and Workbench project have the same definition in regards to the advanced options. For example, either both target and project definitions are using the advanced options or both target and project definitions are not using the advanced options. You can update the installed Sentinel drivers to version 7.2.2 by double-clicking the Sentinel Protection Installer 7.2.2.exe file, located in the Sentinel folder at the root of the ISaGRAF CD-ROM. When reinstalling ISaGRAF, you need to make a backup copy of the Diamond.ini file, located in the ICS Triplex ISaGRAF\ISaGRAF 5.0\Bin folder. In the case where certain files created while in demo mode remained encrypted, the Diamond.ini and the encrypted files could be sent to our support team for decryption. When ISaGRAF Enhanced 2.4 or 4.21 is installed on your computer, you can only install the ISaGRAF 5.X Workbench without advanced options, other ISaGRAF components, or third-party products. You can use Microsoft Access 97 to modify the ISaGRAF database; you cannot use a more recent version. If the Alarms & Events Pro Suite installation process malfunctions, verify that the DCOM properties' Default Impersonation Level is set to Identify. To set the Default Impersonation Level to Identify, complete the following steps: 1. From the Windows Start menu, choose Run. 2. In the Open field, type dcomcnfg, then click OK. 3. Access the default properties for your computer: - For Windows NT or 2000, in the Distributed COM Configuration Properties window, select the Default Properties tab. - For Windows XP, in the Components Services browser, fully expand the Component Services item up to My Computer, then right click My Computer, choosing Properties from the contextual menu, then select the Default Properties tab. 4. In the Default Impersonation Level field, choose Identify, then click OK. Using ISaGRAF ============== When using a 64-bit operating system for the development platform, you need to update the Sentinel driver to version 7.5.0. The Sentinel driver updates are available at the following web address: http://www.safenet-inc.com/support/tech/sentinel.asp To use ISaGRAF, you must have administrator rights on the development platform. For Windows XP Home, you need to modify the security permissions for restricted users: 1. Download the Security Configuration Manager Tool (x86 (Intel version) is SCESP4I.EXE) from Microsoft at the following location: ftp://ftp.microsoft.com/bussys/winnt/winnt-public/tools/scm/SCESP4I.EXE 2. Double-click the SCESP4I.EXE file and extract the contents to a folder on your hard disk. 3. Browse to the folder where you extracted the contents of SCESP4I.exe and locate the Setup.inf (Setup Information) file. 4. Right-click the Setup.inf file and choose Install. 5. Restart the computer when the installation is completed. 6. For each of the following directories, set the security permission to allow full control to users: :\Documents and Settings\All Users\Application Data\ICS Triplex ISaGRAF :\Documents and Settings\All Users\Documents\ICS Triplex ISaGRAF a) In Windows Explorer, locate and select the directory, then right-click and choose Properties from the contextual menu. b) On the Security tab, in the Permissions for Users section, check Allow for the Full control option. 7. Start the Workbench. Licensing ========= The startup options for primary and secondary licence servers used with floating licenses are not currently available. Workbench ========= To use ISaVIEW, you need to install Sun MicroSystems’ Java SE Runtime environment. You can install a version from the Workbench CD-ROM. However, you can download the latest version from the Sun MicroSystems’ web site. In the ISaVIEW screen builder, the following system variables are not functional: SYS_DATA_SERVER, SYS_PLC, SYS_VARIABLE, SYS_PASSWORD. When viewing the ISaView interfaces in the provided demo projects, the buttons for these system variables will not display their values. Before creating an ISaVIEW project for a Workbench project having ISaGRAF 3 configurations, you need to recompile the Workbench project. In the ISaVIEW interface, you can add all objects other than trend graph objects while in debug or simulation mode; You can only add trend graph objects while the Workbench is in editing mode. When using the Propi implementation, the Workbench does not display messages in the output window when building projects, resources, or POUs. The Propi implementation does not support ISaVIEW. When modifying existing structures, you can edit the contents of the fields and add fields to the bottom of the structure; you cannot move or delete fields. The interface menus and messages as well as the documentation for the French, Russian, and Japanese language versions are localized up to version 5.0 SP2. Furthermore, for the Japanese version, the documentation images are displayed in English. While in debug or simulation mode, you can unlock POUs from the Workbench. However, when switching to edition mode, the POU remains in read-only mode. Unlocking POUs from the multi-language editor may cause the Workbench to malfunction. While running the Workbench and an IXL client on the same computer, receiving a warning stating that an IXL client is already running indicates that you need to either reload the symbol table or disconnect and reconnect to the IXL client. When using breakpoints in SFC diagrams, you need to stop debugging from the SFC editor to remove these. When adding instances of function blocks from libraries into a project for the first time, make sure to clean the project before building. When renaming resources or configurations having instances of function blocks defined in IEC 61499 programs, you need to reselect these instances. POU files having future dates are always recompiled. To avoid repeated recompilations, edit and save these files to bring them to a current date. When using the same name for a defined word in a library and for a variable in a project, while in simulation or debug mode, the value displayed for the variable is incorrect. However, the simulator and target are using the variable’s correct value. Compiling an IL delayed operation that is not preceded by an LD operation produces an internal error. When using the PROPI client, you need to set the screen resolution to less than 1024 X 768. The lower resolutions enable displaying all of the PROPI features. You cannot change an IP address then download to a target without having previously recompiled the project. You cannot delete networks defined for use with bindings. Before creating a dependency on a library in a project, make sure the library has been updated to the Workbench version. You update libraries by opening them in the Workbench. For previous versions, when using the targets with advanced options included on the ISaGRAF CD-ROM, you should also install the advanced options module for the Workbench. For a target with advanced options, you need to check "Download advanced options features” in the configuration’s target definitions properties. To use a target with advanced options and not install the advanced options module for the Workbench, you need to check Embed Symbol Table (Complete) in the resource’s compilation options. To use the NT target with advanced options on the same computer running the Workbench, you must first start the target. When switching a Workbench project (with advanced options) running on Windows XP Pro with service pack 2 to simulation mode for the first time, you need to allow the ConfigurationManager.exe file to pass through the Windows firewall. When converting a REAL constant value to an LREAL variable, using an implicit conversion, the result is not accurate. The workaround is to use a temporary variable (having the LREAL data type) to store the REAL numerical value to ensure the proper data type is used for the operation. For instance, the "u1 := 1.2 - 0.1;" line of code yields the 1.10000002384186 value. In the following ST code, the t1 and t2 LREAL variables store the REAL numerical values and enable the correct conversion to LREAL: LREAL u1; LREAL u2; LREAL t1; LREAL t2; t1 := 1.2; t2 := 0.1; u1 := t1 - t2; (* u1 is equal to 1.1 *) u2 := 1.1; (* u2 is equal to 1.1 *) For version source control, the combined project path and name of a Workbench element must not exceed 230 characters. For instance, the following POU and its path containing a total of 88 characters including spaces is acceptable: C:\Users\Public\Documents\ICS Triplex ISaGRAF\Projects\ISaGRAF 5.2\Prj\Demo + config1.resource1.pou1 However, for extended project paths, you could map a drive. The version source control feature is not available for use with library projects. You must not edit any files contained in a project’s VSC folder. When printing documentation for a project, make sure Microsoft Word is not in use for any other task. Furthermore, when using Microsoft Word version 2000 without any service packs, to ensure the correct alignment of headers and footers, do the following: 1. Using a text editor such as Notepad, open the Diamond.ini file located in the ICS Triplex ISaGRAF\ISaGRAF 5.2\Bin folder. 2. In the Settings section, change the value of the Word Updated parameter from 1 to 0. When performing on-line changes, the symbol table is sent to the target (when checked in the resource properties). When opening projects, if the Open in single-resource mode option is not available, do the following: 1. Using a text editor such as Notepad, open the Diamond.ini file located in the ICS Triplex ISaGRAF\ISaGRAF 5.2\Bin folder. 2. In the Settings section, change the value of the OpenProjectWithAdvanceOption parameter from 1 to 0. While in single-resource mode, when switching to simulation mode or attempting to download a resource to which you added a POU then recompiled the resource, you will be prompted with a message stating that the project was not compiled with the latest changes then asked whether you would like to compile it. Click NO and the requested task will proceed. When using the FBD editor, to improve scrolling speed in large POUs, you can choose to not generate the dots indicating wiring intersections, do the following: 1. Using a text editor such as Notepad, open the Diamond.ini file located in the ICS Triplex ISaGRAF\ISaGRAF 5.2\Bin folder. 2. In the Settings section, change the value of the ShowWiringIntersectDots parameter from 1 to 0. When importing resources, the target type of an imported resource must be the same as the destination target type. When replacing variables data by importing, bindings previously defined for those variables are not preserved. When exporting variables data for a resource whose name appears more than once within an application, the variables data for all instances of this resource name is exported. Workaround: Within an application, assign unique names to all resources. When the Workbench is connected to a target in debug mode and used to stop and start resources, you may encounter communication problems with the target's CMG (ConfigurationManager) where a message appears in the output window stating one of two situations: - Get Active resource from CMG has failed: Request sent but DTA timeout on acknowledgment. - Get Stored resource from CMG has failed: Request sent but DTA timeout on acknowledgment. Stopping and restarting the Workbench, without tampering with the target, should correct the situation. You cannot retain the values of structured variables. You cannot bind individual members of arrays or structured variables. When using complex types for output parameters of function blocks, you can only connect these outputs to other block inputs or variables having the same structure type (not a variable field). You cannot use complex types for outputs of functions. You can also assign a complex-type variable to another variable of the same type (a variable! not a field or an element of a variable). For example, if OutStruct is an output parameter of a block having a structure type, YOU CANNOT DO: OutStruct.field1 := 10; In such a case, declare a local parameter having the same type and work on this local parameter, then at the end of the block, you do: OutStruct := LocalStruct; When using the IL language, the following limitations exist: - You cannot use arrays and structures in IL programs. - You cannot program or call functions and function blocks in IL. - You cannot use the IL language in SFC transitions. For information on substituting for other languages, contact technical support. When trending (advanced options), individual nodes on a network timestamp the events they generate using their local clock time. Therefore, to ensure that timestamping uses a standardized time, all nodes should use the same time zone. When using alarms and events (advanced options), you cannot move resources having alarms defined. Workaround: You can copy and paste these resources. While in debug mode, you cannot access the advanced options for configurations or variables. Before setting initial values for I/Os in a structure, you need to unwire them. When using field communications (advanced options), to change the protocol type of a specific driver, you can either create a new one with the desired type then delete the first or use the importing field communications functionality to import replacement data. To use generic devices with advanced options, double-click the GenericIOWiring.reg file located in the ICS Triplex ISaGRAF\ISaGRAF 5.0\Bin folder. Failover mechanisms (advanced options) may not be compatible with all communication drivers. For information on which drivers are compatible, contact Technical Support. When setting up a failover mechanism (advanced options), make sure that the cable used for the parallel port remains secure and isolated from physical damage. If the cable becomes disconnected, the failover mechanism remains inoperative until the cable is reconnected and the secondary node restarted. The mechanism proceeds as follows: 1. Both nodes become active. 2. When the secondary node becomes aware, via the network link, that both nodes are active, it switches to the indefinite standby mode, incapable of becoming active. 3. The primary node remains active and the HMI automatically connects to it. 4. When the FAILOVER ST function is used, it informs the active primary node that the secondary node is no longer operational. This information can then be displayed in the HMI. When using a failover mechanism (advanced options) for a target node, you can only perform complete download operations; you cannot perform partial downloads, consisting of changes made since the last complete download operation, using the On-line Change: Download option. Also, stopping and starting resources only affects resources located on an active primary node; these features do not affect resources located on a standby primary node or on a secondary node. Furthermore, all I/O points used for the heartbeat of a failover mechanism must use the same communication driver. ISaGRAF 3 Projects ================== When running ISaGRAF on Windows XP 64 or Vista 64, you cannot compile and simulate ISaGRAF 3 projects. The following array TIC codes that typically appear when using arrays as function block local variables are available only when using isagraf 3.5x targets: TIC_A3B_ARRAY 0xf7 /* boolean array a := b [size]*/ TIC_A3I_ARRAY 0xf8 /* ana array a := b [size]*/ TIC_A3R_ARRAY 0xf9 /* real array a := b [size]*/ TIC_A3T_ARRAY 0xfa /* timer array a := b [size]*/ When compiling for ISaGRAF 3 targets, you must close the ISaGRAF 3 Workbench when using a version prior to 3.55. For version 3.55, you must also close the ISaGRAF 3 Workbench code generator program. When using the BOO operator (for ISaGRAF 3 configurations), to use an input variable having a data type other than DINT, you need to manually approach the variable element to the operator. Using a link element to connect both elements shall result in a validation error. When reviewing compilation errors, error coordinates do not correspond to editor coordinates. Online help is not available for the ISaGRAF 3 simulator. You can embed zip sources of ISaGRAF 3 configurations onto targets. However, you can only upload these sources using the ISaGRAF 3 Workbench. Run-time Event Logging ====================== The selection of the basic logger and viewer or the full alarms and event management option applies to the Workbench. Therefore, when switching between projects using different event logging options, you need to reselect the option. The Windows 2000 platform on which the alarms server runs must be set to use the English (United States) regional setting. Otherwise, you cannot assign operator help files to appear with alarms and events or view these help files. Furthermore, you must have installed Networking Services. If not running on a network, make sure you used the Null device. You can start and stop the alarms server service using the Services applet in the Windows NT control panel or the Alarms & Events Server Control application. However, ICS Triplex ISaGRAF recommends using the Alarms & Events Service Control application because it provides more information about the server’s status and offers many features not available in the standard Windows Services applet. For the Alarms and Events Notification Setup, in both the Alarm History and Action History viewers, you need to manually refresh the display by clicking the ABC icon, in the viewer’s toolbar. The alarms and events demo is fully functional for periods of 60 minutes at a time; the unlicensed server will time-out after this time period. You may restart the server service, however, it will always time-out after 60 minutes. When using action agents, you need to install these on the same computer, running Windows NT or Windows 2000, as the alarms server (logger) along with an Alarms and Events Notification Setup instance for configuration purposes. Trends Logging and Viewing ========================== Before deleting historical trend data from the Trends Logger, you need to close Trend Link Controls presenting this data. HiBeam ======= When installing the Chinese versions of HiBeam, note that the available versions are Simplified Chinese (PRC) having the encoding GB and Traditional Chinese (Taiwan) having the Big5 encoding. The PLC Import File project type is no longer supported. The extension for image files must be indicated in lowercase letters, for example, Image.gif. Otherwise, you will not be able to browse for or display them. The feature calling images is case sensitive, therefore, images having the extension in uppercase letters will not be displayed. When upgrading to version 1.2 or later, for previous projects having pages with links between them, you need to create a new project with a container having the same number of screens into which you copy and paste the contents of each page then redefine the links. You also need to redefine your trended variables directly in the trend graph object's properties; Logging the values of variables for trending is no longer required. ISaGRAF OPC ==================== Before switching the Workbench to debug mode, make sure to start the OPC server. The OPC server does not support simple arrays of ULint and LReal type variables. The OPC server cannot connect to more than one ISaRSI network per workbench project. Therefore, for resources using more than one such network, use the OPC server in multi-project mode and place the resources using different ISaRSI networks in different projects. The OPC server incorrectly converts the Date data type. If the OPC server disconnects after a long period of time or is unable to connect, perform the following procedure: 1. Close the workbench and a HMI. 2. Shut down the ETCP.exe process. 3. Change the value of the IXLMTimeoutFactor in the registries: a) Create a file called ixl_timeout.reg and insert the following lines in the file: REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\ICSTriplexISaGRAF\OPCServer] "IXLMTimeoutFactor"=dword:00000005 b) Save changes to the file and close it. c) Execute the file by double-clicking it. Before changing the path of project files in the OPC Setup module to access another project, you must make sure that no program (i.e., a HMI) is currently using the OPC server. Run-time Installation ===================== The various ISaGRAF targets with advanced options are installed differently. For Windows 2000, and XP, the target is installed using the ISaGRAF installation. For Windows CE, Linux, and QNX, the targets are installed as detailed in the readme.txt files located in their respective root folder on the Runtime CD-ROM. The ISaGRAF targets without advanced options are installed as detailed in the runtime modules online documentation. When installing a QNX run time, the error log file and the current project files are deleted. Targets ======= The simulation driver is not delivered with the Windows NT target (WIN32-TGT_L). When running on the same computer (locally), the Windows NT target for version 4.20 is incompatible with Workbench versions 4.22 or later. When performing on-line changes having a large quantity of constant strings taking up an excessive amount of temporary variables memory space, you may need to increase this memory space. For example, you can change this memory space from 4096 to 8192, depending on the amount of memory space available on the target. To increase the temporary variables memory space, complete the following steps: 1. In the PrjLibrary.mdb file for the project, in the Target table, increase the value of the SM field. 2. Rebuild and download the project. 3. Try performing an on-line change. If successful, modify all project files (.mdb) in the directory. QNX Run-time modules run on the QNX version 6.2 operating system; QNX version 4.X is no longer supported. Installing Drivers and Packages =============================== When installing drivers and packages, V2K files are no longer automatically associated to an executable file. Therefore, you need to execute the following "V2K_installer filename.v2k IP_address". For example: V2K_installer modbus.v2k 192.168.2.178 Bug Corrections ——————————————— Consult Release.txt for the list of bug corrections. Contacting Us ————————————— Visit our web site at http://www.isagraf.com or contact our location nearest you: North America ============= - Send an e-mail to support@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 - Write to us: ICS Triplex ISaGRAF Inc. Technical Support 9975 Catania Avenue, Local U Brossard (Quebec) Canada J4Z 3V6 Europe ====== - Send an e-mail to supporteurope@isagraf.com - Send a fax to +33 (0)4 76 41 35 61 - Call +33 (0)4 76 04 81 75 - Write to us: ICS Triplex ISaGRAF Inc. Technical Support 6bis Chemin des Prés 38240 Meylan France