开云体育

Well SSB sure works. Yesterday I worked S51DX in Slovenia on 20 metres. That's 8,700+ km with less than 3 watts! My MIC settings were pretty basis but I did add a little compression (set to 5).

?

I'm a happy camper!

--

73, Rick
VE7TK

Website:

Hello Hans

?

Thanks for the detailed analysis and info.?

I had a suspiction that CPU overload may be the reason…

I agree, it is not necessary to update the graph when on TX. User will use a websdr or another radio to check anyway.?
Even on RX I think it is not necessary, can be done once when the setting is confirmed and saved.?

73

Pawe? SO8FM

QMX+, updated to 1_01_003 without any problem. Calibrated without a problem. Already couple SSB contact made.

?

The issue I observed is when you transmit and want to play with equalizer settings at the same time, the QMX+ menu freezes from time to time, especially if you want to make significant change (more than one step, eg. change from +3 to -6 with single fast encoder turn). It unlocks afer a while or after release and press PTT again. Back to RX after PTT release is also delayed then, sometimes stuck on TX. Tested with dummy load. No difference if you are talking to the mic or not, I would assume this is not RF-in-the-shack topic.

?

Functional comment for Equalizer settings: when you go to the max setting (+20) it should stop increasing and not turn over to -20. Same may apply for other settings where 0 is in the middle.

?

73

Pawe? SO8FM

I saw weird calibration results, so my question is should I compare performance with/without calibration?

I assume a factory reset removes calibration or just turn off Phase and Amplitude distortion in the SSB menu.

?

Chris

Hans,

The CW decoder / messaging system has a minor mistake still.? The dictionary used translates the <VE> prosign as? "!"??? ...-. displays "!"? when it should display "VE".? Using a "!" in a stored message plays "VE"

Alternatively, I appreciate that the ! is in the decoder dictionary and do not think it should be removed, but it should be dah-di-dah-di-dah-dah? -.-.--

?

Thank you,

Adam KD9AIE

Hans,

On 003 (20m to 10M QMX), 12m and 10m in DIGI mode seem to have reduced output when using wsjtx.? I unfortunately did not check this on Beta 001 or 002, but it is a noticeable difference from what I had previously experienced on those bands prior to Beta firmware. ? Looking at baseline dB between cycles:
20m 20+dB
17m 20+dB

15m 20+dB

12m under 10db? (prior, also 20+dB)

10m under 10db (prior, also 20+dB)

Thank you,

Adam KD9AIE

On Sat, Mar 22, 2025 at 06:53 AM, Hans Summers wrote:

You might try switching OFF the 80/20m BPF swap in the advanced configuration

Hans,

?

I have been having a similar issues on 20m. (20M to 10M QMX). When first running calibration, I used "R" run mode to do everything via the console.? On both 20m and 11m the Phase Error vs DAC plots finished very quickly and looked strange.? SSB effectively did not work and was just distortion on Tx.?? I re-ran BOTH Phase and USB for 20m using "O" once mode and while the Phase plot still looks strange it did change. Tx improved and I have been making contacts.?? The Phase plot changed when I ran it in "O" mode.?? Items to note:?

1) with 003 I used "R" run mode and was able to replicated the original problem with the plots on 20m and 11m.
2) this happens both when using the terminal via USB, and when just using the QMX menus disconnected from USB.
3) with 003 I can make SSB usable using "O" once mode for phase / USB / LSB calibration, but the plot is still strange:

An observation

If you have CW practice on and use "tune" it will show a SWR of about 1.7 no matter if a dummy load is connected or nothing is connected. A power meter shows that there is no RF out. It might be better to give a message to the user rather than a false reading.

--

? 73
??? KD8CGH

Hi all,

Just to say the SSB firmware is working great and getting better with each iteration - this is fantastic work Hans! But I hope you are going to take a break soon, you deserve it :)

One anecdote: I was using the new firmware with Winlink & Vara HF to successfully make contact with a node in Switzerland, but I was a little bit concerned as the power meter reading on the QMX wasn't showing anything at all, it wasn't budging - but I wrote this off as a quirk of the firmware and how it was interacting with the modem.

But nope. Operator error, of course! I had, somewhere along the line set the output volume of the QMX on my PC down to 50% - and despite, what must have been extremely low transmitted power; VARA HF was still working successfully. Suffice it to say it's working even better now with the volume adjusted back up to 100%.

Once again, fantastic work Hans - thank you for this amazing product,
Dave
EI3HIB

I'm still seeing some strangeness in the 80M sweep:

?

Not enough signal at the test frequency?

?

I'm enclosing it and the BPF filter sweep for reference:

Hans,

few observations/suggestions:

1. Practice mode does not make sense in SSB I guess. When enabled in CW Keyer menu and SSB mode is selected it could be temporarily disabled and then when CW is selected again it could be automatically re-enabled.

2. Displaying CW decoder text in SSB (in fact also in DIGI) does not make sense and looks rather disturbing. I suggest CW decoder part of the screen could be automatically cleared when SSB/Digi mode is selected or perhaps re-used to some other purposes in these modes. Mic input level would make sense in SSB.

3. Short press of left button bring up keyer speed in SSB. Does not make much sense

4. After copying the firmware file my QMX did not reboot itself. All is ok after recycling the power.

?

I can confirm this behavior for several Qxx devices.

?

Hajo

Is there any reason the phase calibration only goes upt to 1200 on 80m, 30m, and 20m?

?

73

?

?

Simon

VK3ELH

This update hang issue is kind of all over the place.

I had run into it upgrading to .002 but didn't fully characterize it because the resolution was fairly easy.

I have 2 QMX and 2 QMX+. (Sorry, I can't help myself....)

QMX 1 - Upgrade from .002. Displayed the symptoms below and also didn't enable the USB drive until I pressed the power button after I put it into update mode. The USB drive remains active and shows both the old and new firmware files after the file transfer. Unplug power, plug back in, turn it back on and the upgrade succeeded.

QMX+ - 1 Same as above.

QMX 2 - Upgrade from .002. Worked as expected. It turned on the USB drive, then off after file transfer, and rebooted on it's own after the transfer.

QMX+ 2 - Upgrade from .001. Worked as expected. It turned on the USB drive, then off after file transfer, and rebooted on it's own after the transfer.

--

Randy, N4OPI

hi, did the update on my qmx 80-20 tonight without any trouble...

calibration takes around 30 minutes, but cannot test SSB yet, have ordered a mic , so in a few days I can test "the ride" ?

?

vy 73 and many thanks to Hans and his great team?

?

ps: today I will upgrade my qmx 20-10 too and next week my qmx+ will arrive, waiting for directly updating ?

?

Mine is doing this as well.?

--

73, Dan - W2DLC