Beat Küng edfcdaa008 commander: check for stale arming_check_reply messages ...

based on the message timestamp.

Previously it was possible to run into the following case:
- 2 external modes are registered (running inside the same ROS node)
- they time out due to the micro xrce agent being blocked for some reason
- PX4 removes them
- the latest arming check replies still arrive to PX4
- the application restarts
- the first mode gets registered
- PX4 handles the previous arming check reply, and clears
  waiting_for_first_response, which reduces the timeout
- the second mode registers and as part of that checks for message
  compatibility. This takes ~1s, triggering a timeout of the first mode

2025-08-26 14:38:05 +02:00

..

checks

commander: check for stale arming_check_reply messages

2025-08-26 14:38:05 +02:00

CMakeLists.txt

PR: add optical flow arming check (#24375)

2025-02-26 08:41:12 +01:00

Common.cpp

HealthAndArmingChecks: allow to warn in certain modes and fail arming checks in other modes

2025-01-30 18:45:10 +01:00

Common.hpp

HealthAndArmingChecks: allow to warn in certain modes and fail arming checks in other modes

2025-01-30 18:45:10 +01:00

HealthAndArmingChecks.cpp

Commander: Introduce global_position_relaxed (#24280)

2025-05-28 08:16:10 +02:00

HealthAndArmingChecks.hpp

PR: add optical flow arming check (#24375)

2025-02-26 08:41:12 +01:00

HealthAndArmingChecksTest.cpp

refactor commander: remove unused argument is_armed in Report class

2024-11-21 14:16:22 +01:00