Add new DeviceBusType_SERIAL to Device::DeviceId union
Add DRV_DIST_DEVTYPE's for all distance sensors
Change distance_sensor_s.id to distance_sensor_s.device_id
Modify all distance_sensor drivers to apply 'proper' device_id
* extend uuv_att_control
* add feedthrough thrust_y + thrust_z direction
* extend uuv_att_control
* add feedthrough thrust_y + thrust_z direction
* update formatting
* fix submarine sitl: indicate motor channel range 0..1 or -1..1 in simulation_mavlink.cpp (#16637)
change motor_count variable to 'pos_thrust_motor_count'
This is more specific to what is actually happening in the code.
'pos_thrust_motors_count' indicates number of motor channels which are configured with 0..1 range (positive thrust) all other motors are configured for -1..1 range
submarine only have motors with -1..1 range.
Thus, pos_thrust_motor_count = 0
Co-authored-by: Thies Lennart Alff <33184858+lennartalff@users.noreply.github.com>
* extend uuv_att_control
* add feedthrough thrust_y + thrust_z direction
* update formatting
Co-authored-by: Thies Lennart Alff <33184858+lennartalff@users.noreply.github.com>
* drivers/uavcannode: Add a simple parameter server
Added a simple parameter server using the libuavcan ParamServer class.
The parameter server exposes a selection of PX4 parameters via UAVCAN.
Also, Increased the stack size of the uavcan work queue in order to
prevent a stack overflow.
* uavcannode: fetch all active PX4 parameters
Co-authored-by: Kenneth Thompson <ken@flyvoly.com>
change motor_count variable to 'pos_thrust_motor_count'
This is more specific to what is actually happening in the code.
'pos_thrust_motors_count' indicates number of motor channels which are configured with 0..1 range (positive thrust) all other motors are configured for -1..1 range
submarine only have motors with -1..1 range.
Thus, pos_thrust_motor_count = 0
Co-authored-by: Thies Lennart Alff <33184858+lennartalff@users.noreply.github.com>
- matrix in PX4/Firmware (92f2043d8b): 054f8b12f4
- matrix current upstream: 977cf52322
- Changes: 054f8b12f4...977cf52322977cf52 2021-01-22 Julian Kent - Ignore debug line in code coverage
4837316 2021-01-22 Julian Kent - Fix small inconsistencies and compiler warnings
d540ca5 2021-01-13 Julian Kent - Coerce default epsilon values to Type
That enables the sensor checks by default
The default for the innovation check integral of 5 is rather conservative, thus
makeing it less likely to be triggered by accidnet (e.g. due to bad wind estimate).
Signed-off-by: Silvan Fuhrer <silvan@auterion.com>
Previously, the logic was not consistent with the description in the params.
It now, if the integral is enabled, declares innovation check failed if
integral is above threshold.
Signed-off-by: Silvan Fuhrer <silvan@auterion.com>
- ecl in PX4/Firmware (18bac6aff5): 99575d73e1
- ecl current upstream: b919f3ddf4
- Changes: 99575d73e1...b919f3ddf4b919f3d 2021-01-21 Paul Riseborough - EKF: Restore protection from extreme innovation values
efb78de 2021-01-21 Paul Riseborough - EKF: Set position fusion gate option false by default
556a195 2021-01-19 Paul Riseborough - EKF: Improve handling of non position mode large position innovations
JacobCrabill
Daniel Duecker
Daniel Agar
Lorenz Meier
Jukka Laitinen
David Sidrane
bazooka joe
honglang
PX4 BuildBot
Silvan Fuhrer
이충경
Matthias Grob
ArthurLamberticus
Hamish Willee
TheLegendaryJedi