1. 15 Aug, 2015 1 commit
  2. 11 Aug, 2015 7 commits
  3. 08 Aug, 2015 3 commits
    • ProDrone's avatar
      Added CRC check to SUMD handler · f26af1d8
      ProDrone authored
      Officially the CRC check is part of the SUMD protocol.
      Framing errors are already covered and i expect these to occur around
      the same time as CRC errors, so i am not sure if someone will ever
      notice the difference...
    • ProDrone's avatar
      rcData[] is keeping the right values now. · 95840ae5
      ProDrone authored
      Logic for valid flightchannel detection is inverted in order to detect
      the first flightchannel failure instead of waiting to check them all.
      Clear PWM channel capture on read.
      This invalidates the control channels on read. They are validated by
      receiving a good value BEFORE the aux channels are received. This is
      done because control channels configures to go OFF on failsafe are
      detected with a PWM capture time-out. Time-out took so long that all aux
      channels where overwritten by their RX configured failsafe values BEFORE
      the invalid (=OFF) control channel was detected.
    • ProDrone's avatar
      SUMD channels are received as 16 bit values instead of 32 · aaa7c7c5
      ProDrone authored
      Preserve 32 bytes of RAM.
  4. 07 Aug, 2015 1 commit
  5. 06 Aug, 2015 1 commit
  6. 05 Aug, 2015 2 commits
  7. 04 Aug, 2015 3 commits
  8. 03 Aug, 2015 20 commits
  9. 31 Jul, 2015 2 commits
    • Konstantin Sharlaimov (DigitalEntity)'s avatar
    • ProDrone's avatar
      RPY to mid-stick and T to lowest (or mid for 3D). · 08b376f2
      ProDrone authored
      On bad (out-of-range) pulses; ROLL, PITCH, YAW will go to `mid_rc` and
      THROTTLE will go to `rx_min_usec` (to `mid_rc` for 3D mode). So these
      channels will no longer be set by the user directly.
      Fallback values for the aux switches (0 .. max) can be set with this
      version. Since these switches may trigger all kind of things, the user
      needs control over them in case of a RX failsafe event.
      A single flight control channel failure (first 4) when using parallel
      PWM is interpreted as a failure for all flight control channels (first
      4), since the craft may be uncontrollable when one channel is down. (+4
      squashed commit)
      Squashed commit:
      [dbfea9e] Apply fallback values also when serial_rx init failed and/or
      disconnected and/or no signal received.
      [b5a2ecd] Added get/set MSP commands for RXFAIL config
      Bumped API minor version up.
      [c0e31ce] minor change for coding standard
      [322705f] Added programmable RX channel defaults on rx lost Update #2