Before a new plant or a modified system goes live, someone has to confirm that a signal leaving a field sensor actually arrives - correctly labelled and correctly scaled - on the operator's screen. That confirmation is the loop check. This guide explains what a loop check verifies during commissioning, how it differs from calibration, and how live SCADA tag values speed the verification.
An Instrument Loop Check in one line: A loop check is a commissioning test that verifies the complete signal path of an instrument loop end to end - from the field sensor, through the marshalling and I/O card, into the controller, and up to the HMI or SCADA display. It confirms the loop is wired correctly, mapped to the right tag, and scaled properly, rather than confirming the sensor's accuracy.
An instrument loop is a chain of components: the field sensor or transmitter, the field wiring, the marshalling cabinet, the I/O card, the controller or RTU, and finally the display where an operator reads the value. A loop check walks a known signal through that entire chain and confirms it emerges intact at the top. Typically the technician injects or forces a value at the field end - or drives the transmitter across its range - while an observer at the HMI confirms the corresponding tag moves the right way and shows the right number.
The check is looking for the mundane but common faults that plague new installations: a landed-wrong wire, two swapped signals, a channel mapped to the wrong tag, a reversed signal, or scaling that turns 4-20 mA into the wrong engineering range. Testing several points - low, mid, and high - catches scaling and reversal errors that a single point would miss. The goal is to prove that when this sensor sees a real process value, the operator will see the correct, correctly named value, with nothing crossed or mislabelled between them.
It is easy to blur loop checks and calibration because both exercise an instrument across its range, but they answer different questions. A loop check asks: does the signal get there, to the right place, at the right scale? It is about continuity, tag mapping, and scaling across the whole path from field to screen. It is not testing whether the sensor's reading is true. Calibration asks the opposite: is this instrument's reading accurate against a traceable standard? It is about accuracy at the device, not the integrity of the path.
A loop can pass its loop check perfectly and still contain an uncalibrated, inaccurate transmitter, because the wiring, mapping, and scaling are all correct even though the sensor is off. Conversely a perfectly calibrated instrument is useless if its signal lands on the wrong tag or is scaled wrong at the HMI. That is why commissioning normally involves both: calibrate the instrument so the reading is true, and loop-check the path so the true reading arrives where it belongs. Related to but distinct from loop calibration, which combines a calibration check across the whole loop, the plain loop check is fundamentally a continuity and scaling verification.
Traditionally a loop check needs two people in two places - one forcing a signal at the field or cabinet, another watching the HMI - coordinating by radio and marking off a loop sheet. Live tag values from a cloud SCADA compress that. As the field signal is driven across its range, the tag's value updates in Merobix in real time, and because the platform is reachable from a browser or mobile device, the person at the instrument can watch the tag move without a second observer glued to a fixed HMI.
That immediacy makes mismatches obvious on the spot. If the field end is at mid-range but the tag reads full scale, the scaling or mapping is wrong; if the wrong tag moves, the channel is mis-mapped; if nothing moves, there is a continuity break to find. Merobix does not inject the test signal or replace the loop sheet, but seeing the live tag alongside the applied value turns a slow back-and-forth into a quick confirmation, and the results can be recorded against each tag so the commissioning record shows which loops were checked and passed. On a large commissioning that visibility meaningfully shortens the schedule.
A loop check verifies the signal path end to end - continuity, correct tag mapping, and correct scaling from the field sensor to the HMI. Calibration verifies the accuracy of the instrument's reading against a traceable standard. A loop can pass its loop check yet contain an inaccurate sensor, so commissioning normally does both: calibrate the device and loop-check the path.
Loop checks are done during commissioning of a new system or after modifications to wiring, I/O, or controller configuration. They confirm that every loop was installed and mapped correctly before the plant is handed over or restarted. Testing at several points across the range catches scaling and reversal errors that a single-point check would miss.
A single point can hide scaling and reversal errors - a reversed or mis-scaled signal might happen to match at one value. Driving the loop to low, mid, and high points confirms the tag tracks correctly across the whole range and in the right direction. That exposes swapped signals, wrong engineering ranges, and reversed inputs that one point would not reveal.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.