Browse Source
If a long-running process drains the mavlink stream rather than parsing it then the cached timestamp can be very, very out-of-date. When we next receieve a timestamp, then, there can be a signficant change in time when we weren't expecting it. run_cmd_get_ack can't use get_sim_time() as it might swallow the ack it is looking for.c415-sdk
1 changed files with 5 additions and 0 deletions
Loading…
Reference in new issue