Maybe I've missed the point on this thread, but since WSJT-X is only a USB
signal why can't we keep it simple and report/log just the Rx dial frequency?
That then avoids complicated and maybe unknown Tx offset and split
calculations, with other people being able to find the Tx easily also
without mathematical gymnastics?
The position of the tones in the passband isn't relevant as they will be
within the Rx filter bandwidth?
Alan G0TLK, sent from my mobile device
On 30 July 2024 15:05:54 Hasan N0AN via wsjt-devel
<wsjt-devel@lists.sourceforge.net> wrote:
Mike,
Tnx clarification, 73 N0AN
On Tue, Jul 30, 2024, 8:21 AM Black Michael <mdblac...@yahoo.com> wrote:
There's a difference between the cluster spotting system and pskreporter.
Cluster spotting includes CW for example (and primarily too) where you need
to know the carrier frequency and you have your own custom offset tone.
FT8-type modes are notably different. On the cluster spotting you will
generally see the suppressed carrier frequency on on pskreporter the actual
transmitted frequency.
They serve two different purposes and anybody doing analysis or looking for
where a call sign actually is needs to know the offset for using things
like notch filters and such.
And this discussion is only about changing the VFO on the rig instead of
WSJT-X and detecting/reporting the real frequency.
Mike W9MDB
On Tuesday, July 30, 2024 at 08:03:29 AM CDT, Hasan N0AN via wsjt-devel
<wsjt-devel@lists.sourceforge.net> wrote:
The problem with adding the DF offset is when the frequency is
published/spotted, (like on QRZ or DXSummit), it is listed as
14.09175..which is NOT the frequency that you need your radio tuned to for
CAT control. If you click on a spot and have CAT control, you will be on
the wrong freq.
In the other method, (without DF offset), the frequency is spotted as
14.091, the radio is tuned to 14.091 if you click on the spot, and you can
see the signal (sync Fo) on 750 Hz (SuperFox).
So for computer control, it is much better to not include the offset in the
frequency in the spot...so you don't have to do math in your head or guess
at the offsets, for your vfo to be set to the proper freq.
73, N0AN
Hasan
On Tue, Jul 30, 2024 at 3:56 AM Reino Talarmo via wsjt-devel
<wsjt-devel@lists.sourceforge.net> wrote:
My humble opinion is that the reported frequency should be sum of the
frequency display and the waterfall frequency. That’s in case those are
really what is actually transmitted. Joe’s case is a bit different and in
that sense a selection may be needed.
73, Reino OH3mA
From: Black Michael via wsjt-devel <wsjt-devel@lists.sourceforge.net> Sent:
Monday, July 29, 2024 8:58 PMTo: wsjt-devel@lists.sourceforge.net; Andy
Durbin <a.dur...@msn.com>Cc: Black Michael <mdblac...@yahoo.com>Subject:
Re: [wsjt-devel] ALL.TXT RX freq is not RX DIAL freq
That value is meant to only change during band change to avoid messing up
typing into the freq box. It's only used in the one place.
Unless Joe has some other observation it doesn't appear to me that this
change harms anything. Making it an option just means nobody will know to
use it to avoid the problem. And we've had plenty of reports of
pskreporter things being wrong which we've already done some work on to
minimize errors. It's pretty critical that pskreporter spots are correct
for any number of reasons.
Mike W9MDB
On Monday, July 29, 2024 at 12:50:03 PM CDT, Andy Durbin <a.dur...@msn.com>
wrote:
Mike,
Thanks for looking at this.
I intentionally proposed an option because Joe had indicated there were
reasons it was implemented to use table frequency rather than current dial
frequency.
By implementing as an option those who like the way it works now would see
no change.
I documented a more extreme case than had been in included in draft 2.
With no frequency table loaded I tuned a spot collector CW spot at
21.011900. I couldn't hear the spot so I used rig conrols to set USB mode
and 21.074000. PSK Reporter showed all the stations I decoded as offsets
from 21.011900!
e.g.
Dial frequency 21.074
All.txt decode 240728_174145 21.012 Rx FT8 -12 -0.8 1465 BD4WVQ K4JOM
EM60
PSK Reporter showed K4JOM received at 21.013.365
73,
Andy, k3wyc
________________________________
From: Black Michael <mdblac...@yahoo.com>
Sent: Monday, July 29, 2024 10:34 AM
To: wsjt-devel@lists.sourceforge.net <wsjt-devel@lists.sourceforge.net>
Cc: Andy Durbin <a.dur...@msn.com>
Subject: Re: [wsjt-devel] ALL.TXT RX freq is not RX DIAL freq
This small change fixes the problem.
Adding this outside the if clause ensures it is updated with current
information...
m_freqNominalPeriod = m_freqNominal;
Although we should probably not do pskreporter when the frequency changes
like this as we aren't sure which frequency was decoded.
Mike W9MDB
void MainWindow::displayDialFrequency ()
{
if (ui->actionUse_Dark_Style->isChecked())
ui->bandComboBox->setStyleSheet("QLineEdit {background-color: #31363b}");
// initialize dark style at startup
Frequency dial_frequency {m_rigState.ptt () && m_rigState.split () ?
m_rigState.tx_frequency () : m_rigState.frequency ()};
// lookup band
auto const& band_name = m_config.bands ()->find (dial_frequency);
m_freqNominalPeriod = m_freqNominal;
if (m_lastBand != band_name)
On Sunday, July 28, 2024 at 11:55:46 AM CDT, Andy Durbin via wsjt-devel
<wsjt-devel@lists.sourceforge.net> wrote:
"What rig do you have that WSJT-X does not follow rig freq changes?
Mike W9MDB"
I have no such rig. WSJT-X follows my rig frequency with 1 Hz resolution
as indicated in the draft paper.
The issue is not that WSJT-X does not follow the rig frequency. The issue
is that WSJT-X knows the rig frequency but may report a different frequency
to ALL.TXT and PSK Reporter.
Would you please read the full draft and let me know if any part needs
clarification.
Thanks and 73,
Andy, k3wyc
_______________________________________________wsjt-devel mailing
listwsjt-devel@lists.sourceforge.nethttps://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
_______________________________________________
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
