SCADA Displays Wrong Values While PLC Reads Correctly: Root-Cause Diagnosis Guide

The Core Pain: Operators Trust Bad Numbers

Your GE RX3i PLC shows a reactor temperature of 87.4 °C. Your Yokogawa CENTUM VP HMI shows 22,937 °C. The field transmitter is healthy. Nothing has changed in the ladder logic. Yet the control room operator sees a wildly wrong reading and hesitates to act. This disconnect causes missed shutdowns, false trips, and loss of process visibility. The root cause is never in the field device. It lives in the data path between the PLC output register and the SCADA tag store.

Five specific faults drive 95 % of these cases. Each one leaves a distinct fingerprint. Identify the fingerprint first, then fix it. This guide walks through each fault with concrete Yokogawa and GE RX3i parameters.

Fault 1 — Scaling Applied Twice

The GE RX3i analog input module AI-215 outputs a 15-bit integer. At 4 mA the raw count is 0; at 20 mA the count is 32,000. The GE PLC function block SCALE_INT converts this to engineering units (EU) — say 0–200 °C — and stores the result in %R00101 as a REAL. If Yokogawa CENTUM VP then reads %R00101 and applies another 0–32000 to 0–200 °C scaling in the tag definition, the displayed value jumps to 200 × (87.4 / 200) × (32000 / 200) = 13,984 °C. Always check the PLC tag type before configuring SCADA scaling.

1. Open GE Proficy Machine Edition. Navigate to the AI block for the suspect channel.
2. Confirm whether the output reference (%R or %AI) holds raw counts or EU. Raw = WORD type; EU = REAL type.
3. In Yokogawa CENTUM VP Builder, open the tag definition for that point. If the GE block already outputs EU, set SCADA Input Low = 0.0 and Input High = 1.0 with Output Low = 0 and Output High = 200 to create a 1:1 pass-through. Remove any raw-to-EU conversion.
4. Write a test value of 100.0 into %R00101 via the GE data monitor. Verify CENTUM VP shows 100.0 ± 0.1. If it does not, re-examine the tag scaling chain.

Fault 2 — Data Type Conflict Between REAL and INT

A 32-bit IEEE 754 REAL stored in two consecutive Modbus holding registers (e.g., 40101 and 40102) looks like a meaningless large integer if the SCADA tag reads only register 40101 as an INT16. Yokogawa CENTUM VP uses tag types REAL, LONG, INT, and WORD. GE RX3i uses REAL (32-bit float) and INT (16-bit signed). These must match across the Modbus boundary. A REAL mismatch produces values like –2,147,352,576 or 3.4028E38 in the SCADA faceplate.

1. In GE Proficy, note the exact data type of each exported tag — REAL occupies 2 Modbus registers; INT occupies 1.
2. In CENTUM VP OPC DA tag settings, set Data Type = REAL for all floating-point GE references. Set register count = 2 per tag.
3. Confirm byte order setting in the Yokogawa Modbus driver matches GE RX3i byte order. GE RX3i uses big-endian word order by default.
4. Force a known REAL value (e.g., 50.0 = hex 42480000) into the GE register. Verify CENTUM VP reads 50.0 without truncation.

Fault 3 — Modbus Word-Order and Byte-Order Errors

The GE RX3i stores a 32-bit REAL across registers 40101 (high word) and 40102 (low word). Yokogawa CENTUM VP with default Modbus driver settings may read register 40101 as low word and 40102 as high word. The result is a byte-swapped float that produces a wildly different number. For example, 87.4 °C (hex 42AE999A) becomes –8.50505E–30 when the words swap. Fix this in the CENTUM VP communication parameter block.

1. Open CENTUM VP System View. Navigate to the Modbus master communication node.
2. Locate the FLOAT32 byte-order parameter. Options are typically: ABCD (big-endian), CDAB (mid-big), BADC (mid-little), DCBA (little-endian).
3. GE RX3i uses ABCD order. Set CENTUM VP driver to ABCD for all REAL tags from GE.
4. Restart the Modbus driver. Verify with a known engineering value. Document the byte-order setting in the loop sheet.

Fault 4 — Address Offset and Stale Data

Address offset errors arise from a 0-based versus 1-based register numbering mismatch. The GE PLC engineer assigns a value to register 40021. The Yokogawa engineer configures the tag to read address 20 (base-0), expecting register 40021 — but in some Modbus drivers base-0 address 20 maps to register 40021, while in others it maps to 40022. A one-register offset means the SCADA tag reads a completely different variable. This is silent and dangerous in a live plant. Stale data is equally hazardous. When CENTUM VP loses Modbus connectivity for more than 500 ms, it freezes the last good value and shows tag quality as "Uncertain." Operators may not notice the quality state change if the HMI faceplate does not color-code quality.

1. Compare the GE Proficy register assignment table against the CENTUM VP tag address table. Resolve base-0 versus base-1 by injecting a unique value (e.g., 123.4) into a specific known register and confirming the correct SCADA tag updates.
2. In CENTUM VP, enable tag quality display on all critical analog faceplates. Configure a system-level alarm when more than 5 % of tags enter "Bad" quality state.
3. Set the Modbus communication timeout to 1,000 ms with 3 retries before declaring tag Bad. Default 30-second timeouts hide intermittent outages.
4. Log all communication errors in the CENTUM VP event journal. Review weekly for recurring dropout patterns that signal hardware faults or network congestion.

Field-Proven Action Advice

Every SCADA-PLC data mismatch falls into one of these five categories: double scaling, data type conflict, word-order error, address offset, or stale data. Start diagnosis by reading the raw register directly on the GE RX3i data monitor and comparing it to the Yokogawa CENTUM VP tag value at the same instant. If the raw register shows the correct EU value and SCADA does not, the fault is in the communication or tag configuration — not the field device. Fix scaling and data type issues first; they are the most common. Then verify byte order, address mapping, and communication quality settings. Document every corrected parameter in the as-built loop sheet. A single misconfigured tag in a critical reactor loop can cause an unplanned shutdown worth tens of thousands of dollars per hour. The fix takes less than 30 minutes when you know which register to check.

For reliable Modbus integration between GE RX3i and Yokogawa CENTUM VP, consider using a dedicated Modbus communication module to bridge protocol differences and simplify troubleshooting.