_OPCPvssServer

Data point elements of type _OPCPvssServer contain the views as well as the state of the views linked to the OPC DA server.

DP element Type Description
Config.CNSViews dyn_string This data point element contains all CNS views which are linked to the server for creating the address space.
State.CNSViews dyn_int

Indicates the current state of the respective CNS view.

Status Description
0 The state of the CNS view is currently not defined because the OPC server is not running. If the server has not been stopped properly (e.g. using the KILL command) the last set status remains until the OPC server is started again.
1 The distributed system is connected and the CNS view or all OPC elements of the view are correctly in the server's address space. The values of all elements in the address space are the same as the actual value of the respective data point element.
2 The distributed system is connected and a delta synchronization is running. Connected OPC clients are able to receive values from the OPC server.
3 The distributed system is connected and the entire CNS view is refreshed in the OPC server's address space (Full Sync). In this case, connected OPC clients receive the last usable values from the OPC server, which are marked with OPC quality "Uncertain, Last Useable Vale". If one CNS view of a system is in Full Sync state, all other CNS views will be in this state also.
4 The distributed system is connected, but the configured CNS view does not exist or cannot be found in the given system.
5 The distributed system is not connected and the server does not have any information about the configured CNS views in the address space. As soon as the distributed system is connected, the OPC server does a full synchronization for all views.
6

The distributed system is not connected, the OPC server has IP identification and CNS views in its address space. The server marks all values of the system of the CNS view with OPC quality status "Uncertain, Last Usable Value". If the connection to the distributed system is established, the OPC server starts a full or a delta synchronization depending on config entry maxUpdateMsgCouint and the amount of changed data.

If the OPC server is started with useLocalIdentification, the address space will be created with the information loaded from the files proj_path/data/DpMsgTypeContainer.bin and proj_path/data/DpMsgIdentification.bin, so TypeContainer and DpIdentification must not be transmitted over the network.