OPC Historical Data Access 1.20 Client communication protocol

Supported device types and versions
Communication line configuration
Communication station configuration
I/O tag configuration
Setting of the right strategy for data reading
DCOM configuration to connect to OPC remote server
Errors and problems
Literature
Changes and modifications
Document revisions

Supported device types and versions

The protocol supports a client side of communication with OPC (OLE for Process Control) HDA (Historical Data Access) servers according to specifications OPC HDA ver. 1.20.

Communication line configuration

Communication line category: OPC Client.

OPC parameters:

• OPC Host: It is required only for "Remote" access, i.e. it is defined only for OPC server type "Remote" (string max. 50 characters). OPC HDA Server must be installed on a computer. You can se the names according to UNC (Universal Naming Convention) (e.g. "\\server" or "server"), DNS domain names (e.g. "domain.com", "example.company.com") or IP address ("196.54.23.113").
• Backup Host: It is required only for "Remote" access. It is a backup OPC host. If it is defined, D2000 KOM tries to establish a communication alternately with OPC Host and Backup Host after failure of communication.
• OPC Server: A name (ProgID) of OPC server (string max. 50 characters).
• Server Type: "InProc", "Local" or "Remote".

Communication station configuration

Communication protocol: OPC Historical Data Access 1.20.

This communication protocol does not require any address parameters for a station.

Station protocol parameters

You may configure the following station parameters:

Table 1

I/O tag configuration

I/O tag types: Ai, Ci, Di, Qi,  TiA, TiR, TxtI.

The address of I/O tag requires to set "OPC Item ID" (string max. 200 characters).

Other required parameters ("OPC HDA Item Parameters") are:

• The selection between "Raw" and "Processed" type of value which is read.
• If you choose "Processed", then set also "Aggregate".
• The option "Async Advise" to permit the asynchronous continuous data acquisition.

Setting of the right strategy for data reading

OPC Historical Data Access is a specification that enables to read the historical data - either "raw" or "processed". Data may be read by the synchronous or asynchronous callings. The asynchronous interface enables also "advise" of required data, i.e. a periodical (see the parameter "Update Interval") sending of the current values from OPC HDA Server by the  asynchronous call-back in a client - KOM process. The only required interface, according to specification of OPC HDA, is "SyncRead" for reading of "raw" data synchronously.

In D2000 KOM Process the protocol OPC HDA is implemented in the way that enables as effective as possible reading of archive data, including the updating of the last values, so that it avoids to combine "OPC Historical Access" protocol with "OPC Data Access" one. The tell command GETOLDVAL enables to call the reading of historical data in any time interval. The obtained data are saved to D2000 Archiv if the primary archive value was used for archiving of the particular I/O tag.

The current data may be acquired in two ways:

1. Minimalist:
   It uses only the synchronous interface "SyncRead". According to the setting of station time parameters, the functions "ReadRaw" and "ReadProcessed" are called periodically. The required interval of values starts from the time of last valid value up to current time. If several values have been received in given interval, the last value with the latest time stamp is considered to be a current value. The other values are sent as "old" values to the server and are stored to the D2000 Archiv.
2. Advise:
   It uses the functions of asynchronous interface "AsyncRead", "AdviseRaw" and "AdviseProcessed". OPC HDA Server sends the last valid data of "raw" or "processed" items in the period which is defined in the parameter "Update Interval". If any new value is not in the defined interval, OPC HDA Server returns the flag of quality "No Data".

The parameter "Async Mode" enables to set a fully asynchronous mode, which uses only "AsyncRead" interface. However, the asynchronous mode has some limitations that is why we do not recommend it in these situations:

• When reading of "raw" data asynchronously, a repeated reading of data that were not in one call is not supported (the flag OPC_S_MOREDATA is returned).
• In asynchronous mode, there is not resolved the right timing of finishing the transaction of tell command GETOLDVAL. It causes an ineffective saving of received values by D2000 Archiv.

The protocol OPC Historical Data Access does not support the data writing (the interfaces "SyncUpdate" and "ReadUpdate"). Also the interfaces "SyncAnnotations", "AsyncAnnotations", "Browser" and "Playback" are not supported.

DCOM configuration to connect to OPC remote server

Remote browsing/local registration of OPC Server

Since the version 7.01.020 rel. 055 and higher D2000 KOM Process supports the acquisition of GUID OPC Servers from ProgID which is placed on remote desktops via DCOM interface with the help of utility OPCENUM (remote browsing). If the utility/windows service OPCENUM has been installed on remote OPC server and the level of access rights enables a remote browsing, the local registration of OPC server is not necessary on the client side. The utility OPCENUM is a part of package "OPC Core Components Redistributable". You can find it on http://www.opcfoundation.org/, or in OPC Server installation .

The registration of OPC Server is not necessary on the OPC client side (D2000 KOM). However, if you decide to register it, you can use one of these two ways:

1. Some of the OPC Servers are supplied with a setup program to support the connection of OPC clients of "third parts" to the remote OPC Server. These programs are named for example "OPC Server Connect". After their installing, OPC Server (its ProgID) occurs in the list of OPC Servers on the clients PC. D2000 OPC Client will use this information only for getting of CLSID from ProgID (see the communication line configuration). The registered OPC Server, however, cannot be operated on the client-side.
2. Manual registration of OPC Server on the client side. Follow these steps:
   
   
   • Copy OPC Server (.exe file + necessary .dll files) into the auxiliary directory on the client PC.
   • Start a command line in this directory.
   • Register OPC Server. If OPC Server is named e.g. "OPCSERVER.EXE" on the disk, then write the command: "OPCSERVER.EXE /regserver" and press ENTER.
   • Delete the auxiliary directory.

Always read the instructions for installation OPC Server and check your steps with those stated in the manual.

Setting of access rights

The connection to the remote OPC Server is subject to the access right control of Windows. From this reason, the same user (together with the password) must be created on both the computer. On the OPC client side the user must be logged. On the OPC Server, the user must have some rights therefore follow these instructions:

• Start the program "DCOMCNFG" in the command line on computer with OPC Server. Check, if DCOM is enabled - the option "Enable Distributed COM on this computer".
• Find OPC Server in the list and open the "Properties" dialog window. Open tab "Security".
• Switch "Launch Permissions" to "Customize" and click on the button "Edit...".
• Check the particular user in the list or add him to it.
• Do the same for "Access Permissions".

Wrong setting of the access rights will probably cause an error (see the chapter "COM/OPC error dump"):

ERROR: ServerProgID caused COM/OPC error 80070005H on CoCreateInstanceEx(CLSCTX_REMOTE_SERVER), Error string : Access is denied.

Track records in the system Event Viewer.

You can avoid this problem, if you add a group "Everyone" to "Launch Permissions" and "Access Permissions". To ensure that the OPC Server will be started under the particular user account (and no under "SYSTEM account"), open "Identity" tab and fill the data for "This user". In this case, you cannot consider OPC Server to be a safe.

OPC Client (D2000 KOM) is not allowed to be started as "Windows service" with parameters "/X1" or "/X2", because then it does not work under the logged on user but under  "SYSTEM account". An authentication of the access rights by OPC Server will fail. Use a start parameter "/X4".

Read the instructions to OPC Server again and keep the producer recommendations.

For the user of WindowsXP (or higher) with SP2 we recommend to change the parameter "Network access: Let Everyone permissions apply to anonymous users" to "Enabled" in the settings "Local Security Policy/Security Options".

Errors and problems

The error messages, mentioned below, may occur during the start or communication. It is recommended to activate the monitoring of communication in the configuration of line for easier identification of problem. You can choose it from these levels:

• Monitor (at least)
• Monitor & Disk (recommended)
• Disk (recommended)

When you set "Monitor & Disk" or "Disk", the file "line_name.LOG" occurs in the subdirectory "\TRACE" in application directory on the computer with the running communication process. This file contains all the debug and error messages.

COM/OPC error dump

The error messages mentioned in the chapter "Errors and problems" are generated in a higher level of OPC client. The most of the mentioned errors will be described on COM/OPC level. The format of these error messages is as follows:

WARNING/ERROR: ServerProgID caused COM/OPC error ErrorCodeHexadecimal on CallDescription, Error string : ErrorDescription

Example:

ERROR: Matrikon.OPC.Simulation.1 caused COM/OPC error C0040008H on IOPCHDA_Server::ValidateItemIDs('ItemID'), Error string : OPC_E_INVALIDITEMID The item definition doesn't conform to the server's syntax.

These error messages are important for an analyzes of problem. If any problems occur, they will be required by a technical support of Ipesoft company.

Literature

The documents OPC Foundation may be found on http://www.opcfoundation.org/.

• OPC FOUNDATION, Historical Data Access Specification, Version 1.20, December 10, 2003.
• OPC FOUNDATION, OPC Common Definitions and Interfaces, Version 1.0, October 27, 1998.
• OPC FOUNDATION, Using OPC via DCOM with Microsoft Windows XP Service Pack 2, (C) 2004 OPC Foundation Inc.

Other:

• OPC DCOM White Paper, Richard C. Harrison, Intellution Inc. © Intellution Inc. 1998

Changes and modifications

• October 15, 2007 - document creating

Document revision

• Ver. 1.0 – October 15, 2007