Keyboard Shortcuts
Likes
- QRPLabs
- Messages
Search
Re: Manual tuner selection?
¿ªÔÆÌåÓýI have good luck with my ZM-2 ATU. Google EMTECH... they come as a kit or pre-built. Jerry WB7S LICW/SKCC/CWOpp On 4/24/2025 7:15 PM, Charlie Cacioppo
via groups.io wrote:
|
QMX SSB : Does a Baofeng Micro works ok ?
Hi, I tried to use a standard Baofeng micro , the one with a small loudspeaker inside that is not usable with QMX.
I have done the easy mods to make possible using this mike with the QMX. No a big issue ...
Tried also the Microphone Test tool in the QMX sw, and the mike seems ok using only 40 db for gain.
BUT, if I listen with another radio the modulation is very bad .. !! Possibly the two radio too close ??
Unfortunatly, if I talk ,does not seem to exit any RF or just a little bit, from the QMX ( I have a swr/wattmeter in line..).
In CW all is ok, in SSB Baofeng micro seems no good. Have you tried the Baofeng Micro ? I guess every body owns one of
this mike that why I am asking.?
?
73 de angelo i1jck |
Re: #qmx SSB Firmware beta 1_01_004 release
#qmx
1_01_004 - menu item history fix would be very helpful
?
With the addition of new items under 'Hardware tests' in the menu, we can now no longer just click twice on the menu button to get to the Tune SWR menu (after using it once).? The 'Hardware tests' selection is remembered, but not the next level down in the menu.? So now it will always go to 'AF filter sweep' (not very often used), and you have to turn the knob to get to 'Tune SWR'.? It would be very nice for QMX to remember the last function used at least one more level down in the menu tree.
?
Similar behavior happens for selecting a CW filter bandwidth - now that the settings are grouped under the new 'CW' section, it does not remember that the last setting I chose was 'CW passband', making it a bit more trouble to change the CW filter.?
?
Stan KC7XE |
Re: Manual tuner selection?
Menu -> Hardware tests -> Tune SWR
from pg 56 of the operations manual:
?
SWR measurement The SWR measurement tool enables the transmitter at a reduced supply voltage determined by the operating percentage defined in the Tune % parameter of the Protection menu. This percentage is displayed for information on the top right of the screen. The top left shows the operating frequency for the SWR measurement, which is the center frequency of the band. The band name is displayed in the bottom left, and SWR measurement in the bottom right. The SWR measurement is updated ten times per second. Controls: ? Use the left rotary encoder to change the band. ? Use the right rotary encoder to change the frequency. ? Start the SWR measurement by pressing the left push button (Keyer/RIT/Menu). The SWR will continue to be displayed until the SWR measurement tool is closed, or the left push button is pressed again, or the rotary encoder is turned to change the band, or a 60 second timeout expires. ? Use the right push button to exit the SWR measurement tool. |
Manual tuner selection?
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? |
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
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
?
?
?
?
|
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?
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
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
?
?
?
?
|
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 ? 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 ? In Device Manager: ? 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 ? Device not started: Device USB\VID_0000&PID_0002\8&29c54ea8&0&1 had a problem starting. Driver Name: usb.inf ? --- ? 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 ? Device started (usbccgp): Device USB\VID_0483&PID_A34C\8&29c54ea8&0&1 was started. Driver Name: usb.inf --- ? If you need anything else Hans, let me know. 73 Tobias ? ? ? ? |
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
? |