The Pentair IntelliTouch Pool Control Driver For Control4 Control your Pentair IntelliTouch from anywhere with this new integration driver for Control4. The new IntelliTouch driver allows you to: Supports the latest Pentair pool systems. Check port on Linux and macOS¶ To check the device name for the serial port of your ESP32 board (or external converter dongle), run this command two times, first with the board / dongle unplugged, then with plugged in. The port which appears the second time is the one you need: Linux.
-->Summary
- Automated testing by using USB Type-C ConnEx
- USB Type-C interoperability test procedures in Windows 10: functional testing (FT) and stress testing (ST).
- Diagnostic procedures and tips to confirm scenarios, such as device addition and removal.
Applies to
- Windows 10
Specifications and procedures**
Note
Some information relates to pre-released product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
The MUTT Connection Exerciser Type-C (USB Type-C ConnEx) hardware board is a custom shield for the Arduino board. The shield provides a four-to-one switch to automate interoperability tests for USB Type-C scenarios.
This topic provides guidelines to automate the testing of systems, devices, docks with USB Type-C connectors and their interoperability with the Windows operating system. You can test hardware that belong to one of the following categories:
- System: Desktops, laptops, tablets, servers, or phones running a SKU of a version of the Windows operating system with an exposed USB Type-C port.
- Dock: Any USB Type-C device that exposes more than one port.
- Device: Any USB device with a Type-C port that can be attached to a system or dock. This category includes traditional USB devices as well as devices that support the accessory and alternate modes as defined in the USB Type-C specification.
Hardware requirements
To perform the USB Type-C interoperability test procedures by using USB Type-C ConnEx, you need:
System under test (SUT)
Desktops, laptops, tablets, servers, or phones with at least one exposed Type-C USB port.
Arduino Mega 2560 R3
Arduino Mega 2560 R3 is used as the microcontroller for the test setup.
Power adapter for the Arduino Mega 2560 R3 microcontroller.
USB Type-C ConnEx
The shield has one male USB Type-C port (labeled J1) to which the SUT is connected. The shield also has four other USB ports (labeled J2, J3, J4, J6) to which devices can be attached that act as peripherals to the SUT. The shield monitors amperage and voltage being drawn from the SUT. You can buy this board from MCCI or JJG Technologies.
USB A-to-B cable
You will use this cable to connect a PC to the microcontroller in order to update the firmware on the microcontroller to run tests.
Peripheral USB devices
Any USB device with a USB Type-C port that can be attached to the SUT. This category includes traditional USB devices and other devices that support the accessory and alternate modes as defined in the USB Type-C specification.
USB charger
USB Type-C that supports USB Type-C current requirements and optionally USB Power Delivery. You also need a USB Micro-B charger for J6.
Proxy controller
The USB Type-C ConnEx can be controlled by using a proxy for running the tests. The proxy controller can be one of these entities:
Secondary desktop PC or a laptop.
The proxy controller communicates with a mobile SUT, the microcontroller to load the firmware.
SUT by using a secondary USB port.
SUT by using a 3.5mm audio jack.
In this set up, you need:
DTMF shield to run tests on SUTs with a single USB Type-C port. DTMF provides the ability to control the shield from a single-port device with an audio jack after the initial flash of the firmware has been completed.
4-pin male-to-male audio cable used to connect the DTMF shield to the SUT. This allows the SUT to control the USB Type-C shield during testing.
Software requirements
Make sure you meet these requirements:
Your SUT must have the version of the Windows operating system with which you want to test interoperability.
The proxy controller must be running Windows 10.
and install the latest MUTT software package on the proxy controller.The package is a suite of tools used to run tests with USB Type-C ConnEx. It includes utilities to update the firmware, switch between the peripheral ports, and send requests to simulate test cases. It also contains test driver packages that test the functionality of the buses, its controller, and devices connected to the bus.
For UCSI based systems we strongly recommended testing with some additional settings to help discover UCSI firmware bugs. This setting will make UCSI firmware issues discoverable and is highly recommended for testing purposes only. Please see Debugging USCI firmware failures in this blog post.
Installation of the test tools requires an elevated command window.
To open an elevated command window, the user must be a member of the Administrators group on the proxy controller. To open an elevated Command Prompt window, create a desktop shortcut to Cmd.exe, select and hold (or right-click) the Cmd.exe shortcut, and select Run as administrator.
USB Type-C ConnEx tools
Here are the tools in MUTT software package that are specific to USB Type-C ConnEx
| Tool | Description |
|---|---|
| ConnExUtil.exe | Command line tool for exercising USB Type-C ConnEx features. |
| CxLoop.cmd | Connects and disconnects each port once. |
| CxStress.cmd | Randomized stress script. |
| CxPower.cmd | Captures power data (voltage and amperage) over a period of time and sends the output to a CSV file. |
For information about all other tools, see Tools in the MUTT software package.
Get started
Follow this procedure to set up your test environment.
The configuration should be similar to this image. Note that the USB Type-C port on the microcontroller provides control over USB Type-C ConnEx when connected to a PC.
In these steps, you will connect the hardware pieces, update the firmware on the microcontroller, and validate the installation. The DTMF shield provides control over USB Type-C ConnEx when connected to the audio port of a phone or tablet.
Connect the microcontroller to the USB Type-C shield.
If the USB Type-C ConnEx did not come assembled, then continue with step 1. If your USB Type-C ConnEx has been assembled, then proceed to step 2.
Caution
This step must be performed carefully because the pins bend easily.
Align the pins of the USB Type-C shield with the receptors on the microcontroller by making sure that the boards are level to each other.
Gently press the two boards together. Be careful not to bend the pins on the shield.
Your assembled unit should be similar to this image:
Power the USB Type-C ConnEx from the attached microcontroller by using either the USB Type-B (connected to the proxy controller) or from an external power adapter. The LCD display is similar to this image:
After five seconds, the LCD display shows the current and voltage.
If you do not the see display as shown in the previous image, make sure your have assembled the unit correctly.
Update the microcontroller with the USB Type-C ConnEx firmware.
Open an elevated Command Prompt window.
Navigate to the location of the MUTT software package, such as C:Program Files (x86)USBTest<arch>.
Run the following command:
MuttUtil.exe –UpdateTabFirmware
Plug in the SUT to the male USB Type-C port (labeled J1) on the shield.
Caution The J1 connector requires additional support when connecting the SUT. The connector is not sturdy enough to sustain the weight of a device or by itself.
Attach the peripherals to the USB ports labeled J2, J3, J4, J6.
Attach the proxy controller to the microcontroller.
- If the proxy controller is a desktop PC or laptop, establish connection over USB. Connect the USB Type-B port on the microcontroller to a USB port on the proxy controller, as shown in the preceding image.
- If the proxy controller is a mobile SUT, establish connection by using the audio port. For this connection, you need the DTMF shield.
Connect the DTMF shield to the assembled unit as shown in this image:
Connect the audio port of the shield to the audio port on the SUT by using a 4-pin male-to-male audio cable.
Your setup should be similar to this image:
Make sure USB Type-C ConnEx is recognized by Device Manager on the proxy controller.
Right-click the Start button in the task bar and select Device Manager.
Expand the Ports (COM & LPT) node and note the COM port that is used by the microcontroller. In this example, it is connected to COM 4.
ConnExUtil.exe
Here are the command line options that ConnExUtil.exe supports for controlling the USB Type-C ConnEx board.
| Use case | Option | Description |
|---|---|---|
| Device Discovery List all devices connected to USB Type-C ConnEx | /list | For USB connected devices, this option lists the device instance path. For audio connected devices it shows Audio. To view audio devices, use this in combination with the /all parameter. Lists with 1-based index that can be used for input to the /# parameter. |
| Device Selection Select all devices connected to USB Type-C ConnEx, including audio. | /all | Optional. Without this parameter, the utility addresses USB connected devices. Use this parameter only if an audio connected device is in use. Audio discovery is time consuming and disabled by default. |
| Device Selection Select a specific device connected to USB Type-C ConnEx ‘n’. | /#n | (Optional) Input n is a 1-based index of the available devices connected to USB Type-C ConnEx which can be viewed by using the /list parameter. Without this parameter, the default behavior is to run each command on all USB Type-C ConnEx boards. |
| Device Command | /setPortp | Switch to the specified port p. Connect a port either by specifying number (1 – 4) or by name (J2, J3, J4, J6). 0 disconnects all ports. |
| Device Command | /getPort | Read the currently connected port. |
| Device Command Read amperage/voltage information | /volts /amps /version | Read the current voltage. Read the current amperage. Read the device version. |
| Device Command Enable SuperSpeed | /SuperSpeedOn | Enables SuperSpeed globally for current and future connections until a /SuperSpeedOff command is sent. SuperSpeed is enabled by default. If SuperSpeed is disabled, and port 1 or 2 is connected, this command triggers a reconnect at SuperSpeed. |
| Device Command Disable SuperSpeed | /SuperSpeedOff | Disables SuperSpeed globally for current and future connections until a /SuperSpeedOn command is sent or the device is reset. If SuperSpeed is enabled and port 1 or 2 is connected, this command triggers a reconnect with SuperSpeed lines disabled. |
Set command delay | /setDelayt | Sets command delay t in seconds. Setting a command delay will cause the next /setPort or /SuperSpeed{On/Off} command to be delayed by t seconds where t ranges from 0 to 99. This is a one-time setting, only the next command is delayed. Sending multiple commands before the delay timer has expired is not supported. |
Set disconnect timeout in milliseconds | /setDisconnectTimeoutt | Set a disconnect timeout for the next non-zero /setPort command. On the next connect event, the port will only remain connected for t milliseconds before disconnecting. This is a one-time setting, only the next connect event will be automatically disconnected. Allowed range is from 0 – 9999 ms. |
Batch Command: Output power measurements to a .csv file. | /powercsv | Append the current power measurements and timestamp into power.csv The first run creates power.csv. On subsequent runs appends data to this file. Rename or delete the file to start fresh data capture. Each run appends a line with the following format: <index>,<time>,<volts>,<amps>. index is the device index given by /list, so multiple devices may be monitored simultaneously. time is the raw timestamp in seconds. volts and amps are recorded to two decimal places. This data may be captured over long periods of time and plotted in a spreadsheet application, see the cxpower.cmd script. |
Batch Command: Run unit test of major functionality | /test | Tests all the major functionality of the device. Use for basic validation of the functionality of the device. If this command fails, please power cycle the device and update the firmware. |
Batch Command: Basic demo of the port switching sequence. | /demo d | Loop through all ports one time, with d second delay on each port Writes the port number, volts and amps on each port into demoresult.txt. |
Sample Commands
Pentair Port Devices Drivers
Connect to a port
Alternatively use the port name as printed on the board:
Disconnect all ports
Loop through all ports
Scripts for controlling the USB Type-C ConnEx board
These scripts exercise the control interface supported by ConnExUtil.exe to run sequential and stress type tests with the USB Type-C ConnEx through the command line. All of these scripts support the optional command line parameter audio to indicate that the USB Type-C ConnEx board is connected over the 3.5 mm audio interface. By default they will only attempt to use USB connected boards.
Simple connect / disconnect sequence: CXLOOP.CMD
Connects and disconnects the SUT to and from each port (1-4) and pauses on each port prompting the tester to validate the connection on that port.
Random connect / disconnect loop: CXSTRESS.CMD
Connects and disconnects the SUT to and from each port at random for a random interval of 0.0-5.0 seconds in an infinite loop. When connecting to the USB Type-C ports it will randomly enable or disable SuperSpeed connection on that port, and will randomly instruct the board to disconnect quickly on that port at some random interval 0 – 999 ms.
The command line parameter C causes the script to only switch between the USB Type-C ports and the disconnected state. A numeric command line parameter resets the maximum random interval between switches from the default of 5.0 seconds to the input value in seconds. Parameters may be passed in any order.
Long running power measurement: CXPOWER.CMD
Saves the amperage and voltage reported by the USB Type-C ConnEx to output file power.csv at 2 second intervals. The data is formatted as comma-separated variables as follows:
index,time,volts,amps
index is the device index given by the ConnExUtil.exe /list command so multiple devices may be monitored simultaneously.
time is the raw timestamp in seconds.
volts and amps are recorded to 2 decimal places.
After capture is complete, this data may be post processed into charts showing power consumption over time, for example the power consumption for the duration of a battery charge cycle. A numeric command line parameter resets the default measurement interval of 2 seconds to the input value in seconds.
About test cases
The USB Type-C interoperability test procedures are divided into two sections: functional testing (FT) and stress testing (ST). Each test section describes the test case and identifies the category that applies to the test. The product must be tested against the entire applicable category. Certain test cases contain links to relevant hints and tips for additional information. This section is focused on USB Type-C functionality and experience. A USB Type-C solution may contains other USB components such as a USB hub or USB controller. Detailed testing of USB hubs and controllers is covered in both the USB-IF's xHCI interoperability test procedures and the Windows Hardware Certification Kit.
These test cases are based on the ConnExUtil commands and example scripts Scripts for controlling the USB Type-C ConnEx board. The test cases refer to the scripts. Customize the scripts as required for your test scenario.
Device Enumeration
Confirms that core aspects of device enumeration are functional.
Alternate Mode Negotiation
Confirms supported alternate modes.
Charging and power delivery (PD)
Confirms charging with USB Type-C.
Role Swap
Confirms role swap.
The stress testing section describes procedures for stress and edge case scenarios, which test device stability over a period of time. Stress testing does require a custom device (the SuperMUTT) for legacy USB validation (non USB Type-C). Additional testing and automation can be achieved with the upcoming USB Type-C test device.
Device Enumeration
Confirms that core aspects of device enumeration are functional.
Charging and power delivery (PD)
Confirms charging with USB Type-C.
FT Case 1: Device Enumeration
| Port | Device |
|---|---|
| J1 | SUT. |
| J2 | PC with USB Type-C port that is connected by using a USB Type-C cable. |
| J3 | USB Type-C charger. |
| J4 | USB Hub (SuperSpeed or high speed) with a mouse connected downstream. |
| J6 | PC with USB Type-A port cable connected by using a USB Type-A to USB Micro-B cable. |
- Power off the SUT.
- Connect the SUT to the port labeled as J1 on USB Type-C ConnEx.
- Connect the proxy controller to USB Type-C ConnEx.
- Connect peripherals to USB Type-C ConnEx.
- Power on the SUT and log on to Windows.
- At an elevated Command prompt, run the CXLOOP.CMD script. When script pauses, confirm the newly activated peripheral is operational.
- Reverse the orientation of USB Type-C cable and repeat step 5 - 7.
For configuration images related to step 2 -4, see Get started....
FT Case 2: Alternate Mode Negotiation
| Port | Device |
|---|---|
| J1 | SUT. |
| J2 | DisplayPort to USB Type-C dongle. |
| J3 | USB Type-C charger. |
| J4 | USB Hub (SuperSpeed or high speed) with a flash drive connected downstream. |
| J6 | PC with USB Type-A port cable connected by using a USB Type-A to USB Micro-B cable. |
- Power off the SUT.
- Connect the SUT to the port labeled as J1 on USB Type-C ConnEx.
- Connect the proxy controller to USB Type-C ConnEx.
- Connect peripherals to USB Type-C ConnEx.
- Power on the SUT and log on to Windows.
- At an elevated Command prompt, run the CXLOOP.CMD script. When script pauses, confirm the newly activated peripheral is operational.
- Reverse the orientation of USB Type-C cable and repeat step 5 - 7.
For configuration images related to step 2 -4, see Get started....
FT Case 3: Charging and power delivery (PD)
| Port | Device |
|---|---|
| J1 | SUT. |
| J2 | None. |
| J3 | USB Type-C charger. |
| J4 | USB mouse. |
| J6 | USB Micro-B charger. |
Power off the SUT.
Connect the SUT to the port labeled as J1 on USB Type-C ConnEx.
Connect the proxy controller to USB Type-C ConnEx.
Connect peripherals to USB Type-C ConnEx.
Power on the SUT and log on to Windows.
At an elevated Command prompt, run the CXLOOP.CMD script. When script pauses, confirm the newly activated peripheral is operational.
Reverse the orientation of USB Type-C cable and repeat step 5 - 7.
Connect USB Type-C ConnEx to port J2.
ConnExUtil.exe /setPort 2
If SUT contains more than one USB Type-C port, connect two USB Type-C ports on the same system with a USB Type-C cable.
Confirm that the SUT is not charging (itself).
Confirm that the LCD reading of power matches the expectations of the wall adapter.
Replace the USB Type-C charger connected to J3 with another USB Type-C charger from a different manufacturer.
Confirm the device is receiving current.
For configuration images related to step 2 -4, see Get started....
FT Case 4: Role Swap
| Port | Device |
|---|---|
| J1 | SUT. |
| J2 | PC with USB Type-C port that is connected by using a USB Type-C cable. |
| J3 | None. |
| J4 | USB flash drive. |
| J6 | PC with USB Type-A port cable connected by using a USB Type-A to USB Micro-B cable. |
Power off the SUT.
Connect the SUT to the port labeled as J1 on USB Type-C ConnEx.
Connect the proxy controller to USB Type-C ConnEx.
Connect peripherals to USB Type-C ConnEx.
Power on the SUT and log on to Windows.
At an elevated Command prompt, run the CXLOOP.CMD script. When script pauses, confirm the newly activated peripheral is operational.
Reverse the orientation of USB Type-C cable and repeat step 5 - 7.
Connect USB Type-C ConnEx to port J2.
Confirm role swap. The Amperage shown on the LCD screen indicates power roles. +ve if J1 is the power sink; -ve if J1 is the power source.
Perform necessary steps to swap data roles and confirm current roles of each system have changed.
For configuration images related to step 2 -4, see Get started....
ST Case 1: Device Enumeration
| Port | Device |
|---|---|
| J1 | SUT. |
| J2 | PC with USB Type-C port that is connected by using a USB Type-C cable. |
| J3 | USB Type-C charger. |
| J4 | USB Hub (SuperSpeed or high speed) with a mouse connected downstream. |
| J6 | PC with USB Type-A port cable connected by using a USB Type-A to USB Micro-B cable. |
Power off the SUT.
Connect the SUT to the port labeled as J1 on USB Type-C ConnEx.
Connect the proxy controller to USB Type-C ConnEx.
Connect peripherals to USB Type-C ConnEx.
Power on the SUT and log on to Windows.
At an elevated Command prompt, run the CXSTRESS.CMD for 12 hours.
Terminate the script by pressing Ctrl-C.
Perform the steps described in FT Case 1: Device Enumeration.
Pentair Port Devices Driver
For configuration images related to step 2 -4, see Get started....
ST Case 2: Charging and power delivery (PD)
| Port | Device |
|---|---|
| J1 | SUT. |
| J2 | None. |
| J3 | USB Type-C charger. |
| J4 | USB mouse. |
| J6 | USB Micro-B charger. |
Power off the SUT.
Connect the SUT to the port labeled as J1 on USB Type-C ConnEx.
Connect the proxy controller to USB Type-C ConnEx.
Connect peripherals to USB Type-C ConnEx.
Power on the SUT and log on to Windows.
At an elevated Command prompt, run the CXSTRESS.CMD for 12 hours. .
Terminate the script by pressing Ctrl-C.
Perform the steps described in FT Case 3: Charging and power delivery (PD).
For configuration images related to step 2 -4, see Get started....
Additional test resources
The following functional tests can be adapted for USB Type-C to improve traditional USB scenarios.
| Test case | Description | Category |
|---|---|---|
| System Boot | Confirms that the product does not inhibit normal system boot. | System, Dock, Device |
| System Power Transitions | Tests whether the system's power transitions and wake-up capability from lower power states are not affected by the product. | System, Dock, Device |
| Selective Suspend | Confirms the selective suspend transitions. | Dock, Device |
The following stress tests can be adapted from the SuperMUTT test documentation to expand USB scenarios.
| Test case | Description | Category |
|---|---|---|
| System Power Transitions | Tests product reliability after repetitive system power events. | System, Dock, Device |
| Transfer Events | Generates multiple transfer and connection events. | System, Dock, Device |
| Plug and Play (PnP) | Generates various PnP sequences. | System, Dock, Device |
| Device Topology | Tests a range of devices and topologies with the product. | System, Dock, Device |
Validating success or failure of the tests
Confirming charging and power
The onboard LCD on the USB Type-C ConnEx displays power (volts, amps, and direction). Confirm that it matches expectations from power sources plugged in and actively enabled with the USB Type-C ConnEx .
Confirming device addition on desktops
- Identify the USB host controller to which your device is connected.
- Make sure that the new device appears under the correct node in Device Manager.
- For USB 3.0 hubs connected to a USB 3.0 port, expect to see two hub devices: one enumerated at SuperSpeed and another at high speed.
Confirm device removal on desktops
- Identify your device in Device Manager.
- Perform the test step to remove the device from the system.
- Confirm that the device is no longer present in Device Manager.
- For a USB 3.0 hub, check that both devices (SuperSpeed and companion hubs) are removed. Failure to remove a device in this case may be a device failure and should be investigated by all components involved to triage the appropriate root cause.
Confirm device functionality
- If the device is a USB hub, make sure that the devices that are downstream of the hub are functional. Verify that other devices can be connected to available ports on the hub.
- If the device is an HID device, test its functionality. Make sure that a USB keyboard types, a USB mouse moves the cursor, and a gaming device is functional in the game controller's control panel.
- A USB audio device must play and/or record sound.
- A storage device must be accessible and should be able to copy a file 200MB or more in size.
- If the device has multiple functions, such as scan & print, make sure to test both the scan and print functionality.
- If the device is a USB Type-C device, confirm that the applicable USB and alternate modes are functional.
Using ETW to log issues
See How to capture a USB event trace with Logman
Reporting test results
Provide these details:
- The list of tests (in order) that were performed before the failed test.
- The list must specify the tests that have failed or passed.
- Systems, devices, docks, or hubs that were used for the tests. Include make, model, and Web site so that we can get additional information, if needed.
The USB-A and USB-B connection types are what most users are accustomed to. However, these days, there are more things you can achieve with the new USB-C type of connection. With this option, users can charge their computer. What’s more, they can also connect their PC to other USB-C type devices, including media players, smartphones, docking stations, and display adapters, among others.
However, we are aware that a good percentage of users are having troubles with their USB-C connection. In most cases, the problems are caused by problems with the hardware or software. Don’t worry because you can easily fix USB-C issues in a Windows 10 computer. After all. You will get notifications which you can use to determine how to resolve the problem.
What is a USB-C connector?
Developed by the USB Implementers Forum, the USB-C connection type is a tool for transmitting both power and data. It is worth noting that this was designed, certified, and released as an industry-standard connector by the members of the organization. Over 700 companies are part of the USB Implementers Forum, including Apple, Microsoft, Dell, HP, Intel, and Samsung. This is also the reason why many computer manufacturers readily accepted USB-C technology.
Is it similar to a micro USB connector?
At first glance, the USB-C connector looks a lot like a micro USB connector. However, the former has a distinct oval shape. Moreover, it is a little bit thicker to accommodate its best feature—like MagSafe and Lightning, the USB-C connector does not have an up or down orientation. You simply have to line the connector correctly, and you wouldn’t have to worry about flipping it to plug it in properly. Another key thing to remember is that the cables have the same connectors on both ends. This means that you would not have a hard time figuring out which end goes where.
Comparing USB-C and USB 3.1
The USB-C connection type’s default protocol is USB 3.1. Theoretically, at 10Gbps, USB 3.1 is twice as fast as USB 3.0. However, the ports for USB 3.1 can still be found in their original, larger shape. Such ports are referred to as ‘USB 3.1 Type-A. Generally, it has become more common to see USB 3.1 ports with USB-C connectors.
How to fix USB-C issues in a Windows 10 computer
Some of the notifications you might encounter when the USB-C connection is not working include the following:
- You might be able to fix your USB device
- Slow USB charger connection
- Display connection might be limited
- PC isn’t charging
- The USB device might not work
- These two devices can’t communicate
- The USB device might not be working properly
- Use a different USB port
- The USB or Thunderbolt device functionality might be limited
Every notification has its solution. Whether you need to fix USB-C compatibility or update your drivers, there’s always something you can do to resolve the issue.
What to do when you see the ‘You might be able to fix your USB device’ error notification
If you see this notification while trying to use a USB-C connection type, there must be something wrong with the device or the drivers on your computer. You can run the troubleshooter for hardware and devices, or you can update your drivers to resolve the problem.
The app contains no malware and is designed specifically for the problem described in this article. Just download and run it on your PC. free download
Developed by Auslogics
Auslogics is a certified Microsoft® Silver Application Developer. Microsoft confirms Auslogics' high expertise in developing quality software that meets the growing demands of PC users.
Running the Hardware and Devices troubleshooter
- On your keyboard, press Windows Key+S.
- Type “control panel” (no quotes), then hit Enter.
- Once Control Panel is up, go to the top-right corner of the window and click the View By option.
- Select Large Icons from the options.
- Click Troubleshooting.
- Go to the left-pane menu, then click View All.
- Select Hardware and Devices.
- Click Next, then follow the on-screen instructions.
The tool will start to identify issues with your hardware and devices, attempting to repair them.
Using Windows Update to fix the device drivers
- Right-click the Windows icon on your taskbar.
- Select Settings from the list.
- Click Updates & Security.
- Go to the left-pane menu and select Windows Update.
- Go to the right pane, then click Check for Updates.
- Install all the available updates.
Updating your device drivers
It is possible that the device drivers in your computer are corrupted, damaged, or outdated. You can update them to give your unit a fresh set of drivers. There are two ways you can do this—going to the manufacturer’s website or automating the update process, using Auslogics Driver Updater.
It is worth noting that manually updating your drivers can be time-consuming and risky. As we’ve mentioned, you have to search for the compatible drivers on the manufacturer’s website. If you download and install the wrong drivers, you might cause more problems to your computer.
Resolve PC Issues with Driver Updater
Unstable PC performance is often caused by outdated or corrupt drivers. Auslogics Driver Updater diagnoses driver issues and lets you update old drivers all at once or one at a time to get your PC running smoother
On the other hand, when you automate the process with the help of Auslogics Driver Updater, you are avoiding possible PC damage. The best part is, the tool will take care of all problematic drivers—not just the one which caused the USB-C connection type problem. So, you will notice a significant improvement in your PC’s performance and speed.
Finding the error codes for device issues
It is important to know the error code to address problems with your device appropriately. To acquire the error code, simply follow the steps below:
- Right-click the Windows icon on your taskbar.
- Select Device Manager from the list.
- Right-click the problematic device, then select Properties.
- Go to the Device Status dialog box to see the error code.
How to fix slow USB charger connected
When the ‘slow USB charger connected’ notification shows up, there are various possible reasons behind it. Here are some of them:
- You’re using a charger that is not compatible with your device or computer.
- Your charger’s power is insufficient for your device or computer. It is worth noting that devices with USB-C connectors have larger power limits. So, charging should be faster with greater levels of power, as long as the device supports USB power delivery.
- You have not properly connected the charger to the port on your device or computer.
- The cable’s power capacity is not sufficient for the charger itself, the device, or the computer.
- Your USB port is dusty or dirty, preventing proper insertion of the charger.
- You’ve connected the charger to your device or computer through an external dock or hub.
You can fix this problem by using the charger and cable that came with your device. These peripherals are designed according to industry standards. So, they have the right power capacity to speed up charging. On the other hand, you can also check if your charger is properly connected to the USB-C port on your device or computer. If the port is dusty or dirty, you can use compressed air to clean it.
Note: Systems with available USB-C connectors have higher power limits, and they can support up to 5V, 3A, or 15W.
Resolving the ‘Display connection might be limited’ error notification
There are many reasons why you see this error notification. It is possible that the dongle has new features that the cable, device, or PC do not support. You should also check if you’ve connected the dongle to the correct port or through an external dock or hub. On the other hand, it is possible that the other devices with the USB-C connection are interfering with the dongle.
You should know that a USB-C connector has Alternate Modes which you can use for non-USB connectors. These modes are HDMI, DisplayPort, and MHL. So, you can resolve the ‘Display connection might be limited’ error notification by checking if your PC, cable, and external display support the aforementioned alternate modes. You can also try to check if the dongle or device is directly connected to your computer. If it is yet the problem persists, try using a different cable.
Getting rid of the ‘PC isn’t charging’ error notification
This error notification is possibly caused by the following:
- You’ve used an incompatible charger.
- You’ve used a charger with lower power limits, preventing it from properly charging your device or computer.
- You’ve incorrectly connected the charger to the port on your PC.
- The cable’s power capacity cannot accommodate the charger.
- The USB ports are dusty or dirty, preventing proper insertion of the charger.
- You’ve connected the charger through an external hub or dock.
You can fix USB-C compatibility issues by using the charger and cable that came with your device’s or computer’s packaging. You can also use compressed air to clean the ports, enabling you to insert the dongle correctly.
Resolving ‘The USB device might not work’ error
This error notification shows up when the Windows version on your PC does not support the driver for the device you’re trying to connect to the USB-C port. So, the solution to this is to install all the latest updates for your operating system. You can do this by following the instructions below:
- Click the Search icon on your taskbar.
- Type “settings” (no quotes), then hit Enter.
- Select Update & Security.
- Click Check for Updates.
- Install the available updates.
How to fix ‘These two devices can’t communicate’ error
You will see this error notification will show up when you are having trouble connecting two devices via USB-C. It is possible that one or both of the devices do not support the USB-C connection type. The workaround here is ensuring that you are connecting two Windows computers.
Resolving the error ‘USB device might not be working properly’
If your computer does not support the device you’re trying to connect via USB-C, you will see this error message. It is also possible that the power on your laptop is limited because you’re sourcing it from your battery. In this case, you can try using a different computer, or you can try plugging your device into an external power source.
What to do when you get a ‘Use a different USB port’ prompt
When you get this error notification, it is likely that the USB port does not support Thunderbolt, DisplayPort, or MHL. If this is the case, then you can try using a different port on your PC. It is also possible that the functionality of the USB device had become limited when you connected it to a particular port. You can try plugging it to a different port on your computer to resolve the problem.
Resolving the error ‘USB or Thunderbolt device functionality might be limited’
The reasons behind this error notification are similar to what caused the limited display connection issues. So, you can resolve this by making sure that your PC and cable support the same USB-C features as the device you’re trying to connect. You also have to make sure that the dongle is directly connected to your computer.
Which connection type do you prefer?
Let us know in the comments below!