Re: [Hamlib-developer] Rigctl status output on FT-920

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

Hi Nate!

On Sun, Oct 27, 2002, Nate Bargmann wrote:
> merlin:~/test/hamlib $ rigctl -vvvvv -r /dev/ttyS0 -m 114
> rigctl, Hamlib version 1.1.4-cvs
[..]
> ft920:ft920_init called 
> rig:rig_open called 
> ft920:rig_open: write_delay = 50 msec 
> ft920:rig_open: post_write_delay = 5 msec 
> ft920: read pacing = 0 
> TX 5 bytes
> 0000     00 00 00 03 10 .....
> RX 28 bytes
> 0000     09 00 3b d8 50 00 00 00 00 10 00 00 00 00 0b 00
> ..;.P...........
> 0010     6e 04 10 00 00 00 00 00 00 00 00 00
> n...........
> ft920: vfo status = 8 
> ft920: VFO = B 
> Opened rig model 114, 'FT-920'
> Backend version: 0.0.1, Status: Alpha

Hey! it's comunicating already!

[..] 
> According to the manual, the returned data for the first six bytes is as
> follows:

be careful of the manuals, sometimes mistakes hide in there. Never trust
them, test each command one by one. And I know what I'm talking about,
this was part of my job when I used to work with STM in Phoenix,AZ.

> 
> Byte 1		Band data (undocumented, but seems to start at 06 for
> 		160m, 09 for 75m, and 09 for 40m.)
> 
> Bytes 2 - 5	Operating frequency in hex.  in the first 14 byte
> 		segment above, 00 3b d8 50 works out to 3.922000 MHz
> 
> My terrible looking ft920.c and .h will be committed shortly.  All
> corrections welcome.

I'm pretty sure some beta-testers will show up. Luc LX2GT will be one of
them (for the FT990 also I think)

> P.S.  The good news for me as that after mucking around the code
> compiles, the software at least can send a simple command to the radio
> and get a reply it doesn't yet understand, and the radio hasn't locked 
> up.  What did I do wrong?

If you cloned ft847.c, you might have to modify/rewrite 
your own get_freq_and_mode.

You've done the harder part. Once your code is committed, we should be
able to help you. Surely, it's going to make it for the arrlss!

73
Stephane