The short answer
A loop check is a methodical test of one control or instrument signal from end to end. A technician stimulates the field device, or simulates its signal, and confirms the right value shows up in the right place on the control system, with the right scaling and alarms. Then the same is done for outputs: command a valve or motor from the screen and confirm the right device moves.
It sounds obvious. In practice, on a new build or a retrofit with hundreds of signals, loop checks routinely turn up swapped wires, wrong channel addresses, incorrect ranges and alarms that never trigger. Finding those problems before start-up is far cheaper than finding them with product in the pipes.
What gets checked
- The device: correct tag, model, range and installation. Valves fail to the correct position on loss of air or signal.
- The wiring: every terminal along the way matches the loop drawing, shields are grounded at one end only, fuses and barriers are right.
- The I/O: the signal lands on the channel the program expects.
- The logic and screen: scaling, engineering units, alarm limits, interlocks and the tag description on the HMI.
- Outputs: a command from the screen moves the correct valve, damper or starter, in the right direction, and feedback confirms it.
How it is done
For analog inputs, the usual approach is to inject a known current at several points across the range and compare what the screen shows. Discrete inputs like level switches and limit switches are actuated, or simulated, and watched for the change of state. Where practical, the real process variable is used, such as pressurizing a transmitter with a hand pump.
Every result goes on a loop check sheet, and the sheet is signed by the technician and usually by the owner's representative or operator. Problems found are fixed and the affected points re-tested.
What loop checks typically find
Every project is different, but the same kinds of problems show up again and again. None of them are exotic, and all of them are much easier to fix on a quiet commissioning day than during a start-up or an upset.
| Finding | What it would have caused |
|---|---|
| Two field wires swapped between channels | Pump 1 status shown as pump 2; operator stops the wrong pump |
| Transmitter range differs from controller scaling | A level or pressure that reads plausibly but wrongly |
| Alarm limit entered in the wrong units | An alarm that never trips, or trips constantly |
| Valve fails open instead of closed | Unsafe response on loss of air or power |
| Shield grounded at both ends | Noisy, jumpy readings that are hard to chase later |
| Tag description copied and not edited | Confusing screens and slow troubleshooting |
A finding is not a failure of the crew that built the system. Loop checks exist because wiring and configuring hundreds of points by hand will always produce a few errors. The goal is to catch them all before anyone depends on the system.
When you need one
- New construction and expansions, as part of commissioning before start-up
- Control system migrations, where every signal moves to new hardware or new terminals. See migrating obsolete PLCs.
- Instrument replacements, to confirm the new device and the controller agree
- After wiring changes in a panel or junction box
- Before relying on a safety function, such as a high-level shutdown or a gas detection trip
Have an operator at the screen during loop checks. They learn the system, they spot tag names that make no sense, and they own the result at start-up.
What makes loop checks go smoothly
Most delays come from preparation, not the testing itself. Before the crew arrives:
- Get current loop drawings or at least an I/O list with tags, ranges and terminal numbers.
- Confirm power is available to panels and field devices, with safe isolation plans for anything that will move.
- Agree who can force or bypass logic during testing, and how forces will be tracked and removed.
- Plan around the process so outputs can be stroked without upsetting production.
Loop checks on live equipment involve energized panels and moving machinery, and in some facilities hazardous locations. They should be carried out by instrument technicians and electricians working to your site's safety procedures and lockout rules.
What you should get at the end
A complete set of signed loop sheets, a punch list of anything deferred, and marked-up drawings reflecting what was actually built. Those records become the foundation of your calibration program and make future troubleshooting much faster. Our loop checks and commissioning team can run the process for new work or a migration.
Common questions
Is a loop check the same as commissioning?
It is one part of it. Commissioning also covers equipment start-up, control tuning, sequence testing and handover. Loop checks are the signal-by-signal foundation underneath.
How long do loop checks take?
It depends on the number of points, how ready the site is, and how many problems turn up. Good drawings and a ready control system make the biggest difference.
Can the PLC programmer do loop checks remotely?
Partly. The programmer can watch the screen remotely, but someone still has to be in the field to stimulate devices, check terminations and watch valves move.
Do we need loop checks after replacing a like-for-like transmitter?
A short one, yes. Confirming the range and scaling at the controller takes little time and catches a common source of wrong readings.
Codes and permit rules change and every building is different. For work on your system, talk to a licensed electrician and your local permit authority.