-
Notifications
You must be signed in to change notification settings - Fork 428
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Activate GPS navdata #75
Comments
That's interesting, I guess once it's been sent by the phone it doesn't need to be sent again, as I've not experienced that (I can just plug it into one of my drones and start reading straight away) |
What drone/GPS firmware version was this with? On 2.4.8 (drone) and 4.1.2-P6 (GPS/FlightRecorder) I actually can't get any navdata back at all unless FreeFlight and QGroundControl seem to have no trouble though. Thoughts? |
I have found the exact same thing as ahensley. If there is any update on this or resolution I would love to know. |
I just tested again with AR.Drone firmware 2.4.7, GPS firmware 4.1.0-P1, and QGroundControl uses a completely different protocol, mavlink, so I assume that's why it doesn't run into this problem. I got the 777060865 value by sniffing traffic sent from FreeFlight to the drone, but maybe this changed in later versions. |
Ouch. Using AR.Drone firmware 2.4.8, GPS firmware 4.1.2-P6, I see the behavior you're seeing: I stop receiving navdata almost immediately. This seems like a big problem. |
It seems that bit 27 of navdata_options is actually the GPS mask. Your 77060865 number enables that bit along with several others. The constants.js file in ar-drone/lib calls this bit "ZIMMU_3000", which is incorrect but no one would know that since Parrot hasn't released an updated SDK. With the latest firmware the GPS packet seems to have changed. In the parseNavdata.js file in ar-drone/lib/navdata I changed the 'gps' parser to comment out everything after unk_2. With that changed the GPS works as it should.
|
Awesome, @timogiles. I found an updated description of the GPS fields at lesire/ardrone_autonomy@a986b33 and opened #93, and your tracking the issue of hanging navdata down to a bad definition should make for an easy fix, which I have in progress at https://github.com/felixge/node-ar-drone/tree/gps_2_4_8 And good catch on ZIMMU_3000 as well. Once I do more testing I'll close this. |
To be clear, I've already confirmed that the gps_2_4_8 branch works with firmware 2.4.8 once you do |
FYI master has the fix for reading GPS data in firmware 2.4.8. |
💖 thank you so much @wiseman . I just recently played with the GPS stuff for the first time - this will come in really handy! |
Grrrrr... no I really don't have any excuses left not to buy a gps dongle :-) Great work everyone! |
@wiseman I'm just triaging some of the issues, is this ok to close now? |
Yes, I think the answer is to use the |
Hi @wiseman !!
Thank you! |
Even with the Flight Recorder GPS accessory, from a cold boot the AR.Drone doesn't send GPS data as part of navdata.
The following command will cause the drone to begin including GPS data (this is what the iOS app sends):
The text was updated successfully, but these errors were encountered: