Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MSC (usb mass storage) mode corrupting blackbox logs #9983

Open
hughsaunders opened this issue Apr 27, 2024 · 0 comments
Open

MSC (usb mass storage) mode corrupting blackbox logs #9983

hughsaunders opened this issue Apr 27, 2024 · 0 comments

Comments

@hughsaunders
Copy link

Current Behavior

I downloaded blackbox logs via msc and couldn't open them.
I then took the sdcard out of the flight controller and inserted it directly into the laptop and copied the same logs.
The SHA signatures are different between the two sets of files, also blackbox_decode can read the files from the sd copy
but not from the msc copy.

I tried the msc copy multiple times and got the same SHA each time, it wasn't a one off error.

SHAS:

hMBPpersonalWired:black box logs hughsaunders$ shasum */*.TXT
c1606a5549259c6a96a56c6a9ef5520bf389927a  msc copy/LOG00001.TXT
51523a8ec33ed9c03b0f2ecfe469ec4924cab49b  msc copy/LOG00002.TXT
3dd26091de20abc46d58029789453a120f7c23c8  sd copy/LOG00001.TXT
0d959f5d831db6783cf83e668ef7cbfb7878a73b  sd copy/LOG00002.TXT

Attempt to decode msc copy files:

hMBPpersonalWired:black box logs hughsaunders$ blackbox_decode msc\ copy/LOG00001.TXT 
Couldn't find the header of a flight log in the file 'msc copy/LOG00001.TXT', is this the right kind of file?

Attempt to decode SD copy files:

hMBPpersonalWired:black box logs hughsaunders$ blackbox_decode sd\ copy/LOG00001.TXT 
Decoding log 'sd copy/LOG00001.TXT' to 'sd copy/LOG00001.01.csv'...

Log 1 of 1, start 04:51.512, end 20:57.935, duration 16:06.422

Statistics
Looptime           1005 avg            3.3 std dev (0.3%)
I frames   30016  117.1 bytes avg  3514012 bytes total
P frames   30007   77.4 bytes avg  2321341 bytes total
H frames     236   10.0 bytes avg     2360 bytes total
G frames    9760   24.5 bytes avg   239419 bytes total
E frames       1    7.0 bytes avg        7 bytes total
S frames    3588   45.8 bytes avg   164497 bytes total
Frames     60023   97.2 bytes avg  5835353 bytes total
Data rate   62Hz   6463 bytes/s      64700 baud

25 frames failed to decode, rendering 9 loop iterations unreadable. 9 iterations are missing in total (9ms, 0.00%)
900465 loop iterations weren't logged because of your blackbox_rate settings (906019ms, 93.75%)

Generated by INAV blackbox_decode 7.1.0 16e6283

Steps to Reproduce

  1. Configure black box logs and go flying
  2. Connect FC via usb, open configurator and on CLI tab enter msc
  3. FC enters usb mas storage mode
  4. Copy BBL files via OS standard method
  5. Attempt to decode BBL via blackbox_decode and find them corrupted.

Expected behavior

Copying blackbox logs via MSC works the same as removing the sdcard and copying the files manually.

Suggested solution(s)

Debug msc mode? Or if MSC isn't supported on MacOs, put up a warning?

Additional context

CLI dump: https://pastebin.com/UercZGc2
Host OS: MacOS 12.7.4

I notice from this document, that msc copy and sd copy should be equivalent: https://github.com/iNavFlight/inav/blob/master/docs/USB_Mass_Storage_(MSC)_mode.md

  • FC Board name and vendor: Atomrc F405 Navi
  • INAV version string:
# INAV/ATOMRCF405NAVI 7.1.0 Mar 27 2024 / 12:49:53 (59a6ee61)
# GCC-10.3.1 20210824 (release)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant