[radio_control] cleanup channel defines - PPM: remove PPM_NB_CHANNEL define an always decode RADIO_CTL_NB (number of channels in radio.xml) - PPM: the actually used/needed channels RADIO_CONTROL_NB_CHANNEL default to RADIO_CTL_NB but can be overwritten by user e.g. to use less channels for intermcu - SBUS: only provide a default for RADIO_CONTROL_NB_CHANNEL - Spektrum: always try to decode up to SPEKTRUM_NB_CHANNEL (12), but copy only used RADIO_CONTROL_NB_CHANNEL to radio_control.values - error if RADIO_CONTROL_NB_CHANNEL > max available channels As far as I can discern this should finally make it possible to override the actually used RADIO_CONTROL_NB_CHANNEL from the airframe file (e.g. to transfer less via intermcu) while still using the proper number of channels for parsing.
MAIN README
Paparazzi UAS
Paparazzi is an attempt to develop a free software Unmanned (Air) Vehicle System. As of today the system is being used successfuly by a number of hobyists, universities and companies all over the world, on vehicle of various size ( 100g to 25Kg ) and of various nature ( fixed wing, rotorcrafts, boats and surface vehicles).
Up to date information is available in the wiki http://wiki.paparazziuav.org
and from the mailing list [paparazzi-devel@nongnu.org] (http://savannah.nongnu.org/mail/?group=paparazzi) and the IRC channel (freenode, #paparazzi).
Required Software
Installation is described in the wiki (http://wiki.paparazziuav.org/wiki/Installation).
For Ubuntu users, required packages are available in the [paparazzi-uav PPA] (https://launchpad.net/~paparazzi-uav/+archive/ppa), Debian users can use the [OpenSUSE Build Service repository] (http://download.opensuse.org/repositories/home:/flixr:/paparazzi-uav/Debian_7.0/)
Debian/Ubuntu packages:
- paparazzi-dev is the meta-package that depends on everything needed to compile and run the ground segment and the simulator.
- paparazzi-jsbsim is needed for using JSBSim as flight dynamic model for the simulator.
Recommended cross compiling toolchain: https://launchpad.net/gcc-arm-embedded
Directories quick and dirty description:
conf: the configuration directory (airframe, radio, ... descriptions).
data: where to put read-only data (e.g. maps, terrain elevation files, icons)
doc: documentation (diagrams, manual source files, ...)
sw: software (onboard, ground station, simulation, ...)
var: products of compilation, cache for the map tiles, ...
Compilation and demo simulation
-
type "make" in the top directory to compile all the libraries and tools.
-
"./paparazzi" to run the Paparazzi Center
-
Select the "Microjet" aircraft in the upper-left A/C combo box. Select "sim" from upper-middle "target" combo box. Click "Build". When the compilation is finished, select "Simulation" from the upper-right session combo box and click "Execute".
-
In the GCS, wait about 10s for the aircraft to be in the "Holding point" navigation block. Switch to the "Takeoff" block (lower-left blue airway button in the strip). Takeoff with the green launch button.
Uploading of the embedded software
-
Power the flight controller board while it is connected to the PC with the USB cable.
-
From the Paparazzi center, select the "ap" target, and click "Upload".
Flight
- From the Paparazzi Center, select the flight session and ... do the same than in simulation !
