Add retry mechanism for Yaesu "newcat" backend

Przeglądaj źródła

After some  testing with an  FT-450 it is  apparent that Yaesu  use at
least some of the busy/invalid  CAT responses that Kenwood document in
their current CAT protocol. The  response received from the FT-450 was
a "?;" from occasional "IF;" commands. In the Kenwood World this means
that  the  command  cannot  be   processed,  this  could  mean  it  is
unrecognized  or it  could  be  a transient  condition  while the  rig
processor is busy. The Kenwood backend  has the ability to retry after
this and some other error responses.

Since the  Kenwood error  response codes are  unambigous in  the Yaesu
language this change implements a  similar protocol for Yaesu "newcat"
backends.  Each  backend may  choose how many  reties by  defining the
'retry' parameter in the rig capabilities structure.

Also cleaned up a lot of code duplication.

Hamlib-3.0

Bill Somerville 2014-10-12 17:02:24 +01:00

rodzic bff3a044eb

commit 3ad5f0c653

1 zmienionych plików z 255 dodań i 759 usunięć

Pokaż wszystkie zmiany Ignoruj znaki białe przy porównywaniu linii Ignoruj zmiany w ilości znaków białych Ignoruj zmiany w znakach białych przy EOL

Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

1014

yaesu/newcat.c

Wyświetl plik

Plik diff jest za duży Load Diff