How come this thread is marked as solved when there is no fix and I had to give on on APM and use Mission Planner?
It isn’t just me either…
I’ve tested this and it’s working me as expected. I need a way to reproduce to be able to find a fix.
Have you tried using APM Planner again and see if it works now? If you do retest can you post the APM Planner 2.0 logs from ~/apmplanner2
Thx
No, but hopefully the criteria for marking an issue as solved is not simply not being able to reproduce it 
Are you using a 3DR Y6B 2014 ?
Have you tried the steps you suggested to me that didn’t work?
I have the Y6B params and reset to defaults, which you say erases everything. Then tried the compass calibration and it failed.
This was for a brand new build that has never flown. This was with 3.2RC12 and RC9.
Hope this helps…
Can you post the APMplanner logs?
I did… And you said they were fine, when compass calibration failed, so I’m not sure what you gain by me doing it again.
I thought you were looking for a way to repro the issue?
Have you seen this thread?
diydrones.com/forum/topics/arduc … %3A1824970
As of 2.0.15 rc3 I have the same problem.
Bill I am not positive what the issue is… apm planner or 3.2 beta. But no matter what I do it always says compass not calibrated. I can’t arm unless I shut off the compass pre arm check. I suppose I should go back to copter 3.1 and just confirm it does the same thing. If not I guess I can chalk it up to copter beta not amp planner. will let ya know… thx
@meavydev: This is your previous logs, and it confirms we have sent the parameters and the APM received. I’m asking for a new log to confirm it’s still an issue, or if it’s somehow rectified after doing the calibration once with Mission Planner. And if there is something new in the log that shows up.
INFO 2014-10-17T16:59:23.608 rep.terminationType 2
INFO 2014-10-17T16:59:23.609 rep.terminationType 2
INFO 2014-10-17T16:59:23.609 New Compass Offset to be set are: -19.4311 , -46.6644 , 85.9154
INFO 2014-10-17T16:59:23.609 New Compass 2 Offset to be set are: 53.6169 , 77.8072 , -3.25068
DEBUG 2014-10-17T16:59:23.660 APL::parameterChanged: "COMPASS_OFS_X" char= "0" int= -19 float= -19.4311
DEBUG 2014-10-17T16:59:23.661 APL::parameterChanged: "COMPASS_OFS_Y" char= "0" int= -47 float= -46.6644
DEBUG 2014-10-17T16:59:23.661 APL::parameterChanged: "COMPASS_OFS_Z" char= "0" int= 86 float= 85.9154
DEBUG 2014-10-17T16:59:23.662 APL::parameterChanged: "COMPASS_OFS2_X" char= "0" int= 54 float= 53.6169
DEBUG 2014-10-17T16:59:23.662 APL::parameterChanged: "COMPASS_OFS2_Y" char= "0" int= 78 float= 77.8072
DEBUG 2014-10-17T16:59:23.662 APL::parameterChanged: "COMPASS_OFS2_Z" char= "0" int= -3 float= -3.25068
DEBUG 2014-10-17T16:59:30.921 APM: Text Message rx'd "PreArm: Compass not calibrated"
INFO 2014-10-17T16:59:30.997 STATUS TEXT: 3 : "PreArm: Compass not calibrated"
The lines that read APL::parameterChanged: are printed in the log by the APM sending confirmation that it received the new offsets.
@givsux: can you post logs of your experience as well, Thx.
Hi,
I now know what the issue is. The problem is that when you set the PARAMETERS it only triggers a save to EEPROM of those COMPASS_OFS_X/Y/X parameters. When you send the SET_SENSOR_OFFSET Mavlink command it sets the COMPASS_DEV_ID of the compass in the parameters as well. My board has the DEV_ID already set. so worked as expected.
I’ll submit a change later today with a tested fix that works. This only effects 3.2 as 3.1.5 does’t use COMPASS_DEV_ID parameters.
PS: I found another defect as well, where the EEPROM wasn’t being formatted by clicking reset to defaults on APM:Copter only (it works on Rover on Plane) This will also be fixed
you can download a daily build that will fix the issue from here firmware.diydrones.com/Tools/APM … 014-11-06/
[quote=“billbonney”]Hi,
I now know what the issue is. The problem is that when you set the PARAMETERS it only triggers a save to EEPROM of those COMPASS_OFS_X/Y/X parameters. When you send the SET_SENSOR_OFFSET Mavlink command it sets the COMPASS_DEV_ID of the compass in the parameters as well. My board has the DEV_ID already set. so worked as expected.
I’ll submit a change later today with a tested fix that works. This only effects 3.2 as 3.1.5 does’t use COMPASS_DEV_ID parameters.
PS: I found another defect as well, where the EEPROM wasn’t being formatted by clicking reset to defaults on APM:Copter only (it works on Rover on Plane) This will also be fixed[/quote]
Hey Bill that seems to have done the trick for me 
I have been very frustrated with this I don’t like to fly with any pre arm checks off! I lost a quad doing that I’m not gonna make that mistake again. I really appreciate you fixing this.
Latest dev builds worked for me. I’ve resetted everything and started from scratch with just the APM Planner and everything worked as expected! 
Thanks a lot thumbsUp