Whitepaper

Certification Testing
Configuration Guidelines
OPC Server Configuration
Compliance
March 12, 2014www.opcfoundation.org

Contents
1Introduction .............................................................................................................................................................................. 3
1.1

2

Terminology ...................................................................................................................................................................... 3

Server Configuration Requirements...................................................................................................................................... 3
2.1

Data Acquisition from Devices ..................................................................................................................................... 3

2.1.1

Modbus Support ...................................................................................................................................................... 4

2.2

PLC/Device Equipment Configuration ....................................................................................................................... 4

2.3

Address Space Configuration ......................................................................................................................................... 4

3

Appendix A – OPC Server Check List................................................................................................................................. 5

4

Appendix B - Example OPC Server Address Space .......................................................................................................... 6

5

Appendix C – Node Address Space Text File .................................................................................................................... 7
5.1

DA Server .......................................................................................................................................................................... 7

5.1.1
6Example CSV File.................................................................................................................................................... 7

Appendix D – COM Variant Data Type Definition .......................................................................................................... 82|Page
www.opcfoundation.org
www.opcfoundation.org

1 Introduction
This document provides the necessary instructions for you to prepare your OPC Server (DA, UA) configuration forcertification testing. Submit your configuration to the lab along with installation instructions.

1.1 Terminology
The terms Node and Tag mean the same thing, i.e. an item in the address-space of the Server.

2 Server Configuration Requirements

A real-world configuration is desired for testing.

Data acquisition from real data-sources is required; see 2.1 Data Acquisition from Devices below.

Address-space size and data-types are described in 2.2 PLC/Device Equipment Configuration on page 4.

The server must be configured to allow multiple OPC Clients to connect concurrently.

A valid license (if applicable) enabling all OPC functionality must be sent to the lab.

Full tracing of OPC activity enabled.

Cannot provide the configuration? Please send Server configuration instructions per these requirements.

2.1 Data Acquisition from Devices
If the OPC Server supports data acquisition from devices (PLCs etc.) then:A minimum of 2 devices must be configured, although 3 are preferred.

Each device should be configured with the manufacturer recommended settings (timeout etc.)

The configuration of these devices should be defined for maximum reliability and data throughput.

If the OPC Server only provides access to in-memory data then it is exempt from the above requirements.

3|Pagewww.opcfoundation.org
www.opcfoundation.org

2.1.1 Modbus Support
The OPC-Foundation lab provides 3 Modbus devices that can be accessed via Serial (COM1) or TCP/IP Ethernet(192.168.2.248, 192.168.2.249, and 192.168.2.250).
We recommend the following Modbus Simulator: www.hmisys.com
Prefer to use an alternate device/protocol? Contact the lab immediately to coordinate arrangements.

2.2 PLC/Device Equipment Configuration
The device should be configured with as many Tags/Nodes as reasonably possible, i.e. 1000+.



It is not necessary to configure more Nodes than the server can handle.

The IP address of the device (if applicable) should be configurable with tools provided with the device.

Any additional hardware/software and/or communications-drivers must be shipped to the lab.

2.3 Address Space Configuration
The Server should be configured with:

Static items - items that won’t be changed by the device.
Dynamic items – items whose values change automatically by the device.

Note: Configured items should not overlap in the physical registers of the device i.e. do not configure 2 bytes and 1word and 16 Booleans to use the same physical addresses.
All supported data types which includes:o Scalar: 100 of each type; constrained servers may use fewer, e.g.5.
o Array: 1 of each type; min. array size of 10-elements (constrained servers use 5-elements).
o Other: 5 of each supported other data-types.
Items with configured ranges for deadband testing must be provided, if supported.
Items with different access-rights must be available, e.g. Read/Write, Read-only, Write-only.

Please refer to Appendix B - Example OPC Server Address Space on page 6.
Please export the items to a CSV file as described in Example CSV File on page 7.

4|Pagewww.opcfoundation.org
www.opcfoundation.org

3 Appendix A – OPC Server Check List
Use the following checklist to prepare the information needed by the Lab. Do not send this list to the lab.
#Itemy/n Initials

YY-MMDDPLC Device(s) (see 2.1 Data Acquisition from Devices on page 3)
1.

2 devices prepared and ready for shipping with return☐

instructions?
2.

Power cables provided for each PLC/device?

☐3.

Communications cables (RS232, RJ45 etc.) provided for each☐

PLC/device?
4.

Devices programmed for testing?

☐5.

Applicable device driver(s) and configuration software☐provided?
OPC Server
6.

Release version software provided to the Certification Test☐Lab?
installer and instructions etc.

7.

Necessary supplies provided if it is a hardware product?

☐Power cables, connectors etc.

8.

License (activation code) provided?

☐

9.

Server’s Address Space prepared with Static, Dynamic and☐R/RW/W items?
10.

Server’s Address Space exported to CSV?

☐See Error! Reference source not found. Error! Bookmark not defined..

11.

Server’s Configuration file provided?

☐

Other Resources
12.

Technical support contact(s) provided?

☐5|Pagewww.opcfoundation.org
www.opcfoundation.org

4 Appendix B - Example OPC Server Address Space
Please refer to the Standardized Address Space Guidelines document available here:
http://www.opcfoundation.org/developer-tools/certification-test-tools/configuration-guidelines/

6|Pagewww.opcfoundation.org
www.opcfoundation.org

5 Appendix C – Node Address Space Text FileA CSV file format has been defined for use with the CTT when load testing your OPC Server. This file will be used
as input for automatically generating configuration files for different test tools.

5.1 DA Server
The first line of the CSV file contains the machine name (or IP address) and the server ProgID, with the remaining
lines containing the itemID, AccessRights, DataType, UseIdentifier, and Device.
ItemID:The fully qualified name of the item in the servers address space

AccessRights: R, W, RW (readable, writeable, read- and writeable).
DataType:

The numeric DataType value of the VariantType of the item
See Appendix D – COM Variant Data Type Definition on page 8.

5.1.1 Example CSV Filelocalhost;OPCSample.OpcDaServer
DeviceA/Configuration/ChangeRateDynamic;RW;18;Configuration;DeviceA
DeviceA/Configuration/ChangeRateDynamicFast;RW;18;Configuration;DeviceA
DeviceA/Configuration/ChangeRateDynamicSlow;RW;18;Configuration;DeviceA
DeviceA/Deadband/Decimal_RW;RW;14;Deadband;DeviceA

7|Pagewww.opcfoundation.org
www.opcfoundation.org

6 Appendix D – COM Variant Data Type Definition
Variant Type

Num

Variant Type

Num

Variant TypeNum

VT_EMPTY

0VT_NULL

1

VT_I2

2

VT_I4

3

VT_R44VT_R85VT_CY

6VT_DATE

7

VT_BSTR8

VT_DISPATCH

9VT_ERROR

10

VT_BOOL

11VT_VARIANT

12

VT_UNKNOWN

13

VT_DECIMAL

14

VT_I116

VT_UI117VT_UI218

VT_UI419VT_I820

VT_UI821

VT_INT

22VT_UINT23

VT_VOID

24

VT_HRESULT25

VT_PTR

26

VT_SAFEARRAY27

VT_CARRAY28

VT_USERDEFINED

29

VT_LPSTR30

VT_LPWSTR

31

VT_FILETIME

64

VT_BLOB65

VT_STREAM

66

VT_STORAGE

67

VT_STREAMED_OBJECT

68

VT_STORED_OBJECT

69

VT_BLOB_OBJECT

70

VT_CF

71

VT_CLSID

72

VT_VECTOR

0x1000

VT_ARRAY

0x2000

VT_BYREF

0x4000

VT_RESERVED

0x8000

VT_ILLEGAL

0xffff

VT_ILLEGALMASKED

0xfff

VT_TYPEMASK

0xfff

The information above was obtained from: http://home.clara.net/marin/COM/variant_type_definitions.htm

8|Pagewww.opcfoundation.org
www.opcfoundation.org

Contact Information:
OPC Foundation
16101 N. 82nd Street, Suite 3B
Scottsdale, AZ 85260
USA
Tel: 480-483-6644
Fax: 480-483-1830
Email: compliance@opcfoundation.org

9|Pagewww.opcfoundation.org
www.opcfoundation.org

Page Intentionally Left Blank

10 | P a g e
www.opcfoundation.org
www.opcfoundation.org

Revision History
Version

Date

AuthorChange

1

2007

CMP

Initial version.

2Mar-12, 2014

CMP

Reformatted to use new template.

11 | P a g e
www.opcfoundation.org
www.opcfoundation.org