Hi Bill,
Thank you very much for this thoughtful explanation regarding band changes in
WSJT-X.As I mentioned, I instructed Rich to update their document to change to
6M before selecting MSK144.I will update my program so that if it detects a
frequency lower than 6M, my program will update the frequency box.50.260 Thanks
again.
73,
Sam W2JDB
-----Original Message-----
From: Bill Somerville <g4...@classdesign.com>
To: wsjt-devel@lists.sourceforge.net
Sent: Wed, Sep 2, 2020 7:18 am
Subject: Re: [wsjt-devel] Bug when using MSK144?
On 01/09/2020 23:56, Sam W2JDB via wsjt-devel wrote:
Hi Bill,
First let me apologize. The message you received from me was intended for
Rich. Fat fingers and some senility. In any event, maybe I can explain it
better or at least I hope I can.
When WSJT-X is using FT8 or FT4 on any of the lower HF band, i.e 160-10 and
the user selects MSK144 as the new mode, the band frequency box populates with
the appropriate new frequencies 6M, 2M and 70cm. The Band selection box select
6M but WSJT-X does not issue a CAT command to change the Rig. On the other
hand, If I was using FT8 or FT4 on 6M and then selected MSK144, WSJT-X
populates the correct frequencies (6M, 2M, 70cm) in the band box, selects 6M
and issues the CAT command to change the rig frequency to 50.260 from the
previous frequency. In addition, should I then select 2M, WSJT-X,
appropriately issues the CAT command to my rig (TS590S which does not have 2M),
and then correctly reverts the band box back selection to 6M, as it should.
The problem that Rich was trying to identify is that for a blind ham changing
the mode from FT8 or FT4 while on the lower bands, they would end up on the
incorrect band.
Programmatically I could try to take care of this problem by moving the focus
to the band box and typing in 6M, but doing it manually as a test resulted in a
change of frequency to 50.200 instead of 50.260.
What I also found is that until the CAT command is issued, there is no UDP
(Status Record) traffic indicating the change in either mode or frequency.
Since you end up on the wrong band, there not would be anything to decode
either.
For now, I instructed Rich to document and inform the blind hams to move to
6M before selecting MSK144 as that seems to work.
Hopefully this is a slightly better explanation.
Again my apologies for all the confusion this may have caused, and I want to
thank you and Joe for your support for the blind ham community.
73,
Sam W2JDB
Hi Sam and Rich, as far as I can see there is one minor cosmetic issue here,
that is the edit field of the band/frequency drop-down combo box can end up
showing a band (wavelength) that is incorrect when a mode is selected for which
there is no working frequency defined for the current band and region. That is
cosmetic because the band name is a derived field that has no functional
significance, the main frequency display in Hertz is the important field as
that determines the frequency the rig is on if CAT controlled (modulo
transverter offsets), and also the Rx frequency logged in completed QSOs. The
other issues you report are only because you are giving that band field more
significance that it deserves. The UDP messages sent indicate the correct mode
and frequency, and I cannot fault them for indicating changes. For the next
release I have fixed the minor defect that allows the band name to be
incorrect, it will become blank, or indicate to the band of the displayed
frequency. The simple advice is that WSJT-X does not ever change the band
unless you either change band on a CAT connected rig, select a frequency from
the main window drop-down list of working frequencies for the current mode and
region combination, enter a band name or frequency in MHz into the edit field
of that same drop-down combo box, or indirectly by starting WSJT-X configured
to return to the last used frequency, switching to a new configuration
configured to return to the last used frequency, or re-enabling "Monitor" when
WSJT-X is configured to return to the last used frequency. I.e. changing mode
never has and will never change the operating band.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
