GE Fanuc Automation

_____________________________________________________________
CIMPLICITY® Monitoring and Control Products

CIMPLICITY HMI
Important Product Information
HMI 6.1 Service Pack 4
Copyright © 2005 GE Fanuc Automation Americas, Inc. All Rights Reserved.

Contents
 Installation
 Web Installation
 CD-ROM Installation
 Registration
 Applicable Product Releases
 New to this Update
 Issues Resolved in this Update
 Determining your Current Version/Build/Service Pack
 Known Compatibility Issues
 Using Windows XP Service Pack 2

Installation

Web Installation
To install this Service Pack from the Web do the following:
1. Download the appropriate file from the GE Fanuc Web site:
 HMI61sp4.exe
2. Extract the Service Pack executable files into a temporary/working directory.
3. Stop all CIMPLICITY applications on the host computer.
4. From Explorer, open the temporary/working directory where you placed the downloaded file.
5. Double-click on SETUP.BAT to initiate the installation program.

CD-ROM Installation
To install this Service Pack from a CD-ROM follow these steps:
1. Stop all CIMPLICITY applications on the host computer.
2. Insert the CD-ROM in your computer.
3. From Explorer, double click on Setup.bat to execute the installation program.

HMI 6.1 Service Pack 4 Page 1 of 43

 Registration
Once your CIMPLICITY software has been licensed, there is no need to re-register the software. If
you are installing CIMPLICITY for the first time, there are two suggested methods of registering:

Option 1. Install CIMPLICITY software and register software when prompted during the
installation procedure. After registering the CIMPLICITY base product, it is not necessary to re-
register after installing the Service Pack.

Option 2. Install CIMPLICITY software and skip registration when prompted during the
installation procedure. Install the Service Pack and register software when prompted. You must
complete the registration procedure at this time to ensure that all of your software is properly
registered and fully functional.

Applicable Product Releases

Product(s): CIMPLICITY HMI for Intel processors.
Version(s): Use this service upgrade to update the following CIMPLICITY versions.

Version: 6.1 SP1 SP1a SP2 SP3

Build: 5303 5383 5383 5396 5405

Caution: Do not install this Service upgrade unless your system has one of the
applicable product releases or a build number greater than one listed above.

Platform(s): HMI 6.1 Service Pack 4 has been validated with Windows 2003 Server, Windows XP
Professional, Windows 2000 and Windows NT 4.0 Service Pack 6a. Please see the Known
Compatibility Issues section for further details.
Please note the following:
1. HMI 6.1 Service Pack 4 only updates those software modules that you have currently installed.
2. If you need to install additional CIMPLICITY product options from your CIMPLICITY HMI
Release 6.1 CD after applying this service upgrade, you must first uninstall the CIMPLICITY
product and reinstall the options you want from the CD.
3. After reinstalling CIMPLICITY HMI software to include additional software modules from the
CD, you must reinstall this Service Upgrade.
4. If you have upgraded directly from version 6.0, there is a ReadMe.rtf file in the
CIMPLICITY\HMI directory that provides information regarding version 6.0.
5. HMI 6.1 Service Pack 4 will upgrade CIMPLICITY projects created prior to this release. Once
your project has been upgraded, you will not be able to configure or run it with any prior version
of CIMPLICITY HMI software.
6. CimView screen files in HMI 6.1 Service Pack 4 are directly compatible with CIMPLICITY
HMI version 6.1.

HMI 6.1 Service Pack 4 Page 2 of 43

 Issues Resolved in this Update
The following issues have been resolved:

Service Pack 4
Action Calendar no longer has an exception when iterating through
events contained in the CimEventList object. (22268)
Action Calendar
There is no longer an erroneous error when the “Apply” button is
selected during Event configuration. (20955)
Alarm blocking now functions correctly when using the global
parameter AM_OLD_POINT_RESET. (22064)
Alarm Manager
Alarm Blocking configuration is now properly loaded on project
start. (21385)
Millisecond timestamps are now working correctly when doing an
Alarm Rest. (20417)
Alarm messages are no longer truncated when printed to a file with
Alarm Printer less than 80 characters. (20875)
Complete messages are now printed if the page width is set to
something other than 80 or 157. (21357)
Allen Bradley The highest Timer file address can now be read correctly. (21881)
Ethernet Device
Communications
Modifying alarm limits no longer causes a termination when the
alarm limits are viewed in CimView or the Point Control Panel.
(21416)
The alm_user file for alarm setups are now saved correctly.
Alarm Viewer OCX (20516)
Resizing a CimView screen that contains an AMVOCX now
correctly shifts the text. (21042)
The Alarm Viewer OCX can now take alarm filter setup
configuration on start-up. (21392)
CimEdit / CimView Under certain circumstances, CimView no longer locks. (22269)

After a popup menu command, the current window no longer loses

focus. (21577)
The value for CimParallelExecution in CimEvent.EventExecution
is now correct. (21566)
CimView translation of right-justified text fields now display
correctly. (21700)
If a link is pasted from another CimEdit screen, the variable values
are now correct. (21723)
It is now possible to use the public variable construct to pass screen
variable values between screens. (22011)
Modifying the Visibility Animation equation no longer causes
CimView to terminate. (22159)
HMI 6.1 Service Pack 4 Page 3 of 43
 The CimEdit global script buffer no longer becomes corrupt.
(22153)
CimView no longer leaves “screen artifacts” after switching frames
in a frame container. (22740)
CimView will no longer terminate when opening a window
initiated by a script. (21868)
It is now possible to select enumerate values from a drop-down
menu when creating an Action in CimEdit. (19955)
Point enumerations are now translated on a screen. This is done by
doing translation of Text object, and Text Button object value
animation expression results (only translates an expression if the
result is a string). This allows for that while still enabling scripts
and other expressions to still compare to constant enumeration
values.

This allows for the translation of the following expression such that
keys for "Hot" and "Warm" are put into the screen CLM file and a
translation can be provided in that file as well:
(ovenTemp GT 130) : "Hot" ? "Warm"

And for the following expressions to work as expected and have

"Lights Are On", and "Lights Are Off" translated:
enumPoint EQ "On" : "Lights Are On" ? "Lights Are Off"

And for an expression such as the following to also be translated.

All enumeration values in a project are put into a screens CLM as
keys for translation:
enumPoint
The Highlight/Unhighlight event has been changed very slightly to
guarantee that the mouse Unhighlight for the screen gets called
when the mouse leaves the screen. The Unhighlight event for the
screen still gets called when another object gets the highlight.
However, with the GefScreen().IsMouseInScreen() you can now
tell if the mouse has moved off the screen or if the screen
unhighlight is was triggered because another object was
highlighted.
When mouse leaves screen

1) If screen is highlighted then trigger screen unhighlight event.

Or
2) If an object other than the screen is highlighted
a) Trigger unhighlight event for that object,
b) Trigger highlight event for screen
c) Trigger unhighlight event for screen

Or
3) If no object is highlighted
a) Trigger highlight event for screen
HMI 6.1 Service Pack 4 Page 4 of 43
 b) Trigger unhighlight event for screen

The Language Mapper now properly translates alarm strings.

CimLangMapper (21627)
Just In Time points are now properly released by the OPC Client
when they are not being used. (22215)
CIMPLICITY OPC The OPC Client no longer provides stale data if it is unable to
Client properly recover from a downed device. (21351)
There is no longer a memory leak when the client is
communicating to an RSLinx device. (22089)
Project path mapping now works correctly in the Windows XP
Configuration Operating System. (22667)
The Datalogger will no longer get “hung” on Maintenance Event
Logging Count or Digital Point State if an executing statement is
Database Logger blocking access to the process mutex. (21990)
If the underlying database a point was being logged to changed, it
no longer causes the Trend OCX to terminate. (21495)
There is now better error handling in the Basic Point API. In the
previous version, the application would terminate, where now it
will return an “out of memory” error. It is recommended that
string space be increased to help prevent this error. (22121)
Event Manager If an event is trying to trigger an action that contains deleted points,
the Event Manger does not terminate. (21288)
Event scripts no longer stay in a “running” state. (21572)

This Service Pack is required to be used with Historian 3.0 in order

Historian 3.0 to use the CIMPLICITY HMI Alarm and Event data. (21983)
CLIE Import no longer counts HMI for CNC points against the I/O
license count. (21992)
Import Export
CLIE import no longer allows importing a point into an object’s
sub item. (21986)
Under certain circumstances, the Router no longer terminates
Inter-Process unexpected. (22431)
Communications Having dual IP Addresses on one Network Interface Card no longer
causes project broadcast not to work. (21521)
The Marquee process no longer halts when processing On Demand
Marquee Driver points. (21485)
The following features are now available in the Object Model
configuration (additional documentation is available in cimserver-
odl.chm) (21370, 20205):
Create / Edit / Delete Alarm Classes
Object Model Create / Edit / Delete Enumerations
Viewing of application and device options installed on the system
Viewing of Device Protocol details
Create / Edit / Delete Measurement Units

HMI 6.1 Service Pack 4 Page 5 of 43

 Omron TCP/IP The Omron protocol now correctly displays the values from a CS1
Device device. (22238)
Communications The Property Pages now display the correct data. (21534)

Milliseconds for the NORMAL state are now provided. (22759)

OPC Alarm and
Event Server The Alarm and Event Server now provide milliseconds for alarm
generation. (22758)
The Point Manger will no longer terminate if a point has been non-
dynamically deleted and then dynamically re-added. A message
box will appear notifying the user that the point is not valid.
(22339)
Setpoint security now works correctly with Just In Time points.
(21367)
The Value Accumulator point now function correctly. (22163)
Point Management
$Raw_Value no longer causes a Point Management termination.
(21530)
Where PLC or cable redundancy is configured and Setpoints are
configured so they are applied to All PLCs in Group, setpoints will
no longer be attempted to the same PLC over the same or
redundant cable connection following a successful setpoint
operation. (22570)
Series 90 Triplex PAC Systems RX3i are now supported using Series 90 Triplex
Device Device Communications. A CIMPLICITY HMI project using the
Triplex dev comm to communicate with a Series 90 PLC can be
Communications converted to communicate with a PACSystems device by changing
the device model from the appropriate Series 90 to the appropriate
PACSystems model.

The following are the available PACSystems RX3i model types

available:
GE Fanuc PACSystems RX3i
GE Fanuc PACSystems RX3i Simplex
GE Fanuc PACSystems RX3i Duplex
GE Fanuc PACSystems RX3i Triplex

The Triplex dev comm can communicate with the PACSystems

RX3i using the diagnostics screen, as well as view the Fault tables.
(21977)
The Triplex dev comm supports Bulk Memory %W for
PACSystems RX7i and RX3i PLCs.

The format of %W addressing is:

%Wxxxxxxx
where:
xxxxxxx is a number between 1 and 5242880 (5M) words or the
HMI 6.1 Service Pack 4 Page 6 of 43
 amount of %W defined in the PLC, whichever is less. (5M words is
currently the maximum that can be configured in the PACSystems
PLCs.) For example, if the PLC has %W Bulk Memory configured
as 2097152 words, then in the Point Manager Point Address field,
you can address it from %W1 to a maximum of %W2097152.
(21977)
The device communication interface supports multiple messages
outstanding over a single TCP/IP connection to a controller’s
Ethernet card. To enable the functionality for use on all devices on
all ports in the project, define the project level global
S90TCP_ALLOW_MULTIMSG with a value of Y. To enable the
functionality on all devices on a specific port within the project,
define the project level global PORT_ALLOW_MULTIMSG to a
value of Y. By default, the functionality is not enabled. (21977)
If multiple messages are enabled, the number of concurrent
messages may be defined from a value of 1 to 64. They are
specified via a project global variable between these values. Invalid
values are ignored. The specification may be defined for all devices
on the project (project-basis), all devices on a port (port-basis) or
for a specific device. The order of precedence (highest to lowest) is
device, then port, then project. If no value is specified via a global,
a value of 1 is assumed.

The following table identifies the order of precedence for

valid globals:

Global… Supercedes…
Device-level Port-level
Port-level S90TCP-level
S90TCP-level Default

The naming convention on the global is:

S90TCP_MAX_POLL_MSG – project basis
PORT_MAX_POLL_MSG – port basis
DEVICE_MAX_POLL_MSG – device basis

Note:
PORT is the name of the S90 Triplex port to be configured such as
S90TRI0, S90TRI1, etc.
DEVICE is the CIMPLICITY DEVICE NAME assigned via the
configuration for the device.

As long as the communication load is within the capability of

the PLC (as it is configured with the existing PLC application),
the communications remains reliable without dropouts. If the
communication load is beyond the capability of the PLC, then
there may be loss of communications or it may be observed that
the Triplex interface will switch between viable communication
paths. If this occurs, reduce the number of concurrent
messages.

When confirming the number of concurrent messages chosen is

HMI 6.1 Service Pack 4 Page 7 of 43
 compatible with the PLC application, be sure to validate the
application with the PLC in run mode running the complete
PLC application. (21977)

Write operations will now work correctly after device

communications have been re-established. (22217)
The maximum message size for data exchange between the Series
90 Triplex device communication interface and the Series 90
Ethernet card has been changed from 1024 to 2000 bytes for polled
device communications. In some configurations, using a larger
size for the cache will reduce the number of message exchanges
between the Series 90 Ethernet card and the HMI application
resulting in improved performance. Modification of the cache size
is accomplished by defining a project level global variable. The
variable, S90TCP_MAX_CACHE may be defined with a value to
affect all devices in the project. Similarly, the variable
PORT_MAX_CACHE may be define to affect all devices on a
single port. Please note that PORT is the name of the S90 Triplex
port to be configured such as S90TRI0, S90TRI1, etc.

The PORT_MAX_CACHE has a higher precedence than does the

S90TCP_MAX_CACHE. The default value is 1024.

The value assigned to the global is the maximum port size. If a

value larger then the maximum is specified, the largest allowed
value will be used.

In some configurations, supporting a larger message size may be

beyond the capability of Series 90-70 (as it is configured with the
existing PLC application). This is more likely to occur where the
IC697CMM741 Ethernet cards are used for communications on the
Series 90-70. If the communications becomes unstable as a result
of using the larger message size, it is recommended that the
application continue to use a cache size of 1024 bytes.

When confirming that the number of concurrent messages chosen is

compatible with the PLC application, be sure to validate the
application with the Series 90-70 in run mode running the complete
PLC application.

Some device communication interfaces support asynchronous

polling. Write (setpoint) requests and poll after set reads are
performed synchronously and are prioritized before pending polling
operations. Mixing synchronous and asynchronous processing can
create a window where asynchronous poll transactions can partially
process between the synchronous transactions resulting in the
incoming data being processed out of sequence. For applications
that require guaranteed FIFO, force synchronous processing by
using one of the following global flags:

HMI 6.1 Service Pack 4 Page 8 of 43

 DC_SYNC_ONLY
Value: Y - processing for all interfaces is synchronous only.
Value N - (Default) - asynchronous polling for all devices in the
project where the features is supported by the device
communication interface

<PORT>_SYNC_ONLY
Value: Y - polling for all devices on the port is synchronous only
Value N - (Default) - asynchronous polling for all devices on the
port where the feature is supported by the device communication
interface

Note: Where it is available, asynchronous polling typically

provides better data collection performance than does synchronous
polling.

In some cases during polling, queued unsolicited data is awaiting

processing. Enabling the following global allows the pending
unsolicited to process before performing the synchronous read:

DC_UNSO_BEFORE_SREAD
Value Y: Process pending unsolicited before synchronous reads for
all interfaces in the project
Value N: (Default) Process synchronous read first

<PORT>_UNSO_BEFORE_SREAD
Value Y: Process pending unsolicited before synchronous reads for
all the given port
Value N: (Default) Process synchronous read first

Note: If this flag is enabled, an application built depending on

POLL AFTER SET to provide the just written value may receive a
pending unsolicited update for the point for the next update prior to
the read value following the setpoint operation.

SPC charts no longer look for the incorrect project name when it is
specified in the SPC table. (22583)
SPC Charts The Global Library functionality now is correct. (22401)

Tracker The PRT User Interface now logs the “user_id” field when
Modifying items. (21667)
RCO now triggers on the first change from 0 to 1. (22023)

The PRT User Interface now logs the “user_id” field when Adding
or Inserting items. (21366)

HMI 6.1 Service Pack 4 Page 9 of 43

 There was an issue where any script names (routing logic modules
and decision output modules) that were identical within a single rco
folder would cause the wrong script to run when the site is
triggered. With this fix users will be able to have script names that
are identical within the same folder. (21541)
The PRT User Interface no longer provides a “Region ID Not
Found” error when using the selection dialog box. (21671)

The PRT User Interface no longer terminates if given an invalid

Region ID with the –R option. (22261)
The function block “Eliminate Decision by Attribute” was not
evaluating correctly. (22459)
SPECIAL NOTE: After Service Pack has been installed, open any
RCO sites that use the “Eliminate Decision by Attribute” function
block and compile the function block.
Certain function blocks were not evaluating correctly when using
the operand “<>”. The function blocks affected by this change are
(20056, 20490):
ComparePointValue
EliminateDecisionByPointValue
SelectDecisionByPointValue
CompareAttrib
CompareAttribValue
EliminateDecisionbyAttribValue
SelectDecisionbyAttrValue

A Trend object with a Status line in the header now displays

correctly after converting the screen to a CTX and back again.
(21546)
XY Plots are no longer terminating when a series is added to it.
Trend (22095)
XY Plots

Service Pack 3
If there are no alarms in the Alarm Viewer OCX, the following
methods no longer cause the screen to terminate:
MoveUpOneAlarm
Alarm Viewer OCX
MoveDownOneAlarm (21215)
AMVOCX has been enhanced to short by four terms, where
previously it would sort by two terms.
Summit BASIC can now properly pass structures containing arrays
CimBasic of structures. (21217)

HMI 6.1 Service Pack 4 Page 10 of 43

 CimView no longer terminates on screen closure with certain
expressions in a screen object. (21307)
There are no longer problems saying screens that contain OLE or
ActiveX objects in .CTX format. (21333)
When a linked object is copied, it now correctly copies the values
of variables. (21320)
CimEdit / CimView
Screen variables can now be accessed below the top-level for a
linked object. (21255)
Variable settings are no longer removed if the arrow key is pressed.
(21312)
Variables selected in the variable browser now correctly populate
their fields. (21279)
Historical Alarm The Historical Alarm Viewer can now properly display data when
the date is moved into the future and then back to the current date.
Viewer (21182)
Marquee The marquee process no longer halts due to the port name. (21323)

Series 90 Triplex There are no longer communication failures due to improper

Device termination of a %L. (21297)
Communications
Support has been added for communications with PAC Systems
RX3i and RX7i devices.
The following domains will be supported:
%AI
%AQ
%I
%R
%Q
%T
SNP Device
%M
Communications
%S
%SA
%SB
%SC
%G
Restrictions:
Projects using the SNP protocol prior to this update will not be
updated to include the configuration support for the RX3i or RX7i.
%W is currently not supported. (21316, 21318)
Point Management Under certain circumstances, the Point Translation process could
terminate when trying to duplicate a point in dynamic mode.
(21379)
The ANA operator now works correctly with virtual points that are
derived from device points. (21272)

HMI 6.1 Service Pack 4 Page 11 of 43

 Enterprise points with long names are now displayed correctly in
the Point Control Panel. (21232)
Tracker The PRTCNT can now count non-serialized items. (21384)

Changing the line type on a trend chart from “Point” to

“Expression” no longer causes the application to terminate.
(21213)
Trend The Trend slider can now display the correct valued when it passes
65535 elements. (21197)
Point lines for array points now work correctly. (21103)

WebView now indicates when a user’s password has expired.

WebView (21243)

Service Pack 2
If Action Calendar is started outside of a project, the user is alerted
Action Calendar to restart the application within a project. (20184)
The capture of an AMVOCX now releases if the left button is
AMVOCX released over the title bar or scroll bar. (20940)
CimBasic no longer terminates if the print function is given an
CimBasic integer. (20537)
Text objects on a CimView screen with the translate option
cleared, would have the translate option set when the screen was
saved as a text (.ctx) file. The translate option from the CimView
screen is now recorded correctly in a .ctx file. (20854)
Relative Setpoint values are no longer corrupted after saving a
CimView screen. (20886)
The AL function in expressions now updates correctly on the
CimEdit / CimView secondary server of a host redundant system. (20650)
When an animated object is right-clicked in CimView, choosing
Point Control Panel no longer displays an error about the object not
having points.
The issue where under certain circumstances, WebView would fail
to execute mouse-down events has been resolved. (21047)
CimEdit no longer terminates when editing link containers. (21007)

Configuration There is no longer a significant delay when opening a project over

Cabinet a network. (21109)

Bulk load is now disabled when the Point Data Logger is

Database Logger performing a datamerge. (20705)
The issue where under certain circumstances, the Event Editor was
Event Manager not reloading scripts has been resolved. (20864)
Historical Alarm CimView screens that contain a Historical Alarm Viewer no longer
Viewer terminate when the user logs out of the screen. (20575)

HMI for CNC Support for CNC Model 30i has been added to this release.

HMI 6.1 Service Pack 4 Page 12 of 43

 InfoAgent Connector Included in this Service Pack is Plant Edition support for the
CIMPLICITY HMI InfoAgent Connector. This is compatible with
Support InfoAgent version 2.0.
The following system global parameter has been added to disable
InterProcess performance counters:
Communications PERF_COUNTERS_ENABLED
The default value for this is Y. (20545)
Support is now available for asynchronous maintenance of the
Modbus TCP/IP connections. The feature can be enabled on a
project or port basis by configuring the appropriate project global
parameter. By default, the feature is disabled and connections are
maintained synchronously. The parameters are described below:

MBETH_ASYNC_CONNECTION affects all Modbus TCP/IP

devcoms on the same project. Configure this parameter to a value
of Y to specify asynchronous connection management as the
default method for all devices within the project. Configure the
parameter to a value of N to define synchronous connection
management as the default.

ModBus TCP/IP <PORT>_ASYNC_CONNECTION affects all Modbus TCP/IP

devices on the given port. Configure this parameter to a value of Y
Device to specify asynchronous connection management for all devices
Communications configured on the <PORT>. Configure the parameter to a value of
N to define synchronous connection management for all devices
configured on the <PORT>.

IMPORTANT: There are Modbus TCP/IP bridges that do not

provide a response as defined by the Modbus TCP/IP protocol
when the queried device is not present. If such devices are
configured on a CIMPLICITY port, use a synchronous connection
on the port. Ports with devices utilizing such bridges are not
supported in asynchronous mode. In addition, the use of
synchronous communications is forced when either the
MBETH_NORESP_ipaddress or
<DeviceID>_CONSERVES_CONN global parameter is enabled.

Time-outs may now be specified down to the millisecond level by

configuring a project and/or port level global parameters. These
parameters work in conjunction with the pre-existing time-out
parameters. The parameters are described below.
NOTE: The minimum time-out must be no less than 0.5 seconds.

MBETH_REQ_MILLISECOND_TIMEOUT affects all Modbus

TCP/IP devcoms on the same project. Define this project level
global to specify a default millisecond component to the timing for
all devices configured in the project. The default value is zero.

<PORT>_REQ_MILLISECOND_TIMEOUT affects all Modbus

HMI 6.1 Service Pack 4 Page 13 of 43
 TCP/IP devcoms on the same port. Define this project level global
to specify a default millisecond component to the timing for all
devices configured on the port.
NOTE: The <PORT> in the above parameters represents the port
name, such as MBTCP0.
When data is entered into the MMS Configuration device, it is now
MMS Device properly updating the configuration. (20935)
Communications Points using a Type III device now update correctly. (20577)

The issue where under certain circumstances, point updates were

not being displayed correctly has been resolved. (20749)
Server Statistic OPC Point Ids are no longer case sensitive. (20751)

The issue where OPC Server setpoints could fail due to a

OPC Device resynchronization problem has been resolved. (20960)
Communications Points configured with Measurement Units now update correctly
when the measurement unit is changed. (20689)
If the using the CIMPLICITY OPC Server and a ping times out and
the connection is recovered (i.e. unsolicited data comes in) before
the next ping or abort, the OPC Client now refreshes data to the
OPC Server. (21086)
Points configured with a too large Rate of Change time no longer
terminate the Point Management process. (20938)
The issue where under certain circumstances, the point
management process could terminate if measurement units were
changed has now been resolved. (20998)
The behavior of ANA was changed in version 6.1. Prior to 6.1 it
behaved as NACK. To revert its behavior to version 6.1, you can
Point Management use the following global parameter:
PTEXP_ANA_EQ_NACK_AND_AL set to “y”, “Y”, “T” or “t”
Points configured with an Alarm Delay no longer terminate the
Point Management process (20937)
$PROJECT.DEVICES now updates correctly when the device is
reconnected. The device count should only be updated when the
device is marked as available. (20893)
Series 90 Triplex When establishing a connection with a Series 90 and/or
PACSystem device, we now use PDU Type 8 instead of PDU Type
Device 2. This enables the PLC’s Ethernet interface to completely clean
Communications up a connection upon termination of said connection. (20431)
SPC Charts Z-Bench scores for Histogram charts are no longer miscalculated
when the Z-Bench is large. (20508)
Attribute Charts now fetch Upper Control Limits and Lower
Control Limits. (18399)
The Xindividuals chart can be configured to display control limits.
The Lower Control Limits and Upper Control Limit calculations
have been modified to the following (17753):
LCL = Mean – 3 * S
UCL = Mean + 3 * S
HMI 6.1 Service Pack 4 Page 14 of 43
 Where S:
S = MR/1.128 and MR = 1 / n-1 (SUM(Xi – Xi-1)) for all data from
X1 to Xn
It is now possible to rescale the Y-axis when point values cause
data to go off the chart with the following global parameter
(20107):
SPC_RESIZE_OUT_OF_BOUNDS set to Y
The SNP Device Communication protocol now supports disabling
BREAK when using the Firmware version 8.2 of PLC Firmware on
Series 90 devices. The following project level global parameters
have been added:
SNP Device SNP_SEND_BREAK set to Y or N will enable or disable sending
Communications BREAK. This can be superceded on a port basis by defining
<PORT>_SEND_BREAK.
SNP_IDLE_TIME by default is 10 seconds when BREAK is
disabled This can be superceded on a port basis by defining
<PORT>_IDLE_TIME. (19395)
SNPX Device When an INI file is used and SNPX_VALIDATE was defined to a
Communications value of N, device communication will always resume following a
drop in the communications. (20824)
In SNPX, one may choose to define the memory sizes for a given
device by creating a file named <PORT>.INI and including
information about the memory sizes for one or more devices
configured on the given CIMPLICITY port. The format of the file
is as follows:

[YOUR_DEVICE_ID]
MemoryType=CountOfMemory Type

Below is a sample file for COM1 (MASTER_COM1.INI) where

one Device, DEVICE1 has been configured:

[DEVICE1]
%AI=2048
%AQ=512
%R=9999
%I=2048
%Q=2048
%T=256
%M=4096
%G=1280
%S=32
%SA=32
%SB=32
%SC=32

By default, the communication interface will evaluate the

HMI 6.1 Service Pack 4 Page 15 of 43
 information and confirm that the last element in each specified
range exists. If the items doesn’t exist, then the communication
interface will, by default, attempt to determine the number of items
configured for the given memory type.
To override this behavior, a global can created at the device, or
project level to override the behavior. When defined, the device
level global overrides the project level global which overrides the
default.
The project level global is defined as SNPX_VALIDATE, the
device level global is DEVICE_VALIDATE
The default value is Y. To override the default, define the global
to have a value of N.
The method PrtGroup.prtgetitemlist correctly resets the project
Tracker associations. (20461)
The method PRTItem.Prodstart now works correctly. (20210)

There are no longer line gaps where historical and new data meet.
(20956)
Trending
There are no longer line gaps when trending buffered points.
(21001, 20950)

Service Pack 1a
Procedure message for open overlay screens now function
correctly. (20623)
CimEdit / CimView
In a host redundant system, points with AL expressions now update
correctly. (20650)
Login Panel The Login Panel application now functions correctly. (20583)

The Tracker Counter process no longer terminates.

Tracker
Trending of logged lines no longer causes the CimView screen to
Trending terminate. (20655)
Logged Expression line types now trend correctly. (20656)

Service Pack 1
Allen-Bradley DF1 This is a correction to the Allen-Bradley DF1documentation which
Device will be fixed in the next major release of the software. Under
“Device Default Properties”, it should read:
Communications
Enter the node ID for the device.
For PLC 2 or PLC 3 this is an optional Station Number
Address used only when writing to a PLC 2 via a KA or KG
module. If this field is not used, it should be set to zero.

HMI 6.1 Service Pack 4 Page 16 of 43

 For PLC 5 this is an address consisting of two fields as
follows:
<Octal digit station address>/< Octal digit station address of
the KF2 Module>

For SLC this is an address consisting of one field as follow:

<Source ID(00-31)>

Note: The Source ID is also knows as the PLC Node

address. For special network configurations a KF3 Node
address can be used.
The “AL” operator now reflects the correct values for some
DISABLED and ENABLED alarms on source points.
Older Alarm Comments files can now be read. Note that in order
for this feature (preserving alarm comments) to work, the user must
Alarm Manager have the global parameter, ALARM_SAVE_COMMENTS, set to
YES. (19867)
Alarm filter settings are no longer reset after a redundant failover
(20037)
The Global Parameter AMVOCX_MAX_DYN can be added to
restrict the number of alarms received by the AMVOCX in
dynamic mode. The actual alarms sent are determined by the
user’s current alarm setup, not the AMVOCX sorting order.
The number of alarms received in dynamic mode is the parameter
value, plus one. (19408)
Alarm Viewer OCX The Alarm Viewer OCX no longer hangs if the setup was changed
while in dynamic mode. (19588)
The Alarm Viewer OCX no longer stops responding to left-mouse
clicks. (19571)
The issue where under certain circumstances, screens could
terminate when an AMVOCX was deleted has been resolved.
(19381)
Changing the setup of an Alarm Viewer will no longer cause it to
stop updating. (19614)
The function SQLRetrieve no longer terminates when performing
CimBasic sequential script execution. (19627)

HMI 6.1 Service Pack 4 Page 17 of 43

 Reuse of an array variable to store query results no longer causes
CimView to terminate. (18885)
Screens that contain a Smart Object now are correctly saved.
(19751)
When creating a Procedure Action, adding the project name as a
prefix to the Point ID now works as expected. (19687)
Drop Down box properties in an OCX now work correctly. (19922)

The CimEdit/CimView on-screen keypad is now enabled through

the command line parameter “/keypad”. (19469)
Text objects with in-place edit setpoints now work correctly in
Japanese. (19478)
CimEdit no longer takes a long period of time to save if there are
meta files attached to the screen. (19595)
Dragging and dropping files into a CimView screen no longer
opens another screen session. (19548)
Replacing or renaming a Point ID in CimEdit PointView no longer
causes CimEdit to hang. (19677)
CimView will no longer terminate when certain screens were used
as a WebView Server. (19766)
The Configuration Cabinet will no longer run out of memory if
there are many object instances of a class and the class
CimEdit / CimView configuration is changed. (19787)
When GefScreen.Width and GefScreen.Height are increased from a
script, they now increase the correct amount. (19780)
CimGetScreen did not work correctly when run under WebView on
Windows XP. (17093)
CimView no longer terminates when an AMV OCX is deleted from
the screen. (19381)
When opening a CimView shortcut on a Windows XP machine, a
"gray screen" no longer appears. (19487)
A CTX file conversion to CIM and back to CTX no longer causes
file corruption, specifically font names when read in from the CTX
file. (20007)
Unicode .CTX files can now be opened in Word or WordPad.
(19938)
Focus on screen controls no longer disappears when tabbing, when
using Windows 2000. (19515)
Tab order is now preserved in Linked Objects. (20342)

CimBasic no longer causes CimView screens to terminate due to a

memory leak.
Special Note:
Runtime-only Event Manager scripts will need to be recompiled.
Runtime-only CimView scripts will need to be recompiled. (19312)
Configuration Virtual Data items can now be used as an Availability Trigger in
Classes. (19268)
HMI 6.1 Service Pack 4 Page 18 of 43
 If a user tries to open a read-only .GEF file, they are now told the
file is read-only. (19294)
If a user is auto-logged out and then auto-logged in as a different
user, they can now change users by logging out and back in again.
(19308)
After upgrading to v6.1, the configuration security tab no longer is
displayed when configuration security is not enabled. (20071)
The DataMerge utility is not as system-intensive as it was
Database Logger previously. (19594)
When using a FloPro/FloNet port configuration retry count of 1 and
FloPro Device a response timeout of 10 or less, devices were periodically being
Communications marked down. The recommended port retry count is 3 and the
recommended response timeout is 100. (19872)
RowStyles Tab in the Historical Alarm Viewer Property Dialog
Box now correctly function when it is translated in Japanese.
(19499)
Historical Alarm
Column sizes in the Historical Alarm Viewer no longer are very
Viewer small when the screen is reopened. (20105)
The ambient font was not being used correctly in an embedded grid
control. (20057)
If a CNC Ethernet device is powered down, at project startup the
CNC licenses are no longer being consumed. (19295)
HMI for CNC
HMI for CNC projects now correctly recognizes CNC connection
licenses.
When importing data, external roles are now correctly being
associated with their alarms. (19886)
Import / Export
When exporting a large amount of data, roles are now exported
correctly. (20414)
InterProcess There is no longer problem with detecting a hyper-threaded
Communications processor. (19745)

The Auto-logout login viewer process is visible if started from the

Login Panel Start Up program group. (20162)
The processing of setpoint operations in the Mitsubishi TCP/IP
Mitsubishi TCP device communication interface has been modified. Following the
Device setpoint request to the PLC, the software can now more quickly
Communications detect the PLC's response allowing for faster completion of the
operation. (19626)
The CIMPLICITY OPC Server will no longer terminate when
trying to add a large number of points from a remotely broadcasted
project. (19382)
OPC Device
Communications If communication to a large number of OPC Servers is lost at the
same time, all devices are always marked down. (19204)
Performance enhancements have been made in this release.

Point Cross The Find and Print buttons on the toolbar in the Point Cross
Reference Reference utility are no longer invisible. (20257)

HMI 6.1 Service Pack 4 Page 19 of 43

 It is now possible to set points with CIMPLICITY Plant Edition
Point Management after losing communication to CIMPLICITY Machine Edition via
Point Bridge. (19790)
Significant digits are no longer lost for integer values stored in a
Recipes recipe. (19155)
The Recipes API now supports 800x600 touch screen dialogs.

Support has been added for communications with PACSystems

RX7i devices.
Series 90 Triplex Restriction:
Device For %L, the PLC must have 100 or fewer %Ls configured, the
Communications program (target name) and all block names must be 7 characters or
less. %W is currently not supported.

The following project-level global variables have been added:

S90TCP_MAX_REQUEST_CACHE affects all Triplex devcoms
in the project.
<PORT_>MAX_REQUEST_CACHE affects all Triplex
devcoms on the given port.
<DEVICE>_MAX_REQUEST_CACHE affects only the cache
for the device specified.
By default, the Triplex device communication interface will queue
up to 100 requests per device for processing. For projects with a
large number of caches (due to a large number of regions to read or
a large number of scan rates for a single device), it is possible to
exceed this value.

Define the parameters to be the maximum number of

queued/cached reads per device/group.

These values can be defined as a greater or lesser value than the

default, but should have a value greater than zero. The default
value is 100.

The following table identifies the order of precedence for valid

globals:

Global… Supercedes…
Device-level Port-level
Port-level S90TCP-level
S90TCP-level Default
(19482)
The Triplex protocol no longer terminates when operating with
large numbers of caches. (19825)
%PLC_FAULT will deliver a start address starting at the beginning
of the fault table include the header information. There are 12

HMI 6.1 Service Pack 4 Page 20 of 43

 bytes of header. Each fault is 42 bytes long. Up to 16 faults can be
requested. To specify a start address at the beginning of a specific
fault (no header) specify %PLC_FAULT.<Fault Number> where
fault number is between 1 and 16 (19447)
%IO_FAULT will deliver a start address starting at the beginning
of the fault table include the header information. There are 12
bytes of header. Each fault is 42 bytes long. Up to 32 faults can be
requested. To specify a start address at the beginning of a specific
fault (no header) specify %IO_FAULT.<Fault Number> where
fault number is between 1 and 32. (19626)
The maximum message size for data exchange between the Series
90 Triplex device communication interface and the Series 90
Ethernet card has been changed from 1024 to 2000 bytes for device
communications. In some configurations, using a larger size for
the cache will reduce the number of message exchanges between
the Series 90 Ethernet card and the HMI application resulting in
improved performance. Modification of the cache size is
accomplished by defining a project level global variable. The
variable, S90TCP_MAX_CACHE may be defined with a value to
affect all devices in the project. Similarly, the variable
PORT_MAX_CACHE may be define to affect all devices on a
single port. Please note that PORT is the name of the S90 Triplex
port to be configured such as S90TRI0, S90TRI1, etc.

The PORT_MAX_CACHE has a higher precedence than does the

S90TCP_MAX_CACHE. The default value is 1024.

The value assigned to the global is the maximum port size. If a

value larger then the maximum is specified, the largest allowed
value will be used.

In some configurations, supporting a larger message size may be

beyond the capability of Series 90-70 (as it is configured with the
existing PLC application). This is more likely to occur where the
IC697CMM741 Ethernet cards are used for communications on the
Series 90-70. If the communications becomes unstable as a result
of using the larger message size, it is recommended that the
application continue to use a cache size of 1024 bytes.

When confirming that the number of concurrent messages chosen

is compatible with the PLC application, be sure to validate the
application with the Series 90-70 in run mode running the complete
PLC application.
Sharp Device Devices are now always marked as “down” when communications
Communications are lost. (19386)

SmartEye Device When the SmartEye device was configured in handshake mode,
Communications loss of device communications was not previously detected. With
this update, when the SmartEye device is configured within
CIMPLICITY to be in handshake mode, the device communication
interface will query the device for status if no data has been
HMI 6.1 Service Pack 4 Page 21 of 43
 received from the device within the configured interval. If the
device does not respond to the status, then the SmartEye device
will be marked down.
By default, the device communication interface will query the
device for status after 100 seconds of silence (i.e. no data received
from the device.) This value can be changed on a per project basis
by defining the project level global
SEA_HANDSHAKE_TIMEOUT. The value assigned to
the global should be equal to the number of seconds of silence that
should pass before querying for status of the device to determine
device availability. To define the value on a per port basis rather
than a per project basis, use the global variable
<port>_SEA_HANDSHAKE_TIMEOUT rather than
SEA_HANDSHAKE_TIMEOUT. Where a port and project
global are defined, the port level defined global will take
precedence. (18989)
P-Charts will now display data when data contains non-zero data
SPC Charts samples. (19591)
The issue where, on occasion, point values were not displayed
when on-demand points were brought into demand has been
resolved. (19351)
Toolkit
The issue where on occasion, data collection would continue for
on-demand points once they were no longer in demand has been
resolved. (19351)
PRTClient now correctly moves items, based on Item Type.
(19684)
Performance counters have been added for the Tracker DS process.
There will now be a counter available under Performance Object in
Performance Monitor called “HMI PRT DS”. To use, highlight all
counters and select Add.
The following steps need to be followed for this to be complete:
Tracker Open a command prompt from the Workbench (Tools / Command
Prompt)
Execute the command “set” at the command prompt to determine
the value for BSM_ROOT
Execute the following command:
installcounters.exe i <BSM_ROOT>
In the PRT User Interface, it is now possible to allow “Region
Label” to be used in place of “Region ID”.
Trending Support has been added to create trend lines from iHistorian.
Please refer to Trend.chm for more details.
A new System Global Parameter,
TREND_DISABLE_READNESTED, has been added to disable
database subqueries for timestamps. To disable timestamps, this
parameter should be set to "1". The parameter has a default setting
of "0".
The Global Parameter on a viewer needs to be in with the System
Global Parameters. On a server, it will need to be in the System
Global Parameters, if CimView is started outside a project. If
HMI 6.1 Service Pack 4 Page 22 of 43
 CimView is started inside a project, then the Global Parameters
will need to be in the Project Global Parameters. (19727)
The Trend Control no longer terminates when a user logs out in a
redundant system. (18104)
Trending either a Reference Line or a CSV Line now function
correctly. (18729)
The Trend Control no longer creates unwanted horizontal lines.
(17860)
When a device point becomes unavailable, the trend now displays
the previous value. (20065)
Two new tools have been added: IDTPOPLOCALDIR and
SCPOPLOCALDIR. They are used in a similar manner as
IDTPOP and SCPOP, except that they will only look for input files
Tools and create output files in the current working directory of their
execution. (18702)

Determining your Version/Build/Service Upgrade/Pack

To determine the CIMPLICITY Version and Build that is installed on your system:
1. Open the CIMPLICITY Workbench.
2. Click Help on the menu bar.
3. Select About Workbench….
4. The following will display for HMI 6.1 Service Pack 2:

Subsequent Service Upgrades and Service Packs will display an equivalent representation for the
highest-numbered version that has been installed.
For product versions prior to Version 4.0, the Service Pack number was not included in the Help
About dialog. Consult the Important Product Information for a version 3.2x Service Pack for details
on determining your product version under CIMPLICITY HMI 3.2x.

HMI 6.1 Service Pack 4 Page 23 of 43

 Known Compatibility Issues

iHistorian
The Service Pack installation will give you the option of installing the iHistorian Client. You may
choose NO when asked and the Service Pack installation will continue.

Series 90 Triplex
In order to gain access to the Diagnostics and Fault Tables, the following steps need to be performed
after the Service Pack has been installed:
1. Open the project and allow it to upgrade
2. In the project Properties, add Series 90 TCPIP protocol (or any other protocol) and click OK
3. Go back into the project Properties and remove Series 90 TCPIP protocol (or any other
protocol) and click OK
The Diagnostics and Fault Tables will now be available. This is only necessary for projects using
Series 90 Triplex that have been upgraded from a previous version. These steps are not necessary for
new projects created from 6.0 Service Pack 1.

Series 90 Triplex
When communicating to a GE Fanuc RX7i PLC with firmware version 2.0, by default, the
dead_scan_rate parameter is set to 45 seconds for every device configured. To speed up/slow down
reconnection, this value can be changed via the device file.
Note: The dead_scan_rate cannot go below the scan rate of the port.

VCR
$LOCAL.xxx points are no longer supported by the VCR option.

Windows 2000
Windows 2000 supercedes the file extension ".SPC" to reference PKCS #7 certificates file format
instead of CIMPLICITY HMI SPC file format. If you are using 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.
If Windows 2000 was installed before the first time you loaded the CIMPLICITY SPC option, you
may also need to manually configure the CIMPLICITY SPC Configuration File Type.
Alternately, if you will not be using an Internet Browser (Such as Internet Explorer or Netscape) on
your computer, you may remove the .SPC file association by performing the following steps:
1. From Windows NT Explorer, click View on the menu bar.
2. Select Options.
3. In the Options dialog, click the File Types tab.

HMI 6.1 Service Pack 4 Page 24 of 43

 4. Search through the list of Registered File Types for the entry labeled “PKCS #7
Certificates.”
5. Select this item, and click on the Remove button.
6. Click Yes in the confirmation box.
7. From the File Types page, click the New Type button.
8. In the Description of type field, type SPC Document.
9. Enter .SPC in the Associated extension field.
10. Create a New action named Open, and browse for SPC configuration as its associated
Application. Typically, this is found in C:\CIMPLICITY\HMI\exe\spccfg.exe.
11. Use the Change Icon button to select the SPC Icon; typically, this is found at
C:\CIMPLICITY\HMI\exe\spc.ico.
12. Close the New File Type and Options dialogs.

Windows 2003 Server

1. The following third-party applications have not been qualified for use with Windows 2003
Server, and are not supported. It is recommended that you do not upgrade to Windows 2003
if you use these applications:
RSLINX

2. The iHistorian client tools are distributed with this service pack and will load on Windows 2003,
however, the current version of iHistorian server is not supported with Windows 2003. You must
install the iHistorian server on a non-Windows 2003 PC.

3. In order for the hosts file to work properly with Windows 2003 (or XP) you will need to import
the file to the LMHOSTS file, to take advantage of enabling LMHOSTS lookup.
Procedure:
 Right-click ‘My Network Places’ on your desktop and choose ‘Properties’.
 For your LAN connection, right-click it and choose ‘Properties’.
 On the ‘General’ tab, double-click on internet protocol “TCP/IP”.
 Click on the ‘Advanced’ button, then click on the ‘WINS’ tab.
 Click on the “Import LMHOSTS” button.
 Browse for the hosts file (\Windows\System32\drivers\etc) and select it.
 OK and close out of all windows.

Note that every time you need to add an entry to the host file you will need to import to
LMHOSTS again.

CIMPLICITY SQL
The CIMPLICITY HMI upgrade does not maintain the integration between the Workbench and
CIMPLICITY SQL. If you currently have CIMPLICITY SQL integration with the HMI Workbench,
use the following procedure to restore the integration:
1. Follow normal HMI upgrade procedures.
2. After you have upgraded to HMI 6.1, insert the CIMPLICITY SQL CD (if autorun is not enabled
on you computer, browse to the CD drive and run setup.exe).
3. Continue with the remainder of the setup process. Upon completion, CIMPLICITY SQL and
Workbench integration will be restored.

If you are upgrading from CIMPLICITY HMI 5.0 or 5.5 to CIMPLICITY HMI Plant Edition 6.1 and

HMI 6.1 Service Pack 4 Page 25 of 43

 have been using the CIMPLICITY Database Server (SQL Server 7.0 MSDE 1.0 edition), and need to
preserve existing databases and data, GE Fanuc recommends that you back up the master database
and any custom databases that may have been created. You can use the following procedure to back
up and restore the master database. You can use the same procedure to back up and restore each
custom database. You should back up your databases prior to uninstalling version 5.x and restore
them once version 6.1 installation is fully completed.

Master Database Backup Procedure

1. Go to Start->Run and type cmd<Enter>. Command prompt window opens.
2. Change the command line directory to your CIMPLICITYHMI\mssql$cimplicity\\binn directory.
3. run osql.exe –S (local)\CIMPLICITY -Usa (for the system administrator logon). The command line
responds by asking for the system administrator Password:
4. Type the system administrator password and press <Enter>. The command line responds with an
OSQL environment, command prompt, and line number (e.g 1>)
5. Type the following to backup the master database.
1>BACKUP DATABASE master TO DISK='<drive>:<path>masterbak.dat' (press <Enter>)
1>RESTORE VERIFYONLY FROM DISK='<drive>:<path>masterbak.dat' (press <Enter>)
2>GO(press <Enter>)
The command line responds similarly to this
Processed 1336 pages for database 'master', file 'master' on file 1.
Processed 1 pages for database 'master', file 'mastlog' on file 1.
BACKUP DATABASE successfully processed 1337 pages in 5.792 seconds (1.889 MB/sec).
The backup set is valid.
6. Type Exit to exit the OSQL command environment. Close the command window.
7. Proceed with CIMPLICITY 5.0 uninstall procedure.

Master Database Restore Procedure

1. Go to Start->Run and type cmd<Enter>. Command prompt window opens.
2. Change the command line directory to your Program Files\Microsoft SQL Server\80\Tools\Binn
directory.
3. run osql.exe -Usa (for the system administrator logon). The command line responds by asking for the
system administrator Password:
4. Type the system administrator password and press <Enter>. The command line responds with an
OSQL environment, command prompt, and line number (e.g 1>)
5. Type the following to restore the master database to a new name. CIMPLICITY SQL automatically
creates a database called CIMPLICITY and adjusts major CIMPLICITY DSNs to point to it. If you don’t
want to restore under the database name CIMPLICITY, you can skip the 1st line (DROP DATABASE
CIMPLICITY) and change the word CIMPLICITY in the remaining statements to a database name of
your choosing:
1>DROP DATABASE CIMPLICITY
2>RESTORE DATABASE [CIMPLICITY] FROM DISK='<drive>:<path>masterbak.dat' WITH
RECOVERY, MOVE ‘master’ TO ‘<sqlDataDrive>:<sqlDataPath>CIMPLICITY.MDF’, MOVE
‘mastlog’ TO ‘<sqlDataDrive>:<sqlDataPath>CIMPLICITY_LOG.LDF’ (press <Enter>)
3>exec sp_MSdbuseraccess 'db', 'CIMPLICITY'
4>GO(press <Enter>)
The command line responds similarly to this
Processed 960 pages for database 'bob', file 'master' on file 1.
Processed 1 pages for database 'bob', file 'mastlog' on file 1.
Converting database 'bob' from version 515 to the current version 539.
Database 'CIMPLICITY' running the upgrade step from version 515 to version 524.
Database 'CIMPLICITY' running the upgrade step from version 524 to version 525.
HMI 6.1 Service Pack 4 Page 26 of 43
 Database 'CIMPLICITY' running the upgrade step from version 525 to version 526.
Database 'CIMPLICITY' running the upgrade step from version 526 to version 527.
Database 'CIMPLICITY' running the upgrade step from version 527 to version 528.
Database 'CIMPLICITY' running the upgrade step from version 528 to version 529.
Database 'CIMPLICITY' running the upgrade step from version 529 to version 530.
Database 'CIMPLICITY' running the upgrade step from version 530 to version 531.
Database 'CIMPLICITY' running the upgrade step from version 531 to version 532.
Database 'CIMPLICITY' running the upgrade step from version 532 to version 533.
Database 'CIMPLICITY' running the upgrade step from version 533 to version 534.
Database 'CIMPLICITY' running the upgrade step from version 534 to version 535.
Database 'CIMPLICITY' running the upgrade step from version 535 to version 536.
Database 'CIMPLICITY' running the upgrade step from version 536 to version 537.
Database 'CIMPLICITY' running the upgrade step from version 537 to version 538.
Database 'CIMPLICITY' running the upgrade step from version 538 to version 539.
To achieve optimal performance, update all statistics on the 'CIMPLICITY' database by running
sp_updatestats.
RESTORE DATABASE successfully processed 961 pages in 0.950 seconds (8.279 MB/sec).
6. Type Exit to exit the OSQL command environment. Close the command window.

HMI 6.1 Service Pack 4 Page 27 of 43

 Using Windows XP Service Pack 2

Understanding Windows Firewall

Windows Firewall, previously known as Internet Connection Firewall or ICF, is a protective
boundary that monitors and restricts information that travels between your computer and a
network or the Internet. This provides a line of defense against someone who might try to access
your computer from outside the Windows Firewall without your permission.
If you're running Windows XP Service Pack 2 (SP2), Windows Firewall is turned on by default.
However, some computer manufacturers and network administrators might turn it off.

Opening Windows Firewall

1. Click Start and then click Control Panel.

2. In the control panel, click Windows Security
Center.
3. Click Windows Firewall.

Security Center

Note You do not have to use Windows Firewall—you can install and run any firewall that you
choose. Evaluate the features of other firewalls and then decide which firewall best meets your
needs. If you choose to install and run another firewall, turn off Windows Firewall.

HMI 6.1 Service Pack 4 Page 28 of 43

 How Windows Firewall Works
When someone on the Internet or on a network tries to connect to your computer, we call that
attempt an "unsolicited request." When your computer gets an unsolicited request, Windows
Firewall blocks the connection. If you run a program such as an instant messaging program or a
multiplayer network game that needs to receive information from the Internet or a network, the
firewall asks if you want to block or unblock (allow) the connection. You should see a window like
the one below.

Firewall Security Alert

If you choose to unblock the connection, Windows Firewall creates an exception so that the
firewall won't bother you when that program needs to receive information in the future. To learn
more about exceptions, see the Using the Exceptions Tab section given below.
Tip Although you can turn off Windows Firewall for specific Internet and network connections,
doing this increases the risk to your computer's security.

What Windows Firewall Does and Does Not Do

It does It does not

Help block computer viruses and Detect or disable computer viruses and worms if they
worms from reaching your are already on your computer. For that reason, you should
computer. also install antivirus software and keep it updated to help
prevent viruses, worms, and other security threats from
damaging your computer or using your computer to spread
viruses to others. For more information
Ask for your permission to block Stop you from opening e-mail with dangerous
or unblock certain connection attachments. Don't open e-mail attachments from senders
HMI 6.1 Service Pack 4 Page 29 of 43
It does It does not
requests. that you don't know. Even if you know and trust the source
of the e-mail you should still be cautious. If someone you
know sends you an e-mail attachment, look at the subject
line carefully before opening it. If the subject line is gibberish
or does not make any sense to you, check with the sender
before opening it.
Create a record (a security log), if Block spam or unsolicited e-mail from appearing in your
you want one, that records inbox. However, some e-mail programs can help you do this.
successful and unsuccessful Check the documentation for your e-mail program
attempts to connect to your
computer. This can be useful as a
troubleshooting tool.

Using the Exceptions Tab

If you're running Windows XP Service Pack 2 (SP2) the Windows Firewall is turned on by
default. This means that most programs will not be allowed to accept unsolicited
communications from the Internet unless you choose to list those programs as exceptions.
There are two programs that, by default, are already added to the exceptions list and can accept
unsolicited communications from the Internet: Files and Settings Transfer Wizard and File and
Printer Sharing.
Because firewalls restrict communication between your computer and the Internet, you might
need to adjust settings for some other programs that prefer an open connection. You can make
an exception for these programs, so that they can communicate through the Windows Firewall.

Allowing Exceptions—the Risks

Each time you allow an exception for a program to communicate through Windows Firewall, your
computer is made more vulnerable. To allow an exception is like poking a hole through the
firewall. If there are too many holes, there's not much wall left in your firewall. Hackers often use
software that scans the Internet looking for computers with unprotected connections. If you have
lots of exceptions and open ports, your computer can become more vulnerable.

To help decrease your security risk:

• Only allow an exception when you really need it.
• Never allow an exception for a program that you don't recognize.
• Remove an exception when you no longer need it.

Allowing Exceptions Despite the Risks

HMI 6.1 Service Pack 4 Page 30 of 43

Sometimes you might want someone to be able to connect to your computer, despite the risk—
such as when you expect to receive a file sent through an instant messaging program, or when
you play a multiplayer game over the Internet.
For example, if you're exchanging instant messages with someone who wants to send you a file
(a photo, for example), Windows Firewall will ask you if you want to unblock the connection and
allow the photo to reach your computer. Or, if you want to play a multiplayer network game with
friends over the Internet, you can add the game as an exception so that the firewall will allow the
game information to reach your computer.

To add a program to the exceptions list

1. Click Start and then click Control Panel.
2. In the control panel, click Windows Firewall.
3. On the Exceptions tab, under Programs and Services, select the check box for the
program or service that you want to allow, and then click OK.

Windows Firewall Exceptions tab

If the program (or service) that you want to allow is not listed
1. Click Add Program.
2. In the Add a Program dialog box, click the program that you want to add, and then click
OK. The program will appear, selected, on the Exceptions tab, under Programs and
Services.
3. Click OK.
HMI 6.1 Service Pack 4 Page 31 of 43
Tip If the program (or service) that you want to allow is not listed in the Add a Program dialog
box click Browse, locate the program that you want to add, and then double-click it. (Programs
are usually stored in the Program Files folder on your computer.) The program will appear under
Programs, in the Add a Program dialog box.

As a Last Resort, Open a Port

If you still do not find the program, you can open a port instead. A port is like a small door in the
firewall that allows communications to pass through. To specify which port to open, on the
Exceptions tab, click Add Port. (When you open a port, remember to close it again when you
are done using it.)

Adding an exception is preferable to opening a port because:

• It is easier to do.
• You do not need to know which port number to use.
• It is more secure than opening a port, because the firewall is only open while the program is
waiting to receive the connection.

Advanced Options
Advanced users can open ports for, and configure the scope of, individual connections to
minimize opportunities for intruders to connect to a computer or network. To do this, open
Windows Firewall, click the Advanced tab, and use the settings under Network Connection
Settings.

How to Share and Set Permissions for Folders and Files Using Windows XP

File and Printer Sharing for Microsoft Networks

The File and Printer Sharing for Microsoft Networks component allows computers on a network
to access resources on other computers using a Microsoft network. This component is installed
and enabled by default. It is enabled per connection using TCP/IP and is necessary to share
local folders.
The File and Printer Sharing for Microsoft Networks component is the equivalent of the Server
service in Windows NT 4.0.
To share folders with other users on your network
1. Open My Documents in Windows Explorer. Click Start, point to All Programs, point to
Accessories, and then click Windows Explorer.
2. Click the folder you want to share.
3. Click Share this folder in File and Folder Tasks.
4. In the Properties dialog box select the radio button Share this folder to share the folder
with other users on your network, as shown in Figure 1 below.

HMI 6.1 Service Pack 4 Page 32 of 43

 Figure 1. Sharing a folder on a network
To change the name of the folder on the network, type a new name for the folder in the
5. Share name text box. This will not change the name of the folder on your computer.
Note The Sharing option is not available for the Documents and Settings, Program Files,
and Windows system folders. In addition, you cannot share folders in other users’ profiles.
To set, view, change, or remove file and folder permissions
1. Open Windows Explorer, and then locate the file or folder for which you want to set
permissions. To open Windows Explore click Start, point to All Programs, point to
Accessories, and then click Windows Explorer.
2. Right-click the file or folder, click Properties, and then click the Security tab as shown in
Figure 2 below.

HMI 6.1 Service Pack 4 Page 33 of 43

 Figure 2. Setting file and folder permissions
To set permissions for a group or user that does not appear in the Group or user names
3. box, click Add. Type the name of the group or user you want to set permissions for and then
click OK, as shown in Figure 3 below.

Figure 3. Adding new group or user permissions

To change or remove permissions from an existing group or user, click the name of the
4. group or user and do one of the following, as shown in Figure 2 above:
• To allow or deny a permission, in the Permissions for...box, select the Allow or Deny
check box.
• To remove the group or user from the Group or user names box, click Remove.

Notes
• In Windows XP Professional, the Everyone group no longer includes Anonymous Logon.
• You can set file and folder permissions only on drives formatted to use NTFS.
• To change permissions you must be the owner, or have been granted permission to do so
by the owner.
• Groups or users granted Full Control for a folder can delete files and subfolders within that
folder regardless of the permissions protecting the files and subfolders.

HMI 6.1 Service Pack 4 Page 34 of 43

 • If the check boxes under Permissions for user or group are shaded or if the Remove
button is unavailable, then the file or folder has inherited permissions from the parent folder.
• When adding a new user or group, by default, this user or group will have Read & Execute,
List Folder Contents, and Read permissions.

HMI 6.1 Service Pack 4 Page 35 of 43

 Below is a list of the CIMPLICITY HMI subsystems and the TCP ports that are used for
communications.
The following ports need to be opened in order for CIMPLICITY HMI to function correctly with the
Windows XP Service Pack 2 Firewall turned on:

Subsystem TCP Port Usage Comments

Router TCP 32000, 32256, 32512, Not configurable

32768, UDP 32000
RtrPing TCP 4000 Configurable using
REDUND_PROBE_PORT
global parm
WebView TCP 80 Configurable from CIMPLICITY
TCP 10212 Options &
Configurable in the Windows
registry
Cabling Redundancy TCP 5000 to 6000 Configurable in
CIMHOSTS.TXT
Allen-Bradley RSLINX actually opens the ports. Depends on selected protocol
Ethernet -- contact Rockwell for
additional information
Allen-Bradley DH ISA Card Interface
Plus
Allen-Bradley DF1 Serial
Allen-Bradley Serial
Intelligent Antenna
Advanced DDE TCP 137, 9, 445, 135
Client
CCM2 Serial
Florpro/Flonet TCP 165
Honeywell IPC 620 Serial or TCP/Telnet User Configurable Port
Johnson Controls N2 Serial or TCP/Telnet User Configurable Port
Serial
Marquee Driver Serial or TCP/Telnet User Configurable Port
Mitsubishi-A Serial Serial
Mitsubishi TCP/IP TCP User configurable
Modbus Plus ISA Card Interface
Modbus RTU Serial or TCP/Telnet User Configurable Port
Modbus TCP/IP TCP For polled communication, any
port to destination:502
Omron Host Link

HMI 6.1 Service Pack 4 Page 36 of 43

 Omron TCP/IP TCP User configurable
OPC Client TCP 137, 9, 445, 135
S90 Triplex TCP 18245
For polled communication any
port to destination 18245
S90 Ethernet / Host TCP 18245
Communications UDP 18245, 18246
Toolkit
Sharp TCP/IP TCP User configurable
Siemens TI Serial Serial
Smart Eye Serial or TCP/Telnet User Configurable Port
SNP Serial
SNPX Serial or TCP/Telnet User Configurable Port
SquareD Serial or TCP/Telnet User Configurable Port
Toyopuc TCP User configurable port
MMS SISCO Stack (Port 102) Contact SISCO for more details
FANUC CNCs (for Varies – requires at least 2n+1 Contact CNC team for more
HMI for CNC) ports (two for each device, plus information
one for the alarm manager)

HMI 6.1 Service Pack 4 Page 37 of 43

 The following executables need to be allowed in order for CIMPLICITY HMI to function correctly
with the Windows XP Service Pack 2 Firewall turned on:
Area Executable Name Comments
Base Functionality cpc.exe
amrp.exe
dc_sim.exe
pm_driver.exe
pm_mcp.exe
ptm_rp.exe
ShowUser.exe
ur.exe
ptmrp_msx.exe
rtr_driver.exe
w32rtr.exe
ptdl.exe
dl_rp.exe
emrp.exe
RtrPing.exe
apsm_rp.exe
sqlserv.exe
WebView CimWebServer.exe
Device dc_diag.exe Devccom Diagnostics
Communications toolkit.exe Toolkit
map_mms.exe MMS
abint_rp.exe Allen-Bradley TCP/IP
abkt_rp.exe Allen-Bradley KT
abrfid_rp.exe Allen-Bradley RF-ID
dde_rp.exe DDE
NTDevSim.exe Dev Sim
flopro_rp.exe FloPro
gefplc_rp.exe GEF PLC
hct_rp.exe HCT
hctgmr_rp.exe HCTGMR
hwabc_rp.exe Honeywell ABC
mb_rp.exe Modbus
mbeth_rp.exe Modbus TCP/IP
mbplus_rp.exe Modbus Plus
melsec_rp.exe Melsec
mits_srl.exe Mitsubishi Serial
nr_rp.exe Johnson Control
omrn_eth.exe Omron TCP/IP
omrn_srl.exe Omron Serial
CimOPCClient.exe OPC Client
pb_rp.exe Point Bridge
perfread_rp.exe Perfread
s90tcp.exe Series 90 TCP/IP
sharp_rp.exe Sharp
sea_rp.exe SmartEye
snp_rp.exe SNP
snpx_rp.exe SNP-X

HMI 6.1 Service Pack 4 Page 38 of 43

 sd_rp.exe (symax) Symax
ti_rp.exe (ti) Texas Instruments
Tracker prt_ui.exe
prtc.exe
prts.exe
prtdb.exe
rcosite.exe
rcocfg_ui.exe
rco_ui.exe
rcodb_rp.exe

DCOM Settings
1. In Windows Control Panel, double-click Administrative Tools. The Administrative Tools dialog
box appears.
2. Double-click Component Services. The Component Services dialog box appears, where
you can access DCOM security.
3. Expand the Component Services folder and continue expanding folders until you locate the
My Computer icon.
4. Right click My Computer and choose Properties. The My Computer Properties dialog box
appears.
5. Click the COM Security tab.
6. In the Access Permissions section, click Edit Limits. The Access Permission dialog box
appears.
7. Select the Remote Access Allow check box for the ANONYMOUS LOGON group.
8. Click OK.

If Firewall is enabled
1. In Windows Control Panel, double-click Windows Security Center. The Windows Security
Center dialog box appears.
2. Click Firewall. The Windows Firewall dialog box appears.
3. Click the Exceptions tab.
4. Click Add Port. The Add a Port dialog box appears.
5. In the Name field, enter a name for the port.
6. In the Port number field, enter 135.
7. NOTE: In the event that port number 135 does not work, the ports 137, 9, or 445 can also be
used.
8. Click OK to return to the Exceptions tab.
9. Click Add Program. The Add a Program dialog box appears.
10. In the Path field, browse to the location of your CIMPLICITY installation; for example,
C:\Cimplicity\HMI\EXE.
11. From the Programs list, select CimOPCClient.exe.
12. Click OK.
13. Click OK to add it to the exceptions list.

HMI 6.1 Service Pack 4 Page 39 of 43

Disclaimer
GE Fanuc cannot guarantee that the above procedures will work on every system. The security
features provided in Windows XP SP2 and greater are widespread and complex. GE Fanuc’s
experience, through testing, has shown that variability between systems, such as installed
software, registry configuration, system and network configuration, etc., result in the security
settings behaving differently on different systems. Therefore, be aware that following these
procedures as written, may not produce the same results on every system. GE Fanuc
recommends using the above steps as an initial starting point when configuring your Windows XP
SP2 system to run our software. For more detailed information on configuring Windows XP SP2,
please refer to the Microsoft documentation.

HMI 6.1 Service Pack 4 Page 40 of 43