Difference between revisions of "Subsystems"
Jump to navigation
Jump to search
| (6 intermediate revisions by 5 users not shown) | |||
| 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> | ||
{| class="wikitable" | |||
|- | |||
| Since '''v6.0''' all subsystems have been moved to modules and no longer exist in Paparazzi. | |||
|} | |||
Mostly a subsystem is a part offering a specific functionality with a | Mostly a subsystem is a part offering a specific functionality with a | ||
| Line 5: | Line 11: | ||
They are selected and configured with a <source lang="xml" enclose="none"><subsystem name="foo" type="bar"></source> in the [[Airframe_Configuration#Firmware_and_Hardware_definitions|firmware section of the airframe file]]. | They are selected and configured with a <source lang="xml" enclose="none"><subsystem name="foo" type="bar"></source> in the [[Airframe_Configuration#Firmware_and_Hardware_definitions|firmware section of the airframe file]]. | ||
{| class="wikitable" | |||
|- | |||
| Since '''v5.8''' it is possible to safely replace ''subsystem'' by ''module'' in your airframe file. The roadmap of Paparazzi is to convert existing subsystems to [[modules]]. | |||
|} | |||
All this does is basically include a makefile <tt>foo_bar.makefile</tt> that adds the respective sources and adds a few configuration options. (See <tt>conf/firmwares/subsystems/...</tt>) | All this does is basically include a makefile <tt>foo_bar.makefile</tt> that adds the respective sources and adds a few configuration options. (See <tt>conf/firmwares/subsystems/...</tt>) | ||
| Line 14: | Line 24: | ||
== Available Subsystems == | == Available Subsystems == | ||
{| class="wikitable" border="1" | {| class="wikitable sortable" border="1" | ||
! Name !! Types !! Firmwares !! Architecture !! Description | ! Name !! Types !! Firmwares !! Architecture !! Description | ||
|- | |- | ||
| Line 115: | Line 125: | ||
* float_dcm | * float_dcm | ||
* int_cmpl_euler | * int_cmpl_euler | ||
* float_mlkf | * float_mlkf | ||
* infrared | * infrared | ||
| Line 135: | Line 144: | ||
* ardrone2 | * ardrone2 | ||
* float_invariant | * float_invariant | ||
* ekf2 | |||
| | | | ||
* fixedwing | * fixedwing | ||
| Line 145: | Line 155: | ||
* rotorcraft | * rotorcraft | ||
* all (experimental, only tested on fw) | * all (experimental, only tested on fw) | ||
* all | |||
| | | | ||
* all | * all | ||
| Line 155: | Line 166: | ||
* all | * all | ||
* mcu with fpu (e.g. stm32f4) | * mcu with fpu (e.g. stm32f4) | ||
* all | |||
|| INS algorithms | || 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 | Most of the INS filters are only providing position and speed, and they need to be used together with an AHRS filter for attitude | ||
| Line 216: | Line 228: | ||
* int_quat | * int_quat | ||
* float_quat | * float_quat | ||
* | * int_euler | ||
* float_euler | |||
* indi | |||
| | | | ||
* rotorcraft | * rotorcraft | ||
| | | | ||
* all | * all | ||
| Attitude control system for rotorcraft | | Attitude control system for rotorcraft | ||
Latest revision as of 02:45, 29 November 2021
| Since v6.0 all subsystems have been moved to modules and no longer exist in Paparazzi. |
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.
| Since v5.8 it is possible to safely replace subsystem by module in your airframe file. The roadmap of Paparazzi is to convert existing subsystems to modules. |
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 |