px4io driver: publish input_rc even if RC connection has been lost
px4io: do not include failsafe condition into rc_lost flag
Proper failsafe handling onboard, including throttle failsafe condition if enabled
Only publish RC inputs if we have seen some valid inputs at some point
Simplify the failsafe handling, reduce 3 params to one
Trigger failsafe action also on failsafe flag
px4io: Allow RC failsafe detection as valid feature
Make throttle failsafe depend on the failsafe threshold parameter. Make the parameter optional (no harm if not found).
px4io driver: publish input_rc even if RC connection has been lost
px4io: do not include failsafe condition into rc_lost flag
px4io: Remove unused variable
px4io: Guard against the RC failsafe value of channel 5 causing a manual override action if set to manual in failsafe
Merge branch 'sbus_failsafe' into failsafe_cleanup
Merged minimal S.BUS failsafe changes
px4io driver: Only publish RC signal if it was at least once valid.
Merged SBUS minimal changes
sensors and px4io driver: Guard against failsafe trigger for inverted remotes
Fix logic for S.Bus failsafe detection
Merge pull request #799 from PX4/failsafe_sbus_cleanup

Failsafe sbus cleanup
navigator hotfix: Increase acceptance range for yaw setpoints.