Re: CW Practice / Rag Chew
Martin, Thanks for the note. Maybe next time the conditions will be better and we will be able to have a QSO. Ed
toggle quoted message
Show quoted text
heard nr Hamburg 439 just over my local noise floor on the QMX
?
73's
Martin
DK3UW
|
qmx SSB Firmware beta 1_01_004 release + WSJT-X
Hello ...
After installing 004, successfully, I've got 3 new com ports, 3, 9, & 10.
All of them allow CAT control of the WSJT software.
Decodes are happening and I have made a number of US and DX contacts today.
But, and there almost always is one, after about 8-10 minutes, the new com ports "go away" and WSJT stops working and wants connections repaired.
Shutting off the QMX+ and turning it back on restores the ports, for another 8-10 minutes.
?
Anybody else seen this behavior after updating to 004ssb?
The radio plays nicely with WSJT for hours at a time with 003ssb.
Thanks,
Dick, K5AND
|
Re: QMX+ with WA3TFS amplifier
Another excellent idea, Jim. If I can¡¯t find those special TRS jacks, I¡¯ll do exactly that !
?
Thanks much !
?
73, Jamie
WB4YDL
|
Thank you for the description, Ludwig, I now understand how the controller input may be limiting this voltage.? For some reason I wasn't thinking about it correctly.
So there probably isn't a problem with this part of the circuit.
Stan KC7XE
|
Stan, sorry my text was a bit short.
VDD for the controller was round 3.0V. With the higher 3.3V at ADC_3V3 the difference from ADC_3V3 to VDD is 0.3V, maybe limited by an internal protection diode. And by the current via this protection the voltage was pulled to 3.3V, around 7.3V across R112.
?
73 Ludwig
|
Yes, Ludwig, I forgot about the possible effect of the A/D input.
the voltage difference 3.3V - 3.0V = 0.3V looks like from a protection
But the measurement he stated at Q111 was 10.6V and 3.3V on ADC_3V3, so the difference would be?
5.3V - 3.3V = 2.0V, which I don't think would happen from the A/D input.??
Or maybe I misunderstood his measurements.
Stan KC7XE
|
Release 1_01_004 bugs that did not get addressed
Two issues that I have reported before are not fixed in 1_01_004 and that is OK. I just wanted to make note that I had tested them and the bugs, as expected, are still there:
?
1. With VFO B selected, SWR sweeps do not sweep.
2. Attempting FT8 with USB mode results in only one transmit cycle. After the first transmit cycle, subsequent transmit cycles produce no power. This has been confirmed by at least one other user.
?
Tony
AD0VC
|
Re: #qmx SSB Firmware beta 1_01_004 release
#qmx
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
?
|
Re: QMX build troubleshooting
It can¡¯t have failed open circuit as the 12v rail was being shorted to ground. You can check that it is working by looking at TX voltage on the diagnostic screen. It should show 0V in RX and slightly less than Vin on TX.
Always a good plan to stop when you are tired, it¡¯s easy to make a mistake and undo all the good work. Hopefully that was the only issue. Glad to have been of assistance.?
73 Nick G0OQK
|
Hello Allan & Hans
Thank you for taking the time to reply. I can see from the group messages that you have a few other irons in the fire!
My interest in the QDX-M is in building a few for our radio group to allow (encourage) experimentation with the FSQ protocol and NVIS propagation. The QDX-M makes an ideal, cheap, dedicated radio, which together with a laptop computer make an ideal field station.
I understand that some experimentation might be necessary to set up the band/low pass filters and I have some equipment here to do that sort of thing. My understanding of band selection is that it is done in firmware after getting the radio going.
So my crunch point is: Can I order a QDX-M with two sets of toroids, caps, and wire etc to proceed with the build? I can source them locally but it would be neater to get one box with all the bits. We're well out in the "bush" and everything happens by on-line order anyway.
Thanks again and I hope all is progressing well with the SSB project.
Best regards
Richard VK2EIK
QF69al
|
Re: #qmx SSB Firmware beta 1_01_004 release
#qmx
|
Re: #qmx SSB Firmware beta 1_01_004 release
#qmx
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
|
Re: #qmx SSB Firmware beta 1_01_004 release
#qmx
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?
|
Re: #qmx SSB Firmware beta 1_01_004 release
#qmx
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
|
Re: #qmx SSB Firmware beta 1_01_004 release
#qmx
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
|
Re: #qmx SSB Firmware beta 1_01_004 release
#qmx
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
|
Re: #qmx SSB Firmware beta 1_01_004 release
#qmx
On Wed, Apr 23, 2025 at 10:15 PM, Hans Summers wrote:
then I could make this feature configurable,
Hello Hans, thanks for the quick response. Exactly this came in my mind but I didn't know about the effort.
And it looks like a thing of old Win7. Changing between a QMX with FW03 and one with FW04 the same COM-Port is available for both, but useable only for the QMX with FW03. For the QMX with FW04 the COM-Port is shown by the device manager as ok. But when I try to use it I get an error message.
?
73 Ludwig
|
QRP Labs QMX-PLUS-CW/SSB/FT8-NRV to be activated during ARRL Field Day 2025 with new club call sign
Please see:
72,
Bill, N4QA//QRP on the mountain in Roanoke County, Virginia.
|
Re: QMX+ with WA3TFS amplifier
Jamie: oops, I mixed up C17 and C16.? What I should have said was that as another PTT option, you could add a SPDT switch.? The switch common is connected to R6/C17 junction (with that leg of C17 lifted).? One switch direction would connect the R6/C17 junction to the PTT-P signal (from QMX, ring of TRS) and the other direction would connect the lifted leg of C17 for RF detection.
?
I don't even have Percocet for an excuse!
--
73,
Jim - AE5JE
|
Re: #qmx SSB Firmware beta 1_01_004 release
#qmx
Hans,
I use a mid 2011 21.5" Mac running OS10.13.6 High Sierra.
Using "Terminal" I have operated, at various?times, ?two QDX's and a U4B and all 3 are identified as /dev/tty.usbmodemFDxxx ? xxx has always been the same number.
I hope this is of some help.
Thanks for all your hard work, I can hardly wait for the BASIC scripting to be available on the QMX(+).
72 John M0JBA
On Wed, 23 Apr 2025 at 20:52, Kaufman, Matt - N3AR via <matt.d.kaufman= [email protected]> wrote:
Good afternoon, Hans -
First - incredible work on this.? There don't seem to be
many folks left that are putting out and fully supporting complex
kits the way that you are, and I can absolutely say that I've
learned quite a bit about soldering (and some about electronics
troubleshooting) from your kits.? Now that I've buttered you up,
here's my question - 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.
Thanks!
73
-- Matt N3AR
On 4/23/2025 11:25 AM, Hans Summers via
wrote:
More info on USB naming, I just checked again the way QMX
does it.?
I attached a screenshot of my?/dev/serial/by-id directory.
There are three devices, named by their "Interface ID", which
are 00, 02 and 08. I could change that so that they are called
00, 01 and 02. The bit which is namable in QDX is the part
that says "QMX_Transceiver" here (and in QDX, by default, is
QDX_Transceiver).?
In WSJT-X or your terminal emulator, you would be able to
specify the port name as, for example:
/dev/serial/by-id/usb-QRP_Labs_QMX_Transceiver-if00
Now this will never change. The other device in the
screenshot is my STLink programmer I use to flash the code
into the QMX.?
So this is why it's useful. On Linux the port naming is
according to when you plug things in (or switch them on). My
plugged in ST programmer therefore has name /dev/ttyACM0 and
then the three QMX ports would become /dev/ttyACM1, 2 and 3.
The issue is that if the ST programer wasn't plugged in then
the QMX ports would be named ttyACM0, 1 and 2. But if you
enter the name as above, in the by-id device folder, then it
never changes regardless of whether there's an ST programmer
or any other kind of serial device attached.?
I recall the original point of this was that people might
connect multiple QDX to their PC. Then they could name them
"QDX-Hi" and "QDX-Lo" for example, if they connected an 80-20m
QDX and a 20-10m QDX. That will happen on QMX too, it's the
QMX which gets a unique name, so if you had multiple QMX they
could be identified. But the unique naming of the port is
already possible (Linux).?
MacOSX and Linux share common roots in UNIX. But I know
nothing about Mac stuff and whether any of this might be
applicable. I'd be happy to make any of the parameters in the
USB device description configurable as well as the product
name, if it helps - but I think this is a question first for a
Mac OSX expert, which I'm not.
On Wed, Apr 23, 2025 at
9:03?PM Hans Summers via
<hans.summers= [email protected]>
wrote:
The solution is simple, upgrade to Linux, Jan.
Maybe not, Diarmuid... we don't even know that Mac
doesn't do it yet...?
|
Dick Hanson
Si Smith
Kaufman, Matt - N3AR
Bill, N4QA/QRP
AE5JE - Jim