timeshift_cam_imu from a Kalibr-style camchain.yaml. It does not use the intrinsics or T_cam_imu.
1. Measure the offset with Kalibr
Run Kalibr’s camera-IMU calibration (kalibr_calibrate_imu_camera) offline for the camera and IMU on the drone. It writes a camchain.yaml. The extension does not run Kalibr for you.
2. Validate the file
The extension’s repository includes a small Python package that loads and checks acamchain.yaml before it goes onto a drone:
T_cam_imu rotation that is not orthonormal, and the extrinsics object flags a suspicious timeshift (has_suspicious_timeshift).
The file holds a cam0 block (a bare block without the cam0: wrapper also loads):
timeshift_cam_imu is in seconds, with Kalibr’s convention t_imu = t_cam + timeshift.
3. Copy it to the drone
Copy the file into the plugin’s per-drone data directory on the drone, namedcamchain.yaml:
<agent-id> is the directory the first command lists for this drone.
4. Restart the plugin
The plugin reads the file once, at start-up:Sync offset on the Sensors card
The Sensors card shows the live camera-IMU sync offset: green at 10 ms or less, yellow up to 30 ms, red above 30 ms. The colour is informational. It does not change the estimator state or the pre-arm report. A sync offset that drifts usually means the camera mode changed (resolution, frame rate or exposure); measure again in the mode you fly.Next steps
Troubleshooting
Low flow quality, scale problems and lost frames.
Modes and fallback
The modes and the scale ladder.