toggle quoted messageShow quoted text
your point #2 is not quite correct, it
doesn't care what the mode other than it must be one that is
expected, i.e. within the set of valid modes.
This was a simple coding error in
MacLoggerDX which has been fixed, I suggest we move on.
On 03/11/2021 13:59, Michael Black via
Do I not understand
Mode=None in WJST-X then?
I thought it meant two
#1 WSJT-X makes no attempt
to set mode
#2 WSJT-X makes no read of
mode (or shouldn't care).
Is one of those assumptions
On Wednesday, November 3, 2021, 08:54:11 AM CDT, Bill
not correct. If an application emulates another
application then it should do so accurately, if it
doesn't then a client can't be expected to behave
exactly as it does for the original application. This
issue has been resolved by a minor change in
MacLoggerDX to improve the DX Lab Suite Commander
emulation it provides.
03/11/2021 13:45, Michael Black via groups.io wrote:
If you set mode to None you can
do whatever you want on the rig.
On Wednesday, November 3, 2021, 01:10:15
AM CDT, Frank, DH4FR <frank.klop@...>
One final question regarding modes:
Is it an error for WSJT-X when the mode on
the rig is not set to USB-D? And how is
this impacted by the "Mode" setting on the
For example, will WSJT-X throw an error
when I switch mode to FM or LSB on the rig
while WSJT-X is actively controlling the
rig and mode is set to "None"?