How to connect an Android device to the AR.Drone ? In order to communicate with the drone, you need to set up a connection between your Android device and the drone first. The drone acts as a Wifi access point hence you need to set up a Wifi connection. In the following this setup procedure is explained using screenshots of an Android 2.2 emulator, therefore the screen on your real device will differ slightly. Note: it is not possible to connect an Android emulator to the drone ! Open the "Settings" dialog and choose "Wireless & networks"     Here you need to enable Wi-Fi. And choose "Wi-Fi"-settings. Your phone will scan all the surrounding access points and present you a list of available "Wi-Fi networks" (in the figure below no Wi-Fi networks are available, because we're running an emulator). After some seconds you should see the AR.Drone's access point, it is named something like "ardrone_%ID%". Touch the list item to establish a connection. The drone will assign an IP address to your Android device using DHCP. Hence you need to make sure, DHCP is enabled for your connection. Press the menu button and go to the "Advanced" settings. "Use static IP" must be disabled. Your device should have been assigned an IP address by the drone, it's something like "192.168.0.2".   How to import YADrone sources into Eclipse ? In order to setup an eclipse project containing all of YADrone's source and library files, e.g. because you want to have a look at or alter the source, just follow these steps: Download the YADrone "full source - Eclipse project" (from the main page). Start Eclipse and go to "File --> Import ...". A dialog will appear (see figure below). Choose "General --> Exisiting Projects into Workspace". After clicking "Next", a new window "Import Projects" is displayed. Here, you first need to select "Select archive file" and then use the "Browse..." button to navigate to the zip file you just downloaded. Eclipse will automatically recognize the contents and offer you two projects, namely "YADrone" and "YADroneAndroid". Check the one you need (or check both). Click "Finish" and you're done. For a quick test, just run "de.yadrone.apps.controlcenter.YADroneControlCenter".   What about the "Magic must be correct"-Exception ? Sometimes, when you start the drone, an exception is thrown and displayed in the console: com.shigeodayo.ardrone.navdata.NavDataException: Magic must be correct : expected 1432778632, was 1432778633 at com.shigeodayo.ardrone.navdata.NavDataParser.requireEquals(NavDataParser.java:103) at com.shigeodayo.ardrone.navdata.NavDataParser.parseNavData(NavDataParser.java:40) at com.shigeodayo.ardrone.navdata.NavDataManager.run(NavDataManager.java:91) at java.lang.Thread.run(Unknown Source) You can ignore this exception ! Navdata packets may contain kind of a versioning information: that's the magic. This is a series of bytes (0x55667788) indicating which header version is used by the drone. Recently, the header version has been updated (I think because a new field has been introduced, some say it's now 68 bytes instead of 64 bytes). Nevertheless, YADrone checks this header version (0x55667788, in decimal it's 1432778632) and if a wrong version has been detected (e.g. 0x55667789, that's 1432778633) it throws an exception. The new version does not seem to influence the way YADrone parses the header, hence for now it is of no importance. [ Back ]