← All tools

Message & Error Explainer

What an ArduPilot message means and what to do about it

Українська

The RunCam camera has not answered yet

Stops itRangefinder, optical flow, camera, OSD and other devices

What ArduPilot says:

A serial port is set up for a RunCam camera, and the camera has not finished starting. ArduPilot asks the camera what it can do, and also gives it CAM_RC_BT_DELAY (7000 ms by default) from power-on to boot. Until both are done arming is refused with “Camera not ready”. “RunCam device not found” means an answer came, but it lists no features at all. With no answer the question is repeated for ever, and the message stays.

What to do, most likely first

  1. You tried to arm within a few seconds of power-on.

    FixWait about ten seconds; “RunCam initialized” in the messages says the camera answered.

  2. The camera has no power (USB only) or its TX and RX are swapped.

    CheckConnect the battery (props off). The camera's TX goes to the flight controller's RX on the port with SERIALn_PROTOCOL 26 (RunCam).

    FixCorrect the wiring and power; the Board & Wiring Planner shows which pad is which UART.

  3. No RunCam is connected: a port was left at 26 by mistake.

    FixSet that port's SERIALn_PROTOCOL to what is really on it, or to -1, and reboot.

Parameters to look at

ParameterWhat it is
CAM_RC_TYPERunCam device type
CAM_RC_BT_DELAYRunCam boot delay before allowing updates
SERIAL1_PROTOCOLTelem1 protocol selection
SERIAL2_PROTOCOLTelemetry 2 protocol selection
SERIAL3_PROTOCOLSerial 3 (GPS) protocol selection
SERIAL4_PROTOCOLSerial4 protocol selection
SERIAL5_PROTOCOLSerial5 protocol selection
The code that sends it

RunCam device not found

libraries/AP_Camera/AP_RunCam.cpp AP_RunCam::parse_device_info() · Open in ArduPilot Copter-4.7.1

Camera not ready

libraries/AP_Camera/AP_RunCam.cpp AP_RunCam::pre_arm_check() · Open in ArduPilot Copter-4.7.1

Written here for Copter 4.6. In the tool you choose your vehicle and version, see your own parameter values beside the ones named here, and drop a flight log to have every message in it explained.

Open it in the Message & Error Explainer