|
Awesome, thanks Hans!
73
-- Matt N3AR
On 4/23/2025 1:26 PM, Hans Summers via
groups.io wrote:
toggle quoted message
Show quoted text
are all of the virtual COM ports identical in
function in this latest QMX firmware?? Meaning can any
of the three be used for any supported function on the
QMX by an application?? Or is it like some radios
(looking at you, Yaesu) where the different virtual
COM ports support different functions/capabilities
from one-another.
I have never owned nor any radio transceiver
other than homebrew and QRP Labs radios. So I mostly have no
idea what they do.
But yes, in QMX, all three Virtual COM ports are
completely identical. In all cases, the supported
functions are currently CAT and Terminal. Any Virtual COM
port is assumed to be a CAT interface, unless a carriage
return or line feed character is received, in which case
it becomes a Terminal. No CAT commands ever include
carriage return or line feed characters which is why this
works. Choosing "Exit Terminal" from the main menu before
closing your terminal emulator returns a COM port to the
CAT function.?
73 Hans G0UPL
|
Fine here too:
?
Same Audio designator as before and same COM22 plus the new COM16 and 18, which were previously unassigned.
I have 4 QMXs and I just need to make sure I plug them into the same USB hub port each time so they come up with the same names.
At one point they were so messed up with changes to where I had them connected that I had to delete every QMX device, COM port, and USB hub port (Including hidden devices) from the device list and physically add each device back in where and in what order I wanted it to show up in the future. This included manually re-assigning the COM port numbers as they came up to the number I wanted.
?Windows 10.
?
Randy, N4OPI
|
Hello Hans,
I'm on Win7 and just finished my QMX+.? The QMX does appear in
the devices list but says it is not connected. I've got the STM
drivers but something is not right...
--
Jean-Jacques - F5IJO
FISTS#17008 LICW#5902
Le 23/04/2025 ¨¤ 22:15, Hans Summers via
groups.io a ¨¦crit?:
toggle quoted message
Show quoted text
Maybe it's only ok for Win10 and up. For field
operation I'm using an older and small Netbook / Notebook
only good for Win7. So I test all for Win7 using the
STMicroelectronics driver for Win7.
?
It would be nearly worst case if I would need a new
Notebook for field operation. Maybe I'm not the only one
who wants to use Win7 together with the QMX?
?
And besides the COM-Port also my audiodevice doesn't
work. I tested using Audacity --> Error.
If it turns out that the new multi-COM feature doesn't
suit Win10 then I could make this feature configurable, so
that if switched off, you just had exactly the same
configuration as before. So don't worry. Let's see, any
other people?with Win7? If so, any feedback?
|
I did some investigation on persistent port naming on Linux some time ago? - read here.? This should work with MACs too as a they a Linux(ish) under the hood.
Will upgrade the firmware and write a udev recipe for the QMX when I get a mo.
Si G0FOZ
Is it at all possible to set up virtual COM ports so that they will have a consistent name when (re)connecting? I've found that under MacOSX, the name changes every time you plug it in. This makes it slightly annoying when you have to set it up every time in WSJT-X and other software.
I think I've seen that ability on a seeedstudio T1000 meshtastic device.
It's done on QDX already and I intend to do it on QMX too. It only works on Linux. On Windows, the OS ignores the name you give it and always gets called COM4, COM5 etc. What happens on Mac I'm not sure! Perhaps some Mac user with a QDX could comment?
73 Hans G0UPL
|
|
|
QMXs
Low Band
80m 600
60m-20m 2500
?
Medium Band
60m-15m 2500
?
High Band
20m -12m 2200
11m 600
10m 2400
?
QMX+ (retest after factory reset)
Almost identical to earlier post
?
|
Hi Ludwig
Re your problem with WSJT-X.? I experienced the same problem BUT it was with ver 003.? The 'error in sound input' seemed to arise with no input from me - it just happened occasionally.? However I did find that the latest Hamlib update seemed to cause this error so I rolled back to the earlier version and now have no problem even with QMX+ ver 004.? This may help with your problem.
Regards
Greg, ZL4GW
|
Hi Hans
Just a minor point.? I have found when having 2 com ports open at the same time i.e. Putty and WSJT-X, the 'microphone test' in Putty doesn't work - there may be a couple of bars but it stops at that point.? However on closing one of the ports, the 'microphone test' functions properly.
Cheers
Greg, ZL4GW
|
Hi,
?
The driver support for Windows 7,? and Windows 10 and 11, is different.?
Check the internet for work arounds or perhaps YouTube.?
There were drivers available for my Windows 7, but I never got them working properly.
Upgrading to Windows 11 with a purchase of a small Mini PC will save a lot of aggravation.?
?
George
|
Hans-
?
? ?As always, great work and amazing results. The multiple virtual COM port discovery and development is quite intriguing - can I make a suggestion/recommendation? I have a QMX+ with the GPS module installed. It would be super cool if one of the those extra COM ports could echo the GPS data out to the connected PC. In this way the QMX+ w/ GPS could be used as a location and time source for the PC for time synchronization for WSJT-X modes or otherwise. When doing POTA I typically have a separate GPS USB dongle connected to a laptop for the sole purpose of time sync. If the QMX+ could provide that same functionality, via its onboard GPS, that is one less gadget/USB port needed.
?
Thanks for all your hard work!
?
Paul W9PEM
|
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
?
|
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 -> ../../ttyACM0usb-QRP_Labs_QMX_Transceiver-if02 -> ../../ttyACM1usb-QRP_Labs_QMX_Transceiver-if08 -> ../../ttyACM2Obviating the need for the additional udev rules in my previous - however I like the snappier, short device name :-)
73 Simon G0FOZ
|
I would not spend any time making changes to support end of life or soon to be end of life operating systems.
|
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
|
The operating system that Hans uses with his QMX+, or one similar, should run on your existing hardware at no cost.
|
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...
|
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
|
Except that one has to learn writing commands from scratch.?
I hope you are not going to suggest using one of the free GUIs that sit on top of Linux. Been there, done that and had to format the whole hard disk after the first update. Thank you for nothing.
I have already paid more than enough to MS and have got no intention to pay more in the near future for something that will soon become obsolete AGAIN.
Bekir TA2RX
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
|
I have windows 11 fw004 and everything is working great except about every 10 minutes Win11 drops all three com ports like clockwork. Power off QMX+ power back on and its up and running again for 10 minutes. Revert to fw003 no QMX+ config changes and its rock solid. I have reset to factory defaults after each flash.?
|
On Thu, Apr 24, 2025 at 10:56 AM, ta2rx bekir wrote:
I hope you are not going to suggest using one of the free GUIs that sit on top of Linux. Been there, done that and had to format the whole hard disk after the first update. Thank you for nothing.
FWIW I have run Linux on nearly all of my systems at home for many many years, using mostly the Debian distro, and no issues.? It runs a lot faster and far more stable than the one Windows 10 system I have left for gaming.
?
Not sure what you are referring to by "one of the free GUIs that sit on top of Linux".? The major Linux distros include a graphical desktop by default.? Do a standard installation and the graphical desktop works out of the box, nothing else to add.
?
|
Kaufman, Matt - N3AR
Si Smith
Richard Dyer
Dj Merrill