Signed-off-by: Claudio Micheli <claudio@auterion.com>

Since Timeout from onboard controller is something that does not require a lot of modifications there is no sense to having it parametrized.

Signed-off-by: Claudio Micheli <claudio@auterion.com>

Signed-off-by: Claudio Micheli <claudio@auterion.com>

Signed-off-by: Claudio Micheli <claudio@auterion.com>

Since commander handles all telemetry_status the same there is no need to subscribe to multiple instances.


Signed-off-by: Claudio Micheli <claudio@auterion.com>

Signed-off-by: Claudio Micheli <claudio@auterion.com>

Signed-off-by: Claudio Micheli <claudio@auterion.com>

Signed-off-by: Claudio Micheli <claudio@auterion.com>

Signed-off-by: Claudio Micheli <claudio@auterion.com>

Signed-off-by: Claudio Micheli <claudio@auterion.com>

Signed-off-by: Claudio Micheli <claudio@auterion.com>

Added COM_ONB_LOSS_T and COM_ONB_REG_T parameters to specify thresholds that triggers "onboard link lost" and "onboard link regained".


Signed-off-by: Claudio Micheli <claudio@auterion.com>

Signed-off-by: Claudio Micheli <claudio@auterion.com>

Major changes:
- Prevent  "HIGH LATENCY DATA LINK LOST" message to appear if iridium telemetry is not used.
- Prevent "DATA LINK LOSS" mavlink messages flooding when QGC is open and then closed.
- Changed "DATA LINK REGAINED" condition (use _datalink_last_heartbeat_gcs insthead of _datalink_lost)



Signed-off-by: Claudio Micheli <claudio@auterion.com>

when still close to ground

Migrate a few more var initializations from the Mavlink class constructor list to the respective declarations.

Whitespace formatting in mavlink_main.cpp/h and begin work of some variable initialization at declaration in mavlink_main.h.

Delete unnecessary #includes from mavlink_main.cpp and relocate a few #defines to mavlink_main.h for future variable initialization work.

The effect was that threads that tried to exit were unnecessarily kept
running.
This did not cause problems except for increased resource usage.

This solves a potential dead-lock when trying to shutdown: a call to exit()
stops all threads and calls all destructors for static objects.
The destructor of LockstepScheduler takes a lock. However this is not
safe, as the lock could already be taken (by any thread).