CIMPLICITY HMI

Version 6.1 (Build 5303) Special Notes, Restrictions, and Known Issues Contents
Overview Installation Notes Release Notes New in this Release Issues Resolved in this Release

Overview
General Description Version 6.1 of CIMPLICITY HMI Plant Edition is for use on Windows NT Version 4.0 Service Pack 6a, Windows 2000 Service Pack 3 and Windows XP Service Pack 1 (accepting no more than 10 clients; it does not support Terminal Services). Runtime Viewers are supported on Windows NT, Windows 2000 and Windows XP. Development Viewers are supported on Windows NT version 4.0 Service Pack 6a, Windows 2000 Service Pack 3 and Windows XP. Version 6.1 is available as a new release or as an upgrade to all previous releases of the CIMPLICITY HMI for Windows based product.

Installation Notes
Please read this ReadMe.rtf file, located in the main CIMPLICITY directory on the CD-ROM. It contains a list of special notes, restrictions and known problems for this release. Installing CIMPLICITY HMI Software Instructions for installing CIMPLICITY HMI can be found in the CIMPLICITY HMI Plant Edition Getting Started topic under Help for CIMPLICITY software. Upgrading from Previous Releases Before you upgrade from a previous release of CIMPLICITY HMI Plant Edition software: Open the Registration program and write down all serial numbers. Save your projects in a directory outside of the CIMPLICITY path. Remember, after you upgrade your projects, they will not work with previous versions of CIMPLICITY HMI software. Before upgrading a Tracker project, you must either delete the backing files (ProjDir\log\*.prt_dc) if the tracking image is not important, or export/import the tracking image. This is done by using the PRT Export capability BEFORE doing the project upgrade and by using the PRT Import capability AFTER the project is upgraded and the backing files are deleted. Shut down CIMPLICITY HMI software. Start the CIMPLICITY HMI Plant Edition installation process. If you are installing from a networked CD drive or file server, be aware that the Setup process may appear to be hung after the Transferring Files popup window appears. This time is dependent on the access time to the networked CD drive or file server.

Page 1

Release Notes
General Information
To provide improved device communications capabilities to the GE Fanuc Series 90 devices, the Series 90 Triplex Ethernet device communications driver is replacing the Series 90 TPC/IP communications driver. If you are currently using the Series 90 TCP/IP communications driver you can convert your existing configuration automatically over to the new driver. If you are using EGD communications you should continue to use the existing communications driver. GE Fanuc is in the process of building a new EGD communications driver, which will be released at a future date to replace the EGD functionality in the Series 90 TCP/IP communications. The Series 90 TCP/IP Triplex driver allows CIMPLICITY HMI to interface to individual Series 90 and/or VersaMax PLCs. Communication is established and maintained to each PLC through a single Ethernet connection to the device. One Ethernet address is assigned to each PLC. Unlike Redundant PLC configurations, non-redundant communication is not contingent on health, mode or run bits in the PLC. If the CIMPLICITY Redundancy option is purchased, the Series 90 Triplex driver will support communication to redundant Series 90 PLCs and redundant cabling to the PLCs.. GE Fanuc continually seeks to improve its products and move them forward as new technology emerges. When Windows XP and Windows 2000 were released by Microsoft, we added support for these operating systems. Microsoft announced in June of 2003 that they were dropping support for Windows NT and Windows 98. GE Fanuc has dropped support for Windows 98 with this release and has made the decision that this will also be the last release to support Windows NT. In future releases, we will be adding support for Windows 2003 Servers. The CIMPLICITY directory must appear in the environment PATH after Windows directories and before any networked or UNC directories; otherwise projects will fail to start. Compressing a hard drive with the Norton Speed Disk corrupts CIMPLICITY HMI licensing unless you specify that all *.ENT, *.KEY and *.RST files cannot be moved in the Norton Utilities before you start to compress the hard drive. Do not use pathnames containing spaces for any files used by CIMPLICITY software. It is recommended that you set your display for a color palette greater than 256 colors if you are viewing the Demo screens. Smaller color palettes cause some of the animated objects and text on the screens to display incorrectly. Do not use a 16-bit zip utility to zip or unzip a project - long file names will be truncated to an 8.3 format.

Allen-Bradley Device Communications

Devices that use a Port_ID keyword of LOCAL must specify the RSLinx station number in the station_number field. For this product option, you need Rockwell Software's RSLinx software. This communication enabler has been tested with Version 2.2.10 with 22002sp.exe.

Page 2

Allen-Bradley Data Highway Plus Device Communcations

If utilizing a 1784-KT/B card to communicate with Allen-Bradley PLCs on a Data Highway Plus network, you may use either the Allen-Brady Communications enabler or the Allen-Bradley Data Highway Plus Communications enabler, but not both on the same computer. For this product option, you need Rockwell Softwares RSLinx software. For Windows NT, both Version 2.0 and 2.1 have been qualified for use. You will need version 2.2.10 if using Windows 2000. This product option is qualified for use with the Windows NT operating system only.

You cannot use Allen-Bradley Communications with an ABKT card and AllenBradley Data Highway Plus Communications on the same computer. A registry entry for Allen-Bradley Data Highway Plus conflicts with one for RSLinx. Data Highway Plus device communication is supported in a single processor Intel system only. Floating point file types are not supported for PLC-3 controllers. If a Data Highway Plus device communications card is configured, it must be installed before CIMPLICITY project is started.

Allen-Bradley DF1 Device Communications

All devices must be available when the device communication interface is started. If a device is down, the points will remain unavailable until the device communication interface is restarted with the device available. No device down alarm is generated if the device is down at startup. For SLCs, the device communication interface supports communications to files up to 99.

APPLICOM Device Communications

This product option is qualified for use with the Windows NT operating system only. As an alternative to the Applicom Device Communication Enabler, the Applicom OPC Server may be used in conjunction with the CIMPLICITY HMI OPC Client. This is the recommended approach when using an Applicom. SendKeys() and OLE calls like CimView.Open work in the Program Editor. However, they do not behave properly when invoked from the event manager. You cannot create an executable that contains more than one script.

Basic Control Engine CimEdit/CimView

If your project is not running and you want to be able to browse for points in the project in CimEdit, start CimEdit from the project cabinet, not the CIMPLICITY HMI menu. Remote Dynamic Configuration is not supported from CimEdit. If CIMPLICITY software is configured to start at boot time and a CimView screen is launched by the users Start program group, and a user logs in to Windows NT quickly after the system boots, CimView may try to start CIMPLICITY software even though it is in the process of starting up. If this happens, exit CimView and restart. To avoid this problem, have users log in after CIMPLICITY software has started, or use the /waitforproject argument in the command line for the CimView screen.

Page 3

Configuration

When displaying the values of unsigned integers in CimView, use the General or Custom display formats instead of the Configured display format to insure numbers are displayed as unsigned. After duplicating a Series 90 TCP/IP Device, you must edit the new Device and enter the proper IP address. To use Remote Dynamic Configuration from a Viewer, you must first start the Viewer.

DDE

When configuring NETDDE, the CIMPLICITY HMI Service should be configured to logon as a user with a non-null password rather than the system account. The computer must be configured so that the user selected has full access to the DDE share. When using a Visual Basic server to gather data for a CIMPLICITY project, it must have the ability to support more than one topic. It has been observed that Visual Basic has the capacity to support 128 items per topic. When communicating with a DDE server whose model type is TEXT, the DDE enabler will attempt to convert the values received based on the configured points data type. When a global parameter, DDE_UNAVAIL_ON_ILLEGAL_VAL is defined and set to a value of Y, a point will go to an unavailable state if the data received from the DDE Server contains an invalid character relative to the points Data Type. For example, if the global is defined and set to Y and the DDE Server sent a value of ABC for a point with a Data Type of INT, the point would transition to an unavailable state. If you are logging to a SQL Server database, you may need to change the database configuration. The maximum number of users must be at least the number of projects connecting to a SQL Server times four (4). If CIMPLICITY is installed on Terminal Server and it is using MSDE, then SQL Server SP2 is required.

Database Logger

Device Communications Driver Toolkit

Before you build the sample executable, you must set the following environment variable: PROCESSOR_ARCHITECTURE=x86 The Device Communications Driver Toolkit API supports developing device communication enablers in the Microsoft Developer Studio visual environment (MSDEV). The following new files provide this support: APIDEV.BAT This batch file sets up the INCLUDE, LIB and PATH environment variables for CIMPLICITY HMI API development, updates the corresponding values in the registry for MSDEV, then starts MSDEV. It passes its command line on to MSDEV so you may use all MSDEV command line arguments and options. For example, to run MSDEV and open the workspace WORK1, open a Command Prompt window from the project, and enter the following command: apidev work1.mdp TLKITTST.MDP and TLKTITST.MAK This MSDEV workspace and make file include settings to build the demonstration communication enabler that comes with the Toolkit. To use these files, open a Command Prompt window from the project, and enter the following commands:

Page 4

cd %bsm_root%\api\dc_api apidev tlkittst.mdp You may then use MSDEV to build TLKITTST.DLL. TLKITUSR.MAK This MSDEV makefile includes settings to build a custom communication enabler based on the templates that come with the Device Communications Driver Toolkit API. To use this file, open a Command Prompt window from the project and enter the following commands: cd %bsm_root%\api\dc_api mkdir \<dir> copy urstm_*.c \<dir> copy tlkitusr.* \<dir>\<_evcomms>.* cd \<dir> apidev <_evcomms>.mak where <dir> is the directory for your enabler and <_evcomms> is the name of your enabler. You may then use MSDEV to build <_evcomms>.DLL. You must still use the procedure in the manual to create <_evcomms>.EXE and copy the .DLL and .EXE files to %BSM_ROOT%\exe.

Ethernet Global Data Device Communications Genius Device Communications

Device communication interface does not properly differentiate between GE PLCs multicasting with the same exchange number . This product option is qualified for use with the Windows NT operating system only. The Genius driver is available for use on Intel based PCs with ISA slots running Windows NT with the following PCIM Cards: IC660ELB921, IC660ELB922, or IC660EL906. You can configure a maximum of 4 PCIM ports for a project. The Device Communication Enabler supports communication to Series 6 programmable controllers with a Genius bus controller; however, the CIMPLICITY Genius Link diagnostic application does not recognize these devices.

Historical Alarm Viewer Integrators Toolkit

In order to use an HAV object in a broadcast session in a project, it is necessary to configure the project's own node as its client (Workbench - Security - Advanced Client). If you are implementing an API, you will need the Microsoft Visual C++ version 6.0. APIs are not thread safe. All code must be written in a single thread. After installing the new version of CIMPLICITY software, recompile and relink any C programs you have developed for your API(s).

Page 5

The makefiles for the APIs are named makefile_api. To build the programs, run the command nmake f makefile_api. There is a limit of 20,000 points for device drivers created with the Device Communications Driver Toolkit API. Make sure %BSM_ROOT% points to the main CIMPLICITY directory (for example, c:\CIMPLICITY).

Marquee Driver Mitsubishi TCP/IP Device Communications Modbus Ethernet Device Communications

When using Remote Marquees, if a clear request arrives before the message is sent to the Marquee, the clear request is postponed until the generate message is sent first. Timer Contacts, Coils, Inputs, Outputs, Internals, Internal Extended, Link Relays and Annunciators are currently limited to arrays of no greater than 256 bytes. This product option is qualified for use with the Windows NT and Windows 2000 operating system only. When specifying UseCounts=1 for STAT_PLC devices in the INI file, the element counts for coils and inputs statues should be configured to a value divisible by 8. Configuring data in coils beyond the end of range of coils can cause all points to go unavailable. The Modbus Plus driver terminates abnormally if the MODBUS Plus cable is connected during system startup. To avoid this problem: 1. Disconnect the Modbus Plus cable before rebooting. 2. Reboot your computer. 3. Reconnect your Modbus Plus cable when the Login window displays. The SA85 Card Configuration tool will not accept IRQ7. The last address in General Reference memory currently cannot be set by either Modsoft PLC programming software or the Modbus Plus device communications option.

Modbus RTU Device Communications OPC

When the Domain Size is User defined, choose values divisible by 8 for Coils and Input Statuses. Select the Delay Load attribute for a point rather than an ON DEMAND update criteria for points that should be subscribed on the OPC Server when the points are in use. Points that have an update criteria that includes ON-DEMAND will remain subscribed on the OPC Server regardless of whether the point is actually in demand. Points with the Delay Load selected will not be added to the OPC Server until they are called into use by the application and a request is made to remove them from the OPC Server when they are no longer in use. As always, it is highly recommended that point update criteria be UNSOLICITED, or in special cases, UNSOLICITED ON CHANGE where OPC is concerned. There is seldom a good reason to use a polled update criteria (ON CHANGE, ON SCAN, POLL ONCE, etc.), especially in high point count projects. Delay Load may be used in conjunction with UNSOLICITED update criteria. This

Page 6

combination provides the most efficient OPC environment for large systems. If point by address points are used with OPC, use the UPDATE=UN attribute when defining them. OPC Diagnostic points should only be used in applications with less than 100 groups. Using the project wizard to configure points on OPC Servers with large address spaces is very resource intensive. If an insufficient amount of resources is available, the Project Wizard will terminate. Support for an Oracle database is provided via Microsoft ODBC for Oracle (with Oracle Client). This driver comes as part of the Microsoft MDAC 2.7sp1, which is installed when you install CIMPLICITY. CIMPLICITY support for Oracle also includes using the DataDirect Technologies (formerly Merant) Connect ODBC driver for Oracle. MERANT can be contacted at 1-800-443-1601. Supported versions are: DataDirect Technologies Connect ODBC Driver for Oracle Version 4.2. Oracle Version 9i. This support has been verified for Windows NT 4.0, Windows 2000 and Windows XP Professional on Intel-compatible processors. The Oracle client software must be installed in the same computer as CIMPLICITY HMI software. If using the MERANT DataDirect driver, the DataDirect ODBC driver must be installed in the same computer as CIMPLICITY HMI software.

Oracle Database Support

Pager

When using Pager with Host Redundancy, the PAGER database and CENTRAL database must be manually copied from the c:\CIMPLICITY\hmi\pager\data directory on the master computer to the same corresponding directory on the slave computer. Pager help files can be accessed from the main CIMPLICITY Help in the CIMPLICITY Program Group. The communication setting in version 7.52 is 7E1, and when upgraded to version 7.6.3, it has been changed to 7E1.5. This will cause pages to fail being sent.

Recipes Report Manager SPC Charts

When configuring points for use by Recipes, the combination of project id, point id, and point attribute name lengths must not exceed 55 characters. It is known that removing Report Manager Lite will also delete the CIMPLICITY Program Group from the Start Menu. Windows NT 4.0 Service Pack 4 and Windows 2000 supersedes the file extension .SPC to reference PKCS #7 certificates file format instead of CIMPLICITY HMI SPC file format. If you are using NT SP4 or Windows 2000 with the CIMPLICITY SPC option, you will not be able to directly open GE Fanuc .SPC documents from the Explorer or Workbench. To avoid this error, activate the SPC option from the Workbench, and open the document from the SPC Configuration File... menu. Alternately, you may remove the .SPC file association by performing the following steps: From the Windows NT Explorer, Select Options from the View menu;

Page 7

In the Options dialog, Click on the File Types tab; Search through the list of Registered File Types for the entry labeled PKCS #7 Certificates. Select this item, and click on the Remove button; Click on the Yes button when prompted to confirm; From the File Types page, click the New Type button; In the Description of Type field, type SpcCfg Document Enter .SPC in the Associated Extension field; Create a New action named Open and browse for SPC configuration as its associated Application; Close the New File Type and Options dialogs.

Series 90 Triplex Device Communications

Diagnostic point RESPONSES was not updating correctly.

To prevent the VERSAMAX SE device from timing out due to inactivity, the following recommendation is made: 1. Configure the timeout on the devices COM port and SE Interface to 60 seconds. 2. Add the global parameter S90TCP_<DEVICE_ID>_IS_SE with a value of Y for each SE device. 3. The connection and request time out values under the TCP/IP tab of the port configuration need to be set to a value that ensures consistency in establishing and maintaining a connection. A value of 55 seconds (55000 ms) is recommended as an initial starting point. An initial value of 5 to 10 seconds may be configured for the heartbeat timer to reduce the possibility of timeout due to inactivity. It is desirable that the request timeout + network latency be less than the time out value configured in the SE and PLC Port configurations. Where SE devices are configured on the port, the mode address must have a valid PLC address even if there are no redundant devices configured on the port. The first time that a connection is established via the S90 Triplex in a project after loading a project later than 6.0 SP1, the memory sizes from the PLC will be read at startup regardless of the setting in the device configuration.

Series 90 Triplex & Series 90 TCP/IP Device Communications Siemens H1-TF Device Communications

You can use any of the following Device Communication Enablers to communicate with a Series 90 PLC over Ethernet, but you can not use them at the same time, on the same computer: Series 90 Ethernet S90 Redundancy S90 TRIPLEX The Siemens driver has not been qualified for Microsoft Windows NT Version 4.0. Use the APPLICOM OPC Server with the CIMPLICITY OPC Client instead.

Page 8

Smarteye Electronic Assembly

A Smarteye concentrator with an address of either 360 or 370 does not log data. Smarteye is currently working on a firmware upgrade.

When configured in handshake mode with communication through a terminal server, the communication interface must be stopped and restarted if the terminal server is power cycled. Microsoft added a feature called Media Sense to Windows 2000. When the Ethernet cable is removed Windows detects this and disables the TCP stack. This causes problems for CIMPLICITY. CIMPLICITY disables this feature during setup. A registry entry is added that causes Windows to ignore the loss of the Ethernet cable. The registry entry is HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameter s Value Name: DisableDHCPMediaSense Data Type: REG_DWORD Value Data Range: 0, 1 (False, True) Default: 0 (False) To re-enable this feature the registry entry can be deleted or the value can be changed to "0". When configuring a PRT Display Point record, click on the Global Property sheet and create a RESET point. The absence of this point could cause PRTCNT to terminate. The PRTCNT process will take the place of PRT_GRD as the default data display engine for Tracker. PRTCNT offers the following improvements over PRT_GRD: PRTCNT connects directly to backing files and does not rely on point updates, which offers faster access to data PRTCNT handles multiple serialized Items per location Projects using PRT_GRD can continue to do so, however the configuration data is easily translated for use in PRTCNT When there is no record for PRTCNT in PRT_INTPROC.IDT, the PRTCNT process will terminate after startup. The following steps need to be followed to avoid this situation: 1. Open Tracker Configuration User Interface. 2. Double click on Interested Processes in the PRT/Advanced folder. 3. In the Interested Processes window, click on the New Document button. 4. In the Interested Process Configuration dialog select PRT_DC for the PRT Service, type PRTCNT in the Interested Process Service field, select Full update type, and click OK. 5. When you restart the project, perform a Configuration Update. To install the WebGateway product, execute the following command from the CIMPLICITY\i386 directory on the CIMPLICITY HMI CD: Setup.exe WEBGATEWAY There is a limit of 10 users when using a non-server operation system, such as Windows NT Workstation, Windows 2000 Professional or Windows XP Professional.

System Sentry

Tracker

WebGateway WebView

Page 9

New in this Release

Alarm Viewer Auto Logout CimEdit / CimView
The Alarm Viewer ActiveX control can now have custom buttons configured to either run a program or trigger and ActiveX event. CIMPLICITY can now be configured to log out the user after a configured period of time, log out the user and start the login process (this will display the login box) or log the user out and log them in as a different user. Users can dynamically change the language of the screen being displayed without closing the screen or shutting down the system. This switch can be made from a screen event that either toggles the language or provides a list of languages to choose from. Frame Containers can be placed in screens allowing the entire screen, or portions of a screen, to change based on a database point value. With this release, we have made an enhancement that improves the ability to launch Quick Trends or Point Control Panel from objects within a Frame Container. Now the frames at the top of the object hierarchy can be ignored, allowing the user to drill down to the first non-frame object to invoke the Quick Trend or Point control panel. Users can configure whether they want Thumbnail support for CimView screens. In order to protect intellectual property, CIMPLICITY HMI had allowed users to compile some of their scripts as runtime scripts. CIMPLICITY HMI now supports both regular and runtime scripts as global scripts that can be protected.

Client Configuration Framework Database Logging HMI for CNC

The 'Client Configuration Framework' enables a seamless change (from the user's perspective) between a Plant Edition native driver and a GE Fanuc OPC server. The user configures Plant Edition 'Ports' and 'Devices' as if they were configuring any native driver. This configuration information is then used to create an XML configuration file for the OPC server to use. The default logging engine has been upgraded from MSDE 1.0 to MSDE 2000. The HMI for CNC option has been updated to take advantage of the latest revision levels of the Fanuc Drivers and Library support software (versions K730 FOCAS1/HSSB and K732 FOCAS1/Ethernet) and the Fanuc Basic Operation Package (versions K750 FOCAS1/HSSB and K752 FOCAS1/Ethernet) user interface software. CIMPLICITY PE has been integrated with the iHistorian product, a plant-wide data historian. The N2 System Protocol device communication option supports Johnson Controls N2 Open and Sys91 protocols. Supported device types are: Companion Plant Controllers (DC9100) Rev 1.0 and Rev 2.0 Companion and Facilitator Digital Controllers (DX9100) Rev 1.1 and Rev 2.0 Companion and Facilitator Temperature Controllers (TC9100) Rev 1.0 Companion and Facilitator Unitary Controllers (UNT) Companion and Facilitator Variable Air Volume Controllers (VAV)

IHistorian Johnson Controls Device Communications

Page 10

Licensing Login/ Logout API Modbus TCP/IP Device Communications

Companion and Facilitator Air Handling Unit Controllers (AHU) While not explicitly supported, other Johnson Controls and third party devices may work to the extent that they implement the available protocols. Hyper-threading support is now available. A Multiprocessor License must still be purchased for computers with multiple physical CPUs. API support for user logins has been added. CIMPLICITY HMI users can now configure and communicate with GE Fanuc VersaMax and VersaPoint devices via Modbus TCP/IP by simply selecting the right model. This selection sets the proper modes in the protocol so you can write to coils and holding registers without changing other configuration parameters. This also provides the minor capability to restore output values when restoring a communication connection. Added support for the following: GE Fanuc VersaMax ENIU GE Fanuc VersaPoint ENIU Communication is also supported via: Modicon COBOX Modbus TCP to Modbus RTU Bridge (TSX Momentum 174-CEV-300-10) or Modicon Modbus Plus to Modbus Ethernet (TSX Momentum 174-CEV200 30) New parameters have been added to Master_OPC_0.ini: RestartDelay: delay before client begins reconnect attempt, in milliseconds ReconnectInterval: time between reconnect attempts, in milliseconds RemoveItemsOnGroupRemove: Controls whether items will be removed before the group is removed. By default, the value is one and items are removed before the group is deleted. ItemAccessDelimiter Defines the tokey to use for the access path delimiter. The default value is a semi-colon. ItemAccessPathEnable Controls whether a search for an access path is to be performed. The ItemAccessDelimiter separates the access path from the item tag. ChangeGroupStateonDeviceTransition Controls whether the Group State will be enabled/disabled when the Device corresponding to the OPC Server is enabled/disabled. ChangeGroupStateOnHostTransition Controls whether the Group State for related groups is enabled/disabled based on host transition from/to primary/secondary in a host redundant environment. Third party OPC Data Servers can now pass alarm and event data to CIMPLICITY PE.

OPC

OPC Alarms and Events

It is now possible to view and archive Alarm and Event messages from CIMPLICITY ME.

Pager Point Bridge Point Cross

A new version of CIMPLICITY Pager, version 7.69, is available with this release. Point Bridge will not halt or block other point updates while waiting for a client setpoint/writepoint request to complete. The Point Cross Reference tool now reports point references in CimView screens.

Page 11

Reference Point Management Series 90 Triplex Device Communications

It is now possible to receive off-node ON_CHANGE requests that only update after a configured number of seconds. The global parameter S90TCP_ALLOW_UNSO has been added to allow for unsolicited communications. The value must be set to Y or YES. A conversion utility has been included to change projects using Series 90 TCP/IP or Series 90 Redundancy Device Communications to Series 90 Triplex Device Communications. This will convert most projects that do not use Ethernet Global Data to the closest equivalent using Series 90 Triplex. It is now possible to read from I/O and PLC Fault tables with this protocol. The privilege level and password for access may now be specified on a per project per PLC basis. The test diagnostic program is now called SRTP_DIAG. The diagnostic will access the PLC at the same privilege level as configured for the device in the project. The project wizard will now auto-detect and configure devices. It will assume non-redundant devices. Redundant device characteristics need to be defined by the user through the configuration transactions.

VCR

Performance has been significantly improved by changing the internal methods for how data is obtained.

Issues Resolved in this Release

The following issues have been resolved: The AL operator did not reflect the correct values for some DISABLED and Alarm Manager ENABLED alarms on source points. PRT and CNC Alarm Classes were not adding new alarm colors correctly. The Status Log message Alarm Does Not Exist did not display the Alarm ID. In certain conditions, the Alarm Manager was not using the timestamp from an unsolicited point. Derived points would only be set to 1 when the point went into alarm, but they would never be cleared until the point was normal again. The ANA function was not working properly with boolean Device Points.

Alarm Printer Alarm Viewer OCX

When printing to a network printer, it was not possible to force the alarm message onto the second line. Dynamic changes to Alarm Classes were not properly reflected in the Alarm Viewer. If a connection was made to a local project using the computer name, instead of local project or Project ID, then alarms were not updated in the OCX. Users could not create AMVOCX custom buttons that trigger an ActiveX event. If the AMVOCX looked for a screen in the default path of GSM_SCREENS and

Page 12

could not locate it, the name was not passed to CimView. If CimView could not locate the file, no message is displayed. Previously, users could double click anywhere on an AMVOCX. Now the only place on an AMVOCX that can be double-clicked is the Count area and where there are no buttons. The alarm list was losing some clicks associated with a double click on the scroll bar. When an alarm did not have a CimView screen associated with it, a less meaningful message box was shown. The right-mouse menu would not select the correct alarm if the CimView screen was either zoomed in or zoomed out. Communications could not be established when the PLC station address was higher than 7. Data from Floating Point Files from a SLC 5/04 were previously unavailable in most cases. ABDF1_portname_USESFP needs to be set appropriately. Array points were not updating correctly when triggered from scripts. The run once action with set point no longer incorrectly reports a failure of the first setpoint. Turn-around delay was not supported. The following project Global Parameter has been added to initialize the turn-around delay: <PORT>_TURN_AROUND_DELAY Units are in ticks, where 1 tick = 1/100 of a second. You could not expose the objects within screen-level containers to the point target tools. The global parameter GSM_FRAMES_EXPOSE_POINT_TARGETS has been added. When set to YES, it will expose the objects within screen level containers to the point target tools. It does this as if the objects were at the screen level. By default, this is set to NO. The Scale method did not work properly for linked objects. Copying MS Forms 2.9 Frame Objects could cause CimEdit to unexpectedly terminate. If windows opened from the Open Screen method were not closed in the other they were opened, the X could disappear from the title bar. Class Objects from more than one project did not function correctly when dropped onto a CimEdit screen. Some CimEdit variables were lost in the upgrade from HMI v4.01. CimView Linked objects would be off by a few pixels in comparison to their location on the CimEdit screen. When browsing for points on text objects, CimView could have two instances of a point, if the point was not full qualified. Polygons configured with patterns and a color of none would ignore the closed attribute. For this change to take effect in CimView, the CimEdit screen needs to be saved. CimEdit terminated if a linked object was broken and then deleted.

Allen-Bradley DF1 Device Communications

Basic Control Engine

CCM2 Device Communications

CimEdit / CimView

Page 13

Unsupported CimView functions called in a WebView screen would cause the screen to become unreliable. Users could not disable the metafile option for CimView screens. Help opened from a linked object would not open correctly. Users could not open multiple global scripts. The command line option /LoadScriptCfg <file to open> has been added. This opens a text file that should contain a list of global scripts that will be loaded. The file names must be enclosed in "" and may contain logicals such as SITE_ROOT, BSM_ROOT etc. The command line option itself can contain logicals. Multiple files may appear on the same line. The global parameter "GSM_GLOBAL_SCRIPTCFG" can also be used to specify the global configuration file. Also note, if a script is not found, the file name with different extensions will be tried (e.g. .cmsrt will be substituted for .cms and .cms will be substituted for .cmsrt). The user was not alerted when MSDE was removed. Use of CIMAlarm.Save could reset values of other fields to their default values.

CIMPLICITY Installation CIMPLICITY Automation Server

CimTable.SetDataLogPtTimedRate did not update correctly. CimTable.SetDataLogPtSyncTime did not update correctly. The value -1 will disable synchronization for the item. The $Object variable value was not read-only on the variables page. Now when you select a different Object ID in the Class Object tab, then go the Variables tab, the $OBJECT variable will not update until Apply or OK is pressed. CimGetEMEvent().PointEvent() did not retrieve all values of a point when accessed from a script. Analog Deadband was not accessible from the Object Model.

Configuration Object Model

Database Logger Host Redundancy

The following properties have been added to CimProject: NeedsConfigUpdate returns true if a configuration update is needed NeedsVersionUpgrade returns true if a version upgrade is needed VersionNumber returns the version number as a string; e.g. 6.10.5133 VersionUpgrade method that does a product version upgrade The CimProjectData object had memory buffer overflows when processing large amounts of data. References to Merant drivers have been changed to DataDirect. When the primary computer was down, the connection to the slave occurred slowly. CimView screens were not exiting if they contained trend controls with a connection to a redundant project where the primary system was off-line. Setpoints and alarm disables were causing hangs of Point Control Panel if the primary system was off-line. Setpoints were not performed when triggered from Event Manager scripts on the secondary node when the primary is down. Logouts/Logins caused problems with open point-based clients (like

Page 14

PointControlPanel, CimView, Trending). When restarting the slave machine in a redundant environment, the Unacked alarm counts would not be correct.

Import/Export InterProcess Control

User-modified role files could fail to import due to sorting. Project broadcasts were not being forwarded over RAS connections. Connections to a cabling redundant server over RAS were not steady. If shutting down a remote project took longer than 30 seconds, a message could appear that the remote service was not responding.

Marquee Driver

When using Remote Marquees, if a clear request arrived before the message was sent to the Marquee, the clear request was not postponed until the generate message was sent first. Under certain conditions, a remote marquee would not be directed to clear a message that was no longer active. This would result in the remote marquee continuing to display the message. Some Modbus Ethernet Bridges would not provide notification when a device was not present and some would. For those that did not, you can define the project global parameter below. If one device on a port goes down, only that device is now marked down. Previously, all devices on the bridge would be marked down. The following global parameter has been added to identify devices to follow this protocol:
MBETH_NORESP_<IP_ADDRESS_OF_BRIDGE>

Modbus TCP/IP Device Communications

OPC Configuration Framework OPC Device Communications

where IP_ADDRESS_OF_BRIDGE is the TCP/IP Address of the bridge and Y is true. The port Scan Rate was not updated in the XML files.

The OPC Client could terminate when dynamic configuration changes were made to the points. New parameters have been added to Master_OPC_0.ini: RestartDelay: delay before client begins reconnect attempt, in milliseconds ReconnectInterval: time between reconnect attempts, in milliseconds With the DetectPingHang equal to 1, it was possible for the OPC Client to abort the connection while or just after it had been established. The check for measuring the duration of a GetStatus has been modified to eliminate this possibility. Groups of points were removed slowly from the OPC Server. Diagnostic points for OPC Server status were not being reinitialized when a server requested shutdown occurred. The Project Wizard was terminating when scanning for a large number of points on a remote OPC Server. The Project Wizard was not handling any invalid characters it found. It now substitutes _ for any invalid characters it finds in a Device ID or a Point ID. Long point addresses failed with delay-load points.

Page 15

Point Bridge

The Point Bridge did not a setpoint success even when the setpoint failed. The Point Bridge did not continue to process updates while waiting for setpoints to complete.

Point Management

Off-node on change points can be updated every X number of seconds by adding the following global parameter: PTMAP_TIMED_POINTS Where if X is greater than 0, the point will be updated in that number of seconds. This parameter must be set on the client machine. This is valid for off-node points only, local points will not be delayed. Point Control Panel could not shut down when talking to four projects, with at least fifty points in each project. If a client was viewing points (e.g., Point Control Panel or CimView), logged off the project and then logged back in using Login Panel, it took a long time for the point values to appear. Point names could not be quoted in the BASIC Getpoint and Setpoint procedures. When viewing points in the Tree View from a Point Control Panel, the Point Management Translation process could halt. Point s could be entered as their own triggers. Now, if a point is entered as its own trigger, the following message box appears: Derived point <PointID> cannot be its own trigger point. Point Management now transmits consistent data to clients who make requests involving points with names that exceed 32 characters. This problem is specific to Enterprise Server points on the Enterprise node. Under certain circumstances, the Point Control Panel would not properly reflect points that were in Manual Mode. Diagnostic point RESPONSES was not updating correctly.

Series 90 Triplex Device Communications

The global parameter S90TCP_ALLOW_UNSO has been added to allow for unsolicited communications. The value must be set to Y or YES. It is now possible to read from I/O and PLC Fault tables with this protocol. To prevent the VERSAMAX SE device from timing out due to inactivity, the following recommendation is made: 1. Configure the timeout on the devices COM port and SE Interface to 60 seconds. 2. Add the global parameter S90TCP_<DEVICE_ID>_IS_SE with a value of Y for each SE device. 3. The connection and request time out values under the TCP/IP tab of the port configuration need to be set to a value that ensures consistency in establishing and maintaining a connection. A value of 55 seconds (55000 ms) is recommended as an initial starting point. An initial value of 5 to 10 seconds may be configured for the heartbeat timer to reduce the possibility of timeout due to inactivity. It is desirable that the request timeout + network latency be less than the time out value configured in the SE and PLC Port configurations. Where SE devices are configured on the port, the mode address must have a valid PLC address even if there are no redundant devices configured on the port. Communication via the V variable to a TI 505 up through 32768 variables did

Siemens TI Serial

Page 16

Communications SNPX Device Communications

not work. The project-level Global Parameter SNPX_VALIDATE has been added to allow the INI file to configure the domain sizes for a device, and also allow the user to override validation check for correctness of the INI file. N disable validation on the INI file for all SNPX devices in the project configured in the INI file, or to disable validation for a specific device Y - enable validation on the INI file for all SNPX devices in the project configured in the INI file SPC charts previous to version 5.5 could not be opened. SPC charts embedded into web pages no longer cause access violations.

SPC Charts

System Sentry Terminal Service Tracker

This product option could not be removed. Only one user could be logged in at a time, despite having the proper licenses for more users. The Decision ID field on the Decision Page would allow non-numeric valuees. Previously, there was no limit to the number of digits that could be entered for a profile setting. Tooltips were not available for Manual Execution. The RCO User Interface could terminate if Project and Site Information were not entered. Attribute names with 14 or more characters did not display correctly. PRT_DS would halt when it was configured with one region and more than one location capacity. Changes to PRTCNT were made to append the numeric form of the event code to the update point and to append a string form matching the library file. The user interface to PRT could become unresponsive when moving PRT items. A check box has been added to the user interface to retrieve the user configuration value. The PRTCNT process would not update when a region was re-ordered. In the Tracking Type field, Detainment has been added. Also, Out of Sequence will now support selecting nothing, so that if an item is out of sequence, the count will be 0 with no action. If the sequence of items entering a in a region is not important, setting OOS Action to nothing will disable OOS, where as selecting an OOS action and having an OOS Cycle of 0 means that there is no tolerance in the region for Out Of Sequence items. The Point ID was not included in an RCO User Interface message when the site was disabled by an unexpected async point. The RCO User Interface was not displaying the proper number of characters for USER_STATUS. The gap between new data and logged data that is off screen has been resolved. If there is no data in the current time range, then there is not going to be a line displayed. If there is data in the current time range then data that is out of range to the left will be reflected unless there is a null value between the current date time and the last logged date time. There were extra lines in the gaps on a trend chart.

Trending

Page 17

VCR

Using an object.attribute point reference would cause VCR to not function correctly. VCR could not process data in a regional locale that was different than the locale the data was collected from. VCR did not work in a host redundant environment. The AMVOCX was generating endless error messages when viewing the VCR in conjunction with a CimView alarm viewer screen. VCR would hang when using point enumerations. The initial VCR querys performance has been greatly enhanced. If a fatal error occurred in the VCR Service, the router would be left in an incorrect state A projects log file was being flooded with the error message Request not found in local point manager when VCR is shut down. The following System Global Parameter will give the user the ability to switch between two VCR query methods:
VCRINITQUERY

1 - uses nested query (default) 2 uses Temporary table 3 uses separate select statement for each point The X button was not disabled while in VCR mode.

WebView

The following CimView methods were not supported: SetWidth, SetHeight, SetZoom and ScrollTo. When unsupported CimView functions were called in a WebView screen, the screen would become unreliable.

CIMPLICITY and Genius are registered trademarks and Series 90 and Series Six are trademarks of GE Fanuc Automation Americas, Inc. PLC-3 is a registered trademark and Data Highway is a trademark of Allen-Bradley Company, Inc. Intel is a registered trademark of Intel Corporation. Windows NT, Windows 95/98, Windows 2000, Windows XP, Microsoft, Access, Excel, SQL Server, MSDE, and Windows are registered trademarks and ODBC is a trademark of Microsoft Corporation. DataDirect is a registered trademark and MERANT is a trademark of MERANT Solutions Inc. Oracle is a registered trademark of Oracle Corporation. All other trademarks, marked and not marked, are the property of their respective owners.

Page 18