Home › Guides › Loop Diagrams Explained

Loop Diagrams Explained: Following One Signal from Field to Control Room

Every instrument on a plant — every pressure transmitter, control valve, temperature sensor and switch — belongs to a loop: a complete path that carries a measurement from the process to the control system, or a command from the control system back to the field. The loop diagram is the drawing that documents that path, terminal by terminal, wire by wire. If you can read a loop diagram, you can install a loop, test it, find its faults and hand it over with confidence. If you cannot, you are working blind, tracing cables by trial and error. This guide explains what a loop diagram shows, how its symbols and numbers work, and how to read one against the other drawings that describe the same loop.

The loop check itself — the end-to-end test that proves a loop works — is covered in our loop checks explained guide. The instruments at the field end are covered in instrumentation transmitters explained, and the control systems at the other end in DCS vs PLC explained and SCADA systems explained.

What a loop is, and what a loop diagram shows

A loop is the smallest complete unit of an instrumentation system. Take a pressure transmitter on a vessel: the process pressure acts on the transmitter, the transmitter produces a signal — usually a 4–20 mA current loop — and that signal travels through a field cable to a junction box, then through a multicore cable to a marshalling cabinet, then to an input card in the control system, where it becomes a number on an operator screen and an input to alarms and control logic. The loop diagram draws that entire chain on one sheet, in the order the signal travels.

For an output loop the chain runs the other way. The control system produces an output — say a 4–20 mA signal to a valve positioner — which travels out through the marshalling cabinet and junction boxes to the field device, which moves the valve. Input loops and output loops use the same drawing conventions, so once you can read one, you can read the other; you only need to remember which direction the signal flows.

What the loop diagram deliberately does not show is just as important. It does not show the process — no pipes, no vessels, no flow arrows. That is the job of the piping and instrumentation diagram, the P&ID. It does not show the physical layout of the plant, the cable tray routes or the exact position of the junction boxes. And it usually does not show the internal electronics of the field device, only its terminals and the connections made to them. A loop diagram is a wiring and signal document, and judging it for what it does not show is a common beginner mistake.

The parts of a loop diagram, in signal order

Most loop diagrams read from left to right, or from the field on one side to the control system on the other. The exact layout varies between projects, but the elements are the same, and they appear in the same logical order.

The field device

At one end sits the field instrument, drawn as a symbol with its tag number — for example, a pressure transmitter tagged PT-101. The tag follows the ISA convention: the letters identify the variable and the function, and the number identifies the loop. The drawing shows the device terminals, usually numbered exactly as they are numbered on the device itself, and any links, jumpers or settings that matter, such as a write-protect link or a local display. If the device needs a separate power supply, that supply and its terminals appear here too.

Field cable and junction box

Next comes the field cable: a pair or a small multicore running from the device to the nearest junction box. The diagram shows the cable number, the number of cores, the core colours or numbers, and the screen or shield, including where the screen is earthed. The junction box appears as a row of terminals, and each core lands on a numbered terminal. Junction boxes are where loops are most often miswired, because several loops share one box and the cores of different cables sit side by side. Careful terminal numbering is the only defence.

Multicore cable and marshalling cabinet

From the junction box, a multicore cable carries many loops to the marshalling cabinet, usually in a control room or equipment room. The diagram shows the multicore number, the pair or core allocation for this loop, and the marshalling terminals where the cores land. Marshalling is also where cross-wiring happens: short links or cross-wires connect the field side of the cabinet to the system side, allowing loops to be routed to the right input or output card. The diagram shows both sides of the marshalling terminals and any links between them.

Control system card and software point

At the far end, the loop lands on a control system input or output card: the card number, the channel number and the terminal numbers. The diagram usually also names the software point — the tag as it appears in the control system database — and any signal conditioning, such as range settings or alarm limits, that the loop check must verify. For a loop that includes a safety function, the diagram may also reference the safety system and its voting arrangement, though the safety logic itself lives in separate documents.

Symbols, tags and wire numbers

Loop diagrams use a compact symbol language. Instruments appear as circles or balloons containing their tag letters, following the ISA standard: the first letter is the measured variable (P for pressure, T for temperature, F for flow, L for level), the following letters are functions (T for transmitter, C for controller, V for valve, S for switch, I for indicator, A for alarm). So PT is a pressure transmitter, TT a temperature transmitter, FV a flow valve and XV a solenoid valve. Learning this letter code is the fastest single step toward reading instrumentation drawings fluently.

Wire numbers are the second language, and they are the one that matters most during installation and testing. A wire number identifies one conductor along its whole run. The same number appears at the field device terminal, at the junction box terminal, at the marshalling terminal and at the system card terminal, so you can follow one core through the entire loop without knowing anything else about it. Wire numbers are usually printed on ferrules slipped over the wire ends, and the discipline is simple and absolute: the ferrule, the terminal and the drawing must all agree. A single disagreement means either the drawing or the installation is wrong, and finding out which is the job before any testing begins.

Cable numbers work the same way at a larger scale. Each cable has a unique number that appears on the drawing, on the cable marker at each end, and in the cable schedule. When you are standing at a junction box with a dozen cables entering it, the cable numbers are how you find the right one. The screen or shield of a signal cable gets its own treatment on the drawing: it shows where the screen is connected to earth, and just as importantly, where it is deliberately left unconnected, because earthing a screen at both ends can create circulating currents that inject noise into the measurement.

Reading a loop diagram against the other drawings

No loop diagram stands alone. It sits in a set of documents that describe the same loop from different angles, and a competent engineer cross-checks between them rather than trusting any single sheet.

The P&ID is the starting point. It shows the instrument in its process context: which vessel or line it measures, which valve it controls, and how it relates to neighbouring loops. Before you wire anything, confirm on the P&ID that the tag you are wiring is the tag the process needs, in the location the process needs. Tag errors — wiring the right instrument to the wrong loop — are embarrassingly common and entirely preventable by this one check.

The hook-up drawing, sometimes called the installation detail, shows the physical side: how the instrument is mounted, how the impulse lines or sensor pockets are arranged, how the cable enters the device, and how the cable is glanded and sealed. The loop diagram tells you which terminal each core lands on; the hook-up drawing tells you how the cable physically gets there and stays weatherproof. Both must be satisfied. A loop that is electrically perfect but lets water into the transmitter housing will fail within weeks.

The cable schedule lists every cable in the project: its number, type, size, route, and the equipment at each end. Use it to confirm that the cable you are pulling is the cable the loop diagram calls for, and to plan the order of work. The instrument index, or instrument list, is the master list of every instrument, its tag, its type, its range and its datasheet reference. If a tag appears on a loop diagram but not in the index, or with a different range, that discrepancy must be resolved before installation, not discovered during commissioning.

A worked reading: tracing a pressure loop

Consider a pressure transmitter, PT-101, measuring the pressure in a vessel. On the loop diagram, the transmitter symbol sits at the left, with two terminals marked plus and minus. A twisted pair cable, numbered C-101, runs from those terminals to junction box JB-3, where the pair lands on terminals 5 and 6. The core colours are shown — red to the plus terminal, black to the minus — and the screen is shown connected to earth at the junction box end only.

From JB-3, the pair joins a multicore cable, M-12, as pair 7, and runs to the marshalling cabinet, where it lands on terminals 21 and 22. Cross-wires link those terminals to the system side, terminals 41 and 42, which connect to channel 3 of analogue input card AI-04. The diagram notes the software tag, the 4–20 mA range, and the engineering range of the transmitter. Reading it in this order — device, field cable, junction box, multicore, marshalling, system card — gives you the complete path, and every number along the way is a checkable fact in the field.

Now imagine the loop check fails: the control room sees no signal. The loop diagram tells you exactly where to divide the problem. Measure the loop current at the transmitter terminals: if it is present there, the fault is downstream, and you move to the junction box, then the marshalling cabinet, then the system card, testing at each point. If it is absent at the transmitter, the fault is at the device or its power supply. This method — testing at the points the diagram defines, in signal order — is why loop diagrams exist, and why a tester who works without one is guessing.

Common mistakes and how to avoid them

The most common loop diagram mistakes are not exotic. Swapped cores at a junction box, where two loops in the same box exchange a pair, produce a loop that appears dead and another that reads the wrong process value — dangerous precisely because one of them looks alive. The defence is to verify cable and pair numbers at every termination, not just at the ends. Screens earthed at both ends, or left floating where the drawing calls for an earth, inject noise that appears as an unstable reading, and the cure is to follow the drawing's earthing note exactly, not to improvise.

Another frequent error is working from a superseded revision. Loop diagrams change during a project: tags are added, ranges are revised, cables are re-routed. Always check the revision number and date on the drawing in your hand against the current revision list, and never work from a photocopy of unknown age. Finally, never pencil a change onto a loop diagram and call it done. Field changes must be red-lined, recorded and fed back so the as-built drawing matches the as-installed loop; the next person to test that loop will trust the drawing, and an unrecorded change turns that trust into a fault.

Frequently asked questions

Related guides

Continue with the loop's two ends and its test: loop checks explained for the end-to-end test, instrumentation transmitters explained for the field devices, and PCB design with AI for the board-level side of electronic design. The rest of this cluster covers reading datasheets, the KiCad tutorial for beginners and PCB stackup design. Then browse all guides for the wider LOTICI library.