* [autopilot] refactor autopilot API for both firmwares
With this, fixedwing and rotorcraft are mostly using the same interface
for the autopilot. Some specific code and messages handling are still
firmware dependent.
A large part of the autopilot logic of the fixedwing is moved from
main_ap to autopilot_static.
More getter/setter functions are provided.
* [autopilot] update the rest of the system and the conf
for using the refactored autopilot API
* [autopilot] fix some errors from CI servers
* [actuators] use dummy actuators module to prevent autoloading
* Rename Bart_heliDD_INDI.xml to tudelft_bs_helidd_indi.xml
* Rename Bart_heliDD_pid.xml to tudelft_bs_helidd_pid.xml
* Delete tudelft_course2016_bebop_colorfilter.xml
* Delete tudelft_course2016_bebop_avoider.xml
* [actuators] don't autoload actuators when set to 'none'
* [gcs] autodetect firmware for strip mode button
This pull request allows you to use both the front camera and the bottom camera on the bebop, and to run optical flow on the bottom camera while running something else on the front camera.
- modules can call cv_add_to_device(&camera, fun) to register the callback fun for the specified camera with the video thread
- use a linked list with listeners for the video
- saving jpeg encoded shots is now in a separate video_capture module
Each "board" (e.g. ARDrone2 or Bebop) defines a video_config_t for each camera,
then you only need to specify 'front_camera' or 'bottom_camera' instead of setting all parameters
Christophe De Wagter
Freek van Tienen
Gautier Hattenberger
Fabien-B
Roland Meertens
Felix Ruess
Ewoud Smeur