Re: [Hamlib-developer] Greetings!

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

On Mon, Jan 01, 2001 at 09:24:54PM -0600, Frank Singleton wrote:
> 
> Documentation help always welcome. !! A web page for our site
> would be cool..

I noticed the project didn't have one, so I guess that's why I
volunteered.  The web pages could contain hamlib's API along with items
like rig capabilities along with command syntax for each rig so it would
be in one place.  They could also serve as a starting point for formal
documentation included in the library distribution.

> Good, I am rationalising the yeasu code at the moment, and
> it would be good to see the CAT docs etc.. 
> 
> You would be most welcome to join us. The fun part is to tweek
> some code, then make sure you can still talk to your rig :-)

Of course!

> I am moving yaesu stuff to table driven functionality.
> see ft747 and ft847 for examples. I am in transit with this
> code, but I am sure you get the idea :^)

I looked at both the 747 and 847.c files and it looks rather
straightforward(!) when comparing them to the CAT info I have.
Hopefully, I can begin to work on this for the '920 later in the week.

> CAT docs are needed, but the FIF-232 could be replaced with
> a cheaper kit based on max232 chip.
> 
> Normally this just converts between TTL levels and RS232
> levels.

I built one for a TS-850 I no longer have, but the rig acted flaky with
it, so I'm not sure if the problem was in the interface or the '850.

> 2 points.
> 
> 1. The API is WIP this why we need comments by
>    people other than the 2 current members. We should
>     have a standard API as a minimum and get it out there
>    in WIDE use. .... and ...
>    
> 2. Yep, some generic way of broadcasting "extra" capabilities and
>    using some enhancements is always possible.

I can always comment. :-O

> That why we want people on the list, to chew through these 
> ideas ..

ditto!

> Yep thats ok, I promise not to jump to v7.0 (hi hi)

Harr!  One thing, and I think this was in the archive, I think should be
followed is the Linux kernel example of an odd minor version number
indicating a development version as it has become common convention for
open source projects.

> Again, you would be most welcome, and the extra rigs we could
> test and develop against is most valuable in getting a wider
> audience for both hamlib development, and end user developers
> using hamlib to create cool stuff (see our wishlist).
> 
> So, just to clarify, I understand you  can help us with
> web and docs, THANKS. Are you willing to code up some backends
> for your rigs. I can provide some help if required.

Yes, I can pitch in.  Time is always a precious commodity, but I usually
have a few hours each evening available to do things.  I enjoy HTML and
CSS and prefer to write my pages from scratch conformant to the W3C HTML
4.01 Transitional DTD.

> You can use FT747 code as example, to map frontend
> API function calls onto backend rig specific CAT
> sequences. see yaesu.h and ft747.[ch]

I will definitely look those over.  I've looked at the '920 CAT commands
in the owner's manual, so this should be interesting.

> Can you join the sourceforge community, then I will add
> you to our project.

No problem.  I'll have to poke around there and see what needs to be
done.

73, de Nate >>

-- 
 Wireless | Amateur Radio Station N0NB          | "None can love freedom
 Internet | n0...@ne...               | heartily, but good
 Location | Wichita, Kansas USA EM17hs          | men; the rest love not
   Wichita area exams; ham radio; Linux info @  | freedom, but license."
             http://www.qsl.net/n0nb/           | -- John Milton