¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. QRPLabs
  2. Messages
Expanded Topics Messages Polls
Date
Re: #qmx SSB Firmware beta 1_01_006 release #qmx

 

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
Re: QMX+ shutdown problem #qmx #QMXplus #shutdown

 

Ok, weirdness prevails..
Q102 and D109 did fix the initial problem and it is up and running. Mostly
When I was troubleshooting why I wasn't getting 3.3v, I pressed the scope probe onto the drain of Q110 and it magically came to life. Mostly
VCC is 4.96
VDD is 3.3
The linear regulator has turned off and varying the input voltage makes the PWM duty cycles change. :-)
And VCC - VDD stay right where they belong.
But! The ADC_3V3 signal measures 1.24v and the diagnostics page shows that VDD is 2.54. Which it is not. It is 3.3.
I re-measured R110 and R112 and still both measure in the vicinity of 22k depending on how long I let the meter charge up C106. 24k this time around. And just to be sure I measured across both of them and I get 48k. So they seem to be ok.
--
Randy, N4OPI
Re: #qmx SSB Firmware beta 1_01_006 release #qmx

 

¿ªÔÆÌåÓý

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?

From: [email protected] <[email protected]> on behalf of Erik Larson via groups.io <kd7ykq@...>
Sent: Friday, April 25, 2025 6:12 PM
To: [email protected] <[email protected]>
Subject: Re: [QRPLabs] #qmx SSB Firmware beta 1_01_006 release
?
Tony, See my description, I did change a port as you suggested, and the "changed" port would not work.
?
Erik - AD7OV
Re: #qmx SSB Firmware beta 1_01_006 release #qmx

 

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
Re: #qmx SSB Firmware beta 1_01_006 release #qmx

 

Tony, See my description, I did change a port as you suggested, and the "changed" port would not work.
?
Erik - AD7OV
Re: #qmx SSB Firmware beta 1_01_006 release #qmx

 

¿ªÔÆÌåÓý

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

From: [email protected] <[email protected]> on behalf of mux_folder2001 via groups.io <canthony15@...>
Sent: Friday, April 25, 2025 4:19 PM
To: [email protected] <[email protected]>
Subject: Re: [QRPLabs] #qmx SSB Firmware beta 1_01_006 release
?
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

From:[email protected] <[email protected]> on behalf of Erik Larson via groups.io <kd7ykq@...>
Sent:?Friday, April 25, 2025 4:45 PM
To:[email protected] <[email protected]>
Subject:?Re: [QRPLabs] #qmx SSB Firmware beta 1_01_006 release
?
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
?
Hamvention?

 

Will QRP labs be at Hamvention in Ohio? If so, what booth/building please.
Will you have built kits (QMX+) on hand for sale?
Thanks and ¡®73
Jim WX8J
Re: #qmx SSB Firmware beta 1_01_006 release #qmx

 

¿ªÔÆÌåÓý

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

From:[email protected] <[email protected]> on behalf of Erik Larson via groups.io <kd7ykq@...>
Sent:?Friday, April 25, 2025 4:45 PM
To:[email protected] <[email protected]>
Subject:?Re: [QRPLabs] #qmx SSB Firmware beta 1_01_006 release
?
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
?
Re: #qmx SSB Firmware beta 1_01_006 release #qmx

 

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.
?
Re: #qmx SSB Firmware beta 1_01_006 release #qmx

 

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
?
Re: #qmx SSB Firmware beta 1_01_005 release #qmx

 

Hi Hans,

the new calib feature is working much better! Thank you!

1. My QMX+ on had problems on 80m on 004 => on 005 it's working completely*. (*I didn't try 160m)
2. My QMX 80-20m had only a few bands working on 004, the currently running calib process looks much better on 005.
3. My QMX 20-10m (with added 6m) is still problematic:
? ? ? ? ?Only 12m is looking good in all 3 calib steps.
?
Although the hardware of all devices is similar, the results are quite different.
?
My Questions:
Do we have a top list of components with the greatest influence on the calibration process?
Maybe, it's not only the transmitter, but also the receiver?
Are there components, the builder can influence?
?
Serial ports:
On Linux the serial ports are working fine, but for the first time I recognized that the modem manager was active.
It didn't interfere on 003 or earlier. The hints in the manual worked.
?
PS:
I had fun with the high band QMX on Madeira.?
It was very easy to work several PY stations in CW on 10m!
For CW 003 is working very nicely.
?
73 Peter DL4PJ
?
Re: #qmx SSB Firmware beta 1_01_006 release #qmx

 

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
Re: #qcxmini BPF Alignment Issues #qcxmini

 

Hi Scott. Don't do any changes to T-1. Photo shows it to be wound perfectly ... that is, if you intended to wind it for 40 meters... You should first verify you installed the correct capacitor at C5 (39 pF labeled 390) and then check for approximately 2.5v at pins 7 and 9 of IC4. If that isn't there then you probably still have some enamel on T-1 wires. Also look at the soldering on C1. The grounded leg is a little harder to get a good joint and needs a little more heat.?

Since you see it working with slight pressure applied, this pressure is probably bending the board and making a bad joint get better temporarily. Keep looking at the board with magnification. You will find it. And since that pressure makes it seem to come up to normal, then there is no need to re-wind T1. Just make sure all the connections are good.

Good luck ... Ron

On Fri, Apr 25, 2025 at 9:32?AM Scott Rainey KO4BJW via <skot0123=[email protected]> wrote:
I just finished my first kit, the QCX Mini. I have very little experience with soldering, other than a few arduinos and such, so I'm pretty new to this.
?
When I go through the alignment steps I find that the BPF readings are very low, around 3-4 max. I've checked continuity on T1 legs and they appear to be fine between each pair. I did heat them up again just to make sure the enamel was burned off. A strange behavior I have found is that if I apply a little pressure on the display board towards the top edge of the screen or bottom edge, as indicated by the circled areas in the picture, the scale goes up to 8ish and is adjustable. I tried a hack to test if this made a real difference and wedged a little bit of paper in the spot, while in the case, to see if it held true but it didn't. Before I desolder and rewind T1 is there something else I should check? I do not own an oscilloscope, only a DVM.
Re: #qmx SSB Firmware beta 1_01_006 release #qmx

 

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
?
Re: #qmx SSB Firmware beta 1_01_005 release #qmx

 

Serial port status with 1_01_006 on my Win10 home machine:
- selecting 1 port works fine (presents as COM10)
- selecting 2 ports work fine (present as COM10, COM12)
- selecting 3 ports does not work: no COM ports appear.? In device manager, the USB Composite Device has this status:
This device cannot start. (Code 10)
{Operation Failed}
The requested operation was unsuccessful.
I couldn't see anything else in the driver events/messages that seemed useful.
?
But on my system with 1_01_004, all 3 ports worked fine, presenting as COM10, COM11, COM12.
The composite device started just fine.
?
Stan KC7XE
Re: Manual tuner selection?

 

This is how I tune but I find it difficult tuning while watching digits rapidly change. It would be great if there was an option to show the SWR on a bar graph of some sort.
Re: #qmx SSB Firmware beta 1_01_005 release #qmx

 

¿ªÔÆÌåÓý

Here is the successful one.

Tony
AD0VC

From: [email protected] <[email protected]> on behalf of mux_folder2001 via groups.io <canthony15@...>
Sent: Friday, April 25, 2025 2:46 PM
To: [email protected] <[email protected]>
Subject: Re: [QRPLabs] #qmx SSB Firmware beta 1_01_005 release
?
I had one success and one failure. I have attached the failure.

Tony
ADoVC
From: [email protected] <[email protected]> on behalf of Hans Summers via groups.io <hans.summers@...>
Sent: Friday, April 25, 2025 2:36 PM
To: [email protected] Notification <[email protected]>
Subject: Re: [QRPLabs] #qmx SSB Firmware beta 1_01_005 release
?
P.S. Tony please run 30m calibrarion and screenshot it at DAC 300 (or thereabouts) and again at it's completion or however far it gets.?

73 Hans G0UPL


On Fri, Apr 25, 2025, 23:35 QRP Labs <hans.summers@...> wrote:
Hi Tony

1 works, 2 works, but 3 ports results in no com ports.

Ok that will be another thing for me to investigate then, considering that 3 worked for you in 1_01_004.?

I'm keen to hear from Ludwig about Win7...

73 Hans G0UPL

Screenshot 2025-04-25 144056.png
Screenshot 2025-04-25 144244.png

Re: #qmx SSB Firmware beta 1_01_005 release #qmx

 

¿ªÔÆÌåÓý

I had one success and one failure. I have attached the failure.

Tony
ADoVC

From: [email protected] <[email protected]> on behalf of Hans Summers via groups.io <hans.summers@...>
Sent: Friday, April 25, 2025 2:36 PM
To: [email protected] Notification <[email protected]>
Subject: Re: [QRPLabs] #qmx SSB Firmware beta 1_01_005 release
?
P.S. Tony please run 30m calibrarion and screenshot it at DAC 300 (or thereabouts) and again at it's completion or however far it gets.?

73 Hans G0UPL


On Fri, Apr 25, 2025, 23:35 QRP Labs <hans.summers@...> wrote:
Hi Tony

1 works, 2 works, but 3 ports results in no com ports.

Ok that will be another thing for me to investigate then, considering that 3 worked for you in 1_01_004.?

I'm keen to hear from Ludwig about Win7...

73 Hans G0UPL

Screenshot 2025-04-25 144421.png
Screenshot 2025-04-25 144453.png

Re: #QMX+ ongewenste eeprom initialisatie

 

Dank Hans, had dit vandaag 2 keer gehad was me eerder niet opgevallen.
73's Ad
Re: #QMX+ ongewenste eeprom initialisatie

 

Dank Stan voor je snelle reactie!?
121 - 140 of 141905