|
Hi all
I updated the?SSB?beta?testing webpage of the brave, here:??and released?firmware?version?1_01_006 to it.?
As discussed in the other?thread... I believe I fixed the problem with USB not working on Windows machines; I tested it on my PC with its out-of-date Win10 which I have not logged into for several YEARS. It worked on USB Serial Ports = 1 and USB Serial Ports = 2 (also with USB sound card appearing) but not on USB Serial Ports = 3. When I boot my PC into Linux as normal, all three options work perfectly. See attached.?
Feedback awaited... and again my apologies for the error in 1_01_005. Just a single character typo which apparently Linux didn't mind but Windows did? ?:-/? ?
|
Hello Hans,
?
thanks for so quick response. It's much better but not 100%.
?
Config 1 port:
The device manager looks fine, 1 COM and 1 Audio
PuTTY starts now - ok!
ENTER into Putty brings no reaction - maybe a different storry.
no CAT control
Audio is ok (Audacity)
?
Config 2 ports:
Device manager shows 1 COM and 1 Audio and 1 Other device - QMX Transceiver (not working, no driver)
Installed STMicroelectronics driver --> 2. COM-Port is shown
PuTTY starts for the first COM-port - ENTER without reaction
PuTTY starts for the second COM-port - ENTER without reaction
Audio is ok (Audacity)
?
no entry to Menu of the QMX - Config locked by terminal
QMX off and on
Config 3 ports:
Device manager shows 2 COM-ports and 1 Audio and 1 USB Mass storage (Couldn't start)
no further tests yet
?
73 Ludwig
?
|
One more information:
?
Config with 1 Port
Starting PuTTY
CAT command FA; brings F as reaction and nothing more
no reaction after typing more commands
?
Could it be something like a hand shake failure?
?
73 Ludwig
|
Windows:
Edition ? ?Windows 11 Pro
Version ? ?24H2
Installed on ? ??11/?18/?2024
OS build ? ?26100.3775
Experience ? ?Windows Feature Experience Pack 1000.26100.66.0
?
Installed QMX firmware 1_01_006.
?
Set serial ports = 1:
One serial port show up in Device manager, and it works. Audio device works, WST-X is able to TX and RX normally.
?
Set serial ports = 2:
Two serial ports show up in Device Manager, but they BOTH are assigned to the SAME COM port (COM5) - See Picture.
PUTTY or WSJT-X can connect to the QMX+, but they cannot both connect.
Looking at the USB device Details:
| Driver Detail Category |
First Port |
Second Port |
| Device Deescription |
USB Serial Device |
USB Serial Device |
| Device Instance Path |
USB\VID_0483&PID_A34C&MI_05\6&E2FE1CA&0&0005 |
USB\VID_0483&PID_A34C&MI_00\6&E2FE1CA&0&0000 |
| Hardware IDs |
USB\VID_0483&PID_A34C&REV_0100&MI_05
USB\VID_0483&PID_A34C&MI_05 |
USB\VID_0483&PID_A34C&REV_0100&MI_00
USB\VID_0483&PID_A34C&MI_00 |
| Compatible IDs |
USB\COMPAT_VID_0483&Class_02&SubClass_02&Prot_01
USB\COMPAT_VID_0483&Class_02&SubClass_02
USB\COMPAT_VID_0483&Class_02
USB\Class_02&SubClass_02&Prot_01
USB\Class_02&SubClass_02
USB\Class_02 |
USB\COMPAT_VID_0483&Class_02&SubClass_02&Prot_01
USB\COMPAT_VID_0483&Class_02&SubClass_02
USB\COMPAT_VID_0483&Class_02
USB\Class_02&SubClass_02&Prot_01
USB\Class_02&SubClass_02
USB\Class_02 |
| Capabilities |
00000080
CM_DEVCAP_SURPRISEREMOVALOK |
00000080
CM_DEVCAP_SURPRISEREMOVALOK |
| Status |
0180200A
DN_DRIVER_LOADED
DN_STARTED
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER |
0180200A
DN_DRIVER_LOADED
DN_STARTED
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER |
| Problem Code |
00000000 |
00000000 |
| Config Flags |
00000000 |
00000000 |
| Matching Device ID |
usb\class_02&subclass_02&prot_01 |
usb\class_02&subclass_02&prot_01 |
| Address |
00000007 |
00000002 |
| Rank of driver |
00FF2003 |
00FF2003 |
| Service |
usbser |
usbser |
| Bus reported device description |
QMX Transceiver |
QMX Transceiver |
| Display Name |
USB Serial Device (COM5) |
USB Serial Device (COM5) |
?
There are a lot more, but mostly GUIDs and system stuff that are the same between both ports. Let me know if you need any others, this seems to be the pertinent ones.
?
Tried changing one of the instances to COM6 and then opening them. the one on COM5 still opened properly, the one on COM6 gave this error:
?
?
Set serial ports = 3:
No USB devices show up. Not serial ports nor audio device.
?
I am willing to do whatever testing might help you Hans - even let you remote onto this computer if you think that will help.
?
Erik - AD7OV
?
|
Just a quick test, it's 1am ;)
?
1 port configuration looks ok in Device Manager, Audio Devices and 1 COM Port
2 port configuration looks ok in Device Manager, Audio Devices and 2 COM Ports
?
3 port configuration:
?
Device Status of USB composite device:
?
This device cannot start. (Code 10)
{Operation Failed}
The requested operation was unsuccessful.
?
Problem code:
0000000A
?
Problem status:
{Operation Failed}
The requested operation was unsuccessful.
C0000001
?
Status:
01806400
DN_HAS_PROBLEM
DN_DISABLEABLE
DN_REMOVABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER
In 3 port configuration the Device Manager Tree also seems to refresh in regular intervals.
?
|
Windows will do this sometimes. You have to force the second com port to another port. In device manager right click on the port you want to change. Select "properties", then "port settings", and then the "advanced" button. Here you will find a drop down to
change the com port. You may see some ports that show as "in use" but you know that you are not using them. In that case it is OK to choose them anyway. Whenever windows sees a new com port it reserves the port for all future time as "in use" so that, if you
ever install that hardware again, it can get the same port. If you are not sure then choose a port that is not marked "in use". Finally, click OK.?
Tony
AD0VC
toggle quoted message
Show quoted text
Windows:
Edition ? ?Windows 11 Pro
Version ? ?24H2
Installed on ? ??11/?18/?2024
OS build ? ?26100.3775
Experience ? ?Windows Feature Experience Pack 1000.26100.66.0
?
Installed QMX firmware 1_01_006.
?
Set serial ports = 1:
One serial port show up in Device manager, and it works. Audio device works, WST-X is able to TX and RX normally.
?
Set serial ports = 2:
Two serial ports show up in Device Manager, but they BOTH are assigned to the SAME COM port (COM5) - See Picture.
PUTTY or WSJT-X can connect to the QMX+, but they cannot both connect.
Looking at the USB device Details:
|
Driver Detail Category
|
First Port
|
Second Port
|
|
Device Deescription
|
USB Serial Device
|
USB Serial Device
|
|
Device Instance Path
|
USB\VID_0483&PID_A34C&MI_05\6&E2FE1CA&0&0005
|
USB\VID_0483&PID_A34C&MI_00\6&E2FE1CA&0&0000
|
|
Hardware IDs
|
USB\VID_0483&PID_A34C&REV_0100&MI_05
USB\VID_0483&PID_A34C&MI_05
|
USB\VID_0483&PID_A34C&REV_0100&MI_00
USB\VID_0483&PID_A34C&MI_00
|
|
Compatible IDs
|
USB\COMPAT_VID_0483&Class_02&SubClass_02&Prot_01
USB\COMPAT_VID_0483&Class_02&SubClass_02
USB\COMPAT_VID_0483&Class_02
USB\Class_02&SubClass_02&Prot_01
USB\Class_02&SubClass_02
USB\Class_02
|
USB\COMPAT_VID_0483&Class_02&SubClass_02&Prot_01
USB\COMPAT_VID_0483&Class_02&SubClass_02
USB\COMPAT_VID_0483&Class_02
USB\Class_02&SubClass_02&Prot_01
USB\Class_02&SubClass_02
USB\Class_02
|
|
Capabilities
|
00000080
CM_DEVCAP_SURPRISEREMOVALOK
|
00000080
CM_DEVCAP_SURPRISEREMOVALOK
|
|
Status
|
0180200A
DN_DRIVER_LOADED
DN_STARTED
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER
|
0180200A
DN_DRIVER_LOADED
DN_STARTED
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER
|
|
Problem Code
|
00000000
|
00000000
|
|
Config Flags
|
00000000
|
00000000
|
|
Matching Device ID
|
usb\class_02&subclass_02&prot_01
|
usb\class_02&subclass_02&prot_01
|
|
Address
|
00000007
|
00000002
|
|
Rank of driver
|
00FF2003
|
00FF2003
|
|
Service
|
usbser
|
usbser
|
|
Bus reported device description
|
QMX Transceiver
|
QMX Transceiver
|
|
Display Name
|
USB Serial Device (COM5)
|
USB Serial Device (COM5)
|
?
There are a lot more, but mostly GUIDs and system stuff that are the same between both ports. Let me know if you need any others, this seems to be the pertinent ones.
?
Tried changing one of the instances to COM6 and then opening them. the one on COM5 still opened properly, the one on COM6 gave this error:
?
?
Set serial ports = 3:
No USB devices show up. Not serial ports nor audio device.
?
I am willing to do whatever testing might help you Hans - even let you remote onto this computer if you think that will help.
?
Erik - AD7OV
?
|
If the device GUID is the same, isn't Windows likely to report it as the 'same' device (and possibly merge it)? ;-)
I'm not at all familiar with the protocols at play here, so I'm talking out of turn, but it might be reasonable to ensure that different (logical) devices have non-matching GUID's, just as a matter of course?
I'm willing to be schooled, however! ?
Paul -- AI7JR
toggle quoted message
Show quoted text
Windows will do this sometimes. You have to force the second com port to another port. In device manager right click on the port you want to change. Select "properties", then "port settings", and then the "advanced" button. Here you will find a drop down to
change the com port. You may see some ports that show as "in use" but you know that you are not using them. In that case it is OK to choose them anyway. Whenever windows sees a new com port it reserves the port for all future time as "in use" so that, if you
ever install that hardware again, it can get the same port. If you are not sure then choose a port that is not marked "in use". Finally, click OK.?
Tony
AD0VC
Windows:
Edition ? ?Windows 11 Pro
Version ? ?24H2
Installed on ? ??11/?18/?2024
OS build ? ?26100.3775
Experience ? ?Windows Feature Experience Pack 1000.26100.66.0
?
Installed QMX firmware 1_01_006.
?
Set serial ports = 1:
One serial port show up in Device manager, and it works. Audio device works, WST-X is able to TX and RX normally.
?
Set serial ports = 2:
Two serial ports show up in Device Manager, but they BOTH are assigned to the SAME COM port (COM5) - See Picture.
PUTTY or WSJT-X can connect to the QMX+, but they cannot both connect.
Looking at the USB device Details:
|
Driver Detail Category
|
First Port
|
Second Port
|
|
Device Deescription
|
USB Serial Device
|
USB Serial Device
|
|
Device Instance Path
|
USB\VID_0483&PID_A34C&MI_05\6&E2FE1CA&0&0005
|
USB\VID_0483&PID_A34C&MI_00\6&E2FE1CA&0&0000
|
|
Hardware IDs
|
USB\VID_0483&PID_A34C&REV_0100&MI_05
USB\VID_0483&PID_A34C&MI_05
|
USB\VID_0483&PID_A34C&REV_0100&MI_00
USB\VID_0483&PID_A34C&MI_00
|
|
Compatible IDs
|
USB\COMPAT_VID_0483&Class_02&SubClass_02&Prot_01
USB\COMPAT_VID_0483&Class_02&SubClass_02
USB\COMPAT_VID_0483&Class_02
USB\Class_02&SubClass_02&Prot_01
USB\Class_02&SubClass_02
USB\Class_02
|
USB\COMPAT_VID_0483&Class_02&SubClass_02&Prot_01
USB\COMPAT_VID_0483&Class_02&SubClass_02
USB\COMPAT_VID_0483&Class_02
USB\Class_02&SubClass_02&Prot_01
USB\Class_02&SubClass_02
USB\Class_02
|
|
Capabilities
|
00000080
CM_DEVCAP_SURPRISEREMOVALOK
|
00000080
CM_DEVCAP_SURPRISEREMOVALOK
|
|
Status
|
0180200A
DN_DRIVER_LOADED
DN_STARTED
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER
|
0180200A
DN_DRIVER_LOADED
DN_STARTED
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER
|
|
Problem Code
|
00000000
|
00000000
|
|
Config Flags
|
00000000
|
00000000
|
|
Matching Device ID
|
usb\class_02&subclass_02&prot_01
|
usb\class_02&subclass_02&prot_01
|
|
Address
|
00000007
|
00000002
|
|
Rank of driver
|
00FF2003
|
00FF2003
|
|
Service
|
usbser
|
usbser
|
|
Bus reported device description
|
QMX Transceiver
|
QMX Transceiver
|
|
Display Name
|
USB Serial Device (COM5)
|
USB Serial Device (COM5)
|
?
There are a lot more, but mostly GUIDs and system stuff that are the same between both ports. Let me know if you need any others, this seems to be the pertinent ones.
?
Tried changing one of the instances to COM6 and then opening them. the one on COM5 still opened properly, the one on COM6 gave this error:
?
?
Set serial ports = 3:
No USB devices show up. Not serial ports nor audio device.
?
I am willing to do whatever testing might help you Hans - even let you remote onto this computer if you think that will help.
?
Erik - AD7OV
?
|
Tony, See my description, I did change a port as you suggested, and the "changed" port would not work.
?
Erik - AD7OV
|
I am on an up to date Windows 10 machine.
Three COM ports worked in 004.
Skipped 005
1 COM port worked on 006
Changed menu to 3 COM ports, now I have no COM ports.
Set to 2 COM ports and I have 2.
Made changes both from Putty and the front panel. Same results.
Had power QMX down each time in order for Windows to detect the change.
1 works
2 works
3 = 0
--
Randy, N4OPI
|
Sorry Erik, I didn't read it carefully. If you did not already, try changing the port and rebooting, both the PC and the QMX.
Tony
AD0VC?
toggle quoted message
Show quoted text
Tony, See my description, I did change a port as you suggested, and the "changed" port would not work.
?
Erik - AD7OV
|
Same result as before. That is why I dumped values for Hans, so he can see what Win 11 is recognizing it as. There must be some difference between Win 10 and Win 11 - his test system is Win 10.
?
Erik - AD7OV
|
No offense to Tony, but I would advise against re-assigning "In Use" port numbers.
I've gotten my Windows machine into a world of USB pain doing that. Unless you know with absolute certainty that the device that owned that port number (if you even know what device it was) will never ever be plugged in again.
I had to go into device manager, View, Show Hidden Devices and then delete all grayed out COM ports under Ports (COM & LPT) and all greyed out entries under Universal Serial Bus Controllers.?
--
Randy, N4OPI
|
FW006 Win 11 WSJTX/FLrig working for over an hour now using 2 com ports! (Putty cat mon). No joy on 3 com ports! setting!
|
Hi,
?
the Problem with the USB Serial Ports = 3 persists on Windows 11.
While using am using WSL (Ubuntu Linux) and forwarding the USB ports to the WSL i got some more debugging output, that might help to track the issue further down:
Relevant dmesg output attaching the QMX with USB Serial Ports = 3:?
[ ?113.234442] vhci_hcd vhci_hcd.0: pdev(0) rhport(0) sockfd(3)
[ ?113.234452] vhci_hcd vhci_hcd.0: devid(524289) speed(2) speed_str(full-speed)
[ ?113.234542] vhci_hcd vhci_hcd.0: Device attached
[ ?113.517512] vhci_hcd: vhci_device speed not set
[ ?113.587627] usb 1-1: new full-speed USB device number 2 using vhci_hcd
[ ?113.667834] vhci_hcd: vhci_device speed not set
[ ?113.737950] usb 1-1: SetAddress Request (2) to port 0
[ ?113.776708] usb 1-1: config 1 contains an unexpected descriptor of type 0x2, skipping
[ ?113.776729] usb 1-1: config 1 interface 9 altsetting 0 has a duplicate endpoint with address 0x85, skipping
[ ?113.780855] usb 1-1: New USB device found, idVendor=0483, idProduct=a34c, bcdDevice= 1.00
[ ?113.780865] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ ?113.780870] usb 1-1: Product: QMX Transceiver
[ ?113.780873] usb 1-1: Manufacturer: QRP Labs
[ ?113.924261] vhci_hcd: connection closed
[ ?113.924577] vhci_hcd: stop threads
[ ?113.924584] vhci_hcd: release socket
[ ?113.924590] vhci_hcd: disconnect device
[ ?118.801330] usb 1-1: can't set config #1, error -110
[ ?118.851634] usb 1-1: USB disconnect, device number 2
?
In the Windows error log, there is also mentioned an error identifying a device according to an address issue.
?
I can confirm (as before), the other USB Serial Port Settings (1 and 2) do work.
?
73 de Moritz KO6DZX
?
|
Thanks Moritz
I found one more single byte error in the 440-byte Compound USB descriptor. Amazing how Linux manages to sort everything out and work fine anyway, despite the errors.?
I've fixed that but I'm now going through the entire 440 byte descriptor and checking everything for each of the three modes (1, 2, 3 serial ports). Then I'll try booting in Win 10 and check it there. If that all works I'll publish a 1_01_007 that will hopefully resolve everything in all cases (hopefully also Win 7 but I can't check that so will wait for news from Ludwig on that).
73 Hans G0UPL
Hi,
?
the Problem with the USB Serial Ports = 3 persists on Windows 11.
While using am using WSL (Ubuntu Linux) and forwarding the USB ports to the WSL i got some more debugging output, that might help to track the issue further down:
Relevant dmesg output attaching the QMX with USB Serial Ports = 3:?
[ ?113.234442] vhci_hcd vhci_hcd.0: pdev(0) rhport(0) sockfd(3)
[ ?113.234452] vhci_hcd vhci_hcd.0: devid(524289) speed(2) speed_str(full-speed)
[ ?113.234542] vhci_hcd vhci_hcd.0: Device attached
[ ?113.517512] vhci_hcd: vhci_device speed not set
[ ?113.587627] usb 1-1: new full-speed USB device number 2 using vhci_hcd
[ ?113.667834] vhci_hcd: vhci_device speed not set
[ ?113.737950] usb 1-1: SetAddress Request (2) to port 0
[ ?113.776708] usb 1-1: config 1 contains an unexpected descriptor of type 0x2, skipping
[ ?113.776729] usb 1-1: config 1 interface 9 altsetting 0 has a duplicate endpoint with address 0x85, skipping
[ ?113.780855] usb 1-1: New USB device found, idVendor=0483, idProduct=a34c, bcdDevice= 1.00
[ ?113.780865] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ ?113.780870] usb 1-1: Product: QMX Transceiver
[ ?113.780873] usb 1-1: Manufacturer: QRP Labs
[ ?113.924261] vhci_hcd: connection closed
[ ?113.924577] vhci_hcd: stop threads
[ ?113.924584] vhci_hcd: release socket
[ ?113.924590] vhci_hcd: disconnect device
[ ?118.801330] usb 1-1: can't set config #1, error -110
[ ?118.851634] usb 1-1: USB disconnect, device number 2
?
In the Windows error log, there is also mentioned an error identifying a device according to an address issue.
?
I can confirm (as before), the other USB Serial Port Settings (1 and 2) do work.
?
73 de Moritz KO6DZX
?
|
Hello Hans,
?
here are some new data I've got when analysing the USB data stream.
I started QMX and PuTTY and the collected data are starting the moment when hitting ENTER.
Each line is one packet (transmission).
?
FW 003
PC->QMX? BULK out "0d"
QMX->PC? BULK in "1b 5b 32 4a"
PC->QMX? BULK in (Response in)
QMX->PC? BULK out (Request in)
QMX->PC? BULK in "1b 5b 48 1b 5b 3f 32 35 6c"
PC->QMX? BULK in (Response in)
QMX->PC? BULK in (1b 5b 33 33 6d 1b 5b 32 34 3b ...) (the menu text)
?
FW 006
PC->QMX? BULK out "0d"
QMX->PC? BULK out (Request in)
QMX->PC? BULK in "1b 5b 32 4a"
?? nothing more
When hitting a character in PuTTY it's send from the PC -> QMX and the transmission is confirmed by the QMX. So the canal is not dead.
?
It looks like the second block (QMX->PC BULK out) is at the wrong place.
?
73 Ludwig
|
Paul - AI7JR
Richard Dyer