A gimbal type is set, but its driver did not start

What ArduPilot says:

• check TYPE

“Mount: check TYPE” means MNTn_TYPE is not 0, yet no driver was created for that gimbal at power-on; drivers are created once, at boot. Its sibling “Mount: not healthy” means the driver runs but the gimbal does not answer: Siyi, Viewpro, Topotek, Xacti and MAVLink (Gremsy) gimbals must report their angles at least once a second. Both are part of the Camera group of the arming checks.

What to do, most likely first

1. The type was set or changed, and the flight controller has not been rebooted since.

   FixReboot.

2. No gimbal is fitted: the parameter is left over from another aircraft's file.

   FixSet MNTn_TYPE to 0 and reboot.

3. This firmware has no driver for that gimbal type.

   CheckThe Firmware Inspector lists what a firmware file was built with; boards with little flash leave most gimbal drivers out.

   FixBuild a firmware with that gimbal driver.

4. For “not healthy”: a serial gimbal is unpowered, or on a port that is not set up for it.

   CheckSiyi, Viewpro and Topotek gimbals need SERIALn_PROTOCOL 8 (Gimbal) on their port and the gimbal's speed in SERIALn_BAUD (115 means 115200). A gimbal that answers reports its firmware at boot, for example “Mount: Siyi gimbal fw v0.2.3”.

   FixSet the port and baud, power the gimbal from the battery (props off) and reboot.

Parameters to look at

Where to do it:Firmware InspectorFirmware BuilderBoard & Wiring Planner