Difference between revisions of "Subsystems"
(simplified table) |
IHaveADrone (talk | contribs) (→Available Subsystems: added indi) |
||
Line 215: | Line 215: | ||
* int_quat | * int_quat | ||
* float_quat | * float_quat | ||
* | * int_euler | ||
* float_euler | |||
* indi | |||
| | | | ||
* rotorcraft | * rotorcraft |
Revision as of 11:13, 17 June 2015
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/firmwares/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, as well as how to write a new subsystem.
Available Subsystems
Name | Types | Firmwares | Architecture | Description |
---|---|---|---|---|
gps |
|
|
|
GPS drivers |
imu |
|
|
|
IMU drivers
Traditional IR sensors can be used for fixedwing but an IMU subsystem is not required |
ahrs |
|
|
|
AHRS algorithms |
ins |
|
|
|
INS algorithms
Most of the INS filters are only providing position and speed, and they need to be used together with an AHRS filter for attitude Currently, only the experimental invariant filter is a full INS |
radio_control |
|
|
|
Radio Control implementations |
telemetry |
|
|
|
Telemetry implementations |
actuators |
|
|
|
Drivers for different ESCs and servos |
stabilization |
|
|
|
Attitude control system for rotorcraft |