HAs anyone had issues with the airspeed sensor using ArduPilot with the shield? I have set the proper millivolts in the code but it doesn't seem to work right. After loading the code and looking at the GCS at a standstill the airspeed is 0....great. At the slightest breeze (or blow toward the tube) the airspeed jumps up to 200 +/-40. It's never worked since I've been using the GCS. This is happening on 3 separate ArduPilot setups so I know it's not the hardware. Any ideas, thoughts, or experiences with this issue?
I know, this post is very old. But here is the answer of the question.
You have to change the GCS_standard_text.pde. Because airspeed is send in cm/s but the GCS expect it in m/s.
Change line 180 from "Serial.print(airspeed,DEC);" to "Serial.print(airspeed/100,DEC);"
Hello Sebastian, I see the name Brifly on the above but can't help think I have posted or not quite understand the nature of this site. Whether or not this is my post I can say I have had the same experience with the airspeed readout in the GCS. I will certainly give this a try and see if that display is corrected. Thank you. The real trouble I have with the entire unit, shield, ardupilot and all is a receiver range as I have posted elseware. When used with 2 different receiver/transmitter units the range is only perhaps 50ft at this time as ground tested before the control surfaces go crazy. Obviously I cannot trust my plane to this and have not even attempted using the unit. I even tried contacting Sparkfun but no response. Not surprising since the product is not supported anymore. Was hoping to find a hardware fault and replace an onboard chip or something. I can afford the mega but am stubborn natured and hope to somehow figure out the trouble! No one else having this issue. Thanks again.
I dont know if this will help you, but personally, i have had loads of problems with Ardu + shield with IMU.
I run Ardu + IMU only, this solution is very reliable.
As far as your range is concerned, this sounds to me as though either you have a dodgy bit of soldering on the board on or around the MUX, if the whole thing spaz's out at about 50ft.
My reasoning, is that we have flown many miles using Ardu + IMU + Ublox (ranged well over the legal limits :) )
So the issue has to be local to your AP or its through put.
My first suggestion to you is to fly the aircraft RC only, removing the AP, make sure its all trimmed, and ranges are acceptable (assuming you are not using Spektrum and its set to range test)
Then fit AP, and fly in stabalized mode to check its ok...
I have about 8 ArduP Mk1's and they are our workhorse for simple grids and having fun, so we need to investigate the desease so to speak, and not the symptoms.
I hope this helps,