Cold Loop and Hot Loop Testing: Step-by-Step Procedures for Instrumentation Commissioning

Share:

Commissioning · Loop Testing · Pre-Commissioning · Instrumentation

Cold Loop and Hot Loop Testing: Complete Step-by-Step Guide for Instrumentation Commissioning

A complete practical guide to cold loop and hot loop testing in process plant commissioning: what each test checks, when it is performed, step-by-step procedures for both analog and digital loops, tools and documentation required, common failures found at each stage, and how cold and hot loop testing fit into the full commissioning sequence.

Step-by-Step Procedures Analog and Digital Loops Commissioning Phase Diagram Documentation Checklist

Before a process plant can be handed over for startup, every single instrument loop must be tested. Not just wired and labeled: tested. The wiring must be confirmed continuous from field junction box to marshalling panel to AI card. The transmitter must be powered and confirmed to produce a signal at the correct address. The DCS or PLC must show that signal at the correct value on the correct tag. The control output must drive the field actuator correctly. And the closed-loop control function must hold setpoint under simulated or real process conditions.

No single test does all of this. That is why instrumentation commissioning is divided into two distinct phases: cold loop testing and hot loop testing. Each phase has a defined scope, specific tools, a defined acceptance criterion, and produces its own set of documentation. Skipping one or mixing the two is a common cause of commissioning delays: starting hot loop testing before cold loop testing is complete always reveals wiring faults that should have been caught earlier, at lower risk and lower cost.

This guide explains both tests completely: what each one checks and why, the step-by-step procedure for analog measurement loops, digital (discrete) loops and control loops, the tools needed for each phase, the documentation produced, and how both tests fit into the overall pre-commissioning and commissioning sequence. For context on the 4-20 mA signal being tested in these procedures, see our guide on the 4-20 mA current loop explained.

What this guide covers
What cold loop testing is: definition, scope and acceptance criteria
What hot loop testing is: definition, scope and acceptance criteria
Where each test fits in the full commissioning phase sequence
Step-by-step cold loop testing procedure for analog 4-20 mA input loops
Step-by-step cold loop testing procedure for digital (discrete) input and output loops
Step-by-step hot loop testing procedure for analog measurement loops
Step-by-step hot loop testing procedure for control loops (transmitter to controller to valve)
Tools and equipment needed for cold loop and hot loop testing
Common faults found during cold loop testing and their causes
Common faults found during hot loop testing and their causes
Documentation and records required for each test phase
The difference between cold loop, hot loop and loop checking (terminology clarified)
Safety considerations for hot loop testing in live process environments
Advertisement
Advertisement

Where Cold and Hot Loop Testing Fit in the Commissioning Sequence

Commissioning a process plant follows a defined sequence of phases. Each phase has a clear set of prerequisites that must be completed before the next phase begins. Cold loop and hot loop testing occupy specific positions in this sequence and have mandatory entry and exit criteria.

Phase 1: Installation
No loop testing yet
Instrument installation, cable pulling, cable termination, cable tagging, junction box wiring. No power applied to field devices.
Phase 2: Pre-Commissioning
COLD LOOP TESTING
System still de-energised or only partially energised. Wiring continuity, I/O card mapping, instrument calibration checks. No live process signals.
Phase 3: Commissioning
HOT LOOP TESTING
System powered, instruments live, process simulation or actual process fluid introduced. Full signal path and control loop functional verification.
Phase 4: Startup
Ready for operation
All loops hot loop tested and signed off. Plant ready for startup. PID tuning completed. Operators trained. Handover package complete.
Critical rule: cold loop testing must be complete before hot loop testing begins
Starting hot loop testing on a loop that has not passed cold loop testing wastes time and creates safety risk. If a wiring fault causes an AI card short when the transmitter is powered during hot loop testing, the card may be damaged. If a control output is incorrectly wired, energising it during hot loop testing could drive the wrong actuator in the process. Cold loop testing at zero energy finds these faults cheaply. Hot loop testing at live voltage finds them expensively and dangerously.

What Is Cold Loop Testing?

Cold loop testing is the systematic verification of wiring continuity, signal path mapping, I/O card assignment and instrument identity across every instrument loop in the system, performed with the system de-energised or with only panel power available. No process power or live field signals are present. A loop is "cold" because the field devices and process are not yet energised.

What cold loop testing confirms
  • The cable from the field instrument arrives at the correct terminal in the correct junction box
  • The cable from the junction box arrives at the correct terminal in the marshalling panel
  • The marshalling terminal connects correctly to the assigned channel of the correct I/O card
  • The I/O card channel is configured in the DCS or PLC to the correct tag name and engineering units
  • There are no open circuits, short circuits or crossed connections in any of the cable segments
  • The instrument is installed at the correct process connection (correct tag, correct location)
  • All cable shields are correctly terminated (one end only, at the panel end)
Figure 1: Cold Loop Test vs Hot Loop Test Setup: What Is Checked at Each Stage
COLD LOOP TEST: Wiring continuity only. System de-energised. TRANSMITTER (unpowered) Jumper or short at TX Continuity? JB Continuity? MARSH. PANEL Correct card? I/O CARD Ch. 04 DCS / PLC Tag: FT-101? Tag OK? MULTIMETER HOT LOOP TEST: Live signal end-to-end. System energised. TRANSMITTER LIVE: 12 mA JB MARSH. PANEL I/O CARD 12.0 mA DCS / PLC FT-101: 50.0% 320 m³/h HART COMM. Hot loop test verifies the complete live signal path: transmitter output to DCS tag display, with correct engineering units and correct value.

Figure 1: Cold loop testing (top, blue) verifies wiring continuity at zero energy using a multimeter or loop calibrator. Hot loop testing (bottom, red) verifies the complete live signal path from powered transmitter through to correct DCS/PLC tag display with correct value and engineering units.

Cold Loop Testing Procedure: Step by Step

Analog Input Loop (4-20 mA Transmitter to DCS/PLC AI Card)

1
Verify instrument identity and installation
Confirm the transmitter tag number on the instrument nameplate matches the loop diagram. Confirm it is installed at the correct process connection (correct nozzle, correct pipe, correct vessel). Check the transmitter is correctly oriented (pressure port facing process, RTD inserted to correct depth, etc.).
2
Locate the field cable at the transmitter head or local junction box
Open the transmitter head or local JB. Identify the signal cable (usually two-core shielded, marked with the loop number). Do NOT connect the cable to the transmitter terminals yet. You need the cable ends free for continuity testing.
3
Place a temporary short (jumper) across the cable cores at the field end
Short the + and - cable cores together at the transmitter/JB end. This creates a closed circuit that can be detected by a continuity tester or multimeter at the panel end. Some commissioning teams use a resistor (e.g. 100 ohm) to allow current measurement rather than just continuity.
4
Verify continuity at the marshalling panel terminal
At the marshalling panel, locate the terminal corresponding to the loop number on the cable schedule. Measure continuity between the + and - terminals. Resistance should be close to zero (or the resistor value if a resistor was installed). If open circuit, the cable has a break or wrong termination. If low resistance on the shield to core, there is a shield-to-conductor fault.
5
Verify cable routing to the correct I/O card channel
Trace the cable from the marshalling terminal to the I/O card channel. Confirm the channel number matches the I/O assignment sheet. Use the ohmmeter at the I/O card terminal to confirm the short placed at the field end is visible. This verifies the full path: field to JB to marshalling to I/O card.
6
Confirm I/O card channel tag in DCS/PLC configuration
With the panel engineer, confirm the I/O card channel is assigned to the correct tag name, engineering range (e.g. 0-1000 m³/h) and units. Some commissioning teams inject a test signal from a loop calibrator at the I/O card terminals to verify the DCS reads the correct value (4 mA = 0%, 20 mA = 100%). This is the furthest into "hot" territory that some teams go during cold loop testing.
7
Record results, sign off and remove jumpers
Record the test result (PASS / FAIL) on the cold loop test sheet for this loop. If PASS, remove the temporary short at the field end. Do not reconnect the transmitter terminals yet if the transmitter has not been calibrated and inspected. Mark the loop as "Cold Loop Complete" in the commissioning tracking system.

Digital (Discrete) Input Loop (Field Switch to DCS/PLC DI Card)

1
Confirm switch tag, location and type (NO or NC)
Verify the switch tag matches the cause-and-effect or I/O list. Confirm whether the switch is normally-open (NO) or normally-closed (NC) and that the DI card channel is configured to match.
2
Operate the switch manually and verify at panel
One technician manually operates the switch at the field (opens or closes). A second technician observes the DI channel state at the marshalling or I/O card using a multimeter or the DCS/PLC monitor. The state change must match the expected logic (NC switch: closed = 0 V across terminals; open = voltage present).
3
Verify tag and logic in DCS/PLC
Confirm the correct tag changes state in the DCS graphics or PLC IO monitor when the switch is operated. Confirm the logic (OPEN = alarm/trip or CLOSED = alarm/trip) matches the cause-and-effect matrix.
Advertisement
Advertisement

Tools and Equipment for Cold Loop Testing

ToolUsed forRequired for
Digital multimeter (DMM)Continuity measurement between cable cores and from core to screen. Resistance measurement to detect short circuits.All analog and digital loops
Loop calibrator (e.g. Fluke 707, Beamex)Injecting a known 4-20 mA signal at the panel terminals to verify DCS reads correct engineering value without needing the transmitter powered.Analog AI loop verification at panel end
Short circuit jumpers / test leadsTemporarily shorting cable cores at field end to create a detectable circuit for continuity testing at the panel end.All loops
Megohmmeter (insulation tester)Measuring insulation resistance between cable cores and between cores and shield. Values below 100 MOhm indicate cable damage, moisture ingress or incorrect shield termination.All cables over 50 m, all cables in wet or underground conditions
Radio / walkie-talkie or mobile phoneCommunication between field technician and panel engineer during the two-person test sequence.All loops
Loop drawing set / I/O list / cable scheduleReference documents confirming correct cable numbers, terminal numbers, I/O card addresses and tag assignments.All loops
Cold loop test sheet / commissioning databaseRecording pass/fail status, date, technician name and any remedial actions for each loop tested.All loops. Required for handover documentation.

Common Faults Found During Cold Loop Testing

Fault foundTypical causeRemedial action
Open circuit on one or both coresCable damaged during installation (pulled over sharp edge, crushed by cable tray cover). Terminal screw not tightened on a wire. Wire cut too short and pulled out of gland. Incorrect core connected to wrong terminal and the correct terminal left empty.Trace cable with tone generator to find damaged segment. Re-terminate loose connections. Replace damaged cable section.
Short circuit between + and - coresCable damage (cores touching). Incorrect termination (two wires connected to same terminal). Moisture inside cable gland or junction box causing insulation breakdown.Megger the cable to locate fault position. Open all intermediate junction boxes and test each segment independently. Dry out cable if moisture is the cause.
Core-to-shield shortShield drain wire accidentally terminated with signal cores. Damaged cable with compromised insulation.Check shield termination at both ends. Shield should only be terminated at one end (panel end). Float the shield at field end.
Cable arrives at wrong terminal / wrong card channelCable routing error during installation. Wrong cable pulled into the panel. Cable tagging error.Retrace cable with tone generator. Move termination to correct terminal. Update as-built drawings.
Wrong tag in DCS/PLC for the I/O channelI/O list used for DCS configuration was an earlier revision. Configuration not updated to match final installation.Update DCS/PLC configuration to match the latest approved I/O list. Configuration change must go through a management of change (MOC) process on operating plants.
Instrument installed at wrong location (wrong process nozzle)Installation carried out from an old revision of the isometric drawing. Tag label transferred to wrong instrument.Verify instrument serial number against purchase order. Relocate instrument to correct nozzle. Update as-built drawings.

What Is Hot Loop Testing?

Hot loop testing is the verification of a complete instrument loop under live energised conditions with the instrument powered and producing a real or simulated signal. It confirms that the complete signal chain from field device to DCS/PLC to operator display (and for control loops, from controller output to final control element) works correctly and gives accurate readings.

Hot loop testing begins only after cold loop testing is complete and signed off for each loop. The system is now powered: the transmitter has its supply voltage, the DCS I/O cards are active, the control outputs are enabled (with appropriate process safety measures in place), and the HART communicator can communicate with the smart transmitter.

What hot loop testing confirms
  • The transmitter powers up and produces a live 4-20 mA signal within NAMUR NE43 normal range (3.8-20.0 mA)
  • The DCS/PLC AI channel displays the correct engineering value for the simulated or injected signal
  • The HART device descriptor loads correctly and the tag is confirmed in the transmitter (not just at the DCS)
  • The transmitter zero and span are correctly set for the process range on the datasheet
  • The display/HMI shows the correct tag, correct units, and a believable engineering value
  • For control loops: the controller output produces the correct signal at the I/O card DO/AO channel
  • For control loops: the field actuator (control valve, motor, pump) responds correctly to the controller output
  • Alarm and trip setpoints are active and trigger at the correct engineering values
  • Fail-safe positions are verified (control valve goes to correct fail position on loss of signal)
Advertisement
Advertisement

Hot Loop Testing Procedure: Step by Step

Analog Measurement Loop (Transmitter to DCS Display)

1
Confirm cold loop test is signed off and transmitter calibration is complete
Check the commissioning database or test sheet. Do not start hot loop testing for this loop unless its cold loop test sheet is signed and the instrument calibration certificate is on file.
2
Connect the transmitter to the loop and energise
Connect the transmitter signal cable to the transmitter terminals. Apply loop power. Measure the loop current with a clamp meter or inline mA meter. It should read within the NAMUR NE43 normal range (3.8-20.0 mA). If the transmitter is not seeing the process variable, it typically reads 4 mA (live zero).
3
Connect HART communicator and confirm device identity
Connect the HART communicator across the loop (at the marshalling terminal or transmitter terminals, anywhere in the loop). Confirm the device descriptor loads correctly: manufacturer, model, tag number, software revision, process range (LRV and URV). The tag programmed in the transmitter must match the DCS tag and the loop diagram.
4
Apply a process simulation and verify DCS display
Using a loop calibrator in source mode, inject 4 mA, 12 mA and 20 mA into the loop (at the transmitter terminals or bypassing the transmitter if it is not yet connected to process). At each injection point, verify the DCS/PLC tag shows the correct engineering value: at 4 mA it must read 0% or the LRV, at 12 mA it must read 50% or the midpoint, at 20 mA it must read 100% or the URV.
5
Verify alarms trigger at correct setpoints
Simulate the signal through the configured alarm setpoints (low-low, low, high, high-high). Confirm each alarm appears on the DCS alarm summary at the correct setpoint value, with the correct tag, correct alarm text, and correct priority.
6
Record results on the hot loop test sheet and sign off
Record the 0%, 50% and 100% values observed on the DCS and compare to the expected values. Record the HART communicator readings. Record all alarm test results. Both the commissioning engineer and the panel engineer must sign the hot loop test sheet before the loop is considered complete.

Control Loop (Transmitter to Controller to Control Valve)

1
Complete measurement loop hot test first
The feedback transmitter (PV input) must pass its hot loop test before the full control loop can be tested. The controller cannot be verified if its process variable input is not confirmed correct.
2
Verify controller output signal at I/O card AO channel
With the controller in MANUAL mode at 0%, 50% and 100% output, measure the actual mA signal at the AO card terminals. Should be 4, 12 and 20 mA respectively. If the output reads correctly, the controller-to-marshalling wiring is confirmed.
3
Verify the I/P converter or positioner receives and responds to the output
Confirm the 4-20 mA output arrives at the I/P converter or smart positioner. For a pneumatic I/P: verify the output air pressure (3-15 psi or 0.2-1.0 bar) varies correctly with the mA input. For a smart positioner: use HART communicator to read actual valve position and confirm it tracks the mA demand signal.
4
Stroke the control valve to fully open and fully closed
From the DCS in MANUAL mode, drive the output to 0% and verify the valve strokes to its fail position. Drive to 100% and verify the valve moves to the opposite extreme. Check the valve action (fail open / fail close) matches the design intent in the cause-and-effect matrix and the valve datasheet.
5
Verify fail-safe position on loss of signal
Disconnect the output signal cable and verify the valve moves to its specified fail-safe position (fail open, fail close or fail-in-last-position) as defined on the valve datasheet and P&ID. Reconnect and confirm valve returns to the commanded position. Record fail-safe action confirmed.

Cold Loop Testing vs Hot Loop Testing: Complete Comparison

ParameterCold Loop TestingHot Loop Testing
System power stateDe-energised (no field power)Fully energised (live loop power)
Commissioning phasePre-commissioningCommissioning
Primary purposeVerify wiring continuity and I/O mappingVerify signal accuracy and loop function
Field devicesInstalled but not powered. Cable disconnected at transmitter head.Fully powered and connected. HART communicable.
Signal sourceTemporary short jumper or ohmmeterPowered transmitter or loop calibrator in source mode
DCS/PLC statePanel power only. I/O cards energised for configuration check.Fully operational. All tags live.
Control outputsNot verified (no field power to actuators)Verified: stroking, fail-safe position, positioner response
What is checkedCable continuity, cable routing, terminal numbers, shield grounding, I/O channel assignment, tag nameSignal accuracy (0%, 50%, 100%), HART tag, alarm setpoints, control valve stroke, fail-safe action, engineering units
Primary toolsMultimeter, megohmmeter, jumper leads, loop calibrator (optional)HART communicator, loop calibrator (source mode), clamp meter, DCS engineering workstation
Team sizeMinimum 2: one field, one panelMinimum 2: one field, one panel. Plus DCS engineer for control loop tests.
Safety riskLow. No live voltage in field.Higher. Live signals. Control outputs may move actuators. Work permit required.
Documentation producedCold loop test sheet signed by field technician and panel engineerHot loop test sheet with mA values, DCS readings, alarm test results, valve stroke confirmation
Prerequisite forHot loop testingPre-startup checks and operator training
Advertisement
Advertisement

Documentation Required for Cold and Hot Loop Testing

Both cold loop and hot loop testing must be fully documented to form part of the commissioning handover package. On an operating site, any loop modification also requires these tests to be re-performed and documented under a Management of Change procedure.

Cold loop test sheet: minimum content per loop
  • Loop number and tag
  • Instrument service description
  • Cable number(s) tested
  • Continuity result: PASS / FAIL for each cable segment
  • Insulation resistance measurement result (if applicable)
  • I/O card slot and channel number confirmed
  • DCS/PLC tag name confirmed
  • Engineering range confirmed (LRV to URV)
  • Date of test, name and signature of field technician
  • Date of test, name and signature of panel engineer / commissioning lead
  • Any deviations found and remedial actions taken
Hot loop test sheet: minimum content per loop
  • Loop number, tag and cold loop test sheet reference
  • Transmitter make, model, serial number and calibration certificate reference
  • HART tag confirmed (as read by HART communicator)
  • Signal injection test results: injected mA, expected DCS reading, actual DCS reading, error
  • Alarm setpoints tested and results (each setpoint: value, expected action, actual action)
  • For control loops: controller output at 0%, 50%, 100% measured at AO card terminals
  • Valve stroke test: fully open position, fully closed position, fail-safe position confirmed
  • NAMUR NE43 fault detection test result (below 3.6 mA and above 20.5 mA)
  • Date, technician and engineer signatures
  • Any deviations and corrective actions

External Resources

Further reading on loop testing and commissioning

Quick FAQs

What is the difference between cold loop and hot loop testing?
Cold loop testing verifies wiring continuity and I/O mapping with the system de-energised. Hot loop testing verifies the complete signal path and control loop function with the system live and powered. Cold loop testing must be completed and signed off before hot loop testing begins on any loop.
Can hot loop testing be done without cold loop testing?
Technically possible but strongly inadvisable. Skipping cold loop testing means wiring faults are not found until the transmitter is powered during hot loop testing. A wiring fault under live voltage can damage I/O cards, trip protective devices or drive actuators incorrectly. Cold loop testing at zero energy is always the safer and cheaper approach to finding wiring errors.
What tools are essential for hot loop testing?
A HART communicator (to confirm transmitter tag, range and configuration), a loop calibrator in source mode (to inject known signals for verifying DCS engineering value accuracy), and a clamp meter or inline mA meter (to verify actual loop current). Access to the DCS engineering workstation for viewing live tags and alarm responses is also required.
What is loop checking? Is it the same as cold or hot loop testing?
"Loop checking" is a general term used on many projects to describe the full process of verifying an instrument loop from field device to DCS. It typically refers to what this guide calls hot loop testing: the live, powered verification of the full signal path. However, some organisations use "loop checking" to mean only cold loop testing. Always confirm the specific scope of "loop checking" on your project from the commissioning procedure document.

What we learn today

  • Cold loop testing verifies wiring continuity, I/O mapping and tag assignment with the system de-energised. It uses a multimeter and temporary jumpers. It must be completed and signed off before hot loop testing starts. Faults found here: open circuits, wrong terminal wiring, wrong I/O card channel, wrong tag in DCS.
  • Hot loop testing verifies the complete live signal path with the system energised: transmitter powers up, HART tag confirmed, DCS displays correct engineering value at 0%/50%/100%, alarms trigger at correct setpoints, control valve strokes correctly and reaches its correct fail-safe position on loss of signal.
  • Both tests require two people (field and panel), produce separate signed test sheets, and form part of the commissioning handover package. Never begin hot loop testing on a loop that has not passed cold loop testing. Safety risk in hot loop testing is significantly higher than in cold loop testing because live voltages and actuator movement are involved.

Leave a Reply

Your email address will not be published. Required fields are marked *