HAMLIB SUPPORT
--------------
If your rig supports data retrieval over the serial line, you should have
a look at the Hamradio Control Libraries (hamlib) project page, at
http://sf.net/projects/hamlib. Get version at least version 1.1.3 if you can.

If unavailable (at the time of writing, hamlib is short before the 1.1.3
release), you should get the CVS version. Details are on the hamlib
project page. Easiest way to get the CVS version is typing:

	wget http://cvs.sf.net/cvstarballs/hamlib-cvsroot.tar.gz

Xlog can read your rig's frequency, mode and signal strength, if compiled
with hamlib support. See the INSTALL file for details. Hamlib support should
be enabled from the preferences dialog box.

TESTING HAMLIB
--------------
At his point you should probably read your rig's manual, to see how you
should hook up your rig to the serial port. For my kenwood rig, I need
a standard serial cable with two 9-pin connectors. You also need write
permission to the serial port. On my system, this means I need to add
myself to the dialout group, with a command like:

	adduser 'username' dialout

Next, you can test hamlib with rigctl, a binary distributed with hamlib.
See which rigs are supported:

	rigctl --list

Then start rigctl with your model number, e.g. '210' for a kenwood TS-870S,
hooked up to COM2:

	rigctl -r /dev/ttyS1 -m 210

Now you can check out if mode, PTT, frequency and signal strength
(all used by xlog) are retrieved. At the 'Rig command:' prompt, type:

	'f': retrieve frequency
	'm': retrieve mode
	't': retrieve PTT (TX/RX mode)
	'l' and then 'STRENGTH': retrieve signal strength (-54=S0 and 0=S9)


XLOG USAGE
----------
Read the manual page for a description on how to use xlog (man xlog).
Dxcc lookups are done and heading and distance to a station is displayed. 
Dxcc information is derived from dxcck2di.txt. See the file dxcck2di.changes
for a list of changes I had to make, to make the lookups more consistent.

Printing is supported by using latex, so you need to install the tetex package.
For an example how to use remote logging (only of interest to program
developers), have a look at sendtoxlog.c in the remote directory.
Xlog can also exchange data with twpsk (version 2.0 and higher) by WA0EIR 
and gmfsk by OH2BNS (starting at version 0.4).

BINARY PACKAGES
---------------
Debian packages are at http://packages.debian.org/xlog.
The xlog home page is at http://people.debian.org/~pa3aba/xlog.html.
You will also find rpm packages there. Slackware packages are at
http://sharon.esrac.ele.tue.nl/pub/slackware/pre-current/contrib/ham/logging.

DEVELOPMENT
-----------
If you are interested in xlog development, go to 
http://savannah.gnu.org/projects/xlog. Information about a mailing list for
xlog development is available on this page.

Send comments to: xlog-discussion@mail.freesoftware.fsf.org
For a list of authors see the AUTHORS file.
