Hi Mike,
are we dealing with a long wait for the TCP/IP connection to close down?
IIRC if the client end initiates the shutdown of a TCP/IP connection
there should be minimum delay. rig_close() will have been called before
rig_open() is called again on the same RIG handle.
73
Bill
G4WJS.
On 23/04/2020 22:20, Black Michael via wsjt-devel wrote:
Actually I just repeated it. Has to do with the timeout.....using
rigctld....or any network-based rig.
So if the rig takes too long to respond...then you get the
timeout...the rig wakes up again...you click the Retry and get invalid
configuration because the rig is till open.
You may be able to duplicate this by turning off your rig, wait for
the timeout, and turn it back on, then click Retry.
de Mike W9MDB
On Thursday, April 23, 2020, 04:10:51 PM CDT, Black Michael via
wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote:
Don't have any more details than the error message of invalid
configuration.
I've seen it on my system too once in a while but never repeatable of
course.
I think it may have to do with WSJT-X opening a 2nd connection without
closing the 1st connection as I saw some of that in recent debug logs.
I do notice that do_start does not ensure that the rig is closed
int HamlibTransceiver::do_start ()
{
TRACE_CAT ("HamlibTransceiver",
QString::fromLatin1 (rig_->caps->mfg_name).trimmed ()
<< QString::fromLatin1 (rig_->caps->model_name).trimmed ());
error_check (rig_open (rig_.data ()), tr ("opening connection to rig"));
Mike
On Thursday, April 23, 2020, 02:40:48 PM CDT, Bill Somerville
<g4...@classdesign.com> wrote:
On 23/04/2020 20:15, Black Michael via wsjt-devel wrote:
> And sometimes doing retry will give a configuration error too which
> requires a restart of WSJT-X...also undesirable.
>
> Mike
Hi Mike,
that's the first report of that, can you supply more details please?
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
