- Mar 01, 2018
-
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
Daniel Agar authored
-
Anthony Lamping authored
-
Anthony Lamping authored
if the vehicle doesn't land and disarm at the end of the mission, the current sequence doesn't reset to 0
-
Anthony Lamping authored
-
Anthony Lamping authored
-
Anthony Lamping authored
-
Anthony Lamping authored
-
Roman authored
the mc pos controller handle it for now Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
- Feb 28, 2018
-
-
Andreas Antener authored
-
Andreas Antener authored
-
Andreas Antener authored
-
Paul Riseborough authored
-
- Feb 27, 2018
-
-
Beat Küng authored
When the timer callback is called at a higher rate than the logger can execute the main loop (which is never the case under normal conditions), the semaphore counter will increase unbounded, and eventually lead to an assertion failure in NuttX. The maximum semaphore counter is 0x7FFF, and when the logger runs at default rate (3.5ms), the logger task must be blocked for 0x7FFF*3.5/1000 = 114 seconds continuously for an overflow to happen. I see 2 cases where that could happen: - the logger execution blocks somehow, or busy-loops in an inner loop - a higher-prio task runs busy and hogs the CPU over a long period of time
-
Beat Küng authored
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
- Feb 26, 2018
-
-
Julian Oes authored
This gets rid of a printf.
-
- Feb 25, 2018
-
-
PX4 Jenkins authored
-
PX4 Jenkins authored
-
- Feb 24, 2018
-
-
Matthias Grob authored
On the Intel Aero and probably also other specific platforms the first measured voltage values despite connected battery are unuasable. The solution here is to start filtering and determining warning only after a measurement above 2.1V was received.
-
Matthias Grob authored
-
- Feb 23, 2018
-
-
Julian Oes authored
This prevents the autopilot from sending an invalid unix timestamp. Usually, if no time is set yet by a GPS, the date is somehow set to 2000-01-01, therefore we can ignore anything earlier than 2001.
-
Matthias Grob authored
-
Roman authored
of mixer trim values Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
- allow the user to apply an offset that covers the entire servo range Signed-off-by:
Roman <bapstroman@gmail.com>
-
ChristophTobler authored
-
- Feb 22, 2018
-
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
- increased the number of pwm outputs - handle PWM_SERVO_SET_MIN_PWM and PWM_SERVO_SET_MAX_PWM Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
mcsauder authored
-
Julian Oes authored
This adds a define for the tune strength instead of hard-coding it with a magic number.
-
Paul Riseborough authored
-