Technical Specification
Tibbo OPC Server is fully compatible with Windows XP/2003 or later (Microsoft Visual C++ 2013 redistributable is required - installed automatically).
Supported DA Asynchronous I/O 2.0 and Synchronous I/O with COM/DCOM technology.
Tibbo OPC server has built-in AggreGate network protocol and can interact with any Tibbo devices by AggreGate agent protocol as well as it can connect to AggreGate server. The OPC Server sends the OPC Client applications the information on the Value, Quality and Timestamp of an item (tag). These fields are read from the AggreGate variables.
If OPC Server loses communication with their data source (AggreGate Server or AggreGate Agent), the process values are set to Bad [Configuration Error] quality. If the AggreGate variable value is empty, the quality is set to Uncertain [Non-Specific] .
Concordance table of the AggreGate variables and the OPC data types are represented in the following chart:
AggreGate Data Type |
OPC Data Type |
INTEGER |
VT_I4 |
STRING |
VT_BSTR |
BOOLEAN |
VT_BOOL |
LONG |
VT_I8 |
FLOAT |
VT_R4 |
DOUBLE |
VT_R8 |
DATE |
VT_DATE |
DATATABLE |
VT_BSTR (by default) |
COLOR |
VT_I4 |
DATA |
VT_BSTR |
It supports arrays of simple data types listed above (VT_ARRAY ). If the table for DATATABLE variable is given the field Value field in the configuration (Learn more about Configuring the Server ), it is taken as the value of this field. Otherwise the table is converted to a string.