Skip to content
Snippets Groups Projects
  1. Jul 06, 2017
  2. Jul 05, 2017
  3. Jul 04, 2017
    • Beat Küng's avatar
      LandDetector: fix vehicle flight time · 1e2ce51c
      Beat Küng authored
      The problem was signed vs unsigned mixing together with 64bit conversion:
      int32_t flight_time = ...;
      uint64_t _total_flight_time = ...;
      _total_flight_time |= flight_time;
      When flight_time is negative, the last line would first extend the sign
      bit to the upper 32bits of the 64bit uint and then apply the bitwise OR.
      The fix is to use an unsigned 32 bit value.
      1e2ce51c
  4. Jul 02, 2017
  5. Jul 01, 2017
  6. Jun 30, 2017
  7. Jun 29, 2017
  8. Jun 28, 2017
    • Daniel Agar's avatar
      FW default PWM_RATE 50 · cd8c8ea5
      Daniel Agar authored
      cd8c8ea5
    • Jan Liphardt's avatar
      airspeed error message clarification (#7497) · d5eab23f
      Jan Liphardt authored
      In day to day practice, there are two reasons for fabsf(airspeed.differential_pressure_filtered_pa) > 15.0f
      
      1/ The sensor has not been calibrated. In this case, the sensor needs to be calibrated.
      2/ It's a windy day, and the operator has powered up the system without covering the pitot tube. In that case, you need to reboot with the pitot cover in place.
      
      The original message ('Check calibration') is ok, but why not be more direct? The user does not have to "check the calibration" - the user has to (a) either calibrate the system in the first place, or (b) not forget the pitot tube cover when powering up the system.
      d5eab23f
  9. Jun 27, 2017
Loading