.png)
Changing a 4–20 mA Transmitter Range? Validate Every Dependent Calculation
A transmitter range change affects more than one display. Trace its mapping through the complete monitoring and control path, then verify every dependent value before accepting the change.
Original conceptual illustration; not a specific product, wiring drawing, live software screen or customer installation.
Key takeaways
Record both the old and new engineering ranges.
Trace raw values through every calculation and alarm.
Keep the change time visible in historical records.
1. Treat the replacement as a signal-chain change
A replacement transmitter can produce a healthy current signal while a controller displays the wrong pressure. Matching the connector and the words ‘4–20 mA’ does not establish an equivalent measurement. The receiving equipment also needs the correct relationship between current and engineering units.
Start with the ordered model, output option, lower and upper range values, units and any configured transfer function. A sensor's physical measuring capability, its configured analogue output range and a screen's display range are separate details. Do not assume a unit can be re-ranged in software; some changes require a different instrument.
ProSense's transmitter catalogue contains different measurement and output options. Use the actual instrument documentation and the accepted project schedule to establish the mapping. This guide describes validation of that mapping, rather than instructions for adjusting a particular model.
2. Find every consumer of the measurement
Draw a small dependency map before changing settings. Follow the input channel into the PLC or RTU calculation, local HMI, remote monitoring point, alarm rules, historian and exported reports. Ask whether each consumer receives raw current, a raw input count or an already converted engineering value.
A common mistake is converting twice: the controller sends bar, but a downstream expression still treats the value as milliamps. Another is updating the main display while a separate alarm expression retains the old span. Record the calculation and units at each boundary so a plausible-looking screen cannot hide an inconsistent path.
Include thresholds stored as percentages, raw counts or engineering units. Their meaning after the change depends on that representation. A pressure limit expressed in bar may stay appropriate, while its equivalent current or raw-count threshold changes. The responsible process owner must confirm whether the operational limit itself remains valid.
3. Work through a hypothetical linear example
Assume a linear mapping in which 4 mA represents 0 bar and 20 mA represents 10 bar. At 12 mA, the fraction of span is (12 − 4) / 16 = 0.5, so the indicated pressure is 5 bar. This is a mathematical example, not a specification for a named transmitter.
Now assume an approved replacement maps the same current endpoints to 0–16 bar. At 12 mA the correct engineering value is 8 bar. A receiver left at 0–10 bar still displays 5 bar: communications and input current can both appear normal while the reported value is wrong.
For the assumed linear mapping, engineering value = lower range + ((current − 4) / 16) × span. Apply the instrument's documented transfer function instead where it is non-linear, reversed or otherwise different. Signal fault levels and over-range behaviour also require model-specific verification; do not fold them silently into normal process values.
Original explanatory diagram. Numerical values are hypothetical where shown; verify the actual equipment and project requirements separately.
4. Prepare a controlled acceptance test
Agree the expected values before testing. Use a simulator, isolated test environment or an approved commissioning arrangement suitable for the application. Electrical work, pressure isolation and changes affecting control or protective functions belong with competent people under the site's procedures; do not inject signals into an operating control loop as an informal experiment.
Test a lower, middle and upper point, then check behaviour near each relevant alarm boundary. At every point compare the accepted reference, received raw value, converted value, display and export. Record tolerances from the project's accuracy requirements rather than inventing a universal pass band.
Capture the existing mapping and all dependent point names.
Confirm the approved replacement range, output and transfer function.
Compare expected and observed values through the complete path.
Check alarms and historical interpretation at the change boundary.
Save the accepted configuration and outstanding actions.
5. Protect the meaning of historical data
Record the effective change time and configuration revision. If the historian stores raw current, a report that applies today's span to all past readings can reinterpret old data incorrectly. If it stores engineering values, the old and new values may already be correctly scaled, but the measurement change still deserves an annotation.
Agree how reports handle a window spanning the change. A maintenance record should explain whether the change involved a replacement, a configuration update or both. Preserve the original readings and approved mapping history; a spreadsheet correction with no traceable rule is difficult to support later.
6. Close the change with evidence
Retain the old and new settings, dependency map, expected test points and recorded results together. Include who is responsible for approving operational thresholds and for confirming that each affected consumer has been checked. This is a project responsibility record, not a claim of named-person review of this article.
If a consumer cannot be verified, record it as outstanding and keep the affected result out of operational acceptance. ProSense Solutions can discuss instrument selection and system integration requirements from the actual ranges, interfaces and reporting needs. Send the existing signal-chain details as well as the proposed replacement model.
Useful project resources
Need help with your application?
Send the equipment models, operating ranges, interfaces and acceptance question you need to resolve. ProSense Solutions can discuss the monitoring and automation system scope; installation, safety and supported software functions require project-specific confirmation.
