Tlf and WAG contest - how to handle mults?
Multipliers in WAG contest is first letter in received DOK exchange (typically letter plus two numbers). How to track and register multipliers in WAG contest? As far as I understand tlf, mults can be based on exchange, but how to handle parts of exchange is a mystery to me. Associated mult list may be used as an alternative. 73 de Olaf LA3RK
Re: Using hamlib for CW keying
I now have my K3 working with keying without any additional boxes like netkeyer, winkeyer or similar. Solution is fairly simple; 1. Install cwdaemon. Standard install uses parallell port for keying so to use eg a serial port you have to modify cwdaemon config file (resided in /etc/default). Had to set ttyS0 instead of parport0. cwdaemon seems to start on boot with the standard debian install. So to get cwdaemon to use serial port you need to restart; sudo service cwdaemon restart 2. Rig is controlled over same serial port. This seems to work fine as the rig communication only uses txd and rxd lines. But there is a catch. My standard install of hamlib triggered both dtr and rts lines and keyed the rig unless rigctld command was changed. To avoid this you need to ask hamlib to clear both the dtr and the rts lines. This can be done by giving rigctld the following options in addition; -C rts_state=OFF -C dtr_state=OFF. 3. On the K3 you need to enter the config menu and set the PTT-KEY entry to OFF-dtr. It seems the cwdaemon keying goes over the dtr line. If you want cwdaemon to control the ptt line, you would probably set this to rts-dtr. Not necessary with a K3 as it provides full break-in. The above works both with tlf and with cqrlog which is used for my main logging. And this solution fully accepts all speed change commands and tx stops from keyboard as it does not utilize the K3 internal keyer. So by this I have no need for tlf (or cqrlog) to use keying via hamlib as long as I use my K3. But my KX3 does not allow for keying via the dtr line so the solution will not work unless the dtr signal is routed via a transistor to the KX3 key input. A solution which can be used for most rigs I assume. So all in all, I do not have to prepare a nanokeyer/winkeyer or similar extra box. Thanks for responses which triggered me into finding a practical solution. PS: Have not tried this on a usb-serial converter, my serial port is a "real" serial port based on an UART 16550. But I note some usb-serial devices has brought out the dtr line, and I would assume that this can be made to work also on these. 73 de Olaf - LA3RK
Re: Using hamlib for CW keying
Keying my K3 via hamlib works nicely. But there are some problems, one is that Hamlib used a simplified control setup based on Kenwood protocol and not fully includes all possibilities in the Elecraft protocol. By checking the actual commands between pc and rig it is apparent that keying is done by KY command, not the Elecraft KYW command. The difference between the two is that KYW blocks further commands while buffer is emptied, fine if you want to change key speed at a certain point. To enable speed changes in text would then necessitate changes in the backend hamlib and as someone pointed out solution will probably differ from rig to rig. Therefore implementing speed changes within a cw string will be difficult using hamlib. However, for simple cases like just sending text strings, use of hamlib would make life simpler. Ie not another box with associated cables. Fine for the casual contester. Keying of a string from the pc can be stopped by sending ^D (pg 15 in K3/KX3 programmers reference) character or just pushing a paddle lever assuming paddle is connected to rig. I would welcome such addition to tlf. Alternative would be to set up nanokeyer, winkeyer or similar, but again, this is basically a box that is unneeded with my K3 or for that matter my KX3. 73 de Olaf - LA3RK
Re: [Tlf-devel] K3 and tlf - resets bw when changing bands
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 t...@forth-ev.de To: olaf.de...@mollefaret.no Cc: tlf-devel@nongnu.org Sent: 11.8.'12, 20:31 Hi Olaf, Am Sat, 11 Aug 2012 08:55:05 +0200 schrieb Olaf Devik olaf.de...@mollefaret.no: 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 ___ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
Re: [Tlf-devel] Tlf 1.2.0 do not find hamlib
Thanks for reply. Issue was solved by compiling hamlib then tlf. The hamlib installation I had followed as a package when I installed cqrlog. Never tried ldconfig though. I do not know if that would have solved the issue. Tlf 1.2 more and less up and running for the WAEDC contest. Still some other issues, see other posts. 73 de Olaf - LA3RK On 08/11/2012 06:46 PM, Bob Nielsen wrote: On Aug 10, 2012, at 7:08 AM, Olaf Devik olaf.de...@mollefaret.no wrote: I have hamlib installed and running ok with cwrlog and by checking rigctl. When setting up tlf fir compiling. /configure --enable-hamlib it claims hamlib can not be found. Compiling wo hamlib works ok. I need rigcontrol. What to do? Mvh Olaf Devik It is working for me (xubuntu 12.04). Perhaps tlf is not in your library path. This can be resolved using ldconfig. 73, Bob N7XY _ Licensed since 1952 N7XY DX Cluster Node - telnet to n7xy.net, port 7300 ___ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
[Tlf-devel] TLF - cwdaemon stops working
I seem to have a weird problem with cwdaemon. Cwdaemon is installed as part of cqrlogger and when checking I can find that cwdaemon is running. Before tlf or cqrlog is started I can check the cwdaemon via nc -u localhost 6789 - which keys the rig as planned. When starting tlf, tlf reports that netkeyer is started with setup as for the previous check. But there is no keying, neither from keyboard or via macros. A recheck with nc -u localhost 6789 is then unsuccessful - no keying - no error messages - but ps -A reports cwdaemon as a running process. Any tips/suggestions? I have had this working in earlier versions of tlf and under ubuntu 11.10. PC is now on ubuntu 12.04. 73 de Olaf - LA3RK ___ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
[Tlf-devel] Tlf 1.2.0 do not find hamlib
I have hamlib installed and running ok with cwrlog and by checking rigctl. When setting up tlf fir compiling. /configure --enable-hamlib it claims hamlib can not be found. Compiling wo hamlib works ok. I need rigcontrol. What to do? Mvh Olaf Devik ___ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
[Tlf-devel] TLF 1.0.0. pre4 crashes
Just as a sidenote. I am currently using TLF 1.0.0pre04, compiled on Ubuntu 10.04. Tlf compiles ok, but at least my version still crashes from time to time. I am not sure what provokes this, but my last crash was reported as follows: *** buffer overflow detected ***: tlf terminated TRX: 7022.2 ┌─Spots=== Backtrace: = │ 1813.6 DR4A 2257Z│ /lib/libc.so.6(__fortify_fail+0x50)[0x1f5980]ZZ 2256Z│ │ 3793.0 LZ/lib/libc.so.6(+0xe487a)[0x1f487a] │ 1814.8 UR8IDX 2257Z│ /lib/libc.so.6(+0xe3d8e)[0x1f3d8e]│18084.0 ZL7A 2256Z│ tlf[0x8063a4f]SM3TLG 2257Z│ │ tlf[0x8061d4d]│ │ tlf[0x806206e] └───┘ /lib/libpthread.so.0(+0x5cc9)[0xaa8cc9] /lib/libc.so.6(clone+0x5e)[0x1e06ae] === Memory map: 0011-00267000 r-xp 08:01 66037 /lib/libc-2.12.1.so 00267000-00268000 ---p 00157000 08:01 66037 /lib/libc-2.12.1.so 00268000-0026a000 r--p 00157000 08:01 66037 /lib/libc-2.12.1.so 0026a000-0026b000 rw-p 00159000 08:01 66037 /lib/libc-2.12.1.so 0026b000-0026e000 rw-p 00:00 0 0026e000-0027 r-xp 08:01 66026 /lib/libdl-2.12.1.so 0027-00271000 r--p 1000 08:01 66026 /lib/libdl-2.12.1.so 00271000-00272000 rw-p 2000 08:01 66026 /lib/libdl-2.12.1.so 00438000-0043e000 r-xp 08:01 65610 /lib/libusb-0.1.so.4.4.4 0043e000-0043f000 r--p 5000 08:01 65610 /lib/libusb-0.1.so.4.4.4 0043f000-00441000 rw-p 6000 08:01 65610 /lib/libusb-0.1.so.4.4.4 00606000-0061e000 r-xp 08:01 331467 /usr/lib/hamlib-kenwood.so 0061e000-0061f000 ---p 00018000 08:01 331467 /usr/lib/hamlib-kenwood.so 0061f000-0064d000 r--p 00018000 08:01 331467 /usr/lib/hamlib-kenwood.so 0064d000-0064e000 rw-p 00046000 08:01 331467 /usr/lib/hamlib-kenwood.so 007a-007a7000 r-xp 08:01 331734 /usr/lib/libltdl.so.7.2.1 007a7000-007a8000 r--p 6000 08:01 331734 /usr/lib/libltdl.so.7.2.1 007a8000-007a9000 rw-p 7000 08:01 331734 /usr/lib/libltdl.so.7.2.1 0083d000-00852000 r-xp 08:01 331059 /usr/lib/libhamlib.so.2.0.12 00852000-00853000 ---p 00015000 08:01 331059 /usr/lib/libhamlib.so.2.0.12 00853000-00854000 r--p 00015000 08:01 331059 /usr/lib/libhamlib.so.2.0.12 00854000-00855000 rw-p 00016000 08:01 331059 /usr/lib/libhamlib.so.2.0.12 00a0c000-00a42000 r-xp 08:01 65803 /lib/libncurses.so.5.7 00a42000-00a44000 r--p 00035000 08:01 65803 /lib/libncurses.so.5.7 00a44000-00a45000 rw-p 00037000 08:01 65803 /lib/libncurses.so.5.7 00aa3000-00ab8000 r-xp 08:01 66038 /lib/libpthread-2.12.1.so 00ab8000-00ab9000 ---p 00015000 08:01 66038 /lib/libpthread-2.12.1.so 00ab9000-00aba000 r--p 00015000 08:01 66038 /lib/libpthread-2.12.1.so 00aba000-00abb000 rw-p 00016000 08:01 66038 /lib/libpthread-2.12.1.so 00abb000-00abd000 rw-p 00:00 0 00b83000-00b9d000 r-xp 08:01 65711 /lib/libgcc_s.so.1 00b9d000-00b9e000 r--p 00019000 08:01 65711 /lib/libgcc_s.so.1 00b9e000-00b9f000 rw-p 0001a000 08:01 65711 /lib/libgcc_s.so.1 00c2c000-00c5 r-xp 08:01 66035 /lib/libm-2.12.1.so 00c5-00c51000 r--p 00023000 08:01 66035 /lib/libm-2.12.1.so 00c51000-00c52000 rw-p 00024000 08:01 66035 /lib/libm-2.12.1.so 00d8e000-00d8f000 r-xp 00:00 0 [vdso] 00fbc000-00fd8000 r-xp 08:01 66014 /lib/ld-2.12.1.so 00fd8000-00fd9000 r--p 0001b000 08:01 66014 /lib/ld-2.12.1.so 00fd9000-00fda000 rw-p 0001c000 08:01 66014 /lib/ld-2.12.1.so 08048000-08085000 r-xp 08:01 401435 /usr/local/bin/tlf 08085000-08086000 r--p 0003c000 08:01 401435 /usr/local/bin/tlf 08086000-08088000 rw-p 0003d000 08:01 401435 /usr/local/bin/tlf 08088000-08418000 rw-p 00:00 0 0861c000-0863d000 rw-p 00:00 0 [heap] b6757000-b6758000 ---p 00:00 0 b6758000-b6f58000 rw-p 00:00 0 b6f58000-b6f59000 ---p 00:00 0 b6f59000-b775c000 rw-p 00:00 0 b7771000-b7773000 rw-p 00:00 0 bfb41000-bfb56000 rw-p 00:00 0 [stack] Aborted Sorry for the bad formatting, but this is as the crash is reported on my system at least. I am not able to open the list so there may be a later version out with corrections. Just for your info, it is just to restart tlf after a crash and sofar I have not lost anything in my logs. 73 de Olaf LA3RK ___ Tlf-devel mailing list Tlf-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/tlf-devel
[Tlf-devel] TLF update?
All My copy of tlf has stopped working on my newly updated kubuntu machine. I note some discussion on patches, but the last version I can find is 0.9.30. Is there an updated version somewhere which I can use? Would very much get this in order for the upcoming tests. 73 de Olaf LA3RK Olaf Devik Email: olaf.de...@mollefaret.no Mob: +47 91170849 ___ Tlf-devel mailing list Tlf-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/tlf-devel
