Hi guys,
Thank you for the clarification. I now understand that I must place a
non-standard frequency such as 14.091 in the drop down list in order to
post the correct frequency. If I decide to re-enable spots I won't use
the radio knob.
73,
Fred WX1S
On 3/3/2025 3:14 AM, Reino Talarmo via wsjt-devel wrote:
Scott, thanks a lot for spotting this for me.
Now it is very clear to me, and I want to share that information with
all of you (again):
“As things are presently coded, retuning your rig with front panel
controls (the "big knob") does NOT change the nominal frequency that
you have selected from the drop-down list. That's the frequency that
will be written to ALL.TXT and posted to PSK Reporter, etc.
One reason this can make sense is that you want to be on 14.074 MHz, say
-- or perhaps on 1296.065 MHz, for EME -- but you know that on that
band your dial calibration is off by -220 Hz. So, you select 14.074
in the drop-down list and then tweak the dial by the necessary +220 Hz.
Everything will then be recorded and posted correctly.
If you want to be on 14.091 and have things recorded and posted as
14.091, type "14.091" into the drop-down control. Better still, put
14.091 into your frequencies list. If you're already on 20 meters,
say 14.074, you can type "91k" (for kHz) into the drop-down list.
-- 73, Joe, K1JT”
I see that it would be a challenge to make a fail-safe code that
allows VFO turning in all cases to set the base frequency. Perhaps a
new confirmation window would be needed stating e.g. “Do you want to
use the new indicated frequency as the base frequency?” each time you
turn VFO. I don’t want to start that discussion again unless someone
it willing to code it and “all” frequency control situations are
clearly defined on the user point of view.
To me the typing of the frequency into the drop-down control for a
temporary change or an additional entry to the frequency list for a
more permanent selection option is good enough.
73, Reino OH3mA
*From:*Scott Armstrong via wsjt-devel <wsjt-devel@lists.sourceforge.net>
*Sent:* Monday, March 3, 2025 2:38 AM
*To:* WSJT software development <wsjt-devel@lists.sourceforge.net>
*Cc:* Scott Armstrong <aa5am.sc...@gmail.com>
*Subject:* Re: [wsjt-devel] Frequency Reporting Anomaly WSJT and FT8/FT4
Reino,
Took a bit to find this one...
I think the thread you are referring to is this one "ALL.TXT RX freq
is not RX DIAL freq" from July 2024.
73,
Scott AA5AM
On Sun, Mar 2, 2025 at 4:06 PM Reino Talarmo via wsjt-devel
<wsjt-devel@lists.sourceforge.net> wrote:
Fred,
From some earlier discussion on this behavior, I got feeling that
the program is designed in that manner. The to be reported
frequency needs to be set by wsjt-x not by VFO. I am not familiar
enough to tell the reason for that behavior, but a proposed change
was rejected at that time. I am not sure whether the discussion
was on this mail-list, but most probably.
73, Reino OH3mA
_______________________________________________
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
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
