← All tools

Message & Error Explainer

What an ArduPilot message means and what to do about it

Українська

The accelerometers have no valid calibration

Stops itIMU: accelerometers, gyros, vibration

What ArduPilot says:

For every accelerometer ArduPilot keeps offsets and scale factors from the six-position calibration, together with the sensor's ID. The check fails when an accelerometer has no saved ID or a different one, when its offsets are all exactly zero, when a sensor that was calibrated is missing now, or when calibration values exist for a sensor that is not there.

What to do, most likely first

  1. The board is new or its parameters were reset: the calibration was never done.

    CheckINS_ACCOFFS_X and its neighbours are all 0.

    FixDo the accelerometer calibration in the ground station: six positions, each held still on a level surface. Then reboot.

  2. The parameters come from another flight controller, or the firmware changed and numbers the IMUs differently: the saved IDs do not match the sensors found.

    CheckThe offsets are not zero, yet the message appeared right after loading a parameter file or flashing.

    FixCalibrate the accelerometers again on this board. Calibration values cannot be carried from one board to another.

  3. An IMU that was calibrated did not start this time.

    CheckFewer “IMU” lines at start-up than before; INS_ACC2_ID or INS_ACC3_ID is not 0 for a sensor that is not listed.

    FixReboot. If the sensor stays missing, the board is faulty: do not calibrate around it, replace the board.

Parameters to look at

ParameterWhat it is
INS_ACCOFFS_XAccelerometer offsets of X axis
INS_ACCSCAL_XAccelerometer scaling of X axis
INS_ACC_IDAccelerometer ID
INS_ACC2_IDAccelerometer2 ID
INS_ACC3_IDAccelerometer3 ID
INS_ACC2OFFS_XAccelerometer2 offsets of X axis
The code that sends it

PreArm: 3D Accel calibration needed

libraries/AP_Arming/AP_Arming.cpp AP_Arming::ins_checks() · 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