Proficy Historian for CloudCreate an OPC UA Data Access Collector
Before you begin
- Deploy Proficy Historian for Azure Cloud.
- Install collectors. You can install them on-premises or on a VNet (which can be different from the one on which Proficy Historian for Azure Cloud is deployed).
About this task
Features:
- You can browse the source for tags and their attributes on an OPC server that supports browsing.
- Both the polled and unsolicited data collection are supported; when changes
to the OPC source tags are detected, they are sent to the Historian server.
Unsolicited data collection is supported for OPC 2.0 only. The minimum poll
interval is 100ms. The collector duplicates raw samples from the OPC server
into Data Archiver.
For unsolicited data collection, if collector compression is disabled, all new values produce an exception. And, the deadband percentage is determined by the collector deadband percent. You can only configure the collector deadband percent by enabling compression.
- The supported timestamp resolution is 1ms.
- Floating point, integer, binary, and string data are supported.
- Python expression tags are supported.
- Device timestamps are accepted.
Supported data types:
| OPC UA DA Collector Data Type | Recommended Data Type in Historian |
|---|---|
OpcUaType_Null |
ihTKVariableString |
OpcUaType_Boolean |
ihTKBool |
OpcUaType_SByte |
ihTKByte |
OpcUaType_Byte |
ihTKByte |
OpcUaType_Int16 |
ihTKInteger |
OpcUaType_UInt16 |
ihTKUInt16 |
OpcUaType_Int32 |
ihTKDoubleInteger |
OpcUaType_UInt32 |
ihTKUInt32 |
OpcUaType_Int64 |
ihTKInt64 |
OpcUaType_UInt64 |
ihTKUInt64 |
OpcUaType_Float |
ihTKFloat |
OpcUaType_Double |
ihTKDoubleFloat |
OpcUaType_DateTime |
ihTKVariableString |
OpcUaType_Guid |
ihTKDataTypeUndefined |
OpcUaType_StatusCode |
ihTKDataTypeUndefined |
OpcUaType_String |
ihTKVariableString |
OpcUaType_ByteString |
ihTKDataTypeUndefined |
OpcUaType_XmlElement |
ihTKDataTypeUndefined |
OpcUaType_NodeId |
ihTKDataTypeUndefined |
OpcUaType_ExpandedNodeID |
ihTKDataTypeUndefined |
OpcUaType_DiagnosticInfo |
ihTKDataTypeUndefined |
OpcUaType_QualifiedName |
ihTKDataTypeUndefined |
OpcUaType_LocalizedText |
ihTKDataTypeUndefined |
OpcUaType_ExtensionObject |
ihTKDataTypeUndefined |
OpcUaType_DataValue |
ihTKDataTypeUndefined |
Supported tag attributes:
- Tagname
- Source Address
- Engineering Unit Description
- Data Type
- Hi Engineering Units
- Lo Engineering Units
The Engineering Unit Description, Hi Engineering Units and Lo Engineering Units vary based on the OPC server vendor.
Procedure
- Run Command Prompt as an administrator.
- Run the AzureCloudHistorianConfigurationUtility.exe file. It is provided along with the collectors installer. After you install collectors, it will be available in the C:\Program Files\GE Digital\Historian Cloud Config folder by default.
- Enter the number corresponding to creating a collector instance.
-
Enter the following details:
Field Description Interface Name Enter the name that you want to provide for the collector instance. Azure Load Balancer IP Enter the Azure Load Balancer IP.
Tip: To find the Azure Load Balancer IP:- Go to the Azure portal.
- Go to the Resource Group that was specified during deployment.
- Select the cluster_name-IP to access the resource of type Public IP Address.
- Select or copy the IP Address.
Username Enter the username to connect to Proficy Historian for Azure Cloud. A value is required. Password Enter the password to connect to Proficy Historian for Azure Cloud. A value is required. Tip: For the default user, ihCloudHistAdmin, this is the value you entered in the Password field at the time of deployment.OPC UA Server URI Enter the URI to connect to the OPC server in the following format: opc.tcp://<host name or IP address of the OPC UA server>:<port number>The OPC UA DA collector is created and started.