Skip to main content

SCADAPack Fault Diagnostics and Troubleshooting

By NFM Consulting 1 min read

Key Takeaway

How to diagnose and resolve SCADAPack faults — LED status codes, event log, DNP3 communication issues, I/O faults, and program errors.

Quick Answer

SCADAPack diagnostics use front-panel LEDs, the Telepace Studio event log, and communication status indicators. Most faults can be diagnosed by checking LED states, reviewing the event log, and verifying communication and I/O configuration.

Status LEDs

  • PWR — Power status (green=normal)
  • RUN — Program executing (green=running, off=stopped)
  • FAULT — Error condition (solid=halted, flashing=degraded)
  • COM — Communication activity

Event Log

Connect with Telepace Studio and open Controller → Event Log. Review timestamped entries for fault codes, communication errors, watchdog timeouts, and I/O exceptions.

DNP3 Troubleshooting

  • Not responding to polls — Check outstation address, port, baud rate, wiring
  • No unsolicited responses — Verify unsolicited is enabled, confirm port matches
  • Stale data — Check deadband settings, verify I/O is connected
  • Event buffer overflow — Increase buffer size or poll frequency

I/O Faults

  • Expansion module not responding — check bus cable and power
  • Analog reading out of range — verify input type configuration and wiring

Self-Diagnostics

Build a fault annunciator routine using SCADAPack system status registers to detect CPU errors, communication faults, and low battery. Report fault conditions via DNP3 binary inputs to the SCADA master.

See also Bristol FB300 troubleshooting and Geo SCADA troubleshooting.

Frequently Asked Questions

Ready to Get Started?

Our engineers are ready to help with your automation project.