Rockwell Automation 1757-PROCESSLINX User Manual
ProcessLinx OPC
Server to Server
Software
1757-PROCESSLINX
User Manual
Important User Information
Because of the variety of uses for the products described in this publication,
those responsible for the application and use of this control equipment must
satisfy themselves that all necessary steps have been taken to assure that each
application and use meets all performance and safety requirements, including
any applicable laws, regulations, codes and standards.
The illustrations, charts, sample programs and layout examples shown in this
guide are intended solely for purposes of example. Since there are many
variables and requirements associated with any particular installation,
Allen-Bradley does not assume responsibility or liability (to include intellectual
property liability) for actual use based upon the examples shown in this
publication.
Allen-Bradley publication SGI-1.1, Safety Guidelines for the Application, Installation
and Maintenance of Solid-State Control (available from your local Allen-Bradley
office), describes some important differences between solid-state equipment
and electromechanical devices that should be taken into consideration when
applying products such as those described in this publication.
Reproduction of the contents of this copyrighted publication, in whole or part,
without written permission of Rockwell Automation, is prohibited.
Throughout this manual we use notes to make you aware of safety
considerations:
ATTENTION
Identifies information about practices or circumstances
that can lead to personal injury or death, property damage
or economic loss
!
Attention statements help you to:
• identify a hazard
• avoid a hazard
• recognize the consequences
IMPORTANT
Allen-Bradley is a trademark of Rockwell Automation, Inc.
Identifies information that is critical for successful
application and understanding of the product.
Preface
Introduction
Overview
This document provides an overview of the ProcessLinx application.
ProcessLinx allows two OPC servers to communicate. Normally a server talks
to a client and visa versa. A server cannot talk to another server because the
interfaces are incompatible. ProcessLinx is specilized software that allows two
servers to communicate.
The OPC (OLE for Process Control) Interface within ProcessLinx acts as an
OPC Client to a ProcessLogix OPC Server as well as to another OPC server.
To interface from ProcessLogix to another server, a ProcessLinx TagMap
configuration must be created. This configuration maps the items from one
system to the other. This is accomplished through the exchange of data with
entities known as tags or OPC items. The OPC items can be logically Grouped
together. ProcessLinx supports both local and remote OPC Servers.
This interface supports bi-directional data flow and supervisory control
between ProcessLogix and other control systems. It enables operators to
control digital and analog control loops implemented within ProcessLogix
controllers from external control system operator consoles. Likewise,
ProcessLogix operator stations may also be used for operator control of digital
and analog control loops implemented in other control system processors.
These capabilities depend on the functionality supported by the external OPC
Server being utilized. ProcessLinx is fully compliant with Versions 2.0 and 1.0a
OPC Data Access Servers.
Functional Description
The ProcessLinx interface runs under the Windows NT/Windows 2000
Professional operating system(s). Two modes of operation are associated with
the interface, which are “configure” and “runtime”. In configure mode a user
can change settings and create TagMaps. In runtime mode the interface uses
the currently loaded configuration to communicate with the external OPC
Server(s). ProcessLinx supports the following:
• OPC Server configuration dialog allows user to define the external OPC
Server by browsing and selecting an existing OPC Server.
• Supports redundant ProcessLogix OPC Servers as well as redundant
external OPC servers by recognizing server fail-over mechanisms.
• Simple TagMap definition dialog allows mapping of an external OPC
Server tag to a ProcessLogix OPC Server tag. Tag Map definition will
include attributes such as OPC Item names, description and data source.
Optionally, scaling conversion using translation tables can be defined to
translate values from one system to the other.
• The number of user-defined TagMap definitions is unlimited.
1 Publication 1757-UM002B-EN-P - January 2003
P-2
• Tag Map configurations are stored in a serialized compact binary file.
• Supports ability to easily import and export ProcessLinx Tag Map
configurations to/from comma delimited (*.csv) ASCII files, which can
be created and/or edited with Microsoft Excel, Microsoft Access or any
text editor.
• Error and informational messages displayed in the main window in
runtime along with optional user-configurable specification maintaining
this data in daily log files.
• Runtime tag monitoring ability to view and change (read/write) data
values in either OPC Server from main client window.
Publication 1757-UM002B-EN-P - January 2003
P-3
Rockwell Automation Technical Support
Rockwell Automation offers support services worldwide, with over 75
sales/support offices, 512 authorized distributors, and 260 authorized systems
integrators located throughout the United States alone, plus Rockwell
Automation representatives in every major country in the world.
Local Product Support
Contact your local Rockwell Automation representative for:
• sales and order support
• product technical training
• warranty support
• support service agreements
Technical Product Assistance
If you need to contact Rockwell Automation for technical assistance, first call
your local Rockwell Automation representative, then:
• Network Pre-sales Hotline, 440.646.3638 (3NET)
• Post-sales Technical Support, 440.646.5800
• Web Links
http://www.ab.com — as a registered member, open to
http://www.ab.com/mem/technotes/techmain.html
Your Questions or Comments about This Manual
If you find a problem or have a comment about this manual, please notify us
of it on the enclosed Publication Problem Report (at the back of this manual).
If you have any suggestions about how we can make this manual more useful
to you, please contact us at the following address:
Rockwell Automation, Allen-Bradley Company, Inc.
Control and Information Group
Technical Communication
1 Allen-Bradley Drive
Mayfield Heights, OH 44124-6118
Publication 1757-UM002B-EN-P - January 2003
P-4
Conventions
Terms and Type Representations
The following table summarizes the terms and type representation
conventions used in this Guide.
Term/Type
Representation
click, click on, click
[button name]
double-click Click left mouse button twice in
drag Press and hold left mouse button
right-click Click right mouse button once.
Meaning Example
Click left mouse button once.
(Assumes cursor is positioned on
object or selection.)
quick succession. (Assumes cursor
is positioned on object or
selection.)
while dragging cursor to new
screen location and then release
the button. (Assumes cursor is
positioned on object or selection to
be moved.)
(Assumes cursor is positioned on
object or selection.)
Click Apply.
Double-click the Pipe.
Drag the file icon onto the
new folder window.
Right-click, and the pop-up
menu appears.
select click to highlight a menu item or
list choice, or click on a button.
<F1> Keys to be pressed are shown in
angle brackets.
<Ctrl>+<C> Keys to be pressed together are
shown with a plus sign.
File
⇒ New
>D:\setup.exe< Data to be keyed in at prompt or in
Shows menu selection as menu
name followed by menu selection.
an entry field.
Select the OPC Item from the
list box.
Press <F1> to view the online
Help.
Press <Ctrl>+<C> to configure
the Pipe.
Click Edit ⇒ Add New
Group to create a Group.
Key in this path location
>D:\setup.exe<.
Publication 1757-UM002B-EN-P - January 2003
Table of Contents
Preface
Chapter1
Setup Procedures
Chapter 2
Getting Started
Chapter 3
ProcessLinx TagMap
Configuration
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-1
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-1
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-1
Rockwell Automation Technical Support. . . . . . . . . . . . . . . . . . . . . . P-3
Local Product Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-3
Technical Product Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-3
Your Questions or Comments about This Manual . . . . . . . . . . . P-3
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-4
Terms and Type Representations . . . . . . . . . . . . . . . . . . . . . . . . . P-4
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Configuring DCS Components. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Installing OPC Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Defining an Interface Control Strategy. . . . . . . . . . . . . . . . . . . . . 1-2
Creating OPC Server Configurations . . . . . . . . . . . . . . . . . . . . . . 1-2
Configure the OPC Server(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Installing ProcessLinx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Preparing the Client’s User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Running Updates on the ProcessLinx Client’s Registry. . . . . . . . 1-4
ProcessLinx Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Configure Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Runtime Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Configure ProcessLinx Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Creating a ProcessLinx Configuration . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Opening a ProcessLinx Configuration . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Creating a Pipe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Creating a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Creating a TagMap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Creating a ProcessLinx TagMap Configuration . . . . . . . . . . . . . 3-15
Data Conversion/Scaling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
OPC Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Translation Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Editing a Pipe, Group or TagMap. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Copying/Moving TagMaps between Groups. . . . . . . . . . . . . . . . . . 3-22
Multiple TagMap Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Testing a ProcessLinx Configuration . . . . . . . . . . . . . . . . . . . . . . . . 3-24
i Publication 1757-UM002B-EN-P - January 2003
Table of Contents ii
Chapter 4
ProcessLinx Runtime Operation
Chapter 5
Import/Export
Chapter 6
Error Diagnosis and Debugging
Chapter 7
Using DCOM OPC Servers
Monitoring Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Reading OPC Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Writing OPC Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Redundant OPC Servers / Fail over . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Server Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Verifying OPC Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
OPCShutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
CSV File Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Pipe Declarations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Group Declarations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
TagMap Declarations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Translation Table declarations . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Quick Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Debug Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
OPC Servers on Windows NT/Windows 2000 . . . . . . . . . . . . . . . . . 7-1
OPC Servers on Windows98 / Windows 95 . . . . . . . . . . . . . . . . . . . 7-2
Publication 1757-UM002B-EN-P - January 2003
Setup Procedures
Chapter
1
Installation
This chapter contains an overview of the setup procedure and the steps you
need to take to set up a configuration prior to using ProcessLinx.
Configuring DCS Components
IMPORTANT
All DCS Components must be configured first in the setup procedure. This
includes installation and setup of the following:
• ProcessLogix System – The ProcessLogix system must be setup and
installed on the PC used to access the ProcessLogix OPC Server.
• DCS – The other DCS system is assumed to be setup prior to
performing the steps in the section Creating a ProcessLinx TagMap
Configuration on page 3-10.
You are required to configure the DCS components before
installing ProcessLinx. If the DCS components are not
configured correctly, server communications will not
succeed.
Installing OPC Servers
Install the desired OPC servers. If a remote DCOM connection is required,
verify the PC is setup on the network with the TCP/IP protocol installed. The
OPC Servers are specified below:
ProcessLogix OPC Server
All of the software components of the ProcessLogix OPC Server are installed
during the ProcessLogix Server installation.
IMPORTANT
1 Publication 1757-UM002B-EN-P - January 2003
The OPC Server option MUST be included with your
ProcessLogix license.
1-2 Setup Procedures
In order for ProcessLinx to connect to the ProcessLogix OPC Server over the
network, the OPC Server Connect option must be installed on the client PC.
Refer to the ProcessLogix Knowledge Builder:
Navigate in Knowledge Builder to
⇒Server and Client Configuration Guide ⇒Using ProcessLogix Data in other Applications
⇒ ProcessLogix OPC Support.
External OPC Server
Consult the External OPC Server documentation for correct installation and
setup on the desired node. This does not have to be the same PC or node
running ProcessLinx. Verify the External OPC Server operation separately.
Defining an Interface Control Strategy
Define the site specific DCS Control Strategy. This step assumes that you have
two working DCS configurations, one in ProcessLogix, and the other in an
external DCS system. This step includes defining exactly which points (control
loops, pumps, motors, etc.) are to be controlled and interfaced and by which
system. This step also tentatively outlines the direction and flow of data
and/or specifies which system is in control of each interfaced point.
It is emphasized that if this step is not performed, data flow direction and
determination of what point is coming from where may get very confusing in
the future. A table laying out all desired interface points, their names within
both systems, and data flow directions should be created and documented for
future reference.
Publication 1757-UM002B-EN-P - January 2003
Creating OPC Server Configurations
Before a ProcessLinx configuration can be realized, an OPC Server database
must be built which defines references to I/O points in the underlying desired
hardware or to control points. With ProcessLogix, this step is not required
since control points defined using Control Builder are immediately available
from the ProcessLogix OPC Server. No OPC Server configuration must be
built for those points in the ProcessLogix OPC Server. This includes points
brought in and defined from other interfaces using the Quick Builder
program.
The External OPC Server configuration (database) must be configured to
define exactly what pieces of hardware or blocks you are interested in. Consult
the External OPC Server documentation for setup.
Setup Procedures 1-3
Configure the OPC Server(s)
Installing ProcessLinx
Before ProcessLinx can work properly in runtime, each OPC Server must be
installed and configured correctly. Follow the installation procedure and setup
specified with the documentation for the external OPC Server. A TCP/IP
connection must also exist between the NT ProcessLogix node and any
remote node running an external OPC server for which you wish ProcessLinx
to connect with. Refer to Using DCOM OPC Servers on page 7-1 to setup
and configure remote OPC servers.
Do the following to install the ProcessLinx software:
1. Insert the ProcessLinx CD.
2. Select Start
3. Enter D(CDROM drive letter):setup.exe.
4. Accept the License Agreement.
5. Follow the rest of the dialog boxes to install ProcessLinx in the default
locations.
⇒ Run.
Preparing the Client’s User Accounts
6. To complete the installation, insert the floppy disk with the License
Activation.
7. Follow the instructions for moving the License Activation to the PC.
ProcessLinx installation is complete.
The easiest way to avoid DCOM security problems is to have the same user
account and password on all machines, DCOM security is bypassed. It is
possible however, to allow a remote OPC Client to access the PLX OPC
Server when the correct permissions are specified. This requires user and
group privileges and DCOMCFG settings to be set appropriately. This is not a
trivial undertaking and most people (including network administrators) have
no idea how to do it properly.
Most of the time OPC is set up with user accounts on the Client machine and
Server machine having the same name and password. This is not specific to
ProcessLinx. It is a Microsoft DCOM issue. OPC is written using COM so it
has inherited all the DCOM flaws.
ProcessLinx is not dependent on a specific version of ProcessLogix. It works
the same in R320 as it does in R500. Refer to your Microsoft documentation
on how to add user accounts.
Both the ProcessLogix Client and the Server must have both the MNGR and
Publication 1757-UM002B-EN-P - January 2003
1-4 Setup Procedures
ps_user accounts on them. Refer to the sections in Knowledge Builder, About
ProcessLogix-To-OPC Server/Client Communications, Communicating with 3rd Party
Clients, and Creating a MNGR Account for a Third-Party Client.
IMPORTANT
For example, if the ps_user account is not the client, you must add it by doing
the following:
1. Right click on My Computer.
2. Select Manage
3. Right click on the Users folder.
4. Select New User.
5. Add a PS_USER account.
6. On the General Tab, check Password Never Expires.
7. Click the Member Of Tab and be sure Administrators and Users are
visible.
The PS_USER account is now setup on the client.
The following instructions apply only to Windows 2000
and Windows XP. Windows NT is not supported.
⇒ Local Users and Groups ⇒ Users.
Publication 1757-UM002B-EN-P - January 2003
Running Updates on the ProcessLinx Client’s Registry
Because OPC is COM based, the Client needs the GUID (Globally Unique
IDentifier) of the OPC Server. If the Client and Server reside on the same box,
the registry already contains the Server’s GUID so the Client can easily find it.
If the Server resides on a remote computer, the Client’s registry does not
contain the Server’s GUID.
If you have ProcessLinx installed on a third machine you will need to make
sure you have the GUIDs of both OPC servers located in the ProcessLinx
machine. You will need to follow similar steps as noted below. The following
steps put the Server’s GUID into the Client’s registry.
Setting up communication between the OPC Client and OPC Server
Follow these instructions to setup communications between the OPC Client
and the OPC Server:
1. Select Start
⇒ Run.
2. Type regsvr32 opcproxy.dll in the Run dialog box.
Setup Procedures 1-5
IMPORTANT
Unless opcproxy.dll is in the Windows\System32 directory
the above command will fail because it can't find the
OPCPROXY.DLL. You need to specify the full path the
the DLL (i.e. regsvr32 “C:\Program Files\Common
Files\OPC Foundation\opcproxy.dll”)
3. On the server machine, go to the
C:\Honeywell\Client\Opcserverconnect, folder and copy the
HSCOPCCONNECT.REG & HSCOPCSERV.REG files to a floppy
diskette.
4. On the ProcessLinx Client machine, create a directory called
C:\Honeywell\Client.
5. Copy the hscopcconnect.reg file and the hscopcServ.reg file from the
floppy, to the C:\Honeywell\Client directory of the ProcessLinx Client.
6. Using Notepad, open then edit the hscopcconnect.reg file.
7. Edit line#19 section. Change the entry
from: @=”d:\\hwiac\\programs\\tps\\hci\\hscopcserv.exe
to: @=”c:\honeywell\client\hscopcserv.exe
8. Go into the C:\Honeywell\Client directory on the Client.
9. Run (double-clicking) each of the .REG files in Step 3,
HSCOPCCONNECT.REG & HSCOPCSERV.REG, one at a time.
All registry changes that tell the Client, the Servers GUID have now
been made to the registry.
Publication 1757-UM002B-EN-P - January 2003
1-6 Setup Procedures
Notes:
Publication 1757-UM002B-EN-P - January 2003
Chapter
Getting Started
This section provides the required information to setup and configure both
the ProcessLinx software as well as the communications interface to the
ProcessLogix OPC Server and the external OPC Server.
2
ProcessLinx Version
Configure Mode
The version of the ProcessLinx can be found by selecting the Help menu in
the main window. The version label below displays Version 2 and Build # is 68,
built on January 10, 2003.
Figure 2.1 ProcessLinx Version Label
In configure mode, you can modify the ProcessLinx Options and Settings
from the main window. ProcessLinx does not communicate with OPC Servers
in configure mode.
To change to configure mode from the menu tab, select Mode
Changing from runtime to configure mode will disestablish all OPC tag items
and Groups and stop all communication with the OPC Servers. You can also
click in runtime or press the keys <Shift+F5> to change back to
configure mode.
1 Publication 1757-UM002B-EN-P - January 2003
⇒ Configure.
2-2 Getting Started
Runtime Mode
To change ProcessLinx to runtime select Mode ⇒ Runtime, click
or press <F5>.
While in runtime mode ProcessLinx acts as an OPC Client to both the
ProcessLogix server and the external OPC Server. Initiating runtime mode
establishes all OPC Groups and Items with the specified OPC Server(s). The
opened TagMap configuration (See Figure 2.1) is activated. If an OPC
server(s) connection cannot be established upon startup, an error will be
logged to the Message Log window and the driver will be placed into configure
mode.
Pipe/Group Pane
Message Log Pane
Publication 1757-UM002B-EN-P - January 2003
Tag View Pane
Runtime Status
OPC Status
Total # of OPC Tags
Figure 2.2 ProcessLinx Example Window
Getting Started 2-3
Configure ProcessLinx Options
To configure ProcessLinx Options select from the Utility menu, Utility ⇒
Configure Options or click in the tool bar. You see:
Figure 2.3 Options Dialog Box
Automatically startup in runtime mode when ProcessLinx is started
This option starts ProcessLogix in runtime mode. This change takes
effect the next time you start the program. If unchecked then you must
manually place ProcessLinx in runtime mode. Default is unchecked.
On auto startup into runtime mode, minimize the program window
This option is used to control whether or not the program starts
minimized or not. On startup if the “Automatically startup in runtime
mode…” is checked then the program window will be minimized.
Default is unchecked.
In runtime mode, ping remote hosts first to verify they exist before
attempting a connection to Remote OPC Server (requires TCP/IP)
This option should always be enabled for all remote OPC Server(s)
communicating via TCP/IP. If checked, ProcessLinx pings the remote host
before attempting an OPC connection to it. If this option is not enabled and
Publication 1757-UM002B-EN-P - January 2003
2-4 Getting Started
a remote server connection is lost, ProcessLinx may keep trying to connect
with it, you may have to restart ProcessLinx.
ATTENTION
!
For local OPC servers (running on the same PC as ProcessLinx) this option
is not used. The default is checked. If enabled, you can change the settings
and have them recognized while in runtime operation.
Interface Error Log Directory
Use this option to specify the error log destination directory. If a folder
is specified, all error and information messages displayed in the driver’s
log window are logged. ProcessLinx generates a new log file daily. If this
field is left blank, no error or information logging occurs.
Maximum # of Screen Buffer Lines in On-Screen Message Log
Use this option to specify the maximum lines to display in the Message
Log Pane. If the current number of lines is greater or equal to this the
first 50% of these messages are removed. This only concerns on-screen
messages. The messages logged to the log file are not removed.
This restart situation depends on how you
setup DCOM with the COM interface (OPC
Server). Be certain to follow the DCOM steps
in Chapter 7 for best performance when you
configure TCP/IP and DCOM with COM I/F
to OPC Server.
Publication 1757-UM002B-EN-P - January 2003
This option also minimizes memory usage. The buffer can consume up
to 1 MB of memory otherwise.
Clear On-Screen Messages When Limit is Hit
Use this option to specify when the number of lines displayed in the
Message Log Pane hits the limit defined in the option above. The whole
buffer (all on-screen messages) is cleared. If unchecked then only the
first 50% will be removed.
Retry Wait Period (in milliseconds) for Redundancy / OPC Server Switchover
Use this option to specify the retry wait period before attempting to
connect to an OPC Server that has stopped communicating. This is
used in runtime mode during a switchover. Changes to this setting can
be made, and are recognized during runtime operation.
Getting Started 2-5
Number of Retries for Redundancy / OPC Server Switchover
This option specifies the number of retries attempts to connect to a
redundant OPC Server. Retries are initiated after communication is lost
with a server. For example, if this is set to three and communication is
lost with the primary server, ProcessLinx will switchover to the
secondary server (if defined). Three connection attempts are made to
the secondary server before switching back to the primary. ProcessLinx
then attempts a connection three times with the primary and so on.
Changes to this setting can be made, and are recognized during runtime
operation.
Publication 1757-UM002B-EN-P - January 2003
2-6 Getting Started
Notes:
Publication 1757-UM002B-EN-P - January 2003
Chapter
3
ProcessLinx TagMap Configuration
A ProcessLinx TagMap configuration is created to communicate OPC
items (also known as tags) from one OPC server to another. This
configuration maps each data point exchanged between systems using
the OPC protocol.
The ProcessLinx configuration is a hierarchy of user-defined objects.
The top-level object is a Pipe. A Pipe defines which OPC Servers are
used for data exchange. It also defines the primary and secondary PC (if
available) hosts of the external OPC Server(s). The next level down is
called a Group.
Each Pipe contains Groups. Groups contain TagMap definitions. Each
Group object can contain as many TagMaps as needed, collectively
“Grouping” similar tags together. The Group is conceptually similar to
a file folder. All TagMaps in a Group have the same data update rates,
dead band, time bias and data flow direction for all TagMaps. During
runtime, each defined ProcessLinx Group creates and encapsulates an
OPC-standard Group.
A TagMap defines the source and destination OPC Items for each data
point. Each map specifies the actual OPC Item names, OPC Server
Access paths, data flow/data master, and scaling options. In runtime,
the TagMap object contains an OPC-standard Item object for each
server.
1 Publication 1757-UM002B-EN-P - January 2003
Loading...