Any chance of having the CW id run concurrently with a data packet, perhaps at fDial + 100 Hz or so? It'd meet the id requirement without interfering with QSOs.
> On Jul 5, 2017, at 14:42, Gary McDuffie <mcduf...@ag0n.net> wrote: > > >> On Jul 4, 2017, at 12:56 PM, Steve Huston <hus...@srhuston.net> wrote: >> >> I did notice that having "CW ID after 73" turned on didn't work well >> in that mode - I would get W2 out before it would change to the next >> part of the sequence and stop. I unchecked it for now. > > Since it takes 13.4 something seconds just to send the data package out one > time, that only leaves about 1.5 seconds for your ID, not including turnover > time. Just turn it off. If the period were extended to finish the ID, you > would not decode the other station on the next turnover because you would > miss quite a bit of the early part of the data from him. > > At least that is my understanding of the facts. Someone please correct me if > I’m wrong. New to the group. > > Gary-AG0N > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
