Re: [Hamlib-developer] Hamlib PTT for TS-570

[Rob F. <fr...@wa...>]

HI Tom & Hank,

On my TS-850SAT, I'm inserting audio over ACC2, but using hamlib or VOX 
for PTT.  Hamlib works from rigctl, but not from recent fldigi 
releases.  I haven't had time to look at it. 

One thing that probably doesn't bear on the present question, but in 
case it does, I'm going to mention it. It is that I need to use RTS/CTS 
for my  hamlib control cable.  I have them wired together at present, 
which is probably why I had to set the timeout on Kenwood rigs 
excessively long in hamlib, and that should probably be reversed, but 
someone (probably me) needs to check and see if using RTS/CTS correctly 
solves the problem of the messups when you are tuning for example with 
VFO while rig commands are happening.  (The TS-850 at least won't send 
or receive rig control commands while the VFO is spinning, and also 
likely some other front panel interface things are happening).

I still think there is something with fldigi that is making it so I can 
use rigctl and not fldigi for PTT.

A few more comments are interspersed below.

Thomas Beierlein wrote:
> Hi Hank, hi Rob,
>
> I think I have finally found out why your hamlib PTT settings do not work and
> why mine does.
>
> Hank as I read your last mail correctly you can now get/set frequency and also 
> switch between TX and RX via rigctl. I assume that the same is true for fldigi,
> but that you get no modulation.
>
> That happens if you insert the audio frequency over the rear ACC2 socket.
> If you do so you 'have to use' the hardware PTT also on the ACC2 socket.
>
> 'Send' key on frontpanel, PTT on microfon socket, automatic VOX changeover and
> also software PTT via hamlib - all switches to TX but choose the audio input
> from  microphone socket for modulation.
>   
I don't think this is the case with my TS-850SAT.
> But if we would like to use the ACC2 interface for the audio input to the TX we
> must use hardware PTT on the same connector. That is the only way it wor
>   
> Hope that clarifies the situation.
>   
It lends some more light, but there are still some mysteries.

Thanks & 73,

Rob, KL7NA
> 73, de Tom DL1JBE.
>
>
> On Fri, Jan 30, 2009 at 11:44:51AM -0600, Henry Taylor wrote:
>   
>> Hi Tom,
>>
>> I think we're getting somewhere.
>>
>> rigctl command  t (lower case) gets the PTT status and it reports  0.
>>                            T (uppercase) takes an argument of either 1 or 
>> 0.  I sent it T 1 and then checked with  t and it reports                   
>>                           the change from 0 to 1.
>>
>> So rigctl can interact with PTT (and freqency and change from CW to USB etc)
>>
>> So then I put  vvvv in the Advanced configuration" line of the Hamlib 
>> screen, saved it, and invoved fldigi from the command line and here's what 
>> it says:
>>
>> "fldigi:  Symbol 'hamlib version' has a different size in shared object, 
>> consider re-linking"
>>
>> In the meanwhile I has changed the way fldigi was installed.  Previously I 
>> had just used the GUI.  So I got rid of that and reinstalled it using the 
>> command line and put it in a different directory.  Now it seems all the 
>> feature of Hamlib work except PTT.
>>
>> And I'm just not sure about that.  1) It doesn't toggle the S-meter like it 
>> does when I TX from the "Hardware PTT" box (to left of RigCat).  That does 
>> TX and I get responses to CQ etc and have been in QSO.  But while in 
>> Hamlib, it doesn't toggle the S-meter.
>>                                                       2) And so far nobody 
>> has responded to my CQ's.  And they don't seem to hear my responses to 
>> their CQ's.  But then you never know about how the band is any given 
>> moment.
>>
>> I have a speaker hooked up to my Rigblaster and I do hear the PSK warble 
>> with both modes.  So it's getting as far as the Line In to the Kenwood.
>>
>> What next ?  Does that 'hamlib version' has a different size mean anything ?
>>
>> And thanks again for all your help.
>>
>> Hank  KD0BVQ
>>
>> At 02:27 AM 1/30/2009, you wrote:
>>     
>>> Hi Hank,
>>>
>>> On Thu, Jan 29, 2009 at 03:41:45PM -0600, Henry Taylor wrote:
>>>       
>>>> rigctl -m 204 -r /dev/ttyS0 -s 9600 -vvvv
>>>>
>>>> which results in a long list of Rig register numbers and then
>>>> Opened rig model 204, 'TS-570D"
>>>> Backend version: 0.6.1  SStatys:  stable
>>>>         
>>> Glad to hear. That is the point we tried to reach :-)
>>>       
>>>> and then from the interactive command line if I run (for example) F 
>>>>         
>>> 7070000
>>>       
>>>> it sets the rig's frquency to 7.070 and if I change it manually using the
>>>> dial to, say,  1707000 and tell it   f   it returns that frequency
>>>> correctly.
>>>>         
>>> Fine.
>>>
>>>       
>>>> What next ?  fldigi is still being flaky about it all.
>>>>         
>>> Please have a look in 'rigctl' running and typing '?' for getting a list of
>>> all commands. There should be a command for get/set PTT ('T' if i remember i
>>> correct). Please try that it works.
>>>
>>> Afterwards check your setting about baudrate, serial interface and so on
>>> in fldigi and compare it to the values you used for rigctl.
>>>
>>> If it still does not run, try to insert the '-vvvvv' into the extra settings
>>> field (above the ptt checkbox) and start fldigi from command line. That should
>>> give us a protocol of fldigi's communication with the rig.
>>>
>>> 73, de Tom DL1JBE.
>>>
>>> --
>>> "Do what is needful!"
>>> Ursula LeGuin: Earthsea
>>> --
>>>
>>>
>>> No virus found in this incoming message.
>>> Checked by AVG - http://www.avg.com
>>> Version: 8.0.176 / Virus Database: 270.10.15/1923 - Release Date: 
>>> 1/29/2009 7:13 AM
>>>       
>
>   

-- 
Rob Frohne, Ph.D., P.E.
E.F. Cross School of Engineering
Walla Walla University
100 SW 4th Street
College Place, WA 99324
(509) 527-2075			 http://people.walllawalla.edu/~rob.frohne