You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tree: 07e307b074

main

master

my1.12

my1.12-iic

pr-sensor-distance

release/1.12

sbg

tf-1.12

tf-1.12-print_test

tf-iic2uart

tf_driver-1.12

tf_i2c-1.12

tf_i2c_collis_pre

v1.13.0-BW

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '07e307b074'

${ noResults }

px4_autopilot/ROMFS/px4fmu_test/init.d

History

Daniel Agar 089c962d92 px4io: moving mixing to FMU side ... Using mixers on the IO side had a remote benefit of being able to override all control surfaces with a radio remote on a fixed wing. This ended up not being used that much and since the original design 10 years ago (2011) we have been able to convince ourselves that the overall system stability is at a level where this marginal benefit, which is not present on multicopters, is not worth the hazzle. Co-authored-by: Beat Küng <beat-kueng@gmx.net> Co-authored-by: Daniel Agar <daniel@agar.ca>		3 years ago
..
CMakeLists.txt	ROMFS list files explicitly instead of using GLOB_RECURSE (#9107)	7 years ago
rc.sensors	distance_sensor/sf1xx: rename to lightware_laser_i2c	4 years ago
rc.standalone	uORB move to PX4 platform layer	4 years ago
rcS	px4io: moving mixing to FMU side	3 years ago