The K3 can apparently be quite slow when switching bands and such.
I recently saw a 3.5 second timeout was not long enough.
So bump up your timeout value to 5000 and see if the problems disappear.
de Mike W9MDB
On Friday, May 11, 2018, 9:26:12 AM CDT, Claude Frantz
<claude.fra...@bayern-mail.de> wrote:
On 05/10/2018 10:21 PM, Sherman Banks wrote:
Hi Sherman & All,
> Trying to control a K3. The most common error is
> Hamlib error: Protocol error while opening connection to rig
> But I have seen one related to the VFO but that doesn’t happen as often.
> I have the Timeout at 3000 and polling at 5 seconds and it happens
> rarely now. Hopefully it will be rare during the next contest. I’m not
> sure it is timeout at this point since I have it so high by changing the
> value in hamlib_settings.json per
I ignore if this can help you a little bit, but here are the settings
used by fldigi, in the case of the K3:
<TIMEOUT>50</TIMEOUT>
<RETRIES>2</RETRIES>
<WRITE_DELAY>5</WRITE_DELAY>
<BAUDRATE>38400</BAUDRATE>
<RTSCTS>false</RTSCTS>
<ECHO>false</ECHO>
<STOPBITS>1</STOPBITS>
Best wishes,
Claude (DJ0OT)
------------------------------------------------------------------------------
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
