ESC calibration error in Arduplane Q-Mode VTOL

Archive Plane 4.1
1

I have seen other comments referring to the error “what is set param error. Please ensure your version is ac3.3+”, but no answers that reasonably correct the error.

I have only seen this error in Arduplane and when trying to calibrate the ESC’s in Q-Mode Config for VTOL. And after clearing the error, the ESC’s do nothing after the reboot.

I have made sure that Mission Planner and the firmware for the FC’s are the latest.

The only answer that I have found is, “Ignore it!”, but that does not resolve the problem and the ESC’c are not calibrated.

Is there a fix for this error, or just live with it?

1 Like
2

I’m seeing this as well and am equally stumped on how to fix it. My setup:

  • ArduPlane 4.6.3
  • Mission Planner 1.3.83 build 1.3.9384.38258 on Debian, connected directly to the autopilot over USB
  • Mission Planner on Gentoo, connected to MAVProxy forwarding traffic to the autopilot (i.e., I’ve tried this in both a direct-connection-over-USB and via-mavproxy method with no difference in behavior)
  • Pixhawk Cube Orange w/ ADS-B in carrier board
  • Tiltrotor “quadplane” with a tri-motor setup in vectored yaw mode
    • Q_ENABLE = 1
    • Q_FRAME_CLASS = 7
    • Q_FRAME_TYPE = 1 (even though this is ignored with …_CLASS == 7)

I did manage to catch an error message in the console from Mission Planner when I clicked the “calibrate ESCs” button:

WARN MissionPlanner.MAVLinkInterface - Trying to set Param that doesnt exist ESC_CALIBRATION=3

Another post (this one) suggested setting ESC_CALIBRATION as well, so I figured I’d go do it myself – but as the MP error indicates, it’s nowhere to be found in the parameter list.

3

Just a thought but when you run the calibration make sure you’re in a Q mode. Q-Stabilized, or Q-hover. It may not work if the plane is in manual or FBWA, etc.

4

Sorry about the delay – work got to me, just getting back to this now!

I definitely wasn’t in any of the Q modes before, but trying that now (QSTABILIZE) I’m getting the same result.

However, i did also find this page: ESC calibration — Plane documentation which indicates a different Q_ESC_CAL parameter for use with quadplanes. This parameter exists for me, so I’m going to give this procedure a shot and will report back.

Edit:

Yep, that worked! I used the Q_ESC_CAL=1 option. Be warned, the motors DID move – like the docs say, make sure you remove props!!