Hello,Today we had our first testflight with the Xbee and it works perfect (ardupilot 1.0) ! We made a flight of three waypoints and landed after that one to change the batt.However after the first flight the xbee log file shows gps altitude of 65500 . The plane started to behave very strange. So we conclude is the gps data was false. Even after several reboots and also a reset on the ardu board. We got a fix , we saw the red light on the gps module was blinkingThe rest of the data seems to be allright.What can be the problem ? Gps faillure ?Regards,Robert
You need to be a member of diydrones to add comments!
@Chris Anderson @Gagarien @Reto
Thanks for the very clear explanations. The problem will be solved by using the V2, I was wishing for that . I allready have the extra components to build it. I just used the V1 to learn about the ardupilot. No problem for me.
I had similar results and think it is safe to say it is not your GPS.
When Ardupilot is powered for the first time it stores the RTL or waypoint 0, your alt is then a reference and reads zero if you descend to a lower alt it read typically some thing like 65000 etc. So it thinks its miles up in the sky and with the autopilot on it wants to nav. to WP1 at 50m or what ever you have in there.
Ardupilot have the auto reset function so if there is a problem it will reset itself storing a new RTL. and zero reference alt up there…in mid flight.
When this happens to me I simply land and reset Ardupilot and try again. I haven’t got enough autopilot time to say it is common but it happens maybe because of my cheap radio set-up and intermittent signal at times while in auto pilot mode..
Also look at your log file closely and try and see were it whent from 0 to 65500 I bet you it was after a reset.
Maybe Chris and Jordi have a clever coding fix for this. Storing RTL so that it would be there after a reset.... naaaa then you would be stuck with that RTL and a nother way of erasing that will have to be coded for future flights. anyway my 5 cents for now.
Replies
Thanks for the very clear explanations. The problem will be solved by using the V2, I was wishing for that . I allready have the extra components to build it. I just used the V1 to learn about the ardupilot. No problem for me.
When Ardupilot is powered for the first time it stores the RTL or waypoint 0, your alt is then a reference and reads zero if you descend to a lower alt it read typically some thing like 65000 etc. So it thinks its miles up in the sky and with the autopilot on it wants to nav. to WP1 at 50m or what ever you have in there.
Ardupilot have the auto reset function so if there is a problem it will reset itself storing a new RTL. and zero reference alt up there…in mid flight.
When this happens to me I simply land and reset Ardupilot and try again. I haven’t got enough autopilot time to say it is common but it happens maybe because of my cheap radio set-up and intermittent signal at times while in auto pilot mode..
Also look at your log file closely and try and see were it whent from 0 to 65500 I bet you it was after a reset.
Maybe Chris and Jordi have a clever coding fix for this. Storing RTL so that it would be there after a reset.... naaaa then you would be stuck with that RTL and a nother way of erasing that will have to be coded for future flights. anyway my 5 cents for now.