Re: Manual tuner selection?
Did you try tuning using the Tune/SWR mode?? In that mode, QMX uses reduced power and turns off the swr protection. That may work with your LDG tuner.
|
Is there a manual tuner that ppl use with the QMX+ - I tried using my LDG Z817 and it seems to go into protective mode for final. too high swr.?
?
Im too old to build and am looking for something retail I can get.?
?
Any suggestions??
?
--
?
Charlie C. ?- K2CMC
LICW/SKCC/NAQCC?
|
I took my QMX to Mt. Porepunkah in North Eastern Victoria for some SOTA and worked another QMX on the North Island of New Zealand on 20m (ZL1HIM). Clear audio both ways.
Cheers?
Glenn VK3YY.?
|
Re: Circuit description around PS and its supply¡
Yes, what Ludwig recommends is important.? A failed Q508 could be the cause of the problems, with D516 being the trigger.
Here is one theory of what happened:
a) With D516 either not connected, or worse, intermittently connected, all of the rapid tx/rx cycles during calibration stressed Q508 until it broke (likely shorted D-S).? [Perhaps this broke IC402, also, since failures there were the reason D516 was added.]
b) With a shorted (always on) Q508, there is an unexpected load during transmit put on the output of T501 and hence the PA transistors; akin to having a high swr.? They responded by failing during the full power parts of the calibration.
c) Failed PA transistors can overload Q507 and/or IC503, causing one or both of those to fail.? We can hope that didn't happen.
?
So do check Q508 before powering up with new PA transistors.
?
This failure theory would have happened independently of firmware if you operated CW with its full break-in, over perhaps an extended period; or at least doing so would have stressed Q508 such that it broke during calibration.
?
Stan KC7XE
|
Re: Circuit description around PS and its supply¡
On Thu, Apr 24, 2025 at 11:33 PM, Wiggle Pig wrote:
D516 wasn¡¯t soldered on correctly at the cathode.
You should check Q508 in RX and TX mode (voltage at S, D and G). To cut the high current lift a leg of L502.
A broken Q508 could be a dangerous load for the PA and may affect the RX path.
?
73 Ludwig
|
Re: #qmx SSB Firmware beta 1_01_004 release
#qmx
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
toggle quoted message
Show quoted text
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
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
?
?
?
?
|
Re: #qmx SSB Firmware beta 1_01_004 release
#qmx
On Thu, Apr 24, 2025 at 04:15 PM, Ian Beeby wrote:
If you¡¯re running anything pre-Windows 10 which is connected to the internet you¡¯re really asking for trouble.
Thanks for your warning Ian. Don't worry, why should I connect my field operation computer to the internet?
perhaps just some time
In my life I had to deal with at least 13 OS and version of OS (not only MS). It took me a whole amount of my life. Often only to get something I had before before I was forced to switch to an other OS or version. And now I don't want to go to a parallel OS universe.
?
73 Ludwig
?
|
Re: #qmx SSB Firmware beta 1_01_004 release
#qmx
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
toggle quoted message
Show quoted text
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
?
?
?
?
|
Re: #qmx SSB Firmware beta 1_01_004 release
#qmx
Thank you, Tobias. Makes me feel a bit better not being in left field, alone. 73 Dick, K5AND ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Tobias [DL3MHT]
Sent: Thursday, April 24, 2025 3:47 PM
To: [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) Windows has stopped this device because it has reported problems. (Code 43) A request for the USB device descriptor failed. 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 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: 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.
|
Re: #qmx SSB Firmware beta 1_01_004 release
#qmx
Immediately after the firmware update, I ran PA mod. test:  And then attempt to run DAC error vs phase on 20m.? It generated an error that would not let me run the test like what is noted in the notes on the original post.? I disconnected the radio from power and attempted to reproduce, but the test ran fine the second attempt.? I have not be able to reproduce it, but I suspect it might be related to immediately running the test post firmware update?
|
Re: Circuit description around PS and its supply¡
Aha, many thanks for this.
i can¡¯t really test that or look in the menus at the moment as the draw when powered up n receive is quite high through the PA. Once I take out the PA transistors then I can check that but hopefully Q507 is OK as I haven¡¯t got a spare for that one at the moment!
?
Thank you so much for the info, hopefully I can get this unit back in working order soon¡I¡¯m really miffed that I popped it as I haven¡¯t had it long and really like it! All that aside I¡¯m quite perplexed why this has happened as I wasn¡¯t doing anything untoward to it; I had the supply at 10V and was running a calibration into a decent dummy load when it occurred, although when I removed it from the case I noticed that D516 wasn¡¯t soldered on correctly at the cathode. ??¡á?
?
homhum. Thanks for the information though. ?
?
73
Piggly
|
Re: #qmx SSB Firmware beta 1_01_004 release
#qmx
Ups, I should have mentioned: I got the USB failures with a High-Band QMX, not QMX+
But in theory that shouldn't matter...
?
-Tobias
?
|
Re: Circuit description around PS and its supply¡
Ah, you beat me to the post there Stan.?
|
Re: Circuit description around PS and its supply¡
I believe that Q507 is switched on during receive, however if you go to the diagnostic screen in terminal it is switched off and only switches on when in TX. ?I haven¡¯t got either of mine in bits to confirm, but from memory I believe it was set up this way so the modulator function could be tested. ?Don¡¯t take this as gospel, as I may have misremembered.?
Nick G0OQK
|
Re: Circuit description around PS and its supply¡
Yes, the tx voltage is on during receive, and will be very close to the supply voltage.
Hans has given a good description of why this is done; it helps receive work better.
It is turned off when entering the diagnostics tool, so you can see a near-0V value in receive, and its full tx value during 'T' tx test.? It is turned back on when exiting that tool.? This is a good way to test Q507 - because if Q507 is broken, it won't go down to near 0V.
?
Having the tx voltage on during receive is normally not a problem for the PA.? The TX signal is off, so the PA driver and gates of PA transistors are off.? It should only be an issue if there is something shorted/failed in that circuit (the BS170s or driver chip).
|
Re: #qmx SSB Firmware beta 1_01_004 release
#qmx
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
?
?
?
?
|
Re: QMX and WinLink/WARA HF settings
Chris, I've never used the Winlink auto-connect feature.? You will need to ask this question in a Winlink forum; it is independent of VARA and radio (QMX).
Stan KC7XE
|
Re: My QMX is turning off, when I reduce voltage under 10V
Hello Ludwig and Hans,
?
because I have planed a SOTA activation and my power supply has no current limit, I didn't want to risk with the check before that. Nothing was visible damaged or burned.
After my successful SOTA activation (there I suddenly met another OM, he had also a QMX :-),
I have tested it now - and, YESSS, it was D105!!!
Because I had no other SMD part, I took a "normal" 1N4148, there was enough space to bend and solder it comfortably.
Now, everything is working perfectly down to 7V.
?
Ludwig, thank you for your support and explanation of the function principle, this was very instructive and inspiring.?Hans, thank you for your brilliant construction of QMX and your support.
?
73 es CUAGN de Stojan, DK4SR
|
Circuit description around PS and its supply¡
Evening all
?
I have a question regarding the operation of the power control around the PA transistors¡does the DAC drive Q512-5 and therefore Q507 when the unit is in receive, meaning the PA supply is present on Q503-6 all the time?
?
My unit¡¯s poorly PA draws excessive current (~2A or so) in receive and the transistors get too warm; I have spares on the way but now I¡¯m wondering about Q507¡
?
Tra all!
|
Re: #qmx SSB Firmware beta 1_01_004 release
#qmx
If I have done a successful calibration with 1.01.003 that I shouldn't have to recalibrate if upgrading to this new version?
|
Glenn S
Dick Hanson