tlf-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Tlf-devel] Fw: Few modifications in Tlf core


From: Thomas Beierlein
Subject: [Tlf-devel] Fw: Few modifications in Tlf core
Date: Tue, 31 Dec 2013 12:53:17 +0100

Sorry forgot to send it to the list. 

Here it comes...

Datum: Tue, 31 Dec 2013 12:22:00 +0100
Von: Thomas Beierlein <address@hidden>
An: Ervin Hegedüs - HA2OS <address@hidden>
Betreff: Re: [Tlf-devel] Few modifications in Tlf core


Hi Ervin,

let us keep the scoring aside for a minute and look for the rig problem
first....

Am Mon, 30 Dec 2013 20:58:54 +0100
schrieb Ervin Hegedüs - HA2OS <address@hidden>:
> 
> > > * getting TRX freq
> > >   may be this isn't Tlf "bug", rather it affects the Hamlib. That
> > > would be very good if anybody could to test it. My TRX is a
> > > Kenwood TS-850SAT, it has 2 VFO. When I start the Tlf, it reads
> > > the current freq from TRX, and shows it. If I switch the another
> > >   VFO, Tlf doesn't follow that, still shows the freq of another
> > >   VFO, which was the current when Tlf started.
> > > 
> > >   Now I modified the source, Tlf always get the actually VFO,
> > >   which really the current in TRX, and get that freq.
> > > 
> > Very well. That was on my todo list for some time also but not with
> > priority. I will pick it up for the master branch shortly.
> 
> thanks,
>  
> > By the way did you find out why VFO_CURR did not use the current vfo
> > but the one who was active when tlf started?
> 
> no, I didn't found - I've tried it with a standalone source, I
> test it only this feature, but my rig produced this result.
> 
> Therefore I asked you (Tlf users), please check this on other
> rigs. May be it's a hamlib bug, but first we have to check with
> others.

I had a look into hamlib. I do not think it is a bug, but a
misunderstanding from our side how RIG_VFO_CURR works.

It remembers the last set/get vfo from the rig. So you are correct that
we need to poll for the actual vfo periodically. But we do not need to
use that vfo afterwards because hamlib remebers it itself as
RIG_VFO_CURR.

I picked only the rig_get_vfo calls from your changes and that is
enough to work like a charme. See my last commit on the master branch
and retest. Thanks for the help.

73, de Tom DL1JBE


-- 
"Do what is needful!"
Ursula LeGuin: Earthsea
--



-- 
"Do what is needful!"
Ursula LeGuin: Earthsea
--




reply via email to

[Prev in Thread] Current Thread [Next in Thread]