Re: CWdaemon
/dev/ttyUSB0 maybe? Check the device file. dmesg will tell you if nothing else. Does cwdaemon have a verbose flag to turn on debugging messages? On Thu, Jul 14, 2022 at 10:44 PM Ed wrote: > > New install of Fedora36, I used the repository for TLF and cwdaemon. > > I copied my TLF contests from my backup. > > Now I cannot get cwdaemon to work, I use this to start it:: > > cwdaemon -d ttyUSB0 -x n > > Suggestions or ideas ? > > Thanks > > Ed W3NR >
Re: CWdaemon
Use the debug option and have a look at the error. -- finger painting on glass is an inexact art - apologies for any errors in this scra^Hibble ()/)/)() ..ASCII for Onno.. On Fri, 15 July 2022, 06:44 Ed, wrote: > New install of Fedora36, I used the repository for TLF and cwdaemon. > > I copied my TLF contests from my backup. > > Now I cannot get cwdaemon to work, I use this to start it:: > > cwdaemon -d ttyUSB0 -x n > > Suggestions or ideas ? > > Thanks > > Ed W3NR > >
CWdaemon
New install of Fedora36, I used the repository for TLF and cwdaemon. I copied my TLF contests from my backup. Now I cannot get cwdaemon to work, I use this to start it:: cwdaemon -d ttyUSB0 -x n Suggestions or ideas ? Thanks Ed W3NR
cwdaemon
I finally remembered how to start it on boot. /etc/default Edit the file as root to point it to USB0 (in my case). Works just as years past. Just took a while for the bulb to come on. Ed W3NR
Re: cwdaemon
SOLVED: installed cwdaemon version 0.11.0 and added the key=DTR option: cwdaemon -d ttyUSB1 -n -xn -o key=DTR -i Now it sends cw ok. 73 de Zilvis LY2SS On Sun, May 1, 2022 at 7:33 PM Žilvinas Atkočiūnas < zilvinas.atkociu...@gmail.com> wrote: > Hi all, > > Could somebody help me with this please? > I run cwdaemon (0.10.2) with these options: "cwdaemon -d ttyUSB1 -n -xn > -iii" > It keys the FT991a rig OK when I issue characters via netcat: > > cwdaemon -d ttyUSB1 -n -xn -iii > cwdaemon: Not forking... > debug output: stdout > Press ^C to quit > cwdaemon:II: setting sound system "Null" > cwdaemon:II: starting generator with sound system "Null": success > cwdaemon:II: --- > cwdaemon:II: request: "?" > cwdaemon:II: Morse character "?" to be queued in libcw > cwdaemon:DD: Morse character "?" has been queued in libcw > cwdaemon:II: keying event "1" > cwdaemon:II: keying event "0" > cwdaemon:II: keying event "1" > cwdaemon:II: keying event "0" > cwdaemon:II: keying event "1" > cwdaemon:II: keying event "0" > cwdaemon:II: keying event "1" > cwdaemon:II: keying event "0" > cwdaemon:II: keying event "1" > cwdaemon:II: keying event "0" > cwdaemon:II: keying event "1" > cwdaemon:II: low TQ callback: start, TQ len = 1, PTT flag = 0x00/ame > cwdaemon:II: low TQ callback: branch 3, PTT flag = 0x00/ame > cwdaemon:II: low TQ callback: end, TQ len = 1, PTT flag = 0x00/ame > cwdaemon:II: keying event "0" > cwdaemon:II: --- > > But when I try to send cw via tlf (master branch from github) I get no cw > signal: > cwdaemon:II: --- > cwdaemon:II: request: "?" > cwdaemon:II: Morse character "?" to be queued in libcw > cwdaemon:DD: Morse character "?" has been queued in libcw > cwdaemon:II: low TQ callback: start, TQ len = 1, PTT flag = 0x00/ame > cwdaemon:II: low TQ callback: branch 3, PTT flag = 0x00/ame > cwdaemon:II: low TQ callback: end, TQ len = 1, PTT flag = 0x00/ame > cwdaemon:II: --- > cwdaemon:II: request: "?" > cwdaemon:II: Morse character "?" to be queued in libcw > cwdaemon:DD: Morse character "?" has been queued in libcw > cwdaemon:II: low TQ callback: start, TQ len = 1, PTT flag = 0x00/ame > cwdaemon:II: low TQ callback: branch 3, PTT flag = 0x00/ame > cwdaemon:II: low TQ callback: end, TQ len = 1, PTT flag = 0x00/ame > cwdaemon:II: --- > > > Is there some option/setting somewhere I missed? > 73 de Zilvis LY2SS >
Re: cwdaemon
Hi Zilvis, Tried with the same cwdaemon (0.10.2) and libcw6 3.5.1-4 on Debian 11 (arch x86_64) + a fresh tlf build, and it had no issues. cwdaemon started as /usr/sbin/cwdaemon -d ttyS2 -n -xn -iii | tee cw.log (I use a physical serial port) Sent a ? using netcat: echo '?' | nc -u -w0 localhost 6789 and then started tlf and pressed F9. Log is attached. Do you see the lines when tlf initializes cwdaemon? cwdaemon:II: escaped request: "0" cwdaemon:II: requested resetting of parameters ...etc... 73, Zoli cwdaemon: Not forking... Press ^C to quit cwdaemon:II: setting sound system "Null" cwdaemon:II: starting generator with sound system "Null": success cwdaemon:II: --- cwdaemon:II: request: "?" cwdaemon:II: Morse character "?" to be queued in libcw cwdaemon:DD: Morse character "?" has been queued in libcw cwdaemon:II: keying event "1" cwdaemon:II: keying event "0" cwdaemon:DD: ...recv_from (no data) cwdaemon:II: keying event "1" cwdaemon:DD: ...recv_from (no data) cwdaemon:II: keying event "0" cwdaemon:DD: ...recv_from (no data) cwdaemon:II: keying event "1" cwdaemon:DD: ...recv_from (no data) cwdaemon:II: keying event "0" cwdaemon:DD: ...recv_from (no data) cwdaemon:II: keying event "1" cwdaemon:DD: ...recv_from (no data) cwdaemon:II: keying event "0" cwdaemon:DD: ...recv_from (no data) cwdaemon:II: keying event "1" cwdaemon:DD: ...recv_from (no data) cwdaemon:II: keying event "0" cwdaemon:DD: ...recv_from (no data) cwdaemon:II: keying event "1" cwdaemon:DD: ...recv_from (no data) cwdaemon:II: keying event "0" cwdaemon:II: low TQ callback: start, TQ len = 1, PTT flag = 0x00/ame cwdaemon:II: low TQ callback: branch 3, PTT flag = 0x00/ame cwdaemon:II: low TQ callback: end, TQ len = 1, PTT flag = 0x00/ame cwdaemon:DD: ...recv_from (no data) cwdaemon:DD: ...recv_from (no data) cwdaemon:DD: ...recv_from (no data) cwdaemon:DD: ...recv_from (no data) cwdaemon:DD: ...recv_from (no data) cwdaemon:DD: ...recv_from (no data) cwdaemon:DD: ...recv_from (no data) cwdaemon:II: --- cwdaemon:II: escaped request: "0" cwdaemon:II: requested resetting of parameters cwdaemon:II: setting sound system "Null" cwdaemon:II: starting generator with sound system "Null": success cwdaemon:DD: PTT flag = 0 (0x00/ame) cwdaemon:II: resetting completed cwdaemon:II: --- cwdaemon:II: escaped request: "3800" cwdaemon:II: requested tone [Hz]: "800" cwdaemon:II: tone: 800 Hz cwdaemon:II: --- cwdaemon:II: escaped request: "g70" cwdaemon:II: requested volume [%]: "70" cwdaemon:II: --- cwdaemon:II: escaped request: "226" cwdaemon:II: requested morse speed [wpm]: "26" cwdaemon:II: --- cwdaemon:II: escaped request: "71" cwdaemon:II: requested weighting: "1" cwdaemon:II: --- cwdaemon:II: escaped request: "d0" cwdaemon:II: requested PTT delay [ms]: "0" cwdaemon:DD: PTT flag = 0 (0x00/ame) cwdaemon:II: ensure PTT off cwdaemon:II: --- cwdaemon:II: escaped request: "e8" cwdaemon:EE: band switch output not implemented cwdaemon:DD: ...recv_from (no data) cwdaemon:II: --- cwdaemon:II: request: "?" cwdaemon:II: Morse character "?" to be queued in libcw cwdaemon:DD: Morse character "?" has been queued in libcw cwdaemon:II: keying event "1" cwdaemon:II: keying event "0" cwdaemon:DD: ...recv_from (no data) cwdaemon:II: keying event "1" cwdaemon:DD: ...recv_from (no data) cwdaemon:II: keying event "0" cwdaemon:DD: ...recv_from (no data) cwdaemon:II: keying event "1" cwdaemon:DD: ...recv_from (no data) cwdaemon:II: keying event "0" cwdaemon:DD: ...recv_from (no data) cwdaemon:II: keying event "1" cwdaemon:DD: ...recv_from (no data) cwdaemon:II: keying event "0" cwdaemon:DD: ...recv_from (no data) cwdaemon:II: keying event "1" cwdaemon:DD: ...recv_from (no data) cwdaemon:II: keying event "0" cwdaemon:DD: ...recv_from (no data) cwdaemon:II: keying event "1" cwdaemon:DD: ...recv_from (no data) cwdaemon:II: keying event "0" cwdaemon:II: low TQ callback: start, TQ len = 1, PTT flag = 0x00/ame cwdaemon:II: low TQ callback: branch 3, PTT flag = 0x00/ame cwdaemon:II: low TQ callback: end, TQ len = 1, PTT flag = 0x00/ame cwdaemon:DD: ...recv_from (no data) cwdaemon:DD: ...recv_from (no data) cwdaemon:DD: ...recv_from (no data) cwdaemon:DD: ...recv_from (no data) cwdaemon:DD: ...recv_from (no data) cwdaemon:DD: ...recv_from (no data) cwdaemon:DD: ...recv_from (no data) cwdaemon:DD: ...recv_from (no data)
cwdaemon
Hi all, Could somebody help me with this please? I run cwdaemon (0.10.2) with these options: "cwdaemon -d ttyUSB1 -n -xn -iii" It keys the FT991a rig OK when I issue characters via netcat: cwdaemon -d ttyUSB1 -n -xn -iii cwdaemon: Not forking... debug output: stdout Press ^C to quit cwdaemon:II: setting sound system "Null" cwdaemon:II: starting generator with sound system "Null": success cwdaemon:II: --- cwdaemon:II: request: "?" cwdaemon:II: Morse character "?" to be queued in libcw cwdaemon:DD: Morse character "?" has been queued in libcw cwdaemon:II: keying event "1" cwdaemon:II: keying event "0" cwdaemon:II: keying event "1" cwdaemon:II: keying event "0" cwdaemon:II: keying event "1" cwdaemon:II: keying event "0" cwdaemon:II: keying event "1" cwdaemon:II: keying event "0" cwdaemon:II: keying event "1" cwdaemon:II: keying event "0" cwdaemon:II: keying event "1" cwdaemon:II: low TQ callback: start, TQ len = 1, PTT flag = 0x00/ame cwdaemon:II: low TQ callback: branch 3, PTT flag = 0x00/ame cwdaemon:II: low TQ callback: end, TQ len = 1, PTT flag = 0x00/ame cwdaemon:II: keying event "0" cwdaemon:II: --- But when I try to send cw via tlf (master branch from github) I get no cw signal: cwdaemon:II: --- cwdaemon:II: request: "?" cwdaemon:II: Morse character "?" to be queued in libcw cwdaemon:DD: Morse character "?" has been queued in libcw cwdaemon:II: low TQ callback: start, TQ len = 1, PTT flag = 0x00/ame cwdaemon:II: low TQ callback: branch 3, PTT flag = 0x00/ame cwdaemon:II: low TQ callback: end, TQ len = 1, PTT flag = 0x00/ame cwdaemon:II: --- cwdaemon:II: request: "?" cwdaemon:II: Morse character "?" to be queued in libcw cwdaemon:DD: Morse character "?" has been queued in libcw cwdaemon:II: low TQ callback: start, TQ len = 1, PTT flag = 0x00/ame cwdaemon:II: low TQ callback: branch 3, PTT flag = 0x00/ame cwdaemon:II: low TQ callback: end, TQ len = 1, PTT flag = 0x00/ame cwdaemon:II: --- Is there some option/setting somewhere I missed? 73 de Zilvis LY2SS
Re: unixcw/cwdaemon and SDR support
Hi Matthew, I did run into the issue with cwdaemon: after an upgrade its config file was reset and it produced an erratic keying. Changing sound back to 'n' solved the issue and my conclusion was that cwdaemon is meant for either keying or side tone generation, but not for both. Which was just fine for me as I anyway prefer the side tone generated by the rig. So I didn't bother looking into it. For unixcw you can contact Kamil (unixcw.sourceforge.net) although he doesn't seem to be too active recently. I was able to get some fixes included into the code by providing a PR on sourceforge. But that was several years ago. Is the root cause of the issue clear? Simply reducing buffer size wouldn't hurt too much the performance IMO, so if that really cures the problem then it should be OK. Re tlfmarkers: currenly it contains just the last handful of spots received from the cluster, not what is exactly shown on the band map. I think this is a bug, i.e. the band map evolved into a usable feature whereas tlfmarkers remained using old spot handling. Probably it has not many users, so no-one complained. So this one is a task to be completed. 73, Zoli ha5cqz
Re: unixcw/cwdaemon and SDR support
Hi Matthew, I did run into this issue with cwdaemon: after an upgrade its config file was reset and it produced an erratic keying. Changing sound back to 'n' solved the issue and my conclusion was that cwdaemon is meant for either keying or side tone generation, but not for both. Which was just fine for me as I anyway prefer the side tone generated by the rig. So I didn't bother looking into it. For unixcw you can contact Kamil (unixcw.sourceforge.net) although he doesn't seem to be too active recently. I was able to get some fixes included into the code by providing a PR on sourceforge. But that was several years ago. Is the root cause of the issue clear? Simply reducing buffer size wouldn't hurt too much the performance IMO, so if that really cures the problem then it should be OK. Re tlfmarkers: currenly it contains just the last handful of spots received from the cluster, not what is exactly shown on the band map. I think this is a bug, i.e. the band map evolved into a usable feature whereas tlfmarkers remained using old spot handling. Probably it has not many users, so no-one complained. So this one is a task to be completed. 73, Zoli ha5cqz
unixcw/cwdaemon and SDR support
I have used tlf for not too serious CW contesting over the past few years. I really like the software and appreciate the active development. I have a Hermes-Lite 2 SDR (and amp): http://www.hermeslite.com/ I have forked linhpsdr and added a cwdaemon port into the SDR software. This allows TLF to key the Hermes-Lite 2 via linhpsdr (all neatly taken care of in software). Linhpsdr also has CAT and works nicely with tlf. My fork can be found here: https://github.com/m5evt/linhpsdr I set about modifying the cwdaemon code for this task, so was using unixcw underneath this. I very quickly realised that neither pulseaudio or alsa worked for me out of the box. I connected up a USB serial adapter and looked at the appropriate serial lines on a scope. NULL option works perfectly, but (obviously) has no sidetone. Alsa, produced sidetone, didn't call back correctly to the cwdaemon function call, no keying. Pulse, really choppy keying via the cwdaemon function call. However, although with pulse the keying is choppy, sidetone is fine, so you might not realise it. I have been through the archives on this list and there seem to be some knowledgeable folk in cwdaemon/unixcw. Could anyone confirm if either pulseaudio or alsa are working for them as expected in cwdaemon? I really don't want to get into custom kernels, these bugs seem audio related and I don't think they should need custom kernels? I tweaked some pulse settings and got it to work for me (see fork here): https://github.com/m5evt/unixcw-3.5.1 Although I have something that works for me. It just feels like it is going to be problematic to support reliably across a range of flavours of Linux with different audio systems. I appreciate this list is related to tlf, but I would welcome any people who use tlf/cwdaemon together to comment. I feel like I am better starting from scratch with this now. Cwdaemon like functionality has also been added to SparkSDR http://www.ihopper.org/radio/sparksdr2.htm so there are a couple of options that may be of interest to people. This type of setup lends itself very well to remote contesting radio operations. Related, I would like to see about overlaying what I see on the band map in tlf onto the linhpsdr SDR panadapter. The following image should give you an idea of what I mean: http://www.telepostinc.com/NaP3_v400_RC1_d.png But I would like to view based on the filtering I have set for the band map (mults etc.) in tlf. Will the tlfmarkers file give me everything I need for this? Does this file contain raw from the cluster or have filters (e.g. mults) applied? 73 Matthew M5EVT.
unixcw/cwdaemon and SDR support
I have used tlf for not too serious CW contesting over the past few years. I really like the software and appreciate the active development. I have a Hermes-Lite 2 SDR (and amp): http://www.hermeslite.com/ I have forked linhpsdr and added a cwdaemon port into the SDR software. This allows TLF to key the Hermes-Lite 2 via linhpsdr (all neatly taken care of in software). Linhpsdr also has CAT and works nicely with tlf. My fork can be found here: https://github.com/m5evt/linhpsdr I set about modifying the cwdaemon code for this task, so was using unixcw underneath this. I very quickly realised that neither pulseaudio or alsa worked for me out of the box. I connected up a USB serial adapter and looked at the appropriate serial lines on a scope. NULL option works perfectly, but (obviously) has no sidetone. Alsa, produced sidetone, didn't call back correctly to the cwdaemon function call, no keying. Pulse, really choppy keying via the cwdaemon function call. However, although with pulse the keying is choppy, sidetone is fine, so you might not realise it. I have been through the archives on this list and there seem to be some knowledgeable folk in cwdaemon/unixcw. Could anyone confirm if either pulseaudio or alsa are working for them as expected in cwdaemon? I really don't want to get into custom kernels, these bugs seem audio related and I don't think they should need custom kernels? I tweaked some pulse settings and got it to work for me (see fork here): https://github.com/m5evt/unixcw-3.5.1 Although I have something that works for me. It just feels like it is going to be problematic to support reliably across a range of flavours of Linux with different audio systems. I appreciate this list is related to tlf, but I would welcome any people who use tlf/cwdaemon together to comment. I feel like I am better starting from scratch with this now. Cwdaemon like functionality has also been added to SparkSDR http://www.ihopper.org/radio/sparksdr2.htm so there are a couple of options that may be of interest to people. This type of setup lends itself very well to remote contesting radio operations. Related, I would like to see about overlaying what I see on the band map in tlf onto the linhpsdr SDR panadapter. The following image should give you an idea of what I mean: http://www.telepostinc.com/NaP3_v400_RC1_d.png But I would like to view based on the filtering I have set for the band map (mults etc.) in tlf. Will the tlfmarkers file give me everything I need for this? Does this file contain raw from the cluster or have filters (e.g. mults) applied? 73 Matthew M5EVT.
Re: padding in cwdaemon packets
Hi Drew and Zoli, Am Sun, 8 Dec 2019 17:51:12 +0100 schrieb Csahok Zoltan : > Hi Drew, > > Trailing zero and newline have most likely historical origin. > > The zero was introduced abt 9 years ago in this commit: > https://github.com/Tlf/tlf/commit/5a2be34d01b296bc8b8d8b362407cc3077e3c6d8#diff-8be0c8c50997da170641d3392ba81b5a At that time it was unclear if cwdaemon needed a the send message as a zero terminated string or not, so I added it to be sure. Actual it seems that it is not needed. We can revert that commit. 73, de Tom > Apparently cwdaemon needed it. Now it does not for sure, neither any > newline. It actually removes NL: > https://github.com/acerion/cwdaemon/blob/master/src/cwdaemon.c > (line 1140) > > winkeydaemon as a defensive measure silently ignores non-processable > characters. Probably cwdaemon (libcw) does the same. > > Technically the trailing NL is a result of not chopping it after > fgets(). While for CW it is irrelevant, it might make sense for > digital modes. Not sure, though, as digital keyer code could add NL > on its own. > > So all in all I think we could get rid of both trailing chars without > issues. > > 73, > Zoli > > > On Sat, Dec 07, 2019 at 04:35:28PM +, Drew Arnett wrote: > > Doing some debugging and cleanup of my pywinkerdaemon implementation > > of cwdaemon. (I introduced some bugs with recent feature > > introduction.) > > > > A few years ago, I looked at the UDP packets several different > > cwdaemon clients sent. Some, like TLF, send a single trailing null > > character which is not needed. Some sent quite a lot. (Allocated a > > max UDP data structure, wrote nulls, then wrote the message to the > > beginning. Still, should have not bothered transmitting all that > > padding.) > > > > Looking at tlf as included in debian 10.2 today, I see it also has a > > \n (0x0a) character between the end of the CW message and the single > > null character. > > > > I recommend that tlf doesn't transmit either the 0x0a or the 0x00 > > trailing characters. Unless this would break other independent > > cwdaemon implementations. Anybody know? > > > > Best regards, > > > > Drew > > n7da -- "Do what is needful!" Ursula LeGuin: Earthsea --
Re: padding in cwdaemon packets
Hi Drew, Trailing zero and newline have most likely historical origin. The zero was introduced abt 9 years ago in this commit: https://github.com/Tlf/tlf/commit/5a2be34d01b296bc8b8d8b362407cc3077e3c6d8#diff-8be0c8c50997da170641d3392ba81b5a Apparently cwdaemon needed it. Now it does not for sure, neither any newline. It actually removes NL: https://github.com/acerion/cwdaemon/blob/master/src/cwdaemon.c (line 1140) winkeydaemon as a defensive measure silently ignores non-processable characters. Probably cwdaemon (libcw) does the same. Technically the trailing NL is a result of not chopping it after fgets(). While for CW it is irrelevant, it might make sense for digital modes. Not sure, though, as digital keyer code could add NL on its own. So all in all I think we could get rid of both trailing chars without issues. 73, Zoli On Sat, Dec 07, 2019 at 04:35:28PM +, Drew Arnett wrote: > Doing some debugging and cleanup of my pywinkerdaemon implementation > of cwdaemon. (I introduced some bugs with recent feature > introduction.) > > A few years ago, I looked at the UDP packets several different > cwdaemon clients sent. Some, like TLF, send a single trailing null > character which is not needed. Some sent quite a lot. (Allocated a > max UDP data structure, wrote nulls, then wrote the message to the > beginning. Still, should have not bothered transmitting all that > padding.) > > Looking at tlf as included in debian 10.2 today, I see it also has a > \n (0x0a) character between the end of the CW message and the single > null character. > > I recommend that tlf doesn't transmit either the 0x0a or the 0x00 > trailing characters. Unless this would break other independent > cwdaemon implementations. Anybody know? > > Best regards, > > Drew > n7da
padding in cwdaemon packets
Doing some debugging and cleanup of my pywinkerdaemon implementation of cwdaemon. (I introduced some bugs with recent feature introduction.) A few years ago, I looked at the UDP packets several different cwdaemon clients sent. Some, like TLF, send a single trailing null character which is not needed. Some sent quite a lot. (Allocated a max UDP data structure, wrote nulls, then wrote the message to the beginning. Still, should have not bothered transmitting all that padding.) Looking at tlf as included in debian 10.2 today, I see it also has a \n (0x0a) character between the end of the CW message and the single null character. I recommend that tlf doesn't transmit either the 0x0a or the 0x00 trailing characters. Unless this would break other independent cwdaemon implementations. Anybody know? Best regards, Drew n7da
[Tlf-devel] cwdaemon/ winkeyer questions
Currently I am running Xubuntu 12.04LTS x86 and will go to Xubuntu 14.04LTS later this spring. Depending on motherboard used it could be x86 or x64 OS. Logging programs are Tlf (naturally), CQRLog and Xlog. CW/PTT port is on ttyS0 to an MFJ 1279T. I currently have cwdaemon 0.94 installed. I understand that this has some bugs and I think I experienced it with the recent contests. Is the new version (0.10.0) since it has a new maintainer better? Or is it better to use winkeyer- server? I like the winkeyer config window the one time I tried it but it conflicted with the installed cwdaemon. I tried setting cwdaemon to default to ttyS0 but the program didn't like the changed config. I don't think CQRLog nor Xlog work with winkeyer, correct? What is the recomendations and/or opinions for this? Thanks, Jim/W3FA ___ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
Re: [Tlf-devel] cwdaemon/ winkeyer questions
On 03/26/2014 09:12 PM, Jim Bruce wrote: Currently I am running Xubuntu 12.04LTS x86 and will go to Xubuntu 14.04LTS later this spring. Depending on motherboard used it could be x86 or x64 OS. Logging programs are Tlf (naturally), CQRLog and Xlog. CW/PTT port is on ttyS0 to an MFJ 1279T. I currently have cwdaemon 0.94 installed. I understand that this has some bugs and I think I experienced it with the recent contests. Is the new version (0.10.0) since it has a new maintainer better? Or is it better to use winkeyer- server? I like the winkeyer config window the one time I tried it but it conflicted with the installed cwdaemon. I tried setting cwdaemon to default to ttyS0 but the program didn't like the changed config. I don't think CQRLog nor Xlog work with winkeyer, correct? What is the recomendations and/or opinions for this? Thanks, Jim/W3FA win-keyer works perfectly with tlf and cqrlog, but not xlog. Ed W3NR ___ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
Re: [Tlf-devel] cwdaemon or winkeyer
Nate == Nate Bargmann n...@n0nb.us writes: Nate * On 2013 20 Nov 06:13 -0600, Ed wrote: On Wed, 20 Nov 2013 09:57:44 +0100 Ervin Hegedüs - HA2OS airw...@gmail.com wrote: Hello, On Wed, Nov 20, 2013 at 09:04:55AM +0100, Fabian Kurz wrote: On Wed, Nov 20, 2013 at 09:00:18AM +0100, Thomas Beierlein wrote: To expand the question a little bit. There are some other keying devices supported (but not good as I fear). Maybe we can get some more feedback. Let us make a table and append to it: callcwdaemon winkeyer MFJ1278 ORIONkeyer == DL1JBE x DJ1YFK x OK1RR x HA2OS x W3NR x Nate N0NB x Nate Caveat, I have a Ham Gadgets Master Keyer 1 which implements the K1EL Nate protocol. I also use a MK1 and would love to use the K1EL protocol instead of cwdaemon driving it like a straight key. There is a small program that behaves like cwdaemon but does K1EL, I think written by the CQR guy. It is a graphical thing though, I'd much rather see a proper daemon that starts at boot and I can forget about :-) -- Pierfrancesco Caci, ik5pvx ___ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
Re: [Tlf-devel] cwdaemon or winkeyer
Good question! I am using cwdaemon. To expand the question a little bit. There are some other keying devices supported (but not good as I fear). Maybe we can get some more feedback. Let us make a table and append to it: callcwdaemon winkeyer MFJ1278 ORIONkeyer == DL1JBE x Please all users of tlf: Add to the table and resend to the list. 73, de Tom Am Tue, 19 Nov 2013 18:24:00 -0500 schrieb Ed aut...@gmail.com: I know this is a loaded question, but which do most of you use ? Ed W3NR ___ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel -- Do what is needful! Ursula LeGuin: Earthsea -- ___ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
Re: [Tlf-devel] cwdaemon or winkeyer
On Wed, Nov 20, 2013 at 09:00:18AM +0100, Thomas Beierlein wrote: To expand the question a little bit. There are some other keying devices supported (but not good as I fear). Maybe we can get some more feedback. Let us make a table and append to it: callcwdaemon winkeyer MFJ1278 ORIONkeyer == DL1JBE x DJ1YFK x 73 Fabian -- Fabian Kurz, DJ1YFK Munich, Germany fab...@fkurz.net +49 176 24079617 http://fkurz.net/http://lcwo.net/ ___ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
Re: [Tlf-devel] cwdaemon or winkeyer
Hello, On Wed, Nov 20, 2013 at 09:04:55AM +0100, Fabian Kurz wrote: On Wed, Nov 20, 2013 at 09:00:18AM +0100, Thomas Beierlein wrote: To expand the question a little bit. There are some other keying devices supported (but not good as I fear). Maybe we can get some more feedback. Let us make a table and append to it: callcwdaemon winkeyer MFJ1278 ORIONkeyer == DL1JBE x DJ1YFK x OK1RR x HA2OS x 73, Ervin ___ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
Re: [Tlf-devel] cwdaemon or winkeyer
On Wed, 20 Nov 2013 09:57:44 +0100 Ervin Hegedüs - HA2OS airw...@gmail.com wrote: Hello, On Wed, Nov 20, 2013 at 09:04:55AM +0100, Fabian Kurz wrote: On Wed, Nov 20, 2013 at 09:00:18AM +0100, Thomas Beierlein wrote: To expand the question a little bit. There are some other keying devices supported (but not good as I fear). Maybe we can get some more feedback. Let us make a table and append to it: callcwdaemon winkeyer MFJ1278 ORIONkeyer == DL1JBE x DJ1YFK x OK1RR x HA2OS x W3NR x Ed W3NR ___ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
Re: [Tlf-devel] cwdaemon or winkeyer
On Wed, 20 Nov 2013 09:57:44 +0100 Ervin Hegedüs - HA2OS airw...@gmail.com wrote: Hello, On Wed, Nov 20, 2013 at 09:04:55AM +0100, Fabian Kurz wrote: On Wed, Nov 20, 2013 at 09:00:18AM +0100, Thomas Beierlein wrote: To expand the question a little bit. There are some other keying devices supported (but not good as I fear). Maybe we can get some more feedback. Let us make a table and append to it: callcwdaemon winkeyer MFJ1278 ORIONkeyer == DL1JBE x DJ1YFK x OK1RR x HA2OS x K1VP x I use the USBwinkeyer if that matters. For things like Field Day or similar events I have used CWdaemon. -- Ed Lawson Ham Callsign: K1VP PGP Key ID: 1591EAD3 PGP Key Fingerprint: 79A1 CDC3 EF3D 7F93 1D28 2D42 58E4 2287 1591 EAD3 ___ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
[Tlf-devel] cwdaemon version
Ok, now what version do we need to be using ? I have 0.9.5-1 from the Mint14 repository. Ed W3NR ___ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
Re: [Tlf-devel] cwdaemon or winkeyer
To all, thanks for the feedback so far. Now let us bring the different threads together and make an actual table: callcwdaemon winkeyer MFJ1278 ORIONkeyer == DL1JBE x DJ1YFK x OK1RR x HA2OS x W3NR x N0NB x K1VP x N7XY x That means that all uses the NET_KEYER interface which operates via sockets. Seems the ORIONkeyer can be dropped and we can concentrate on making the other ones better. Does anyone still have/use the old MFJ1278 (maybe only for RTTY)? 73, de Tom DL1JBE. -- Do what is needful! Ursula LeGuin: Earthsea -- ___ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
Re: [Tlf-devel] cwdaemon version
Hi Ed, Am Wed, 20 Nov 2013 18:11:35 -0500 schrieb Ed aut...@gmail.com: Ok, now what version do we need to be using ? I have 0.9.5-1 from the Mint14 repository. From my experiences cwdaemon 0.9.4 has some bugs. I rely mostly to 0.9.2 at the moment. - no correct PTT handling - does not queue more than one message correctly (and therefore does not work with autosend) As far as I know the 0.9.5 may have the same problems. An easy check is to send two CW messages (maybe F2 and F3) shortly after each other. 0.9.4 will mix the messages. cwdaemon 0.9.7 got some work and fixed these problems. But for me it crashes often. 73, de Tom DL1JBE -- Do what is needful! Ursula LeGuin: Earthsea -- ___ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
[Tlf-devel] cwdaemon or winkeyer
I know this is a loaded question, but which do most of you use ? Ed W3NR ___ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
[Tlf-devel] Alternative winkeyer interface via cwdaemon for tlf
Hello tlf-ers, I've not been able to play radio for the past 5 months, and for the short term future. However, I have been busy in other ways and thought some might be interested in the winkeyer interface to tlf I developed. It's similar to OK2CQR's solution, but with more features. It's here: http://g4kno.com/software_it/jWinkeyServer/jWinkeyServer.html Hope it may be of use to someone, but please remember it's beta software. 73 Andy, G4KNO. ___ 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] cwdaemon 0.9.4 and PTT
Hi all, I've documented before my experiences with the PTT function on the parallel port and that it's doesn't appear to be working. I was just wondering if there had been any developments on this problem - I'd really like to use the voice-keyer in tlf for the next contest. Thanks. Rob, N6ROB ___ Tlf-devel mailing list Tlf-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/tlf-devel
[Tlf-devel] cwdaemon-0.9.4 does not compile
I can not compile cwdemon-0.9.4 on puppy linux. The error message is: quote Configure: error: Package requirements (libcw) are not met: Package libcw was not found in the pkg-config search path. unquote I have installed UNIXCW-2.2 and the libcw.so is in /usr/local/lib I have also set UNICW_LIBS to /usr/local/lib What to do? Rein PA0R -- http://pa0r.blogspirit.com ___ Tlf-devel mailing list Tlf-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/tlf-devel
Re: [Tlf-devel] cwdaemon-0.9.4 does not compile
At the risk of stating the obvious, is /usr/local/lib in /etc/ ld.so.conf? If not, add it and run 'ldconfig' as root. Unless Puppy Linux does things in a non-standard way, that should work. Bob, N7XY On Dec 23, 2007, at 6:40 AM, Rein Couperus wrote: I can not compile cwdemon-0.9.4 on puppy linux. The error message is: quote Configure: error: Package requirements (libcw) are not met: Package libcw was not found in the pkg-config search path. unquote I have installed UNIXCW-2.2 and the libcw.so is in /usr/local/lib I have also set UNICW_LIBS to /usr/local/lib What to do? Rein PA0R -- http://pa0r.blogspirit.com ___ Tlf-devel mailing list Tlf-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/tlf-devel Bob Nielsen [EMAIL PROTECTED] ___ Tlf-devel mailing list Tlf-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/tlf-devel
Re: [Tlf-devel] cwdaemon on debian
On Thu, 09 Nov 2006 14:40:53 -0500 Christopher Moore [EMAIL PROTECTED] wrote: Hello, I'm running Debian unstable and get the following error when I run cwdaemon status ppdev0: failed to register device! Does your parallel port work okay with a printer? Try removing the lp module (rmmod lp) and adding ppdev (insmod ppdev). I'm trying to use the parallel port. Would it be better to use a com port? Thanks Chris w1gm Joop, PG4I ___ Tlf-devel mailing list Tlf-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/tlf-devel
Re: [Tlf-devel] cwdaemon on debian
Christopher Moore escribió: Hello, I'm running Debian unstable and get the following error when I run cwdaemon status ppdev0: failed to register device! I'm trying to use the parallel port. Would it be better to use a com port? It may be busy. try rmmod lp and then excecute cwdaemon. 73, Fede LU4HKN. ___ Tlf-devel mailing list Tlf-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/tlf-devel
[Tlf-devel] cwdaemon 0.9.4beta1 abailable for testing
Hoping to reach the right people, especially those who run *BSD... I have just uploaded a beta version of cwdaemon to http://www.xs4all.nl/~pa4tu/tmp/cwdaemon-0.9.4beta1.tar.gz From the ChangeLog: * Patch by Lada, OK1ZIA which adds threading to cwdaemon. A separate thread has been added for reading data from the socket. The gives us the advantage that cwdaemon will stop immediately after receiving ESC0 and will not finish the current character. Tested okay on i386 architecture. What about FreeBSD, OpenBSD Also, if you want to add something to cwdaemon before the next release, this is the time to do so... :) Regards, Joop PG4I ___ Tlf-devel mailing list Tlf-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/tlf-devel
[Tlf-devel] cwdaemon TLF
The only way I can get RTS to be set to off is to start cwdaemon with the following: [EMAIL PROTECTED]:/home/ed]# cwdaemon -d ttyS1 -x n -n and then in logcfg I set PTT to 0. Is this the correct way to do this.? I use DTR for CW and RTS for keying the digital modes. Thanks Ed W3NR ___ Tlf-devel mailing list Tlf-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/tlf-devel
