Re: [Hamlib-developer] Re: compile

[<rs...@su...>]

On Thu, 25 Oct 2001, Stephane Fillod wrote:

> Be careful, rpcrig is rather shallow right now. There's only rig_set_freq
> and reading caps is not implemented yet (you would get anything but
> expected values).

OK, it was only an example. I am testing here by switching from one device
to another. Maybe I should leave out all alpha-state devices.

> > #3  <signal handler called>
> > #4  0x413ab2f1 in rpcrig_close (rig=0x8110810) at rpcrig_backend.c:170
> > #5  0x4002b06c in rig_close (rig=0x8110810) at rig.c:497
> > #6  0x4001b4b3 in Rig::close (this=0x812e308) at rigclass.cc:70
>
> Maybe related to the double close issue? Or is it peculiar to some backends?
> Could you try again with the new fix?

Only certain backends (such as the rpc rig) still crash on close() without
an open(). Still happens here with the new version.

> > Then I am trying to figure out which radio modes (AM, ...) are currently
> > available. I suppose I will have to parse the freq_range_list array. But
> > still one thing shouldn't happen: Select FT847, Kontakt finds out
> > "everything except WFM is ok". Then select RTTY -> RigException. Every

>    very simple, RIG_MODE_WFM is not declared in caps :*)

Of course, but this is not the problem. This button gets correctly
disabled (that's why I wrote "everything except WFM is ok").

>    Anyone has protocol specs handy? Frank?

Yes, me. The FT847 protocol supports LSB, USB, CW, CW-R, AM, FM, CW(N),
CW-R(N), AM(N), FM(N).


> RTTY is not supported (yet) by ft847_set_mode. BTW, is this mode
> available on the rig?

Not explicitely, but a myRig->caps->tx_range_list2[something].modes &
RIG_MODE_RTTY returned true, otherwise this button would not have been
available and no RigException would have been produced. Does the backend
internally note the last set frequency somehow? That might cause this
problem here. I still have to work on the detection of available modes.

> > Now rig_close (+ft847_close) is called twice, it seems.
>
> good point! rig_close was missing a rig->state.comm_state update...
> I've commited a fix, it should now be safe to call rig_close() twice.

This is fixed now.

73, Robert
-- 
Robert Steinhaeusser, DL1NC / N9KBK                         rs...@su...
http://1409.org                                   ro...@st...