A defensible calibration is a chain of evidence: identify the loop, isolate safely, record as-found points, adjust only when required, verify as-left performance and restore the process.
Follow the workflow
Read the tag, engineering range, supply arrangement and PLC input type. Determine whether the transmitter is loop-powered or separately powered and whether the work requires bypasses or process isolation.
Do this in the product
In the lab, set the engineering minimum and maximum to match the example transmitter.
Open the exerciseApply or observe values at 0, 25, 50, 75 and 100% of span where the procedure requires. Record both input reference and output current before making an adjustment. A five-point up/down test can expose hysteresis.
Do this in the product
Use 4, 8, 12, 16 and 20 mA in the scaling challenge and record the expected engineering values.
Open the exercisePercent span equals (mA − 4) ÷ 16. Engineering value equals minimum plus percent span multiplied by engineering span. A 12 mA signal is 50% span, not 60%.
Do this in the product
Run 12 mA on a 0–100 range; the server grader expects 50 engineering units and shows its formula.
Open the exerciseNear-zero current suggests an open loop or lost power. Values below the normal measurement region or above it may be configured fault signals. Do not “calibrate out” a wiring fault.
Do this in the product
Pro learners can classify live-zero fault regions and keep the graded diagnosis record.
Open the exerciseCore concepts
The simulator creates a repeatable result; these concepts make that result transferable to real vendor software and supervised practical work.
The valid measurement starts at 4 mA so 0 mA can indicate a broken or unpowered loop.
The difference between maximum and minimum engineering values. A −50 to 150 °C transmitter has a 200 °C span.
A reference standard’s calibration chain and uncertainty must support the required tolerance.
Continue in the workspace
Run the foundation exercise publicly, then use a subscription for advanced challenges, saved configurations, full attempt history, sharing, assigned paths and team reporting.
Related learning surfaces
Competency and practice field guide
Direct answer
4–20 mA loop calibration tutorial becomes useful when it connects measurement range, units, lower and upper range values, tolerance, loop supply, transmitter, current path, input mode, raw range, scale, reference standard and as-found record with known process reference through sensor and transmitter to loop current, input conversion, raw value, scaled engineering tag, display and alarm, then proves at least low, midpoint and high reference points produce values within the declared tolerance through the complete loop under normal, boundary, fault and recovery conditions. The objective is a repeatable engineering or learning result, not merely activity inside a page or tool.
This guide is written for instrumentation and PLC learners checking transmitter output, loop current, input raw counts and engineering values at controlled points. The intended result is specific: the learner can document as-found data, test low, midpoint and high points, separate sensor, transmitter, wiring, input and scaling errors and record as-left evidence.
System map / 02
Treat these as connected checkpoints. Each checkpoint has an expected state, an observable state and a boundary to the next part of the system. That structure prevents a software indication from being mistaken for physical proof.
measurement range, units, lower and upper range values, tolerance, loop supply, transmitter, current path, input mode, raw range, scale, reference standard and as-found record. For 4–20 mA loop calibration, scaling and as-found evidence, record the initial condition, actor, requested change, observable result and stopping condition before selecting a tool or implementation.
known process reference through sensor and transmitter to loop current, input conversion, raw value, scaled engineering tag, display and alarm. Separate request, internal state, output or service, physical or user-visible result and independent feedback so each boundary can be inspected.
at least low, midpoint and high reference points produce values within the declared tolerance through the complete loop. Run more than one cycle from a known state and retain the values, timings or artifacts that demonstrate repeatability.
3.6 or 21 mA fault indications, open loop, short, reversed polarity, wrong input mode, offset, span error, nonlinear point and restored wiring. Choose minimum, maximum, simultaneous, delayed or restart conditions that reveal assumptions hidden by the happy path.
a reference, sensor, transmitter, supply, wiring, current, input, raw conversion, scaling or display mismatch. Preserve the first symptom, divide the system at a measurable boundary and change one condition only after predicting the result.
the loop restored, as-left results recorded and affected alarms and control functions retested. Restore normal state, remove temporary changes, repeat affected checks and document which claims remain limited to the learning environment.
Procedure / 03
Run the steps in order the first time. Later, the same structure becomes a diagnostic loop: define the expected condition, observe the boundary, interpret the difference and choose one proving action.
Convert measurement range, units, lower and upper range values, tolerance, loop supply, transmitter, current path, input mode, raw range, scale, reference standard and as-found record into initial conditions, one stimulus and observable pass criteria.
Evidence: Another person can repeat the case without guessing the intended result.
Avoid: Using page completion or an animation as the acceptance criterion.
Document known process reference through sensor and transmitter to loop current, input conversion, raw value, scaled engineering tag, display and alarm and name who owns each state or decision.
Evidence: Every request and result has a source, destination and useful inspection point.
Avoid: Using the same value as command, status and independent feedback.
Apply at least low, midpoint and high reference points produce values within the declared tolerance through the complete loop from a clean start and record the expected evidence.
Evidence: Repeated runs produce the same bounded result.
Avoid: Changing several parameters before a baseline exists.
Test 3.6 or 21 ma fault indications, open loop, short, reversed polarity, wrong input mode, offset, span error, nonlinear point and restored wiring without changing the acceptance contract.
Evidence: Limits, timing and restart behavior reach defined states.
Avoid: Testing only one ideal sequence.
Introduce or analyse a reference, sensor, transmitter, supply, wiring, current, input, raw conversion, scaling or display mismatch and locate the first disagreement.
Evidence: The proving action distinguishes the leading hypotheses.
Avoid: Resetting, forcing or replacing before evidence is retained.
Complete the loop restored, as-left results recorded and affected alarms and control functions retested and repeat the affected regression cases.
Evidence: A learner completes the surface by explaining the result, passing a changed case and identifying what still requires supervised target-equipment practice.
Avoid: Treating an acknowledged message or one successful rerun as handover.
Diagnostic matrix / 04
The table is a reasoning aid, not a parts-replacement chart. Preserve the initial symptom, inspect the named boundary and use the interpretation to choose the next controlled test. Site safety procedures and equipment manuals remain authoritative.
| Observed symptom | Inspect | Interpretation | Next proving action |
|---|---|---|---|
| The expected result is unclear | Requirement, initial state, actor, stimulus, units and pass condition | The learner, instructor and assessor may be solving different versions of the task. | Rewrite one observable acceptance case before continuing. |
| Internal state changes but the outcome does not | Request, final owner, output or service boundary and independent feedback | A software or interface indication proves intent at one layer, not the complete outcome. | Trace the first boundary after the changing state. |
| Normal case passes but an edge case fails | Limits, timing, simultaneous events, reset and restart assumptions | The implementation contains a hidden assumption exposed by the changed condition. | Add the failed boundary as a permanent regression case. |
| The failure disappears after reset | Original symptom, histories, diagnostics, timestamps and active cause | Reset changed evidence or state without proving the initiating cause. | Reproduce under a controlled condition and preserve pre/post-event data. |
| Simulator and target disagree | Model boundary, software version, task timing, I/O behavior, data types and configuration | A learning model and the intended target do not share one of the recorded assumptions. | Reduce the case and verify against current target documentation. |
| The result cannot be explained | Prediction, observation, proving action, alternative hypotheses and limitations | Activity occurred but the evidence is not yet transferable or reviewable. | Have the learner defend the signal path and repeat a changed case. |
Product evidence / 05
The browser platform can retain programs, scenario results, attempts and observable machine state so practice is attached to evidence rather than seat time alone.
A browser tutorial cannot calibrate equipment or prescribe hazardous-area and live-loop methods; use approved instruments, procedures and traceable references.
Commissioning notebook / 06
Use these as written briefs rather than click-through instructions. For every case, state the expected condition before acting, retain the first useful observation and explain why the final result proves the requirement. A different program or component choice can still be correct when it produces the same bounded behavior and evidence.
Case 01
predict → observe → prove
Engineering context. measurement range, units, lower and upper range values, tolerance, loop supply, transmitter, current path, input mode, raw range, scale, reference standard and as-found record. For 4–20 mA loop calibration, scaling and as-found evidence, record the initial condition, actor, requested change, observable result and stopping condition before selecting a tool or implementation. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Write the acceptance case” stage of the workflow: convert measurement range, units, lower and upper range values, tolerance, loop supply, transmitter, current path, input mode, raw range, scale, reference standard and as-found record into initial conditions, one stimulus and observable pass criteria. The acceptance record should show this result: another person can repeat the case without guessing the intended result. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “The expected result is unclear” as one bounded deviation. Inspect requirement, initial state, actor, stimulus, units and pass condition The working interpretation is that the learner, instructor and assessor may be solving different versions of the task. The next proving action is to rewrite one observable acceptance case before continuing. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is using page completion or an animation as the acceptance criterion. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: What points should be checked in a 4–20 mA calibration? A defensible short answer is: Use the procedure-defined points—commonly low, midpoint and high, with additional ascending and descending points when hysteresis or linearity matters.
Case 02
predict → observe → prove
Engineering context. known process reference through sensor and transmitter to loop current, input conversion, raw value, scaled engineering tag, display and alarm. Separate request, internal state, output or service, physical or user-visible result and independent feedback so each boundary can be inspected. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Build the map” stage of the workflow: document known process reference through sensor and transmitter to loop current, input conversion, raw value, scaled engineering tag, display and alarm and name who owns each state or decision. The acceptance record should show this result: every request and result has a source, destination and useful inspection point. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “Internal state changes but the outcome does not” as one bounded deviation. Inspect request, final owner, output or service boundary and independent feedback The working interpretation is that a software or interface indication proves intent at one layer, not the complete outcome. The next proving action is to trace the first boundary after the changing state. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is using the same value as command, status and independent feedback. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: Is 12 mA always 50 percent? A defensible short answer is: It is 50% of an ideal 4–20 mA span, but the engineering value also depends on the configured lower and upper range and any nonlinear mapping.
Case 03
predict → observe → prove
Engineering context. at least low, midpoint and high reference points produce values within the declared tolerance through the complete loop. Run more than one cycle from a known state and retain the values, timings or artifacts that demonstrate repeatability. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Run the baseline” stage of the workflow: apply at least low, midpoint and high reference points produce values within the declared tolerance through the complete loop from a clean start and record the expected evidence. The acceptance record should show this result: repeated runs produce the same bounded result. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “Normal case passes but an edge case fails” as one bounded deviation. Inspect limits, timing, simultaneous events, reset and restart assumptions The working interpretation is that the implementation contains a hidden assumption exposed by the changed condition. The next proving action is to add the failed boundary as a permanent regression case. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is changing several parameters before a baseline exists. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: What should I learn first about 4–20 mA loop calibration, scaling and as-found evidence? A defensible short answer is: Start with the operating contract and evidence path: measurement range, units, lower and upper range values, tolerance, loop supply, transmitter, current path, input mode, raw range, scale, reference standard and as-found record, followed by known process reference through sensor and transmitter to loop current, input conversion, raw value, scaled engineering tag, display and alarm. Add advanced features only after the baseline is predictable.
Case 04
predict → observe → prove
Engineering context. 3.6 or 21 mA fault indications, open loop, short, reversed polarity, wrong input mode, offset, span error, nonlinear point and restored wiring. Choose minimum, maximum, simultaneous, delayed or restart conditions that reveal assumptions hidden by the happy path. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Challenge assumptions” stage of the workflow: test 3.6 or 21 ma fault indications, open loop, short, reversed polarity, wrong input mode, offset, span error, nonlinear point and restored wiring without changing the acceptance contract. The acceptance record should show this result: limits, timing and restart behavior reach defined states. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “The failure disappears after reset” as one bounded deviation. Inspect original symptom, histories, diagnostics, timestamps and active cause The working interpretation is that reset changed evidence or state without proving the initiating cause. The next proving action is to reproduce under a controlled condition and preserve pre/post-event data. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is testing only one ideal sequence. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: How do I practise 4–20 mA loop calibration, scaling and as-found evidence effectively? A defensible short answer is: Use short cases with known initial conditions, a written prediction, one action and an observable result. Then alter a boundary or fault and explain why the evidence changed.
Case 05
predict → observe → prove
Engineering context. a reference, sensor, transmitter, supply, wiring, current, input, raw conversion, scaling or display mismatch. Preserve the first symptom, divide the system at a measurable boundary and change one condition only after predicting the result. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Isolate one failure” stage of the workflow: introduce or analyse a reference, sensor, transmitter, supply, wiring, current, input, raw conversion, scaling or display mismatch and locate the first disagreement. The acceptance record should show this result: the proving action distinguishes the leading hypotheses. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “Simulator and target disagree” as one bounded deviation. Inspect model boundary, software version, task timing, I/O behavior, data types and configuration The working interpretation is that a learning model and the intended target do not share one of the recorded assumptions. The next proving action is to reduce the case and verify against current target documentation. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is resetting, forcing or replacing before evidence is retained. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: What counts as proof of competence? A defensible short answer is: A repeatable artifact or system result plus an explanation of the signal path is stronger than time spent, screenshots or a copied answer. Physical competence requires separate supervised evidence.
Case 06
predict → observe → prove
Engineering context. the loop restored, as-left results recorded and affected alarms and control functions retested. Restore normal state, remove temporary changes, repeat affected checks and document which claims remain limited to the learning environment. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Close the evidence loop” stage of the workflow: complete the loop restored, as-left results recorded and affected alarms and control functions retested and repeat the affected regression cases. The acceptance record should show this result: a learner completes the surface by explaining the result, passing a changed case and identifying what still requires supervised target-equipment practice. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “The result cannot be explained” as one bounded deviation. Inspect prediction, observation, proving action, alternative hypotheses and limitations The working interpretation is that activity occurred but the evidence is not yet transferable or reviewable. The next proving action is to have the learner defend the signal path and repeat a changed case. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is treating an acknowledged message or one successful rerun as handover. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: Why test faults and restart behavior? A defensible short answer is: Because a reference, sensor, transmitter, supply, wiring, current, input, raw conversion, scaling or display mismatch or 3.6 or 21 ma fault indications, open loop, short, reversed polarity, wrong input mode, offset, span error, nonlinear point and restored wiring can expose assumptions that never appear during ideal startup and steady operation.
Answer surface / 07
These concise answers define the operating, training and product boundaries most often missed in broad summaries. The full workflow and diagnostic table above provide the evidence behind them.
Use the procedure-defined points—commonly low, midpoint and high, with additional ascending and descending points when hysteresis or linearity matters.
It is 50% of an ideal 4–20 mA span, but the engineering value also depends on the configured lower and upper range and any nonlinear mapping.
Start with the operating contract and evidence path: measurement range, units, lower and upper range values, tolerance, loop supply, transmitter, current path, input mode, raw range, scale, reference standard and as-found record, followed by known process reference through sensor and transmitter to loop current, input conversion, raw value, scaled engineering tag, display and alarm. Add advanced features only after the baseline is predictable.
Use short cases with known initial conditions, a written prediction, one action and an observable result. Then alter a boundary or fault and explain why the evidence changed.
A repeatable artifact or system result plus an explanation of the signal path is stronger than time spent, screenshots or a copied answer. Physical competence requires separate supervised evidence.
Because a reference, sensor, transmitter, supply, wiring, current, input, raw conversion, scaling or display mismatch or 3.6 or 21 ma fault indications, open loop, short, reversed polarity, wrong input mode, offset, span error, nonlinear point and restored wiring can expose assumptions that never appear during ideal startup and steady operation.
No. It can build concepts and diagnostic reasoning. Exact firmware, I/O electrical behavior, networking, safety and commissioning require current official tools, documentation and target equipment.
Keep the requirement, initial state, program or configuration, observed values, fault hypothesis, proving action, recovery result and a concise limitations statement.
Continue the signal path / 08