I've been trying to calibrate the Accelerometers since the day 2.9 has come out and have not been successful yet. Here is what I've tried using the mission planner calibration method.
- Powered via usb (both on my quad and off)
- Everything connected/nothing connected
- Powered via lipo battery sending commands over telemetry
- Completely resetting the EEPROM, and the code
- Changed the filter value
- Sending the commands via the CLI
Every time the calibration fails and i'm left with values like:
INAV_ACORR_X 89.765
INAV_ACORR_Y -59.582
INAV_ACORR_Z 40.448
INS_ACCOFFS_X 0.001
INS_ACCOFFS_Y 0.309
INS_ACCOFFS_Z 2.953
INS_ACCSCAL_X 1
INS_ACCSCAL_Y 1
INS_ACCSCAL_Z 1
INS_GYROFFS_X -0.011
INS_GYROFFS_Y 0.915
INS_GYROFFS_Z 0.061
I've been to scared to try flying it to even think about doing the auto trim method.
I've read around the "ArduCopter 2.9 / 2.9.1 released" thread and it seems like there might be a couple of others out there that are having the same problem
Any help would be greatly apprecieated
Replies
I've got a board that can't be calibrated, even with the more relaxed threshold in Randy's custom firmware.
These are the values I'm seeing when I do the calibration in the CLI:
Bad board?
I'm guessing modifying the code to have a threshold of 7.6 is not a great idea, if it's that far out.
hey guys
loaded the "relaxed" version and had some nice results
Log and KLM attached,
as side note randy i have my TC set to 8 and im quite happy with it up there.... drops are only about 1-2m. im sure you could see that in the logs.
log.txt
2013-04-01 10-11-07.tlog.kml
I've created slightly modified versions of 2.9.1b here with more forgiving accelerometer calibration checks.
APM2.x quad is here.
APM2.x hexacopter is here.
So if your accelerometer calibration is failing you could try uploading these through the mission planner's firmware screen. On the bottom right you'll see the "Load custom firmware" link.
Please note that these are for the APM2 or APM2.5 only.
In fact, this tolerance check is only stopping the final save of the new scaling and offsets to the eeprom. If you knew what those values should be then you could enter them directly into the mission planner's Adv Parameter List. Sadly it appears that when we fail the calibration, although we display the new scaling and offsets from the calibration algorithm, we sadly don't display enough digits of accuracy for you to make use of them. ..so close and yet so far. :-(.
Gutzmann,
Ok, so the issue is probably that your Z accelerometer offsets (2.953) is very close to the limit which is 3.0. "3.0" was picked because it was a bit worse than the worst board on the dev team. Your board seems to be very close to that. The numbers that you've got above are probably from the old "level" procedure which didn't have the tolerance check.
I can easily provide a version of the code with the tolerance check increased (maybe to 3.5 or 4.0). Do you think you could upload the code with Arduino or would it be easier for me to provide a hex? If it's a hex, are you running an APM2 quad?.
If anyone can point me to other people having this issue I'd like to sort them out too.
Use 2.9.1 and MP 1.2.33 and problem will be solved i think..
Hi, i had the same issue with mine when updated the planner to version 1.2.32, so i decided to re-install the ver. 1.2.30 , and problem resolved.
p.s - i haven´t tried yet with the latest ver. 1.2.33, so i can´t comment about it.
Gil