I've made some flights today with my hexa (2.0.46 firmware version).
The problem is that even if i the flight was sometimes at 10-15m on the kmz file/log the altitude reported by the baro was max 1-2 m.
I don't have a sonar installed.
How can i check to see if the baro is dead ? It can be replaced ?
I've attached the log and kmz file. I will upload a video soon.
Thanks for your oppinions / help.
Tags:
Permalink Reply by Kirill on October 4, 2011 at 12:27pm Try to go to test -> altitude in CLI mode via APM Planner terminal for instance and see what it will show you...
Permalink Reply by Alex on October 4, 2011 at 8:34pm on the floor level it shows values between -0.11 -> 0.5 m. If i raise it manually to aprox 2m the readings are the same....
Permalink Reply by Alex on October 5, 2011 at 6:52am I've tried with other firmware versions, same problem. the only hardware change was when i soldered the filter pads(2 weeks ago aprox.). The baro traces are near the filter pads ? Here is how i've solder : http://www.rcgroups.com/forums/showpost.php?p=19408439&postcoun...
Permalink Reply by Kirill on October 5, 2011 at 10:45am It seems to be showing right values, +-0.5m variations is normal for baro sensor.
Filter pads? Could you explain, please, what is it?
Permalink Reply by Alex on October 5, 2011 at 10:56am
Filter pads, read here, at the bottom : http://code.google.com/p/arducopter/wiki/AC2Assembly
Ok, now i'm totally confused... i made another test: i blow in the sensor (normally, i think, that the values should go UUUUPPP) but nothing happends, same values... I'm on a step distance to replace the baro sensor...
Permalink Reply by Kirill on October 5, 2011 at 12:32pm Thanks for the link.. That's very sophisticated thing, you really might have damaged the sensor while soldering.
Yep, blowing in the sensor must cause changes...
Permalink Reply by 3D Robotics Tech Support on October 5, 2011 at 4:11pm Hi Alex,
The values should change for the tests that you've tried. You can also check to see if the ADC chip is working correctly: try running the ADC test in CLI mode and see if the gyro values are normal (around 1600)? If the gyro values are incorrect (i.e. 0 or 1) then there may be a problem with the ADC chip. If the gyro values are fine, then the pressure sensor is likely the problem.
Permalink Reply by Alex on October 5, 2011 at 8:38pm I've made a test 5 minutes ago. For several seconds i've moved it and after that i let it on the table. The values are in the txt file.Where is the problem ? Thank you.
P.S. Now i've desoldered the filter pads.
Permalink Reply by 3D Robotics Tech Support on October 6, 2011 at 11:52am Hi Alex,
Thanks for including the ADC test values. It looks like the ADC chip is fine, so most likely it's the pressure sensor.
Permalink Reply by Alex on October 7, 2011 at 7:41am Tomorrow i will change it and i will be back with the results. Thanks for help.
Season Two of the Trust Time Trial (T3) Contest has now begun. The fourth round is an accuracy round for multicopters, which requires contestants to fly a cube. The deadline is April 14th.51 members
1299 members
24 members
48 members
111 members
© 2013 Created by Chris Anderson.
Powered by
