Re: AOR report, was Re: [Hamlib-developer] Hi

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

Hi John!

There we go! I've fixed couple of things in the aor backend and commited
it to the cvs rep. There's still no func/level/parm support yet, but I
hope the freq/mode/vfo work better.

Quick reminder for anonymous cvs access to hamlib rep: 

cvs -d:pserver:ano...@cv...:/cvsroot/hamlib login
cvs -z3 -d:pserver:ano...@cv...:/cvsroot/hamlib \
	co hamlib

Eventualy, you may have to set LD_LIBRARY_PATH to the directory where the
backend plugins sit.

You can give testrig a shot (with traces sent by mail).
But rigctl is more interresting to me.
Start it with "rigctl -m 501 -vvvv", and then the commands available are
the following:

f,F	get_freq/set_freq	try various (<1MHz, <30Mhz and >1GHz)
v,V	get_vfo/set_vfo		VFOA, VFOB
m,M	get_mode/set_mode	FM, USB, LSB, CW, WFM, etc.
				passband is in Hz (pass 0 for default)
G	vfo_op			UP, DOWN
_	get_info		should give remote Id and firmware vers


Please, let me know also if the commands issued by Hamlib have the
expected effect on the AOR receiver. From your previous traces, it looks
like the rig accepted some, and some others are still a mistery to me...


Cheers,
Stephane