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.

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.

of mixer trim values

Signed-off-by: Roman <bapstroman@gmail.com>

Signed-off-by: Roman <bapstroman@gmail.com>

- allow the user to apply an offset that covers the entire servo range

Signed-off-by: Roman <bapstroman@gmail.com>

Signed-off-by: Roman <bapstroman@gmail.com>

Signed-off-by: Roman <bapstroman@gmail.com>

Signed-off-by: Roman <bapstroman@gmail.com>

Signed-off-by: Roman <bapstroman@gmail.com>

Signed-off-by: Roman <bapstroman@gmail.com>

- 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>

Signed-off-by: Roman <bapstroman@gmail.com>

Signed-off-by: Roman <bapstroman@gmail.com>

This adds a define for the tune strength instead of hard-coding it with
a magic number.

The filter is disabled by default, thus the behavior is unchanged.

and call hrt_absolute_time() only once.