Troubleshooting

Use the charts in this section if you have an outstation on your system that should be, but is not, communicating with the ClearSCADA server. The charts guide you through a series of checks to assess why the outstation might not be communicating. The checks vary with the type of communications that the outstation uses.

We suggest that you start with CHART 1: Basic Checks for Outstations with no Communications. This chart will guide you through some basic checks. If these checks do not solve the communications problem that ClearSCADA has detected, you will be directed to carry out further checks on other charts. Alternatively, use the table below to check which chart you need to refer to if your system is displaying a specific error message.

If ClearSCADA has detected an abnormal condition on an advanced driver, we recommend the following:

If the problem that ClearSCADA has detected is related to communications with an outstation or dial-up modem, enable I/O logging on any affected channels (see Enable or Disable I/O Logging on a Channel)
Display the relevant Driver Logging window (see Define the Driver Logging Settings). Use the Typical button on the window to enable those driver logging options that are typically required for investigating abnormal conditions.

After the abnormal condition has re-occurred, send the log files to Schneider Electric. You may be asked to turn on different logging options and reproduce the abnormal condition, if the condition cannot be diagnosed from the initial logs. For further information on driver logging options, see Common Advanced Driver Log File Options.

When troubleshooting on a ClearSCADA system, always check the Events List for diagnostic messages. These may help to identify the cause of any abnormal conditions that ClearSCADA has detected. Additionally, each item’s Status display summarizes that particular item’s current status. This might also help to indicate the location or extent of the problem that ClearSCADA has detected (see Status Attributes that are Common to Many Drivers).

For information on analyzing a ClearSCADA system, see System Analysis, and the driver-specific documentation.

Event Journal Message	Reason	Type of Communications Being Used	Chart to Which you Should Refer for more Information
Assign to COM Port Failed	The Windows® operating system has returned an error that is currently unhandled by ClearSCADA . The error indicates that an attempt to assign a COM Port has failed. The Driver Log file indicates the specific operating system error that was returned. If such an error occurs, send the Driver Log file to Schneider Electric for investigation.	Direct Serial Comms	see CHART 2a: Outstations using Direct Serial Communications
		Remote Serial Comms	see CHART 3a: Outstations using Remote Serial Communications
		PSTN Comms	see CHART 4a: Outstations using PSTN Communications
Assign to TCP/IP Port Failed	The Windows® operating system has returned an error that is currently unhandled by ClearSCADA. The error indicates that an attempt to assign a TCP/IP Port has failed. The Driver Log file indicates the specific operating system error that was returned. If such an error occurs, send the Driver Log file to Schneider Electric for investigation.	Remote Serial Comms	see CHART 3a: Outstations using Remote Serial Communications
		PSTN Comms	see CHART 4a: Outstations using PSTN Communications
		TCP/IP Comms	see CHART 5a: Outstations using TCP/IP Communications
COM Port Already Assigned	The COM port is being used by an application other than ClearSCADA.	Direct Serial Comms	see CHART 2a: Outstations using Direct Serial Communications
		Remote Serial Comms	see CHART 3a: Outstations using Remote Serial Communications
		PSTN Comms	see CHART 4a: Outstations using PSTN Communications
Could not bind to UDP port for inbound messages	The driver could not bind to the UDP port to listen for messages. This could be because another application (or a non-driver part of ClearSCADA) is already bound to that port.	Network Comms	see CHART 6a: Outstations using Network Communications
I/O Failure	The Windows operating system returned an error during a read or write operation, or a received data packet was corrupt.	Direct Serial Comms	see CHART 2a: Outstations using Direct Serial Communications
		Remote Serial Comms	see CHART 3a: Outstations using Remote Serial Communications
		PSTN Comms	see CHART 4a: Outstations using PSTN Communications
I/O Timeout	This error may be due to one of several consecutive timeouts. The error might indicate, for example, that the driver has not received a reply to a request, or that the Windows® operating system has not signalled that a write operation has completed its transmission. The Driver log file will provide more information about the error.	Direct Serial Comms	see CHART 2a: Outstations using Direct Serial Communications
		Remote Serial Comms	see CHART 3a: Outstations using Remote Serial Communications
		PSTN Comms	see CHART 4a: Outstations using PSTN Communications
		TCP/IP Comms	see CHART 5a: Outstations using TCP/IP Communications
Internal Error in Driver	The driver has encountered an unhandled condition. The error message relates to an unexpected condition occurring within the driver. If such an error occurs, send the Driver Log files to Schneider Electric for investigation.	Remote Serial Comms	see CHART 3a: Outstations using Remote Serial Communications
		PSTN Comms	see CHART 4a: Outstations using PSTN Communications
		TCP/IP Comms	see CHART 5a: Outstations using TCP/IP Communications
Invalid COM Port	A COM port has been specified that is not defined in the Windows® operating system (for example, COM99 has been configured, but that port does not actually exist in the server). On a Hot-Standby system, ensure that the same ports are available on each server. (This applies to Direct and PSTN communications.)	Direct Serial Comms	see CHART 2a: Outstations using Direct Serial Communications
		Remote Serial Comms	see CHART 3a: Outstations using Remote Serial Communications
		PSTN Comms	see CHART 4a: Outstations using PSTN Communications
Invalid Host Address	The Windows® operating system could not match the specified Host Address with a valid destination.	Remote Serial Comms	see CHART 3a: Outstations using Remote Serial Communications
		PSTN Comms	see CHART 4a: Outstations using PSTN Communications
		TCP/IP Comms	see CHART 5a: Outstations using TCP/IP Communications
Modem AT Command Error	The configured AT command is not compatible with the attached modem, so the modem is returning an error.	PSTN Comms	see CHART 4a: Outstations using PSTN Communications
Modem Failed	The driver has attempted to poll the attached modem with the configured AT command. However, the driver has not received a valid response within the configured Standard Reply Delay.	PSTN Comms	see CHART 4a: Outstations using PSTN Communications
No Write in Progress	The Windows® operating system has indicated that a Write operation has completed. However, ClearSCADA has no record of such a Write operation.	Direct Serial Comms	see CHART 2a: Outstations using Direct Serial Communications
No Write in Progress		PSTN Comms	see CHART 4a: Outstations using PSTN Communications
Unable to Connect to TCP/IP Port	The driver has attempted to connect to a remote device, but that device has not acknowledged the request.	Remote Serial Comms	see CHART 3a: Outstations using Remote Serial Communications
		PSTN Comms	see CHART 4a: Outstations using PSTN Communications
		TCP/IP Comms	see CHART 5a: Outstations using TCP/IP Communications

Further Information

Driver Log Files: see Driver Logging.

Server settings that define the number of consecutive read/write failures that have to be exceeded before an I/O Failure alarm is generated: see Define the Maximum Number of Consecutive Failed Reads and Writes.

Server settings that define the number of consecutive timeouts that have to be exceeded before an I/O Timeout alarm is generated: see Define the Maximum Number of Consecutive Read and Write Timeouts.