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: b64abf48b2

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 'b64abf48b2'

${ noResults }

px4_autopilot/ROMFS

History

Nik Langrind ba5efa5642 px4io: When running HITL, don't publish actuator_outputs. Fixes #13471. ... When running in HITL mode, pwm_out_sim publishes actuator_outputs. px4io unconditionally publishes the uOrb actuator_outputs. When HITL is configured, the px4io copy of the uOrb has all zeros. The result is that there are two publications, one valid, and one all-zeros. This causes the HIL_ACTUATOR_CONTROLS mavlink message to be incorrect (all-zeros) and the SERVO_OUTPUTS_RAW mavlink message to be inconsistent, as it takes the data from one or the other uOrb randomly each cycle. The fix is to let px4io know that HITL is in effect when it is started, and modify px4io to suppress publication in this case. This is a bigger more complicated fix than I would like, but I think it is conceptually correct. Signed-off-by: Nik Langrind <langrind@gmail.com>		5 years ago
..
px4fmu_common	px4io: When running HITL, don't publish actuator_outputs. Fixes #13471.	5 years ago
px4fmu_test	Fixed filename	6 years ago
CMakeLists.txt	bl_update: build and include board bootloader if config available	5 years ago