Replies to This Discussion

Permalink Reply by Drone Savant on January 6, 2013 at 6:52pm

You probably knocked your gyro loose. If you are brave you can try to reflow it perhaps. 

• ▶ Reply

Permalink Reply by Drone Savant on January 6, 2013 at 6:55pm

I forgot to mention for you to try and run the ADC test with the board sitting still. Check the numbers for sanity... http://code.google.com/p/ardupilot-mega/source/browse/libraries/AP_...

• ▶ Reply

Permalink Reply by David Posea on January 6, 2013 at 7:04pm

How do I run a test from a .pde file? Sorry for now knowing the "basics" yet.

• ▶ Reply

Permalink Reply by Drone Savant on January 6, 2013 at 7:11pm

You will need the Arduino GUI... you can follow the instructions located at - http://code.google.com/p/arducopter/wiki/ProgrammingArduino

This will require at least a basic understanding of programming an Arduino. Someone may be willing to walk you through it if you get totally stuck. 

Was this board purchased from a *legit* 3drobotics vendor? You can contact support if so. They don't do any repairs so they will likely tell you to buy a new board but you can at least have them help diagnose it I would imagine. 

• ▶ Reply

Permalink Reply by David Posea on January 6, 2013 at 8:38pm

I do firmware development so I'm sure I can figure out the GUI. I ran the terminal setup / level command and it says gyro did not converge, diff=1.123 (various values). It seems a hard knock must have damaged the gyros. I check the board under a microscope and didn;t see any obvious damage but I'm buying a new board anyway. And yes, it was a 3DR board and the new one will be also.

• ▶ Reply

Permalink Reply by Drone Savant on January 6, 2013 at 8:41pm

Just use the Arduino GUI to upload that code I linked above and it should give you raw Gyro output. You will just need to set the proper board type and serial port, then press the upload button. 

if you are into this sort of stuff you could always toss it in the toaster. 

http://www.sparkfun.com/tutorials/60

• ▶ Reply

Permalink Reply by weelian soh on January 7, 2013 at 7:02pm

You might want to give this a shot. Use the CLI to reset and erase the eeprom and reload the firmware.

http://code.google.com/p/arducopter/wiki/AC2_CLI

I had the same problem of my new quad APM2.5 crashing causing the gyros and magnetometer go out of whack, same thing no physical damage though I suspect the heavy G forces during the crash caused something weird to happen. My dealer Yovi, helped by erasing eeprom and reloading the firmware and that fixed the board. He also advised me that if I want to update my firmware, it is a good idea to erase the eeprom before doing it.

Hope this works for you! Cheers!

• ▶ Reply

Permalink Reply by David Posea on January 7, 2013 at 7:27pm

I'll give it a try. Roll and pitch are working correctly now but yaw when graphed looks like a heart monitor! I don't think the hardware is really at fault. It looks like the PID loop eliminates error a little at a time, until it gets close to 0 then spikes up again all at once. I'll post a graph later tonight.

• ▶ Reply

Permalink Reply by David Posea on January 7, 2013 at 9:24pm

the reset and reprogram didn't work. I have a new board on order. It has to be hardware. Altitude is also pretty unsteady with the hexa sitting still.

• ▶ Reply

Permalink Reply by weelian soh on January 7, 2013 at 10:17pm

Just curious, did you try the reset button on the board? You might want to try the erase eeprom command again and try a re-calibration.

• ▶ Reply

Permalink Reply by David Posea on January 16, 2013 at 9:55am

I tried everything, and got nowhere. My new board should arrive today so I can compare resutls. It's just really weird yaw would change so much, so fast, with the hexa sitting on my pool table.

• ▶ Reply

Permalink Reply by David Posea on January 16, 2013 at 11:37pm

It was the board. Roll, Pitch, and yaw all stay nice and steady now, as well as altitude.

• ▶ Reply

• ‹ Previous
• 1
• 2
• Next ›
• Page