- Feb 01, 2016
-
-
David Sidrane authored
-
David Sidrane authored
-
David Sidrane authored
-
David Sidrane authored
-
David Sidrane authored
-
Pavel Kirienko authored
-
nephne authored
-
- Jan 31, 2016
-
-
Lorenz Meier authored
-
Roman authored
-
Paul Riseborough authored
-
bugobliterator authored
-
bugobliterator authored
-
Paul Riseborough authored
-
bugobliterator authored
-
Paul Riseborough authored
-
Paul Riseborough authored
-
Paul Riseborough authored
-
Paul Riseborough authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Holger Steinhaus authored
-
- Jan 29, 2016
-
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Holger Steinhaus authored
-
Holger Steinhaus authored
-
Mark Whitehorn authored
-
Mark Whitehorn authored
-
Andrew Tridgell authored
the value '1000' is not really magic, and it was resulting in sending a single 1ms pulse on all IO channels for a brief instant on startup. With some servos this led to the control surfaces being at extremes (and straining) on startup. It may also contribute to making ESC calibration harder on multi-rotors In the worst case it could cause a IC motor with reverse throttle to go full throttle on startup A logic analyser shows the problem very clearly. Changing the default_value fields to 0 from 1000 fixes the issue and no pulses are generated until an explicit value suitable for the airframe is provided via one of the many methods PWM output values can be generated Conflicts: src/drivers/boards/px4fmu-v4/px4fmu_pwm_servo.c src/lib/ecl
-
- Jan 27, 2016
-
-
Andreas Antener authored
-
Andreas Antener authored
-
Roman authored
- after jumped takeoff set previous vel setpoint such that thrust setpoint is continuous
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Roman authored
-