Industrial Instrumentation in TwinCAT: 4–20 mA, RTD, Thermocouple and Signal Validation

Define the measurement contract

For each instrument record the tag, measured quantity, engineering unit, calibrated range, electrical signal, normal operating band, accuracy requirement, sample requirement, fail direction and alarm limits. Identify whether the channel is used for indication, control, protection, quality evidence or a combination.

The electrical design and PLC software should share the same range and units. A 4–20 mA transmitter configured for 0–16 bar must not be scaled as 0–10 bar in the application.

Convert raw data once

Keep the terminal value and diagnostic status available, but convert them through one owned channel function block. The block should apply the configured raw range, engineering range, clamping policy and filtering, then return value, quality and diagnostic state.

For a linear channel, document the conversion rather than embedding unexplained constants throughout the code. RTD and thermocouple terminals require the correct sensor type, connection method and compensation settings; the terminal diagnostic bits are part of the measurement, not optional metadata.

Quality is separate from value

Return explicit quality states such as good, uncertain, bad, under-range, over-range, wire break, short circuit, stale or substituted. Process logic must define what it does when quality is not good. Holding the last value may be appropriate for display, but it must not silently continue a critical controller forever.

Filtering should be justified by the process dynamics and scan time. Excessive smoothing hides faults and adds control delay. Use separate thresholds and delay timers to prevent alarm chatter instead of distorting the process value.

Commission the complete loop

1. Verify tag, terminal, channel and wiring against the drawings.
2. Simulate at least low, mid and high points with traceable test equipment where appropriate.
3. Confirm raw value, engineering conversion, display, historian value and alarm behaviour.
4. Test wire break, out-of-range and power-loss diagnostics.
5. Record as-found and as-left results, equipment identifier and calibration status.
6. For controlled loops, confirm the final scaled process variable before enabling automatic control.

Practical software interface

A channel structure should contain the raw value, engineering value, unit/range metadata, quality, diagnostic code, alarm states and simulation/substitution status. Simulation and forcing must be clearly indicated, access-controlled where necessary, and removed or accounted for before acceptance.