"maybe your CAT serial baud rate is too low for this delay to encompass the first poll. Can you increase your CAT serial baud rate?"
Bill, COM port baud is 38,400. I doubt the baud is the cause of the problem. Thanks for confirming this check was in earlier versions. That is significant because I found no evidence of this test in my controller log prior to yesterday morning when I started using ver 2.1.0. I think that shows this version of WSJT-X does not behave the same as earlier versions. I'm using the 64 bit version because the only reason for making the update was to get the faster decode processing. I currently have no interest in FT4. I just noticed that ver 2.1.0 runs this test each it starts but ver 2.0.1 does not seem to. I ran a test series in which I started ver 2.1.0 , checked my controller log, stopped ver 2.1.0, started ver 2.0.1, checked controller log , repeat 4 times. Each time ver 2.1.0 was started my controller log shows it changed VFO A. The controller log shows no activity when ver 2.0.1 is started. Typical log for ver 2.1.0 start: 119:06:46.683 New IF - IF00007074055 004100005020010000; 119:06:46.695 New FA - FA00007074055; 119:06:46.697 New RX freq=7074055 119:06:46.700 split offset = 445 119:06:47.330 New IF - IF00007074000 004100005020010000; 119:06:47.343 New FA - FA00007074000; 119:06:47.345 New RX freq=7074000 119:06:47.346 split offset = 500 I'll try the 32 bit version later in the day but I see no reason to use it instead of 2.0.1 32 bit. 73, Andy, k3wyc
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
