hamlib-developer

[Hamlib-developer] Possible rotctl bug with the Yaesu G232B interface

[Azelio B. <aze...@gm...>]

May I report a possible problem with rotctl when using the G232B? (on
Ubuntu 14.04)

Rotator command: P
Azimuth: 100
Elevation: 55
gs232b_rot_set_position called: 100.000000 55.000000
write_block(): TX 9 bytes
0000    57 31 30 30 20 30 35 35 0d                          W100 055.
read_string(): Timed out 0.400458 seconds without reading a character.
write_block(): TX 9 bytes
0000    57 31 30 30 20 30 35 35 0d                          W100 055.
read_string(): Timed out 0.400447 seconds without reading a character.
write_block(): TX 9 bytes
0000    57 31 30 30 20 30 35 35 0d                          W100 055.
read_string(): Timed out 0.400451 seconds without reading a character.
write_block(): TX 9 bytes
0000    57 31 30 30 20 30 35 35 0d                          W100 055.
read_string(): Timed out 0.400444 seconds without reading a character.
set_pos: error = Communication timed out

Rotator command:

The G232B is supposed to send only a CR after the W command: is it my
serial port settings that prevents the CR from getting thru or have I
found a bug?
Thank you

Re: [Hamlib-developer] Possible rotctl bug with the Yaesu G232B interface

[Bill S. <g4...@cl...>]

On 14/04/2016 13:45, Azelio Boriani wrote:
> May I report a possible problem with rotctl when using the G232B? (on
> Ubuntu 14.04)
>
> Rotator command: P
> Azimuth: 100
> Elevation: 55
> gs232b_rot_set_position called: 100.000000 55.000000
> write_block(): TX 9 bytes
> 0000    57 31 30 30 20 30 35 35 0d                          W100 055.
> read_string(): Timed out 0.400458 seconds without reading a character.
Hi Azelio,

that looks like a simple communications error. Maybe the wrong serial 
port or wrong baud rate. What was the command you ran to start rotctl?

73
Bill
G4WJS.