hamlib-developer

[Hamlib-developer] Rig identification / source code location

[Orv B. <w6...@pa...>]

OK, so it's not tomorrow yet, and I promised not to ask another question
today, but maybe it is where you're reading this, and I just have to
ask.  :-)

I have a TenTec Omni VI Plus.  HOWEVER - in the tentec directory, there
are only two radios coded, the rx320, and the pegasus. By grepping for
Omni in the source, I find the omni.c file (clearly identified as the
TenTec Omni VI Plus within the source code), in the Icom subdirectory.

That probably explains why, when running rigctl, it identifies it as an
Icom radio.  It might also explain why only a few of the commands worked
when going through them with rigctl.

Now it's true that Icom has a radio called the Omni, but it's pretty
clear that the file omni.c isn't for it.

Should I just move omni.c into the tentec dir and recompile?  Or is
there more to it than that?

Thanks for bearing with me.

73 - Orv - W6BI
-- 
Orv Beach <w6...@pa...>

Re: [Hamlib-developer] Rig identification / source code location

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

* Orv Beach <w6...@pa...> [2003 Jan 10 22:21 -0600]:
> I have a TenTec Omni VI Plus.  HOWEVER - in the tentec directory, there
> are only two radios coded, the rx320, and the pegasus. By grepping for
> Omni in the source, I find the omni.c file (clearly identified as the
> TenTec Omni VI Plus within the source code), in the Icom subdirectory.

Okay, I'm getting well out of my field of knowledge here, but the TT
Omni apparently uses the ICOM CI-V protocol.

> Should I just move omni.c into the tentec dir and recompile?  Or is
> there more to it than that?

Probably not until you do some preparation!

At a minimum you will have to change some #include path names and also
make some changes in the Makefile.am in each directory then rebuild the
project as though builing from CVS.  See README.betatester.

In some cursory glances in that part of the project, I'm guessing that 
the functions in omni.c rely on the common icom.c file.

Knock yourself out, it's the only way we learn.  ;-)

> Thanks for bearing with me.

My bearings are pointing me toward bedtime!

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 Yamamoto

Re: [Hamlib-developer] Rig identification / source code location

[Orv B. <or...@or...>]

Okay, I got a handle on it now.  I untarred it fresh and recompiled it,
and you're right, Nate.

It's confusing to have the radios sorted by directories named by brand,
when they're actually sorted by protocol  :-(

Nate, you were right, once I found the right radio file, and determined
that the max serial port speed of the TT Omni VI Plus was 19200, I set
the radio to that and rigctl was able to communicate with the radio
without defining the serial port speed on the command line.  Sheesh...

Then I went on to Gnome rig, which still wasn't working.  A bit of
playing around seemed to show that even though you can set the serial
port in the config file (via the UI), it apparently isn't using it.  It
started working when I changed the serial port in defaults.h from ttyS1
to ttyS0 and recompiled.  I'll let them know.

I'll compile a list of radio functions via rigctl that don't seem to
work and post them in a while.

Thanks for your help, Nate!

And now, I'm pulling the plug for the night, too...

73 - Orv - W6BI

On Fri, 2003-01-10 at 20:33, Nate Bargmann wrote:
> * Orv Beach <w6...@pa...> [2003 Jan 10 22:21 -0600]:
> > I have a TenTec Omni VI Plus.  HOWEVER - in the tentec directory, there
> > are only two radios coded, the rx320, and the pegasus. By grepping for
> > Omni in the source, I find the omni.c file (clearly identified as the
> > TenTec Omni VI Plus within the source code), in the Icom subdirectory.
> 
> Okay, I'm getting well out of my field of knowledge here, but the TT
> Omni apparently uses the ICOM CI-V protocol.
> 
> > Should I just move omni.c into the tentec dir and recompile?  Or is
> > there more to it than that?
> 
> Probably not until you do some preparation!
> 
> At a minimum you will have to change some #include path names and also
> make some changes in the Makefile.am in each directory then rebuild the
> project as though builing from CVS.  See README.betatester.
> 
> In some cursory glances in that part of the project, I'm guessing that 
> the functions in omni.c rely on the common icom.c file.
> 
> Knock yourself out, it's the only way we learn.  ;-)
> 
> > Thanks for bearing with me.
> 
> My bearings are pointing me toward bedtime!
> 
> 73, de Nate >>
-- 
Orv Beach <or...@or...>