I'll trouble shoot this with Joop off list. Shouldn't be related to
the type of serial port, but we will see. First step was a better
assertion statement that would provide the value that failed to match.
Good sign that the code got that far before throwing an error. Will
be looking at K1EL docs
Now I remember that actually our FD is setup is just like this:
using a single USB-serial converter with RX/TX controlling the rig via hamlib
and DTR doing keying via cwdaemon. We had no issues with it.
The only thing is that at Tlf start-up the key is down for a second.
I'll check hamlib config t
Hi Drew,
is pywinkerdaemon intended to work with USB ports? I get:
$ ./pywinkeyerdaemon.py -d /dev/ttyUSB1 -p 6788
Traceback (most recent call last):
File "./pywinkeyerdaemon.py", line 310, in
winkeyer = Winkeyer(args.device)
File "./pywinkeyerdaemon.py", line 43, in __init__
self.
The reason I am asking this question is because I am comparing the
present behavior of Tlf's CT mode to that of my CT ver 9 manual and the
two do not match. Tlf does send F5 followed by F2 as described in the
CT manual, but the F2 have different definitions between the two
programs.
If there are
D'oh! Read the man page, Nate!
RIGCONF=rig_configuration_parameters
Send rig configuration parameters to Hamlib.
e.g. RIGCONF=civaddr=0x40,retry=3,rig_pathname=/dev/ttyS0
I plan to try this.
73, Nate
--
"The optimist proclaims that we live in the best of al
That's cool, Olaf.
It stands to reason that the DTR and RTS lines would explicitly need to
be turned off as I think the kernel automatically enables them when an
application initializes the port.
This was a more or less silly idea I had and I'm glad to see it will
work! I'll have to try it too.
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). H
