Difference between revisions of "Subsystems"
Jump to navigation
Jump to search
m |
(updated which gps drivers currently work for which firmware) |
||
Line 19: | Line 19: | ||
|[[Subsystem/gps|gps]] | |[[Subsystem/gps|gps]] | ||
|| | || | ||
*ublox | * ublox | ||
* ublox_utm | * ublox_utm | ||
* nmea | * nmea | ||
* mediatek_diy | * mediatek_diy | ||
* skytraq | * skytraq | ||
| all | | | ||
* all | |||
* fixedwing | |||
* all | |||
* all | |||
* rotorcraft | |||
| GPS drivers | |||
|- | |- | ||
|[[Subsystem/imu|imu]] | |[[Subsystem/imu|imu]] |
Revision as of 15:09, 7 May 2012
Mostly a subsystem is a part offering a specific functionality with a defined interface and can have multiple different implementations. (See sw/airborne/subsystems/...)
They are selected and configured with a <subsystem name="foo" type="bar">
in the firmware section of the airframe file.
All this does is basically include a makefile foo_bar.makefile that adds the respective sources and adds a few configuration options. (See conf/autopilot/subsystems/...)
This makes it easier to put an airframe file together (they replace the old raw makefile section) and also allows us to change the code and move/rename files behind the scenes without breaking everyones airframe files.
See FirmwareArchitecture for the differences to Modules.
Available Subsystems
Name | types | firmwares | description |
---|---|---|---|
gps |
|
|
GPS drivers |
imu |
|
|
IMU drivers |
ahrs |
|
all | AHRS algorithms |
radio_control |
|
|
Radio Control implementations |
telemetry |
|
all |
Telemetry implementations |
actuators |
|
|
drivers for different ESCs for rotorcraft |