SCADAPack Fault Diagnostics and Troubleshooting
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
Minor faults clear via Telepace Studio Controller Reset. Persistent faults may require power cycle. Check the event log for the fault code and root cause before clearing.
Check outstation address, communication port, baud rate, wiring (RS-485), firewall (TCP), and whether the SCADAPack is in a fault/halt state. Review the Telepace Studio event log.
A solid FAULT LED indicates a hardware or program fault that has halted or degraded operation. Connect with Telepace Studio and check the event log for the specific fault code.