"@Bill, It would still work fine with the ASCII GCS protocol, just our packet receiving inside our XBeeGCS would not work. That and you wouldn't be able to see that a new waypoint is loaded via wp_index, since we actually do not change that variable.…"
Haha, okay, you are correct on both counts in your 2nd to last post. All packets are sent in big endian format, and we do perform that x10 multiply for lat/lon and x100 for altitude in the transmit() method of XBeeGCS.java."
"Hey everybody, turns out there was a huge problem with the git repository this morning, and all of our refactoring and documentation commits from yesterday were lost. We've restored it now, and are considering putting it in a new repository.
"@NS Rana: Thanks! We have tested it in the air, and as far as we can tell, it flies to the waypoint we loaded in the air. The XBeeGCS shows that the next waypoint is the one we loaded, along with our special waypoint index (997). After reaching it,…"
"@Greg: yep, the GCS code is also in that github link in the blog post, inside the xbee-api/ folder.
@Bill: That sounds great, I hope the GCS code we have up now is flexible enough. Right now our solution on the ArduPilot is kinda hackish in itself,…"
Hey everybody, me and my friend Chester would like to share our implementation of loading a waypoint into the ArduPilot in air. We use XBee radios, NewSoftSerial, and our own GCS written in Java (using Andrew Rapp's xbee-api) to do this. Our GCS was…