Is your feature request related to a problem? Please describe.
Current telemetry extraction only supports .tlog files, but DataFlash .bin files are more consistently collected (since they're in the flight controller), and have potentially faster data rates which .tlogs don't have access to. May include data after losing connection to the operator, and can potentially be used for slightly more accurate accelerometer integration (for very rough positioning estimates).
[ ] should feed in to the existing .csv to DataFrame pipeline/process
[ ] ideally should form part of a broader abstraction around information types instead of users needing to know specific internals of the log file formats they're using
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
alternative
reason(s) why unsuitable
only use .tlog files instead
ok-ish, but lower data rates, and not always available
Is your feature request related to a problem? Please describe. Current telemetry extraction only supports
.tlog
files, but DataFlash.bin
files are more consistently collected (since they're in the flight controller), and have potentially faster data rates which.tlog
s don't have access to. May include data after losing connection to the operator, and can potentially be used for slightly more accurate accelerometer integration (for very rough positioning estimates).Describe the solution you'd like
.bin
to.csv
, like existing.tlog
support.csv
toDataFrame
pipeline/process.tlog
files insteadmavlogdump
for extraction insteadAdditional context