I see that's a default freq in the code. So the message is getting sent out before it's been set. Perhaps the message should be ignored until the frequency is set. 73 Mike W9MDB <https://www.avast.com/?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> This email has been sent from a virus-free computer protected by Avast. www.avast.com <https://www.avast.com/?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Sat, Nov 21, 2015 at 4:40 PM, Steven Franke <s.j.fra...@icloud.com> wrote: > Hi Mike > > On Nov 21, 2015, at 4:36 PM, Michael Black <mdblac...@gmail.com> wrote: > > > > Testing the new udp_dameon I saw this on starting up WSJT-X > > Discovered WSJT-X instance: WSJT-X > > WSJT-X: Dial frequency changed to 18446744073709551615 > > WSJT-X: Dial frequency changed to 21076000 > > > > Is that a bug in the daemon or WSJT-X sending a bogus message? > > > > I see this too, only on startup. I believe that this is an initialization > issue in wsjt-x. Only happens on the very first “Dial frequency changed” > message here. > > Steve k9an > > > > ------------------------------------------------------------------------------ > _______________________________________________ > 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
