The ArDrone Protocol

Implementation of the Protocol is hard and messy and this the reason this issue exist - to help and track the protocol implementation for the SDK
Here are some resources and todos (work in progress) that need to be completed to have a fully capable SDK that understand the Protocol of the drones completely

Resources

• BufferIDs: https://github.com/Parrot-Developers/arsdk-ng/blob/master/libarsdk/src/arsdk_transport_ids.h
• SDK3 (official) C SDK - https://developer.parrot.com/docs/SDK3/#go-deeper
  must be built in order to have the reference Features to be able to track them down.
• XML reference of all commands & values - https://github.com/Parrot-Developers/arsdk-xml
• PyParrot (unofficial) Python SDK - https://github.com/amymcgovern/pyparrot
• Android - https://github.com/Parrot-Developers/groundsdk-android
  • Concepts (useful for tracking and impl features): https://github.com/Parrot-Developers/groundsdk-android/blob/master/doc/concepts.rst

https://github.com/elpiel/arsdk-java-generated/

Generated JAVA code from the https://github.com/Parrot-Developers/groundsdk-android repository + some information on how to generate it
Includes references from the arsdk-xml repository generated into Java classes of the Features and the Protocol in general.

Related issue for question on how this all works: Parrot-Developers/arsdk-xml#2

TODOs:

• ArDrone3 Implement (de)serialization for Feature::ArDrone3 #20
  • Implement (de)serialization for Ardrone3::GPSState #13 GPSState
  • .... TODO: Add the rest of the ArDrone3 commands
• TODO: Add the rest of the Commands to the list