Difference between revisions of "Subsystems"

From PaparazziUAV
Jump to navigation Jump to search
(updated which gps drivers currently work for which firmware)
(added architecture column for specifying compatible subsystems, needs review)
Line 15: Line 15:


{| class="wikitable" border="1"
{| class="wikitable" border="1"
! Name !! types !! firmwares !! description
! Name !! Types !! Firmwares !! Architecture !! Description
|-
|-
|[[Subsystem/gps|gps]]
|[[Subsystem/gps|gps]]
Line 30: Line 30:
* all
* all
* rotorcraft
* rotorcraft
|
* all
| GPS drivers
| GPS drivers
|-
|-
Line 61: Line 63:
* rotorcraft
* rotorcraft
* rotorcraft
* rotorcraft
|
* all
* all
* all
* all
* all
* all
* all
* all
* all
* all
* all
* all
* all
|| IMU drivers
|| IMU drivers
(Note: traditional IR sensors can be used for fixedwing, but an IMU subsystem is not required)
|-
|-
|-
|-
Line 69: Line 86:
* int_cmpl_euler
* int_cmpl_euler
* int_cmpl_quat
* int_cmpl_quat
| all || AHRS algorithms
* infrared
|
* all
|
* all
|| AHRS algorithms
|-
|-
|[[Subsystem/radio_control|radio_control]]
|[[Subsystem/radio_control|radio_control]]
Line 80: Line 102:
* all
* all
* fixedwing
* fixedwing
|
* all
* STM32
* all
| Radio Control implementations
| Radio Control implementations
|-
|-
Line 88: Line 114:
* xbee_api
* xbee_api
|  
|  
all
* all
|
* all
* LPC21xx
* all
| Telemetry implementations
| Telemetry implementations
|-
|-
Line 106: Line 136:
* rotorcraft
* rotorcraft
* rotorcraft
* rotorcraft
|
* all
* all
* all
* all
* all
* all
| drivers for different ESCs for rotorcraft
| drivers for different ESCs for rotorcraft
(Note fixedwing ESCs and servos are possible on all firmwares/archs)
|}
|}


[[Category:Software]] [[Category:Developer_Documentation]] [[Category:Subsystems]]
[[Category:Software]] [[Category:Developer_Documentation]] [[Category:Subsystems]]

Revision as of 12:54, 10 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 Architecture Description
gps
  • ublox
  • ublox_utm
  • nmea
  • mediatek_diy
  • skytraq
  • all
  • fixedwing
  • all
  • all
  • rotorcraft
  • all
GPS drivers
imu
  • aspirin_v1.0
  • aspirin_v1.5
  • aspirin_v2.1
  • b2_v1.0
  • b2_v1.1
  • b2_v1.2
  • yai
  • aspirin_i2c
  • aspirin2_i2c
  • analog
  • ppzuav
  • crista
  • crista_hmc5843
  • all
  • all
  • all
  • all
  • all
  • all
  • all
  • fixedwing
  • fixedwing
  • fixedwing
  • fixedwing
  • rotorcraft
  • rotorcraft
  • all
  • all
  • all
  • all
  • all
  • all
  • all
  • all
  • all
  • all
  • all
  • all
  • all
IMU drivers

(Note: traditional IR sensors can be used for fixedwing, but an IMU subsystem is not required)

ahrs
  • float_dcm
  • int_cmpl_euler
  • int_cmpl_quat
  • infrared
  • all
  • all
AHRS algorithms
radio_control
  • ppm
  • spektrum
  • datalink
  • all
  • all
  • fixedwing
  • all
  • STM32
  • all
Radio Control implementations
telemetry
  • transparent
  • transparent_usb
  • xbee_api
  • all
  • all
  • LPC21xx
  • all
Telemetry implementations
actuators
  • mkk
  • asctec
  • asctec_v2
  • pwm_supervision
  • skiron
  • heli
  • rotorcraft
  • rotorcraft
  • rotorcraft
  • rotorcraft
  • rotorcraft
  • rotorcraft
  • all
  • all
  • all
  • all
  • all
  • all
drivers for different ESCs for rotorcraft

(Note fixedwing ESCs and servos are possible on all firmwares/archs)