I've been suffering USB problems with Linux but this also raises the question of USB cables. All too often a charge only cable turns up as well as crap steel/aluminium cored cables which break easily.
I'm thinking of soldering up one right now. Chop off USB A and Micro USB female ends from extension cables. Solder to two sets of 5 pins and get the multimeter out.
OR
Get out an old UNO and do an auto tester. It would need a switchable load/supply to measure the cable resistance and shorts. OLEDs are cheap, may as well have a proper display. Maybe an ESP32 with built in display.
And of course the deluxe model has a TFT screen, web interface, appropriate test/fail sounds. Fail should burn out the cable to ensure it's never used again.
@hilldweller Not sure if it's related, but there are such things as USB testers and USB cable testers. However I would bet the software drivers are the most likely problem, not the hardware.
Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting
W-O-W eye opener. Working my way through some cable there seems to be about 0.5E per wire generally, but the wow bit is a couple of cables used for charging show 30E, wriggle and a bit less, squirt of contact cleaner and down to 0.5E.
All that scanning of USB data and some problems could be as simple a dirty contacts.
One cable I had on the bench was charging only, I wonder if I fell for that one in all my feverish testing.
1E in the power lines is pretty significant if pulling max current out of the USB.
@hilldweller What is E?
Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting
@hilldweller What is E?
Maybe me cracking up, but I'm sure E was often used on circuit diagrams for ohms. Illogical I know. I typed it automatically.
Are you sure E didn't represent voltage (Electromotive force? Ohms law was E = IxR)
I had a psychic girlfriend but she left me before we met.
Are you sure E didn't represent voltage (Electromotive force? Ohms law was E = IxR)
It certainly does.
@hilldweller It's certainly not ohms, I assume volts when I see E. For ohms an acceptable abbreviation would be R.
Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting