Question Is there anyway to test speed of USB-C port on my PC ?

[NoGagMaestro]

https://www.msi.com/Motherboard/PRO-B760-P-WIFI-DDR4/Specification

I have a MSI Pro B760-P Wifi DDR 4 Motherboard which has a 1x USB 3.2 Gen2 Type C (Rear) on the back . I use it to transfer files for my nintendo switch and phone. I notice when using Nintendo it states high speed USB 2.0 and on my Note 10+ plus phone I will get the fast charging display upon connection but it immediately drops to slow charging. I'm wondering if the port is not working at the speeds it's supposed to and if not how do I change it. Thanks

Here is what it says when viewed under usb device viewer
Port3] : SAMSUNG Mobile USB Composite Device


Is Port User Connectable: yes
Is Port Debug Capable: no
Companion Port Number: 19
Companion Hub Symbolic Link Name: USB#ROOT_HUB30#4&10ea92fe&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
Protocols Supported:
USB 1.1: yes
USB 2.0: yes
USB 3.0: no

Device Power State: PowerDeviceD0

---===>Device Information<===---
English product name: "SAMSUNG_Android"

ConnectionStatus:
Current Config Value: 0x01 -> Device Bus Speed: High (is SuperSpeed or higher capable)
Device Address: 0x0B
Open Pipes: 8

===>Device Descriptor<===
bLength: 0x12
bDescriptorType: 0x01
bcdUSB: 0x0210
bDeviceClass: 0x00
*!*ERROR: device class should be Multi-interface Function 0xEF
When IAD descriptor is used
bDeviceSubClass: 0x00
*!*ERROR: device SubClass should be USB Common Sub Class 2
When IAD descriptor is used
bDeviceProtocol: 0x00
*!*ERROR: device Protocol should be USB IAD Protocol 1
When IAD descriptor is used
bMaxPacketSize0: 0x40 = (64) Bytes
idVendor: 0x04E8 = Samsung Electronics Co., Ltd.
idProduct: 0x6860
bcdDevice: 0x0C00
iManufacturer: 0x01
English (United States) "SAMSUNG"
iProduct: 0x02
English (United States) "SAMSUNG_Android"
iSerialNumber: 0x03
English (United States) "RF8M91Y8EZM"
bNumConfigurations: 0x01

---===>Open Pipes<===---

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
bmAttributes: 0x02 -> Bulk Transfer Type
wMaxPacketSize: 0x0200 = 0x200 max bytes
bInterval: 0x00

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x01 -> Direction: OUT - EndpointID: 1
bmAttributes: 0x02 -> Bulk Transfer Type
wMaxPacketSize: 0x0200 = 0x200 max bytes
bInterval: 0x00

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x82 -> Direction: IN - EndpointID: 2
bmAttributes: 0x03 -> Interrupt Transfer Type
wMaxPacketSize: 0x001C = 1 transactions per microframe, 0x1C max bytes
bInterval: 0x06

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x85 -> Direction: IN - EndpointID: 5
bmAttributes: 0x02 -> Bulk Transfer Type
wMaxPacketSize: 0x0200 = 0x200 max bytes
bInterval: 0x00

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x03 -> Direction: OUT - EndpointID: 3
bmAttributes: 0x02 -> Bulk Transfer Type
wMaxPacketSize: 0x0200 = 0x200 max bytes
bInterval: 0x00

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x84 -> Direction: IN - EndpointID: 4
bmAttributes: 0x03 -> Interrupt Transfer Type
wMaxPacketSize: 0x000A = 1 transactions per microframe, 0x0A max bytes
bInterval: 0x09

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x83 -> Direction: IN - EndpointID: 3
bmAttributes: 0x02 -> Bulk Transfer Type
wMaxPacketSize: 0x0200 = 0x200 max bytes
bInterval: 0x00

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x02 -> Direction: OUT - EndpointID: 2
bmAttributes: 0x02 -> Bulk Transfer Type
wMaxPacketSize: 0x0200 = 0x200 max bytes
bInterval: 0x00

---===>Full Configuration Descriptor<===---

===>Configuration Descriptor<===
bLength: 0x09
bDescriptorType: 0x02
wTotalLength: 0x0088 -> Validated
bNumInterfaces: 0x04
bConfigurationValue: 0x01
iConfiguration: 0x00
bmAttributes: 0x80 -> Bus Powered
MaxPower: 0xFA = 500 mA

===>Interface Descriptor<===
bLength: 0x09
bDescriptorType: 0x04
bInterfaceNumber: 0x00
bAlternateSetting: 0x00
bNumEndpoints: 0x03
bInterfaceClass: 0x06 -> This is an Image USB Device Interface Class
bInterfaceSubClass: 0x01
bInterfaceProtocol: 0x01
iInterface: 0x05
English (United States) "MTP"

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
bmAttributes: 0x02 -> Bulk Transfer Type
wMaxPacketSize: 0x0200 = 0x200 max bytes
bInterval: 0x00

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x01 -> Direction: OUT - EndpointID: 1
bmAttributes: 0x02 -> Bulk Transfer Type
wMaxPacketSize: 0x0200 = 0x200 max bytes
bInterval: 0x00

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x82 -> Direction: IN - EndpointID: 2
bmAttributes: 0x03 -> Interrupt Transfer Type
wMaxPacketSize: 0x001C = 1 transactions per microframe, 0x1C max bytes
bInterval: 0x06

===>IAD Descriptor<===
bLength: 0x08
bDescriptorType: 0x0B
bFirstInterface: 0x01
bInterfaceCount: 0x02
bFunctionClass: 0x02 -> This is Communications (CDC Control) USB Device Interface Class
bFunctionSubClass: 0x02
bFunctionProtocol: 0x01
iFunction: 0x08
English (United States) "CDC Serial"

===>Interface Descriptor<===
bLength: 0x09
bDescriptorType: 0x04
bInterfaceNumber: 0x01
bAlternateSetting: 0x00
bNumEndpoints: 0x01
bInterfaceClass: 0x02 -> This is Communications (CDC Control) USB Device Interface Class
bInterfaceSubClass: 0x02
bInterfaceProtocol: 0x01
iInterface: 0x06
English (United States) "CDC Abstract Control Model (ACM)"
-> This is a Communications (CDC Control) USB Device Interface Class

===>Descriptor Hex Dump<===
bLength: 0x05
bDescriptorType: 0x24
05 24 00 10 01
-> This is a Communications (CDC Control) USB Device Interface Class

===>Descriptor Hex Dump<===
bLength: 0x05
bDescriptorType: 0x24
05 24 01 00 02
-> This is a Communications (CDC Control) USB Device Interface Class

===>Descriptor Hex Dump<===
bLength: 0x04
bDescriptorType: 0x24
04 24 02 02
-> This is a Communications (CDC Control) USB Device Interface Class

===>Descriptor Hex Dump<===
bLength: 0x05
bDescriptorType: 0x24
05 24 06 01 02

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x84 -> Direction: IN - EndpointID: 4
bmAttributes: 0x03 -> Interrupt Transfer Type
wMaxPacketSize: 0x000A = 1 transactions per microframe, 0x0A max bytes
bInterval: 0x09

===>Interface Descriptor<===
bLength: 0x09
bDescriptorType: 0x04
bInterfaceNumber: 0x02
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0x0A -> This is a CDC Data USB Device Interface Class
bInterfaceSubClass: 0x00
bInterfaceProtocol: 0x00
iInterface: 0x07
English (United States) "CDC ACM Data"

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x83 -> Direction: IN - EndpointID: 3
bmAttributes: 0x02 -> Bulk Transfer Type
wMaxPacketSize: 0x0200 = 0x200 max bytes
bInterval: 0x00

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x02 -> Direction: OUT - EndpointID: 2
bmAttributes: 0x02 -> Bulk Transfer Type
wMaxPacketSize: 0x0200 = 0x200 max bytes
bInterval: 0x00

===>Interface Descriptor<===
bLength: 0x09
bDescriptorType: 0x04
bInterfaceNumber: 0x03
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0xFF -> Interface Class Unknown to USBView
bInterfaceSubClass: 0x40
bInterfaceProtocol: 0x02
iInterface: 0x00

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x85 -> Direction: IN - EndpointID: 5
bmAttributes: 0x02 -> Bulk Transfer Type
wMaxPacketSize: 0x0200 = 0x200 max bytes
bInterval: 0x00

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x03 -> Direction: OUT - EndpointID: 3
bmAttributes: 0x02 -> Bulk Transfer Type
wMaxPacketSize: 0x0200 = 0x200 max bytes
bInterval: 0x00
-> This is a Vendor Specific USB Device Interface Class

===>Descriptor Hex Dump<===
bLength: 0x08
bDescriptorType: 0x24
08 24 80 0C 00 01 00 01

===>BOS Descriptor<===
bLength: 0x05
bDescriptorType: 0x0F
wTotalLength: 0x0016
bNumDeviceCaps: 0x02

===>USB 2.0 Extension Descriptor<===
bLength: 0x07
bDescriptorType: 0x10
bDevCapabilityType: 0x02
bmAttributes: 0x00000006 -> Supports Link Power Management protocol

===>SuperSpeed USB Device Capability Descriptor<===
bLength: 0x0A
bDescriptorType: 0x10
bDevCapabilityType: 0x03
bmAttributes: 0x00
wSpeedsSupported: 0x0F
-> Supports low-speed operation
-> Supports full-speed operation
-> Supports high-speed operation
-> Supports SuperSpeed operation
bFunctionalitySupport: 0x01 -> lowest speed = full-speed
bU1DevExitLat: 0x01 -> less than 1 micro-seconds
wU2DevExitLat: 0x01F4 -> less than 500 micro-seconds

 

[Barty1884]

The Switch vs Phone are different concerns - the Switch is data transfer, the phone is power/charging....

The Switch has/ad a (or maybe multiple, including the dock?) that are software limited to 2.0 speeds. IIRC, it was something to do with speeds causing interference, but don't remember exactly how/why, so don't quote me on that.

In terms of testing the speed of the port - you'd need a device (external SSD, for example) and a cable capable of the higher transfer speeds to verify what it is actually operating at. The port itself, if functioning as designed, should be capable of 10Gbps, in perfect conditions.

 

[NoGagMaestro]

The Switch vs Phone are different concerns - the Switch is data transfer, the phone is power/charging....

The Switch has/ad a (or maybe multiple, including the dock?) that are software limited to 2.0 speeds. IIRC, it was something to do with speeds causing interference, but don't remember exactly how/why, so don't quote me on that.

In terms of testing the speed of the port - you'd need a device (external SSD, for example) and a cable capable of the higher transfer speeds to verify what it is actually operating at. The port itself, if functioning as designed, should be capable of 10Gbps, in perfect conditions.

So not all usb-c cables have the same type speed? This is the usb-c cable I use https://www.amazon.com/gp/product/B07DQM7WH5/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&th=1

I remember testing the port with a ssd when I first got the computer but don't remember the speeds. I'm guessing it's working fine and it is being limited by the phone charging and switch limitations.

 

[Barty1884]

So not all usb-c cables have the same type speed? This is the usb-c cable I use https://www.amazon.com/gp/product/B07DQM7WH5/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&th=1

I remember testing the port with a ssd when I first got the computer but don't remember the speeds. I'm guessing it's working fine and it is being limited by the phone charging and switch limitations.

Usb-c is tricky, as it's really just the name for the universal connector. The implementation can vary - especially with data transfer. You'll find a LOT of cables that are only 2.0 speeds, but plenty sufficient for a charger, for example.

I can't see the specific cable linked, I just get search results - but unless it specified supported speeds, there's a chance it is the limiting factor.

As mentioned, AFAIK ,(at least) one port on the switch or dock is software limited - try a.n.other port

 

[NoGagMaestro]

Usb-c is tricky, as it's really just the name for the universal connector. The implementation can vary - especially with data transfer. You'll find a LOT of cables that are only 2.0 speeds, but plenty sufficient for a charger, for example.

I can't see the specific cable linked, I just get search results - but unless it specified supported speeds, there's a chance it is the limiting factor.

As mentioned, AFAIK ,(at least) one port on the switch or dock is software limited - try a.n.other port

https://jsaux.com/products/100w-fast-charging-usb-c-to-usb-c-cable-cc0050There's only one usb-c port on the bottom of the switch to transfer data. I think it has something to do with the DBI program I use to transfer games as all users are complaining about getting only 2.0 speeds with that. As far as the cable not sure why the link is showing a search,