This section is intended for use by system administrators and high-level engineers who need to use statistical and diagnostic information to assess the state of the ClearSCADA system. This section contains information that is specific to this particular driver.
NOTE: When troubleshooting on a ClearSCADA system, use the Events List to view any diagnostics messages. These may help you to identify the cause of any unexpected system behavior.
Driver logging is useful for investigating driver abnormal conditions or potential abnormal conditions. It provides useful diagnostic information for specific aspects of the system. For instance, the Points logging option provides diagnostic information for the points on a particular driver.
The driver logging options that are typically required for investigating driver abnormal conditions are enabled by default. We recommend that the 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 log files and defining the log file settings, see Driver Logging in the ClearSCADA Guide to Server Administration.
Should you need to contact Schneider Electric for assistance to resolve an abnormal condition on your system, you might be asked to provide Log files to help in assessing the cause of the abnormal condition. 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 specific to the this driver. The driver supports these driver log file options:
- Application—Logs general information about the driver.
- Errors—Logs any errors detected during driver operation. For example, communications failures, or a failure of the connection to the ClearSCADA database.
- Timers—Logs information about low-level internal thread timer queues.
ATTENTION: When enabled, the Timers option can cause a large amount of information to be logged. This can make it more difficult to locate information of interest, due to the high amount of data. It is also possible that the information required maybe overwritten if the log files become full very quickly. For this reason, we recommend that the Timers option is disabled and that you only enable it if specifically asked to do so by a Schneider Electric engineer.
- Events—Logs information about low-level internal thread event queues.
ATTENTION: When enabled, the Events option can cause a large amount of information to be logged. This can make it more difficult to locate information of interest, due to the high amount of data. It is also possible that the information required maybe overwritten if the log files become full very quickly. For this reason, we recommend that the Events option is disabled and that you only enable it if specifically asked to do so by a Schneider Electric engineer.
- Database Objects—Logs changes to database items.
- Requests (Actions)—Logs information about any external requests from users, plus internal requests within the driver.
- Client Sink—Logs information about the low-level interface from server to driver.
- Server Sink—Logs information about the low-level interface from driver to server.
- Browse Server—Logs information about the use of the browse options on configuration Forms.
- Crystal Reports—Logs Crystal-specific diagnostic information.
As the Crystal Reports application accesses the ClearSCADA database using ODBC, you may also need to generate ODBC log files (see ODBC Logging in the ClearSCADA Guide to Client Administration).