Current Behavior
Being able to ping your FC via mavlink is a really usefully feature for testing / develpment. It looks like inav does not support timesync
(which replaced the ping protocoll, see discussion on ardupilot
Suggested Solution
Add timesync protocoll to inav mavlink, perhaps in a client-only version - this would allow any modern GCS like QGroundControll,
QOpenHD to ping the inav FC via mavlink (+ when done properly even calculate latencie(s) and more of the link)
Who does this impact? Who is this for?
All users using inav with mavlink telemetry
Current Behavior
Being able to ping your FC via mavlink is a really usefully feature for testing / develpment. It looks like inav does not support timesync
(which replaced the ping protocoll, see discussion on ardupilot
Suggested Solution
Add timesync protocoll to inav mavlink, perhaps in a client-only version - this would allow any modern GCS like QGroundControll,
QOpenHD to ping the inav FC via mavlink (+ when done properly even calculate latencie(s) and more of the link)
Who does this impact? Who is this for?
All users using inav with mavlink telemetry