Robot Calibration
Camera intrinsics, hand-eye transforms, kinematic zeroes, timing and dynamics: the measurements that make sensor coordinates agree with motion.
- Last reviewed
- Reading time
- 6 min
- Citations
- 9
Calibration makes measurements and commands refer to the same physical world. A camera pixel, depth value, joint encoder and motor command each has its own coordinate system, clock and error. A robot policy can learn around a stable bias; it cannot reliably absorb a transform that changes after every camera bump or a label stream shifted by a variable delay.
The useful unit is not one calibration file. It is a chain with a validation residual at every link: intrinsics, depth, camera-to-robot transform, robot kinematics, time alignment and actuator response.
Try the check below and choose the diagnostic that separates a fixed hand-eye error from random policy error.
Self-check
Read the reasoning
- Inspect the hand-eye rotation and its validation residualA small angular transform error creates lateral position error that grows with working distance. The consistent direction is a calibration signature.
- Collect more demonstrations for the same policyMore data can teach a stable bias, but the distance-dependent systematic direction points to geometry. Fixing the transform removes the error for every policy and dataset.
- Increase the vision encoder parameter countCapacity does not make the camera and robot frames agree. A larger model may conceal the bias on familiar poses and retain the same physical defect.
Systematic, geometry-dependent misses are calibration evidence; measure the transform before changing the learner.
The calibration chain
A manipulation system commonly carries these transforms and models:
- camera intrinsics and lens distortion;
- depth scale and depth-to-color alignment;
- camera extrinsics relative to the robot base or wrist;
- joint encoder zeroes and link parameters;
- tool-center-point and payload parameters;
- timestamps and sensor-to-command latency;
- actuator or controller response.
The output of one stage is the input to the next. A 6-DoF pose estimator can be accurate in camera coordinates and still place the gripper incorrectly because the hand-eye transform is wrong. FoundationPose can estimate and track novel-object poses under model-based or model-free inputs Wen 2024; it does not calibrate the camera to the arm for you.
Camera intrinsics
Intrinsics map pixels to rays. The core parameters are focal lengths, principal point and lens distortion. Zhang's planar-target method recovers them from several views of a flat pattern at unknown orientations, followed by nonlinear refinement Zhang 2000. Its practical strength is that the target pose need not be measured.
Good calibration images cover the full field of view, vary distance and tilt, keep the target sharp, and avoid collecting many near-duplicate views. Report reprojection error and inspect its spatial pattern. A low mean can hide a bad corner of the image or a few dominant views.
Do not transfer intrinsics across a changed focus, resolution or crop without validation. Image resizing requires a corresponding scale of focal length and principal point. A model trained on undistorted images must receive the same transformation at deployment.
Depth is a measurement model
Depth cameras do not produce uniformly accurate metric state. Stereo error grows with range, repetitive patterns create ambiguous matches, and low texture or specular surfaces can invalidate measurements. The RealSense tuning guide describes the distance-squared growth and the effects of scene texture and lighting Grunnet-Jepsen 2026. The D400 family datasheet also documents false depth and saturation failure cases rather than one universal accuracy number RealSense 2026.
Calibrate depth scale against known distances across the operating range. Plot residual against range and image location. Measure invalid-pixel rate on the actual materials in the task. If color and depth sensors are separate, validate their registration after every resolution or firmware change.
Hand-eye calibration
Hand-eye calibration solves the rigid relationship between camera motion and robot motion. For a wrist camera, the unknown is usually the transform from gripper to camera; for a fixed camera, it is base to camera. Shiu and Ahmad wrote the problem as the homogeneous transform equation over paired robot and camera motions and solved it in closed form Shiu 1989; Tsai and Lenz gave the classic efficient solution Tsai 1989.
The dataset needs rotational diversity. Motions around nearly one axis leave parts of the transform weakly constrained. Use many poses across the workspace, reject target detections with poor geometry, and reserve some poses for validation rather than solving on every sample.
Validate in the units the task cares about. Place the calibration target at several distances and orientations, transform its detected pose into the robot frame, and measure translation and rotation residuals. Then execute slow reaches to independent landmarks. Reprojection error alone does not close the robot-coordinate loop.
Kinematic and tool calibration
Nominal link lengths and joint zeroes describe the design, not necessarily the assembled machine. Encoder offsets, compliance and tool mounting error can shift the end effector. The forward-kinematics model in kinematics shows how each parameter contributes to the final pose Lynch 2017.
At minimum, define and verify the tool center point. Touch a fixed physical point from several tool orientations. If the estimated point moves, the tool transform is wrong. For higher accuracy, fit joint offsets and selected link parameters from external pose measurements, then validate on a held-out workspace grid.
Do not fit every possible parameter without an observability analysis. Flexible models can trade one incorrect link length against another and reproduce the calibration poses while extrapolating poorly.
Time calibration
Spatial calibration assumes simultaneous measurements. A camera frame at time paired with joint state at creates a pose error proportional to motion speed. At slow motion the system looks calibrated; at production speed it misses.
Use hardware timestamps where available. Record camera exposure time, robot-state time, command time and arrival time separately. Estimate offset by correlating a motion visible in both streams, such as a tracked tool moving through a known trajectory. Repeat under load because buffering and network transport can add variable latency.
For learned policies, perform alignment before forming observation-action pairs. A fixed two-frame shift changes the apparent control law and can make a policy look temporally unstable.
Dynamics and actuator calibration
Sim-to-real work often calls this system identification. Measure how commanded position, velocity or torque becomes realized motion. Fit latency, gains, friction and actuator response at the operating amplitudes and rates.
Hwangbo and colleagues identified actuator-model error as a central transfer obstacle on ANYmal and learned an actuator network from real measurements to replace the inadequate analytic component Hwangbo 2019. This is calibration by residual learning: known rigid-body structure remains, while the hard actuator mapping is estimated from data.
Record both commands and measured response. A dataset that stores only the command cannot distinguish policy error from controller tracking error.
Calibration versus visual servoing
Visual servoing closes the loop on image error and can reduce sensitivity to an imperfect global pose estimate. The task-function formulation uses the relationship between feature motion and camera motion to drive features toward a target Espiau 1992.
It does not make calibration irrelevant. The interaction model, velocity command and safety geometry still need consistent conventions. It changes which errors become steady-state bias and which bend the path.
Drift and ownership
Calibration is an operational asset. Store it with hardware serial numbers, camera settings, tool identity, software version, date, temperature where relevant, procedure and validation results. Define triggers for revalidation: camera remount, collision, tool change, firmware update, focus change or a residual crossing its threshold.
Build a short automated check that can run before data collection and evaluation. Fixed landmarks should transform into the robot frame within tolerance; timestamps should stay within a bound; commanded and measured motion should agree under a standard sequence.
The final output is not “calibrated.” It is a set of measured residuals with an operating range and an owner. That is what lets a policy failure be attributed to the learner rather than to an invisible disagreement between coordinates.
See also
- Perception for Manipulation
Calibration through 6-DoF pose: the pipeline that finds the object, and its error budget.
- Kinematics
Forward and inverse kinematics, DH parameters, and the Jacobian; the theory behind the 3D playground.
- State Estimation
Kalman filters, factor graphs, and pose estimation from noisy sensors.
- The Robot Learning Stack
Data capture, schemas, training, simulation, evaluation, serving and robot integration as one reproducible system rather than a model checkpoint.
Linked from
- Robot Learning Curriculum for ML Engineers
A dependency-aware route from supervised learning to real robot policies, with the minimum robotics stack each stage assumes.
- The Robot Learning Stack
Data capture, schemas, training, simulation, evaluation, serving and robot integration as one reproducible system rather than a model checkpoint.
- Kinematics
Forward and inverse kinematics, DH parameters, and the Jacobian; the theory behind the 3D playground.
- State Estimation
Kalman filters, factor graphs, and pose estimation from noisy sensors.
- Perception for Manipulation
Calibration through 6-DoF pose: the pipeline that finds the object, and its error budget.
- ROS 2 for Machine Learning Engineers
Topics, services, actions, QoS, tf2, rosbag2 and MoveIt explained as the production boundary around a learned policy.
References
Z. Zhang, IEEE Trans. Pattern Analysis and Machine Intelligence, 2000.
https://doi.org/10.1109/34.888718
Y. C. Shiu, S. Ahmad, IEEE Trans. Robotics and Automation, 1989.
https://doi.org/10.1109/70.88014
R. Y. Tsai, R. K. Lenz, IEEE Trans. Robotics and Automation, 1989.
https://doi.org/10.1109/70.34770
Kevin M. Lynch, Frank C. Park, Cambridge University Press, 2017.
https://modernrobotics.northwestern.edu/
RealSense, RealSense, as of 2026-08-22.
https://www.realsenseai.com/wp-content/uploads/2026/03/RealSense-D400-Series-Datasheet-Mar-2026.pdf
Anders Grunnet-Jepsen, John N. Sweetser, John Woodfill, RealSense documentation, as of 2026-08-22.
https://dev.realsenseai.com/docs/tuning-depth-cameras-for-best-performance/
Jemin Hwangbo, Joonho Lee, Alexey Dosovitskiy, Dario Bellicoso, Vassilios Tsounis, Vladlen Koltun, Marco Hutter, Science Robotics 4(26), 2019.
https://arxiv.org/abs/1901.08652
B. Espiau, F. Chaumette, P. Rives, IEEE Trans. Robotics and Automation, 1992.
https://doi.org/10.1109/70.143350
Bowen Wen, Wei Yang, Jan Kautz, Stan Birchfield, CVPR 2024.
https://arxiv.org/abs/2312.08344
Spot a factual error or missing qualification? Report a content correction.