Hi Mike,
I wonder if the retry count could be reset after a successful connection.
73 Alan M0NNB
On Mon, Jul 12, 2021 at 5:06 PM Alan Hopper
wrote:
> Hi Mike,
> this is with WSJT-X connecting to the fake rigctld in SparkSDR. It
> connects and then if a delay happens some time later (hours in re
I assume you're compiling hamlib -- so change netrigctl.c on this line
.timeout = 3000, /* enough for the worst rig we have */
Make that 5000 or higher and see if that makes it happy. I may change that to
1 as that is now the worst rig we have.
.timeout = 5000, /* enough for the worst
Hi Mike,
this is with WSJT-X connecting to the fake rigctld in SparkSDR. It
connects and then if a delay happens some time later (hours in real use) it
will reconnect again but if the delay happens again it does not retry.
Maybe be retry was planned for the initial connect? For long running
connec
It should be trying to reconnect twice with 3 second timeout each time.
What rig are you using? You could increase the timeout value by adding a
switch to rigctld
rigctld --set-conf=timeout=1
You could also try increasing the retry in rigctld.c from 3 to maybe 4 or 5 and
see if that makes
Hi all,
I've been doing some testing to try and make the hamlib NET rigctl
connection to SparkSDR as robust as possible. Very infrequently (maybe once
in 24hrs) responses from spark are delayed by a few seconds, This causes a
time out at the WSJT-X side which then auto reconnects which is great,
ho
