The OPC Server Package is a Windows based software application that allows OPC compatible clients
to connect to a Trusted
This document describes the OPC server in its Windows Service form (T8030S). For OPC Server
release 17 and earlier and other executable versions (T8030X), please refer to issue 14 of this
document.
Features
•Industry standard OPC interface
•Supports OPC Data Access v1.0, v2.05a and OPC Alarms & Events v1.1
•Single or Dual-redundant link to a Trusted
•Handles up to 32 Trusted
•Update rate of down to 10ms.
•Events time-stamped to a resolution of 1ms
•Collects sequence of events ( SOE ) and process historian data
•Automatically interfaces to IEC1131 TOOLSET to obtain tag references in Trusted
Controllers
•Online monitoring of tag values
•Reports communications and server status to Clients
M
T
System and access the process data.
TM
System
TM
Controllers
TM
•Operates as a Windows Service regardless of user login (T8030S)
Issue 23 April 10 PD-T8030S 1
TrustedTM OPC T8030S
Issue Record
Issue
Number Date Revised by Technical CheckAuthorised by Modification
1June 00 J Parry G Creech R Cockman
2June 00 J Parry G Creech R Cockman
3June 00 J Parry G Creech R Cockman
4Mar 01 P Barnett G Creech R Cockman To reflect server
release 1.7
5Jan 02 P Barnett G Creech R Cockman
6G Creech R Cockman Remove old logo
7Mar 02 A Murrell G Creech R Cockman
8Mar 02 A Bass G Creech R Cockman Trusted ICS changed
to Trusted
9May 02 P Barnett G Creech R Cockman Drawings reformatted
10 June 02 P Barnett G Creech R Cockman Extended attributes
added
11 Mar 04 D Johnson G Creech R Cockman MR000097-05 + build
13 of OPC server
12 April 04 D Johnson G Creech R Cockman MR000097-09
13 June 04 N Owens G Creech R Cockman formatting
14 Oct 04 J Bourn G Creech R Cockman formatting
15 Oct 05 J W Clark G Creech R Cockman Format
16 Dec 05 N Owens G Creech R Cockman Updated for Windows
Service version
17 Aug 06 N Owens I Vince P Stock Backwards
compatibility
18 Sep 06 N Owens I Vince P Stock Start/Stop commands,
Registry
19 Dec 06 N Owens I Vince P Stock Service/exe
differentiation
20 Mar 07 N Owens I Vince P Stock Corrections
21 Sep 07 N Owens I Vince P Stock Throughput specs
22 Feb 10 S Blackett N Owens P Stock New features Multiple
subscriptions; OPC
Server status
23 April 10 S Blackett N Owens P Stock Features minor change
Table 2 PC IP Address Allocation...........................................................................................................35
Table 3 TrustedTM Controller IP Address Allocation ...............................................................................35
Issue 23 April 10 PD-T8030S 8
TrustedTM OPC T8030S
Notice
The content of this document is confidential to ICS Triplex Technology Ltd. companies and their
partners. It may not be given away, lent, resold, hired out or made available to a third party for any
purpose without the written consent of ICS Triplex Technology Ltd.
his document contains proprietary information that is protected by copyright. All rights are reserved.
T
Microsoft, Windows, Windows 95, Windows NT, Windows 2000, and Windows XP are registered
trademarks of Microsoft Corporation.
The information contained in this document is subject to change without notice. The reader should, in
all cases, consult ICS Triplex Technology Ltd. to determine whether any such changes have been
made. From time to time, amendments to this document will be made as necessary and will be
distributed by ICS Triplex Technology Ltd.
Information in this documentation set may be subject to change without notice and does not represent
a commitment on the part of ICS Triplex Technology Ltd..
The contents of this document, which may also include the loan of software tools, are subject to the
confidentiality and other clause(s) within the Integrator Agreement and Software License Agreement.
No part of this documentation may be reproduced or transmitted in any form or by any means,
electronic or mechanical, including photocopying and recording, for any purpose, without the express
written permission of ICS Triplex Technology Ltd.
Disclaimer
The illustrations, figures, charts, and layout examples in this manual are intended solely to illustrate the
text of this manual.
The user of, and those responsible for applying this equipment, must satisfy themselves as to the
acceptability of each application and use of this equipment.
This document is based on information available at the time of its publication. While efforts have been
made to be accurate, the information contained herein does not purport to cover all details or variations
in hardware or software, nor to provide for every possible contingency in connection with installation,
operation, or maintenance. Features may be described herein which are present in all hardware or
software systems. ICS Triplex Technology Ltd. assumes no obligation of notice to holders of this
document with respect to changes subsequently made.
ICS Triplex Technology Ltd. makes no representation or warranty, expressed, implied, or statutory with
respect to, and assumes no responsibility for the accuracy, completeness, sufficiency, or usefulness of
the information contained herein. No warranties of merchantability or fitness for purpose shall apply.
Issue 23 April 10 PD-T8030S 9
TrustedTM OPC T8030S
Revision and Updating Policy
All new and revised information pertinent to this document shall be issued by ICS Triplex Technology
Ltd. and shall be incorporated into this document in accordance with the enclosed instructions. The
change is to be recorded on the Amendment Record of this document.
Precautionary Information
WARNING
Warning notices call attention to the use of materials, processes, methods, procedures or limits which
must be followed precisely to avoid personal injury or death.
CAUTION
Caution notices call attention to methods and procedures which must be followed to avoid damage to
the equipment.
Notes:
Notes highlight procedures and contain information to assist the user in the understanding of the
information contained in this document
Warning
RADIO FREQUENCY INTERFERENCE
Most electronic equipment is influenced by Radio Frequency Interference (RFI). Caution should be
exercised with regard to the use of portable communications equipment around such equipment.
Signs should be posted in the vicinity of the equipment cautioning against the use of portable
communications equipment.
MAINTENANCE
Maintenance must be performed only by qualified personnel, otherwise personal injury or death, or
damage to the system may be caused.
Associated Documents
Product descriptions provide product specific information.
The Safety Manual contains the recommended safety requirements for the safety system design.
The 1131 Toolset – Users’ Guide provides programming reference.
PD8082B – Toolset Suite, provides specific guidance on system configuration and application
generation.
PD8151B – Communications interface, provides specific guidance on communications configuration.
The Operator and Maintenance Manual contains general guidelines on maintenance and diagnostic
procedures.
Issue 23 April 10 PD-T8030S 10
TrustedTM OPC T8030S
1. Description
1.1. Overview
OPC (OLE for Process Control ) is an industry standard for transferring process and event data
between a server and one or more client applications.
TM
The OPC Server provides an OPC link between a Trusted
Using Ethernet Interface cards within the server’s host PC, it connects to one or more Trusted
Controllers. OPC client applications can connect to the server using Microsoft COM ( or DCOM over a
network ). Each client can browse the server to view the available tag references. Using these
references, the clients can then arrange for groups of tags to be synchronously updated at defined
intervals. Values may also be written asynchronously to the server.
Figure 1 shows how the OPC Server fits between the Trusted
OPC client applications.
System and one or more OPC clients.
TM
System hardware and one or more
TM
Figure 1 Communication Path for TrustedTM OPC
Issue 23 April 10 PD-T8030S 11
TrustedTM OPC T8030S
1.2. TrustedTM OPC Architecture
The server can be divided into four main functions: The Browse Interface, the OPC Data Access
Interface, the OPC Alarms & Event Interface and the Communications Interface.
1.2.1. The Browse Interface
The server provides a list of tag references that OPC clients can browse in a standard manner. The
root node is the Trusted
as sub-items. Selecting a controller in the tree will show a list of its tags in a window to the right.
Figure 2 shows an example browse tree structure. If Controller # 1 is selected, and then a tag on the
right is selected, the path would be:
M
T
Ethernet Interface. All controllers defined from ‘Edit/Controllers’ are shown
TrustedTM Ethernet IF
Controller # 1
Controller # 2
Figure 2 Example Browse Tree Structure
TrustedEthernetIF.Controller1.<Tag>
Where <Tag> may be a controller level tag or a further hierarchical path to a data point.
1.2.2. OPC Data Access Interface
When an OPC Data Access client attaches to the server, a unique server object is created within the
main server application. The client can create and edit groups within this server object. Each group
has a number of tag references and an update rate. Every time the tags are to be updated, the server
will inform the client of the new values, quality, time, etc.
See the specific OPC Data Access client documentation for further information.
1.2.3. OPC Alarm & Event Interface
When an OPC Alarm & Event client attaches to the server, a unique server object is created within the
main server application. Each time an event occurs, the server informs the client of the event. Event
information includes the tag name, value, time the event occurred, etc.
See the specific OPC Alarm & Event client documentation for further information.
Issue 23 April 10 PD-T8030S 12
TrustedTM OPC T8030S
1.2.4. OPC Data Access vs. OPC Alarm & Event
OPC Data Access and OPC Alarm Event clients are based on separate OPC standards. While some
OPC clients support both standards within the same package, most OPC clients will support one or the
other. OPC Data Access clients are the most common, and are used by many MMI (Man Machine
Interface) packages to monitor specific process variables originating from a Trusted
TM
system. OPC
Alarm & Event clients are used primarily in “Event Historian” or “Event Log” type applications.
OPC Data Access clients query the server by tag name. They can query the value of a specific tag,
create groups of tags which will be updated at regular intervals, subscribe to a tag to receive updates
when that tag’s value changes, or change the value of the tag in the Trusted
TM
controller. The server
allows Data Access clients to access any Controller tag that either has a communications address or is
configured for Sequence of Event or Process Historian updates.
OPC Alarm & Event clients query the server by controller name. Instead of being able to query by tag
name, the Alarm & Event clients receive all events originating from subscribed controllers. The server
will generate events only for tags defined by a Controller that are configured for Sequence of Event
updates.
1.2.5. Communications Interface
The server manages all OPC client queries, updates, polling groups, and subscriptions. The server
translates these requests into a combination of both polled and event updates, which are sent to the
appropriate Trusted
know about or need to understand the specific communication details between the server and the
Controllers.
TM
controller. As is the intention of the OPC standards, the OPC clients do not
Issue 23 April 10 PD-T8030S 13
TrustedTM OPC T8030S
2. Installation and Configuration
2.1. ‘Log on as a Service’ privilege
The server runs as a Windows service. This means that it has no application window, it does not
appear on the taskbar and it cannot be started using an icon. However, it is able to run even when no
users have logged in and can automatically start on boot up without needing a user to log in.
Before installing the OPC Server, a user may be given privilege to start an application as a service.
Choose a user with Administrator privileges. If the service is to start in the local system account, then a
separate privileged user is not required.
Versions of the OPC Server before 102 operate as executable programs within the user login, and do
not need a service privilege. Starting and stopping these versions requires the program to be stopped
and restarted. The configuration functions described here are available from the server program itself.
2.1.1. Windows 2000 and XP
Click Start | (and Settings on 2000) Control Panel | Administrative Tools | Local Security Policy.
In XP, ‘Administrative Tools’ may also appear on the Start menu, or may have been disabled. To
enable this, right click on ‘Start’ and select Properties. In the ‘Start Menu’ tab, click Customize. In
the Advanced tab, scroll down the ‘Start menu items’ to the bottom and select to display ‘System Administrative Tools’.
If the Control Panel is arranged in categories, in the Control Panel ‘Pick a category’ view, select ‘Performance and Maintenance’ and then Administrative Tools. Select ‘Local Security Policy’.
In ‘Local Security Settings’, select ‘Local Policies’. Select ‘User Rights Assignment’. Double-click
on ‘Log on as a service’. The Properties window shows the users that are allowed to start a service.
If the chosen user does not appear in the list, add the user by clicking ‘Add’ (2000) or ‘Add user or group’ (XP). In XP, clicking ‘Advanced’ and ‘Find Now’ displays all available users.
Issue 23 April 10 PD-T8030S 14
TrustedTM OPC T8030S
2.2. Installing the OPC Server
M
The Trusted
is accomplished by running the setup program on the installation CD, which will run automatically if
Autoplay is enabled.
In addition to the OPC Server, the setup program will install a number of files required for OPC. The
setup program also updates the registry to allow OPC clients to browse for and connect to the server.
Windows versions NT, 2000 and XP require administrator privileges in order to complete the
installation. Windows NT installations require Service Pack 4 or higher. Basic configuration consists of
telling the OPC Server which Controller to connect to, where to find its symbol database, and how fast
to poll the controller for updates.
The installation program offers the option of a full installation, which includes the OPC Server, and
‘Remote Configuration Program Only’, which only provides the configuration tool and not the OPC
Server.
The installation program allows a specific username to be used to run the service. If the service is to
run under the local system account, there is no need to enter a user and password. If a specific user is
required and was given the privilege in section 2.1, enter the username and password.
The installation will ask for the serial number supplied with the package on a label, as shown in Figure
3. Enter the serial number and attach the label to the PC on which the OPC Server is installed.
T
OPC Server must be installed and configured before OPC clients can use it. Installation
Figure 3 Serial Number Entry
Issue 23 April 10 PD-T8030S 15
Loading...
+ 34 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.