Introduction

The HumanOS® OPC-DA Control Driver is used to access, steer and manage devices based on OPC protocol.

Driver Configuration

For remote accessing the OPC controls, a DCOM gateway must be configured.

Device Information

The device information is an XML file specifying the access and commands of a OPC-Device.

Header

The header of the device information declares the

• Device id
• Driver id (always {FAAB832E-2D4B-41EA-9041-68278B99BDC1})
• Base URL as the address, including opcda://

Example:

{
  "Id": "F6699E8B-3E6B-491E-8A47-24BA97175413",
  "Name": "SiemensOpcDAControl",
  "DeviceId": "FAAB832E-2D4B-41EA-9041-68278B99BDC1",
  "Address": "opcda://localhost/Matrikon.OPC.Simulation.1"
}

DataAccess

The connector supports the data access of classical OPC server.

Name	Description	Data Type
Id	Id of the data access point	System.Guid
Name	Name of the item	System.String
Address	OPC-DA address (e.g ".TestValue")	System.String
AccessMode	Read, write or callback flags

Additional OPC-DA properties

Name	Description	Data Type
opc:GroupId	Id of the group (MED: Medium speed (default); FAST: Fast speed; SLOW: Slow speed)	System.String

{
  "Id": "5E2EE368-ABF7-49BC-BDF9-CF43ECC4B679",
  "Name": "Test Value",
  "Address": ".TestValue1",
  "DataClass": "Event",
  "DataType": "System.Double",
  "Access": {
    "Read": true,
    "Receive": true,
    "Write": true
  },
  "Properties": [
    {
      "Name": "GroupId",
      "Value": "MED"
    }
  ]
}

Alarm and Event Access

The OPC-AE is not implemented in version 2.0.