OPC Specification Support Details

OPC Data Access (DA) Support

• OPC DA 1.x, 2.x, 3.x standards support
• Used for reading/writing of real-time data with OPC DA servers connected to control system devices such as PLC, DCS, etc. 
• Browse OPC server address space
• Read or write 1 to N values, tags, items
• Subscribe to data chages on values, tags, items, alter subscription rate if needed, and unsubscribe
• Browse and read OPC Item Properties on any tag/item
• Includes 44 example code snippets you can use plus a Visual Studio.NET example application 

OPC UA Alarms & Conditions Support

• Browse OPC server address space for available alarms & conditions on nodes (tags)
• Receive Event Notifications separately from real-time data change notifications
• Filter event subscriptions on message, severity, time, & source
• Build re-usable select classes for common filters you need
• Enable/disable conditions
• Apply comments to conditions
• Acknowledge or confirm condition states
• Shelve, un-shelve, timed shelve, or one-shot shelve alarms
• Requires you have an OPC UA – Alarms & Conditions compatible server
• Includes 11 example code snippets

OPC UA Complex Data Support

OPC Data Client supports working with server specific non-standard data types including structures and industry standard data models. The OPC Data Client provides the functionality for your application to access OPC UA servers that support complex data and data models.  Twelve different code samples help you get results quickly. 

Functions include but not limited to:

• Access server data type metadata/data dictionaries and decode them to build meaningful structures in your code
• Read Data
• Subscribe to Data
• Write Data
• Create a Data Type
• Complex data type model in OPC UA 1.04 (based on DataTypeDefinition) is supported with Binary encoding in Client-Server model.
• The "old" pre-OPC UA 1.04 complex data type model (based on DataTypeDictionary) is also still supported, and both models work together and in a unified way from developer's perspective.

OPC UA PubSub Support

• Subscribe to dataset messages from a publisher and consume resulting data or events
• Use UDP (with IPv4 or IPv6) or Ethernet (with or without VLAN tagging), or MQTT for datagram transport.
• Parse UADP or JSON message mapping or OPC UA UDP and OPC UA Ethernet protocol mappings, and decode data encoded with Variant, DataValue, or RawData encoding.
• Receive chunked messages automatically assembled, and key frames and delta frames preprocessed.
• Deal with different header profiles, such as fixed cyclic, dynamix, or flexible.
• Specify filtering by various criteria.
• Provide complete or partial metadata for message decoding.
• Identify dataset fields by their names or indexes.
• Load and inspect PubSub configuration from a binary file, or access it live in an OPC UA server over its information model.
• Optionally, avoid using physical identifiers, specify PubSub objects by their names, and use automatic logical resolution (with data from a configuration file or an OPC server) to make PubSub subscriptions.
• Use the included OPC UA Demo Publisher tool to publish test messages.
• Use the OpcCmd Utility to make PubSub subscriptions without a need for coding.
• Detailed documentation and sample code available