Debug
- Last UpdatedOct 21, 2026
- 2 minute read
For debugging purposes, the user can set the interface to send extra interface specific messages to the pipc.log file. There are seven different types of debugging messages. These will be sent to the log depending on which check box was selected in the Debugging section of the opcae tab. To send all possible debugging messages, check the Maximum check box. To turn off all debugging message, check the No Debug check box. (/DB=#, where # is 1, 2, 4, 8, 16, 32, 64 or a combination of any or all values, maximum=127)
In general, enable debug options for a short period of time, as they can bloat log files and reduce performance. For options marked "Technical Support only," enable only at the direction of OSIsoft Technical Support. For details about other command-line parameters, refer to the PI Universal Interface (UniInt) User Guide
|
Option |
Description |
Value |
|---|---|---|
|
Internal testing |
For internal testing only |
/db=1 |
|
Startup |
Logs startup information for each PI point, including instrumenttag and exdesc |
/db=2 |
|
Log messages for tag |
This setting will log the same items as /DB=32, but it will log them for only the tag specified as the debug tag (/DT=tagname). If there is no tag specified, the first tag for which a value is received will be declared the debug tag |
/db=4 |
|
Connections |
Logging for connections. |
/db=8 |
|
Event tags |
Logging for event tags. The interface will print the name of each tag into the pipc.log file, as it receives data. This can create very large log files very quickly. |
/db=16 |
|
Tags that specify vendor specific array |
Logging for tags that contain vendor specific array information. |
/db=32 |
|
Internal data translation |
Logging for internal data translation. This is internal and is not useful for users. |
/db=64 |
Debug tag
This optional parameter is for use with the ‘Log messages for tag’ debugging option. When this option is selected information for the specified debug tag will be written to the pipc.log file. Enter the name of the debug tag in the textbox or use the adjacent triple dot button to browse for the debug tag. If the textbox is left blank, messages will be logged for the first interface tag that receives data. (/DT=tagname)