/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
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.
&g
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
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
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 he
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 '?' |
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
c
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. Whic
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. Whic
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
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
7cc3077e3c6d8#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
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
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
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
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
ed (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
Hi Ed,
Am Wed, 20 Nov 2013 18:11:35 -0500
schrieb Ed :
> 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 m
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
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
> call cwdaemon winkeyer MFJ1278 ORIONkeyer
> ==
> DL1JBE x
> DJ1YFK x
> OK1RR x
> HA2OS x
> K1VPx
N7XY x
Well, almost anyway. I have the kit but sti
her 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
te:
> > > > 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 app
her 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
t; 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-deve
callcwdaemon winkeyer MFJ1278 ORIONkeyer
==
OK1RR x
73,
Martin, OK1RR
___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel
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:
call cwdaemon 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
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
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:
Thomas
All problems apart from the cwdaemon seems to have been sorted out. Did
as follows after advice from group members.
1. Removed Tlf - sudo make uninstall
2. Removed compiled hamlib - sudo make uninstall
3. Reinstalled hamlib dev packaged from repositories
4. Compiled tlf with hamlib
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
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
_
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 pupp
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
Sorry, I should have said that the pins numbers I was referring to were
on the parallel port.
On Fri, 2007-12-07 at 22:37 -0800, Rob Vance wrote:
> Hi All,
>
> I am using Gutsy Gibbon (Ubuntu 7.10) with tlf 0.9.30 and cwdaemon
> 0.9.4.
>
> I am having troubles with my set-up
Hi All,
I am using Gutsy Gibbon (Ubuntu 7.10) with tlf 0.9.30 and cwdaemon
0.9.4.
I am having troubles with my set-up and I noticed that the pins that are
supposed to toggle voltage for PTT are not working.
According to my voltmeter pin 16 is not toggling when sending a
voice-keyer message
> ...First you need to configure and install unixcw
> A STEP BACK?
>
> I believe we need a most compact binary and not a nightmare depending on
> the 1024 libraries installed before... Take unixcw and simply integrate
> it into cwdaemon...
>
I could of course do this, but
...First you need to configure and install unixcw
A STEP BACK?
I believe we need a most compact binary and not a nightmare depending on
the 1024 libraries installed before... Take unixcw and simply integrate
it into cwdaemon...
BTW cwdaemon still needs some help. It works OK on a custom
I have just released version 0.9.4 of cwdaemon, see:
http://pg4i.chronos.org.uk/download/cwdaemon-0.9.4.tar.gz
>From the changelog:
* Cwdaemon has been ported to the latest version of unixcw, version 2.3.
First you need to configure and install unixcw, which adds the unixcw
developm
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?
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 excecut
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?
Thanks
Chris w1gm
___
Tlf-devel mailin
I was a bit inaccurate. cwdaemon tested within tlf, tried to increase
speed with +. Assumed that a single + means a speed increase of 2 wpm,
tried to use 10 of them to get another 20 wpm above tlf limit. It
sounded suspicious, it was not 70 wpm :-), must be 60 or so...
No other bug found than
- compiles and runs on my Slackware 10.2 (kernel 2.6.16.4) perfectly
- keys my Orion perfectly with TLF 0.9.30
- weighting set to -30 stops the keying (bug), the process still runs
and needs to be killed manually. If weighting set to -10, runs
perfectly. Positive weighting values - without any p
Op ma, 17-04-2006 te 15:54 -0400, schreef Diane Bruce:
> It compiles and runs. Whether it still keys my transmitter I don't know,
> I tested on my main freebsd desktop not the hamradio desktop. I'll try
> and do that tomorrow. But at least it's a data point.
>
Thanks Diane,
looking forward to y
On Mon, Apr 17, 2006 at 10:33:34AM +0200, Joop Stakenborg wrote:
> 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
>
...
> Tested okay on i386
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
Op zo, 13-11-2005 te 10:32 -0500, schreef Ed:
> I hope this is useful to someone, as I spent several hours trying to get
> this up and running. BTW I just accidently came across the /etc/default
> file, I saw no mention of it anywhere.
I didn't advertise it in the README because it is debian s
ell. As you've probably discovered,
/etc/default has a lot of config files in it. Sometimes I'm not sure
if this is a feature or a bug, but I've trained myself to look there
first.
I would suggest that you file a bug report against cwdaemon (it's as
easy as running "reportbug
This was not easy, but I managed to muddle through this. To save others
that may be interested, but discouraged here is how I set up cwdaemon to
work correctly with TLF using serial port keying.
I edited /etc/default/cwdaemon file and changed the following
DEVICE="ttyS1" this se
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
52 matches
Mail list logo
