Fix .PM3 traces that exceed single-byte range
This was done programmatically using python. Files with a range that fell outside of [-128,127], but which would fit into that range, were offset by the noted amount to ensure the file woul now fit within range [-128,127]. This allows the trace files to be converted to one-byte-per-sample binary format, for example. offset | filename -----|----- `-14` | `lf_Q5_mod-manchester.pm3` `-14` | `lf_Q5_mod-nrz.pm3` `-10` | `lf_Q5_mod-fsk1.pm3` `-15` | `lf_Q5_mod-biphase.pm3` `-9` | `lf_Q5_mod-fsk2.pm3`
This commit is contained in:
1 parent
f1d638c295
commit
1a7267ca53
5 files changed
+118427
-118427
No files matched your search
+23423
-23423
File diff suppressed because it is too large.
Load diff
+23896
-23896
File diff suppressed because it is too large.
Load diff
+23811
-23811
File diff suppressed because it is too large.
Load diff
+23722
-23722
File diff suppressed because it is too large.
Load diff
+23575
-23575
File diff suppressed because it is too large.
Load diff
Reference in new issue
Block a user