Re: [Tlf-devel] K3 and tlf - resets bw when changing bands

[Olaf Devik]

Thanks for info. Will set default bw as pr your suggestion.

As to operating system story is as follows:

1 Had kubuntu 10.10 working with tlf all ok.
2 Updated to kubuntu 12.04 after a number of network connection issues. Did 
a clean new install.
3 Installed cqrlog which installs the hamlib package and uses both cwdaemon 
and rigctld. All ok.
4 Downloaded tlf 1.2. Compiling with. /configure --enable-hamlib failed. 
Did not find hamlib. Tried autoconf. Did not help.
5 Removed package hamlib - which also removed cqrlog - unwanted sideeffect.
6 Downloaded hamlib source. Compiled.
7 Compiled tlf 1.2 with --enable-hamlib. All ok. Rig control working via 
rigctld.
8 Reinstalled cqrlog ok with rigctld. Both can be open and have rig grg. 
Fine.
9 Checked cwdaemon with nc -u localhost 6789 rig keying ok. Tlf claims 
cwdaemon ok. But no keying neither from macros nor keyboard. Keying from 
cqrlog not ok. Recheck with nc -u does not function anymore. Tlf or cwrlog 
problem?
10 Function keys in tlf do not work eg F1 gives A in input field.
11 Tlf 1.2 works ok as logging tool but all keying done manually.

Any tips? If you need it I can reset to give you output from . /configure.

73 de LA3RK

Mvh
Olaf Devik

------- Original message -------
> From: Thomas Beierlein <address@hidden>
> To: address@hidden
> Cc: address@hidden
> Sent: 11.8.'12,  20:31
>
> Hi Olaf,
>
> Am Sat, 11 Aug 2012 08:55:05 +0200
> schrieb Olaf Devik <address@hidden>:
>
> > My K3 combined with tlf/hamlib reads frequency/mode nicely both into
> > cqrlog and to tlf and if necessary simultaneously by use of rigctld
> > daemon. Some hassle to set up as I had to compile hamlib from source,
> > the standard install were not found by tlf unless hamlib was compiled.
> >
> > My question is as follows, why do the K3 return to a wide bandwidth
> > every time I change bands or turn the vfo outside the bandlimits -
> > this only happens when the k3 is communicating with tlf. There seems
> > to some builtin logic that overrides the bw and resets the bw to
> > approx 1000 hz every time I change  band. Is there some logic built
> > into tlf or is this a hamlib issue?
> That is done by tlf intentional. Every time you change band it reset
> the bandwidth to the 'default' value, which is coded inside hamlib
> (Seems for your K3 that default is set to 1000 Hz).
>
> You can overide the default bandwidth setting with
>
> 'CWBANDWIDTH=xxx'
>
> in logcfg.dat where xxx is one of the supported bandwidth settings of
> your K3.
>
>
> Wrt to the need to self compile hamlib: Which operating system and
> hamlib version did you try before? Did you install also the
> development headers (hamlib-dev packacke or similar) before?
> Some Linux systems split the headers out from the library package.
>
> It would be good if you can try building tlf again without the self
> compiled hamlib and send me the output of the ./configure command.
>
>
> 73, Tom DL1JBE