I’ve run sdtest in the ProffieOS/Arduino serial monitor successfully in the past, but over the last few months it hasn’t been working. Finally got around to trying again with fresh cables (always start with: is it plugged in?) but no luck. Uploads are working fine. Commands such as stab, blast, on/off…all working in the serial monitor.
I usually set my USB Type to “serial” only to avoid bad eject SD card corruption, so I set it to “serial + mass storage” thinking that might help. Did that matter?
Still getting a “whut?” after entering sdtest as a command. Any suggestions? It’s not critical but that data (sd speed/streams) is important enough that I’d like to have access to it. Thanks 
Do you have DISABLE_DIAGNOSTIC_COMMANDS in your config file?
1 Like
Well, in the last edition of my config I had it hashed out, but in “cleaning up” the new version I left it in.
Working now, with depressing results. My usual rocksteady choice is coming back:
Time to read blocks: Average speed: 792.63 kb/s, 8.99 simultaneous audio streams.
Oof, that hurts. Thanks!!
1 Like
I should’ve taken this advice the first few times. Thanks for the reminder…I think I’ll put these in everything.
I’ve been using Gigastone, Samsung, and Kodak U3 cards with reasonable success–I did some early testing and they consistently out-performed the standard C10/U1 SD cards–but I have not been using them long enough to confirm just how durable their performance will be.
I look for the “U3” symbol and preferably an “A2” designation although the A1’s have been working fine. Here are some links to explain the coding for SD card performance:
A Guide to Speed Classes for SD and microSD Cards - Kingston Technology
A1 vs A2 SD Card Ratings Explained
Yes, UHS 3 is recommended.
Ah, yes. I was using Kioxia cards because they were more stable during the ‘SD card not found’ era. But I see now they are U1. Wahwahwaaaaah…