Skip to content

FPV Camera Gimbal (XF C-20T)

Point the FPV camera with your head while your hands stay on the HOTAS. The head tracker feeds Magic Box, Magic Box sends pan and tilt over your normal RC link, and the flight controller passes them to the gimbal as two PWM signals:

head tracker → Magic Box → TX module → ((RF)) → receiver → flight controller → C-20T gimbal

This page covers the PWM route (pan + tilt). It’s what we fly in two models: an F-22 on INAV and a UH-1D Huey on ArduPilot (examples at the bottom).

PartNotes
XF Robot C-20T gimbal3 axes, 46 g (Alloy) / 49 g (Basic), takes cameras up to 20 g / 19 mm. Power 7.4–26.4 V (2S–6S); 1.5 W at rest, up to 14 W when stalled. Range: pitch −105…+145°, roll ±60°, yaw ±160°.
C-20 Integrated Base Plate (marked FPV_BP)Ships in the XF Headtracker Datalink kit. Splits power and signals between the gimbal and a DJI air unit.
Head tracker with PPM outputWe use the SyncPilot module (FMS × XF Robot) on the goggles. Any PPM head tracker works the same way on the Magic Box side.
Flight controllerTwo free servo outputs. Tested with INAV 7.1.0 and ArduPilot.
XF Config Module J1.0 + Windows PCFor GimbalConfig (calibration, modes). Needs the CH341 USB driver.

The C-20T has six connectors: ① Upgrade port (Config Module → PC), ② Power Out / CVBS (analog camera only), ③ 8-pin power-communication port (JST SH, BM08B-SRSS-TB), ④/⑤ coax between air unit and camera — video only, no OSD, ⑥ AV cable.

Port ③ pinout — pin functions can’t be remapped:

PinFunction
1Power In
2GND — must be shared with the signal source
3UART Rx
4UART Tx
5PWM1 = mode, or S.BUS / CRSF input
6PWM2 = sensitivity
7PWM3 = pitch
8PWM4 = yaw

All connectors sit on the air-unit half of the plate (you can snap the plate along the perforation).

PortPins / purpose
1 — Power-communication (GH 8-pin, cable out)Power In, GND, NC, NC, PWM1–4. Powers the gimbal.
2 — DJI 3-in-1 (GH 6-pin, cable out)O3 Power In, GND, UART Rx, UART Tx, GND, DJI HDL. Powers the air unit.
3 — DatalinkGND, 5 V (max 0.5 A), UART Rx, NC
4 — Power Out5 V, 0.5 A (fan)
5 — DJI transferringto the air unit
6 — Gimbal transferringto gimbal port ③

Priority, highest first: head tracker direct (XF private protocol) → S.BUS / CRSF → PWM → MAVLink. A head tracker talking to the gimbal directly wins over the PWM coming from Magic Box.

Roll is digital only (S.BUS, CRSF, MAVLink or head tracker direct). PWM carries mode, sensitivity, pitch and yaw — there’s no PWM pin for roll. On the PWM route you control pan and tilt; roll isn’t controlled.

  1. Port 1 cable → gimbal power + two FC servo outputs. Pitch (PWM3) and yaw (PWM4) take signal only — ground comes through the shared battery negative. Power the gimbal from the flight pack, not from a BEC or the servo rail.
  2. Port 2 cable → air unit power + FC UART. On an FC with a DJI socket this goes plug-to-plug and the same UART carries MSP DisplayPort, so the OSD shows in the goggles.
  3. Camera coax between gimbal and air unit — leave slack. A coax pulled tight is the usual cause of a jerky pitch axis.

The gimbal reads standard servo PWM, so a receiver with spare PWM outputs can in principle drive it directly. We’ve only flown the FC route.

2. Magic Box: head tracker → Cam Pan / Cam Tilt

Section titled “2. Magic Box: head tracker → Cam Pan / Cam Tilt”

Set up the head tracker as a Wired module exactly as in External Inputs. With the SyncPilot the axes arrive on these PPM slots:

AxisHead tracker channel
Yaw → panCH5
Pitch → tiltCH6
RollCH7
ModeCH8
SensitivityCH4
  1. Add two module inputs — ht pan (HT CH5) and ht tilt (HT CH6).
  2. Pick two free Magic Box channels, set their Function to Cam Pan and Cam Tilt, and bind each one to its module input.
  3. Camera moves the wrong way? Tick Reversed on that channel. In our Huey the tilt channel is reversed.
  4. Add an Override on both channels: Activation Button = a button on the throttle, Override Source = a rotary knob on the throttle (one per channel). With the button on, the camera follows the knobs instead of your head — manual centring in flight, and a cut-off if the head tracker misbehaves. That’s the job GOTO-ZERO can’t do in a plane.

3. Flight controller: route, limit, smooth

Section titled “3. Flight controller: route, limit, smooth”

The FC passes the two Magic Box channels to the servo outputs wired to the gimbal.

INAV — in the Servo Mixer add the RC channel carrying Cam Pan to the yaw output and Cam Tilt to the pitch output.

  • Weight sets range and ratio.
  • Speed 10–20 smooths a nervous camera.
  • Outputs → MIN / MAX caps travel, e.g. tilt 1300–1700 µs. On yaw, 1000–2000 µs = ±160°.

ArduPilot — pass the RC channels through with SERVOn_FUNCTION = RCINx (51 = RCIN1 … 66 = RCIN16). Example: Cam Pan on CH10 and Cam Tilt on CH11 → SERVO9_FUNCTION = 60, SERVO10_FUNCTION = 61.

GimbalConfig runs on Windows only: Config Module J1.0 into port ①, CH341 driver, USB-A → USB-C cable (dual USB-C cables are sometimes not recognised). After every change: Upload Param → Save Param To Flash.

  • Mode: FPVM-ANGL for planes. It’s the only mode without tilt protection — in PitchLock or Horizon the gimbal neutralises past 60° of bank. A head tracker needs an angle mode anyway. The factory preset M0 is FPVM-ANGL, so PWM works straight out of the box.
  • Sensitivity only applies in FPV mode.
  • Presets (mode, sensitivity, angles) apply only to pins with no signal. On the PWM route pins 5 and 6 stay empty, so mode and sensitivity come from the preset.
  • Channel Mapping doesn’t apply to PWM. In MAVLink presets are ignored.

Gyro calibration — the sequence that works for us:

  1. Unplug the air unit — its fan disturbs the calibration — and disconnect the signal wires.
  2. Power the gimbal level (Mounting AUTO detects UP / DOWN at power-on) and wait 3–5 min for the IMU to warm up.
  3. Gimbal Stop → Gyro Calibration → Save To Flash → Gimbal Run.

Tune in CwHeadTracker (Windows):

  • Gain per axis. 2.0 means 30° of head = 60° of camera. The unit in our F-22 came set to 8.0 — the main source of a twitchy camera.
  • Offset trims the centre.
  • After changes: Upload Param → Save Flash.

Quick adjustments in the field: the Sensitivity −/+ buttons on the module; long-press M recentres.

  • Activate it in DJI Assistant 2 (DJI FPV Series) with a DJI account. Power the air unit from a battery and connect USB-C to the PC — USB alone isn’t enough. Without activation output power stays at 20 mW or less.
  • Pair with Goggles 3: Status → pick the product → link button on the air unit (blinks red) → link on the goggles → solid green.
  • Power range 7.4–26.4 V. Full detail in the DJI O4 Air Unit Series User Manual.

Gimbal ignores the PWM? Check in this order

Section titled “Gimbal ignores the PWM? Check in this order”
  1. Common ground. Measure between the flight-pack negative and the gimbal GND — it must read 0 V. We once had a 3S balance plug seated on cells 2–4: the FPV ground sat 4.1 V high and the gimbal never saw the PWM.
  2. Signal at the FC output. A multimeter on DC volts shows a 50 Hz servo pulse as a small steady voltage: 1500 µs ≈ 0.25 V, 2000 µs ≈ 0.33 V. Move your head and the reading should change.
  3. Mode. Tilt the base plate by hand. The camera following smoothly means FPV mode is active.

F-22, INAV 7.1.0 (SpeedyBee F405 Wing). Port 1 cable to the battery and servo outputs 7 (pitch) and 6 (yaw), signal only. Port 2 cable plug-to-plug into the SpeedyBee DJI socket — air unit power plus UART5 as MSP DisplayPort for the goggle OSD.

UH-1D Huey, ArduPilot (FC without a DJI socket). PWM from outputs 9 (yaw) and 10 (pitch), SERVO9_FUNCTION = 60 and SERVO10_FUNCTION = 61. Both signals come from one servo plug turned across the header on the signal row — it picks up two adjacent outputs; secure it with a zip tie. FPV power from the flight pack via a 4S balance plug, not from the BEC. Full build — channels, arming, failsafe, OSD: UH-1D Huey 470 (HOTAS + FPV).