I just wonder...
We did qso on 144.150 (qsy by vfo knob). After qso I moved back to
144.174 that is saved to wsjtx/frequencies.
Because wsjtx sends heard calls to pskreporter as a "block" time to time
I think the sending happened after our qso when I was again back on 144.174
I just wonder
Try the latest hamlib
New hamlib for installation directions
#1 Shut down WSJTX
#2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of
WSJTX -- hopefully your browser doesn't block it but may warn you multiple
times.
If you can do a "Save As" you can save it
Saku,
My experience has been that pskreporter displays the frequency as received by
the receiving station. So, this would be display frequency plus the audio
frequency used for the qso.
Sometimes the two are not the same, for instance, your transmit frequency and
that of the other station
I noticed today for the K3 if a band on the radio is set to DATA_REV (MD9), the
mode is not changed to DATA (MD6) when changing bands like it is if the mode is
any other setting. Looks like Mode 6 or 9 are considered accepted. Is this
intentional? I would think DATA (MD6;) should always be
Hi!
I worked a local qso on 144.150 using FT8 (that was displayed on WSJT-X
frequency reading)
Afterwards I looked at pskreporter where both our calls were reported on
144.175
I.E. frequency that was stored WSJT-X band quick settings (144.174) +
audio frequency.
Now question is:
Does
