Skip to content
All analysis

Sector · Robotics · 05 Aug 2026

TCP sheet TV-3: the millimeter that turned into scrap

Tool center point checks, mastering state, and fixture datums decide whether the path still matches the world—robotics TCP verification sheet, not collision dump annotations, not cycle waterfalls, not gripper photo logs.

TCP sheet TV-3: the millimeter that turned into scrap

Sheet: TV-3 · Cell R4 EOAT change
Trigger: Tip replace + weekend mastering
Claim before run: “TCP fine — we taught it last month.”
Format: Verification sheet. Not a kinematics lecture.


Pre-checks (as ticked)

| Check | Tick | Field find | | --- | --- | --- | | Mastering all axes | ☑ | J4 off by one pulse after battery work | | EOAT ID in controller | ☑ | GR-C loaded; mechanical tip was GR-B length | | TCP XYZ verify | ☐ skipped | “no time” | | 4-point / ABC verify | ☐ skipped | — | | Fixture datum touch | ☐ skipped | Datum block missing |

Printed TCP verification checklist on robot cell desk

A skipped TCP line is a pre-authorized miss.


First AUTO result

Path looked “almost.” Insert miss 1.8 mm.
Scrap × 11 before protective stop.
Collision dump blamed geometry; TCP sheet (blank) was the earlier witness.


Required TV-3 closeout

  1. Mastering validate print attached.
  2. EOAT length/ID match mechanical + software.
  3. TCP verify within tolerance (write numbers, not “OK”).
  4. One fixture datum touch recorded.
  5. Dry-run at reduced speed signed before AUTO.

Robot pointer tip at calibration spike for TCP check

If the tip and the number disagree, the path is fiction.


Adjacent fences

Collision dumps own forensic stops. Cycle waterfalls own lost seconds. Gripper photo logs own wear. Payload logs own mass lies. TV-3 owns whether the tool point is still true. Do not teach around a wrong TCP and call it process knowledge.


Close

Millimeters are not opinions. TV-3 makes them signatures—or scrap makes them invoices.

More in this sector