OPC User Manual en.pdf

7/30/2019 OPC User Manual en.pdf

1/86

Industrial Measurement and Control

HWIOPC Server

User Manual

Doc. No.:51-52-25-141

Revision: 1

Date: 7/05


2/86

ii HWIOPC Server User Manual Revision 17/05

NNoott iicceess aanndd TTrraaddeemmaarrkkss

Copyright 2005 by HoneywellRevision 1 July 2005

WARRANTY/REMEDY

Honeywell warrants goods of its manufacture as being free of defective materials and faultyworkmanship. Contact your local sales office for warranty information. If warranted goodsare returned to Honeywell during the period of coverage, Honeywell will repair or replacewithout charge those items it finds defective. The foregoing is Buyer's sole remedy and is inlieu of all other warranties, expressed or implied, including those of merchantabilityand fitness for a particular purpose. Specifications may change without notice. Theinformation 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 theHoneywell web site, it is up to the customer to determine the suitability of the product in theapplication.

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.


3/86

Revision 1 HWIOPC Server User Manual iii7/05

LLiicceennssee AAggrreeeemmeenntt

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, onone 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. Youmay 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 COPIESYou 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 Softwaredocumentation 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'srights 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.


4/86

iv HWIOPC Server User Manual Revision 17/05

AAbboouutt TThhiiss DDooccuummeenntt Abstract

The HWIOPC Server (Honeywell Industrial OPC Server) provides a means for interfacing data fromHoneywell 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 Doc ID

HC900 Controller Installation and User Guide 51-52-25-107

HC Designer User Guide 51-52-25-110

ContactsWorld Wide Web

The following lists Honeywells World Wide Web sites that will be of interest to our customers.

Honeywell Organization WWW Address (URL)

Corporate http://www.honeywell.com

Industrial Measurement and Control http://www.honeywell.com/imc

Telephone

Contact us by telephone at the numbers listed below.

Organization Phone Number

United States and Canada Honeywell 1-800-423-9883 Tech. Support1-888-423-9883 Q&A Faxback

(TACFACS)1-800-525-7439 Service


5/86

Revision 1 HWIOPC Server User Manual v7/05

Table of Contents

Table of Contents ...........................................................................................................................v1 Preface .................................................................................................................................... 1

1.1 INTENDED AUDIENCE........................................................................................................ 11.2 PRODUCT SUPPORT ........................................................................................................... 11.3 PCREQUIREMENTS ........................................................................................................... 1

2 Int roduct ion ............................................................................................................................ 22.1 OVERVIEW ........................................................................................................................ 2

3 Working directory and Conf iguration files .......................................................................... 43.1 WORKING DIRECTORY ...................................................................................................... 43.2 CONFIGURATION FILES ..................................................................................................... 4

4 Instal lat ion .............................................................................................................................. 54.1 INSTALLATION PROCEDURE.............................................................................................. 54.2 MODIFY/REPAIR/UNINSTALL.......................................................................................... 12

5 HWIOPC Register ................................................................................................................. 135.1 CHECK WHETHERHWIOPCSERVER IS REGISTERED ..................................................... 145.2 NEW LICENSE REGISTRATION......................................................................................... 145.3 TRANSFERLICENSE FROM ONE MACHINE TO ANOTHER................................................ 16

6 Quick Start ............................................................................................................................ 196.1 PREREQUISITES ............................................................................................................... 196.2 CONSIDERATIONS............................................................................................................ 196.3 CONFIGURING OPCDATABASE (ADDRESS SPACE)USING OPCUTILITY...................... 19

6.3.1 Running the OPC Utility........................................................................................... 206.3.2 Starting the the OPC Server.................................................................................... 206.3.3 Uploading the existing configuration........................................................................ 216.3.4 Adding a Device Group............................................................................................ 216.3.5 Adding a Device....................................................................................................... 22

6.3.5.1 Device general page......................................................................................... 236.3.5.2 Controller Type page........................................................................................ 246.3.5.3 Connection page............................................................................................... 246.3.5.4 Communication page........................................................................................ 256.3.5.5 Tag page........................................................................................................... 25

6.3.6 Adding Tag Groups and Tags.................................................................................. 276.3.6.1 Importing Tags from HC900............................................................................. 286.3.6.2 Generating tag groups and tags automatically................................................. 316.3.6.3 Adding tag groups and tags manually.............................................................. 32

6.4 USING THE TEST OPCCLIENT ........................................................................................ 376.4.1 Running Test OPC Client........................................................................................ 376.4.2 Browsing the address space of the Server and adding items ................................. 386.4.3 Writing Values.......................................................................................................... 406.4.4 Saving Test Client File............................................................................................. 40

6.5 MONITORING................................................................................................................... 406.5.1 Monitor Device Tag.................................................................................................. 416.5.2 Monitor Client Item................................................................................................... 41

6.6 USING TAG EXPORT FILE ................................................................................................ 436.7 COPY/PASTE OPC TAG NAME ......................................................................................... 436.8 QUERYING OPCCLIENTS................................................................................................ 446.9 TROUBLESHOOTING ........................................................................................................ 45

6.9.1 Using System Tags.................................................................................................. 45


6/86

vi HWIOPC Server User Manual Revision 17/05

6.9.1.1 System tags...................................................................................................... 456.9.1.2 Browsing system tags....................................................................................... 45

6.9.2 Using Diagnosis....................................................................................................... 46

6.9.2.1 Diagnostics Record........................................................................................... 466.9.2.2 Diagnosis Result Types....................................................................................476.9.2.3 Start/Stop Diagnosis......................................................................................... 476.9.2.4 Save Diagnostics Record.................................................................................476.9.2.5 Clear Diagnostics Record................................................................................. 47

7 HWIOPC DCOM Configurat ion............................................................................................ 487.1 OVERVIEW ...................................................................................................................... 487.2 WIN2000SP4.................................................................................................................. 48

7.2.1 General Security Configuration................................................................................ 487.2.1.1 Automatic DCOM configuration........................................................................ 487.2.1.2 Manual DCOM configuration............................................................................ 50

7.2.2 Special Security Configuration................................................................................. 537.2.2.1 Default account................................................................................................. 53

7.2.2.2 Special accounts............................................................................................... 547.3 WINXPSP2..................................................................................................................... 557.3.1 Local Security Policy Setting................................................................................... 557.3.2 Internal Firewall Configuration................................................................................. 567.3.3 My computer Properties........................................................................................... 59

7.3.3.1 Run DCOMCNFG ............................................................................................. 597.3.3.2 DCOM Default Properties................................................................................. 607.3.3.3 Common DCOM Security................................................................................. 61

7.3.4 HWIOPC DCOM Properties.....................................................................................637.3.4.1 Automatically configure HWIOPC DCOM Properties....................................... 637.3.4.2 Manually configure HWIOPC DCOM Properties.............................................. 65

7.3.5 Special Security Configuration................................................................................. 697.3.5.1 Default account................................................................................................. 697.3.5.2 Special account................................................................................................ 69

8 Other Informat ion ................................................................................................................. 709 Defini tion List ....................................................................................................................... 71


7/86

PrefaceIntended Audience

Revision 1 HWIOPC Server User Manual 17/05

11 PPrreeffaaccee

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 OPCprotocol. The suite consists of an OPC Server, the core component, and other applications thatare 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 filesexported via HC Designer, version 3.0. This results in quick development of the OPC serverdatabase. HWIOPC allows the OPC Client to either browse the OPC server database (addressspace) for desired OPC tags or copy/paste the OPC tags into the OPC Client database if browsingcapability is not available in the client.

11..11 IInntteennddeedd AAuuddiieennccee

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

11..22 PPrroodduucctt SSuuppppoorrtt

The following products are supported:

HC900 C30, C50 single Ethernet connectionHC900 C70R single or redundant Ethernet connection

11..33 PPCC RReeqquuii rreemmeennttss

PC:

Pentium III, 1GHz, 256MB RAM (minimum)Pentium 4, 2GHz, 512MB RAM (recommended)

Operating System Support:

Windows 2000 Professional, Service Pack 4Windows XP Professional, Service Pack 2


8/86

IntroductionOverview

2 HWIOPC Server User Manual Revision 17/05

22 IInnttrroodduucctt iioonn

22..11 OOvveerrvviieeww

The HWIOPC suite includes the following components:

1. OPC ServerThis 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 compatiblewith 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 aclock image in the taskbar.

3). OPC Utility- an OPC utility that is used to:

import tags that are exported by HC Designer to the addressspace of the OPC Server

configure the address space of the OPC Server manually

configure the server using DTG (Digital Tag Generation) forcertain tag groups

query the information of the OPC clients connected with theOPC Server,

monitor the internal value of device tags and the real timevalue 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 ClientThe 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 andverify the address space configuration of the OPC Server, display syntax

structures, data types along with live data values and allow write operations toassist in setting up other PC applications.

3. HC900R DriverA library that provides connectivity to both redundant and non-redundant HC900 systems that are MODBUS/TCP slaves on an Ethernet network.

4. HTSLLoggerThe 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 filesunder the directory C:\HTSLLogger\.


9/86

IntroductionOverview


2). HTSLLogViewer- a tool that is used to display and classify log

messages in the log files recorded by the HWIOPC Server and thedevice driver.


10/86

Working directory and Configuration files


33 WWoorrkkiinngg ddii rreeccttoorryy aanndd CCoonnffiigguurraatt iioonn ffii lleess

33..11 WWoorrkkiinngg ddii rreeccttoorryy

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.

33..22 CCoonnffiigguurraatt iioonn FFii lleess

The OPC Server uses one device driver configuration file to save the device driver and devicegroups information. It provides two configuration files for each device.

The first is theDevice Configuration File in XML format, and the other a PointsConfiguration File in CSV format.All configuration files are stored under the relative directory \HTSL\data\, such as c:\ProgramFiles\HTSL\.

Device Driver Configuration FileIt contains the parameters for DLL ProgID and driver name.

The file name is DevicesConfig.xml.

Device Configuration FileIt contains the parameters for physical connection. For example, the file for the Ethernetport 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 andcontents through the OPC utility tools.

Points Configuration FileIt 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 thefollowing:

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 andcontents through OPC Utility.


11/86

Installation


44 IInnssttaall llaatt iioonn

44..11 IInnssttaall llaatt iioonn PPrroocceedduurree

Note:If the HWIOPC suite has been ins talled in your computer and has not been uninstalled,make sure two services named HTSLLogger and HWIOPC are stopped before starting thefollowing installation steps.

The HWIOPC CD will start the installation guide automatically after being inserted to CD-ROM, butif not, double click on the install program named Setup.exe. The installation guide will appear.


12/86

Installation


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

The license dialog box shown below will appear. ClickYes if you accept all the terms of thepreceding License Agreement.


13/86

Installation


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

The dialog box shown below will appear. ClickNext after choosing the components you want toinstall.


14/86

Installation


There are five components in this package:OPC Server: Files of OPC Server, OPC Utility, OPC Server Monitor, HTSL ProductRegister.

OPC Client: Files of OPC Client.OPC Custom Common Dll: Common Dll files for OPC DA Custom interfaces. If no OPCrelevant software has been installed on your computer, you must select this component. Ifyou are not sure, we recommend that you also select it.HC900R Driver: Files of Device driver for redundant and non-redundant HC 900controller 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. ClickNext.

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


15/86

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 clickRetry.If you dont want to replace the file or remove the file, you can check the box Dont display thismessage again and then clickIgnore.


16/86

Installation


After installing the components, if you dont install the component OPC Server, please go to Step11. 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 themessage box shown below and continue to configure DCOM permissions for the OPC Server thatcommunicates 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 windowand 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, theinstallation will add the EVERYONE, INTERACTIVE and SYSTEM groups to both the launchpermissions 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 thenext step.Click the button Cancel if you dont want to automatically set DCOM permissions.


17/86

Installation


The window shown below will appear. Click the buttonFinish. The installation is completedsuccessfully.

Open Services inControl Panel. Start the service named OpcEnum, and change thestartup 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 Registertoregister the OPC Server. Then, execute the next step, i.e. Step 13. Otherwise, if you dont installthe 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 pressingF1 or clicking the menuHelp->Contents on the main window of the OPC Utility.


18/86

Installation


44..22 MMooddii ffyy//RReeppaaii rr//UUnniinnssttaall ll

Note:

Before modify ing/repairing/uninstalling the HWIOPC suite, make sure thatOPCServerMonitorhas 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 ofSection 4.1.

A ReadOnly file causes the other. In this case, confirm that the action related to the file namedisplayed 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 someof them are common Dll files that are necessary to run programs relative to the OPC protocol ordeveloped with VC++.


19/86

HWIOPC Register


55 HHWWIIOOPPCC RReeggiisstteerr

To use the HWIOPC Server, you need to apply for license and register a license certificate per thelicense process first. The service HWIOPC will stop automatically after running for 4 hours as ademonstration version if its license is not registered. The service will need to be re-started after the4-hr timeout.

The HWIOPC License cannot be reused on multiple computers because each computer has itsunique license. But the license can be transferred from one machine to another when you haveregistered a license certificate for a particular machine and want the certificate to be moved toanother machine due to some circumstances.

The HWIOPC Server has two model types, Non-Redundant and Redundant. If the HWIOPCServer is registered as Non-Redundant, then the HWIOPC Server can only support HC900 C30and C50 controllers and cannot support HC900 C70R controllers. If the HWIOPC Server isregistered as Redundant, then the HWOPC Server can support HC900 C30, C50 and C70Rcontrollers. That is to say, if you purchase the HWIOPC Server - Redundant version, you willactually 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 isregistered and what is the current feature, how to execute a new license registration afterpurchasing the HWIOPC Server and how to transfer a license from one machine to another. Thetool named HTSL Product Registeris used for all of the license processes. You can launch thetool by clicking Start->HWIOPC->HWIOPC Register, the main window of the tool willappear as shown below,


20/86

HWIOPC Register


55..11 CChheecckk wwhheetthheerrHHWWIIOOPPCC SSeerrvveerr iiss rreeggiisstteerreedd

Do the following to check whether HWIOPC Server is registered,

1. Launch the tool HTSL Product Register.2. Click theGetLicenseInfo button on the tool.

If the HWIOPC Server has been registered, the edit box ofLicense Type will displayPermanent. The edit box ofFeatures will display Non-Redundant if you have purchasedthe Non-Redundant option or displayRedundant if you have purchased the Redundantoption. The edit box for the Reference Code File will display \ XXXX.cert.

Otherwise, if the HWIOPC Server has not been registered, then a message box will showas below,

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

55..22 NNeeww LLiicceennssee RReeggiisstt rraatt iioonn

You need to apply for a new license after you purchase the HWIOPC Server software. You will geta license certificate that can be installed on your PC, and then the HWIOPC Server will run as aregistered version.

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


21/86

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 theGenerate 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 .hid. For example, if the HWIOPC Server is installed in the directoryC:\Program Files\HTSL\, then the full path name for the HostID file generated will beC:\Program Files\HTSL\Server\.hid. Then close thetool.

4. Send the Voucher Number and the generated HostID file to the email [email protected] apply for a new license. The email subject should be NewLicense Application. The body of email should just have the Voucher ID and a copy of theHost ID file.

5. After one working day, you will receive a license certificate file from the above emailaddress. The license certificate file name should be Node 0.cert. Save the license certificate file to a local folder, such as d:\HC900 License\.

6. Launch the tool HTSL Product Registeragain.7. Click theBrowse button, an open file dialog will appear. Select the license certificate file

you received, such as d:\HC900 License\ Node 0.cert.Then click the Install button; the HWIOPC Server will be registered per the licensecertificate file.


22/86

HWIOPC Register


You can check whether the HWIOPC Server has been registered successfully with your selectedfeature 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.

55..33 TTrraannssffeerrLLiicceennssee ffrroomm OOnnee MMaacchhiinnee ttoo AAnnootthheerr

Transfer of license certificate happens when you have registered a license for a particular machineand want the certificate to be moved to another machine due to some circumstances. In such ascenario you can request for termination of the license on the former machine and request alicense on the new machine.

When the license certificate is terminated on a machine, it generates a termination file thatcontains sufficient information to validate whether the certificate is genuine or not. If the certificateis genuine, [email protected] 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, thenHWIOPC 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 daysafter 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.


23/86

HWIOPC Register


Steps to transfer the HWIOPC Server from one machine to another:

1. Launch the tool HTSL Product Registeron the machine where you have registered theHWIOPC Server.

2. Input the Voucher Number on the tool.3. Click theTerminate 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 (-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 firsttime that you are transferring the license, then the full path name of the termination file willbeC:\Program Files\HTSL\Server\ Node 0.term. If itis the second time that you transfer the license, then the full path name of the terminationfile will be C:\Program Files\HTSL\Server\-0 Node0.term.Then close the tool.

4. Install HWIOPC Server on the new machine to which you wish to transfer the HWIOPCServer.

5. Launch the tool HTSL Product Registeron 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 newmachine. Close the tool.


24/86

HWIOPC Register


7. Send the Voucher Number, the termination file generated in step 3, and the HostID filegenerated in the last step to the email address [email protected] apply for alicense 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 emailaddress. The license certificate file name should be -XNode 0.cert. Save the license certificate file to a local folder on the new machine, such asd:\HC900 License Transfer\.

9. Launch the tool HTSL Product Registeragain 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\-0Node 0.cert. Then click the Install button; the HWIOPC Server will be registered with thefeature in the license certificate file on the new machine.

You can check whether the HWIOPC Server has been registered successfully with your selectedfeature 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 thereceived license certificate file name. Otherwise, you will fail to transfer the HWIOPC Server fromone machine to another.


25/86

Quick Start


66 QQuuiicckk SSttaarrtt

66..11 PPrreerreeqquuiissii tteess

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 HWIOPCServer, you should have correctly set the DCOM permissions. Refer to HWIOPC DCOMConfiguration for how to configure DCOM permissions for the HWIOPC Server.

66..22 CCoonnssiiddeerraatt iioonnss

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 thatother tools, such as the OPC Utility and the OPC Test Client, cannot connect with it and functionproperly.

If you want to continue to use the HWIOPC Server after 4 hrs, you need to restart the serviceHWIOPC, 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.

66..33 CCoonnffiigguurriinngg OOPPCC DDaattaabbaassee ((AAddddrreessss SSppaaccee)) UUssiinngg OOPPCCUUtt ii ll ii ttyy

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 aDevices tree

structure. Basically, it consists of a Device Group (for one or more controllers), Device (such as anHC900 controller), Tag Group (such as for a P ID, Variables, Signal Tags, etc.) and Tag (item intag 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 (includingtag name). The maximum length for a full tag name (includes all levels) in the hierarchy space is255 characters (including separator symbol '.'). Therefore, the maximum name length of each levelstring is 24 characters. An example of a full OPC tag name for the above OPC serverconfiguration is:

HC900R_MBTCP.HC900.Variable.VAR006 (4 levels)


26/86

Quick Start


6.3.1 Running the OPC Utili ty

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 Start ing the the OPC Server

Do any of the following to start the service: Using OPC Utility

Click the button on the ToolBarto start the service.

Using Services consoleClick Start on the TaskBar, point to Settings, and then click on Control Panel.Double-click onAdminist rat ive Tools, and then double-click on Services. Right-click onthe service named "HWIOPC", and then click onStart.

Using OPCServer Monitor

Right-click on the OPCServer Monitor displayed as an icon on the taskbar, and thenclick on the popup menu item Start Service.

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


27/86

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 sameas the address space of the OPC Server. Any successful modification to the configuration on-linevia 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 OPCServer initialized during installation. You should delete this initial device group before you do yourown 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 commoncommunications 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 devicegroups in Devices Page, or go directly to Step 2.

2. Right-click on the device group or blank area in theDevices page, then click on thepopup menuAdd Device Group or from the Edit menu, selectDevice Group >Add.

3. A dialog box shown below that contains a combo box listing all device drivers willappear. Select a device driver, type the device group name, and then click on thebutton OK. The device driver of a device group cannot be changed once it is created.


28/86

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 menuAdd 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 23Controller Type Page, see page 24Connection Page, see page 24Communication Page, see page 25Tag Page, see page 25


29/86

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.


30/86

Quick Start


6.3.5.2 Contro ller 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 Connect ion 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).


31/86

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 nameentered has not been used by another device; otherwise, the tags of the other device that also usethe file name will be lost.

Register format: this is for indicating the order for transmitting floating point registers (2consecutive). Refer to the on-line Help of the HC Designer. FP_B is the default used forHoneywell products such as HC900.

Separate Symbol: delimiter used to separate function block name and tag name in exportfile. 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 betweenthe physical device and OPC Server PC, you can adjust it according to the needs andperformance of the physical device. After setting a scan rate for the device, all tags ofthe device will adopt the same scan rate. Correspondingly, the edit box for Scan Rate inthe tag properties dialog box will be grayed and does not allow you to change its valule.


32/86

Quick Start


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


33/86

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 theaddress space; however, the Import Tags method is recommended to minimize errors. Theselections for dealing with the import allow the original address space to be retained and onlyallow additions for future edits to the configuration. Edits to the address space made be doneon-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 taglabels and descriptions, it is the most efficient of the three methods. You should start withthis method and use it exclusively for edits to match your HC900 configuration as much aspossible.

Generating tag groups and tags automatically:This method would be used principally for simple applications to support testing aninterface to a controller without importing its tags. It should not be used after the tagimport method since it will overwrite the address space. Tag groups and tags will begenerated for a number of control loops, Variables, Signal Tags, and SetpointProgrammers 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 forVariables and Tags is defaulted to Float. You will need to consult the Tag Informationreport from HC Designer to determine the assignment of specific data types to a Variableor Signal Tag number. The number of groups and tags generated may not be the sameas 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 ofModbus Holding Registers supported by Function Code 3 for Read and Function Code16 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 thecontroller, the Access Right is known and will be grayed out. Because of the low efficiencyof the method, we recommend that you use this method only for small modifications to theHWIOPC server address space. .


34/86

Quick Start


6.3.6.1 Import ing 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 fileexported by HC Designer 3.0. The file format should be CSV (Comma delimited) and unalteredonce 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 ExportReport 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 Tagsreport 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 isentered 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 ModbusRegisters 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 groupand 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 isa 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 buttonOpen. 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 tagname duplication and Modbus address duplication that may be encountered duringimporting tags. You can use the defaults for initial tag import. Click on the button OK toimport tags from the file selected. Click on the button Cancel if you don't want tocontinue.


35/86

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 theDevice name as shown in the table below (depending on file content imported). Allparameters 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 andVariables to Boolean.

Tag Group Sub-Group Tag Names Group Content

PID Loop Tag Name loop parameters All control loop parametersSignal Tag (none) Signal Tags Defined Signal Tags, Float &BoolVariable (none) Variables Defined Variables, Float &Bool

SetPointParam SPP Tag Name SPP parameters General programmer valuesSetPointSegment SPP Tag Name SPP parameters All Ramp/Soak Segment valuesScheduler SPS Tag Name SPS parameters General scheduler valuesSchedulerSegment SPS Tag Name SPS parameters Segment values Segs 1-50SequenceParam SEQ Tag Name SEQ parameters General sequencer valuesSequenceStep SEQ Tag Name SEQ parameters Step values Steps1-64SequenceState SEQ Tag Name SEQ parameters State number for each stepAlternator ALT Tag Name ALT parameters All Alternator valuesStage STG Tag Name STG parameters All Stage valuesDeviceControl DC Tag Name DC parameters All Device Control valuesRamp RAMP Tag Name Ramp parameters All Ramp valuesHand-Off-Auto HOA Tag Name HOA parameters All HOA valuesUser-Defined Variable Tag Name

Signal Tag NameVariablesSignal Tags

All defined with data typesAll defined with data types


36/86

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 tagsare ignored.

For cases, where the second option that deals with Tag name duplication is selected, thetag in the HCD export file, whose name already exists in the address space of the OPCServer, will be renamed automatically by the OPC Server based on the following namingconventions:

a. Expand an attachment at the end of the tag name. The attachment includes anunderscore as a separator and the Modbus address for the tag. For example: for thetag "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, theOPC Server will use the tag information in the HCD export file to overwrite the current taginformation.When importing a tag export file, the OPC server will only be compatible with an HC Designer 3.0export and will not support an export from previous versions of the HC Designer tools.


37/86

Quick Start


6.3.6.2 Generating tag groups and tags automatically

DTG is an acronym for Device TagGeneration. 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 fortest 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, andthen 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 tobe 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 thedevice will be cleared during the operation. If you want to continue, click on the buttonYes, or else click on the button No.If you select to continue in the above step, a dialog box as shown below will appear andlet you to enter the number of tag groups and tags desired.

Note: You will need to consult the Tag Information Report and the Summary FunctionBlock report in HC Designer to determine the actual tag, variable, loop, and setpointprogrammer identification since this method will only list by number. These reports willalso be needed to determine the data type for the signal tags and variables (analog ordigital). You will need to apply the correct data type.


38/86

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 maximumnumber of segments for each programmer to generate tags related to a segment

6.3.6.3 Adding tag groups and tags manually

66..33..66..33..11 AAddddiinngg aa ttaagg ggrroouuppFollow 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 menuAdd Tag Group .3. A dialog box shown below will appear. Select a group name then click on the buttonOK.

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 whenadding tags only, simply add tags to the UTG tag group.


39/86

Quick Start



40/86

Quick Start


66..33..66..33..22 AAddddiinngg aa ttaaggDo 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 menuAdd 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, isnot changeable. For Modbus registers outside of the documented registeraddresses for HC900, the access right can be changed.


41/86

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 willretrieve data of the tag from the physical device.Depending on the performance of its physical device and the connection between thedevice and OPC Server PC, you can adjust it according to the needs and performance ofthe 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 forcea scan rate to these different kinds of physical devices.

The scan rate of the tag configured here has no relationship with RevisedUpdateRate ofan OPC group. When an OPC group is being created, the OPC Server has no way toknow what tags will be added to the group, thus the OPC Server can only compare therequested update rate of the OPC group with the base rate. If the requested update rate isfaster 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 canconnect with a same tag, and those OPC groups request different update rates. If theOPC Server retrieves data from the physical device for each group using different scanrates, it will largely increase the communication burden. To avoid the low efficiency, theOPC Server will periodically retrieve data from the physical device for a tag using its ownscan rate set here.Note:For the device driver of redundant HC900 controllers system, you can only set a scan ratefor 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 anddoes not allow you to change its valule.


42/86


43/86

Quick Start


66..44 UUssiinngg tthhee TTeesstt OOPPCC CCll iieenntt

A Win32 application, serving as an OPC client, is used to verify the operation of the HWIOPCServer. It can display syntax structures, data types along with live data values, and allow writeoperations to assist in setting up other PC applications. It will be installed on your computer if thecomponent 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,


44/86

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 clickNew Server onthepopup menu.

2. A dialog box listing all the OPC Servers in the local PC will appear. SelectHWI.OPCServer.V1 (HWIOPCServer) in the OPC Server lists. If the HWIOPC Server ison a remote PC, enter the IP address where the OPC Server is running in the RemoteMachine entry field. Leave the entry field empty if the OPC Server is running on thelocal machine, then click on the button OK.

3. Select and right-click on the server just created, and then clickAddGroup onthe popupmenu.

4. The dialog box shown below will appear. Enter the relative properties and click on thebutton 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.


45/86

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.


46/86

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 thenclick on the button OK. The new value will be written to the OPC Server and can beobserved 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 forfuture testing to avoid re-entering group items.

66..55 MMoonnii ttoorriinngg

One of the key features of the OPC Utility is monitoring the internal value of device tags of theOPC Server or real time value of the items of the OPC clients.

Start Monitorin the Operation Log means that the utility will be in the Monitor mode.Stop Monitorin 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 staticproperties will appear in Device Tags list or Client Items list, but its dynamic properties will notappear unless Monitor is started.

After Monitor is started, the OPC utility will refresh the dynamic properties of device tags or clientitems from the OPC Server periodically based on a 1000ms rate until Monitor is stopped. This canaffect the communications performance of the OPC Server.

You can configure the address space of the OPC Server in either mode - monitoring or notmonitoring.


47/86

Quick Start


6.5.1 Moni tor Device Tag

The OPC utility can be used to monitor the internal value of device tags in the address space ofthe OPC Server.Do the following to monitor the internal value of a device tag:

1. Start the service HWIOPC. Refer toSection 6.3.2 for instructions.2. Upload the current configuration of the OPC Server. Refer toSection 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 bedisplayed 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 OPCitem 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 taggroup Variable, the value for these tags is shown as blank, and the qualities of these tags areBAD 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 clientsconnected to the OPC Server.Do the following to monitor the real time value of an OPC item:

1. Start the service HWIOPC. Refer toSection 6.3.2 for instructions.2. Refresh the information of all OPC clients connected to the OPC Server. Refer toSection

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.4. Start Monitor by clicking on the button on the ToolBar. It will display the real time

value, quality and timestamp of the client items. Click on the same button again to stopMonitor.


48/86

Quick Start



49/86

Quick Start


66..66 UUssiinngg TTaagg EExxppoorrtt ffii llee

Using the OPC Utility, you can export all tag information in the address space of the OPC Serverto a CSV file. The contents of the file include full tag name, address, data type, access right, scanrate 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 buttonStart if you want to export, or click on the button Cancel if you don't want to continue theoperation.

3. After selecting the separated char in step 2, another dialog box titledOpen will pop up tolet you enter a file name. Enter the file name, and click on the button Save to continue, orelse 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.

66..77 CCooppyy//PPaassttee OOPPCC ttaagg nnaammee

This function enables you to add tags from the HWIOPC server to the OPC Client if the client doesnot 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 copiedto 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


50/86

Quick Start


66..88 QQuueerryyiinngg OOPPCC CCll iieennttss

Using the OPC utility, you can observe all OPC clients informationconnecting with the HWIOPCServer, including their groups and static properties of items. Considering the performance of theOPC Server, the utility will not refresh the information of clients automatically. Therefore, you needto 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 thedetails of how to monitor.

There are two ways to refresh the information of clients:

1. Upload both devices and clients information by clicking on the button on the ToolBar.2. Refresh clients information by right-clicking at theClients tab and clicking on the popup

menu Refresh. See the figure below.


51/86

Quick Start


66..99 TTrroouubblleesshhoooott iinngg

6.9.1 Using System Tags

To monitor/diagnose device and communication status for each device, especially for theredundant 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 cannotconfigure 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 thecreation of all other device tags. All of the nine system tags are created under the tag groupnamed_System. That means, each device must have a tag group named_System, andunder 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 atleast on one port, otherwise its value is 0; device inactive or communications bad on allports

_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, andits 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.


52/86

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.

NoteAfter 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 OPCServer, especially while diagnosing the events relevant to data refresh, such asIOPCDataCallback::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 Serverany 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 rowafter 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 theevent.


53/86

Quick Start


6.9.2.2 Diagnosis Result Types

There are three result types in theDiagnostics list: Information

It indicates that the event has executed successfully with no error or warning.

WarningIt indicates that the event has executed successfully with minor errors or warnings.

ErrorIt 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 itemTools->Diagnosis->Start. After Diagnosis is started successfully, the button will change todisabled.

To stop Diagnosis, click on the button on the ToolBar, or click on the menu itemTools->Diagnosis->Stop. After Diagnosis is stopped successfully, the button will change todisabled.

6.9.2.4 Save Diagnost ics Record

This function is available only when there are one or multiple records inDiagnostics list, the OPCutility is initialized, and Diagnosis is stopped.

To save the diagnostics records, right-click atDiagnostics list, then click on the popup menu itemSave. Or, click on the menu Tools->Diagnosis->Save.

6.9.2.5 Clear Diagnost ics 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 atDiagnostics list, then click on the popupmenu itemClear.


54/86

HWIOPC DCOM Configuration


77 HHWWIIOOPPCC DDCCOOMM CCoonnffiigguurraatt iioonn

77..11 OOvveerrvviieeww

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 ofconfiguration 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 theaccount used by the OPC client, and grant the account access and launch permission for the OPCServer.

On the computer running the OPC Client, you must specify the location of the OPC Server that willbe accessed.

So, if you want to allow OPC clients to connect to the HWIOPC Server across the network, theHWIOPC DCOM configuration must be done first.

The DCOM configuration is different on WinXP SP2 versus Win2000 SP4 because WinXP SP2improves the shielding of WinXP from the network through RPC, DCOM communication, securitypolicy, and the internal Windows firewall enhancement.

77..22 WWiinn22000000 SSPP44

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

7.2.1 General Security Configuration

There are two approaches to accomplish the general security configuration: Automatic DCOMconfiguration 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 atthe last step of the installation.

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


55/86



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 needhigher-level security, its better to manually set the DCOM configuration using DCOMCNFG.EXE.


56/86



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 permissionsinstead of the local account HWIOPCMngr, so that all accounts on the computer are enabled toaccess 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.

77..22..11..22..11 RRuunn DDCCOOMMCCNNFFGGYou 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 usuallysimpler to install and configure the server as a user with local administrative rights.

77..22..11..22..22 DDCCOOMM DDeeffaauull tt PPrrooppeerrtt iieess

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 themachine is available to others via DCOM. In general, the other settings need not to be changed.


57/86



77..22..11..22..33 SSeelleecctt tthhee aappppll iiccaatt iioonn HHWWIIOOPPCCSelect HWIOPC from the application list, and then click on the button Properties.

77..22..11..22..44 SSeeccuurrii ttyy pprrooppeerrtt iieess PPaaggeeClick the security tab from the HWIOPC properties dialog box shown below.

77..22..11..22..55 AAdddd AAcccceessss ppeerrmmiissssiioonnssThe access permission contains an Access Control List of principles that are allowed to interactwith objects supplied by a server. To add access permissions to an account:


58/86



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

2. Click on the button Add, then all domains and groups will appear as shown in the dialogbox 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 accountHWIOPCMngr, and click on the button Add.


59/86



5. Click on the button OK to finish the Access permission setting for the HWIOPC Server.

77..22..11..22..66 AAdddd LLaauunncchh ppeerrmmiissssiioonnssThe launch permission contains an Access Control List of principles that are allowed to start up aserver 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 launchpermission and click on the button Edit in the HWIOPC property dialog box, and then the stepsare 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 mayuse the default account or a special account.

Default account means that the OPC client uses the current logged on user of the computer thatthe 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 remotecomputer.

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 mustensure that there is an identical user with the same password as the current logged-on user of theOPC client computer existing in the computer running HWIOPC Server, and the user of the OPCServer 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 username and password, such as HWIOPCMngr. Make sure the account is enabled.


60/86



2. If you have automatically set DCOM permissions for the HWIOPC Server duringinstallation, then go directly to next step. Otherwise, you need to grant the above accountor Everyone with access and launch permissions for HWIOPC. Refer toAdd 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 OPCClient 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 OPCserver with a fixed account named mngr. To allow the OPC clients of these software packages toaccess 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 accountmust be identical with the user used by the OPC client. Make sure the account isenabled.

2. If you have automatically set DCOM permissions for the HWIOPC Server duringinstallation, then go directly to the next step. Otherwise, you need to grant the aboveaccount or Everyone with access and launch permissions for the HWIOPC. Refer toAdd 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 theOPC Client can connect to the HWIOPC Server.


61/86



77..33 WWiinnXXPP SSPP22

WinXP SP2 includes many changes and security enhancements versus Win2000, three of whichdirectly impact OPC communication via the network. First, the local account access via a networkwill be authenticated as Guest by default. Second, the internal firewall has been enhanced and isturned 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 Secur ity Policy Setting

You need to change local security policy setting on the computer on which the HWIOPC Server isrunning.

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 itemNetwork access: Sharing and security model for local accounts in

the right policy list and change its setting to Classic local users authenticate asthemselves.

Refer to the figure shown below.


62/86



7.3.2 Internal Firewall Configuration

If the OPC client application is also running on XP SP2, you need to change the internal firewallconfiguration of both the computer that the HWIOPC Server is running on and the computer thatthe OPC client application is running on, if separate.

The SP2 internal firewall is turned on by default. If the machine is sufficiently protected behind acorporate firewall, then the internal firewall could be turned off permanently.

When the internal firewall is turned off, the configuration for internal firewalls introduced in thissection can be ignored.

Otherwise, you need to follow the steps below to add programs and port to the exceptions ofwindows firewall.

1. Open Control Panel->Network and Internet Connections->WindowsFirewall. The following dialog box will appear

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


63/86



3. Click the tabExceptions, the page shown below will appear,

4. Click the buttonAdd Program. A dialog box titled Add a Program will appear asshown 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 findHWIOPC.exe under the installed directory.

The default directory is C:\Program Files\HTSL\server\HWIOPC.exe.

Click OK to add HWIOPC to Exceptions page.


64/86



Similarly, addMicrosoft Management Console (used by the DCOM configurationutility) and all other OPC client applications that will connect to the remote OPC Servervia DCOM to the Exceptions page, such as OPC Client(VC).

The file name ofMicrosoft Management Console is mmc.exe under the systemdirectory. 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, andthen click OK.


65/86



7.3.3 My computer Properties

You need to configure common DCOM security on the computer on which the HWIOPC Server isrunning.

7.3.3.

Documents

OPC User Manual en.pdf