hamlib-developer

[Hamlib-developer] Hi

[John R. <j0...@ts...>]

Hi,
I just came across hamlib, if I get time over xmas I'll try and test the Aor 8200 support. I may be able to help with FT1000 support after that.

Regards
John


-- 
John Ronan <j0...@ts...>, +353-51-302938
Telecommunications Software Systems Group - WIT, http://www.tssg.org

Re: [Hamlib-developer] Hi

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

On Wed, Dec 19, 2001, John Ronan wrote:
> I just came across hamlib, if I get time over xmas I'll try and test the Aor 8200 support. I may be able to help with FT1000 support after that.
 
Great! the AR-8200 as never been tested. Anyway, let me know how it works
for you, I can help if you need, and please report with rigtctl -vvvv
traces so I can fix it.
Patches or CVS commits welcome too!

Cheers,
Stephane F8CFE 

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

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

Hi John!

On Mon, Jan 07, 2002, John Ronan wrote:
> Sorry about talking so long to reply... I tried rigctl and no commands
> seemed to complete succesfully.. (hamlib version 1.1.2). I"m travellinga
> lot at the moment... so I do apologise for not haveing more information.

You don't have to apologise, we're all hacking Hamlib on spare time.
There's no hurry, no stress, just fun!
And btw, your report is very interresting. This is the first time ever 
I see Hamlib traces to an AOR receiver. And It's somehow not so bad!
This give me a better idea on the AOR protocol, what works, 
what doesn't :)     I clearly see where some fixes are needed.

Quick question: did testrig succeeded in changeing some paramters (freq,
mode) ?
Also, are you familiar with CVS? This is to know if you can test
directly from cvs checkouts, or if you prefer me to roll you snapshot
tarballs.  You would benefit from (i.e. be able to test) latest fixes
Development version of rigctl works fine, and is much more versatile than
testrig.

Anyway, thank you very much for your report and your time,

Cheers,
Stephane

> ./testrig 501 -vvvv
> testrig:hello, I am your main() !
> rig:rig_init called
> rig: loading backend aor
> aor: _init called
> rig_register (501)
> rig:rig_open called
> Port /dev/ttyS0 opened ok
> rig_set_vfo: error = Feature not available
> TX 12 bytes
> 0000     52 46 30 30 32 38 33 35 30 31 32 35    RF0028350125
> TX 1 bytes
> 0000     0a     .
> fread_block: timedout after 0 chars
> TX 3 bytes
> 0000     4d 44 36       MD6
> TX 1 bytes
> 0000     0a     .
> RX 1 bytes
> 0000     3f     ?
> TX 12 bytes
> 0000     52 46 30 30 32 31 32 33 35 31 37 35    RF0021235175
> TX 1 bytes
> 0000     0a     .
> RX 1 bytes
> 0000     0a     .
> TX 3 bytes
> 0000     4d 44 33       MD3
> TX 1 bytes
> 0000     0a     .
> RX 1 bytes
> 0000     0a     .
> TX 12 bytes
> 0000     52 46 30 30 30 30 37 37 30 30 30 30    RF0000770000
> TX 1 bytes
> 0000     0a     .
> RX 1 bytes
> 0000     3f     ?
> TX 3 bytes
> 0000     4d 44 32       MD2
> TX 1 bytes
> 0000     0a     .
> RX 1 bytes
> 0000     0a     .
> TX 12 bytes
> 0000     52 46 30 30 30 37 32 35 30 31 30 30    RF0007250100
> TX 1 bytes
> 0000     0a     .
> RX 1 bytes
> 0000     0a     .
> TX 3 bytes
> 0000     4d 44 34       MD4
> TX 1 bytes
> 0000     0a     .
> RX 1 bytes
> 0000     3f     ?
> TX 12 bytes
> 0000     52 46 30 30 30 33 39 38 30 30 30 30    RF0003980000
> TX 1 bytes
> 0000     0a     .
> RX 1 bytes
> 0000     0a     .
> TX 3 bytes
> 0000     4d 44 32       MD2
> TX 1 bytes
> 0000     0a     .
> RX 1 bytes
> 0000     0a     .
> TX 12 bytes
> 0000     52 46 30 30 30 31 38 37 35 30 30 30    RF0001875000
> TX 1 bytes
> 0000     0a     .
> RX 1 bytes
> 0000     3f     ?
> TX 3 bytes
> 0000     4d 44 35       MD5
> TX 1 bytes
> 0000     0a     .
> RX 1 bytes
> 0000     0a     .
> TX 3 bytes
> 0000     4d 44 35       MD5
> TX 1 bytes
> 0000     0a     .
> RX 1 bytes
> 0000     0a     .
> TX 12 bytes
> 0000     52 46 30 30 31 34 32 35 30 33 37 35    RF0014250375
> TX 1 bytes
> 0000     0a     .
> RX 1 bytes
> 0000     3f     ?
> rig_set_freq: error = Target VFO unaccessible
> TX 3 bytes
> 0000     4d 44 34       MD4
> TX 1 bytes
> 0000     0a     .
> RX 1 bytes
> 0000     0a     .
> rig_set_mode: error = Invalid parameter
> rig_set_ptt: error = Feature not available
> rig_set_ptt: error = Feature not available
> rig_get_vfo: error =  Feature not available
> TX 2 bytes
> 0000     52 58  RX
> TX 1 bytes
> 0000     0a     .
> RX 1 bytes
> 0000     0a     .
> rig_get_freq: error =  Invalid parameter
> TX 2 bytes
> 0000     4d 44  MD
> TX 1 bytes
> 0000     0a     .
> RX 1 bytes
> 0000     3f     ?
> rig_get_mode: error =  Invalid parameter
> rig_get_strength: error =  Feature not available
> rig:rig_close called
> TX 2 bytes
> 0000     45 58  EX
> TX 1 bytes
> 0000     0a     .
> RX 1 bytes
> 0000     0a     .
> rig:rig_cleanup called
> port /dev/ttyS0 closed ok

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