[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Using hamlib for CW keying
From: |
Nate Bargmann |
Subject: |
Re: Using hamlib for CW keying |
Date: |
Fri, 29 Nov 2019 12:51:59 -0600 |
User-agent: |
NeoMutt/20180716 |
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'll have to look at the Tlf code to
see if config parameters can be passed to the library without going
through tigctld.
73, Nate
--
"The optimist proclaims that we live in the best of all
possible worlds. The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
signature.asc
Description: PGP signature
- Re: Using hamlib for CW keying, (continued)
Re: Using hamlib for CW keying, Nate Bargmann, 2019/11/21
Re: Using hamlib for CW keying, Nate Bargmann, 2019/11/25
Re: Using hamlib for CW keying, Olaf Devik, 2019/11/27
Re: Using hamlib for CW keying, Olaf Devik, 2019/11/29
- Re: Using hamlib for CW keying,
Nate Bargmann <=