hamlib-developer

[Hamlib-developer] Pull Request: Fix AI regression and new option rigctl to skip AI restpre

[Bill S. <g4...@cl...>]

Hi All,

if/when c177ef is merged to stable then a924165 from this pull request 
should join it.


The following changes since commit ca77efcc04736e8d3fa59d4d6420615081f26e93:

   Allow for poor emulations of Kenwood rigs that have no ID command 
(2015-11-29 20:56:42 +0000)

are available in the git repository at:

   git://git.code.sf.net/u/bsomervi/hamlib kenwood-ai-restore

for you to fetch changes up to aebe52a45e11b816267ac9ba83acedd35c0430da:

   Add a new command line option '--no-restore-ai' ('-n') to rigctl 
(2015-12-04 00:22:01 +0000)

----------------------------------------------------------------
Bill Somerville (2):
       Use correct function to execute set  type commands with no response
       Add a new command line option '--no-restore-ai' ('-n') to rigctl

  doc/utility_programs.texi |  6 ++++++
  include/hamlib/rig.h      |  1 +
  kenwood/kenwood.c         | 11 ++++-------
  src/misc.c                |  6 ++++++
  src/misc.h                |  4 ++++
  tests/rigctl.1            |  5 +++++
  tests/rigctl.c            |  7 ++++++-
  yaesu/newcat.c            |  3 ++-
  8 files changed, 34 insertions(+), 9 deletions(-)

73
Bill
G4WJS.

Re: [Hamlib-developer] Pull Request: Fix AI regression and new option rigctl to skip AI restpre

[Bill S. <g4...@cl...>]

On 04/12/2015 03:33, Nate Bargmann wrote:
> Will this command line option need to be applied to rigctld as well?
Hi Nate,

I don't believe it is necessary for rigctld. rigctld will restore AI 
mode which seems fine in all cases. Do you see a user case where rigctld 
would be used to just change the AI state? I would have thought if that 
were needed then when rigctld exits one could send:

   $ rigctl <normal-options> --no-restore-ai A ON

to enable AI mode after exiting rigctld.

73
Bill
G4WJS.

Re: [Hamlib-developer] Pull Request: Fix AI regression and new option rigctl to skip AI restpre

[Nate B. <n0...@n0...>]

* On 2015 04 Dec 05:59 -0600, Bill Somerville wrote:
> On 04/12/2015 03:33, Nate Bargmann wrote:
> > Will this command line option need to be applied to rigctld as well?
> Hi Nate,
> 
> I don't believe it is necessary for rigctld. rigctld will restore AI 
> mode which seems fine in all cases. Do you see a user case where rigctld 
> would be used to just change the AI state?

Off-hand, no.  Everyone is creative, however!  ;-)

> I would have thought if that were needed then when rigctld exits one
> could send:
> 
>    $ rigctl <normal-options> --no-restore-ai A ON
> 
> to enable AI mode after exiting rigctld.

Works for me.  Leave it as-is until and unless someone presents a use
case for adding the option.

73, Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us