Files
paparazzi/conf/airframes
Christophe De Wagter 2c55ce3686 Files for PDF exercise (#67) (#2687)
* files for PDF exercise

* Explicit call to python2 for systems that default to python3

* Description and comments fixes

[flight_plan] remove warning about dummy WP

Reformatted indents to 2 spaces

Added configs for ps4 gamepads, fixed typos (#68)

Update: for flight testing in the CyberZoo

Fix color gain in mav_course_exercise.xml airframe (#72)

[flight_plan] Re-measured the autoland border. It is not safe to exit the red sqaure so it auto-lands to prevent damage. (#73)

[Camera] Vision runs faster is unnecessary frames are not grabbed. (#74)

Co-authored-by: Matteo Barbera <matteo.barbera97@gmail.com>
2021-04-09 09:12:55 +02:00
..
2017-02-19 11:45:57 +01:00
2021-02-02 18:37:24 +01:00
2017-11-06 17:16:13 +01:00
2017-02-19 11:45:57 +01:00
2021-02-02 18:37:24 +01:00
2020-07-05 21:38:09 +02:00

If you have your own autonomous aircraft, it is really apriciated if you would:
* Create your own short UPPERCASE directory name within this one, e.g. "MYX"
* Prefix your airframe names with the same name in lowercase and add an underscore, e.g. myx_superdart.xml

This will make your life of updating Paparazzi much simpler...

It can be helpful to take a look at how other paparazzi enthousiasts like you did just that.

TIP: Remember to put the following DOCTYPE line in the top of your airframe file: 

 <!DOCTYPE airframe SYSTEM "../airframe.dtd">

Have a great day!