OPC Server Support

GainSeeker SPC supports OPC Servers.  Hertzler Systems is a member of the OPC Foundation. Several new template commands have been added to make this support possible.  GainSeeker SPC is the OPC client (the client requests data, the server provides data).  GainSeeker SPC talks to various OPC servers.

The OPC servers typically talk to hardware devices such as PLCs. Thus, the OPC Servers function as both a server (to OPC clients) and client (when asking the PLC for data). The OPC Servers contain groups of tags, or items.  

Each item contains a value and a quality (e.g. the value is good or bad).  Each item also contains a time stamp. It is recommended that you use the local workstation's clock for date/time information.  Some servers do provide a tag containing the date and time, or you can set up your own tag with the clock information if you want to get it from the server instead of the client.

OPC Support is available through the GainSeeker OPC Connectivity Pack.  If you do not have this connectivity pack installed, you will receive a warning when creating or running a template that uses the OPC commands.

If you want to purchase or want more information about the GainSeeker OPC Connectivity Pack, contact the Hertzler Systems Account Management team.

Receive Mode

There are two options for retrieving data from an OPC Server.  Setting the receive mode lets you pick between the two options.  The first is subscription mode ( Y); the second is synchronous mode ( N).  Following are descriptions of when you might use each of the modes:

When to use subscription mode (receive mode = " Y")

Use the subscription mode when you want to poll OPC items on a frequent basis.  The subscription read method allows your client application to remain responsive because the client isn't polling the server and waiting for data to come back.  Instead, the server is doing the work.  The OPC Server can look at all of the items that have been requested of it and group them together by update rate, proximity of memory addresses, etc. to optimize how it polls the PLC to satisfy subscription requests.  Thus, the OPC Server can manage its priorities to provide optimal performance versus being constantly told what to do by the client, which is what happens with synchronous reads.  When many OPC clients will be communicating simultaneously, the importance of using subscription reads grows.  It is even more important if the PLC network or its protocol is generally slow to begin with.  If you need to have data polled in the PLC or field device at a fixed rate (e.g. 500ms), but you doubt the data will change often, subscription reads are the best use of overall computer, computer network, and PLC network resources.

When you use the subscription mode you should use the OPC_ReceiveValue and OPC_ReceiveQuality commands.  You may set up a channel for subscription mode and still use the OPC_TriggerValue command, but this creates unnecessary overhead.

When to use synchronous mode (receive mode = " N")

Use the synchronous mode when you need to read OPC items on demand, and you only want to read the item a finite number of times, e.g. when a user clicks on a button.  Use it when you want to read an OPC item's value NOW and not take other steps until you are sure the read is done.

When you use the synchronous mode you should use the OPC_TriggerValue and OPC_TriggerQuality commands.

List of known compatible OPC Servers

Following is a list of OPC Servers and their PROGIDs and CLSIDs.  You will need to use either the PROGID or the CLSID when connecting to an OPC Server with the OPC_CONNECT command.  This is a list of the OPC Servers that have been tested with GainSeeker SPC.  There are many other OPC Servers that will be compatible with GainSeeker SPC.  In fact, all OPC Servers should be compatible.  If your OPC Server is not on the list, use the OPC Server browser to test it.  See Using the OPC Server Browser for details.

Even if your OPC Server is in the list, you should check the CLSID with the OPC Server Browser to verify that it is correct.  You should also browse the items (tags) to verify the names.  Remember, most item names are case-sensitive.

Using the OPC Server Browser

You can use the OPC Server Browser to test compatibility of your server with GainSeeker SPC.  To access the browser, pick the Browser utility menu item off the OPC Server menu in the Designer module.

From the browser you can either enter the name of the OPC Server in the Remote host name field or browse for your server by clicking the Browse button.

Once you have selected your server, click the Connect button to begin communicating with it.  The CLSID displayed is the one you will need to use in the OPC_Connect command.

Once connected, you may browse for the Item IDs.  With an Item ID selected, you can read and write data to the item with the Trigger and Write buttons.

OPC and DCOM

If you want to access an OPC Server on a remote computer, you must configure DCOM (Distributed COM) correctly on both the client and server machines.  The instructions for doing this are listed below.  For a more detailed description, visit the OPC Data Client - Custom Client Development website

Communicating across networks using DCOM

GainSeeker SPC's OPC interface allows you to communicate across networks using Windows NT's Distributed Component Object Model ( DCOM).  Before you can use GainSeeker with DCOM, you must use DCOM Configuration to set application properties, such as security and location.  On the computer running GainSeeker SPC, you must specify the location of the OPC server application (the application which responds to requests from SPC) that will be accessed or started.  For the OPC server application, you must specify the user account that will have permission to access or start the application, and the user accounts that will be used to run the application.

Configuring GainSeeker to use DCOM

Install GainSeeker on one PC (the client PC) and the OPC server on another (the server PC).  

Configure the server PC as follows:

1. In the Windows Start menu, select Run..., type in dcomcnfg and click on the "OK" button.  This starts the Distributed COM Configuration Properties application.  (For Windows XP, now select Component Services, Computer, and then select your computer.  Next, right click on your computer's icon and select Properties from the menu.)

2.  In the "Default Properties" tab:

   1. Select "Enable Distributed COM on this computer."

   2. Set the "Default Authentication Level" to "Connect."

   3. Set the Impersonation Level to Identify (default)

3. In the "Default Protocols" tab:

   1. Make sure that "Connection-oriented TCP/IP" is in the list.

4. In the "Default Security" tab (for Windows XP, select " COM Security"), for both "Access Permissions" and "Default Permissions":

   1. Click on "Edit Default"

   2. In the "Registry Value Permissions" dialog, click on "Add...".

   3. Select Everyone (or the appropriate subset of users) and click on Add.

   4. Select "SYSTEM" and click on "Add."

   5. Click on "OK" to return to the "Registry Value Permissions" dialog

   6. Click on "OK" to return to the "Distributed COM Configuration Properties" application

5. In the Applications tab, select the server you want to use (e.g. "Software Toolbox OPC Power Server") and click on the "Properties" button.  (For Windows XP, select your computer, then select DCOM config, then select the correct application and right-click on it to get to the "Properties" menu item.)

6. In the "(OPC Server name) Properties" dialog box:

   1. In the "Security" tab, select "Use default access permissions" and "Use default launch permissions".

   2. Select "Use custom configuration permissions" but do not edit the settings.

   3. In the "Identity" tab:  Select "The interactive user."  (That is, the user who is currently logged on to the computer.)

   4. In the "General" tab:  Set the "Authentication Level" to "Default".

   5. In the "Location" tab:  Check only "Run application on this computer".

7. If you want to browse from remote computers for OPC Servers, follow these steps.  In the Applications tab, select " OPCEnum" (or "OPC ServerList Class" on some computers) and click on the "Properties" button.  In the " OPCEnum Properties" dialog box:

   1. In the "Security" tab, select "Use default access permissions" and "Use default launch permissions".

   2. Select "Use custom configuration permissions" but do not edit the settings.

   3. In the "Identity" tab:  Select "The interactive user."  (That is, the user who is currently logged on to the computer.)

   4. In the "General" tab:  Set the "Authentication Level" to "Default".

   5. In the "Location" tab:  Check only "Run application on this computer".

8. Start the OPC server.

Configure the client PC as follows:

1. In the Windows Start menu, select Run..., type in dcomcnfg and click on the "OK" button.  This starts the Distributed COM Configuration Properties application.  (For Windows XP, now select Component Services, Computer, and then select your computer.  Next, right click on your computer and select Properties from the menu.)

2. In the "Default Properties" tab:

   1. Select "Enable Distributed COM on this computer."

   2. Set the "Default Authentication Level" to "Connect."

   3. Set the "Impersonation Level" to "Identify."  (This is the default setting.)

3. In the "Default Protocols" tab make sure that "Connection-oriented TCP/IP" is in the list.

4. In the "Default Security" tab (for Windows XP, select "Default COM Security"), for both "Default Access Permissions" and "Default Launch Permissions":

   1. Click on "Edit Default...".

   2. In the "Registry Value Permissions" dialog, click on "Add...".

   3. Select "Everyone" (or the appropriate subset of users) and click on "Add."

   4. Select "INTERACTIVE" and click on "Add."

   5. Select "SYSTEM" and click on "Add."

   6. Click on "OK" to return to the "Registry Value Permissions" dialog.

   7. Click on "OK" to return to the "Distributed COM Configuration Properties" application.

Things to keep in mind when using the DCOM Configuration application:

• If you change Access or Launch Permissions on the client side, you will need to restart your client side application.

• Likewise, if you change Access or Launch Permissons on the OPC server side either through the Default Security tab or from the Applications tab, you will need to restart the server side application for the changes to take effect.

• If you change anything on the Default Properties or Default Protocols tab, we recommend you reboot the computer before assessing if the changes took effect.

• Once you get your DCOM Configuration settings right, you should not have to change them again.

• Document your settings carefully, make screenshots if you want and paste them into a Word document.

• Proper and organized documentation of how you have your machine setup can be a lifesaver if you have to reload a machine in an emergency (e.g. drive failure, hardware failure, etc).

Files needed for OPC support

There are several files that need to be properly installed and registered in order for the OPC interface to work properly.  All of these files are installed and registered during the GainSeeker installation.

COM errors which may occur with OPC

Below are some typical COM errors that may occur with GainSeeker OPC commands.

Sample OPC template

The following is a very basic sample template to interface with an OPC Server.  This template will initialize one channel and connect to the OPC Server.  It will then loop until it gets a good quality value.  Once the quality if good, it will read the data value and then disconnect from the OPC Server.  See Template Commands in the appendices for more information on the commands used in the formulas.

Sample template flow:

1. Initialize the channel in synchronous mode

2. Connect to the OPC Server

3. Read the value

4. Check the quality of the value

5. If the quality is not good, re-read the value and re-check the quality

6. If the quality is good, set Data 1 column to the value

7. Disconnect from the OPC Server

Sample template for one column: