¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: QMX+ with WA3TFS amplifier

 

Thanks Donald - quite right. I¡¯m probably going to do what Jim is doing and just keep it a QMX / QDX only amp. It¡¯s just a fun little project to learn about and really appreciate the author putting it out. Then there¡¯s the fun of figuring out an ¡®issue¡¯ to make it work for your chosen radio.
?
Good stuff !
?
73, Jamie
WB4YDL


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

 

If you¡¯re running anything pre-Windows 10 which is connected to the internet you¡¯re really asking for trouble. However, rather than splashing out on a new whizzy machine, many older machines will run a flavour of Linux and be much more responsive than under Windows - and that upgrade is not going to cost you lots of money, perhaps just some time getting up to speed with the new OS.

--
¡ª

Amateur Radio Station EI6IGB/G8OGJ
New Ross
Co. Wexford
Ireland


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

 

On Wed, Apr 23, 2025 at 03:41 PM, Hans Summers wrote:
The SSB calibration tool now tests the PA amplitude modulator first, and refuses to run if the modulator isn't working properly. To determine if it is working properly or not, it sets the DAC value to 1000. This should produce a PA voltage of around?5.02 V in theory. "Fail" is when the measured voltage is outside the range 4 to 7V. Probably this range is too wide and could be considerably narrowed. But it should easily identify cases where a fault in the amplitude modulation circuit is causing the PA voltage to be always at max.,?which would both prevent proper phase distortion measurements, as well as prevent SSB generation working, as well as stress the PA transistors because they'd run at full power during the entire lengthy calibration process.
Might this be why I suspect my PA might have failed just now running calibration cycle?
I know I didn't need to but I wanted to see it run the process so I could see what it was doing...


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

 

The operating system that Hans uses with his QMX+, or one similar, should run on your existing hardware at no cost.


Re: QMX PA popped. :-(

 

Interestingly it looks like the cathode tab of D516 is not connected to the solder pad, looking like it might have been touching but now not; I'm wondering if this might have caused it.


QMX PA popped. :-(

 

Afternoon all,
?
Well, it was all going too well.
?
I had been using the 003 SSB firmware with good success and decided to flash the 004 update...this went well but I decided to run a calibration cycle and it got about 75% of the way through and the current draw jumped up with the attendant untoward smell emanating from the unit.
?
I suspect the finals have failed.
This was running on 10 V from my bench PSU with a proper dummy load so I'm not perplexed as to why this would have occurred.
?
Darn.


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

 

On Thu, Apr 24, 2025 at 02:29 PM, Brian KB9WFS wrote:
I would not spend any time making changes to support end of life or soon to be end of life operating systems.
Hello Brian, may I send you my bank account number to get money to by all the new stuff to use for field operation?
?
73 Ludwig


Re: FT8CN Getting it to Work!

 

I use FT8CN in POTA for activations (Android).
Calling CQ works well. ?Searching, e.g., for P2P QSOs, is more difficult with the limited screen.
The configuration settings are sufficiently commented ("?" , English), I disabled tracking because calls have to be deleted manually and as a block after the QSO.
The log is sufficient for POTA.
Conclusion: I save 1.5 kg (PC) of weight during POTA activations, which is a lot in a backpack. Normal QSOs are limited by the small screen and handling.
73 Reiner


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

 

I would not spend any time making changes to support end of life or soon to be end of life operating systems.


Re: qmx SSB Firmware beta 1_01_004 release + WSJT-X

 

¿ªÔÆÌåÓý

Hi Stan ¡­

I had set my polling to 10sec as Hans had suggested.

Thanks for your input.

?

Dick, K5AND

?

From: [email protected] <[email protected]> On Behalf Of Stan Dye via groups.io
Sent: Thursday, April 24, 2025 1:34 AM
To: [email protected]
Subject: Re: [QRPLabs] qmx SSB Firmware beta 1_01_004 release + WSJT-X

?

On Wed, Apr 23, 2025 at 03:41 PM, Dick Hanson wrote:

after about 8-10 minutes, the new com ports "go away" and WSJT stops working and wants connections repaired

I have just been operating FT8 with lots of contacts on 40m for over an hour now, with no com port problems.? For the last half-hour, I also connected to the QMX terminal and started the "Input analysis" screen - so it was actively using two of the com ports with no issues.

?

So I'm not seeing this behavior.?? What do you have your wsjt-x 'poll interval' set to?? Mine is at 60sec; I changed it to 5sec for the past 15 min to see if that made a difference, but so far OK, including a fun QRP contact to the VP2VI expedition, and another the opposite way to Hawaii, so QMX is doing well on 5W!.


Stan KC7XE

?


Re: qmx SSB Firmware beta 1_01_004 release + WSJT-X

 

¿ªÔÆÌåÓý

Good morning, Hans ¡­

?

I am using Windows 11, 64 bit.

Only WSJT is connected and other two ports unused.

The system plays nicely for a short time and then drops the ports.

After turning radio off and then back on, the ports are back.

?

Just to be clear, this issue is NOT present with 003 version.

73

Dick, K5AND

?

From: [email protected] <[email protected]> On Behalf Of Hans Summers via groups.io
Sent: Thursday, April 24, 2025 1:44 AM
To: [email protected]
Subject: Re: [QRPLabs] qmx SSB Firmware beta 1_01_004 release + WSJT-X

?

Hi Dick and Richard,?

?

You reported COM ports got dropped in the new firmware - I have not seen any problems. But I am using Linux.?


It would be very helpful if you can provide more details. What is your OS (most important question)? But also, did you connect ONLY WSJT-X via CAT, or were you also using the other two ports for something? I ask, because quite possibly there is some kind of unwanted interaction between ports; it's quite tricky to create a multi-session system and I may have neglected something, something that doesn't provide perfect isolation between the different connections.?

?

73 Hans G0UPL

?

?

On Thu, Apr 24, 2025 at 9:33?AM Stan Dye via <standye=[email protected]> wrote:

On Wed, Apr 23, 2025 at 03:41 PM, Dick Hanson wrote:

after about 8-10 minutes, the new com ports "go away" and WSJT stops working and wants connections repaired

I have just been operating FT8 with lots of contacts on 40m for over an hour now, with no com port problems.? For the last half-hour, I also connected to the QMX terminal and started the "Input analysis" screen - so it was actively using two of the com ports with no issues.

?

So I'm not seeing this behavior.?? What do you have your wsjt-x 'poll interval' set to?? Mine is at 60sec; I changed it to 5sec for the past 15 min to see if that made a difference, but so far OK, including a fun QRP contact to the VP2VI expedition, and another the opposite way to Hawaii, so QMX is doing well on 5W!.


Stan KC7XE

?


CW Practice / Rag Chew

 

¿ªÔÆÌåÓý


On 4/23/25 I had a CW practice / rag chew session on 20 meters. I worked two stations:


Conditions were OK. SSN = 142, SFI = 163, A = 12, K = 1.

Early on I heard a couple of weak stations calling but they were too weak to work. My next CW practice session will be?April 28 at 09:00 EDT / 13:00 UTC on 20 meters.?Anyone and everyone is welcome. This practice is intended for operators who are new to CW or they need some practice. IT DOES NOT MATTER HOW POOR YOUR CW IS. Mistakes are OK. Poor fists are OK. Slow speed is OK. Really slow speed is OK. This practice is meant for you to improve your CW. I will do my best to adjust to your skill level. Operate at any power level. If several stations show up, I will operate as a round-table control station. I will do it as a round-table so everyone gets a chance to transmit. Please listen to my directions.

Details:
Date - April 28 2025
Time - 09:00 EDT? 13:00 UTC
Band - 20 Meters


How to find me - I will find a clear frequency and call CQ. Go to the Reverse Beacon Network and search for my call sign AB8DF.


That will tell you what frequency I am on. Tune your station to that frequency and if you hear me give me a call. If there is a QSO in progress, please wait for a break in the action. Then send your callsign. If I hear you, I will invite you to join the QSO and start a round-table QSO.

Reply to this email if you have questions.

IT DOES NOT MATTER HOW POOR CW IS

Ed
AB8DF


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

 

I'll have a look at adding additional CAT commands to FLRIG in my next play-time :-)
Great to have the multiple terminals - FLRIG shown doing its stuff with the terminal monitoring CAT commands.


As an update to my previous - if your Linux distro already has serial by ID, thanks to Hans adding meaningful names to the interface, these show up in /dev/serial/bi-id like:
usb-QRP_Labs_QMX_Transceiver-if00 -> ../../ttyACM0
usb-QRP_Labs_QMX_Transceiver-if02 -> ../../ttyACM1
usb-QRP_Labs_QMX_Transceiver-if08 -> ../../ttyACM2


Obviating the need for the additional udev rules in my previous - however I like the snappier, short device name :-)

73 Simon G0FOZ


Re: Question: Does the power icon go on and off when you are sending CW?

 

¿ªÔÆÌåÓý

Thanks for the reply.?
I have enough cores to stop and stray RF I will try that.?

I have reread the manual and see that the power I referred to is ¡®tx status¡¯ ?and I will make the changes you suggest .

73 de k2cmc
Charlie

--
?
Charlie C. ?- K2CMC
LICW/SKCC/NAQCC?


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

 

Excellent work Hans,
?
I applied my hack on udev to get the new ports consistent, and now my machine shows:

?/dev/QMX00 -> ttyACM0
?/dev/QMX02 -> ttyACM1
?/dev/QMX08 -> ttyACM2

So I can now use a persistent name /dev/QMXxxxx for flrig / putty etc. instead of whatever ACMX is allocated irresepctive of how busy the ports are on this PC.

If any one else needs this the udev rule is:
SUBSYSTEMS=="usb", ENV{.LOCAL_ifNum}="$attr{bInterfaceNumber}"
SUBSYSTEM=="tty", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="a34c", SYMLINK+="QMX%E{.LOCAL_ifNum}", MODE="0666"
?
I've included the line that gets the interface serial from the USB info and passes to the terminal naming in the avove.

Thanks again Hans, and particularly for the new CAT codes - very useful to me.

73 Simon G0FOZ
?


Re: qmx SSB Firmware beta 1_01_004 release + WSJT-X

 

Hi Dick and Richard,?

You reported COM ports got dropped in the new firmware - I have not seen any problems. But I am using Linux.?

It would be very helpful if you can provide more details. What is your OS (most important question)? But also, did you connect ONLY WSJT-X via CAT, or were you also using the other two ports for something? I ask, because quite possibly there is some kind of unwanted interaction between ports; it's quite tricky to create a multi-session system and I may have neglected something, something that doesn't provide perfect isolation between the different connections.?

73 Hans G0UPL



On Thu, Apr 24, 2025 at 9:33?AM Stan Dye via <standye=[email protected]> wrote:
On Wed, Apr 23, 2025 at 03:41 PM, Dick Hanson wrote:
after about 8-10 minutes, the new com ports "go away" and WSJT stops working and wants connections repaired
I have just been operating FT8 with lots of contacts on 40m for over an hour now, with no com port problems.? For the last half-hour, I also connected to the QMX terminal and started the "Input analysis" screen - so it was actively using two of the com ports with no issues.
?
So I'm not seeing this behavior.?? What do you have your wsjt-x 'poll interval' set to?? Mine is at 60sec; I changed it to 5sec for the past 15 min to see if that made a difference, but so far OK, including a fun QRP contact to the VP2VI expedition, and another the opposite way to Hawaii, so QMX is doing well on 5W!.

Stan KC7XE
?


Re: qmx SSB Firmware beta 1_01_004 release + WSJT-X

 

On Wed, Apr 23, 2025 at 03:41 PM, Dick Hanson wrote:
after about 8-10 minutes, the new com ports "go away" and WSJT stops working and wants connections repaired
I have just been operating FT8 with lots of contacts on 40m for over an hour now, with no com port problems.? For the last half-hour, I also connected to the QMX terminal and started the "Input analysis" screen - so it was actively using two of the com ports with no issues.
?
So I'm not seeing this behavior.?? What do you have your wsjt-x 'poll interval' set to?? Mine is at 60sec; I changed it to 5sec for the past 15 min to see if that made a difference, but so far OK, including a fun QRP contact to the VP2VI expedition, and another the opposite way to Hawaii, so QMX is doing well on 5W!.

Stan KC7XE
?


Re: Question: Does the power icon go on and off when you are sending CW?

 

The power meter should "pulse" on with every dot and dash, and will go off between them at lower CW speeds.
This can be controlled with the "Tx->Rx hang time" setting for the "Pwr/SWR display".
?
The CW keyer should never "go to sleep" while sending.? This suggests you may have RF coming back on your feedline that interferes with the keyer.?? This can happen even with a well-matched antenna from "common-mode currents" that arise from imbalances in the antenna system, and often happens with EFHW antennas (and others).? Try adding a common-mode choke (or several ferrite beads) to your feedline, or to the cable between your radio and tuner and see if the problem goes away.
?
?


Re: QMX SSB settings for Winlink?

 

You can use the terminal menu to set the mode with a CAT command:
open "PC and CAT", then "CAT command test", then type the MDx command to set the mode
x = 1 for LSB, 2 for USB, 3 for CW, and 6 for DIGI.
MD (without the number following) returns the current mode.
?


Re: Jeffery Moore contact info

 

See this post he made a few months ago with his contact info:
?