Re: [Hamlib-developer] AR8600 Mark2 Troubleshooting...

[<si...@ta...>]

Hi, 
I've been using Hamlib with my AORs for years, although maybe not on the latest builds.The "communications on" dot may be misleading as it tends to appear any 
time the radio senses activity on the port, even if not at the right 
speed or encoding.
In same cases I've seen it come up a pc boot time.Excuse me if I'm suggesting obvious things, but you didn't mention if computer control is working ok with other software.Are you able to talk directly to the radio using a terminal emulator? Minicom will do under Linux and is normally available in all repositories.
Set up the terminal at the same speed you have on the radio (4800 I understand) with 8 bits data, no parity, 1 bit stop. 
Connect and issue a command such as "RX"  (capital letters!) followed by the return key.
If you get a reply on the screen you've got comms.When all parameters are ok you get a string will the current frequency, vfo and other stuff.If you get a "?" something with the command or parameters are wrong.
Garbled characters may come up in case of wrong parameters. 
 
73 
S 
 
 
Da: "Trey Keifer" li...@ha...
A: ham...@li...
Cc: 
Data: Tue, 18 Oct 2011 19:21:32 -0500
Oggetto: [Hamlib-developer] AR8600 Mark2 Troubleshooting...



Hello all,> 
> Trying to get hamlib to work with an AOR 8600 Mark2 receiver and having some troubles. I can connect via rigctl (it shows the serial icon on the LCD of the receiver) but any command I send returns the following error message:
> 
> > Rig command: f
> get_freq: error = Communication timed out
> 
> Full dump with verbose logging on is as follows:
> 
> > [user@localhost /]# rigctl -vvvvvv -m 513 -r /dev/ttyUSB0 -s=4800
> rigctl, Hamlib 1.2.12
> Report bugs to <ham...@li...>
> 
> rig:rig_init called 
> rig: loading backend aor
> aor: _init called
> rig_register (508)
> rig_register (501)
> rig_register (502)
> rig_register (513)
> rig_register (504)
> rig_register (506)
> rig_register (503)
> rig_register (505)
> rig_register (514)
> rig_register (515)
> rig:rig_open called 
> TX 3 bytes
> 0000    52 58 0d                                           RX.
> read_string: timedout without reading a character
> Opened rig model 513, 'AR8600'
> Backend version: 0.6.1, Status: Beta
> 
> Rig command: f
> TX 3 bytes
> 0000    52 58 0d                                           RX.
> read_string: timedout without reading a character
> get_freq: error = Communication timed out
> 
> Rig command: 
>