HG Atelier / The Operator Switch
Technical Systems / Systems-03

Fault Isolation

A symptom tells you where a problem became visible. It does not tell you where the problem began. This lesson trains the discipline of finding the first state that stopped matching the model before changing the system.

The objective is not to make the warning disappear. It is to restore a trustworthy system state and prove that the explanation survived an independent check. If the system gives you numbers, ask what relationship should connect them.
Walkthrough / before the instrument

Here is what you are about to do.

You are not being asked to know electronics from memory. You will be given a system model and its reference relationships, then use them to decide what should be true, what to measure, what the evidence means, and whether a repair actually restored the system.

End capability
Given an unfamiliar but bounded system, externalize the model, preserve rival explanations, buy discriminating evidence, locate the first abnormal boundary, make a bounded change, and prove recovery.
The case

A temperature logger says 57.5 °C. A trusted reference says 24.0 °C.

The display is wrong, but that does not tell you which part is wrong. You will trace a small signal chain from physical temperature to sensor voltage, buffer output, ADC conversion, software, and display.

  • The equations and released reference values stay available.
  • You get only three diagnostic measurements before intervention.
  • You must predict before revealing each result.
  • A cosmetic fix will not pass independent verification.
  • At the end, you will transfer the same method to a different Black Knight telemetry fault.
If the system gives you numbers, ask what relationship should connect them.
Reference access is not a failure of competence.
01 / ModelBuild the expected state.Use supplied relationships to calculate what healthy boundaries should show.
02 / HypothesesKeep serious rivals alive.Translate possible causes into different observable predictions.
03 / TestBuy information.Choose a boundary and relationship before the measurement appears.
04 / DiagnoseFind the first break.Use expected versus observed state to localize the smallest supported fault region.
05 / Act + VerifyChange one justified thing.Predeclare recovery checks, intervene, then prove the explanation survived.
06 / Transfer + RecordUse the method again.Solve a structurally similar but physically different telemetry problem and preserve the causal record.
You will always know what stage you are in and why it comes next.
Situation → teach → derive expected state

Start with the system you think you have.

A low-voltage environmental logger is being checked against a calibrated 24.0 °C reference block. Its display reports 57.5 °C and raises a high-temperature warning. You are authorized to use the designated 0–5 V test points and to swap the plug-in ADC reference module. You are not authorized to redesign the circuit or work on hazardous energized equipment.

Capability
Locate the first abnormal state, choose a discriminating test, make one bounded intervention, and verify recovery against predeclared expectations.
Method / what the walkthrough becomes

Diagnosis is a comparison problem.

Model
Name the states and transformations that should connect cause to indication.
Expected state
Derive what should be observable at useful boundaries before measuring.
Discrepancy
The first point where observed state no longer matches expected state bounds the fault region.
Discriminating test
Prefer a measurement that makes plausible hypotheses predict different results.
Verification
Declare what must become true before the intervention. A green display is not an independent check.
What is being assessed

Not equation recall.

  • Recognize which relationship applies.
  • Use the supplied relationship correctly.
  • Check scale and units.
  • Interpret whether the result fits the proposed mechanism.
Standing lawReference access is not a failure of competence. The task is to choose and apply the right relationship, not recite it from memory.
Training system: temperature signal chain
The values are synthetic but internally consistent. Equations stay visible throughout the lesson.
Temperature signal chain and test-point modelA 24 degree reference block feeds a temperature sensor, then a gain-of-two buffer, then a twelve-bit ADC using a 2.5 volt reference, then software conversion and the display. The learner derives the expected sensor voltage, buffer voltage and ADC counts from supplied relationships. REFERENCE24.0 °Cindependent SENSORVS = ?TP-S BUFFER ×2VB = ?TP-B 12-BIT ADCcode = ?VREF 2.50 VTP-REF CONVERSIONexpected ?display CAL INPUT1.000 V → ?
Temperature sensorVS = 0.50 V + (0.010 V/°C)T

T is temperature in °C. The constant and slope are supplied by the sensor model.

BufferVB = 2VS

The buffer's released gain is 2.

12-bit ADCN ≈ 4095 × VIN / VREF

N is ADC count. Lower VREF raises the count for the same input.

Relative deviation(observed − expected) / expected

Useful for comparing the direction and scale of a discrepancy.

Worked refresher — not the live answer.
At 20 °C: VS = 0.50 + 0.010×20 = 0.70 V. The buffer gives 1.40 V. With VREF = 2.50 V, the ADC predicts about 4095×1.40/2.50 = 2293 counts.
How to derive the live case
  1. Substitute T = 24.0 °C into the sensor law to get the expected sensor voltage.
  2. Use that voltage as the input to the released ×2 buffer.
  3. Use the resulting buffer voltage as VIN in the 12-bit ADC relationship with VREF = 2.50 V.
  4. Run the same ADC relationship separately for the independent 1.000 V calibration input.
  5. Keep units attached. The arithmetic supports the model; the later diagnostic task is deciding what a mismatch means.
Build the healthy expected state

Use the supplied relationships. Arithmetic is not the point; the point is knowing what should connect the numbers. Values within normal rounding are accepted.

24.0 °C through the sensor law · volts
Buffer gain ×2 · volts
1.48 V input, 2.50 V reference · counts
1.000 V input, 2.50 V reference · counts
Independent reference and reported system valueThe independent temperature reference is 24 degrees Celsius while the system display reports 57.5 degrees Celsius. The discrepancy appears downstream, but the fault location is not yet known.INDEPENDENT REFERENCE24.0 °CSYSTEM DISPLAY57.5 °CSYMPTOM LOCATION ≠ FAULT LOCATION
StateExpected state not yet built
Predict / externalize rivals

Make rival explanations earn different predictions.

The board keeps the reasoning outside your head. Choose two live rivals, then choose a measurement whose expected result differs between them. If both explanations predict the same result, the test cannot discriminate between them.

Rule
A serious hypothesis predicts what should be observed before the observation arrives.
System reference · 24.0 °C trusted reference · display 57.5 °C · nominal VREF 2.50 VOpen model + derivation
Source conditionTrusted block: 24.0 °C. System display: 57.5 °C.
AuthorityUse designated 0–5 V test points; swap plug-in reference module only after evidence supports it.
Sensor lawVS = 0.50 V + (0.010 V/°C)T
Buffer lawVB = 2VS
ADC lawN ≈ 4095 × VIN/VREF
Expected TP-S0.74 V
Expected TP-B1.48 V
Expected countsTemp ≈2424; 1.000 V cal ≈1638.
Derivation: 0.50 + 0.010×24 = 0.74 V → ×2 = 1.48 V → 4095×1.48/2.50 ≈ 2424. Independent calibration: 4095×1.000/2.50 ≈ 1638. These are expectations, not diagnoses.
Rival Hypothesis Board
The independent 24.0 °C reference already weakens “actual temperature high.” It remains visible as a rejected rival, not a selectable live explanation.
HypothesisWhat it predictsHigh-value boundaryEvidence that weakens it
H1 — Actual temperature highLocal reference, TP-S and TP-B should all be high.Independent local temperatureThe calibrated reference at the sensor site remains 24.0 °C.
H2 — Sensor biased highTP-S high; TP-B high; VREF normal; calibration channel normal.TP-STP-S matches the sensor law at 24.0 °C.
H3 — Buffer gain faultTP-S normal; TP-B departs from 2×TP-S; VREF and calibration channel normal.TP-S → TP-BTP-B remains 2×TP-S.
H4 — ADC reference lowTP-S and TP-B normal; TP-REF low; calibration counts inflated.TP-REF + independent calibration channelVREF and calibration channel both match healthy expectation.
H5 — Conversion coefficients wrongAnalog path, VREF and raw calibration counts normal; released configuration does not match.Configuration + raw countReleased coefficients match and raw counts are already wrong.
Rival A
No prediction committed.
Rival B
No prediction committed.
Prediction under Rival A
Prediction under Rival B
Why the board exists

A list of possible causes is not yet reasoning.

The useful step is converting each cause into an observable prediction, then buying the measurement that separates them.

State
Rivals not committed
Operate / quantitative evidence

Buy information, then quantify the discrepancy.

You have three diagnostic measurements before intervention. The reference relationships remain available. Before each result appears, identify the relationship you are using and state what the measurement is supposed to discriminate.

Constraint
Three evidence requests. A successful path must establish an upstream analog state, measure VREF, and use the independent calibration channel.
System reference · 24.0 °C trusted reference · display 57.5 °C · nominal VREF 2.50 VOpen model + derivation
Source conditionTrusted block: 24.0 °C. System display: 57.5 °C.
AuthorityUse designated 0–5 V test points; swap plug-in reference module only after evidence supports it.
Sensor lawVS = 0.50 V + (0.010 V/°C)T
Buffer lawVB = 2VS
ADC lawN ≈ 4095 × VIN/VREF
Expected TP-S0.74 V
Expected TP-B1.48 V
Expected countsTemp ≈2424; 1.000 V cal ≈1638.
Derivation: 0.50 + 0.010×24 = 0.74 V → ×2 = 1.48 V → 4095×1.48/2.50 ≈ 2424. Independent calibration: 4095×1.000/2.50 ≈ 1638. These are expectations, not diagnoses.
Available tests
Relationship reference
V_S = 0.50 + 0.010T — sensor expectation.
V_B = 2V_S — buffer expectation.
N ≈ 4095 V_IN / V_REF — ADC scaling.
(observed−expected)/expected — relative deviation.
Released configuration comparison — use when the question is whether software coefficients changed.
Diagnostic measurement
3 evidence requests remain.
Committed rival test
Stop condition

If you spend the budget without establishing both the causal scale check and an upstream normal state, do not intervene. Restart with a better test strategy.

Interpret / diagnose

Name the first state that broke the model.

A diagnosis should explain every relevant observation with the fewest unsupported assumptions. It should also say what the current evidence does not establish.

Proof target
Diagnosis + first abnormal boundary + surviving uncertainty.
System reference · 24.0 °C trusted reference · display 57.5 °C · nominal VREF 2.50 VOpen model + derivation
Source conditionTrusted block: 24.0 °C. System display: 57.5 °C.
AuthorityUse designated 0–5 V test points; swap plug-in reference module only after evidence supports it.
Sensor lawVS = 0.50 V + (0.010 V/°C)T
Buffer lawVB = 2VS
ADC lawN ≈ 4095 × VIN/VREF
Expected TP-S0.74 V
Expected TP-B1.48 V
Expected countsTemp ≈2424; 1.000 V cal ≈1638.
Derivation: 0.50 + 0.010×24 = 0.74 V → ×2 = 1.48 V → 4095×1.48/2.50 ≈ 2424. Independent calibration: 4095×1.000/2.50 ≈ 1638. These are expectations, not diagnoses.
Evidence ledger
Diagnostic law

The downstream symptom can be honest.

With a low ADC reference, the converter can faithfully report a high code even though the sensor and buffer voltages are normal. The display is wrong about temperature because the measurement chain's reference assumption is wrong.

Boundary

Do not infer a component failure from a single abnormal reading if the reference used to create that reading has not been checked.

Action / bounded intervention

Change the smallest thing your diagnosis actually supports.

You are authorized to swap the plug-in 2.50 V reference module. Before acting, choose the intervention and define the evidence that would count as recovery.

Operational spine
Diagnosis → authorized action → predeclared verification.
System reference · 24.0 °C trusted reference · display 57.5 °C · nominal VREF 2.50 VOpen model + derivation
Source conditionTrusted block: 24.0 °C. System display: 57.5 °C.
AuthorityUse designated 0–5 V test points; swap plug-in reference module only after evidence supports it.
Sensor lawVS = 0.50 V + (0.010 V/°C)T
Buffer lawVB = 2VS
ADC lawN ≈ 4095 × VIN/VREF
Expected TP-S0.74 V
Expected TP-B1.48 V
Expected countsTemp ≈2424; 1.000 V cal ≈1638.
Derivation: 0.50 + 0.010×24 = 0.74 V → ×2 = 1.48 V → 4095×1.48/2.50 ≈ 2424. Independent calibration: 4095×1.000/2.50 ≈ 1638. These are expectations, not diagnoses.
Choose one action
Predeclare recovery

Select the checks that must pass. Choose at least three; the independent reference and ADC reference path must be represented.

Failure mode

Calibration theater

Changing a software offset can make one number look correct while leaving the ADC reference wrong. A cosmetic match is not closure if an independent calibration channel still fails.

State
No intervention committed
Verify / recover

The intervention is not the result.

Compare the post-action state with the criteria you committed before the change. Then classify the outcome as pass, fail or inconclusive.

Closure rule
Expected → observed → pass / fail / inconclusive. Diagnose mismatch before declaring recovery.
System reference · 24.0 °C trusted reference · display 57.5 °C · nominal VREF 2.50 VOpen model + derivation
Source conditionTrusted block: 24.0 °C. System display: 57.5 °C.
AuthorityUse designated 0–5 V test points; swap plug-in reference module only after evidence supports it.
Sensor lawVS = 0.50 V + (0.010 V/°C)T
Buffer lawVB = 2VS
ADC lawN ≈ 4095 × VIN/VREF
Expected TP-S0.74 V
Expected TP-B1.48 V
Expected countsTemp ≈2424; 1.000 V cal ≈1638.
Derivation: 0.50 + 0.010×24 = 0.74 V → ×2 = 1.48 V → 4095×1.48/2.50 ≈ 2424. Independent calibration: 4095×1.000/2.50 ≈ 1638. These are expectations, not diagnoses.
Post-action verification
CheckObservedMeaning
Independent check

The 1.000 V calibration input is valuable because it bypasses the temperature sensor and buffer. If it recovers at the same time as the temperature channel, the diagnosis gains support from a separate path.

Evidence state
Not verified
Cross-context / Black Knight training simulation

Same method. Different physics.

A coolant loop's central display reports 0.91 bar while a local mechanical reference reads 2.10 bar. The training problem is now digital telemetry rather than an analog ADC reference. The method must survive the surface change.

Cross-context test
Find the first abnormal boundary without assuming the previous fault repeats.
Coolant telemetry path
Black Knight coolant telemetry training pathProcess pressure is sensed locally, converted by a node processor, sent through a gateway packet, and shown on a central display. An independent mechanical reference reads 2.10 bar while the central display reads 0.91 bar.PROCESS2.10 bar localTRANSDUCERpressure → signalLOCAL NODEvalue + timeGATEWAYpacket streamCENTRAL0.91 bar
Open reference shelf
Δt = t_current − t_packet — age of a reported state.
Adjacent-boundary agreement — compare the same physical quantity before and after a transformation or handoff.
Sequence progression — a fresh stream should advance in time/sequence rather than repeat an old state indefinitely.
(observed−expected)/expected — relative deviation when scale matters.
Cross-context rule

The previous fault was an analog reference error; this one is a stale digital state. The test is whether the same causal grammar survives when the failed component changes.

Method state
Not yet tested
Record / maintain

Keep the causal record.

The useful record preserves the model, rival mechanisms, discriminating measurements, intervention, and independent verification so another operator can reconstruct why the diagnosis won.

Session scope
Cross-context diagnostic reasoning only; physical bench work remains external.
Fault-isolation record
Next real-world step

Take the method to a safe bench.

Use a low-voltage training circuit, meter, schematic and known reference to practice tracing expected state through a real signal path. Work only within equipment and energy levels you are trained and authorized to handle.

Maintenance

Keep the method current by diagnosing unfamiliar but bounded systems. If practice becomes “replace the likely part until it works,” the capability has degraded even if the vocabulary remains familiar.

← Operator Switch