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

[Nate B. <n0...@ne...>]

Well, at least rigctl is talking to the radio, although the returned
data seems to be different enough from other Yaesu models that rigctl is
confused.  Here's an example:

merlin:~/test/hamlib $ rigctl -vvvvv -r /dev/ttyS0 -m 114
rigctl, Hamlib version 1.1.4-cvs
Report bugs to <ham...@li...>

rig:rig_init called 
rig: loading backend yaesu
yaesu: _init called
rig_register (105)
rig_register (120)
rig_register (101)
rig_register (121)
rig_register (114)
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

Rig command: f
ft920:ft920_get_freq called 
ft920: read pacing = 0 
TX 5 bytes
0000     00 00 00 00 0e .....
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:  freq = 10000000 Hz  for VFO = 129 
Frequency: 10000000

-----------------------------------------------------------------

Opcode of 10, P1 of 03 is telling the '920 to return two fourteen byte
records, one for VFO A and the other for VFO B.

According to the manual, the returned data for the first six bytes is as
follows:

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.

73, de Nate >>

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?

-- 
 Wireless | Amateur Radio Station N0NB          | "We have awakened a
 Internet | n0...@ne...               | sleeping giant and
 Location | Bremen, Kansas USA EM19ov           | have instilled in him
  Amateur radio exams; ham radio; Linux info @  | a terrible resolve".
             http://www.qsl.net/n0nb/           | - Admiral Yamomoto