Re: [Hamlib-developer] RTS/DTR control?

[RT C. <rt...@be...>]

OK-  below is with rigctl, Hamlib 1.2.15.3. Testing with a K3 on a real serial 
port.

Default PTT works (no RTS/DTR functionality set on the K3): I can set the ptt on 
and off with

rigctl -v --model=229 --rig-file="/dev/ttyS1" T 1
rigctl -v --model=229 --rig-file="/dev/ttyS1" T 0

Then I turn on RTS for ptt on the K3. Something is screwy with rigctl in this 
case:

rigctl -v --model=229 --rig-file="/dev/ttyS1" --ptt-type="RTS" 
--ptt-file="/dev/ttyS1" T 1
rigctl -v --model=229 --rig-file="/dev/ttyS1" --ptt-type="RTS" 
--ptt-file="/dev/ttyS1" T 0

nothing happens. Is the syntax correct?

But if I do the following two commands, the ptt does turn on (but only after the 
f command):
rigctl -v --model=229 --rig-file="/dev/ttyS1" --ptt-type="RTS" 
--ptt-file="/dev/ttyS1" T 0
rigctl --model=229 --rig-file="/dev/ttyS1" f

With this sequence, both 'T 0' and 'T 1' work to toggle the RTS.

I also tried with a dummy rig, that did nothing at all.

Tor
N4OGW





________________________________
From: Nate Bargmann <n0...@n0...>
To: RT Clay <rt...@be...>
Cc: ham...@li...
Sent: Sat, March 30, 2013 5:13:20 PM
Subject: Re: [Hamlib-developer] RTS/DTR control?

* On 2013 30 Mar 09:33 -0500, RT Clay wrote:
> I don't think that would work. At least for the K3 backend I need, the
> only TX method defined is the software command.

That is the default but can be changed, as I understand it.

For example, 'rigctl -m 229 -L' returns, in part:

ptt_type: "Push-To-Talk interface type override"
        Default: RIG, Value: 
       Combo: RIG, DTR, RTS, Parallel, CM108, None
ptt_pathname: "Path name to the device file of the
    Push-To-Talk"
        Default: /dev/rig, Value: String.

So, rig_set_conf could be called with 'ptt_type' 'RTS' and then again
with 'ptt_pathname' '/dev/ttyS0' or whatever.  The 'rig_ptt' will assert
RTS on the port the K3 is connected to, unless '/dev/rig' is a symlink
already pointing toward that port, instead of using the CAT command.  If
not, it is a bug that should be fixed.


> I really don't want to tie up two serial ports for each radio- at
> least with the K3 there is no problem doing rig control and RTS/DTR on
> the same port.

Right, and the K3 is a good candidate to test if this works as we
expect.

73, de Nate >>

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us