ABB Totalflow Fault Diagnostics and Troubleshooting
Key Takeaway
How to diagnose ABB Totalflow faults — measurement alarms, communication failures, archive gaps, power issues, and PCCU32 diagnostic tools.
Quick Answer
Totalflow diagnostics use the PCCU32 alarm and event log as the primary troubleshooting tool. Common issues include measurement alarms (DP/pressure/temperature out of range), communication failures (DNP3/Modbus), archive gaps, and power system problems.
Alarm Types
- Measurement — High/low DP, pressure, temperature out of range, wire break
- Communication — Serial port error, Ethernet fault, GC comm loss
- Power — Low battery, solar charger fault
- Application — Flow calculation error, archive write failure
- Hardware — I/O module fault, ADC error
Common Measurement Issues
- Zero flow with gas flowing — Failed DP transmitter, stalled turbine meter, or application in alarm state
- Negative flow rate — Reverse DP, check transmitter zeroing
- Unrealistic compressibility — Gas composition error, check GC integration
Archive Gaps
Caused by power loss, application error during record period, flash write errors, or configuration changes. Event log identifies the cause and timing.
DNP3 Troubleshooting
- No response → check outstation address, port, baud rate, wiring
- Stale data → verify deadband settings, I/O connected
- Event buffer overflow → increase buffer or poll frequency
See also SCADAPack troubleshooting and Bristol FB300 troubleshooting.
Frequently Asked Questions
Common causes: failed DP transmitter (AGA-3), stalled turbine meter (AGA-7), no ultrasonic meter communication (AGA-9), or application in alarm state. Check PCCU32 application alarms and live input values.
Connect PCCU32 and navigate to Archives → Event Log. Export to CSV for analysis or ABB support.
Power loss, flow calculation application error, flash memory write errors, or configuration changes. The event log shows the cause and timing of any gap.