HWIOPC Server

User Manual
Doc. No.:51-52-25-141 Revision: Date: 1 7/05

Industrial Measurement and Control

Notices and Trademarks

Copyright 2005 by Honeywell Revision 1 July 2005 WARRANTY/REMEDY
Honeywell warrants goods of its manufacture as being free of defective materials and faulty workmanship. Contact your local sales office for warranty information. If warranted goods are returned to Honeywell during the period of coverage, Honeywell will repair or replace without charge those items it finds defective. The foregoing is Buyer's sole remedy and is in lieu of all other warranties, expressed or implied, including those of merchantability and fitness for a particular purpose. Specifications may change without notice. The information we supply is believed to be accurate and reliable as of this printing. However, we assume no responsibility for its use. While we provide application assistance personally, through our literature and the Honeywell web site, it is up to the customer to determine the suitability of the product in the application.

Industrial Measurement and Control Honeywell 1100 Virginia Drive Fort Washington, PA 19034

HC900 Hybrid Controller is a trademark of Honeywell OPC is a trademark of the OPC Foundation Other brand or product names are trademarks of their respective owners.

ii

HWIOPC Server User Manual

Revision 1 7/05

License Agreement
Read this agreement before opening the software. Once you have removed the software from its envelope, you have accepted the agreement. USAGE RIGHTS Your rights, with respect to the Software, are non-exclusive. The software may only be used by one user, on one computer at a time. The software may be transferred to another computer, as long as it is only used by one user at a time. The Software and its documentation may not be copied or distributed to others. You may not create, modify, alter, adapt, merge, de-compile or reverse-engineer the Software, and you may not remove or obscure Honeywell or other included copyright or trademark notices. TERM OF LICENSE This agreement is effective unit terminated. Terminate the Agreement by destroying the Software, documentation and all backup copies. BACKUP COPIES You may make backup copies of the Software. The copyright notice(s) must be included on each backup copy. COPYRIGHTS The Software accompanying this manual is protected by United States copyright law. The Software documentation is copyrighted. You may only copy the Software and the Software documentation for backup or to load the Software onto your computer as part of program execution. TITLE TO SOFTWARE AND CONFIDENTIALITY The Software and all copies thereof are proprietary to Honeywell and title thereto remains in Honeywell. All applicable rights to patents, copyrights, trademarks and trade secrets in the Software are and shall remain in Honeywell. You may not sell, transfer, publish, or otherwise make available any software copies thereof to others. You acknowledge that the Software is a trade secret of Honeywell. You agree to secure and protect each program, software product and copies thereof in a manner consistent with the maintenance of Honeywell's rights therein and to take appropriate action by instruction or agreement within your organization to satisfy your obligations hereunder. Violation of these provisions shall be a basis for immediate termination of this license. Termination of the license shall be in addition to and not in lieu of any other legal or equitable remedies available in Honeywell.

Revision 1 7/05

HWIOPC Server User Manual

iii

About This Document

Abstract The HWIOPC Server (Honeywell Industrial OPC Server) provides a means for interfacing data from Honeywell HC900 controllers (redundant and non-redundant) to client applications on local or remote computers using the OPC protocol. The HWIOPC suite consists of an OPC Server, the core component, and other applications that are used to configure, monitor, diagnose, log, and verify the operation of the OPC Server. The software operates on Windows XP Professional and Windows 2000 Professional PCs. References The following list identifies all documents that may be sources of reference for material discussed in this publication.
Document Title HC900 Controller Installation and User Guide HC Designer User Guide Doc ID 51-52-25-107 51-52-25-110

Contacts World Wide Web The following lists Honeywells World Wide Web sites that will be of interest to our customers.
Honeywell Organization Corporate Industrial Measurement and Control WWW Address (URL) http://www.honeywell.com http://www.honeywell.com/imc

Telephone Contact us by telephone at the numbers listed below.

Organization United States and Canada Honeywell Phone Number 1-800-423-9883 1-888-423-9883 1-800-525-7439 Tech. Support Q&A Faxback (TACFACS) Service

iv

HWIOPC Server User Manual

Revision 1 7/05

Table of Contents
Table of Contents ...........................................................................................................................v 1 Preface .................................................................................................................................... 1

1.1 1.2 1.3

2 3

INTENDED AUDIENCE ........................................................................................................ 1 PRODUCT SUPPORT ........................................................................................................... 1 PC REQUIREMENTS ........................................................................................................... 1 OVERVIEW ........................................................................................................................ 2 WORKING DIRECTORY ...................................................................................................... 4 CONFIGURATION FILES ..................................................................................................... 4 INSTALLATION PROCEDURE .............................................................................................. 5 MODIFY/REPAIR/UNINSTALL .......................................................................................... 12 CHECK WHETHER HWIOPC SERVER IS REGISTERED ..................................................... 14 NEW LICENSE REGISTRATION ......................................................................................... 14 TRANSFER LICENSE FROM ONE MACHINE TO ANOTHER ................................................ 16 PREREQUISITES ............................................................................................................... 19 CONSIDERATIONS ............................................................................................................ 19 CONFIGURING OPC DATABASE (ADDRESS SPACE) USING OPC UTILITY ...................... 19

Introduction ............................................................................................................................ 2

2.1 3.1 3.2

4

Working directory and Configuration files .......................................................................... 4

Installation .............................................................................................................................. 5

4.1 4.2
5

HWIOPC Register ................................................................................................................. 13

5.1 5.2 5.3

6

Quick Start ............................................................................................................................ 19

6.1 6.2 6.3

6.3.1 Running the OPC Utility ........................................................................................... 20 6.3.2 Starting the the OPC Server .................................................................................... 20 6.3.3 Uploading the existing configuration........................................................................ 21 6.3.4 Adding a Device Group............................................................................................ 21 6.3.5 Adding a Device....................................................................................................... 22 6.3.5.1 Device general page......................................................................................... 23 6.3.5.2 Controller Type page ........................................................................................ 24 6.3.5.3 Connection page............................................................................................... 24 6.3.5.4 Communication page........................................................................................ 25 6.3.5.5 Tag page........................................................................................................... 25 6.3.6 Adding Tag Groups and Tags.................................................................................. 27 6.3.6.1 Importing Tags from HC900 ............................................................................. 28 6.3.6.2 Generating tag groups and tags automatically................................................. 31 6.3.6.3 Adding tag groups and tags manually .............................................................. 32

6.4

USING THE TEST OPC CLIENT ........................................................................................ 37

Running Test OPC Client ........................................................................................ 37 Browsing the address space of the Server and adding items ................................. 38 Writing Values.......................................................................................................... 40 Saving Test Client File ............................................................................................. 40 Monitor Device Tag.................................................................................................. 41 Monitor Client Item................................................................................................... 41

6.4.1 6.4.2 6.4.3 6.4.4

6.5 6.6 6.7 6.8 6.9

MONITORING ................................................................................................................... 40 USING TAG EXPORT FILE ................................................................................................ 43 COPY/PASTE OPC TAG NAME ......................................................................................... 43 QUERYING OPC CLIENTS................................................................................................ 44 TROUBLESHOOTING ........................................................................................................ 45
Using System Tags.................................................................................................. 45
HWIOPC Server User Manual v

6.5.1 6.5.2

6.9.1
Revision 1 7/05

6.9.1.1 System tags ...................................................................................................... 45 6.9.1.2 Browsing system tags....................................................................................... 45 6.9.2 Using Diagnosis ....................................................................................................... 46 6.9.2.1 Diagnostics Record........................................................................................... 46 6.9.2.2 Diagnosis Result Types .................................................................................... 47 6.9.2.3 Start/Stop Diagnosis......................................................................................... 47 6.9.2.4 Save Diagnostics Record ................................................................................. 47 6.9.2.5 Clear Diagnostics Record................................................................................. 47 HWIOPC DCOM Configuration............................................................................................ 48

7.1 7.2

OVERVIEW ...................................................................................................................... 48 WIN2000 SP4 .................................................................................................................. 48

7.2.1 General Security Configuration................................................................................ 48 7.2.1.1 Automatic DCOM configuration ........................................................................ 48 7.2.1.2 Manual DCOM configuration ............................................................................ 50 7.2.2 Special Security Configuration................................................................................. 53 7.2.2.1 Default account................................................................................................. 53 7.2.2.2 Special accounts............................................................................................... 54

7.3

WINXP SP2..................................................................................................................... 55

8 9

7.3.1 Local Security Policy Setting ................................................................................... 55 7.3.2 Internal Firewall Configuration ................................................................................. 56 7.3.3 My computer Properties........................................................................................... 59 7.3.3.1 Run DCOMCNFG ............................................................................................. 59 7.3.3.2 DCOM Default Properties................................................................................. 60 7.3.3.3 Common DCOM Security ................................................................................. 61 7.3.4 HWIOPC DCOM Properties..................................................................................... 63 7.3.4.1 Automatically configure HWIOPC DCOM Properties ....................................... 63 7.3.4.2 Manually configure HWIOPC DCOM Properties .............................................. 65 7.3.5 Special Security Configuration................................................................................. 69 7.3.5.1 Default account................................................................................................. 69 7.3.5.2 Special account ................................................................................................ 69 Other Information................................................................................................................. 70 Definition List ....................................................................................................................... 71

vi

HWIOPC Server User Manual

Revision 1 7/05

Preface Intended Audience

1 Preface
The HWIOPC suite provides a means for interfacing data from Honeywell HC900 controllers (redundant and non-redundant) to client applications on local or remote computers using the OPC protocol. The suite consists of an OPC Server, the core component, and other applications that are used to configure, monitor, diagnose, log, and verify the operation of the OPC Server. The OPC server provides tag import capability from the HC900 configuration using .csv report files exported via HC Designer, version 3.0. This results in quick development of the OPC server database. HWIOPC allows the OPC Client to either browse the OPC server database (address space) for desired OPC tags or copy/paste the OPC tags into the OPC Client database if browsing capability is not available in the client.

1.1 Intended Audience

The manual is produced for the OPC Configuration Administrator who intends to configure the devices and tags of the OPC Server and the OPC Client User who intends to implement and test the OPC Server.

1.2 Product Support

The following products are supported: HC900 C30, C50 single Ethernet connection HC900 C70R single or redundant Ethernet connection

1.3 PC Requirements
PC: Pentium III, 1GHz, 256MB RAM (minimum) Pentium 4, 2GHz, 512MB RAM (recommended) Operating System Support: Windows 2000 Professional, Service Pack 4 Windows XP Professional, Service Pack 2

Revision 1 7/05

HWIOPC Server User Manual

Introduction Overview

2 Introduction
2.1 Overview
The HWIOPC suite includes the following components: 1. OPC Server This component consists of the parts listed below, 1). HWIOPC Server - an OPC Server running as a background service that supports HC 900 controller systems, including C70R, C30 and C50. This OPC Server follows OPC DA v2.05A protocol and is also compatible with OPC DA v1.0A protocol. 2). OPCServer Monitor- an application that is used to start/stop the service above and monitor the service state. It starts automatically after the installation is finished or the computer is started, and appears as a clock image in the taskbar. 3). OPC Utility - an OPC utility that is used to: import tags that are exported by HC Designer to the address space of the OPC Server configure the address space of the OPC Server manually configure the server using DTG (Digital Tag Generation) for certain tag groups query the information of the OPC clients connected with the OPC Server, monitor the internal value of device tags and the real time value of OPC client items, and diagnose events occurring in the OPC Server. export the OPC server tag database as a .csv report file. 4). HTSL Product Register - a tool used to register the OPC Server. 2. OPC Client The component contains two OPC Clients: OPC Client (VC) and OPC Client (VB). The OPC Client (VC) connects with the OPC Server through a custom interface, and the OPC Client (VB) connects with the OPC Server through an automation interface. They are designed to test the two interfaces of the OPC Server and verify the address space configuration of the OPC Server, display syntax structures, data types along with live data values and allow write operations to assist in setting up other PC applications. 3. HC900R Driver A library that provides connectivity to both redundant and non-redundant HC 900 systems that are MODBUS/TCP slaves on an Ethernet network. 4. HTSLLogger The component contains the following: 1). HTSLLogger - a background service implemented as a COM Server and used to store the log of the OPC Server and Device Driver to disk files under the directory C:\HTSLLogger\.

HWIOPC Server User Manual

Revision 1 7/05

Introduction Overview 2). HTSLLogViewer - a tool that is used to display and classify log messages in the log files recorded by the HWIOPC Server and the device driver.

Revision 1 7/05

HWIOPC Server User Manual

Working directory and Configuration files

3 Working directory and Configuration files

3.1 Working directory
The default working directory of HWIOPC is C:\Program Files\HTSL. In this directory, there are 6 folders. See the table below, Relative Directory Description \HTSL\ HWIOPC work directory, such as C:\program files\HTSL\ \HTSL\server\ Including HWIOPCServer, OPCServerMonitor, OPCUtility \HTSL\drv\ Including all device drivers \HTSL\client\ Including OPC Client_VC, OPC Client_VB \HTSL\data\ Including all configuration files (XML and CSV files) \HTSL\logger\ Including HTSLLogger, HTSLLogView \HTSL\out\ Including temporary files You cannot change these directories otherwise unexpected results will occur.

3.2 Configuration Files

The OPC Server uses one device driver configuration file to save the device driver and device groups information. It provides two configuration files for each device. The first is the Device Configuration File in XML format, and the other a Points Configuration File in CSV format. All configuration files are stored under the relative directory \HTSL\data\, such as c:\Program Files\HTSL\.

Device Driver Configuration File It contains the parameters for DLL ProgID and driver name.
The file name is DevicesConfig.xml.

Device Configuration File

It contains the parameters for physical connection. For example, the file for the Ethernet port communication consists of the following:

IP Address, Port, Redundant IP Address.

The default file name is MBTCPCHN1Config.xml. You cannot change its name and contents manually, but can change the name and contents through the OPC utility tools.

Points Configuration File

It includes the detailed information of all the points related to this device. For example, the file for a device supporting the Modbus protocol consists of the following:

Point Name, Access Right, Data Type, Data Table (i.e. Register Type), Address, Description .
The file default name is MBTCPPoints.csv. You cannot change its name and contents manually, but can change the name and contents through OPC Utility.

HWIOPC Server User Manual

Revision 1 7/05

Installation

4 Installation
4.1 Installation Procedure
Note: If the HWIOPC suite has been installed in your computer and has not been uninstalled, make sure two services named HTSLLogger and HWIOPC are stopped before starting the following installation steps. The HWIOPC CD will start the installation guide automatically after being inserted to CD-ROM, but if not, double click on the install program named Setup.exe. The installation guide will appear.

Revision 1 7/05

HWIOPC Server User Manual

Installation

After few seconds, the above window will be replaced by the welcome dialog box shown below, click Next.

The license dialog box shown below will appear. Click Yes if you accept all the terms of the preceding License Agreement.

HWIOPC Server User Manual

Revision 1 7/05

Installation

The following dialog box will appear. Please choose the destination location, i.e. the working folder of HWIOPC described in Section 3, then click Next.

The dialog box shown below will appear. Click Next after choosing the components you want to install.

Revision 1 7/05

HWIOPC Server User Manual

Installation

There are five components in this package: OPC Server: Files of OPC Server, OPC Utility, OPC Server Monitor, HTSL Product Register. OPC Client: Files of OPC Client. OPC Custom Common Dll: Common Dll files for OPC DA Custom interfaces. If no OPC relevant software has been installed on your computer, you must select this component. If you are not sure, we recommend that you also select it. HC900R Driver: Files of Device driver for redundant and non-redundant HC 900 controller systems. HTSLLogger: Files of HTSLLogger. Please refer to Section 2 for more details. The dialog box shown below will appear. You may change the folder name in this dialog box. Click Next.

After you select the destination location, choose the components and give the program a folder name. The following dialog box displaying your settings will appear. Click Next to begin copying files. Click Back if you want to change the settings.

HWIOPC Server User Manual

Revision 1 7/05

Installation

The following window shows the progress of the installation.

During the installation, the following type of message boxes may appear. A Locked File causes it, i.e., some file you want to install or uninstall is locked by another program. Usually, these files are OPC Common files or system files. If you really want to install or uninstall the file, you must exit the relevant programs and then click Retry. If you dont want to replace the file or remove the file, you can check the box Dont display this message again and then click Ignore.

Revision 1 7/05

HWIOPC Server User Manual

Installation

After installing the components, if you dont install the component OPC Server, please go to Step 11. If you want to install the component OPC Server, the following message box will appear and indicate that the HWIOPC suite has been installed successfully. Click the button OK in the message box shown below and continue to configure DCOM permissions for the OPC Server that communicates with an OPC Client application running on different computers via DCOM.

The window shown below will appear. As displayed in the window, you can first automatically set DCOM permissions through the window and then manually adjust the configuration using DCOMCNFG.exe. You can also totally configure DCOM permissions manually by using DCOMCNFG.exe. Click the button Next. If the check box Set DCOM permissions automatically is checked, the installation will add the EVERYONE, INTERACTIVE and SYSTEM groups to both the launch permissions and the access permissions. Go to next step. If the check box is not checked, the install will do nothing and go to directly to the next step. Click the button Cancel if you dont want to automatically set DCOM permissions.

10

HWIOPC Server User Manual

Revision 1 7/05

Installation

The window shown below will appear. Click the button Finish. The installation is completed successfully.

Open Services in Control Panel. Start the service named OpcEnum, and change the startup type of the service to be Automatic. After the above steps, the HWIOPC has been installed on your computer successfully. If the component OPC Server is selected and installed, refer to Section 5 HWIOPC Register to register the OPC Server. Then, execute the next step, i.e. Step 13. Otherwise, if you dont install the OPC Server, go directly to the next step. You can launch the OPC Utility to configure, monitor and diagnose the HWIOPC Server if it is selected during the Step 5.

To learn how to use the OPC Utility, refer to its online help by pressing F1 or clicking the menu Help->Contents on the main window of the OPC Utility.

Revision 1 7/05

HWIOPC Server User Manual

11

Installation

4.2 Modify/Repair/Uninstall
Note: Before modifying/repairing/uninstalling the HWIOPC suite, make sure that OPCServerMonitor has been stopped and exited. During the removal of the HWIOPC suite, two types of message boxes may appear, A Locked File causes the first. It was explained in Step 8 of Section 4.1. A ReadOnly file causes the other. In this case, confirm that the action related to the file name displayed in the message box below is not an issue, and then click Yes to continue. We do not recommend that you check the option Dont display this message again, because once it is checked, all ReadOnly files installed by the HWIOPC will be removed, even though some of them are common Dll files that are necessary to run programs relative to the OPC protocol or developed with VC++.

12

HWIOPC Server User Manual

Revision 1 7/05

HWIOPC Register

5 HWIOPC Register
To use the HWIOPC Server, you need to apply for license and register a license certificate per the license process first. The service HWIOPC will stop automatically after running for 4 hours as a demonstration version if its license is not registered. The service will need to be re-started after the 4-hr timeout. The HWIOPC License cannot be reused on multiple computers because each computer has its unique license. But the license can be transferred from one machine to another when you have registered a license certificate for a particular machine and want the certificate to be moved to another machine due to some circumstances. The HWIOPC Server has two model types, Non-Redundant and Redundant. If the HWIOPC Server is registered as Non-Redundant, then the HWIOPC Server can only support HC900 C30 and C50 controllers and cannot support HC900 C70R controllers. If the HWIOPC Server is registered as Redundant, then the HWOPC Server can support HC900 C30, C50 and C70R controllers. That is to say, if you purchase the HWIOPC Server - Redundant version, you will actually get both Non-Redundant and Redundant features. If you purchase the HWIOPC Server Non-Redundant version, you will only get the Non-Redundant feature. The section details the step-by-step approach regarding how to check if the HWIOPC Server is registered and what is the current feature, how to execute a new license registration after purchasing the HWIOPC Server and how to transfer a license from one machine to another. The tool named HTSL Product Register is used for all of the license processes. You can launch the tool by clicking Start->HWIOPC->HWIOPC Register, the main window of the tool will appear as shown below,

Revision 1 7/05

HWIOPC Server User Manual

13

HWIOPC Register

5.1 Check whether HWIOPC Server is registered

Do the following to check whether HWIOPC Server is registered, 1. Launch the tool HTSL Product Register. 2. Click the GetLicenseInfo button on the tool. If the HWIOPC Server has been registered, the edit box of License Type will display Permanent. The edit box of Features will display Non-Redundant if you have purchased the Non-Redundant option or display Redundant if you have purchased the Redundant option. The edit box for the Reference Code File will display <Windows Directory>\<Your Voucher Number> XXXX.cert. Otherwise, if the HWIOPC Server has not been registered, then a message box will show as below,

In this case, the HWIOPC Server will stop after running for 4 hours. If you have purchased a version of the software, you will need to register the OPC Server for continuous use. Refer to New License Registration.

5.2 New License Registration

You need to apply for a new license after you purchase the HWIOPC Server software. You will get a license certificate that can be installed on your PC, and then the HWIOPC Server will run as a registered version. The flow diagram below shows the process of registering a new license for the HWIOPC Server.

14

HWIOPC Server User Manual

Revision 1 7/05

HWIOPC Register

Steps to register HWIOPC Server after installing the HWIOPC Server: 1. Launch the tool HTSL Product Register. 2. Input the Voucher Number in the respective entry area provided by the tool. 3. Click the Generate button on the tool. The edit box behind the button will then display the full path name of the generated HostID file. The file name will be <Your Voucher Number>.hid. For example, if the HWIOPC Server is installed in the directory C:\Program Files\HTSL\, then the full path name for the HostID file generated will be C:\Program Files\HTSL\Server\<Your Voucher Number>.hid. Then close the tool. 4. Send the Voucher Number and the generated HostID file to the email address [email protected] to apply for a new license. The email subject should be New License Application. The body of email should just have the Voucher ID and a copy of the Host ID file. 5. After one working day, you will receive a license certificate file from the above email address. The license certificate file name should be <Your Voucher Number> Node 0 .cert. Save the license certificate file to a local folder, such as d:\HC900 License\. 6. Launch the tool HTSL Product Register again. 7. Click the Browse button, an open file dialog will appear. Select the license certificate file you received, such as d:\HC900 License\<Your Voucher Number> Node 0.cert. Then click the Install button; the HWIOPC Server will be registered per the license certificate file.
Revision 1 7/05 HWIOPC Server User Manual 15

HWIOPC Register

You can check whether the HWIOPC Server has been registered successfully with your selected feature via Check whether HWIOPC Server is registered.

Note:
Do not change the generated HostID file name and received license certificate file name. Otherwise, you will fail to register the HWIOPC Server.

5.3 Transfer License from One Machine to Another

Transfer of license certificate happens when you have registered a license for a particular machine and want the certificate to be moved to another machine due to some circumstances. In such a scenario you can request for termination of the license on the former machine and request a license on the new machine. When the license certificate is terminated on a machine, it generates a termination file that contains sufficient information to validate whether the certificate is genuine or not. If the certificate is genuine, [email protected] will issue a new certificate for another machine by obtaining details about the new machine.

Note:
One Voucher Number allows the license to be transferred a maximum of five times. If HWIOPC Server is running when you execute termination, HWIOPC Server in the installed system can still run for five days with the available feature after termination, and then it will stop automatically and turn into a demo version. Otherwise, if the HWIOPC Server is stopped when you execute termination, then HWIOPC Server will turn into demo version after it is started again. So, if you want to keep HWIOPC Server running as a registered version for five days after termination, do remember to start HWIOPC Server first before termination.

The flow diagram below shows the process of transferring a license for the HWIOPC Server.

16

HWIOPC Server User Manual

Revision 1 7/05

HWIOPC Register

Steps to transfer the HWIOPC Server from one machine to another: 1. Launch the tool HTSL Product Register on the machine where you have registered the HWIOPC Server. 2. Input the Voucher Number on the tool. 3. Click the Terminate button on the tool. The edit box behind the button will display the full path name of the generated termination file. The file name will be <Your Voucher Number>(-X, >=2nd transfer time) Node 0.term. For example, the HWIOPC Server will be installed in the directory C:\Program Files\HTSL\ by default. If it is the first time that you are transferring the license, then the full path name of the termination file will be C:\Program Files\HTSL\Server\<Your Voucher Number> Node 0.term. If it is the second time that you transfer the license, then the full path name of the termination file will be C:\Program Files\HTSL\Server\<Your Voucher Number>-0 Node 0.term.Then close the tool. 4. Install HWIOPC Server on the new machine to which you wish to transfer the HWIOPC Server. 5. Launch the tool HTSL Product Register on the new machine. 6. Input the Voucher Number on the tool and click the Generate button. The edit box behind the button will then display the full path name of the generated HostID file for the new machine. Close the tool.

Revision 1 7/05

HWIOPC Server User Manual

17

HWIOPC Register

7. Send the Voucher Number, the termination file generated in step 3, and the HostID file generated in the last step to the email address [email protected] to apply for a license on the new machine. The email subject should be Transfer License Application amd Voucher Number and the 2 files in the body of the email. 8. After one working day, you will receive a license certificate file from the above email address. The license certificate file name should be <Your Voucher Number>-X Node 0.cert. Save the license certificate file to a local folder on the new machine, such as d:\HC900 License Transfer\. 9. Launch the tool HTSL Product Register again on the new machine. 10. Click the Browse button, an open file dialog will appear. Select the license certificate file you received, such as d:\HC900 License Transfer\<Your Voucher Number>-0 Node 0.cert. Then click the Install button; the HWIOPC Server will be registered with the feature in the license certificate file on the new machine. You can check whether the HWIOPC Server has been registered successfully with your selected feature on the new machine via Check whether HWIOPC Server is registered.

Note:
Do not change the generated termination file name, the generated HostID file name and the received license certificate file name. Otherwise, you will fail to transfer the HWIOPC Server from one machine to another.

18

HWIOPC Server User Manual

Revision 1 7/05

Quick Start

6 Quick Start
6.1 Prerequisites
You have installed the software on the server PC running Windows 2000 or XP Professional. You will be interfacing to HC900 (C30, C50, or C70 R) controller systems via Ethernet. If you want to use the OPC Client running on a remote machine to connect with the HWIOPC Server, you should have correctly set the DCOM permissions. Refer to HWIOPC DCOM Configuration for how to configure DCOM permissions for the HWIOPC Server.

6.2 Considerations
You may use the HWIOPC Server for setup/test purposes but it will be subject to a 4 hr. timeout if not registered. After the timeout, the HWIOPC Server will shut down automatically, and so that other tools, such as the OPC Utility and the OPC Test Client, cannot connect with it and function properly. If you want to continue to use the HWIOPC Server after 4 hrs, you need to restart the service HWIOPC, and then the HWIOPC Server will run for an additional 4 hrs. You must register the software on your PC for continuous server interface to OPC clients.

6.3 Configuring OPC Database (Address Space) Using OPC Utility

OPC Utility is a unique tool used to configure, monitor and diagnose the HWIOPC Server. The address space of the OPC Server is organized as a hierarchy structure called a Devices tree structure. Basically, it consists of a Device Group (for one or more controllers), Device (such as an HC900 controller), Tag Group (such as for a PID, Variables, Signal Tags, etc.) and Tag (item in tag group, such as PV, a specific Variable, or a specific Signal Tag).

The maximum number of levels in the address space heirarchy of the OPC Server is 10 (including tag name). The maximum length for a full tag name (includes all levels) in the hierarchy space is 255 characters (including separator symbol '.'). Therefore, the maximum name length of each level string is 24 characters. An example of a full OPC tag name for the above OPC server configuration is: HC900R_MBTCP.HC900.Variable.VAR006 (4 levels)

Revision 1 7/05

HWIOPC Server User Manual

19

Quick Start

6.3.1 Running the OPC Utility

Refer to Step 13 in Section 4.1 Install to learn how to run the OPC Utility. The picture shown below is the main window of the OPC Utility.

6.3.2 Starting the the OPC Server

Do any of the following to start the service: Using OPC Utility on the ToolBar to start the service. Click the button Using Services console Click Start on the TaskBar, point to Settings, and then click on Control Panel. Double-click on Administrative Tools, and then double-click on Services. Right-click on the service named "HWIOPC", and then click on Start. Using OPCServer Monitor Right-click on the OPCServer Monitor displayed as an icon click on the popup menu item Start Service. on the taskbar, and then

After the service is started successfully, the OPC Utility will automatically try to build a connection with the OPC Server.

20

HWIOPC Server User Manual

Revision 1 7/05

Quick Start

6.3.3 Uploading the existing configuration

Important: Before editing a configuration, you must upload the existing configuration of the OPC Server. After uploading successfully, the address space displayed in the OPC Utility will always be same as the address space of the OPC Server. Any successful modification to the configuration on-line via the utility will also be downloaded to the OPC Server and take effect immediately. For demo purposes, there is one device group and one device in the address space of the OPC Server initialized during installation. You should delete this initial device group before you do your own configuration. You can right click on the device group for a menu selection including Delete.

6.3.4 Adding a Device Group

A device group defines a grouping for one or more devices (controllers) with a common communications driver. Follow the steps below to add a device group:

1. Select a Device Group in the Devices page if there are either one or multiple device groups in Devices Page, or go directly to Step 2. 2. Right-click on the device group or blank area in the Devices page, then click on the popup menu Add Device Group or from the Edit menu, select Device Group > Add. 3. A dialog box shown below that contains a combo box listing all device drivers will appear. Select a device driver, type the device group name, and then click on the button OK. The device driver of a device group cannot be changed once it is created.

Revision 1 7/05

HWIOPC Server User Manual

21

Quick Start

6.3.5 Adding a Device

Do the following steps to add a device:

1. Select the device group to which you want to add a device. 2. Right click on the selected device group, and then click on the popup menu Add Device; or select the menu Edit->Device->Add on the MenuBar. 3. The OPC Utility will open a wizard that will guide you for adding a device. This wizard includes the following pages: Device General Page, see page 23 Controller Type Page, see page 24 Connection Page, see page 24 Communication Page, see page 25 Tag Page, see page 25

22

HWIOPC Server User Manual

Revision 1 7/05

Quick Start

6.3.5.1 Device general page This page includes the following device properties: Device Name: for one device. Only input alphanumeric characters (A-Z, a-z) and number characters (0-9); Configuration file name: saves device properties that exist in one sub-directory of the project directory, here is \MBTCP\; configuration file name must be one XML file.

Note:
Each device should have an individual configuration file. Make sure that the configuration file name entered has not been used by another device, otherwise, the configuration of the other device that also uses the file name will be lost.

Revision 1 7/05

HWIOPC Server User Manual

23

Quick Start

6.3.5.2 Controller Type page This page includes the following device properties: Controller type: you can select any of these types of controllers: C30, C50 or C70R.

6.3.5.3 Connection page This page includes the following device properties: IP Address: Controller IP address; IP address cannot be 255.255.255.255 or 0.0.0.0; Redundant IP Address: on different subnet, only used for C70R CPU controller; Port: TCP/IP link port, 502 is default (for Modbus).

24

HWIOPC Server User Manual

Revision 1 7/05

Quick Start

6.3.5.4 Communication page This page includes the following device properties: Connect time out: range is 1-5 second Response time out: range is 1-1000 millisecond Retry delay: range is 1-500 millisecond Retry count: range 1-3

6.3.5.5 Tag page This page includes the following device properties: Tag file name: used to save all device tags. Must be a CSV file and will be saved under the data subdirectory \HTSL\data\.

Note:
Each device should have an individual tag file. You should make sure that the tag file name entered has not been used by another device; otherwise, the tags of the other device that also use the file name will be lost. Register format: this is for indicating the order for transmitting floating point registers (2 consecutive). Refer to the on-line Help of the HC Designer. FP_B is the default used for Honeywell products such as HC900. Separate Symbol: delimiter used to separate function block name and tag name in export file. This presently a fixed selection of PERIOD for the HC900 driver. Scan Rate: the rate (default is 500ms) at which the driver accesses data from the physical device. Depending on the performance of its physical device and the connection between the physical device and OPC Server PC, you can adjust it according to the needs and performance of the physical device. After setting a scan rate for the device, all tags of the device will adopt the same scan rate. Correspondingly, the edit box for Scan Rate in the tag properties dialog box will be grayed and does not allow you to change its valule.

Revision 1 7/05

HWIOPC Server User Manual

25

Quick Start

After completing the above wizard, a new device will be created from the setting in the wizard. A device summary is displayed indicating the user selections. The user can go <Back> to make desired changes or <Finish> if settings are correct. The initial status of the new device is Closed.

26

HWIOPC Server User Manual

Revision 1 7/05

Quick Start

6.3.6 Adding Tag Groups and Tags

After adding a device, you need to configure tags for the device. To configure device tags, you can use any or all of the following three methods to build the address space; however, the Import Tags method is recommended to minimize errors. The selections for dealing with the import allow the original address space to be retained and only allow additions for future edits to the configuration. Edits to the address space made be done on-line while the OPC server is running. Importing Tags from HC900: You can import tag groups and tags of a controller from a file exported by HCDesigner 3.0. Because the tags imported are the same as points in the controller and include the tag labels and descriptions, it is the most efficient of the three methods. You should start with this method and use it exclusively for edits to match your HC900 configuration as much as possible. Generating tag groups and tags automatically: This method would be used principally for simple applications to support testing an interface to a controller without importing its tags. It should not be used after the tag import method since it will overwrite the address space. Tag groups and tags will be generated for a number of control loops, Variables, Signal Tags, and Setpoint Programmers only, generated according to their number sequence in the configuration, starting with 1. All tags generated will assume default tag names and the data type for Variables and Tags is defaulted to Float. You will need to consult the Tag Information report from HC Designer to determine the assignment of specific data types to a Variable or Signal Tag number. The number of groups and tags generated may not be the same as in the controller so will need to be reviewed. Adding tag groups and tags manually This methodallows configuration of tag groups and individual tags in a group consisting of Modbus Holding Registers supported by Function Code 3 for Read and Function Code 16 and 06 for Write. To use this method, you must know the parameters Modbus address (1 to 65535 max.), its Data Type, and Access Right. For standard addresses in the controller, the Access Right is known and will be grayed out. Because of the low efficiency of the method, we recommend that you use this method only for small modifications to the HWIOPC server address space. .

Revision 1 7/05

HWIOPC Server User Manual

27

Quick Start

6.3.6.1 Importing Tags from HC900 This is the recommended method for configuring HC900 tag groups and tags. With this approach, you can import all tag groups and tags of a controller to its device in the address space from a file exported by HC Designer 3.0. The file format should be CSV (Comma delimited) and unaltered once exported from HC Designer. The file will not be imported if format errors exist.

Before the operation, you should first export tags for your HC900 configuratioon to an Export Report file using HC Designer 3.0. You can consult the Help document In HC Designer for details; however, the actions are summarized below. It is suggested that you use the All Modbus Tags report file export for initial OPC server configuration since this is the most complete, however, other report files could also be used to do this incrementally. Make sure that a Title and Author is entered for the HC900 configuration in HC Designer prior to export. To export a report, do this: In HC Designer 3.0, select File>Export Report, then select FBDs category, then All Modbus Registers from the list. Create a filename and save to a known location. You can now import tags in the exported file to the OPC Server as follows; 1. Select the Device (controller) that requires tag import. If you have not added a Device or a Device group, you should refer to add device group and add device first. 2. Click the menu Edit-> Device->Import Tags or right click on the Device and select. . The submenu Import Tag is active only when the selected node in Devices and Clients is a device, or else the submenu will be inactive. 3. An Open File Dialog will appear. Select the .csv report file exported by HC Designer 3.0. Then, click the button Open. If the file has already been opened by another application, you should close it first, and then select it. 4. A dialog box shown next will appear. Select a method used to deal with the issues of tag name duplication and Modbus address duplication that may be encountered during importing tags. You can use the defaults for initial tag import. Click on the button OK to import tags from the file selected. Click on the button Cancel if you don't want to continue.

28

HWIOPC Server User Manual

Revision 1 7/05

Quick Start

Typical HC900 Tag Import Using HCD All Modbus Tags Export Report The imported tags for HC900 will be categorized into a tag group hierarchy under the Device name as shown in the table below (depending on file content imported). All parameters for a group will be presented with their Modbus address and Data Type (Float, Word (Integer 16), Boolean). The OPC server converts Digital Signal Tags and Variables to Boolean.
Tag Group PID Signal Tag Variable SetPointParam SetPointSegment Scheduler SchedulerSegment SequenceParam SequenceStep SequenceState Alternator Stage DeviceControl Ramp Hand-Off-Auto User-Defined Sub-Group Loop Tag Name (none) (none) SPP Tag Name SPP Tag Name SPS Tag Name SPS Tag Name SEQ Tag Name SEQ Tag Name SEQ Tag Name ALT Tag Name STG Tag Name DC Tag Name RAMP Tag Name HOA Tag Name Variable Tag Name Signal Tag Name Tag Names loop parameters Signal Tags Variables SPP parameters SPP parameters SPS parameters SPS parameters SEQ parameters SEQ parameters SEQ parameters ALT parameters STG parameters DC parameters Ramp parameters HOA parameters Variables Signal Tags Group Content All control loop parameters Defined Signal Tags, Float &Bool Defined Variables, Float &Bool General programmer values All Ramp/Soak Segment values General scheduler values Segment values Segs 1-50 General sequencer values Step values Steps1-64 State number for each step All Alternator values All Stage values All Device Control values All Ramp values All HOA values All defined with data types All defined with data types

Revision 1 7/05

HWIOPC Server User Manual

29

Quick Start

Important: For future imports where you want to add only changes, you would most often use the third method of dealing with selection that retains the existing database; duplicate tags are ignored. For cases, where the second option that deals with Tag name duplication is selected, the tag in the HCD export file, whose name already exists in the address space of the OPC Server, will be renamed automatically by the OPC Server based on the following naming conventions: a. Expand an attachment at the end of the tag name. The attachment includes an underscore as a separator and the Modbus address for the tag. For example: for the tag "VAR001" whose Modbus address is 6500, the new tag name will be "VAR001_6500". Generally, the new tag would assure uniqueness. a. Add the tag to the device using the new tag name. The points in the selected file will be added to the Device as its tag groups and tags. An import log file named "ImportLog.csv" will be generated under the relative directory "\HTSL\out". The file records the importing results of each point in the selected file.

Note:
When Tag name duplication and Tag Modbus address duplication occur at the same time, the OPC Server will use the tag information in the HCD export file to overwrite the current tag information. When importing a tag export file, the OPC server will only be compatible with an HC Designer 3.0 export and will not support an export from previous versions of the HC Designer tools.

30

HWIOPC Server User Manual

Revision 1 7/05

Quick Start

6.3.6.2 Generating tag groups and tags automatically DTG is an acronym for Device Tag Generation. It is used to generate tags for an HC900 controller automatically. It is one of three methods for device tags configuration but is only recommended for test purposes. The Import Tags method is recommended for HC900 projects.

Note:
In this function, the OPC Server will clear all existing tag groups and tags of the device first, and then will generate tag groups and tags according to the your entries. If there are still active OPC items connected to these tags, the OPC items' qualities will change to be BAD since the tags have been deleted and don't exist in the address space of the OPC Server. So, before using DTG, you should delete all the OPC items connected to the OPC Server first. Do the following to use DTG: 1. Select the device (controller) for which you want to generate tags. 2. Click on the menu Edit->Device->Generate Tags as shown below.

3. A confirm message will popup to inform you that all existing tag groups and tags of the device will be cleared during the operation. If you want to continue, click on the button Yes, or else click on the button No. If you select to continue in the above step, a dialog box as shown below will appear and let you to enter the number of tag groups and tags desired. Note: You will need to consult the Tag Information Report and the Summary Function Block report in HC Designer to determine the actual tag, variable, loop, and setpoint programmer identification since this method will only list by number. These reports will also be needed to determine the data type for the signal tags and variables (analog or digital). You will need to apply the correct data type.

Revision 1 7/05

HWIOPC Server User Manual

31

Quick Start

This dialog box shown previously includes the following entry fields: Number of Loops: enter the number of consecutive PID function blocks that will be automatically generated starting with Loop 1. Parameters for each control loop are listed Number of Variables: enter the number of consecutive Variable tags that will be automatically generated starting with Variable 1 Number of Signal Tags: enter the number of consecutive signal tags that will be automatically generated starting with Signal Tag 1 Number of SP Programmers: enter the number of consecutive set point programmers function blocks will be automatically generated and the maximum number of segments for each programmer to generate tags related to a segment 6.3.6.3 Adding tag groups and tags manually 6.3.6.3.1 Adding a tag group Follow the steps below to add a tag group manually:

1. Select a device or a tag group in the Devices page. 2. Right-click on the device or tag group. Select the popup menu Add Tag Group . 3. A dialog box shown below will appear. Select a group name then click on the button OK. Note: The tag group names are fixed. If you wish to add a unique tag group, it is suggested that you add these groups under UTG (User Tag Group) or when adding tags only, simply add tags to the UTG tag group.

32

HWIOPC Server User Manual

Revision 1 7/05

Quick Start

Revision 1 7/05

HWIOPC Server User Manual

33

Quick Start

6.3.6.3.2 Adding a tag Do the following steps to add a tag manually:

1. Select the tag group into which you want to add a tag. 2. Right click on the selected tag group, then select the popup menu Add Tag. Or select the menu Edit->Tag->Add on the MenuBar. 3. The Utility will open a dialog box shown next to let you enter the properties of the new tag. 4. Click on the button OK in the dialog box; the new tag will be displayed in the tag list as the last row. Note: The access right for an established HC900 Modbus address is known; therefore, is not changeable. For Modbus registers outside of the documented register addresses for HC900, the access right can be changed.

34

HWIOPC Server User Manual

Revision 1 7/05

Quick Start

This dialog box includes the following properties: Function block: tag type selections include Variables, Signal Tag, PID, Setpoint, etc; Tag name: indicate one tag in name space. Only input alphanumeric characters (A-Z, a-z) and number characters (0-9); Address: Modbus address in the controller; Description: string used to describe the tag; Data type: selections include Float, Boolean, Short, Word, DWORD, and Long; Access Right: selections include read only, write only or read/write; Scan rate: scan rate in the OPC server. Scan rate of the tag in the OPC server, for example, how often the OPC Server will retrieve data of the tag from the physical device. Depending on the performance of its physical device and the connection between the device and OPC Server PC, you can adjust it according to the needs and performance of the physical device. The OPC Server can support different kinds of physical devices. The OPC Server can only specify a base scan rate (for example, 50ms) and cannot force a scan rate to these different kinds of physical devices. The scan rate of the tag configured here has no relationship with RevisedUpdateRate of an OPC group. When an OPC group is being created, the OPC Server has no way to know what tags will be added to the group, thus the OPC Server can only compare the requested update rate of the OPC group with the base rate. If the requested update rate is faster than the base rate, for example: 50ms, the OPC Server will return the revised rate (50ms) to the OPC client through the parameter RevisedUpdateRate. It is possible that many OPC items in different OPC groups from different OPC clients can connect with a same tag, and those OPC groups request different update rates. If the OPC Server retrieves data from the physical device for each group using different scan rates, it will largely increase the communication burden. To avoid the low efficiency, the OPC Server will periodically retrieve data from the physical device for a tag using its own scan rate set here. Note: For the device driver of redundant HC900 controllers system, you can only set a scan rate for each device (default is 500ms), all tags of the device will adopt the same scan rate. Correspondingly the edit box for Scan Rate in the above dialog box will be grayed and does not allow you to change its valule.

Revision 1 7/05

HWIOPC Server User Manual

35

Quick Start

You can click on the button to select a tag of a group type. The default properties will be filled in on the dialog box. You can change the values of the properties selections. After the function block in the tag property dialog box is confirmed, you can only add this function block type in the register map list dialog box. , the OPC utility will validate the tag address or will pop up an alarm If you click on the button dialog if the validation failed.

36

HWIOPC Server User Manual

Revision 1 7/05

Quick Start

6.4 Using the Test OPC Client

A Win32 application, serving as an OPC client, is used to verify the operation of the HWIOPC Server. It can display syntax structures, data types along with live data values, and allow write operations to assist in setting up other PC applications. It will be installed on your computer if the component named OPC Client is selected when installing the HWIOPC suite.

6.4.1 Running Test OPC Client

There are two methods to run Test OPC Client: Click on the menu Start->Programs->HWIOPC->OPC Client->OPC Client (VC) on the desktop. Click the menu Tools->Run OPC Test Client in the OPC Utility. The main window as shown below will appear,

Revision 1 7/05

HWIOPC Server User Manual

37

Quick Start

6.4.2 Browsing the address space of the Server and adding items
Do the following to browse the address space of the HWIOPC Server and add items. Start the OPC Server. Refer to Section 6.3.2 for details. 1. Right-click in the blank area of the left-top window, and then click New Server on the popup menu.

2. A dialog box listing all the OPC Servers in the local PC will appear. Select HWI.OPCServer.V1 (HWIOPCServer) in the OPC Server lists. If the HWIOPC Server is on a remote PC, enter the IP address where the OPC Server is running in the Remote Machine entry field. Leave the entry field empty if the OPC Server is running on the local machine, then click on the button OK. 3. Select and right-click on the server just created, and then click AddGroup on the popup menu. 4. The dialog box shown below will appear. Enter the relative properties and click on the button OK. Refer to the two sections, 4.5.1 General Properties and 4.4.4.1 IOPCServer::AddGroup, in opcda205A_cust.doc for the description of the parameters listed in the "AddGroup" dialog box.

5. Select and right-click on the group, and then click Add Items on the popup menu.

38

HWIOPC Server User Manual

Revision 1 7/05

Quick Start

6. The dialog box shown next will appear:

7. Then the items will be displayed in the main window of the OPC Client as shown below.

Revision 1 7/05

HWIOPC Server User Manual

39

Quick Start

6.4.3 Writing Values

To write the value of an item: 1. Select and right-click on the item, and then click Write Value to Item on the popup menu

2. A dialog box with an empty edit box will appear. Enter a value in the edit box, and then click on the button OK. The new value will be written to the OPC Server and can be observed using the test OPC Client. Note: Boolean writes require 0 for Off and 1 for On.

6.4.4 Saving Test Client File

You may save the test client configuration via the File menu as an .xml file. It can be called up for future testing to avoid re-entering group items.

6.5 Monitoring
One of the key features of the OPC Utility is monitoring the internal value of device tags of the OPC Server or real time value of the items of the OPC clients. Start Monitor in the Operation Log means that the utility will be in the Monitor mode. Stop Monitor in the Operation Log means that the utility will not be monitoring. If a tag group in the Devices page or an OPC group in the Clients page is selected, its static properties will appear in Device Tags list or Client Items list, but its dynamic properties will not appear unless Monitor is started. After Monitor is started, the OPC utility will refresh the dynamic properties of device tags or client items from the OPC Server periodically based on a 1000ms rate until Monitor is stopped. This can affect the communications performance of the OPC Server. You can configure the address space of the OPC Server in either mode - monitoring or not monitoring.

40

HWIOPC Server User Manual

Revision 1 7/05

Quick Start

6.5.1 Monitor Device Tag

The OPC utility can be used to monitor the internal value of device tags in the address space of the OPC Server. Do the following to monitor the internal value of a device tag: 1. Start the service HWIOPC. Refer to Section 6.3.2 for instructions. 2. Upload the current configuration of the OPC Server. Refer to Section 6.3.3. 3. Click the Devices tab in Devices and Clients, and select the tag group that contains the tag you want to monitor. The properties of all the tags of the selected tag group will be displayed in the Device Tags list. 4. Start Monitor by clicking on the button on ToolBar. It will display the internal value, quality, and timestamp of the tags. Click on the same button again to stop Monitor.

Note:
For efficiency, the OPC Server will not refresh the internal value of a device tag unless an OPC item linking to the device tag is created by an active OPC client. For example, in the image below, since there is no active OPC item linked to the tags of the tag group Variable, the value for these tags is shown as blank, and the qualities of these tags are BAD by default.

6.5.2 Monitor Client Item

The OPC utility can be used to monitor the real time value of the items created by OPC clients connected to the OPC Server. Do the following to monitor the real time value of an OPC item: 1. Start the service HWIOPC. Refer to Section 6.3.2 for instructions. 2. Refresh the information of all OPC clients connected to the OPC Server. Refer to Section 6.8. 3. Click on the Clients tab in Devices and Clients, and select the OPC group that contains the item you want to monitor. The properties of all the items of the selected group will be displayed in Client Items list. on the ToolBar. It will display the real time 4. Start Monitor by clicking on the button value, quality and timestamp of the client items. Click on the same button again to stop Monitor.

Revision 1 7/05

HWIOPC Server User Manual

41

Quick Start

42

HWIOPC Server User Manual

Revision 1 7/05

Quick Start

6.6 Using Tag Export file

Using the OPC Utility, you can export all tag information in the address space of the OPC Server to a CSV file. The contents of the file include full tag name, address, data type, access right, scan rate and description of each tag. To export all tag information: 1. Click on the menu File-> Export. The submenu Export Tag is active only after the operation Upload, or else the submenu will be inactive. 2. A dialog box below will appear. Select a separated char (character) that is used to divide different segments in a full tag name. The default char is DOT. Then click on the button Start if you want to export, or click on the button Cancel if you don't want to continue the operation.

3. After selecting the separated char in step 2, another dialog box titled Open will pop up to let you enter a file name. Enter the file name, and click on the button Save to continue, or else click on the button Cancel to exit the operation. 4. The dialog box displayed in step 2 will appear again and display the exporting progress. After all tags are exported to the file, the dialog box will close. 5. Open the exported file and check the tag information.

6.7 Copy/Paste OPC tag name

This function enables you to add tags from the HWIOPC server to the OPC Client if the client does not provide the capability of browsing the address space and requires you to enter the full OPC tag name. To copy the full name of a name to clipboard, select and right-click on the tag in Device Tags list, and click on the popup menu Copy full tag name to clipboard. The full tag name is copied to the clipboard and then you can paste the text to the proper entry field of the OPC client. Example of OPC tag name copy/pasted for the PV of an HC900 control loop: HC900Group.HC900_1.PID.DRUM_LVL.PV

Revision 1 7/05

HWIOPC Server User Manual

43

Quick Start

6.8 Querying OPC Clients

Using the OPC utility, you can observe all OPC clients informationconnecting with the HWIOPC Server, including their groups and static properties of items. Considering the performance of the OPC Server, the utility will not refresh the information of clients automatically. Therefore, you need to refresh the information of clients manually if you want to know the latest information on them. If you want to observe the dynamic properties of items, start Monitor. Refer to Section 6.5 for the details of how to monitor.

There are two ways to refresh the information of clients: on the ToolBar. 1. Upload both devices and clients information by clicking on the button 2. Refresh clients information by right-clicking at the Clients tab and clicking on the popup menu Refresh. See the figure below.

44

HWIOPC Server User Manual

Revision 1 7/05

Quick Start

6.9 Troubleshooting
6.9.1 Using System Tags
To monitor/diagnose device and communication status for each device, especially for the redundant controllers, the OPC server provides nine special system tags. You can browse these tags and their values through the OPC Utility or the OPC client, but cannot configure them through the OPC Utility. 6.9.1.1 System tags After the OPC server is started, device system tags will be created automatically before the creation of all other device tags. All of the nine system tags are created under the tag group named _System. That means, each device must have a tag group named _System, and under the tag group there are nine system tags as listed below: _Active: device status, its value is 1 when the device is active, communications OK at least on one port, otherwise its value is 0; device inactive or communications bad on all ports _ConnectionCount: total number of connections with the device; _ConnectionCountFailed: number of failed connections to the device; _TransactionCount: total number of transaction via Modbus protocol with device; _TransactionCountFailed: number of failed transactions via Modbus protocol; _E1Status: HC900 E1 Ethernet Port Status, Normal is 1, Failed is 0 E2Status: HC900 E2 Ethernet Port Status, Normal is 1, Failed is 0 _E1: IP address used by the HC900 controller on E1 port; _E2: Redundant IP address used by the HC900 controller on E2 port; _IP: The IP address currently used by the controller. Its value is 1 when E1 is currently used, its value is 2 when E2 is currently used, and its value is 0 if the device is closed;

6.9.1.2 Browsing system tags You can browse system tags and their values through the OPC Utility or the OPC Client. The figure below shows how system tags are displayed in the OPC Utility.

Revision 1 7/05

HWIOPC Server User Manual

45

Quick Start

6.9.2 Using Diagnosis

Diagnosis is used to observe the events that occur in the OPC Server. Before starting Diagnosis, select the events you want to diagnose. Each event and its relevant information will be displayed in the Diagnostics list as the last record. You can save the diagnostics records to file, and clear the existing diagnostics records.

Note
After Diagnosis is started, the utility will fetch the events log from the OPC Server periodically, based on 1000ms rate until Diagnosis is stopped. Diagnosis increases the burden on the OPC Server, especially while diagnosing the events relevant to data refresh, such as IOPCDataCallback::OnDataChange(). So it is recommended that you select the events you really want to diagnose and stop Diagnosis immediately if you don't need to diagnose the OPC Server any longer. 6.9.2.1 Diagnostics Record A diagnostics record includes five fields, Client the OPC Client name that connects to the OPC Server. Time The time when the event occurs. Event Event name. HRESULT Result value. Details Double-click on the client name in a diagnostics row. The details will appear as a new row after the record. Double-click on the client name again, the details row will hide. Details consist of three parts: Interface Point, Function Result, and parameters of the event.

46

HWIOPC Server User Manual

Revision 1 7/05

Quick Start

6.9.2.2 Diagnosis Result Types There are three result types in the Diagnostics list: Information It indicates that the event has executed successfully with no error or warning. Warning It indicates that the event has executed successfully with minor errors or warnings. Error It indicates that the event has failed. 6.9.2.3 Start/Stop Diagnosis

To start Diagnosis, click on the button on the ToolBar, or click on the menu item Tools->Diagnosis->Start. After Diagnosis is started successfully, the button will change to disabled. To stop Diagnosis, click on the button on the ToolBar, or click on the menu item Tools->Diagnosis->Stop. After Diagnosis is stopped successfully, the button will change to disabled. 6.9.2.4 Save Diagnostics Record This function is available only when there are one or multiple records in Diagnostics list, the OPC utility is initialized, and Diagnosis is stopped. To save the diagnostics records, right-click at Diagnostics list, then click on the popup menu item Save. Or, click on the menu Tools->Diagnosis->Save. 6.9.2.5 Clear Diagnostics Record This function is available only if there are one or multiple records in the Diagnostics list. To clear the existing diagnostics records, right-click at Diagnostics list, then click on the popup menu item Clear.

Revision 1 7/05

HWIOPC Server User Manual

47

HWIOPC DCOM Configuration

7 HWIOPC DCOM Configuration

7.1 Overview
DCOM is an object protocol that enables COM components (such as OPC client and OPC server) to communicate directly with each other across a network. To allow a remote OPC client to connect to the OPC Server over the network, a certain amount of configuration is required on both the server and the client system. On the computer running the OPC Server, you must create an account that is the same as the account used by the OPC client, and grant the account access and launch permission for the OPC Server. On the computer running the OPC Client, you must specify the location of the OPC Server that will be accessed. So, if you want to allow OPC clients to connect to the HWIOPC Server across the network, the HWIOPC DCOM configuration must be done first. The DCOM configuration is different on WinXP SP2 versus Win2000 SP4 because WinXP SP2 improves the shielding of WinXP from the network through RPC, DCOM communication, security policy, and the internal Windows firewall enhancement.

7.2 Win2000 SP4

The HWIOPC DCOM configuration can be divided to two steps: first is General Security Configuration, the other is Special Security Configuration.

7.2.1 General Security Configuration

There are two approaches to accomplish the general security configuration: Automatic DCOM configuration and Manual DCOM configuration. 7.2.1.1 Automatic DCOM configuration You can automatically set the DCOM configuration during the installation of the HWIOPC Server. If the component OPC Server is selected for installation, the dialog box shown below will appear at the last step of the installation.

Select Set DCOM permissions automatically in the dialog box shown previously, the installation will add the EVERYONE, INTERACTIVE, and SYSTEM groups to both the launch permissions and the access permissions for HWIOPC automatically.

48

HWIOPC Server User Manual

Revision 1 7/05

HWIOPC DCOM Configuration

HWIOPC Security Permissions

HWIOPC Access permissions

HWIOPC Launch permissions It is the simplest method and enables everyone to access the HWIOPC Server, but if you need higher-level security, its better to manually set the DCOM configuration using DCOMCNFG.EXE.

Revision 1 7/05

HWIOPC Server User Manual

49

HWIOPC DCOM Configuration

7.2.1.2 Manual DCOM configuration In this section, a local account named HWIOPCMngr is admitted to access and launch the HWIOPC Server as an example of how to manually set DCOM access and launch permissions. Actually, you can add the group Everyone to access permissions and launch permissions instead of the local account HWIOPCMngr, so that all accounts on the computer are enabled to access and launch the HWIOPC Server. The new configuration will take effect when the HWIOPC server is restarted. This section describes the steps for manual configuration of DCOM permissions. 7.2.1.2.1 Run DCOMCNFG You can start the DCOMCNFG by the Command Prompt line as shown below,

DCOMCNFG is a configuration tool provided by Microsoft and used to set DCOM permissions. The configuration is stored in the registry so you must be able to access the registry. It is usually simpler to install and configure the server as a user with local administrative rights. 7.2.1.2.2 DCOM Default Properties The default properties tab contains settings that affect all DCOM communication on the machine. First of all, ensure that the Enable Distributed COM on this computer is selected so that the machine is available to others via DCOM. In general, the other settings need not to be changed.

50

HWIOPC Server User Manual

Revision 1 7/05

HWIOPC DCOM Configuration

7.2.1.2.3 Select the application HWIOPC Select HWIOPC from the application list, and then click on the button Properties.

7.2.1.2.4 Security properties Page Click the security tab from the HWIOPC properties dialog box shown below.

7.2.1.2.5 Add Access permissions The access permission contains an Access Control List of principles that are allowed to interact with objects supplied by a server. To add access permissions to an account:

Revision 1 7/05

HWIOPC Server User Manual

51

HWIOPC DCOM Configuration

1. Select the Uses custom access permissions, and then click on the Edit button. The dialog box shown below will appear,

2. Click on the button Add, then all domains and groups will appear as shown in the dialog box below,

3. Click on the button Show Users to show all users. 4. Select the user name that you want to admit permission, such as the local account HWIOPCMngr, and click on the button Add.

52

HWIOPC Server User Manual

Revision 1 7/05

HWIOPC DCOM Configuration

5. Click on the button OK to finish the Access permission setting for the HWIOPC Server. 7.2.1.2.6 Add Launch permissions The launch permission contains an Access Control List of principles that are allowed to start up a server or service. The procedure to set the launch permissions is similar to those for access permissions. The only difference is that to configure launch permissions, you should select the Uses custom launch permission and click on the button Edit in the HWIOPC property dialog box, and then the steps are same as the configuration for access permissions.

7.2.2 Special Security Configuration

If the OPC client wants to connect to the HWIOPC Server running on a remote computer, it may use the default account or a special account. Default account means that the OPC client uses the current logged on user of the computer that the OPC client is running on to access the remote computer. Special account means that the OPC client always uses a special account to access the remote computer. This section will explain how to configure DCOM permissions for the two cases. 7.2.2.1 Default account Most of the OPC clients access the OPC server with a default account. In this case, you must ensure that there is an identical user with the same password as the current logged-on user of the OPC client computer existing in the computer running HWIOPC Server, and the user of the OPC Server computer has relevant permissions for HWIOPC. Do the following to admit the user with access and launch permissions for HWIOPC: 1. Create a local user account on both the server and client computer with identical user name and password, such as HWIOPCMngr. Make sure the account is enabled.

Revision 1 7/05

HWIOPC Server User Manual

53

HWIOPC DCOM Configuration

2. If you have automatically set DCOM permissions for the HWIOPC Server during installation, then go directly to next step. Otherwise, you need to grant the above account or Everyone with access and launch permissions for HWIOPC. Refer to Add Access permissions and Add Launch permissions for detailed operations. 3. Log onto the client computer with the account. 4. Start the OPC client, and configure the IP address of the server computer. Then the OPC Client can connect to the HWIOPC Server. 7.2.2.2 Special accounts Some OPC clients use a special account to access the OPC server and ignore the logon account, such as EBI or PlantScape Vista (Honeywell HMI software packages). They access the OPC server with a fixed account named mngr. To allow the OPC clients of these software packages to access the HWIOPC Server, you must do the following for each OPC client: 1. Create an account on the server computer. The user name and password of the account must be identical with the user used by the OPC client. Make sure the account is enabled. 2. If you have automatically set DCOM permissions for the HWIOPC Server during installation, then go directly to the next step. Otherwise, you need to grant the above account or Everyone with access and launch permissions for the HWIOPC. Refer to Add Access permissions and Add Launch permissions for detailed operations. 3. Start the OPC client and configure the the IP address of the server computer. Then the OPC Client can connect to the HWIOPC Server.

54

HWIOPC Server User Manual

Revision 1 7/05

HWIOPC DCOM Configuration

7.3 WinXP SP2

WinXP SP2 includes many changes and security enhancements versus Win2000, three of which directly impact OPC communication via the network. First, the local account access via a network will be authenticated as Guest by default. Second, the internal firewall has been enhanced and is turned on by default. Third, more DCOM limitations have been added. HWIOPC DCOM configuration can be divided to five steps as following.

7.3.1 Local Security Policy Setting

You need to change local security policy setting on the computer on which the HWIOPC Server is running. To change local security policy setting: 1. Open Control Panel->Administrative Tools->Local Security Policy, 2. Click on Security Settings->Local Policies->Security Options in the left tree, 3. Select the item Network access: Sharing and security model for local accounts in the right policy list and change its setting to Classic local users authenticate as themselves. Refer to the figure shown below.

Revision 1 7/05

HWIOPC Server User Manual

55

HWIOPC DCOM Configuration

7.3.2 Internal Firewall Configuration

If the OPC client application is also running on XP SP2, you need to change the internal firewall configuration of both the computer that the HWIOPC Server is running on and the computer that the OPC client application is running on, if separate. The SP2 internal firewall is turned on by default. If the machine is sufficiently protected behind a corporate firewall, then the internal firewall could be turned off permanently. When the internal firewall is turned off, the configuration for internal firewalls introduced in this section can be ignored. Otherwise, you need to follow the steps below to add programs and port to the exceptions of windows firewall. 1. Open Control Panel->Network and Internet Connections->Windows Firewall. The following dialog box will appear

2. Do not check the box Dont allow exceptions, otherwise, DCOM communication will be denied.

56

HWIOPC Server User Manual

Revision 1 7/05

HWIOPC DCOM Configuration 3. Click the tab Exceptions, the page shown below will appear,

4. Click the button Add Program. A dialog box titled Add a Program will appear as shown below.

5. Select HWIOPC from the Programs list. If it does not exist in the Programs list, you can click on the button Browse to find HWIOPC.exe under the installed directory. The default directory is C:\Program Files\HTSL\server\HWIOPC.exe. Click OK to add HWIOPC to Exceptions page.
Revision 1 7/05 HWIOPC Server User Manual 57

HWIOPC DCOM Configuration Similarly, add Microsoft Management Console (used by the DCOM configuration utility) and all other OPC client applications that will connect to the remote OPC Server via DCOM to the Exceptions page, such as OPC Client(VC). The file name of Microsoft Management Console is mmc.exe under the system directory. The default is C:\Windows\system32\mmc.exe. 6. Click Add Port in the Exceptions page, the dialog box below will appear,

Enter DCOM in Name field, enter 135 in Port number field, select TCP radio button, and then click OK.

58

HWIOPC Server User Manual

Revision 1 7/05

HWIOPC DCOM Configuration

7.3.3 My computer Properties

You need to configure common DCOM security on the computer on which the HWIOPC Server is running. 7.3.3.1 Run DCOMCNFG DCOMCNFG is a configuration utility provided by Microsoft and used to set DCOM permissions. The configuration is stored in the registry so you must be able to access the registry. It is usually simpler to install and configure the server as a user with local administrative rights. You can start the DCOMCNFG by the command line as shown below,

Then Component Services window will appear as shown below,

Component Services (DCOMCNFG Main Window)

Revision 1 7/05

HWIOPC Server User Manual

59

HWIOPC DCOM Configuration

7.3.3.2

DCOM Default Properties

Click on Console Root->Component Services->Computers in the left tree of Component Services, then select My computer in the right sub window as shown below,

Right click on My Computer and click on the popup menu Properties. A dialog box titled My Computer Properties will appear. Select the tab Default Properties, the following page will appear,

My Computer Properties Select the Enable Distribute COM on this compute so that the machine is available to others via DCOM. In general, the other settings need not be changed.

60

HWIOPC Server User Manual

Revision 1 7/05

HWIOPC DCOM Configuration

7.3.3.3

Common DCOM Security

Do the following to edit COM security of My computer, 1. Click the tab COM Security in the My Computer Properties dialog box shown previously. The page shown below will appear,

COM Security 2. Click the button Edit Limits in Access Permissions. The following dialog box titled Access Permission will appear,

Add Everyone to the Group or user names list of the Access Permission dialog box, and allow both Local Access and Remote Access permission for Everyone.
Revision 1 7/05 HWIOPC Server User Manual 61

HWIOPC DCOM Configuration Select ANONYMOUS LOGON in the Group or user names list, and allow both Local Access and Remote Access permission to it. Click the button OK back to the COM Security page. 3. Click the button Edit Limits in Launch and Activation Permissions of the COM Security page, then the following dialog box titled Launch Permission will appear,

Add Everyone to the Group or user names list of the above Launch Permission dialog box, and allow Local Launch, Remote Launch, Local Activation and Remote Activation permissions for Everyone.

62

HWIOPC Server User Manual

Revision 1 7/05

HWIOPC DCOM Configuration

7.3.4 HWIOPC DCOM Properties

You need to conduct HWIOPC DCOM configuration introduced in this section on the computer on which the HWIOPC Server is running. There are two approaches to conduct the DCOM configuration: Automatic DCOM configuration and manual DCOM configuration. 7.3.4.1 Automatically configure HWIOPC DCOM Properties You can automatically set the DCOM configuration during the installation of the HWIOPC Server. If the component OPC Server is chosen for installation, the dialog box shown below will appear at the last step of installation.

Select Set DCOM permissions automatically in the above dialog box, the installation will add the EVERYONE, INTERACTIVE and SYSTEM groups to launch permissions (including Local Launch, Remote Launch and Local Activation) and access permisstions (including Local Access and Remote Access) for the HWIOPC automatically as shown below,

HWIOPC DCOM Propeties

Revision 1 7/05

HWIOPC Server User Manual

63

HWIOPC DCOM Configuration

HWIOPC Launch permissions

HWIOPC Access permissions It is a simplest method and enables everyone to access the HWIOPC Server. But, if you need higher-level security, manually set the DCOM configuration using DCOMCNFG.EXE.

64

HWIOPC Server User Manual

Revision 1 7/05

HWIOPC DCOM Configuration

7.3.4.2 Manually configure HWIOPC DCOM Properties In this section, a local account named HWIOPCMngr belonging to the Users group is admitted to access and launch the HWIOPC Server as an example of how to manually set DCOM access and launch permissions. Actually, you can add the group Everyone to access permissions and launch permissions instead of the local account HWIOPCMngr, so that all accounts on the computer are enabled to access and launch the HWIOPC Server. The new configuration will not take effect until the HWIOPC server is restarted. This section describes the steps to manually configure DCOM permissions. 7.3.4.2.1 Run DCOMCNFG Refer to Run DCOMCNFG. 7.3.4.2.2 Open the DCOM properties dialog box of HWIOPC Click Console Root->Component Services->Computers->My Computer->DCOM Config->HWIOPC in the left tree of Component Services as shown below,

Revision 1 7/05

HWIOPC Server User Manual

65

HWIOPC DCOM Configuration Select and right-click HWIOPC, then click the popup menu Properties. The following dialog box will appear,

HWIOPC DCOM Properties 7.3.4.2.3 Security properties Page Click the tab Security at the HWIOPC DCOM Properties dialog box, the page below will appear,

Security page of HWIOPC DCOM Properties

66

HWIOPC Server User Manual

Revision 1 7/05

HWIOPC DCOM Configuration

7.3.4.2.4 Add Launch and Activation permissions The launch and activation permission contains an Access Control List of principles that are allowed to start up a server or service and activate the server and service. To add launch and activation permissions to an account: 1. Select the radio button Customize and click on the button Edit in Launch and Activation Permissions of the Security page of HWIOPC DCOM Properties dialog box. The Launch Permission dialog box shown below will appear.

Launch Permission 2. Click on the button Add, then a dialog box used to select Users or Groups as below will appear,

Revision 1 7/05

HWIOPC Server User Manual

67

HWIOPC DCOM Configuration

3. Enter the user name for which you want to admit permission, such as the local account HWIOPCMngr. Click on the button OK and go back to the Launch Permission dialog box as shown below,

4. Select the four checkboxes to allow permissions: including Local Launch, Remote Launch, Local Activation and Remote Activation. 5. Click the button OK to finish the Access permission. Then, the account will be added to Group or user names that have launch and activation permissions for the HWIOPC Server. 7.3.4.2.5 Add Access permissions The access permission contains an Access Control List of principles that are allowed to interact with objects supplied by a server. To add access permissions to an account, select the radio button Customize and click on the button Edit in Access Permissions of the Security page of HWIOPC DCOM Properties dialog box, and then go through the similar steps of the configuration for launch and activation permissions.

68

HWIOPC Server User Manual

Revision 1 7/05

HWIOPC DCOM Configuration

7.3.5 Special Security Configuration

If the OPC client wants to connect the HWIOPC Server running on a remote computer, it may use Default account or Special account. Default account means that the OPC client uses the current logged user of the computer on which the OPC client is running to access the remote computer. Special account means that the OPC client always uses a special account to access the remote computer. The section will explain how to configure DCOM permissions for the two cases. 7.3.5.1 Default account Most of the OPC clients access the OPC server with default account. In this case, you must ensure that there is an account using the same user name and password as the current logged-on user of the OPC client computer existing in the computer on which the HWIOPC Server is running and that the account of the OPC Server computer has relevant permissions for the HWIOPC. Do the following to admit the account with access and launch permissions for the HWIOPC, 1. Create a local user account on both the server and client computer with an identical user name and password, such as HWIOPCMngr . Make sure the account is enabled. 2. If you have automatically set DCOM permissions for the HWIOPC Server during installation, then go directly to the next step. Otherwise, you need to grant the above account or Everyone with access and launch permissions for the HWIOPC. Refer to Add Launch and Activation permissions and Add Launch permissions for detailed operations. 3. Log on the client computer with the account such as HWIOPCMngr. 4. Start the OPC client, and configure the IP address of the server computer. Then the OPC Client can connect to the HWIOPC Server.

7.3.5.2 Special account Some OPC clients use a special account to access the OPC server and ignore the logon account, such as EBI or PlantScape Vista (Honeywell software packages). They access the OPC server with a fixed account named mngr. To allow the OPC clients of these software packages to access the HWIOPC Server, you must do the following for each OPC client, 1. Create an account on the server computer. The user name and password of the account must be identical with the user used by the OPC client. Make sure the account is enabled. 2. If you have automatically set DCOM permissions for the HWIOPC Server during installation, then go directly to next step. Otherwise, you need to grant the above account or Everyone with access and launch permissions for the HWIOPC. Refer to Add Launch and Activation permissions and Add Launch permissions for detailed operations. 3. Start the OPC client, and configure the IP address of the server computer. Then, the OPC Client can connect to the HWIOPC Server.

Revision 1 7/05

HWIOPC Server User Manual

69

Other Information

8 Other Information
Contact your local sales representative to obtain other product notes relative to the OPC server interface to the OPC clients for Specview, PlantScape Vista R400, Experion, or EBI.

70

HWIOPC Server User Manual

Revision 1 7/05

Definition List

9 Definition List
Address Space The address space of the HWIOPC Server is organized as a hierarchy structure called Devices tree structure. It includes Device Group, Device, Tag Group and Tag. Hierarchy space maximum level number in address space of HWHtslOPC Server is 10(include tag name), the maximum length of tag name in hierarchy space is 255 characters (include separator symbol '.'). So, the maximum length of each level string is 24 characters. Asynchronous vs. Synchronous Assuming that most OPC clients want to access Cached data in OPC Server, there are several ways for a client to obtain that data from a server. It can perform a synchronous read from cache (simple and reasonably efficient). This may be appropriate for fairly simple clients that are reading relatively small amounts of data and where maximum efficiency is not a concern. A client that operates in this way is essentially duplicating the scanning that the server is already doing. It can subscribe to cached data using IAdviseSink or IOPCDataCallback which is more complex but very efficient. This is the recommended behavior for clients because it will minimize use of CPU and NETWORK resources. See opcda205A_cust.doc for more information. Asynchronous Read The OPC client reads one or more items in a OPC group from the OPC Server through calling IOPCAsyncIO2::Read (OPC DA v2.05A) or IOPCAsyncIO::Read (OPC DA v1.0A). The results are returned via the clients IOPCDataCallback connection established through the servers IConnectionPointContainer. See the two sections, IOPCAsyncIO2::Read and IOPCAsyncIO::Read, in opcda205A_cust.doc for more information. Asynchronous Cache Refresh The OPC client forces a callback to IOPCDataCallback::OnDataChange for all active items in the group (whether they have changed or not) through calling IOPCAsyncIO2::Refresh2 (OPC DA v2.05A) or IOPCAsyncIO::Refresh (OPC DA v1.0A). Inactive items are not included in the callback. There is a parameter named dwSource that indicates the data source, i.e. where the data comes from. The values of dwSource includes CACHE or DEVICE. If the data source is CACHE, the OPC Server will return the data in the cache of the OPC Server to the OPC client via Callback. Asynchronous Cache Refresh indicates this case. Otherwise, if the data source is Device, then all active items in the CACHE are refreshed from the device BEFORE the callback. Asynchronous Device Refresh indicates this case. See the two sections, IOPCAsyncIO2::Refresh2 and IOPCAsyncIO::Refresh, in opcda205A_cust.doc for more information. Asynchronous Device Refresh The OPC client forces a callback to IOPCDataCallback::OnDataChange for all active items in the group (whether they have changed or not) through calling IOPCAsyncIO2::Refresh2 (OPC DA v2.05A) or IOPCAsyncIO::Refresh (OPC DA v1.0A). Inactive items are not included in the callback. There is a parameter named dwSource that indicates the data source, i.e. where the data comes from. The values of dwSource includes CACHE or DEVICE. If the data source is CACHE, the OPC Server will return the data in the cache of the OPC Server to the OPC client via Callback. Asynchronous Cache Refresh indicates this case. Otherwise, if the data source is Device, then all active items in the CACHE are refreshed from the device BEFORE the callback. Asynchronous Device Refresh indicates this case. See the two sections, IOPCAsyncIO2::Refresh2 and IOPCAsyncIO::Refresh, in opcda205A_cust.doc for more information.
Revision 1 7/05 HWIOPC Server User Manual 71

Definition List

Backup An operation used to backup the current configuration files of the OPC Server to a package file. The package file can be restored to the OPC Server as the current configuration using Restore. The two operations will enable you to save stage configuration. For example, you need to save the configuration for one project before starting a new configuration for another project. Client A Win32 application working as an OPC Client and communicating with the OPC Server using OPC v2.05A or v1.0A protocol. All the OPC clients connected to the HWIOPC Server can be displayed in the Clients page of the utility. Data Type A classification for one of various types of data such as: Float - 32 bit Real value (double register), IEEE format typical of analog data in HC900 Boolean - Single bit data On or Off - typical of digital Variables and Signal Tags in HC900 Word - Unsigned 16 bit integer data typical of bit-packed registers in HC900 Short - Signed 16 bit integer data typically not used in HC900 DWord - Unsigned 32 bit integer data - typically not used in HC900 Long - Signed 32 bit integer data - typically not used in HC900 DCOM Distributed Component Object Model. It is a version of the COM that is designed to work across networks and, specifically, the Internet. Device The second level inthe Devices tree structure. It is displayed in the Devices page, and can contain one or multiple tag groups and tags. Each device group can contain a maximum of 255 devices. In Devices tree, there are five kinds of images before a device, each image represents a different status. The status of all devices will be refreshed automatically in the OPC Utility. Refer to Device Status. Each device group can contain a maximum of 255 devices. Device Driver Each device driver is an INPROC COM Server that should be registered in the machine where the OPC Server is running. A device driver serves as a bridge between the HWIOPC Server and the physical devices, such as HC900 controllers. The HWIOPC Server can read data from and write data to a physical device by using the corresponding device driver. Each device driver supports a kind of physical device. Through different device drivers, the HWIOPC can communicate with different kinds of physical devices. For redundant HC900 controllers system, the default name of its device driver is "HC900 Ethernet Driver", the ProgID of its device driver is "MBHC900R.MBTCP.1". All devices of a device group in the Devices tree structure of the HWIOPC Server must use one identical device driver. Device Group The first level in the Devices tree structure. It contains one or multiple devices using the same device driver. For example, a device group named C70RControllers contains all the C70R controllers, and another device group named C30Controllers contains all the C30 controllers. The maximum number of device groups in OPC Server is 255. Device Status The main status of a device includes Opened/Closed and Active/InActive. When a device is closed, the OPC Server will not build a connection or communicate with its physical device. When a device is opened, the OPC Server will try to communicate with its physical device to get or write data, and so you can not only configure the device but also watch data of tags of the device through the OPC Utility and the OPC Client. If the OPC Server can connect and

72

HWIOPC Server User Manual

Revision 1 7/05

Definition List

communicate with its physical device successfully, then the device is called Active. If the OPC Server fails to communicate or connect with its physical device, the device is called InActive. In the Devices tree, there are five kinds of images before a device; each image represents a different status. The status of all devices will be refreshed automatically in the OPC Utility. Devices Tree Structure See Address Space. Diagnosis A working mode of the OPC Utility. It is used to observe the events that occur in the OPC Server. Before starting Diagnosis, you need to select the events you want to diagnose. Each event and its relevant information will be displayed in the Diagnostics list as the last record. Dynamic Properties Dynamic property means that the value may be changed due to the change of point value in physical devices or the change of the communication status between the OPC Server and the physical devices. A Device Tag has three dynamic properties: Internal Value, Timestamp and Quality. An OPC Item also has three dynamic properties: Real Time Value, Timestamp and Quality. Export An operation used to output all tags information in the address space of the OPC Server to a CSV file. The contents of the file include full tag name, address, data type, access right, scan rate and description. Group An OPC group created by an OPC client. All groups of the OPC clients connected to the HWIOPC Server can be displayed in the Clients page of the OPC Utility. HC900R Device Driver A kind of Device Driver used to support the communication between the HWIOPC Server and redundant HC900 controller system. Its ProgID is "MBHC900R.MBTCP.1". Its default name in the OPC Utility is "HC900 Ethernet Driver". HWIOPC Server The HWIOPC Server is a Honeywell Instruments OPC Server developed by HTSL that follows OPC DA v2.05A and is compatible with OPC DA v1.0A protocol. It supports the standard objects and interfaces of both custom interface and automation interface, but does not provide optional objects or interfaces. The HWIOPC Server provides a means of bringing data and information from Honeywell HC 900 controller (C30, C50 and C70R) systems to client applications on local or remote computers. The ProgID of the HWIOPC Server is "HWI.OPCServer.V1". The HWIOPC Server runs as a background service named "HWIOPC". It will be installed on your computer if the component named OPC Server is chosen when installing the HWIOPC suite. The startup type of the service is initialized to be automatic during the installation. In this reference, HWIOPC Server is also shortened to be OPC Server. HWIOPC Suite A suite of products developed by HTSL for the purpose of providing data and information from Honeywell HC 900 controller (C30, C50 and C70R) systems to client applications on local or remote computers. It can be installed on your computer by using the installation package named HWIOPCInstall.exe. The suite consists of the following parts, OPC Server, HC900R device driver, OPC Utility, OPC Client and HTSLLogViewer. HTSLLogViewer A Win32 application developed by HTSL and used to query log message recorded by the HWIOPC Server and device drivers in log files. It cannot open a log file that is currently opened by another application, such as the background service HTSLLogger. It will be installed on your computer if the component named OPC Server is chosen when installing the HWIOPC suite.

Revision 1 7/05

HWIOPC Server User Manual

73

Definition List

Import One of the three methods used to configure tag groups and tags for a device. It can create tag groups and tags for a device automatically according to the points information in a .csv file exported by the HCDesigner3.0. Internal Value (of Tag) The OPC Server stores the value in its cache for each tag. The value in the cache of OPC Server is called Internal Value in the reference. If there is no OPC item connected to a tag, the internal value of the tag will be invalid, the quality of the tag will be bad. If there is one or more OPC items connected to a tag and the OPC Server communicates with the physical device normally, the internal value of the tag will be valid, the quality of the tag will be good. Item An OPC item created by an OPC client under an OPC group. All items of the OPC clients connected to the HWIOPC Server can be displayed in the Client Items list of the OPC Utility. LoopModeMap A special tag in the PID tag group that represents the mode of an HC900 control loop. It is used to interface Mode status with Honeywells PlantScape Vista, Experion, and EBI software database via their OPC Client driver. It allows both reading and writing the loops mode MAN/AUTO and LSP/RSP when using the Mode acronyms for IM&C products (UDC/Micromax/S9000 selection for mode acronym setup during installation. It uses the Modbus address 0xXX00 (hex). For example, the LoopModeMap address for Loop #1 is 0x0100 (256 in decimal), the LoopModeMap address for Loop #2 is 0x0200 (512 in decimal), and so on. When importing or generating tags, the OPC Server will create the tag automatically for each control loop. You can also manually configure the tag LoopModeMap for a control loop tag group. The mapping of status and tag value is shown below,
MODE Status in EBI R300/ePKS R210 MODE Status in PlantScape VISTA R400 Mode Value

MAN AUTO CASC MAN-RSP

MAN-LSP AUTO-LSP AUTO-RSP MAN-RSP

0 1 2 6

When LoopModeMap is part of an OPC tag, it is used for both the Source and Destination addresses in an Analog point definition for a control loop within the Quick Builder database generator. Monitor A working mode of the OPC Utility. It is used to watch the dynamic properties of client items or device tags. Start Monitor means the utility will be in monitor mode. Stop Monitor means the utility will not be monitoring. If a tag group in the Devices page or a group in the Clients page is selected, its static properties will show in the Device Tags list or the Client Items list , but its dynamic properties will not show unless Monitor is started. After Monitor is started, the OPC Utility will refresh the dynamic properties of device tags or client items from the OPC Server periodically based on a 1000ms rate until Monitor is stopped. It may affect the communication performance of the OPC Server so should be used cautiously. You can configure the address space of the OPC Server when in the monitor mode, or not monitoring. OPC OLE for Process Control.

74

HWIOPC Server User Manual

Revision 1 7/05

Definition List

OPC Server In this reference, it is a short name of the HWIOPC Server. OPC Test Client A Win32 application, serving as an OPC client, is developed with VC++ v6.0 by HTSL for the purpose of verifying the operation of the HWIOPC Server. It can display syntax structures, data types along with live data values and allow write operations to assist in setting up other PC applications. It will be installed on your computer if the component named OPC Client is chosen when installing the HWIOPC suite. OPC Utility A Win32 application named OPCUtility. It is developed by HTSL, and is a unique tool used to configure, monitor and diagnose the HWIOPC Server. It will be installed on your computer if the component named OPC Server is chosen when installing the HWIOPC suite. Restore An operation used to restore a package file to the OPC Server as the current configuration. The package file is generated by the operation Backup. The two operations will enable you to save and stage a configuration. For example, you need to save the configuration for one project before starting a new configuration for another project. Scan Rate The rate at which the driver accesses data from the device in support of requests from OPC clients. Depending on the performance of its physical device and the connection between the device and OPC Server PC, you can adjust it according to the needs and performance of the physical device. The OPC Server can support different kinds of physical devices. The OPC Server can only specify a base scan rate (for example, 50ms) and cannot force a scan rate to these different kinds of physical devices. The scan rate of the tag configured here has no relationship with RevisedUpdateRate of an OPC group. When an OPC group is being created, the OPC Server has no way to know what tags will be added to the group, thus the OPC Server can only compare the requested update rate of the OPC group with the base rate. If the requested update rate is faster than the base rate, for example: 50ms, the OPC Server will return the revised rate (50ms) to the OPC client through the parameter RevisedUpdateRate. It is possible that many OPC items in different OPC groups from different OPC clients can connect with a same tag, and those OPC groups request different update rates. If the OPC Server retrieves data from the physical device for each group using different scan rates, it will largely increase the communication burden. To avoid the low efficiency, the OPC Server will periodically retrieve data from the physical device for a tag using its own scan rate set here. Note: For the device driver of redundant HC900 controllers system, because the device driver communicates with the controller via Modbus protocol, and according to this protocol, the continuous addresses should be enveloped into one transaction to maximize the efficiency of communication. To support both different scan rate for each tag and continuous addresses in one transaction, HWIOPC Server needs to build different group according to different scan rate and different addresses. However, HWIOPC Server supports online editing and its response performance is critical, if HWIOPC wastes too much time on dynamic grouping analysis during all kinds of configuration and checking whether it is time for all groups to refresh data, its performance may be degraded. Thus you can only set a scan rate for each device (default is 500ms), all tags of the device will adopt the same scan rate. Correspondingly the edit box for Scan Rate in the dialog box below will be grayed and does not allow you to change its valule. Static Properties Static property means that the value of which will be changeless unless you changes its configuration. There are eight properties of an OPC item. Five of them are static properties: Tag Name, Data Type, Scan Rate, Access Right and Description.

Revision 1 7/05

HWIOPC Server User Manual

75

Definition List

There are also eight properties of a Device Tag. Five of them are static properties: Tag Name, Data Type, Scan Rate, Access Right and Description. Synchronous Cache Read This function reads the value, quality and timestamp information for one or more items in a group through calling IOPCSyncIO::Read. The function runs to completion before returning. The data can be read from CACHE in which case it should be accurate to within the UpdateRate and percent deadband of the group. Synchronous Cache Read indicates this case. The data can be read from the DEVICE in which case an actual read of the physical device is to be performed. Synchronous Device Read indicates this case. Expected behavior is that a CACHE read should be completed very quickly (within milliseconds). A DEVICE read may take a very long time (many seconds or more). For this reason the OPC clients are expected to use CACHE reads in most cases. DEVICE reads are intended for special circumstances such as diagnostics. See the section IOPCSyncIO::Read in opcda205A_cust.doc for more information. Synchronous Device Read This function reads the value, quality and timestamp information for one or more items in a group through calling IOPCSyncIO::Read. The function runs to completion before returning. The data can be read from CACHE in which case it should be accurate to within the UpdateRate and percent deadband of the group. Synchronous Cache Read indicates this case. The data can be read from the DEVICE in which case an actual read of the physical device is to be performed. Synchronous Device Read indicates this case. Expected behavior is that a CACHE read should be completed very quickly (within milliseconds). A DEVICE read may take a very long time (many seconds or more). For this reason the OPC clients are expected to use CACHE reads in most cases. DEVICE reads are intended for special circumstances such as diagnostics. See the section IOPCSyncIO::Read in opcda205A_cust.doc for more information. Tag The last level in the Devices tree structure. It is different from the above three kinds of nodes. When a tag group on the Devices page is selected, all tags of the tag group will show in the Device Tags list. Each device can contain a maximum of 10000 tags. Tag Group The middle level in the Devices tree structure. For HC900 controllers, specific first level tag groups are automatically generated when the Import Tags method is used to develop the OPC address space. A tag group can contain one or multiple sub tag groups and tags. The maximum level of tag groups is 7. For example: you can create no more than seven levels of tag groups. For HC900 controllers (C30, C50 and C70R), You can only select a tag group name from a combo box when adding the first level tag group. The tag groups in the combo box include AnalogInput, DiscreteInput, DiscreteOutput, SignalTag, Variable, PID, SetPoint, SetPointParam, SetPointAdditional, SetPointSegment, Scheduler, SchedulerSegment, SequenceParam, SequenceStep, SequenceState, Stage, Ramp, Hand-Off-Auto, Alternator, DeviceControl, UserDefined, MiscellaneousParam, and UTG. Except for the type UTG, you can only add the tags whose addresses are in the range of the register map of the tag group, or else system will inform you that the tag address is invalid. For the tag group UTG, you can enter any Modbus address ranging from 1 to 65535. These are refered to as Holding Registers and the system will read data for these addresses via function code 03 and write via function code 06 or 16. You can add a maximum of 1000 tags under the tag group UTG. For HC900 Modbus addresses, the Access Right is known and, therefore, grayed. For open addresses (not dedicated), the Access Right is available for selection.

76

HWIOPC Server User Manual

Revision 1 7/05

Definition List

For example, when you want to add a tag under the tag group Variable (including directly under the tag group Variable or under a sub tag group of the tag group Variable), you can only add the tags whose addresses are in the range of the Variable register map.

Upload An operation used to retrieve the existing configuration of the address space and clients information of the OPC Server to the OPC Utility. UTG This is an acronym for User Tag Group. This type of tag group for HC900 controllers (including C30, C50 and C70R) allows the user to define a unique group of Modbus addresses. Unlike other types of tag groups, such as PID and Variable, you can enter any address ranging from 1 to 65535 for tags in this group defined as Holding Registers. The system will read data for these registers using function code 03 and write via function code 06 or 16. User can add a maximum of 1000 tags under the tag group UTG. For HC900 Modbus addresses, the Access Right is known and, therefore, grayed. For open addresses (not dedicated), the Access Right is available for selection.

Revision 1 7/05

HWIOPC Server User Manual

77

Sales and Service

Sales and Service

For application assistance, current specifications, pricing, or name of the nearest Authorized Distributor, contact one of the offices below.
ARGENTINA Honeywell S.A.I.C. Belgrano 1156 Buenos Aires Argentina Tel. : 54 1 383 9290 ASIA PACIFIC Honeywell Asia Pacific Inc. Room 3213-3225 Sun Kung Kai Centre N 30 Harbour Road Wanchai Hong Kong Tel. : 852 829 82 98 AUSTRALIA Honeywell Limited 5 Thomas Holt Drive North Ryde Sydney Nsw Australia 2113 Tel. : 61 2 353 7000 AUSTRIA Honeywell Austria G.M.B.H. Handelskai 388 A1020 Vienna Austria Tel. : 43 1 727 800 BELGIUM Honeywell S.A. 3 Avenue De Bourget B-1140 Brussels Belgium Tel. : 32 2 728 27 11 BRAZIL HONEYWELL DO Brazil And Cia Rua Jose Alves Da Chunha Lima 172 Butanta 05360.050 Sao Paulo Sp Brazil Tel. : 55 11 819 3755 BULGARIA HONEYWELL EOOD 14, Iskarsko Chausse POB 79 BG- 1592 Sofia BULGARIA Tel : 359-791512/ 794027/ 792198 CANADA Honeywell Limited The Honeywell Centre 300 Yorkland Blvd. Toronto, Ontario M2j 1s1 Canada Tel.: 800 461 0013 Fax:: 416 502 5001 CZECH REPUBLIC HONEYWELL, Spol.S.R.O. Budejovicka 1 140 21 Prague 4 Czech Republic Tel. : 42 2 6112 3434 DENMARK HONEYWELL A/S Automatikvej 1 DK 2860 Soeborg DENMARK Tel. : 45 39 55 56 58 FINLAND HONEYWELL OY Ruukintie 8 FIN-02320 ESPOO 32 FINLAND Tel. : 358 0 3480101 FRANCE HONEYWELL S.A. Btiment le Mercury Parc Technologique de St Aubin Route de lOrme (CD 128) 91190 SAINT-AUBIN FRANCE Tel. from France: 01 60 19 80 00 From other countries: 33 1 60 19 80 00 NORWAY HONEYWELL A/S Askerveien 61 PO Box 263 N-1371 ASKER NORWAY Tel. : 47 66 76 20 00 POLAND HONEYWELL Sp.z.o.o UI Domaniewksa 41 02-672 WARSAW POLAND Tel. : 48 22 606 09 00 PORTUGAL HONEYWELL PORTUGAL LDA Edificio Suecia II Av. do Forte nr 3 - Piso 3 2795 CARNAXIDE PORTUGAL Tel. : 351 1 424 50 00 REPUBLIC OF IRELAND HONEYWELL Unit 1 Robinhood Business Park Robinhood Road DUBLIN 22 Republic of Ireland Tel. : 353 1 4565944 REPUBLIC OF SINGAPORE HONEYWELL PTE LTD BLOCK 750E CHAI CHEE ROAD 06-01 CHAI CHEE IND.PARK 1646 SINGAPORE REP. OF SINGAPORE Tel. : 65 2490 100 REPUBLIC OF SOUTH AFRICA HONEYWELL Southern Africa PO BOX 138 Milnerton 7435 REPUBLIC OF SOUTH AFRICA Tel. : 27 11 805 12 01

GERMANY HONEYWELL AG Kaiserleistrasse 39 D-63067 OFFENBACH GERMANY Tel. : 49 69 80 64444 HUNGARY HONEYWELL Kft Gogol u 13 H-1133 BUDAPEST HUNGARY Tel. : 36 1 451 43 00 ICELAND HONEYWELL Hataekni .hf Armuli 26 PO Box 8336 128 reykjavik Iceland Tel : 354 588 5000 ITALY HONEYWELL S.p.A. Via P. Gobetti, 2/b 20063 Cernusco Sul Naviglio ITALY Tel. : 39 02 92146 1 MEXICO HONEYWELL S.A. DE CV AV. CONSTITUYENTES 900 COL. LOMAS ALTAS 11950 MEXICO CITY MEXICO Tel : 52 5 259 1966 THE NETHERLANDS HONEYWELL BV Laaderhoogtweg 18 1101 EA AMSTERDAM ZO THE NETHERLANDS Tel : 31 20 56 56 911

ROMANIA HONEYWELL Office Bucharest 147 Aurel Vlaicu Str., Sc.Z., Apt 61/62 R-72921 Bucharest ROMANIA Tel : 40-1 211 00 76/ 211 79 RUSSIA HONEYWELL INC 4 th Floor Administrative Builiding of AO "Luzhniki" Management 24 Luzhniki 119048 Moscow RUSSIA Tel : 7 095 796 98 00/01 SLOVAKIA HONEYWELL Ltd Mlynske nivy 73 PO Box 75 820 07 BRATISLAVA 27 SLOVAKIA Tel. : 421 7 52 47 400/425 SPAIN HONEYWELL S.A Factory Josefa Valcarcel, 24 28027 MADRID SPAIN Tel. : 34 91 31 3 61 00 SWEDEN HONEYWELL A.B. S-127 86 Skarholmen STOCKHOLM SWEDEN Tel. : 46 8 775 55 00 SWITZERLAND HONEYWELL A.G. Hertistrasse 2 8304 WALLISELLEN SWITZERLAND Tel. : 41 1 831 02 71 Contd

78

HWIOPC Server User Manual

Revision 1 7/05

Sales and Service

TURKEY HONEYWELL A.S. Caryiryolu Sok No. 7 Ucgen Plaza, Kat 5-6-7 Icerenkoy 81120 Instanbul Turkey Tel (90-216) 575 66 00 UNITED KINGDOM HONEYWELL Honeywell House Arlington Business Park Bracknell, Berkshire RG12 1EB Tel: +44 (0) 1344 656000 U.S.A. HONEYWELL INC. INDUSTRIAL PROCESS CONTROLS 1100 VIRGINIA DRIVE PA 19034-3260 FT. WASHINGTON U.S.A. Tel. : 1-800-343-0228 VENEZUELA HONEYWELL CA APARTADO 61314 1060 CARACAS VENEZUELA Tel. : 58 2 239 0211

Revision 1 7/05

HWIOPC Server User Manual

79

Industrial Measurement and Control Honeywell International 1100 Virginia Drive Fort Washington, PA 19034
51-52-25-141 Rev. 1 0705 Printed in USA

www.honeywell.com/imc