Hamlib

LIbrary for Amateur Radio Equipment Control Applications.

Go to file

Stéphane Fillod, F8CFE e93ee7c51a Moved frame handling to frame.c Renamed bcd2freq/freq2bcd to from_bcd/to_bcd Coded and tested icom_get_freq Made use of generic icom_transaction git-svn-id: https://hamlib.svn.sourceforge.net/svnroot/hamlib/trunk@170 7ae35d74-ebe9-4afe-98af-79ac388436b8		2000-10-01 12:37:10 +00:00
common	better libhamlib.so version :-)	2000-09-29 03:33:58 +00:00
ft747	starting to implement set/get pairs	2000-09-24 03:36:47 +00:00
ft847	* empty log message *	2000-09-23 03:49:13 +00:00
icom	Moved frame handling to frame.c	2000-10-01 12:37:10 +00:00
src	Moved from ../common	2000-10-01 12:29:12 +00:00
API	file creation, basically scratch notes	2000-09-14 00:48:00 +00:00
COPYING	file creation, basically scratch notes	2000-09-14 00:48:00 +00:00
INSTALL	Initial revision	2000-07-18 21:35:26 +00:00
Makefile	removed "make verify". Added reference to common/Makefile	2000-09-25 00:02:11 +00:00
PLAN	* empty log message *	2000-09-16 01:08:32 +00:00
README	describe frontend/backend structure	2000-09-24 02:15:52 +00:00
README.developer	updated code snippet example	2000-09-24 02:19:42 +00:00
README.license	included full GPL license	2000-08-19 16:21:23 +00:00
THANKS	Initial release	2000-09-19 07:02:20 +00:00
TODO	some work has been done, but there's more to do!	2000-09-16 01:09:51 +00:00
TODO.skeleton	Initial revision	2000-07-18 20:55:08 +00:00

README

hamlib - (C) Frank Singleton 2000 (vk3fcs@ix.netcom.com)

The purpose of this project is to provide stable, flexible,
shared libraries that enable quicker development of Amateur
Radio Equipment Control Applications.
 
Many Amateur Radio Transceivers come with serial interfaces
that allows software to control the radio. This project will
endeavour to provide shared libraries that greatly simplify
the application programmers interaction with radio equipment.
 

The shared libs will provide functions for both radio control,
and data retrieval from the radio.
 
The structure of the libraries will be as follows.

(1)	There will be 1 frontend library "libhamlib" that
	provides the generic API for user applications.

(2)	There will be "n" backend libraries that "wrap" 
	rig specific communications inside frontend API.

(3)	Frontend lib will load (on demand) the appropriate
	backend lib as required. 

Frontend Library
----------------

libhamlib.so -  frontend lib that provides generic API
		for all RIG types. This is what Application
		programmers will "see"

Backend Examples are:
---------------------
 
1.libft747.so will provide connectivity to Yeasu
  FT 747GX Transceiver via a standard API.

2. libft847.so will provide connectivity to Yaesu FT 847
   "Earth Station" via a standard API.
 
3. libxxxx.so will provide connectivity to the Wiz-bang
   moon-melter 101A (yikes..)

Hamlib will also enable developers  to develop
professional looking GUI's towards a standard control library
API, and they would not have to worry about the underlying
connection towards physical hardware.
 
Initially serial (RS232) connectivity will be handled, but
I expect that IP (and other) connectivity will follow afterwards. 


Take a look at README.developer for more info.

Also, take a look at http://sourceforge.net/projects/hamlib/
Here you will find a mail list, and  the latest CVS releases.

Have Fun / Frank S. 

  73's de vk3fcs/km5ws