A tightening tool's torques pass a wheel or send it to rework. See what changed, and what didn't.
A tightening tool records five bolt torques for a wheel. The pipeline reads the tool's log, checks each torque against a window, and passes the wheel or sends it to rework. A firmware update that changes no reading is shown as exactly that.
Invented example data, recorded when the demo was built. The demo records and compares; it controls nothing. The screenshots are from a build of the same demo: each build gives its runs new fingerprints and times, so those differ from the live demo's, and what the screenshots show is the same.
The pipeline
Three steps, from a tool's log to a station decision.
read_tool_logreads the tightening tool's log: the five bolt torques.torque_checklists each bolt whose torque is outside the window.station_decisionpasses the wheel where no bolt is outside the window, and sends it to rework where one is.
What the demo plants
The runs, and what was changed in each.
| Run | What was changed |
|---|---|
p9-46-torque-baseline | Nothing: the baseline. All five torques are inside the window. |
p9-47-torque-tool-firmware-changed | The tool's firmware, 4.2 to 4.3, a setting of read_tool_log. Its readings are the same. |
p9-48-torque-one-bolt-low | The tool's log: bolt 3 reads 104.2 N·m where it read 119.6. |
What onetrace shows
Each change, located in the record.
The firmware change: a setting moved, the outputs did not
The page names the setting, tool_firmware, 4.2 to 4.3. Every step's output is the same in both runs, so every step reads Same and the comparison says the two runs do not differ. A changed setting is shown even when nothing it touches moves.
One bolt low: first difference at read_tool_log, then rework
The tool's log is an input from outside the pipeline, kept as its digest, so the page shows it changed, and no setting did. read_tool_log is the first difference: bolt 3 reads 104.2 N·m. torque_check lists it outside the 110.0 to 130.0 N·m window, and station_decision says rework where it said pass.
read_tool_log, from its input.
What it doesn't say
A located change, not a reason.
The comparison shows which reading moved and the decision that followed, and that a firmware update changed no reading. It doesn't say why the bolt was under-torqued, or whether the window is right. See what each verdict means and what onetrace does not claim.
Try it yourself: this pipeline in the live demo, or on your machine with pip install onetrace-console and onetrace-console demo --open.