Re: [Tlf-devel] TLF-1.3.1 early pre release

[Ervin Hegedüs]

On Mon, Oct 01, 2018 at 06:32:54AM +0200, Thomas Beierlein wrote:
> Am Sat, 29 Sep 2018 23:17:55 +0200 schrieb Ervin Hegedüs <address@hidden>:
> 
> > Hi Thomas,
> ...
> > I just sat down to RIG since one hour ago, and tried to made some
> > RTTY QSO's, testing the new version.
> > 
> > * when the callsign filled from Fldigi, the COUNTRY and ZONE in
> >   bottom border or Worked window is wrong; that shows always
> >   the last QSO info
> > * sometimes the CQ zone filled with _that_ value, not the CQ zone
> >   of current CALL
> > * the BMAUTOADD doesn't works; I moved away with click in Fldigi
> >   waterfall to the next signal, Tlf calculates the new FREQ, and
> >   tune VFO, may be it defines...
> > 
> Hmm, that sounds not so good after all.
> 
> The first two problems may be connected to the change from Stephen to
> enable the use of the cty.dat files from CT9. I checked it working, but
> must admit only for CW.

I think I've found source of all problems, and doesn't connect to
Stephan's patch. The Fldigi fills the callsign, and there missed
some extra function call in first two issues.

The third issue occured because the bmautoadd worked only when
user types the callsign, the Fldigi callsign set was ignored.
I've fixed it too.

There is a plus minor issue: in fldigixmlrpc.c Tlf sets the RIG's
VFO based on its mode and the Fldigi's carrier. Those values are
differs, eg: when OP uses USB or LSB, we need to calculate as
other way the accurate freq. I didn't know about RTTY-REV, so
I've wrote the code that calculate freq as same way than LSB/USB.

At this weekend I could work with a K3 in FSK mode, and
checked RTTY-REV mode, but the calc was wrong: always tune the
VFO to another direction. The first commit fixes this issue.


> I will look into the patches you provided in meantime.

right, thanks.
 
> P.S. Please note that I will be away most of the week, so responses
> from me may be late.

thanks for info,


73, Ervin