I would love an app that looks something like this.

I think all the data is here already,† but presented in an incomprehensible fashion.

† (Except whether a cable might be limiting the throughput, which I think would be very useful to know.)

I feel like if USB-C is such a mess where cables all look the same, having something like this to debug would help a lot.

I didn’t include power delivery, btw, which would also be helpful to know – I just don’t understand it very much.

Other nice things I could imagine:
- obviously, reacting in real time to connecting/disconnecting
- highlighting device(s) connected recently if you’re debugging
- showing activity on the cable if it’s happening
- highlighting special ports if they’re not equal
- eject buttons for devices that need it
btw thankful that even in making this mock I finally wrapped my head around this situation, as I had to make this table. I had no idea all these speeds were an option:
@mwichary I wrote a whole book about this
@glennf @mwichary I love my BLE CaberQU USB-C cable tester, that checks data speed AND charging capability for USB-C cables. (Two more things that do not correlate as much as most people would expect.)
@tphinney @mwichary I bought one. Defective. They sent me a new one. Same. The founder was baffled. I sent it back for QA. They sent me a 3rd and 4th. The one that I think worked failed on data rates on Thunderbolt 4/USB4 cables. It also kept testing cables that worked perfectly well at full speed/voltage as failed. So I don't know what to make of that.

@glennf @mwichary Oh wow. That sucks. I should have known you would have tried it!

I have had mostly good luck with it... but there is one cable that kinda flunked that I just tossed without further ado. Next time I will try it out in use as well, just to see.

@tphinney @mwichary Yes, it may be that I have edge case cables or got a spate of bad devices, but I tried a dozen cables and sometimes got different results by switching ends or rotating plugs. It could be that this is a USB-C problem, not a cyberQU problem, too!