UndocumentedCommands

Undocumented AR.Drone Commands

This page describe several observed AR.Drone commands and their suspected behavior. Note that these are not officially documented by Parrot and so using them may cause unexpected results!

These commands are compared to the SDK documentation version 1.7.

AT*PMODE

AT*PMODE=seq,int

Could this be related progressive video mode? Appears to be called on initialization; in fact in the Linux demo code it is the very first command sent to the drone on start.

AT*MISC

AT*MISC=seq,int,int,int,int

This is the second command set on start. The meaning of the values are unknown. On example startup the values 2, 20, 2000, 3000 are sent. The inputs are represented in the Linux example application and in that application's source code as MiscVar[0] through MiscVar[3].

AT*CTRL

AT*CTRL=seq,int

This command is partially documented. Possible values appear to be:

typedef enum
{
  NO_CONTROL_MODE = 0,          /*<! Doing nothing */
  ARDRONE_UPDATE_CONTROL_MODE,  /*<! Deprecated - Ardrone software update reception (update is done next run) */
                                /*<! After event completion, card should power off */
  PIC_UPDATE_CONTROL_MODE,      /*<! Ardrone PIC software update reception (update is done next run) */
                                /*<! After event completion, card should power off */
  LOGS_GET_CONTROL_MODE,        /*<! Send previous run's logs */
  CFG_GET_CONTROL_MODE,         /*<! Send active configuration file to a client through the 'control' socket UDP 5559 */
  ACK_CONTROL_MODE,             /*<! Reset command mask in navdata */
  CUSTOM_CFG_GET_CONTROL_MODE   /*<! Requests the list of custom configuration IDs */
} ARDRONE_CONTROL_MODE;