Re: [Hamlib-developer] Can't communicate with TS-450S via Digimaster USB

[A. J. C. <va...@is...>]

Hi there Nate,

I don't disagree with what you're saying - I'm not sure quite sure how
this FTDI-based interface does all of it's work; however, you're
probably going to hate me saying this too, but "It works fine in
Windows".   I've mainly been using HamRadioDeluxe in Windows, and to get
the box to work I had to disable CTS, DTR and RTS when telling it about
how to access the Kenwood on this particular COM port.  Aside from the
baud being set at 4800, I don't know if it's even attempting to do any
flow control at all.

Oh, and I'm not moving gear around, Linux & Windows tests are being done
from a dual-boot laptop.

Is there any way to create a test rig source file that would open the
serial port & rig init, expect failure, close off as if the process were
going to terminate but instead to a full retry of re-opening the port
and rig init?

This is very consistent in my testing.  If I reset the FTDI interface
box, run rigctl, it won't get identification and erorrs out at the end
with "Communication timed out" (although it's odd that the timeout is so
short - a test with 20 retries has "timedout 0.1..." and "timedout
0.2..." errors.

Yet if I just re-run the same rigctl command, it opens find and I can
run commands on the rig (and rigctl has no issues no matter how many
times I run it after that).

I've also found that the serial_handshake="None" behaves just the same
as XONXOFF.

Yet, the hamlib calls via software that relies on hamlib can't get the
rig initialized.

I'd love to do more testing, though I may also contact ZLP electronics
about this device and what to expect.  I can't imagine there's any real
hardware handshaking between the FTDI box and the rig, as it's only a 3
conductor connector towards the rid (1/8" phono-type jack).

Thanks,

On 11/27/2011 04:06 PM, Nate Bargmann wrote:
> * On 2011 27 Nov 17:19 -0600, A. J. Clark wrote:
>> Hi there Nate,
>>
>> Got around to testing today with the 20111127 nightly snapshot.
>>
>> One thing that's interesting when I run rigctl the first time with all
>> the usual parameters, I get "rig_open: error = Communication timed out"...
>>
>> The second time I run it, no complaints, I can read frequency and exit.
>>
>> The output I've got from xlog's trace this time is:
>>
>> rig:rig_init called
>> kenwood_init called
>> kenwood_init: if_len = 38
>> rig_set_conf: serial_handshake='"XONXOFF"'
> 
> I just noticed that you're specifying XONXOFF.  The ts450.c default is
> RIG_HANDSHAKE_HARDWARE which implies the connection of RTS/CTS lines
> between the serial port and IF232 interface (if that's what you're
> using).  XONXOFF would seem to require radio protocol support and I've
> not seen any of the Kenwood rigs use it.
> 
> Looking at the IF232C manual, I see that it calls for the connection of
> the RTS/CTS along with TX, RX, and GND lines.  Other than this, I am out
> of ideas but the errors shown by rigctl seem consistent with improper
> flow control.
> 
> 73, de Nate >>
> 

-- 
VA7AQD
Adam Clark
Kamloops, BC