Difference between revisions of "User/AirborneCodeReorg"

From PaparazziUAV
Jump to navigation Jump to search
Line 1: Line 1:
This page summarizes the changes needed to switch from the all "raw makefile in airframes" to a new "xml only aiframes" syntax
This page summarizes the changes needed to switch from the "raw makefile in airframes" to a new "xml only aiframes" syntax


==First step==
==First step==

Revision as of 20:01, 17 August 2010

This page summarizes the changes needed to switch from the "raw makefile in airframes" to a new "xml only aiframes" syntax

First step

  • fixed wings users:

Comment out or remove the following lines in the makefile section of your airframe.xml

ap.CFLAGS += -DRADIO_CONTROL
ap.srcs += radio_control.c $(SRC_ARCH)/ppm_hw.c  

Add a new xml section like this:

 <target name="fixed_wings" board="tiny_2.11">
   <subsystem name="radio_control" type="ppm"/>
 </target>

you can look in conf/airframes/microjet5.xml to see how it's done. The list of supported boards is "twog_1", "tiny_2.11", "tiny_2.1", "tiny_1.1", "tiny_0.99", "booz" and "lisa_l_1.0"

available subsystems

Name type airframe(s) description
radio_control ppm FW ppm based R/C input
radio_control spektrum FW spektrum based R/C input
telemetry transparent FW, rotor to be used with any serial link replacement
telemetry xbee_api FW, rotor for XBee modems in API mode
actuators ? FW automatically select 4015 or 4017 depending on board
attitude infrared FW
attitude gyro FW roll gyro and pitch gyro separately?
attitude imu FW ?? or call it ahrs? but infrared are not an ahrs...
gps ublox_lea5h FW
gps ublox_lea4p FW
gps skytraq FW
airspeed ets FW Eagle Tree Systems airspeed and baro sensor
navigation common FW or no type for standard nav?