Emerson ROC800 Fault Diagnostics and Troubleshooting
Key Takeaway
How to diagnose ROC800 faults — status LEDs, alarm/event log, measurement alarms, communication failures, zero flow diagnostics, and archive gap analysis.
Quick Answer
Diagnose ROC800 issues using front-panel status LEDs, the ROCLINK 800 alarm/event log, and live data monitoring. Common issues: zero flow (failed DP transmitter or stalled turbine), communication failures (baud rate or address mismatch), and archive gaps (power loss or calculation errors). Connect ROCLINK 800 and check the event log first.
What Do the Status LEDs Mean?
- PWR — Power status (green = normal)
- CPU — Processor status (green = running, red = fault)
- COMM — Communication activity (flashing = active)
What Are Common Measurement Faults?
- Zero flow with gas flowing — Failed DP transmitter (AGA-3), stalled turbine or failed pulse input (AGA-7), meter run in alarm state
- Negative flow — Reverse DP, check transmitter zeroing
- Unrealistic compressibility — Gas composition error
What Causes Communication Failures?
- Serial: baud rate mismatch, wrong COM port, cable fault, RS-485 termination
- Ethernet: IP address wrong, port 4000/5000/20000 blocked by firewall
- DNP3: outstation address mismatch with SCADA master configuration
What Causes Archive Gaps?
Power loss, meter run in alarm state during record period, flash memory write errors, or configuration changes. Event log identifies the cause.
For protocol troubleshooting, see Modbus troubleshooting and DNP3 troubleshooting. For competing platform diagnostics, see ABB Totalflow troubleshooting and SCADAPack fault diagnostics.
Frequently Asked Questions
Common causes: failed DP transmitter (AGA-3), stalled turbine or failed pulse input (AGA-7), meter run in alarm state. Check ROCLINK 800 alarm log and live AI values.
Connect ROCLINK 800 → Archive → Event Log. Shows timestamped alarms, configuration changes, communication faults, and power events.
Power loss, meter run alarm state during the record period, flash memory errors, or configuration changes. Event log identifies the cause and timing.