LIbrary for Amateur Radio Equipment Control Applications.
 
 
 
 
 
 
Go to file
Stephane Fillod 6c370dd36d serial: fix blocking call on ports, esp. on win32
Summary from Lada:

On Win7, good testing command is:
C:\hamlib> rigctl -vvvvv -m 214 -r COM1 -s 4800 -C data_bits=8 -C
stop_bits=2 -C serial_handshake=Hardware -C timeout=1000

Behavior of this command differs on COM port. On hardware ports
(onboard, PCI NetMos, all probably 16550-compatible) rigctl freeze in
data write. It is correct, no hardware handshake is estabilished. On
FT232 USB port initialization failed by timeout. I think it is not
correct but this is not subject of this e-mail.

Looked into hamlib source and found, that timeout argument is no
longer handled. SetCommTimeouts takes timeout from c_cc[VTIME] which
is not filled.

Signed-off-by: Ladislav Vaiz <spam@nagano.cz>
2013-05-06 23:47:56 +02:00
adat Add Android build support 2013-04-26 22:31:56 -05:00
alinco Add Android build support 2013-04-26 22:31:56 -05:00
amsat Add Android build support 2013-04-26 22:31:56 -05:00
android Add Android build support 2013-04-26 22:31:56 -05:00
aor Add Android build support 2013-04-26 22:31:56 -05:00
ars Add Android build support 2013-04-26 22:31:56 -05:00
bindings Binding test scripts--fix set_freq ordering 2013-02-12 18:51:38 -06:00
c++ ABI backward compatibility enhancement 2012-10-08 13:07:35 -05:00
celestron Add Android build support 2013-04-26 22:31:56 -05:00
doc doc/Makefile.am: Don't build/distribute PDF manual 2013-04-21 19:18:57 -05:00
drake Add Android build support 2013-04-26 22:31:56 -05:00
dummy Add Android build support 2013-04-26 22:31:56 -05:00
easycomm Add Android build support 2013-04-26 22:31:56 -05:00
flexradio Add Android build support 2013-04-26 22:31:56 -05:00
fodtrack Add Android build support 2013-04-26 22:31:56 -05:00
gnuradio
gs232a Add Android build support 2013-04-26 22:31:56 -05:00
heathkit Add Android build support 2013-04-26 22:31:56 -05:00
icom Add Android build support 2013-04-26 22:31:56 -05:00
include rig.h: Replace rig_func_e with CPP macros 2013-01-31 18:00:50 -06:00
jrc Add Android build support 2013-04-26 22:31:56 -05:00
kachina Add Android build support 2013-04-26 22:31:56 -05:00
kenwood Add Android build support 2013-04-26 22:31:56 -05:00
kit Add Android build support 2013-04-26 22:31:56 -05:00
kylix
lib win32termios: fix in tcflush 2013-05-06 08:35:00 +02:00
lowe Add Android build support 2013-04-26 22:31:56 -05:00
m2 Add Android build support 2013-04-26 22:31:56 -05:00
macros gr_pwin32.m4: Replace inline sleep() function 2013-04-24 21:58:50 -05:00
microtune
miniVNA
pcr Add Android build support 2013-04-26 22:31:56 -05:00
perl
prm80 Add Android build support 2013-04-26 22:31:56 -05:00
racal Add Android build support 2013-04-26 22:31:56 -05:00
rft Add Android build support 2013-04-26 22:31:56 -05:00
rotorez Add Android build support 2013-04-26 22:31:56 -05:00
rs Add Android build support 2013-04-26 22:31:56 -05:00
sartek Add Android build support 2013-04-26 22:31:56 -05:00
scripts build-win32.sh: Distribute hamlib.html 2013-04-26 22:37:16 -05:00
skanti Add Android build support 2013-04-26 22:31:56 -05:00
spid Add Android build support 2013-04-26 22:31:56 -05:00
src serial: fix blocking call on ports, esp. on win32 2013-05-06 23:47:56 +02:00
tapr Add Android build support 2013-04-26 22:31:56 -05:00
tentec Add Android build support 2013-04-26 22:31:56 -05:00
tests man page corrections 2013-03-13 15:02:43 -05:00
ts7400 Add Android build support 2013-04-26 22:31:56 -05:00
tuner Add Android build support 2013-04-26 22:31:56 -05:00
uniden Add Android build support 2013-04-26 22:31:56 -05:00
winradio Add Android build support 2013-04-26 22:31:56 -05:00
wj Add Android build support 2013-04-26 22:31:56 -05:00
yaesu Add Android build support 2013-04-26 22:31:56 -05:00
.gitignore .gitignore: Ignore generated texinfo files 2013-02-24 07:31:13 -06:00
AUTHORS Updates for 1.2.15 cycle 2012-02-02 20:40:55 -06:00
Android.mk Add Android build support 2013-04-26 22:31:56 -05:00
COPYING
COPYING.LIB
ChangeLog
INSTALL Add Readline option to README files 2013-02-22 21:50:53 -06:00
LICENSE LICENSE: Add 2012, format for 80 columns 2012-10-05 12:46:36 -05:00
Makefile.am Add Android build support 2013-04-26 22:31:56 -05:00
NEWS Add Android build support 2013-04-26 22:31:56 -05:00
PLAN
README Bring documentation up to date with recent changes 2012-10-09 21:16:13 -05:00
README.betatester Add Readline option to README files 2013-02-22 21:50:53 -06:00
README.developer Add Readline option to README files 2013-02-22 21:50:53 -06:00
README.release ABI backward compatibility enhancement 2012-10-08 13:07:35 -05:00
README.win32 Disable static builds by default 2012-10-11 09:17:58 -05:00
Segfault-award
THANKS
TODO Updates for 1.2.15 cycle 2012-02-02 20:40:55 -06:00
TODO.skeleton
autogen.sh Install build files rather than symlink 2012-10-13 19:09:46 -05:00
configure.ac Add Android build support 2013-04-26 22:31:56 -05:00
hamlib.m4
hamlib.pc.in

README

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 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".  Will have different
                names on other platforms, e.g. libhamlib-2.dll
                on MS windows.

Backend Examples are:
---------------------

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

2. hamlib-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 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
--------------------------

C language API documentation is at:

        http://www.hamlib.org/index.php?title=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

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 3, 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.  Itis 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