green heron rt-21 time outs

[jmeloranta]

For the most part green heron rt-21 works fine. However, I occasionally get time out and then I have to re-enable the rotor in qlog. I have changed the min speed setting on the controller to 9 and that helps a bit. At least the controller is no longer getting upset but qlog still gets time out. Is there any setting that could increase the timeout?

[aa5sh]

I experience the same thing at times. hamlib - rotctl is throwing those errors. They typically define soft vs hard errors. QLog suppresses the soft errors but will give the message and disconnect on the hard errors. I'm not sure what is going on with rotctl giving those errors, it's something with hamlib but I looked there and don't really see anything. So I'm not sure of the proper resolution.

[jmeloranta]

I think with small values for min speed around 5 I was seeing time out + the green heron controller getting up set as well (no motion flashing). Then increasing the value improved the situation. The controller no longer gets upset but qlog still reports occasionally time out. My guess is that the rotor controller is just slow to respond at times and this leads to this issue. I would imagine that it is possible to change the time out value somehow in hamlib?

[aa5sh]

Ok I actually just found a way to pass a longer timeout to the rotor from within QLog. I will test it some and it seems better I put in a pull request to extend it.

token_t timeout_token = rot_token_lookup(rot, "timeout");
if (timeout_token != -RIG_EINVAL) {
    int ret = rot_set_conf(rot, timeout_token, "2500");
    if (ret == RIG_OK) {
        qWarning() << "Rotator timeout set to 2500ms";
    } else {
        qWarning() << "rot_set_conf(timeout) failed:" << rigerror(ret);
    }
} else {
    qWarning() << "timeout token not found";
}

[jmeloranta]

If it is generic to all rotators then perhaps make it eventually user adjustable?