Re: [Hamlib-developer] Kenwood TH-D72

[Stephane F. <f8...@fr...>]

Hi Paul,

Thanks for quick report.

Tue, Apr 19, 2011, Paul Campbell skribis:
> #    rigctl -m 217 -vvvvv -r /dev/ttyUSB0
> rigctl, Hamlib 1.2.12
> Report bugs to <ham...@li...>
> 
> rig:rig_init called
> rig: loading backend kenwood
> kenwood: _init called
[snip]
> kenwood_init
> kenwood_init: if_len = 38
> rig:rig_open called
> th_get_vfo: called
> th_get_vfo_char: called
> kenwood_transaction: BC
> TX 3 bytes
> 0000    42 43 0d                                           BC.
> RX 3 characters
> 0000    42 43 0d                                           BC.
> kenwood_safe_transaction: wrong answer len for cmd BC: expected = 5, got 3
> Opened rig model 217, 'TH-D7A'
> Backend version: 0.4, Status: Alpha

It looks like a plain echo, which is unusual for a kenwood protocol.
Since this rig has advanced APRS builtin, I'm wondering whether ttyUSB0
is the terminal for the APRS console or maybe GPS. Could it be two
serial-over-USB devices are provided by the TH-D72A ? What happends when
you replace /dev/ttyUSB0 by /dev/ttyUSB1 ?

Can you please send the result of the "lsusb -v" on your system?
Maybe the result of the command "dmesg" could be useful too.

If you are accustomed to serial terminals like minicom, gtkterm, ..,
you may try to guess the right port/protocol by connecting at 9600 8N1,
no handshake. Try commands like FQ<return> or FA<return> or FV 0<return>
or ID<return>  etc..
Look also in the menus, maybe specific mode has to be set 
for the serial interface to act as remote control, like hinted below
http://www.mail-archive.com/xa...@li.../msg04888.html

Are you Ubuntu user? Make sure you're not running the Natty kernel,
the Maverick kernel is reported[1] to be fine for cp210x driver.
[1] http://vernon.mauery.com/content/programming/kenwood_th-d72_and_linux

Still according to [1], the packet TNC has to be disabled on the rig.

Hope this helps..
-- 
Stephane - F8CFE