Robot TCP calibration: the four-point method

Calibrate a robot tool centre point with the four-point and six-point methods, identify payload, verify with a dial indicator, and know what accuracy to expect.

Reference
RE-675
Published
Updated
Read
8 min

About the author · Sources, testing and AI policy

Robot arm tool tip touching a sharp calibration point beside a dial indicator

A tool centre point (TCP) that is 3 mm wrong does not give a 3 mm error. Turn the wrist 180 degrees and the tip lands 6 mm from where the program says it is. Re-teaching points hides this at one orientation and exposes it at the next. This guide covers the four-point method, a worked error calculation, a rotate-and-watch check, and when to calibrate again. Positioning terms follow ISO 9283.

What a TCP is

The TCP is the origin of the tool frame, stored as an offset from the robot’s flange: X, Y, Z plus three rotations. When you command a Cartesian pose, the controller solves the joint angles so this point, not the flange, reaches the target.

Three frames get mixed up. The base frame is fixed to the robot, the flange frame is where the tool bolts on, and your TCP defines the tool frame. A program written in tool coordinates behaves differently from the same numbers in base coordinates.

Worked example: how a TCP error grows

Say the real tool tip is 150 mm from the flange along the tool Z axis, but the stored TCP says 147 mm. The error d is 3 mm, fixed in the tool frame.

With the tool pointing straight down, the tip sits 3 mm off the target. That looks like a constant offset, so an operator re-teaches the point and the problem seems gone.

Now reorient the tool by an angle θ at the same target. The error vector turns with the tool, so the difference between the two tip positions is:

shift = 2 × d × sin(θ / 2) (the largest case, when the error is perpendicular to the turning axis)

Wrist turn θTip shift for d = 3 mm
30°2 × 3 × sin 15° = 1.55 mm
90°2 × 3 × sin 45° = 4.24 mm
180°2 × 3 × sin 90° = 6.00 mm

The shift can never exceed 2d. A TCP error is worth fixing before anything else, but it does not grow without limit: the 3 mm error caps at 6 mm.

Orientation errors behave differently because the tool length multiplies them. A tool-axis direction that is 1° off, at 150 mm from the TCP, puts the tip off by 150 × sin 1° = 2.62 mm. At 0.1° it is 0.26 mm. A short pointer hides orientation errors; a long welding torch does not.

Error budget: a common metrology rule of thumb is to keep the setting error at one quarter of the tolerance you are trying to hold. If a dispensed bead must land within ±0.5 mm, aim for a TCP error of about 0.12 mm or better. That figure is a rule of thumb, not a standard; set yours from your process.

The four-point method, step by step

You need a sharp reference point fixed in the cell: a calibration tip in a holder, a needle in a block or a conical target. The robot touches that same physical point from four different wrist orientations. The controller fits a sphere through the four flange positions, and the sphere centre is the TCP.

  1. Fit a pointer. Use a rigid, machined tip. A bent welding wire gives a bent answer.
  2. Choose four orientations. Spread them widely: forward, left, right and back, tilted well apart. Four nearly identical angles make the sphere fit unstable.
  3. Approach slowly. Jog in small steps for the last few millimetres. Hitting the point bends the tip and moves the reference.
  4. Record each point. Touch, check by eye from two directions, store. Redo any point that felt uncertain.
  5. Read the fit error. Most controllers report it. Compare it with your error budget, not with a fixed number.
  6. Add orientation. Four points give position only. A six-point or similar method adds the tool Z and X directions so the frame is fully defined.
  7. Name and save it. Store the TCP under its tool number with the date and who calibrated it.

Every major brand has a guided routine, and the number of points, the naming and the menus differ between brands and controller generations. Follow your controller’s manual for the exact sequence.

Payload belongs in the same session

The controller also needs the tool mass and centre of gravity to compensate gravity and limit acceleration. Declaring a heavy tool as a light one can cause overshoot, position error at speed and overload alarms that look like mechanical faults.

Most controllers offer an automatic payload identification routine. Run it with the real tool and the real cables attached. A cable bundle dragging on the fixture changes the answer.

Verify before you trust it

Touch the reference point, then rotate the wrist around the TCP. A correct TCP stays on the point. A wrong one traces a small circle around it, and the circle’s diameter is about twice your error.

So a 1.2 mm circle means a TCP error of roughly 0.6 mm. This check takes a minute and catches most mistakes.

Tighter work: mount a dial indicator on the fixture and rotate the tool against it. Welding: run a test seam on scrap and cut a cross-section. Dispensing: lay a bead on paper and measure it against the fixture datums.

If you see this, do this

  • If every path is out by the same small amount, check the TCP first with the rotate-and-watch test.
  • If paths are right at one orientation and wrong at another, the TCP is wrong; re-teaching points will not fix it.
  • If the robot crashed or the tool was knocked, re-verify the TCP before the next production run.
  • If you changed the tool, a torch tip or a gripper finger, calibrate again, including payload.
  • If the TCP is good but parts are still off, look at repeatability against accuracy and at the part fixture, not at the TCP.

Mistakes that ruin a calibration

MistakeEffectFix
Four nearly identical orientationsUnstable sphere fit, large errorSpread orientations across the workspace
Flexible pointerEach touch deflects differentlyUse a rigid machined tip
Approaching at speedOvershoot and a bent tipJog the last few millimetres
Calibrating with a dummy toolReal tool offset differsUse the production tool and cables
Forgetting payloadOvershoot and overload alarmsRun payload identification after the TCP
No re-check after a crashSlow drift in qualityVerify the TCP after any collision

What you need to buy

Most small cells need a machined calibration tip that fits your tool holder and a magnetic-base dial indicator for verification. Laser calibration services and laser trackers are for cells where absolute accuracy, not repeatability, is the requirement, such as vision-guided assembly or large workpieces. Prices vary with the shop and the tool holder; ask for a quote rather than planning around a number from a web page.

Related: industrial robot programming, industrial robot cost in India, robot vision cameras, cobot buying guide, robot arm kinematics.

Frequently asked questions

What is TCP in a robot?

The tool centre point is the origin of the tool coordinate system, defined relative to the robot flange. The controller uses it to place and orient the tool in space.

How many points do I need for TCP calibration?

Four points give position. A six-point routine adds tool orientation. A careful four-point calibration can be enough for pick and place, while welding and dispensing usually need orientation too.

Why does my robot drift after calibration?

Common causes are a flexible pointer, orientations too close together, calibrating with a different tool, or a missing payload. Run the rotate-and-watch test to see which.

Can I calibrate a TCP without a reference point?

The four-point method needs a fixed, rigid physical reference. Some controllers offer touch-probe or laser routines, but they still rely on a known target.

How often should a TCP be checked?

After mounting a tool, after any collision, and at planned maintenance intervals. In high-accuracy cells, check at the start of each production run.

Calibration drifts with wear and crashes, so it belongs in the robot maintenance checklist.

Calibration fixes accuracy; this comparison explains why repeatability can still look good on a badly calibrated robot.

Frames are the foundation of both calibration and jogging; see tool and user frames explained.

Calibrate the tool first, then the camera, as the vision-guided robotics guide explains, and see camera calibration for the second half.

Program positions are only as good as the tool frame, and the RAPID guide explains why the tool must be defined first.

Programs from offline programming software depend on an accurate TCP, so calibrate before the first dry run. Seam tracking sensors are defined in tool space too, so tracking needs a correct TCP first.

Sources and further reading

  • ISO 9283: performance criteria and test methods for industrial robots, including pose accuracy and repeatability.
  • ABB robot manuals: TCP definition and calibration routines for IRC5 and OmniCore controllers.
  • FANUC: tool frame setup procedures.
  • Universal Robots manuals: TCP configuration for cobot installations.

Last reviewed: November 2026. The error formulas above are geometry, not measured results. The one-quarter error budget is a general rule of thumb.

Pass it onWhatsAppLinkedIn

Keep reading

Continue learning

Free: the final-year project pack

A shortlist with BOMs, a report outline that matches the usual chapter scheme, a costing sheet and 40 viva questions. Built for the February–April submission season.

The Build Note

One short email when something is worth your bench time.

A new build sheet, a part price that moved, or a mistake worth avoiding. No daily drip, no recycled news.

One short email when a build or a price is worth your time. Unsubscribe in one click.