Replay telemetry log data even there are uninterpretable trailing bytes #14210
Description
Feature Description
Hi,
If we upload a telemetry log file with more than 8 bytes of trailing zeros that are not part of any mavlink packet, QGC refuses to replay it by showing a Log Replay Link Error.
Instead of throwing an error, it is good to have automatic tlog trimming that ignores those meaningless bytes and then replays the log with some warning messages.
Use Case
It is possible that we have a tlog writer on the drone that writes logs to the onboard computer. In situations like crashes or power outages, the log file may not be properly closed leaving trailing dirty bytes in the tlog file.
Flight Stacks
No response
Vehicle Types
No response
Platforms
No response