On 18/07/2019 13:43, Andy Durbin wrote:
My controller log search found no instances of this test before the
time I started using ver 2.1.0. Can you please confirm that this
test was not executed in ver 2.0.1.
73,
Andy, k3wyc
Andy,
the test has been in for many versions including v2.0.1. As I said, it
is just an indication that the CAT interface is being reinitialized,
that will be due to an unrecoverable error. The most likely error is
that Omni-Rig is reporting the rig has gone off-line.
Alex VE3NEA has reported that WSJT-X is not waiting for the first poll
by Omni-Rig and is therefore not getting the correct VFO frequency, i.e.
the starting point for the resolution test, that would explain why the
frequency is not being set back where it was before the test starts.
Unfortunately the procedure Alex recommended to ensure that Omni-Rig has
completed the first frequency poll of the rig does not work for all
rigs. I did introduce a brute force delay to try and combat this, 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?
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
