Hi Tim the only down side I have found of not adding it is . . . If you go into the CONFIG menu and click okay (even just for a look and make no changes) when you come out WSJT-X will flip to the closest defined frequency in the list for that mode. In my case I found this when working EME on 50.190 MHz I went in to look at my decoder settings and then clicked OK. I did not realise I had been QSY'd to be on 50.276 MHz for some minutes and wondered where the signals had gone too.
Regards, Peter VK5PJ On Thu, Jun 20, 2019 at 9:33 AM Tim Goeppinger via wsjt-devel < [email protected]> wrote: > I remember back a year ago when we did tests of DXpedition mode, I entered > the > DXpedition frequency into the list for the software. I think it was 14090 > KHZ, > > Since then DXpeditions have done their operating on frequencies all over > the digital subbands, > and I got tired of adding their frequency to the list each time. One time > I decided to spin my dial > to the frequency without entering it to the list. The DXpedition mode > worked great - it did all the > QSYing within the audio spectrum to make the DX QSO, and the frequency > logged just fine. I have > been spinning the dial without frequency entry ever since. > > Fast forward to this month for Field Day where I am heading up the FT8 For > Field Day group in Facebook. We have a separate list of frequencies to > use, so that we don't disrupt normal FT8 activity. > Many of our members are busy entering these frequencies to their list. My > opinion is that they do not > need to do this. Am I wrong, and am I leading them astray? What is the > down-side of operating on a frequency that is not on the list? > > Thanks & 73, > > Tim N6GP > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
