Julian Oes 874c6f385b commander: unify offboard timeouts ...

The implementation before this change had two timeouts, a hard-coded
timeout of 0.5 seconds as well as a by param configurable timeout with
certain failsafe actions set.

This change aims to fix two problems:
1. The hard-coded offboard timeout can be triggered easily with sped up
   lockstep simulation. Since i t is hard-coded it can't be adapted to
   the speed factor.
2. The offboard signal can time out but no action will be taken just
   yet. This means we end up in an in-between stage where no warning or
   failsafe action has happened yet, even though certain flags are set
   to a timeout state.

This patch aims to fix this by unifying the two timeouts to the existing
configurable param. The convoluted double timeout logic is replaced by a
simple hysteresis.

For anyone that has previously not changed the default timeout param (0),
the param will now be changed to 0.5 seconds which reflects the
previously hardcoded time. For anyone with a specific timeout
configured, the behaviour should remain the same.

Also, going forward, timeouts lower than 0.5 seconds should be possible.

2020-03-04 09:35:14 +01:00

..

cannode

uavcannode updates and px4_fmu-v4_cannode example

2020-02-16 12:11:54 -05:00

px4fmu_common

commander: unify offboard timeouts

2020-03-04 09:35:14 +01:00

px4fmu_test

Fixed filename

2019-06-13 10:04:26 +02:00

CMakeLists.txt

cmake px4_add_romfs_files FATAL_ERROR if file doesn't exist

2019-12-12 13:42:30 -05:00