The SCADAPack platform provides comprehensive diagnostic capabilities for various communication protocols and operational conditions. This includes detailed diagnostics for:

• DNP3: Protocol layer analysis, network routing, and event logging.
• Modbus: Client and server diagnostics, including store-and-forward routing.
• IEC 60870-5-104: Protocol layer analysis and event logging.
• TCP/IP: Diagnostics for DNP3 over IP, IP servers, and TCP service ports.
• PLC Communication: Protocol packet displays, communication status, and device status for serial and network PLC services.
• SCADAPack System: General system diagnostics.

This diagnostic information is crucial for troubleshooting communication issues. Specifically, this article outlines how to examine DNP3 event status within the SCADAPack's buffer to diagnose communication problems with remote clients like Geo SCADA and DNPnet.

Procedure:

1. Enable Telnet Server:
   • Access the SCADAPack x70 configuration.
   • Navigate to "IP Communication" -> "Ethernet Ports" -> "Services."
   • Enable the Telnet server option. (Telnet is not a secure protocol since it sends data in cleartext. It is recommended that Telnet be disabled on the device when not in use)
   • Apply and write the changes to the SCADAPack.

2. Connect via Telnet:
• Open a command prompt (CMD).
• Use the telnet command to connect to the SCADAPack's IP address.
• Example: telnet 172.16.1.200

3. View DNP3 Event Log:
   • Once connected, type Status e and press Enter.
   • The SCADAPack will display the current DNP3 events stored in its buffer.

This screenshot displays the accumulated event count when the remote client is not polling data, such as during a connection outage.

This screenshot shows zero events, indicating either no events have occurred, or the remote client has polled all buffered data.

4. Verification of Event Logging and Polling:
• Verify Logging:
• Disconnect the communication between the SCADAPack and the DNPnet client.
• Use RemoteConnect or a similar tool to force value changes on points monitored by the SCADAPack multiple times.
• Run the Status e command again. Verify that the event count in the buffer has increased, confirming event logging.

• • Verify Polling:
    • Reconnect the DNPnet client.
    • Run the Status e command again.
    • If the event count returns to zero, it indicates that the client has successfully polled and cleared the events.

When direct serial or Telnet connections aren't available, use the FILEDIAG command (detailed in the RemoteConnect Manual under "SCADAPack Operations Technical Reference > Command Line Operations > Diagnostics Commands") to direct diagnostics to a SCADAPack log file.

Alternatively, you can examine DNP3 event status by monitoring the DNP3 Event Statistics within the SCADAPack x70 system data. This data, detailed in the RemoteConnect Manual under "SCADAPack Operations Technical Reference > System Data > SYS_EVENTS: Event Statistics for DNP3," can be mapped to RemoteConnect objects for monitoring.

發佈於: 施耐德電機Taiwan