Debug an Open Platform Communications (OPC) client process
- Last UpdatedApr 24, 2025
- 1 minute read
When the options for debugging an Open Platform Communications (OPC) client process are enabled, you can obtain log information about the communication between Omnicomm and the specific OPC client process.
The debugging options are shown in the following table:
|
Option |
Description |
|---|---|
|
-d xxxxxxxxxxxxxxx |
debug flaglog command/message details. |
|
-p xxxxxxxxxxxxxxx |
performance flaglog receiving or sending commands/messages with time stamp. |
Note: xxxxxxxxxxxxxxx is a hexadecimal number that is up to 16 digits. It is used to turn on logging-specific commands or messages between Omnicomm and the OPC client process.
The first 4 digits from the right are used for commands or messages that are sent by Omnicomm to the OPC Client process; the next 4 digits are reserved for those sent by the OPC client process to Omnicomm.
The following table provides a summary of the commands or messages that are sent between Omnicomm and the OPC client process.
|
Omnicomm to OPC Client Process |
OPC Client Process to Omnicomm |
||||
|---|---|---|---|---|---|
|
bit |
hex |
Description |
bit |
hex |
Description |
|
1 |
1 |
Initialize |
1 |
10000 |
Success |
|
2 |
2 |
Group definition |
2 |
20000 |
Error |
|
3 |
4 |
Item definition |
3 |
40000 |
Warning |
|
4 |
8 |
Integrity update |
4 |
80000 |
Data |
|
5 |
10 |
Write data |
5 |
100000 |
Heartbeat |
|
6 |
200000 |
Shutdown |
|||