Does anyone know about any small manual (or auto if it works with qmx) tuners that can handle 70w? I am building a 3d printed case for my qmx, and an amp. I need a good light tuner.
Mostly CW here too, but I did a couple of Qs on SSB. Local, but I got good signal and audio reports on 10m.?
--
73, Dan? NM3A
|
Re: #qmx SSB Firmware beta 1_01_007 release
#qmx
Mine worked great with two ports enabled then I enabled 3 ports and it dropped all 3 com ports after 10 minutes. I'm going to try again!
|
Re: #qmx SSB Firmware beta 1_01_007 release
#qmx
Hans ¡ ? Version 007 fixed my problems with Win11 dropping ports after 10 minutes or so. Everything playing nicely now for an hour. ? Thank you for all you extra work on this! 73 Dick, K5AND ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Hans Summers via groups.io
Sent: Saturday, April 26, 2025 9:24 AM
To: [email protected] Notification <[email protected]>
Subject: [QRPLabs] #qmx SSB Firmware beta 1_01_007 release? I updated the?SSB?beta?testing webpage of the brave, here:??and released?firmware?version?1_01_007 to it.? This fixes one more typo I found in the USB compound device configuration. I carefully checked all 440 bytes one by one in all three configurations (1, 2 and 3 serial port). I believe in the 1-port configuration the configuration is byte for byte, identical to 1_00_027. Waiting for Ludwig to confirm any issues or not with WIn 7.? I booted my PC into Windows 10 on the old HD and all three serial ports worked properly, and audio too.?
|
Re: QMX: Is the latest firmware correcting the distorted audio?
On Fri, Apr 25, 2025 at 09:00 PM, Don wrote:
but I have a constant whistle. I can eliminate it by turning the mic gain way down into the 40s but then the audio starts to sound distorted again
This whistle sounds like it may be an acoustic feedback problem, perhaps with your mic and IC705 speaker.? Try with headphones on the IC705 and see if it goes away.? There are probably a few reasons this could happen on the high-band QMX but not the low-band one.
When you turn the mic gain way down, it would reduce/remove the feedback, but the noise-gating feature will start causing dropouts, garbling the audio.
|
Re: #qmx SSB Firmware beta 1_01_006 release - calibration
#qmx
Notes on calibration of my other QMX* devices.?? Some (hopefully) useful info:
?
Calibration of my QMX high-band:
- all completed normally and looked good, except 30m phase error had an irregular shape, large downs and ups near the beginning similar to the irregular shapes that occurred with earlier versions.
?
Calibration of my QMX+ rev2:?
- The 160m phase error plot stopped very early, at about DAC=750.? The symptoms were exactly the same as the 80m on my QMX low-band, where the calibration DAC values started at 2xxx rather than 0.? Retries do the same; it never completes.
- The 20m phase error plot stopped early, about DAC=1500.? But one retry allowed it to complete.? I didn't see the DAC values on the first run to see if they started high.
?
Calibration of my QMX+ rev3 (done overnight, so cooler temperatures):
- 40m, 30m, and 6m PE calibration stopped early; 40m at DAC~1000,? 30m at DAC~1200, and 6m at DAC~700.
- a single 'O' retry fixed the 40m and 6m PE sweeps.
- 'O' retries did not fix the 30m; it stopped at the same place, repeatable - See series of screenshots below.?
-? Note: 1) the new startup measurement messages are not present;
-? Note: 2) it stops after a "change greater than 30 degrees" message.? The change >30 degrees was in fact a measurement of 0.1 following a measurement of 359.8, so it was a phase rollover, not a large change.? So the change from near 0 to 359.7 at DAC=250 worked, but the opposite change from 359.8 to 0.1 at DAC=1250 did not work.
- I power-cycled the QMX+ (first power-cycle since start of calibration) to see if behavior would change on 30m; no change.?
- 160m USB IMD optimization flatlined with all values at 0 (I never saw that before).? A single 'O' retry fixed this (I did this before any of he above retries).
- All other PE and IMD completed and looked to have reasonable values.
?
I hope this info is useful in some way -
Stan KC7XE
?
|
Re: QMX+ with ~1000 tone on 12M & 6M
Hi All,
?
This is the 12m spectrum looks like on my QMX rev3, when dummy load connected.
Does this indicate a bad PCM1804? Do I need replace it?
--
73, de BD8BTE
op: Lun Yang
|
After testing the parameters with the help of Stan, Olivier and Martin, my qmx+ work now in CW and RTTY with Fldigi+flrig.
The right solution was to made FSK in fldigi and also turn the QMX+ in DIGI mode.
Many thanks for the help.
Thanks Hans for this nice rx/tx.
Best 73,
Andr¨¦ F6APU
?
?
|
Re: #qmx SSB Firmware beta 1_01_007 release
#qmx
Win 11 fw007 all three ports enabled and working...drops all 3 com ports after 10 minutes again. Set for two ports seems rock solid so far.?
|
Just joined the group qmx on the way
Thanks for letting me join the group. ?I placed an order for a qmx kit when I found out about the experimental ssb firmware. ?The boards look to be a work of art. ?Short of printing a mini mic housing anyone have a recommendation for an amazon mic they have gutted and put the proper element in? ?I have the modded mic I did for my sbitx I will try, but the element in it now may have too much gain. ?Looking forward to using this in the field and maybe in the shack!
?
Ryan
KK6DZB
|
Re: QMX SSB : Does a Baofeng Micro works ok ?
On Fri, Apr 25, 2025 at 07:03 AM, - Andy - wrote:
Cure is to replace the capsule for a few cents if you are unfortunate to have one.
On some of the old Retevis and Baofeng mics, the (physical) mic port is actually sealed leading to muffled audio.
Drilling a small hole in front of the element solves it and transmitted audio becomes clear.
You might check that before replacing the mic element.
?
73, Mike KK7ER
?
|
Re: #qmx SSB Firmware beta 1_01_007 release
#qmx
Hmmm
I think I must be doing something wrong...if so please enlighten
me!
Under 1_01_007, Lubuntu 25.04.: 1 port (default) seems to work. I
could connect with Putty to ttyacm0. Tried to change to 2 ports
via terminal, but it reverted to 1 port every time I moved off the
'Number of Ports' field.?
Changed to 2 ports using the QMX+ buttons and knobs, and saw
ttyACM0 and 1 in dmesg. Putty connected, but pressing enter did
not bring up the menu, on both of those. Did not reboot, but
restarted QMX+, restarted Putty. Same.
Did not try 3 ports.
Roger
8P6RX
On 26/04/2025 10:23, Hans Summers via
groups.io wrote:
toggle quoted message
Show quoted text
Hi all
I updated the?SSB?beta?testing webpage of the brave,
here:??and
released?firmware?version?1_01_007 to it.?
This fixes one more typo I found in the USB compound device
configuration. I carefully checked all 440 bytes one by one in
all three configurations (1, 2 and 3 serial port). I believe
in the 1-port configuration the configuration is byte for
byte, identical to 1_00_027. Waiting for Ludwig to confirm any
issues or not with WIn 7.?
I booted my PC into Windows 10 on the old HD and all three
serial ports worked properly, and audio too.?
|
Re: #qmx SSB Firmware beta 1_01_007 release
#qmx
My system info:
Tony
AD0VC
toggle quoted message
Show quoted text
This one seems to work for me. When I switched to 3 ports, device manager showed two COM11 ports and COM13. I changed one of the COM11 to COM12 (which was shown as "in use"). I had to power cycle the QMX+ and then everything works. I have tried all three ports
in terminal mode and COM11 in FT8.
Tony
AD0VC
Hi all
I updated the?SSB?beta?testing webpage of the brave, here:??and
released?firmware?version?1_01_007 to it.?
This fixes one more typo I found in the USB compound device configuration. I carefully checked all 440 bytes one by one in all three configurations (1, 2 and 3 serial port). I believe in the 1-port configuration the configuration is byte for byte, identical
to 1_00_027. Waiting for Ludwig to confirm any issues or not with WIn 7.?
I booted my PC into Windows 10 on the old HD and all three serial ports worked properly, and audio too.?
|
Re: #qmx SSB Firmware beta 1_01_007 release
#qmx
This one seems to work for me. When I switched to 3 ports, device manager showed two COM11 ports and COM13. I changed one of the COM11 to COM12 (which was shown as "in use"). I had to power cycle the QMX+ and then everything works. I have tried all three ports
in terminal mode and COM11 in FT8.
Tony
AD0VC
toggle quoted message
Show quoted text
Hi all
I updated the?SSB?beta?testing webpage of the brave, here:??and released?firmware?version?1_01_007
to it.?
This fixes one more typo I found in the USB compound device configuration. I carefully checked all 440 bytes one by one in all three configurations (1, 2 and 3 serial port). I believe in the 1-port configuration the configuration is byte for byte, identical
to 1_00_027. Waiting for Ludwig to confirm any issues or not with WIn 7.?
I booted my PC into Windows 10 on the old HD and all three serial ports worked properly, and audio too.?
|
#qmx SSB Firmware beta 1_01_007 release
#qmx
Hi all
I updated the?SSB?beta?testing webpage of the brave, here:??and released?firmware?version?1_01_007 to it.?
This fixes one more typo I found in the USB compound device configuration. I carefully checked all 440 bytes one by one in all three configurations (1, 2 and 3 serial port). I believe in the 1-port configuration the configuration is byte for byte, identical to 1_00_027. Waiting for Ludwig to confirm any issues or not with WIn 7.?
I booted my PC into Windows 10 on the old HD and all three serial ports worked properly, and audio too.?
|
Re: #qcxmini BPF Alignment Issues
#qcxmini
Thanks Ron, I appreciate the reassurance on my windings. I've checked the capacitor C5 and it is labeled 390 and C1 joint looks pretty good. I'll be resoldering the one leg of T1 as pointed out by Keith and if that makes no difference and then check voltage at pins 7&9.?
|
Re: #qcxmini BPF Alignment Issues
#qcxmini
No offense taken at all! I'll resolder the leg between C5 & C8.
?
I agree, from the front side it looks like an incomplete solder joint. From the back side it appears normal. I'm REALLY hoping this is it, I'm getting kind of discouraged after a few days of no progress in tracking down my mistake. I was very close to ordering a new board yesterday and starting over now that I have a little more experience.?
|
Re: #qmx SSB Firmware beta 1_01_006 release
#qmx
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
|
Re: #qmx SSB Firmware beta 1_01_006 release
#qmx
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
?
|
#qmx New build, incomplete initialization problem?
#qmx
Good day. My QMX+ V3 seems to be stuck in firmware update. By providing a new firmware file it will try to initialize, and after a few minutes gets stuck on Band Version. Stays there for a minute or so, then reverts to the clock. After that, I can get to screens with garbage. I can sometimes get to the Menus and beyond, in and out to non-sense screens. Both push buttons seem to work, because I can easily navigate in the menu, until the system gets stuck on a choice, then it goes back to the clock. ith a right button push, I can go back to garbage screens and sometimes into the menu system. From some of the screens, a quick push on the top decoder will result in a shut-down and a new firmware update state.
I conclude it is not fully initializing, for reasons unknown. I have tried a "Factory Reset" many times, and that seems to get stuck, too.
Ideas? Thank you in advance!
|
Re: #qcxmini BPF Alignment Issues
#qcxmini
Hi Scott
From your enclosed pictures I still don't like the look of the joint between the C5 and C8 legends. In the pic it has a dark ring around the wire, which the others don't have, suggesting that the solder has not wicked-up around the wire.
My apologies for calling your competence into question but I thought a recheck and resolder here would be a whole lot easier than doing the whole of T1 again.
Keith, G0GNL
|
Richard Dyer
Dick Hanson
