Commits on Apr 18, 2022

1. core: use separate mavlink_status_t again …

   Previously, we made an attempt to fix the outgoing sequence numbers.
   Therefore, we would ignore the chan number for the mavlink_status_t,
   however, this lead to serious problems when doing system tests with
   multiple mavsdk instances sending messages to each other as they would
   sometimes both use the mavlink_status_t data and mess up each others
   parsing.
   
   Therefore, we remove the previous hack, and go back to separate
   mavlink_status_t. This will probably mess up outgoing sequence numbers
   but given they can't reliably be used to assess drop rate anyway it's
   an ok pill to swallow, for now. And this enables more consistent system
   tests, and in general applications with more than one Mavsdk instance.

   

   julianoes committed Apr 18, 2022
   Configuration menu

   • View commit details
   • Copy full SHA for f9309ae
   • Browse repository at this point

   Copy the full SHA

   f9309ae View commit details

   Browse the repository at this point in the history