Hi,
I am using version 1.8.1 on Ubuntu 14.04.
I see that you using the command-line interface to the K3NG keyer.
I think this is a very good idea sinc the winkeyer protocol is not quite
right in the K3ng keyer.
I found that the only way I could get CLI to work is to first connect to
the port using a terminal program (kermit) and then it would work.
If I did not do this, the keyer would send strings of ???? , meaning
it did not understand what it was being sent. My guess is that that
kermit was setting the baud rate and otherwise the port was probably
at some other baud. After kermit set it, the keyer worked fine.
73, Jim W2XO
Fri, 2014-10-03 23:18
#1
K3NG keyer - baud rate not set on port?
I'm quite sure now that the baud rate is not being set.
I brought up CQRlog, the keyer only responded with ???
to all keying inputs. Then I did:
stty -f /dev/ttyACMO 115200
and it fixed the problem, but every time you reboot the computer,
the port is not set to 115200 baud.
-- Jim, W2XO