|
OPC Storage as "Gateway" Between OPC Client Applications
OPC Storage can be started from any OPC client applications resp. is available to any OPC client applications as soon as it has been started as a service. The first time an OPC client application accesses the OPC Storage, the default namespace of the OPC Storage is provided, for example, Node1 with Tag1 and Tag2, Node2 with Tag1 and Tag2.
The OPC namespace of the OPC Storage can be statically defined in the OCT configuration file or extended dynamically by the OPC clients by creating items. The items of the namespace may be of any data type covered by the OPC specifications. Arrays of fixed and variable length are also supported for these data types.
The StorageWatchdog system item allows monitoring communication between the OPC Storage and the OPC client(s).
OPC Storage can be started from any OPC client applications resp. is available to any OPC client applications as soon as it has been started as a service. The first time an OPC client application accesses the OPC Storage, the default namespace of the OPC Storage is provided, for example, Node1 with Tag1 and Tag2, Node2 with Tag1 and Tag2.
The OPC namespace of the OPC Storage can be statically defined in the OCT configuration file or extended dynamically by the OPC clients by creating items. The items of the namespace may be of any data type covered by the OPC specifications. Arrays of fixed and variable length are also supported for these data types.
The StorageWatchdog system item allows monitoring communication between the OPC Storage and the OPC client(s).
|