- Nov 06, 2018
-
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
- Nov 05, 2018
-
-
Dennis Mannhart authored
-
Dennis Mannhart authored
- set integral states and setpoint of reference state to 0 - set thrust to NAN if it will be computed from position and velocity control
-
Martina authored
obstacle_distance: update distances description according to latest obstacle_distance mavlink message
-
- Nov 02, 2018
-
-
Daniel Agar authored
-
Daniel Agar authored
-
Nuno Marques authored
-
- Nov 01, 2018
-
-
Jake Dahl authored
-
Jake Dahl authored
-
Jake Dahl authored
added unseal() and seal() around write_flash() for enabling/disabling cell undervoltage, we found out today this wasn't being written because that address is in protected flash
-
Jake Dahl authored
-
Jake Dahl authored
-
Jake Dahl authored
commented out something causing trouble with CI, it is in an unused function but I'd like to keep the comment there as a reference for future development effort
-
Jake Dahl authored
-
Jake Dahl authored
-
Jake Dahl authored
-
Jake Dahl authored
-
Jake Dahl authored
-
Jake Dahl authored
-
hdiethelm authored
* lis3mdl: Report calibration successful when starting with -C option * lis3mdl: Use PX4_OK, PX4_ERROR for return value / orb_unadvertise * Fixes #10740
-
Thunder authored
-
Julian Oes authored
This change has two effects: 1. We always acknowledge a param write no matter if the value was actually changed or not. This is according to the spec: https://mavlink.io/en/services/parameter.html#write-parameters 2. This fixes the bug where int32 parameters were not actually acked because the memory of the param value was casted directly to float and then compared. In the case of a int32 parameter set from 0 to 1 it would mean that the cast to float of the memory representation was still 0 and therefore it was assumed to be "no change" and the ack was omitted.
-