KEPServer Enterprise Release Notes

Welcome to KEPServer Enterprise.

KEPServer Enterprise provides OPC server connectivity with over 40

different PLCs and devices for the following FactoryTalk View products:
� FactoryTalk View Machine Edition, Supervisory Edition or RSView32 running
on a Workstation computer. The OPC servers for Workstation
computers support the Microsoft Windows 7 Professional, Vista, XP, 2000,

2008, NT, 98 & 95 operating systems. FactoryTalk View Studio and

RSView32 also use these drivers during application development.

� FactoryTalk View Machine Edition running on a PanelView Plus or

PanelView CE.

If you are using KEPServer Enterprise on PanelView Plus or PanelView Plus CE,
use the Firmware Upgrade Wizard to download the drivers. The firmware upgrade
wizard can be downloaded from the Rockwell Automation Technical Support
website at http://support.rockwellautomation.com.

KEPServer Enterprise does not require an activation key for use with
FactoryTalk View Machine Edition. KEPServer Enterprise is activated by the
FactoryTalk View Studio key during application development or by FactoryTalk View
ME Station on PanelView Plus, PanelView Plus CE or Workstation computer at runtime.

KEPServer Enterprise requires an activation key for use with FactoryTalk View
Supervisory Edition or RSView32. Activation is included with KEPServer Enterprise
when ordered for use with FactoryTalk View Supervisory Edition or RSView32.

********************************************************************************
KEPSERVER ENTERPRISE COMPATIBILITY

FactoryTalk View Machine Edition V6.0 v5.1

PanelView Plus 6 KEPServer 5.3 N/A
PanelView Plus CE N/A KEPServer 4.5
PanelView Plus N/A KEPServer 4.5
Windows Desktop KEPServer 5.3 KEPServer 4.5
and/or
KEPServer 4.5

* For FactoryTalk view Studio, install both versions of KEPServer when creating
MERs
for FactoryTalk view ME v5.1 and FactoryTalk View ME v6.0 terminals

* For FactoryTalk View ME Station, install KEPServer 5.3 on Vista and newer
operating systems.

********************************************************************************
DRIVERS

Included on the CD is the KEPServer Enterprise OPC Server � featuring the

following drivers. If the driver you require is not listed here please contact
your local Rockwell Automation office or distributor to see if and when the
driver may be available.

KEPServer Enterprise Drivers v5.3

Drivers available for the PanelView Plus, PanelView Plus 6 and
PanelView Plus CE with FactoryTalk View Machine Edition are marked with an
asterisk.

Analog Devices
Aromat
Aromat Ethernet
*Automation Direct EBC
*Automation Direct ECOM
*BACNET
BUSWARE Ethernet
Contrex
Contrex M Series
Cutler-Hammer
DDE Client Driver
*DIRECT-NET
*EtherTRAK
Fuji Flex
GE CCM
*GE Ethernet
*GE Ethernet Global Data
GE Focus 1 Ethernet
GE SNP (not supported by PanelView Plus 6)
GE SNPX (not supported by PanelView Plus 6)
Hilscher Universal
Honeywell UDC
IA Super SEL
IDEC
IO Pointscan 100
K Sequence
Micro-DCI
*Mitsubushi A Series
*Mitsubushi Ethernet
*Mitsubishi FX
*Mitsubishi FX Net
*Modbus Ascii Serial
*Modbus Ethernet
Modbus Plus
*Modbus Serial
*Modbus Unsolicited Serial
*Omron FINS Ethernet
*Omron FINS Serial
*Omron Host Link
*Omron Process Suite
Optimation Optilogic
Partlow Ascii
Phillips P8/PC20
*Siemens S5
Siemens S5 (3964R)
*Siemens TCP/IP Ethernet
*Simatic 505
*Simatic 505 Ethernet
*Simulator
*SquareD
Thermo Westronics Ethernet
Thermo Westronics Serial
*TIWAY Host Adapter
Toshiba
Toshiba Ethernet
Toyopuc Ethernet PC3/PC2
 Toyopuc Serial
*Uni-Telway
*User Configurable Driver
Wago Ethernet
Yaskawa Memobus Plus
Yokogawa Darwin
Yokogawa Darwin Serial
Yokogawa DX
Yokogawa DX Serial
Yokogawa DXP

KEPServer Enterprise v4.5 Drivers

Drivers available for the PanelView Plus and
PanelView Plus CE with FactoryTalk View Machine Edition are marked with an
asterisk.

Analog Devices
Aromat
Aromat Ethernet
*Automation Direct EBC
*Automation Direct ECOM
*BACNET
BUSWARE Ethernet
Contrex
Contrex M Series
Cutler-Hammer
DDE Client Driver
*DIRECT-NET
*EtherTRAK
Fuji Flex
GE CCM
*GE Ethernet
*GE Ethernet Global Data
GE Focus 1 Ethernet
GE SNP (not supported by PanelView Plus 6)
GE SNPX (not supported by PanelView Plus 6)
Honeywell UDC
IA Super SEL
IDEC
IO Pointscan 100
K Sequence
Micro-DCI
*Mitsubushi A Series
*Mitsubushi Ethernet
*Mitsubishi FX
*Mitsubishi FX Net
*Modbus Ascii Serial
*Modbus Ethernet
Modbus Plus
*Modbus Serial
*Modbus Unsolicited Serial
*Omron FINS Ethernet
*Omron FINS Serial
*Omron Host Link
*Omron Process Suite
Optimation Optilogic
Partlow Ascii
 Phillips P8/PC20
*Siemens S5
Siemens S5 (3964R)
*Siemens S7 MPI
*Siemens S7-200
*Siemens TCP/IP Ethernet
*Simatic 505 Serial
*Simatic 505 Ethernet
*Simulator
*SquareD
Thermo Westronics Ethernet
Thermo Westronics Serial
*TIWAY Host Adapter
Toshiba
Toshiba Ethernet
Toyopuc Ethernet PC3/PC2
Toyopuc Serial
*Uni-Telway
*User Configurable Driver
Wago Ethernet
Yaskawa Memobus Plus
Yokogawa Darwin
Yokogawa Darwin Serial
Yokogawa DX
Yokogawa DX Serial
Yokogawa DXP

********************************************************************************
KEPServer Enterprise additional information:

1. The KEPServer Enterprise software contains complete on-line help to assist

with KEPServer setup and driver configuration.

2. Whether your runtime target is the workstation, PanelView Plus 6, PanelView Plus

or PanelView Plus CE, you will need to configure KEPServer Enterprise to

communicate to your device from the workstation.

If your runtime target is the PanelView Plus 6, PanelView Plus or PanelView Plus
CE, the KEPServer Enterprise data is compiled into the FactoryTalk View
Machine Edition .MER file when the runtime project is created.

The KEPServer project file which gets compiled in the MER is dependent on
the KEPServer "Default Project" setting which is configured under
Tools>Options>General>Project File Settings. If you have changed the name
of the current KEPServer project you must also change the name
of the "Default Project" to ensure the correct project file gets
compiled into the MER for use on the PanelView Plus and PanelView Plus CE.

When the MER is opened on PanelView Plus CE the KEPware

project file (example: default.pfe) is stored along with the projects
temporary files in the directory "KepServer".
Example: "\Storage Card\Rockwell Software\RSViewME\Temp\~MER.00\KepServer"
This will be the location of the server project file if the temporary files
were configured to be stored in the default location.
3. KEPServer Enterprise comes with an OPC test client application.
For information on the Workstation OPC test client please see the OPC Quick
Client on-line help.

The PanelView Plus CE test client application can be found at:

\Storage Card\KEPServerEnterprise\opcquickclient_ce.exe.

This client allows you to test KEPServer OPC data items.

In order for the KEPServer to use the correct project file you must first
open your MER which contains the KEPServer items.
This extracts the KEPServer project file required by the server.

The KEPServer Enterprise OPC test client application is not available for the
PanelView Plus.

4. If you have selected a serial driver you will need to configure the serial port
settings for KEPServer Enterprise on the workstation. If your runtime target is
the PanelView Plus or PanelView Plus CE the serial ports will be configured
when the client connects to the server and the server loads the project
file (default.pfe).

5. KEPServer event messages are routed through the FactoryTalk View

Diagnostics Log System. No messages will be logged to the FactoryTalk View
Diagnostics log if it is not configured. The ability to control which
diagnostic events are displayed in FactoryTalk View is determined by the
settings in the Diagnostics Setup editor in FactoryTalk View Studio and not
by the Event Log settings in KEPServer Enterprise. In the FactoryTalk View
Diagnostics Log system, KEPServer Enterprise events are
added to the 'Operator� category. There are three kinds of event messages
that are logged: Info, Warning and Error messages. The user controls which
event messages will be logged to the Diagnostics Log system from the
Diagnostics Setup editor.

********************************************************************************
Key Differences between KEPServerEnterprise V4 and V5:

1. Overview

This guide intends to provide a brief description of the differences between

KEPServerEnterprise V4 and KEPServerEnterprise V5. For more information on features
and options, refer to the KEPServerEnterprise V5 help file.

2. Changes Made in KEPServerEnterprise V5

The most important change made in KEPServerEnterprise V5 is the separation of

the Configuration and the Runtime. The server Runtime is now administered through
a separate administration utility. This separation allows projects to be both
created and edited either online or offline.

2.1 Server Administration

Several changes have been made to the server administration as a consequence of

separating the server Runtime from the Configuration. Many settings that impact
how a project runs have been moved to the Project Properties, and travel with
a project when it is moved to a new PC.
Settings that affect how the server works (such as DCOM configuration) have
been moved to the KEPServerEnterprise Administration menu. Affected functions
and processes are as follows:
� Runtime start and stop.
� Client connection re-initialization.
� Event Log re-initialization.
� User Management.
� UA Management.
� Server Settings, including DCOM Management, Runtime Process Mode
(Service or Desktop), Process Priority, and Processor Affinity
(multi-core CPU Management).

2.2 KEPServerEnterprise V5 Configuration

As previously mentioned, KEPServerEnterprise V5 separates the server Runtime

and Configuration. This means that users can create or edit a project while
online or offline. Since the Runtime uses a default project, users must save
the edited online project to an OPC or XML-formatted file in order to move
it to another PC. Project settings can now be accessed through the Configuration
by clicking File | Project Properties. Settings include the V4 Project
Identification information, OPC DA, OPC DA Compliance, OPC AE, and OPC UA.

2.3 Security

2.3.1 OPC Client Connections

In order to address the demand for improved OPC and DCOM configuration
security, KEPServerEnterprise V5 enforces strict DCOM compliance at startup.
This server setting is enabled through the Runtime Options dialog, which is
located through the Administration menu by clicking Settings | Runtime Options.
The option is located beneath OPC Connection Security, in the checkbox
"Use DCOM configuration utility settings." The default setting is checked.
In KEPServerEnterprise V4, this option is located through the Configuration
by clicking Tools | Options� | OPC Settings. The default setting is unchecked.
This means that as long as DCOM is configured, local clients can connect.
Note: Users that are unable to connect to KEPServerEnterprise V5 but are able
to connect to KEPServerEnterprise V4 should uncheck this option.

2.3.2 Advanced Simulator

The Advanced Simulator Driver uses ODBC to connect to data sources. When
running as a service, users can only connect to a data source defined as
a System DSN. When running interactively on the desktop, users should
utilize User or System DSNs. It is recommended that System DSNs be used.

2.3.3 DDE Client Driver

Since DDE cannot run as a service, the DDE Client Driver can only be used
when the server is running interactively on the desktop.

2.3.4 InTouch Client Driver

The InTouch Client Driver works similarly to the DDE Client Driver. It
can only be used when the server is running interactively on the desktop.

2.3.5 ODBC Client Driver

The ODBC Client Driver uses ODBC to connect to data sources. When running
as a service, users can only connect to a data source defined as a System
DSN. When running interactively on the desktop, users should utilize User
or System DSNs. It is recommended that System DSNs be used.

2.3.6 OPC DA Client Driver

The OPC DA Client Driver is an OPC DA connection and depends on DCOM just
like any other OPC DA client. In order for this driver to work correctly,
users must properly configure DCOM on all machines involved in the OPC connection.

********************************************************************************
ANOMALIES FIXED

KepserverEnterprise V4.500.465.0

BACnet/IP V4.65.54.0

KS-7532
Fixed channel wizard issue that prevented a user from moving to the next page
under certain circumstances.

KS-7011
Fixed issue with processing multiple read property responses from certain
brands of hardware. The issue resulted in toggling the quality of all items
associated with object and repeated "device not responding" errors.

------------------------------------------------------------------------------

Idec Serial V4.40.71.0

KS-8616
Added support for "Extra Data Register" (D10000-D49999) for the MicroSmart model
(for Slim Type CPU modules only).

------------------------------------------------------------------------------
SquareD Serial V4.10.74.0

KS-8877
Fixed issue where the driver was not parsing received data packets correctly
when the route ID contained one or more nodes that were not equal to 255.

------------------------------------------------------------------------------
UCON (user configurable) V4.210.183.0

KS-8941
Fixed issue where the Event counter was not incrementing for unsolicited
transactions when a command preceded an initial read response.

KS-8941
Fixed issue with the �Update Tag� command where it would try to parse to the
next delimiter if the tag device data format option was selected (but disabled
in UI) and the fixed length option was also selected.

KS-8775
Fixed issue with ASCII Real and ASCII Real (packed 6-bit) formats where
legacy projects failed to load a default value for the "Use decimal comma in
place of decimal point" option in the format properties.

Fixed issue with ASCII Real and ASCII Real (packed 6-bit) formats where
non-negative numbers with negative exponents only displayed the exponent.

------------------------------------------------------------------------------
Yokogawa CX Ethernet V4.30.55.0

KS-8595
Fixed issue where a device returning an error code to a command would cause
the driver to timeout, rather than process the error.

------------------------------------------------------------------------------

Omron FINS Ethernet V4.102.73.0

KS-8623
Fixed issue where communications to the PLC would sometimes fail.

Server Runtime V4.500.465.0

KS-8013
Fixed issue where a memory leak occurred when loading invalid XML files, either
manually through the UI or through the IPersistFile interface.

KS-8279
Fixed issue where an invalid branch could be returned to a client application
when using OPC Browse.

------------------------------------------------------------------------------
Server Runtime (CE Only) V4.500.465.0

KS-10903
Fixed issue with Asynchronous writes with 2 Clients referencing the same tag.

KS-11151
Fixed issue where a project containing tags with scaling could not be loaded.