Difference between revisions of "Subsystems"
Jump to navigation
Jump to search
(comparison now in FirmwareArchitecture) |
m |
||
Line 1: | Line 1: | ||
<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages hideprefix=always>Subsystems</categorytree> | <categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages hideprefix=always>Subsystems</categorytree> | ||
Mostly a subsystem is a part offering a specific functionality with a | Mostly a subsystem is a part offering a specific functionality with a | ||
defined interface and can have multiple different implementations. (See <tt>sw/airborne/subsystems/...</tt>) | defined interface and can have multiple different implementations. (See <tt>sw/airborne/subsystems/...</tt>) |
Revision as of 05:32, 21 April 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 |
|
all | 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 |