Joe, A couple of things on the auto sequencer....
1. I was calling CQ and W3ZUP answered me while I had the auto sequencer enable. I would not expect the auto sequencer to do anything in that instance (I do not respond automatically to CQ replies with what I did with ISCAT) When W3ZUP answered the auto sequencer jumped to TX1 but without updating the call so still had call from last QSO. 2. I double clicked on W3ZUP to get his call into the next messages. My next decoded was of both W3ZUP calling me and of KB7IJ calling W3ZUP. The auto sequencer changed the call to KB7IJ and moved me back to TX1 calling him. It is my thought that the auto sequencer should not answer CQs nor should it be changing the DX Call. I was quite surprised to see the double decode as they were right on top of each other. They were very similar in signal strength. Just curious if it would be possible to have variants of JT9G and H with the same bandwidth but with the nsps dropped down into the 12 (or so) range so t_msg is short enough to accommodate meteor scatter on 144 and 222? I understand the s/n advantage would drop accordingly but pings, especially on 222, tend to be strong but very short. Thank you for all the work Joe, much appreciated. 73 de Bill ND0B ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
