To access developer settings with FreeFlight7, go to parameters (on the top right corner), select the advanced tab (on the top, the third tab) and select the Developer tab (on the left).
In this tab, three developer settings are available:
Direct connection to the drone#
The ANAFI Ai firmware disables the possibility to connect to a drone directly (not through a SkyController) from a PC or a smartphone by default.
Thus, it is not possible to connect to a drone anafi-ai.local address over wifi without first enabling the “Direct connection” setting of the drone.
To enable this option, a security ADB public key needs to be authorized by the drone firmware. A default ADB public key is available on your local machine at this path:
A new ADB key pair can be generated with this following command:
$ adb keygen [myfile]
Copy-paste the ADB public key in the text area that appears after enabling the Shell access option in FreeFlight7.
Reboot the drone. The remote shell can now be accessed with the following commands:
$ adb connect anafi-ai.local:9050 $ adb shell
The drone must be connected to the computer through Wi-Fi.
AirSDK missions logs#
When this option is enabled, the missions can write logs to rotating log files. To learn more about how to write logs from your mission, please refer to the Ulog documentation.
/!\ Mission logs are not encrypted and all missions and other users have access to the logs. Therefore sensitive information should not be logged by a mission, and before a mission is distributed logs should be cleaned up /!\
To retrieve mission logs you have to plug your drone to a computer with a USB cable. The logs will be available at /missions-data/FDR/log.bin
These files can be read with the Parrot Logan tool. Logan can be installed with the following command (it is assumed that steps described in section Adding Linux packages are already completed):
$ sudo apt-get install parrot-tools-logan-lite
Live access to mission logs#
Regardless of the previous setting, mission logs are available within an adb shell session with the following command:
$ ulogcat -b autopilot