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