Re: [Hamlib-developer] RIG_TRN

[Stephane F. <f4...@fr...>]

On Mon, Jun 24, 2002, Dale E. Edmons wrote:
[...]
> Here's how it looks to me:
>         1) somebody enables exception handling and the backend
>         sends the autoinformation on via myrig_set_trn().  (Is the
>         trn parameter like FILE, or RIG?)

Please, try reserving the "exception" word for C++. 
trn is an on/off parameter. Please see rig_set_trn() comments in src/rig.c

>         2) somewhere (I forget where) in rig.c signal exception
>         handling is enabled and the myrig_decode() is installed
>         as the handler.  (Is myrig_decode() supposed to read
>         and decode/parse all incoming commands from the
>         rig?  What is done with the information?)

yes. information is decoded in 3)

>         3) An exception occurs and myrig_decode() is called, which
>         calls myrig_transaction() to read the command. (?)  Now we
>         have the actual command that came from the rig and caused
>         an exception, we decode it to find out what command it it.
>         Now what do we do with it???

myrig_decode then calls the installed callback, if any.
see icom/icom.c: icom_decode_event() for an example

>         4) myrig_decode() returns and the code in rig.c handles all
>         of the messy cleanup etc.

what cleanup are you talking about?

> The big question is in 3).  Taking the most common example from
> the ts2k "sm...;" which gives us the current meter value.  This
> command comes it, we determine it is a particular "op code"
> "sm", it has two parmaters, Sub/Main, and Value.  These are
> easily parsed.  Where do we send the data or what do we do with it?

So far, there's no "meter_changed" event. There's only callbacks for 
freq,mode,vfo,ptt and dcd. Before adding any new ones, please tell me
what events do you want to track.

> Is a previous myrig_transaction() on the stack waiting for
> any response from the rig, which we provide?  I don't know of
> a place in RIG where current values are kept (except vfo_curr).

sorry, I don't understand your question.



Cheers,
Stephane