14.01.2013 Views

A.R.Drone Developer Guide - Abstract

A.R.Drone Developer Guide - Abstract

A.R.Drone Developer Guide - Abstract

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

8 <strong>Drone</strong> Configuration<br />

The drone behaviour depends on many parameters which can be modified by using the AT*CONFIG<br />

AT command, or by using the appropriate AR<strong>Drone</strong>LIB function (see chapter 4.1).<br />

This chapter shows how to read/write a configuration parameter, and gives the list of parameters<br />

you can use in your application.<br />

8.1 Reading the drone configuration<br />

8.1.1 With AR<strong>Drone</strong>Tool<br />

AR<strong>Drone</strong>Tool implements a ’control’ thread which automatically retrieves the drone configuration<br />

at startup.<br />

Include the file in your C code to access the<br />

ardrone_control_config structure which contains the current drone configuration. Its most interesting<br />

fields are described in the next section.<br />

If your application is structured as recommended in chapter 5 or you are modifying one of the<br />

examples, the configuration should be retrieved by AR<strong>Drone</strong>Tool before the threads containing<br />

your code get started by AR<strong>Drone</strong>Tool .<br />

8.1.2 Without AR<strong>Drone</strong>Tool<br />

The drone configuration parameters can be retrieved by sending the AT*CTRL command with<br />

a mode parameter equaling 4 (CFG_GET_CONTROL_MODE).<br />

The drone then sends the content of its configuration file, containing all the available configuration<br />

parameters, on the control communication port (TCP port 5559). Parameters are sent as<br />

ASCII strings, with the format Parameter_name = Parameter_value.<br />

Here is an example of the sent configuration :<br />

55

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!