A Look at Tibbo's OPC Server
A Look at Tibbo's OPC Server
When it comes to hardware communication, an open platform communications server can come in handy. See how Tibbo's work in that field can lend a hand.
Join the DZone community and get the full member experience.Join For Free
OPC stands for Open Platform Communications — a set of specifications and standards for industrial telecommunication. OPC defines the transfer of real-time plant data between control devices from various manufacturers. The aim of OPC was to support a common bridge for Windows-based software applications and process control hardware. It was designed to minimize the quantity of duplicated effort made by hardware companies and their software partners.
Tibbo's OPC Server supports the most typical OPC spec-OPC Data Access (OPC DA), which is used for reading and writing real-time data. Any device that supports the Tibbo AggreGate protocol can be a data source. AggreGate is a white-label IoT integration platform utilizing modern network technologies to configure, control, monitor and support electronic devices, as well as shared networks of such electronic devices. It also assists you with aggregating device data in the cloud, where you can "slice and dice" it according to your requirements. Moreover, the platform allows other enterprise applications transparently access this data through the AggreGate server.
Tibbo OPC server has embedded AggreGate network protocol. It can both interact with any Tibbo devices via AggreGate agent protocol and connect to AggreGate server. The AggreGate agent protocol open-source solution is published for Java, C#, and C++ programming languages, so your connection scheme is not restricted to AggreGate server or Tibbo devices only.
A simple example: TPS reads Tibbit #29 (ambient temperature meter) and forwards data to OPC server via AggreGate agent protocol.
A more complex example: We have a Windows-based PC controlling a wood processing machine by means of an AggreGate server through the Modbus protocol. If the OPC server is linked with the AggreGate server, the data from the machine is sent to the OPC Server, and therefore, we can operate and monitor the machine via any OPC client.
- Compatibility with Windows XP/2003 or later (Microsoft Visual C++ 2013 redistributable is required - installed automatically)
- Support of DA Asynchronous I/O 2.0 and Synchronous I/O with COM/DCOM technology
The OPC Server transmits the information on the Value, Quality and Timestamp of an item (tag) to the OPC Client applications. These fields are read from the AggreGate variables.
The process values are set to Bad [Configuration Error] quality if OPC Server loses communication with its data source (AggreGate Agent or AggreGate Server). The quality is set to Uncertain [Non-Specific] if the AggreGate variable value is empty.
In the following chart below you can see a concordance table of the AggreGate variables and the OPC data types:
|AggreGate Data Type||OPC Data Type|
|DATATABLE||OPC VT_BSTR (by default)|
It also supports arrays of simple data types listed above (VT_ARRAY).
Opinions expressed by DZone contributors are their own.