Driver Logging can be used to help diagnose abnormal conditions relating to driver activity. Driver logging can also be used for assessing potential problems. The log files that are produced provide useful diagnostic information about specific aspects of the system. For example, the Points logging option provides diagnostic information about the points on a particular driver.
Should you need to contact Schneider Electric for assistance with resolving a problem that ClearSCADA has detected, you might be asked to provide Log files to help in assessing the cause of the problem. Be aware that existing warranty and support arrangements determine the level of help that you receive should you need to contact Schneider Electric.
This section explains the driver logging options that are common to many advanced drivers.
Those driver logging options that are typically required for investigating abnormal conditions are enabled by default. We suggest that the logging options are left at this default unless other logging options are specifically requested by Schneider Electric, or the default options are adversely affecting system performance.
For information on any driver logging options that are not listed below, see the driver-specific documentation.
These driver log file options are common to many advanced drivers:
Logs general information about the driver.
Logs any errors detected during driver operation. For example, a loss of connection to the ClearSCADA database.
Logs information about low-level internal thread timer queues.
ATTENTION: The Timers option typically logs a large amount of information. As such, we recommend that this option is only enabled if specifically requested by Schneider Electric’s engineers.
Logs information about low-level internal thread event queues.
ATTENTION: The Events option typically logs a large amount of information. As such, we recommend that this option is only enabled if specifically requested by Schneider Electric’s engineers.
Logs information about low-level I/O.
Logs configuration changes to database items (any create, delete, or modify activity on the system).
Logs general information about the channels on the system, including the channel’s state, and activities including attaching or detaching outstation sets.
Logs general information about the outstation sets on the system, including one shot, promoted dial out, and channel switching.
Logs general information about the outstations on the system, including the outstation’s state, current channel, and any switching activity.
Logs general information about the points on the system, including controls and persistence.
Logs information on dial-up modem exchanges and states.
Each channel has a scanner that is responsible for scanning the outstation(s) on that channel. The Scanner Log File option logs information about each scanner.
Logs information about any external requests from users, plus internal requests within the driver.
Logs information about point data retrieved by the driver.
Logs information about the phases of outstation scanning (primary, secondary, promoted, exception, and so on).
Logs information about the low-level interface from server to driver.
Logs information about the low-level interface from driver to server.
Logs information about the use of the browse options on configuration Forms.
Logs information about the time taken to perform individual server requests. This includes how long a driver thread waits for the local driver sink lock, how long the database takes to process the request, and the total time taken to complete both activities.
Further Information
Log files and Log file settings: see Driver Logging.
Displaying log files: see Display a Driver Log File.
The log file options to turn on if experiencing problems with an advanced driver, see Troubleshooting.
Types of log file supported by ClearSCADA: see Logging and Monitoring.