search

coby7016 / arducopter

Automatically exported from code.google.com/p/arducopter
0 stars 0 forks source link

Compass issue - test output wrong and reported heading off #209

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
ACM 2.36

Software compiled from source in Arduino, but also shows up downloaded throught 
the 1.037 Mission planner.

Output seems to be broken for me. When I setup the software, the compass 
diagnostic output very large negative numbers for the heading , but somewhat 
reasonable values for the x,y,z components. I entered my magnetic deviation 
using the planner during the setup using the value of -0.6666 degrees (- 40')  
I flew one flight hoping that the compass alignment would fix the heading 
output, but after the flight, the mavlink compass heading was off by 90 
degrees, and I captured the compass test output with still bizarre values. 
Simple mode was working correctly though. Flying the older compass purchased 
11/2010. I saw the same behavior with the downloaded hex file from the planner 
last night.
BR-HMC5843-01   HMC5843 - Triple Axis Magnetometer

Attached screen capture of compass output from CLI test compass

Original issue reported on code.google.com by hrp...@gmail.com on 17 Jul 2011 at 5:58

Attachments:

GoogleCodeExporter commented 9 years ago 
I diagnosed this to somehow bad declination being stored for a Mission Planner 
setup entry of -0.66666666

Using the CLI to enter declination -0.6666666 seems to work ok with good 
compass values.

Original comment by hrp...@gmail.com on 18 Jul 2011 at 5:19

GoogleCodeExporter commented 9 years ago 
during the setup, what did you enter? -0.40 ?

Original comment by Meee...@gmail.com on 19 Jul 2011 at 8:10

GoogleCodeExporter commented 9 years ago 
This issue can be deleted. All along I've been entering -.40 for my declination 
during setup and I changed to -.666666 just recently after reading a post about 
cli entry of declination (which I thought was talking about mission planner 
entry of declination during setup). Now I understand that the cli entry format 
is different than the mission planner input format and the planner is 
converting for me.   

Since decimal values .60000000 to .9999999 are really illegal in planner setup 
entry it might make sense to return an error dialog box instead of continuing 
the setup with a funky declination value. 

Anway sorry for my confusion.

Original comment by hrp...@gmail.com on 19 Jul 2011 at 12:48

GoogleCodeExporter commented 9 years ago

Original comment by jasonshort on 19 Jul 2011 at 4:09