LIbrary for Amateur Radio Equipment Control Applications.
 
 
 
 
 
 
Go to file
Stéphane Fillod, F8CFE 16dd038887 * first attempt at having a combined command line and interactive utility,
that is able to perform single Hamlib API calls. For maintenance reasons,
  both interfaces are combined. Work is not complete yet, but it works!
  The "dummy" rig backend proved to be helpful in that regard :-)
  More API calls are to come, and also a man page for the command line,
  and explanations about the short/long options triggering calls.
  FIXME: API calls requesting more than one argument are not working yet
  (still have to figure out how getopt can accept more than one arg for one
  option...)


git-svn-id: https://hamlib.svn.sourceforge.net/svnroot/hamlib/trunk@400 7ae35d74-ebe9-4afe-98af-79ac388436b8
2001-02-25 23:14:19 +00:00
aor * update after API modification (new fields, KHz -> kHz) 2001-02-14 23:54:21 +00:00
doc * add missing files. Hopefuly, checkouts should compile fine now. 2001-02-14 01:01:34 +00:00
dummy * started to be more verbose in API calls, still much work to do 2001-02-14 23:57:30 +00:00
ft747
ft847
icom * added icom_get_dcd 2001-02-14 23:55:54 +00:00
include * added RIG_LEVEL_IS_FLOAT macro to known which levels are of float type, 2001-02-25 23:06:18 +00:00
kenwood * update after API modification (new fields, KHz -> kHz) 2001-02-14 23:54:21 +00:00
lib
src * enabled dcd state retrieval code 2001-02-15 00:00:11 +00:00
tests * first attempt at having a combined command line and interactive utility, 2001-02-25 23:14:19 +00:00
winradio * update after API modification (new fields, KHz -> kHz) 2001-02-14 23:54:21 +00:00
yaesu * update after API modification (new fields, KHz -> kHz) 2001-02-14 23:54:21 +00:00
API
AUTHORS
COPYING
ChangeLog
INSTALL
LICENSE * welcome in the new millenium\! 2001-02-11 23:10:23 +00:00
Makefile.am * added new 'dummy' backend, for debugging purpose mainly 2001-02-14 01:02:39 +00:00
Makefile.in * add missing files. Hopefuly, checkouts should compile fine now. 2001-02-14 01:01:34 +00:00
NEWS
PLAN
README
README.developer
THANKS * credits 2001-02-11 22:50:35 +00:00
TODO
TODO.skeleton
aclocal.m4 * regenerated 2001-02-09 23:02:09 +00:00
config.guess
config.sub
configure * regenerated (new backend) 2001-02-14 01:04:20 +00:00
configure.in * added new 'dummy' backend\n* misc update 2001-02-14 01:03:42 +00:00
cvs2cl.pl
install-sh
ltconfig
ltmain.sh
missing
mkinstalldirs

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.libhamlib-ft747.so will provide connectivity to Yaesu
  FT 747GX Transceiver via a standard API.

2. libhamlib-ft847.so will provide connectivity to Yaesu FT 847
   "Earth Station" via a standard API.
 
3. libhamlib-xxxx.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