DISCLAIMER
The example below is intended to demonstrate one or more features or methods and is presented as an example only. Schneider Electric assumes no liability for the use or application of this example or any portion thereof.
When trying to troubleshoot communications issues, it is usually necessary to analyze driver log files, I/O log files and Events list covering a period of time that includes an occurrence of the issue.
This article will show how to enable such logs and how to configure its settings. The driver "DNP3" will be used as an example, but the procedure will be the same for most of the native ClearSCADA drivers.
We will start with the driver settings. In order to troubleshoot communications issues, it is usually helpful to enable the driver's "I/O" flag.
We can do that by starting the "Server Status" tool (right click on the server icon, select "Status"). Under "General/Modules", right click on the driver (in this case, "DNP3") and select the option "Logging...":
Under the “Current Options” tab, make sure the I/O option is selected (in blue), click on “Make Default” and “Apply”:
At the “Configuration” tab, you will see the location of the log file as part of the “File base” setting.
Make sure you adjust the “Maximum size of each file” and “Maximum number of log files” so they will keep the messages for a period of time long enough to capture the issue and give you time to grab the log files (probably more than the default shown below):
Now, go to the Channel object that is linked to the outstation you want troubleshoot communications in ViewX, right click and select “Enable IO Logging”. Check the “Persist” option and click “OK”:
Note: The "Persist" option means that the I/O logs will continue to be generated even after a driver (or server) restart.
Now both "DriverDNP3" and "IO" log files will be generated. For example:
The example below is intended to demonstrate one or more features or methods and is presented as an example only. Schneider Electric assumes no liability for the use or application of this example or any portion thereof.
When trying to troubleshoot communications issues, it is usually necessary to analyze driver log files, I/O log files and Events list covering a period of time that includes an occurrence of the issue.
This article will show how to enable such logs and how to configure its settings. The driver "DNP3" will be used as an example, but the procedure will be the same for most of the native ClearSCADA drivers.
We will start with the driver settings. In order to troubleshoot communications issues, it is usually helpful to enable the driver's "I/O" flag.
We can do that by starting the "Server Status" tool (right click on the server icon, select "Status"). Under "General/Modules", right click on the driver (in this case, "DNP3") and select the option "Logging...":
Under the “Current Options” tab, make sure the I/O option is selected (in blue), click on “Make Default” and “Apply”:
At the “Configuration” tab, you will see the location of the log file as part of the “File base” setting.
Make sure you adjust the “Maximum size of each file” and “Maximum number of log files” so they will keep the messages for a period of time long enough to capture the issue and give you time to grab the log files (probably more than the default shown below):
Now, go to the Channel object that is linked to the outstation you want troubleshoot communications in ViewX, right click and select “Enable IO Logging”. Check the “Persist” option and click “OK”:
Note: The "Persist" option means that the I/O logs will continue to be generated even after a driver (or server) restart.
Now both "DriverDNP3" and "IO" log files will be generated. For example:
Released for:Schneider Electric USA
