|
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.?
|
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.?
|
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.?
|
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.?
|
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.?
|
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.?
|
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!
|
This _007 release fixes all 3 COM ports on my fully-patched Win10-home edition.
Thank you!
Stan KC7XE.
|
Hello Hans,
?
you are quick!
?
Maybe not a USB problem?
?
73 Ludwig
|
Hi Hans,
i can confirm, the connection/driver issue with Windows 11 and the 3 serial ports is solved with Version 1_01_007.?
Thank you very much, that was quick!
--
Moritz, KO6DZX
|
On Sat, Apr 26, 2025 at 07:43 PM, @Ludwig_DH8WN wrote:
?
73 Ludwig
|
Beta 07 works fine with Win 10. All three COM ports can be enabled.
Not so with Win 8. It sees only two ports no matter will one choose 2 or 3 in QMX menu. And there are no CAT control in WJST-X or JS8-Call with Win 8. The same was right for Beta 04.
With Win 10 there is still the problem with WinLink/VARA USB audio from PC to QMX. As far as I see it is very weak. That is why QMX doesn't transmit anything. There is no such problem with WJST-X or JS8-Call. So it is somehow connected with VARA communication with QMX. So in WinLink I have to fulfill TX using loudspeakers of PC.
Hans, can you please try Winlink/VARA on your PC under Win 10?
?
BR/Sergey
|
playing around with the LC; CAT command.... if there are "." on the cw decoder, the LC command does not display them.?? Instead of outputting 32 characters you get less and less the more periods that are added:
LCA1404110P ? ? RT ED ARTEKA * E;
LCA1404110P ? ? T ED ARTEKA * EN;
LCA1404110P ? ? T ED ARTEKA * EN;
LCA1404110P ? ? D ARTEKA * EN ?;
LCA1404110P ? ? ARTEKA * EN ?EN;
LCA1404110P ? ? RTEKA * EN ?ENE;
LCA1404110P ? ? RTEKA * EN ?ENE;
LCA1404110P ? ? EKA * EN ?ENE ;
LCA1404110P ? ? EKA * EN ?ENE ;
LCA1404110P ? ? A * EN ?ENE ?;
LCA1404110P ? ? A * EN ?ENE ?;
LCA1404110P ? ? * EN ?ENE ? ;
LCA1404110P ? ? * EN ?ENE ? ;
LCA1404110P ? ? EN ?ENE ? ?;
|
Beta 07 works fine with Win 10. All three COM ports can be enabled.
Not so with Win 8. It sees only two ports no matter will one choose 2 or 3 in QMX menu. And there are no CAT control in WJST-X or JS8-Call with Win 8. The same was right for Beta 04.
With Win 10 there is still the problem with WinLink/VARA USB audio from PC to QMX. As far as I see it is very weak. That is why QMX doesn't transmit anything. There is no such problem with WJST-X or JS8-Call. So it is somehow connected with VARA communication with QMX. So in WinLink I have to fulfill TX using loudspeakers of PC.
Hans, can you please try Winlink/VARA on your PC under Win 10?
I could... but, it would take unnecessary time, and, I believe you!
I suppose VARA just isn't putting out full volume. QMX in SSB mode is set up so that full volume from the PC means full PEP output power. That works for JS8 and WSJT-X because they have?the gain slider on the bottom left and when it's at the topmost position, it's full output volume. On QMX I get numbers from the USB sound card in the range -2^23 to?+2^23 (as WSJT-X and JS8 output 16-bit audio in the range -32768 to?+ 32767 and the PC sound system multiplies that by 256 in its conversion to 24-bit to interface to the QMX USB soundcard).?
I can very easily put in a simple gain block in the USB signal path when USB is selected as the source for SSB transmission.?
|
playing around with the LC; CAT command.... if there are "." on the cw decoder, the LC command does not display them.?? Instead of outputting 32 characters you get less and less the more periods that are added:
Yes, unforeseen side-effect of the way CAT is implemented. in QMX the thousands separator can be set to ',' (UK/US/etc style) or '.' (European/etc style) by a setting. CAT replies ignore any character that is a , always as well as any character which is the thousands separator. You?must have set your thousands separator to '.' and that's why it is being ignored. If you set your thousands separator to ',' then you'd get the CW decoded ',''s coming through - but nothing would ever get you the ',''s.?
The reason it was done this way is that many CAT commands, to comply with the TS480 CAT specification, are just the numbers; like FA; which returns the frequency in Hz without any thousands separators at all.?
I will fix it for LC; in the next firmware...?
|
I'll also confirm that _007 is working on Windows 10 Home with my QMX+.. I can see 3 COM ports, COM8 (the original one), COM 22 and COM23. Also see the audio ports. I ran the full SSB Cal. on COM23, and all seemed to complete normally, with similar looking curves (except 160m, as expected). Now I am seeing good SSB output power on the QMX+ display. Haven't tried any real operation yet.
Tnx Hans!
73, Randy, KS4L
|
I've checked out 1_01_007 on my Intel iMac running MacOS 15.4.1. ?When all 3 serial ports enabled, they appear as
/dev/cu.usbmodem1414101
/dev/tty.usbmodem1414101
/dev/cu.usbmodem1414106
/dev/tty.usbmodem1414106
/dev/cu.usbmodem1414108
/dev/tty.usbmodem1414108
?
I can run WSJT-X with any of them for CAT. ?I can also run a serial terminal in parallel using the command line plus screen command. ?However I have found that in order to run both the serial terminal and WSJT-X in parallel, I have to start up WSJT-X first. ?If I start up the serial terminal first, then WSJT-X won't communicate via CAT. ?I also have found that I have to reboot the QMX before WSJT-X will communicate if I made the mistake of starting up the serial terminal first. ?Hope this is useful information.
?
73
?
Paul
M1CNK
|
On Sat, Apr 26, 2025 at 01:56 PM, Paul Wilton wrote:
I have found that in order to run both the serial terminal and WSJT-X in parallel, I have to start up WSJT-X first. ?If I start up the serial terminal first, then WSJT-X won't communicate via CAT.
Interesting, Paul.? That does not happen on my Win10 machine; any process can use any of three ports in any order.? If I start WSJT-x second, I just have to change it to the second or third port, since it will by default try to use the prior port which is now occupied.? Maybe your issue is Mac specific.
Stan KC7XE
|
I reran the calibration routines with 1_01_007 on my high band QMX. ? The results mostly mirrored the results I got with 1_01_003 with the exception of 10m USB sync where I got a straight line at 60000 - see below
?
When I had run it under 1_01_003 I got a valley shaped graph and a figure of 40
?
73
?
Paul
M1CNK
|
On Sat, Apr 26, 2025 at 03:00 PM, Hans Summers wrote:
Yes, unforeseen side-effect of the way CAT is implemented. in QMX the thousands separator can be set to ',' (UK/US/etc style) or '.' (European/etc style) by a setting. CAT replies ignore any character that is a , always as well as any character which is the thousands separator. You?must have set your thousands separator to '.' and that's why it is being ignored. If you set your thousands separator to ',' then you'd get the CW decoded ',''s coming through - but nothing would ever get you the ',''s.?
Thanks Hans, I had wondered if it was related to the frequency. Your explanation makes sense. ? I wanted to note that I have experienced that both "," and "." are omitted in the CAT response no matter what separator you choose.?? I am working on a python script that parses the LC cat responses and can output various things that might be useful for logging. ? Thank you!
|
Richard Dyer
Dick Hanson
Randy