Pctel Port Devices Driver

16-04-2021 admin

Count on PCTEL for the help and resources you need to get the most from your equipment and keep your network running strong. General Support For inquiries related to topics such product availability, lead times, and shipping, reach out to your sales representative or our customer service teams. Windows device driver information for PCtel Serial Wave Device. The PCtel Serial Wave Device modem is an electronic device which converts a computer's digital signals to specific frequencies to be able to travel over television or cable lines. The destination modem demodulates the frequencies back into digital signal. Select Update Driver. If Windows doesn't find a new driver, you can try looking for one on the device manufacturer's website and follow their instructions. Reinstall the device driver. In the search box on the taskbar, enter device manager, then select Device Manager. Right-click (or press and hold) the name of the device, and select Uninstall. Install drivers using Device Manager If your driver was not detected or installed by Windows Update, you can try installing the driver manually if you have a compatible version. Windows 10 and previous versions of Windows such as Windows 7 share the same driver model, so it should work.

Pctel Port Devices Driver Vga
Pctel Port Devices Driver Device
Pctel Port Devices Drivers

-->

This section describes the class-of-device (CoD) registry subkeys and entries that apply to the Bluetooth driver stack.

'COD Major' and 'COD Type' Values

Original equipment manufacturer (OEMs) can use the COD Major and COD Type values to indicate the Class of Device for a Bluetooth-enabled Windows device. After the Bluetooth class installer sets the Class of Device based on these registry values, a remote device can determine whether it is connecting to a portable computer, a desktop computer, a phone, and so on.

The registry path to the COD Major and COD Type values is:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesBTHPORTParameters

Note that setting these values changes the Bluetooth Class of Device for the system, regardless of which Bluetooth radio may be attached. You can set the COD Major and COD Type to DWORD values as defined for the Class of Device field values in the Bluetooth SIG Assigned Numbers.

The Bluetooth profile driver, BthPort.sys, reads the COD Major and COD Type values to determine how it should respond to a device inquiry. These values affect only the COD_MAJOR_XXX and COD_XXX_MINOR_XXX bits of the Class of Device. The COD_SERVICE_XXX bits are not affected by this registry entry.

If the COD Major and COD Type values are not set or are set to invalid values, the Bluetooth class installer will set these values to COD_MAJOR_COMPUTER and COD_COMPUTER_MINOR_DESKTOP, respectively.

Scanning Parameterization Settings

Profile drivers can specify scanning parameters settings for their device(s) in their profile driver's INF file to tailor to the specific needs of a given device scenario.

You can override the default system scanning parameters by providing one or more of the following scanning parameters listed below into the AddReg directive. More information on how to use this directive can be found in INF AddReg Directive.

Value Name	Type	Min Value	Max Value
HighDutyCycleScanWindow	DWORD 0x10001	0x0004	0x4000. Shall be equal or smaller than the HighDutyCycleScanInterval parameter
HighDutyCycleScanInterval	DWORD 0x10001	0x0004	0x4000
LowDutyCycleScanWindow	DWORD 0x10001	0x0004	0x4000. Shall be smaller than the LowDutyCycleScanInterval parameter
LowDutyCycleScanInterval	DWORD 0x10001	0x0004	0x4000
LinkSupervisionTimeout	DWORD 0x10001	0x000A	0x0C80
ConnectionLatency	DWORD 0x10001	0x0000	0x01F4
ConnectionIntervalMin	DWORD 0x10001	0x0006	0x0C80. Shall be smaller or equal to ConnectionIntervalMax
ConnectionIntervalMax	DWORD 0x10001	0x0006	0x0C80

Note

Changes to scanning parameters make a global impact on the performance of the Bluetooth stack. Making changes to scanning parameters programmatically is not permitted. Using Low Duty Cycle scanning parameters that are too aggressive can not only have a negative impact to the available bandwidth for other Bluetooth Low Energy connections, but also for Bluetooth BR/EDR connections.

-->

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.
1. 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.
2. 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.
  1. Connect the DTMF shield to the assembled unit as shown in this image:
  2. 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.
1. Right-click the Start button in the task bar and select Device Manager.
2. 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

Connect to a port

Alternatively use the port name as printed on the board:

Pctel Port Devices Driver Vga

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.