[Top][All Lists]

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

Re: [Tlf-devel] Upload tlf-0.9.20

From: Rein Couperus
Subject: Re: [Tlf-devel] Upload tlf-0.9.20
Date: Wed, 21 Jul 2004 13:56:21 +0200
User-agent: KMail/1.5.4

O.k., another try....

O.K., I managed to test it with the K2, and found 2 bugs. The new test version 
I cannot test the implicit set_bandwidth facility, as the K2 driver in hamlib 
does not support it. Now at least the routine sees the bandwidth entered into 
the logcfg.dat and refuses to execute if CWBANDWIDTH=0, as tested on the K2.

I also think the Kenwood backend should not set the default cw bandwidth to 50 
Hz. This is a Hamlib problem.

73, Rein Pa0R

On Tuesday 20 July 2004 19:18, Joop Stakenborg wrote:
> Rein Couperus wrote:
> > - Added test version of CWBANDWIDTH=xxx to set bandwidth from Hamlib when
> > mode is switched:
> >     A value of 0 to switch off automatic mode switching (demanded by PG4I)
> >     A value of x for setting the bandwidth with the mode
> >     If the parameteer is not there, PASSBAND_NORMAL is used (default)
> > This parameter works for cw only, I will add the same for SSB if this one
> > works. As I have no rig that can do this via Hamlib (the ORION has a
> > native driver), maybe somebody can test this (what say, Joop?).
> Nope, don't work.
> No matter what I use for a number xxx for CWBANDWIDTH=xxx, the rig
> always switches to 50 Hz width. Omitting CWBANDWIDTH uses 50 Hz, but
> this may be a kenwood backend failure. Using 0 (zero) to turn it off,
> does not work, still switches to 50 Hz.
> Can anyone else confirm if this is working or not? I have been reading
> the source code, but can't find anything odd....
> > 73,
> >
> > Rein Pa0R
> Regards,
> Joop PG4I

address@hidden or address@hidden

reply via email to

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