Disable set_ptt confirmation logic. Seems many rigs can't deal with it.

https://github.com/Hamlib/Hamlib/issues/623
pull/649/head
Michael Black W9MDB 2021-03-20 16:57:46 -05:00
rodzic 1fdbebd7b2
commit ae3fef1e0c
1 zmienionych plików z 8 dodań i 1 usunięć

Wyświetl plik

@ -2641,6 +2641,7 @@ int HAMLIB_API rig_set_ptt(RIG *rig, vfo_t vfo, ptt_t ptt)
if (retcode != RIG_OK) { RETURNFUNC(retcode); }
#if 0
hl_usleep(50 * 1000); // give PTT a chance to do it's thing
// don't use the cached value and check to see if it worked
@ -2656,8 +2657,10 @@ int HAMLIB_API rig_set_ptt(RIG *rig, vfo_t vfo, ptt_t ptt)
rigerror(retcode));
retcode = RIG_OK; // fake the retcode so we retry
}
if (tptt != ptt) { rig_debug(RIG_DEBUG_WARN, "%s: failed, retry=%d\n", __func__, retry); }
#else
tptt = ptt;
#endif
}
while (tptt != ptt && retry-- > 0 && retcode == RIG_OK);
}
@ -2685,9 +2688,13 @@ int HAMLIB_API rig_set_ptt(RIG *rig, vfo_t vfo, ptt_t ptt)
if (retcode != RIG_OK) { RETURNFUNC(retcode); }
#if 0
retcode = rig_get_ptt(rig, vfo, &tptt);
if (tptt != ptt) { rig_debug(RIG_DEBUG_WARN, "%s: failed, retry=%d\n", __func__, retry); }
#else
tptt = ptt;
#endif
}
while (tptt != ptt && retry-- > 0 && retcode == RIG_OK);