Thread: [Hamlib-developer] Rigctl status output on FT-920
Library to control radio transceivers and receivers
Brought to you by:
n0nb
Menu
▾
▴
hamlib-developer
|
From: Nate B. <n0...@ne...> - 2002-10-28 04:40:35
|
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
|
|
From: Stephane F. <f8...@fr...> - 2002-10-28 22:56:13
|
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 |
|
From: Robert <ro...@st...> - 2002-10-28 23:56:24
|
Hi all, I'm still alive ;-) > I'm pretty sure some beta-testers will show up. Luc LX2GT will be one o= f > them (for the FT990 also I think) Once I ever make it so far, I'll be testing IC275/475 and FT990... if my = mom=20 doesn't sell those TRX til then...=20 73, Robert |
|
From: Stephane F. <f8...@fr...> - 2002-10-29 23:46:33
|
On Sun, Oct 27, 2002, Nate Bargmann wrote: > 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.) you're right, it appears undocumented. However, Hamlib probably won't ever need it. > Bytes 2 - 5 Operating frequency in hex. in the first 14 byte > segment above, 00 3b d8 50 works out to 3.922000 MHz okay, it's no big-endian BCD like the ft847. This is plain 32 bits big-endian integer. I've commited something for ft920_get_freq, can you give it a try and tell me what you get (with comm traces, I have no yeasu). If you need any other special commands for arrlss, let me know. 73 Stephane |
|
From: Nate B. <n0...@ne...> - 2002-10-30 03:53:52
|
* Stephane Fillod <f8...@fr...> [2002 Oct 29 17:49 -0600]:
Darn!
I just spent the entire evening banging on this too and got it working.
Only to have CVS pop up an error that I didn't understand. Now you beat
me to the punch...Oh well, collabrative development. :-)
Now, my code sits here viewable only by little ol' me...
> you're right, it appears undocumented. However, Hamlib probably won't
> ever need it.
I agree. It appears we can safely discard the first byte of each
record.
> > Bytes 2 - 5 Operating frequency in hex. in the first 14 byte
> > segment above, 00 3b d8 50 works out to 3.922000 MHz
>
> okay, it's no big-endian BCD like the ft847. This is plain 32 bits
> big-endian integer.
Yup.
> I've commited something for ft920_get_freq, can you give it a try and
> tell me what you get (with comm traces, I have no yeasu).
> If you need any other special commands for arrlss, let me know.
I verified that *my* version will both get and set the frequency. :)
Setting the frequency required no changes.
I'd like to keep banging on this as I'm getting a nice handle on things
now. So, I guess I'll have to look at your file and mine and decide
which I like better, merge them and then see what works.
I would have gotten this done sooner but had a fire dept training
session last night. Full gear, air pack, and flames in a confined
space. Fun stuff!
73, de Nate >>
--
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
|
|
From: Nate B. <n0...@ne...> - 2002-10-30 13:00:10
|
Hi Stephane.
I tested and confirmed your code works with my '920. Of course, yours
is much cleaner and more concise than what I came up with. :-)
I had already made a number of other changes to ft920.c and .h, so I
will merge the files and commit them this evening. I intend to continue
work on the 920 and implement the remaining functions already declared.
Then I hope to move on and flesh things out the rest of the way.
I'm still getting my head around all the Hamlib data structures so that
is taking most of my time--learning the program flow and data
manipulation.
What a thrill to see the correct frequency show up on my screen. I
should have done this years ago!
73, de Nate >>
--
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
|
Thanks for helping keep SourceForge clean.
X