¿ªÔÆÌåÓý
One thing I have seen is that windows will install a new physical com port with the same port number as a virtual port I have defined with vspMgr. My solution was to delete the virtual port with vspMgr and make a new one on a different port. You can also use
device manager to force the new com port to a different number.
Tony
AD0Vc
From: [email protected] <[email protected]> on behalf of mux_folder2001 via groups.io <canthony15@...>
Sent: Thursday, April 24, 2025 4:19 PM To: [email protected] <[email protected]> Subject: Re: [QRPLabs] #qmx SSB Firmware beta 1_01_004 release ?
Interesting. I am running the same OS build here with no USB related issues on my QMX+. I have been running two COM ports to the QMX+ for the past several hours without a hiccup.
Tony
AD0VC
From: [email protected] <[email protected]> on behalf of Tobias [DL3MHT] <dl3mht@...>
Sent: Thursday, April 24, 2025 2:46 PM To: [email protected] <[email protected]> Subject: Re: [QRPLabs] #qmx SSB Firmware beta 1_01_004 release ?
FYI - Complete USB failure on two different machines running Windows 11 Pro
?
One Ryzen 7 5800X machine with 32GB Ram
One 11th Gen Intel(R) Core(TM) i5-1135G7 with 16 GB Ram
?
Edition ? ?Windows 11 Pro
Version ? ?24H2 Installed on ? ??31/?12/?2024 OS build ? ?26100.3775 Experience ? ?Windows Feature Experience Pack 1000.26100.66.0 ?
In Device Manager:
Unknown USB Device (Device Descriptor Request Failed) ?
Device status:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.
?
Under Events:
?
Device configured (usb.inf):
Device USB\VID_0000&PID_0002\8&29c54ea8&0&1 was configured.
Driver Name: usb.inf
Driver Package ID: usb.inf_amd64_8a7970bf56a67043 Class GUID: {36fc9e60-c465-11cf-8056-444553540000} Driver Date: 06/21/2006 Driver Version: 10.0.26100.3624 Driver Provider: Microsoft Driver Section: BADDEVICE.Dev.NT Driver Rank: 0xFF0000 Matching Device ID: USB\DEVICE_DESCRIPTOR_FAILURE Outranked Drivers: usb.inf:USB\DEVICE_DESCRIPTOR_FAILURE:00FF2000 Device Updated: false Parent Device: USB\ROOT_HUB30\7&124f193f&0&0 ?
Device not started:
Device USB\VID_0000&PID_0002\8&29c54ea8&0&1 had a problem starting.
Driver Name: usb.inf
Class GUID: {36fc9e60-c465-11cf-8056-444553540000} Service:? Lower Filters:? Upper Filters:? Problem: 0x2B Problem Status: 0x0 ?
---
?
Functionality restored when going back to beta 1_01_003:
?
USB Composite Device:
?
Device configured (usb.inf):
Device USB\VID_0483&PID_A34C\8&29c54ea8&0&1 was configured.
Driver Name: usb.inf
Driver Package ID: usb.inf_amd64_8a7970bf56a67043 Class GUID: {36fc9e60-c465-11cf-8056-444553540000} Driver Date: 06/21/2006 Driver Version: 10.0.26100.3624 Driver Provider: Microsoft Driver Section: Composite.Dev.NT Driver Rank: 0xFF2006 Matching Device ID: USB\COMPOSITE Outranked Drivers:? Device Updated: false Parent Device: USB\ROOT_HUB30\7&124f193f&0&0 ?
Device started (usbccgp):
Device USB\VID_0483&PID_A34C\8&29c54ea8&0&1 was started.
Driver Name: usb.inf
Class GUID: {36fc9e60-c465-11cf-8056-444553540000} Service: usbccgp Lower Filters:? Upper Filters:? ---
?
If you need anything else Hans, let me know.73 Tobias
?
?
?
?
|
