D2000 OPC Server operation
The topic describes how to run the program D2000 OPC Server and its operation.
Running the OPC Server
It is not necessary to run the D2000 OPC Server individually, the Windows operating system runs it always when an OPC is attempting to connect it.
OPC Server operation
- OPC server and OPC client on one computer
The communication between the OPC server and the OPC client is performed through the interface COM. - OPC server and OPC client on various computers
In this case, the communication between the OPC server and the OPC client is performed through the interface DCOM.
Monitoring of OPC Server operation
D2000 OPCServer operation can be monitored after you set the level of debug info. You can set this level in the system registers:
HKEY_LOCAL_MACHINE\SOFTWARE\Ipesoft\D2000V70\OPCServers\ProgID\DebugLevel
DWORD register key is created automatically when first starting the D2000 OPC Server. The default value is 0. You can set the following values, which monitor the OPC client calls to D2000 OPC Server on the various levels. The higher number you set, the higher level (including lower levels) is used.
| Value | Level of debug info |
|---|---|
| 0 | The default value, no debug info. |
| 1 | Monitors only OPC calls that end by an error except E_NOTIMPL error (i.e. the callings that are not supported in D2000 Server). |
| 2 | Monitors only OPC calls that end with errors including E_NOTIMPL. |
| 3 | Monitors all OPC calls except the asynchronous callback calls. |
| 4 | Monitors the asynchronous callback calls. |
| 5 | Detail monitoring of values that are sent in both synchronous and asynchronous callback calls. |
All debug info is saved into .log file of the D2000 OPC Server. See more information in the chapter Error reporting.
Related pages:
Pridať komentár