Cwdaemon keyboard trouble persists

9 posts / 0 new
Last post
K3GHH
Cwdaemon keyboard trouble persists

I'm running the latest 1.9.1 and like it very much... Thanks! But the problem I reported a year ago is still present: keyboard CW using cwdaemon is impossible.

This is the output from typing "probably not": PRPROBABLYNOTO and here's "how is this working?": HOHOHOWISTHOWISTHISWORKING?HWW (I was using "word mode, first word in letter mode.")

A year ago I thought the "problem is that 'word mode' uses the space bar as a signal to begin sending the next word, and if the previous word has not completed yet the two words are mingled." These little tests suggest it isn't that simple.

Is anyone using keyboard CW with cwdaemon? Mine is 0.9.5-1.1 from the Kubuntu Trusty repository.

--John K3GHH

ok2cqr
ok2cqr's picture
Re: Cwdaemon keyboard trouble persists

John,

please run cwdaemon from console:

sudo cwdaemon -n -d ttyUSB0

where ttyUSB0 is the keying port. It won't key the device but it will write the output to the console. Paste here the output, please. Thanks!

I don't have any keying device for cwdaemon because I use WinKeyer USB from K1EL but the debug output was fine.

73 Petr, OK2CQR

K3GHH
Thanks very much, Petr. I'll

Thanks very much, Petr. I'll have to remember how to do that. I'm keying the transceiver from a parallel port, using an adapter bought from another ham --- it's probably just the simple transistor circuit I had planned to build for myself. Anyway, I'll try to get that console output.

--John K3GHH

K3GHH
Console output:

After stopping the cwdaemon that KSysGuard said was already running, making sure lp was not loaded, and unplugging my parallel-port keying adapter, here's the output:

john@john-N105:~$ sudo cwdaemon -n -d parport0
cwdaemon: Not forking...
cwdaemon: Device used: parport0
cwdaemon: Press ^C to quit
^Ccwdaemon: Exiting
john@john-N105:~$

This doesn't look like much information, Petr, but maybe it tells you something!

Plugging my parallel-port adapter back in, starting cwdaemon in a terminal window, and starting CQRlog gets me back to the situation described above. The CW function keys all sound great (I defined a couple in addition to the F1 CQ) and "letter mode" is fine, but the word modes behave as above.

--John K3GHH

ok2cqr
ok2cqr's picture
Re: Console output:

I'm sorry John, I forget to mention that after running cwdaemon -n -d parport0, you must try to send some text in cw keying window. It will appear in the console. Thas is what I need...

K3GHH
Console output with text

Petr, the first part of this is just from the F1 (CQ) key. The rest of it was typed in "word" mode.

john@john-N105:~$ sudo cwdaemon -n -d parport0
[sudo] password for john:
cwdaemon: Not forking...
cwdaemon: Device used: parport0
cwdaemon: Press ^C to quit
cwdaemon: Speed: 30 wpm
cwdaemon: Message = CQ CQ CQ DE K3GHH K3GHH K
cwdaemon: Morse = C
cwdaemon: Morse = Q
cwdaemon: Morse =
cwdaemon: Morse = C
cwdaemon: Morse = Q
cwdaemon: Morse =
cwdaemon: Morse = C
cwdaemon: Morse = Q
cwdaemon: Morse =
cwdaemon: Morse = D
cwdaemon: Morse = E
cwdaemon: Morse =
cwdaemon: Morse = K
cwdaemon: Morse = 3
cwdaemon: Morse = G
cwdaemon: Morse = H
cwdaemon: Morse = H
cwdaemon: Morse =
cwdaemon: Morse = K
cwdaemon: Morse = 3
cwdaemon: Morse = G
cwdaemon: Morse = H
cwdaemon: Morse = H
cwdaemon: Morse =
cwdaemon: Morse =
cwdaemon: Morse = K
cwdaemon: Message = HOW
cwdaemon: Morse = H
cwdaemon: Morse = O
cwdaemon: Message = IS
cwdaemon: Morse = H
cwdaemon: Message = THIS
cwdaemon: Morse = H
cwdaemon: Morse = O
cwdaemon: Message = THING
cwdaemon: Morse = H
cwdaemon: Morse = O
cwdaemon: Morse = W
cwdaemon: Morse = I
cwdaemon: Morse = S
cwdaemon: Morse = T
cwdaemon: Message = WORKING?
cwdaemon: Morse = H
cwdaemon: Morse = O
cwdaemon: Morse = W
cwdaemon: Morse = I
cwdaemon: Morse = S
cwdaemon: Morse = T
cwdaemon: Morse = H
cwdaemon: Morse = I
cwdaemon: Morse = S
cwdaemon: Morse = T
cwdaemon: Morse = H
cwdaemon: Morse = I
cwdaemon: Morse = N
cwdaemon: Morse = G
cwdaemon: Morse = W
cwdaemon: Morse = O
cwdaemon: Morse = R
cwdaemon: Morse = K
cwdaemon: Morse = I
cwdaemon: Morse = N
cwdaemon: Morse = G
cwdaemon: Morse = ?
cwdaemon: Morse = H
cwdaemon: Morse = W
cwdaemon: Morse = O
cwdaemon: Morse = W
^Ccwdaemon: Exiting
john@john-N105:~$

--John K3GHH

ok2cqr
ok2cqr's picture
Re: Console output with text

Thank you for the debug output. It seems something is wrong with cwdaemon because it sends always whole data, not only what it gets (in the message = ). What version of CW daemon are you using?

K3GHH
RE: console output with text

My cwdaemon is 0.9.5-1.1 from the Kubuntu Trusty repository.

--John K3GHH

K3GHH
Working as designed?

It just occurred to me that perhaps the "word" modes are working exactly as they were designed, sending one word at a time: Send one word, wait until it completes, then send the next word. I apologize for not considering this, and for complaining that the program does not do something it may never have been intended to do.

For those who have not tried it, to send "probably not" in a "word" mode one would type "PROBABLY[spacebar]NOT", but the spacebar after "not" must not be hit until "probably" (and a space) have been sent; after they have gone out, one can hit the spacebar that starts the word "not." Hitting the spacebar immediately after typing "not" will start "not" immediately, even if "probably" is only half completed.

The only other keyboard system I have tried, Xlog using cwdaemon, has a buffer that allows a certain amount of typing ahead, several normal sentences as I recall. The CW dutifully trails along, sending what's been typed complete with spaces between words. (Xlog does not allow one to backspace and correct mistakes, though... so type carefully.)

Again, I apologize if I have misunderstood what "word" modes mean. But even if my setup is working as designed, it is not practical for keyboard CW.

--John K3GHH