hamlib-developer

[Hamlib-developer] hamlib and TS870

[Joop S. <pa...@de...>]

Hello Stephane and others,

I have tried to use rigctl with my TS-870. According to the menu on
the TS-870, communication is set to 9600 bps with 1 stopbit. I have
tried with the default com-port settings on my linux-box and with
'setserial /dev/ttyS0 baud_base 9600'. Both with the same results:

aba@pc3:~$ rigctl -m 210
fread_block: timedout after 0 chars

[ctrl led on the rig switches on]

Rig command: f
fread_block: timedout after 0 chars
Frequency: 4611874313014867991get_freq: error = Communication timed out

Rig command: F 14.023
Frequency: fread_block: timedout after 0 chars
set_freq: error = Communication timed out

Rig command: q
aba@pc3:~$


Do I need to dive into the source code? Did I overlook something?
Thanks,

Joop PA4TU

Re: [Hamlib-developer] hamlib and TS870

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

On Sun, Dec 09, 2001, Joop Stakenborg wrote:
> Hello Stephane and others,
> 

Hi Joop,

> I have tried to use rigctl with my TS-870. According to the menu on
> the TS-870, communication is set to 9600 bps with 1 stopbit. I have
> tried with the default com-port settings on my linux-box and with
> 'setserial /dev/ttyS0 baud_base 9600'. Both with the same results:
> 
> aba@pc3:~$ rigctl -m 210
> fread_block: timedout after 0 chars
> 

Can you run rigctl with "-vvvvv" option and report the traces please?
This will tell us what's Hamlib is doing, and what characters are
exchanged on the serial line. 

Eventually, if you suspect a problem with the serial cable, you may try to
talk directly to the rig with minicom, and issue simple commands like 
'ID'.

> [ctrl led on the rig switches on]
> 
This is a goood sign anyway.

> Do I need to dive into the source code? Did I overlook something?

Not necessarily. This is just this backend has never been tested :-)

Cheers,

Stephane F8CFE

Re: [Hamlib-developer] hamlib and TS870

[Joop S. <pa...@de...>]

On Sun, 9 Dec 2001 14:58:55 +0100
Stephane Fillod <f4...@fr...> wrote:

> On Sun, Dec 09, 2001, Joop Stakenborg wrote:
> 
> Can you run rigctl with "-vvvvv" option and report the traces please?
> This will tell us what's Hamlib is doing, and what characters are
> exchanged on the serial line. 
> 

aba@pc3:~$ rigctl -vvvvv -m 210 
rig:rig_init called 
rig: loading backend kenwood
kenwood: _init called
rig_register (203)
rig_register (204)
rig_register (216)
rig_register (210)
rig:rig_open called 
TX 3 bytes
0000	 46 52 3b	FR;
RX 1 bytes
0000	 d2	.
RX 1 bytes
0000	 fb	.
fread_block: timedout after 0 chars
Opened rig model 210, 'TS-870S'

Rig command: f
TX 3 bytes
0000	 46 52 3b	FR;
RX 1 bytes
0000	 d3	.
RX 1 bytes
0000	 fb	.
fread_block: timedout after 0 chars
Frequency: 4611874313014867991get_freq: error = Communication timed out

Rig command: F 14.000
TX 3 bytes
0000	 46 52 3b	FR;
Frequency: RX 1 bytes
0000	 92	.
RX 1 bytes
0000	 fb	.
fread_block: timedout after 0 chars
set_freq: error = Communication timed out

Rig command: q
rig:rig_close called 
rig:rig_cleanup called 
aba@pc3:~$


> Eventually, if you suspect a problem with the serial cable, you may try to
> talk directly to the rig with minicom, and issue simple commands like 
> 'ID'.
> 

The serial line is OK, I have tested it with a modem. It is a 9 wire
cable to a 9 pin connector at both ends.
I have tried to talk to my transceiver with minicom, but I never get
anything back, whatever communication parameter I try.
From the tests I get the impression that serial line speeds do not match
the communication paramaters of the transceiver.
is this correct?

Maybe I should give kontakt a try.....

Joop

Re: [Hamlib-developer] hamlib and TS870

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

On Sun, Dec 09, 2001, Joop Stakenborg wrote:
> aba@pc3:~$ rigctl -vvvvv -m 210 
> TX 3 bytes
> 0000	 46 52 3b	FR;
> RX 1 bytes
> 0000	 d2	.
> RX 1 bytes
> 0000	 fb	.
> fread_block: timedout after 0 chars
> Opened rig model 210, 'TS-870S'
> 

FR; command should retrieve current VFO (kenwood/kenwood.c:kenwood_get_vfo)
However, the kenwood protocol does not use 8 bits characters, which
is rather suspect. Anyway, it seems to receive something since it tries
to reply (certainly an error code, but with wrong speed?).

> I have tried to talk to my transceiver with minicom, but I never get
> anything back, whatever communication parameter I try.

Maybe trying with some other known-to-work CAT program would help.
Easy to find under DOS/win32, not so easy under Linux...

> >From the tests I get the impression that serial line speeds do not match
> the communication paramaters of the transceiver.
> is this correct?

This could be the most reasonable explanation. Have you tried playing
with speed/handshake/parity/number of data and stop bits/ etc. ?
Reading kenwood/ts870s.c, it looks like Hamlib is setting up the serial
port to 57600bps, 8N1, no parity.
Maybe the TS-870 cannot cope with too high speed?

Note: whatever speed value you setup the port, Hamlib reconfigures it.
So the TS-870 should be setup to 57600bps.

> Maybe I should give kontakt a try.....

I'm afraid you won't have more luck since kontakt is based on Hamlib.
However, I'm almost sure Robert would be happy to have some feedback
on his development.

Please, let me know if the speed setup can help in solving your problem.

73, 
Stephane F8CFE