LIbrary for Amateur Radio Equipment Control Applications.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Mike Black W9MDB 4dbce1a0aa Add setvbuf to rigctl.c and rigctld.d to overcome non-buffering of stderr on mingw builds. 3 days ago
.github Debugging README in github build 4 months ago
amplifiers astyle files for 4.5 release 2 months ago
android astyle files for 4.5 release 2 months ago
bindings Fix spelling errors 3 months ago
c++ Change all to remove HAVE_CONFIG dependency and include <hamlib/config.h> by default 8 months ago
doc Add OTRSP protocol manual for future implmentaion 2 weeks ago
docker-build Fix spelling errors 3 months ago
extra Migrate README in kylix 4 months ago
include Remove winpthreads.h 1 month ago
lib astyle files for 4.5 release 2 months ago
macros bindings: Fix tcl build with slibtool 5 months ago
perl Trying to fix github build for README.md change 4 months ago
rigs Remove incorrect debug line in icom.c 2 weeks ago
rotators Astyle files 2 months ago
scripts Add MSVC projects to scripts/MSVC for 32 and 64-bit builds in C++ 1 month ago
security Make pthread.h a default include and remove config.h from being included in rig.h 1 month ago
simulators Update simicom.c 6 days ago
src Fix an uninitialized value warning from valgrind 2 weeks ago
tests Add setvbuf to rigctl.c and rigctld.d to overcome non-buffering of stderr on mingw builds. 3 days ago
.editorconfig Add new levels: RFPOWER_METER, COMP_METER, VD_METER and ID_METER, supported at least by most of recent Icom rigs. Add level NOTCHF_RAW for manual notch frequency without specified unit for Icom rigs. Add level MONITOR_GAIN. Add functions DUAL_WATCH and DIVERSITY, supported now by K3/K3S. Fix VOXDELAY level commands for many Icom rigs. Add MONITOR_GAIN level for Icom rigs. Fix and add many K3 commands and add specific rig models for K3S, KX2 and KX3 -- they are very similar to K3, but have slight differences. Extend dump_caps output for rigctl: add complete details of ext levels and frequency ranges. Tests have been performed on IC-7000, IC-756ProIII, IC-7300, IC-7600 and K3. 3 years ago
.gitignore Updated especially read_string() with flush flag. 7 months ago
AUTHORS Add INDI rotator backend 2 years ago
Android.mk add new rotator grbltrk 5 months ago
COPYING Updated GPL 2/LGPL 2.1 licenses 11 years ago
COPYING.LIB Updated GPL 2/LGPL 2.1 licenses 11 years ago
ChangeLog Update ChangeLog 2 years ago
INSTALL Trying to fix github build for README.md change 4 months ago
LICENSE Update LICENSE 1 month ago
Makefile.Windows Fix spelling errors 3 months ago
Makefile.am Debugging github README problem 4 months ago
NEWS Update NEWS for 4.5 release 5 days ago
PLAN Fix spelling errors 2 years ago
README Add README back 4 months ago
README.betatester Update README.betatester 4 months ago
README.coding_style Add some tips on shell scripts 2 years ago
README.developer Migrate tentec README 4 months ago
README.freqranges Format to break lines before 80 characters 1 year ago
README.md Rename README to README.md 4 months ago
README.multicast Improve multicast UDP snapshot data documentation 10 months ago
README.osx Add Macports to README.osx 2 years ago
README.release Fix spelling errors 2 years ago
README.win32 Add MSVC projects to scripts/MSVC for 32 and 64-bit builds in C++ 1 month ago
SECURITY.md Fix SECURITY.md 2 years ago
Segfault-award Fix netrigctl.c power2mW buffer overflow 11 months ago
THANKS minor changes 14 years ago
VFOs.txt Update VFOs.txt 2 years ago
bootstrap Remove bashisms from shell scripts 2 years ago
configure.ac Add Gemini DX-1200 HF-1K amplifier 3 months ago
cppcheck.sh Change all to remove HAVE_CONFIG dependency and include <hamlib/config.h> by default 8 months ago
hamlib.m4 Add LIBUSB flags to hamlib.m4 1 year ago
hamlib.pc.in Fix hardcoded pcconfig libdir 5 years ago

README.md

Hamlib - (C) Frank Singleton 2000 (vk3fcs@ix.netcom.com) (C) Stephane Fillod 2000-2011 (C) The Hamlib Group 2000-2012

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 programmer's interaction with radio equipment and other controllable devices such as rotators, switches, etc.

Supported Radios

The Hamlib Wiki page, Supported Radios, contains a snapshot of the supported radios at the time of the last Hamlib release. Go to http://www.hamlib.org to reach the Wiki.

Hamlib Design

The library provides functions for both radio and rotator control, and data retrieval from the radio or rotator. A number of functions useful for calculating distance and bearing and grid square conversion are included.

libhamlib.so - library that provides generic API for all RIG types. This is what Application programmers will "see". Will have different names on other platforms, e.g. libhamlib-2.dll on MS windows. Also contains all radio and rotator "backends" (formerly in their own dlopen'ed libraries) provided by Hamlib.

Backend Examples are:

  1. yaesu will provide connectivity to Yaesu FT 747GX Transceiver, FT 847 "Earth Station", etc. via a standard API.

  2. xxxx. 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 we expect that IP (and other) connectivity will follow afterwards. Connection via a USB port is accomplished via the Linux kernel support. USB to serial converters are well supported. Other such devices may be supported as long as they present a serial (RS-232) interface to Hamlib.

Availability

Most distributions have the latest Hamlib release in their testing or alpha versions of their distribution. Check your package manager for the Hamlib version included in your distribution.

Developing with Hamlib API

API documentation is at:

    https://github.com/Hamlib/Hamlib/wiki/Documentation

Take a look at tests/README for more info on simple programming examples and test programs.

C++ programming is supported and language bindings are available for Perl, Python, and TCL. A network daemon utility is also available for any programming language that supports network sockets (even netcat!).

Recompiling

Hamlib is entirely developed using GNU tools, under various Linux systems. The library may be recompiled by the familiar "three step":

    ./configure
    make
    sudo make install

For debugging use this configure ./configure CFLAGS=-g -O0 -fPIC --no-create --no-recursio

See the INSTALL file for more information.

Contributing

Consult the README.betatester and README.developer files in this directory if you feel like testing or helping with Hamlib development.

Contributions of rig specifications and protocol documentation are highly encouraged. Do keep in mind that in some cases the manufacturer may not provide complete control information or it is only available under a Non-Disclosure Agreement (NDA). Any documentation must be publicly available so we can legally write and distribute Free Software supporting a given device.

The Hamlib team is very interested to hear from you, how Hamlib builds and works on your system, especially on non-Linux system or non-PC systems. We try to make Hamlib as portable as possible.

Please report in case of problems at hamlib-developer@lists.sourceforge.net Git email formatted patches or in unified diff format are welcome!

Also, take a look at http://sourceforge.net/projects/hamlib/ Here you will find a mail list, link to the Wiki, and the latest releases. Feedback, questions, etc. about Hamlib are very welcome at the mail list:

    <hamlib-developer@lists.sourceforge.net>

Hamlib Version Numbers

Like other software projects, Hamlib uses a version numbering scheme to help program authors and users understand which releases are compatible and which are not. Hamlib releases now follow the format of:

Major.minor.incremental

Where

Major: Currently at 4, but can be advanced when changes to the API require client programs to be rewritten to take advantage of new features of Hamlib. This number has advanced a couple of times throughout the life of Hamlib. Advancement of the major number is only for frontend API changes that require modification of client source. ABI compatibility is presently maintained to prior releases so that a program linked to an earlier 1.2.Y.[Z] release will work with a later 3.Y[.Z] release without recompiling. It is our intention to maintain such ABI compatibility as long as practical.

Minor: This number advances when either new backend(s) or new rig model(s) to existing backend(s) are added. Advancing this number informs client program authors (and users of those programs) that new model/backend support has been added. Will also include bug fixes since the last Incremental release.

Incremental: May be undefined (e.g. Hamlib 3.0) and would advance to 1 (e.g. Hamlib 3.0.1) for any bug fixes or feature additions to existing model(s) or backend(s), then to 2, etc. New rig models or backends are not included in Incremental. When Release is advanced, Incremental will reset to undefined and will not be included as part of the version number.

Release schedule

Hamlib has in the past maintained a "ready when it's ready" philosophy. However, given that much of the Linux user base is now influenced by the Ubuntu distribution and its timed six month release schedule, Hamlib releases will be scheduled in advance of Ubuntu releases. Planned release dates for Hamlib are now 1 February and 1 August of each calendar year. Between those dates various Incremental releases will occur as development warrants.

Have Fun / Frank S / Stephane F / The Hamlib Group

73's de vk3fcs/km5ws / f8cfe