|
Name |
|
Date |
Size |
#Lines |
LOC |
| .. | | 03-May-2022 | - |
| data/ | H | 27-Feb-2021 | - | 25,938 | 22,090 |
| po/ | H | 03-May-2022 | - | 19,337 | 15,112 |
| src/ | H | 03-May-2022 | - | 32,814 | 25,432 |
| ABOUT-NLS | H A D | 03-Nov-2012 | 91.6 KiB | 1,283 | 1,244 |
| AUTHORS | H A D | 21-Jun-2016 | 229 | 7 | 4 |
| COPYING | H A D | 03-Nov-2012 | 31.7 KiB | 622 | 513 |
| ChangeLog | H A D | 27-Feb-2021 | 35.3 KiB | 648 | 610 |
| INSTALL | H A D | 04-Aug-2019 | 3.3 KiB | 94 | 67 |
| Makefile.am | H A D | 16-Feb-2021 | 267 | 15 | 8 |
| Makefile.in | H A D | 27-Feb-2021 | 24.8 KiB | 804 | 712 |
| NEWS | H A D | 03-Nov-2012 | 96 | 4 | 3 |
| README | H A D | 21-Jun-2016 | 2 KiB | 61 | 47 |
| TODO | H A D | 10-Apr-2015 | 388 | 10 | 6 |
| acinclude.m4 | H A D | 03-Nov-2012 | 790 | 33 | 31 |
| aclocal.m4 | H A D | 27-Feb-2021 | 148.8 KiB | 3,972 | 3,713 |
| compile | H A D | 25-Mar-2018 | 7.2 KiB | 348 | 258 |
| config.guess | H A D | 23-Jul-2013 | 44.1 KiB | 1,553 | 1,346 |
| config.rpath | H A D | 07-Apr-2015 | 18.3 KiB | 691 | 594 |
| config.sub | H A D | 23-Jul-2013 | 34.7 KiB | 1,789 | 1,651 |
| configure | H A D | 27-Feb-2021 | 269 KiB | 8,885 | 7,441 |
| configure.ac | H A D | 27-Feb-2021 | 3.1 KiB | 103 | 87 |
| depcomp | H A D | 03-Nov-2012 | 13.5 KiB | 480 | 304 |
| install-sh | H A D | 03-Nov-2012 | 7 KiB | 295 | 169 |
| missing | H A D | 17-Apr-2015 | 6.7 KiB | 216 | 143 |
| mkinstalldirs | H A D | 03-Nov-2012 | 1.9 KiB | 112 | 85 |
README
1- REQUIREMENTS -
2----------------
3See the INSTALL file for package requirements when you want to compile xlog
4yourself.
5
6- HAMLIB SUPPORT -
7------------------
8If your rig supports data retrieval over the serial line, you should have
9a look at the Hamradio Control Libraries (hamlib) project page, at
10http://sf.net/projects/hamlib. Xlog can read your rig's frequency, mode
11and signal strength.
12
13- TESTING HAMLIB -
14------------------
15At his point you should probably read your rig's manual, to see how you
16should hook up your rig to the serial port. For my kenwood rig, I need
17a standard serial cable with two 9-pin connectors. You also need write
18permission to the serial port. On my system, this means I need to add
19myself to the dialout group, with a command like:
20
21 adduser 'username' dialout
22
23Next, you can test hamlib with rigctl, a binary distributed with hamlib.
24See which rigs are supported:
25
26 rigctl --list
27
28Then start rigctl with your model number, e.g. '210' for a kenwood TS-870S,
29hooked up to COM2:
30
31 rigctl -r /dev/ttyS1 -m 210
32
33Now you can check out if mode, PTT, frequency, signal strength and power
34(all used by xlog) are retrieved. At the 'Rig command:' prompt, type:
35
36 'f': retrieve frequency
37 'm': retrieve mode
38 't': retrieve PTT (TX/RX mode)
39 'l' and then 'STRENGTH': retrieve signal strength (-54=S0 and 0=S9)
40 'l' and then 'RFPOWER': retrieve rig power (0.39 = 100 Watts)
41
42The hamlib FAQ at http://hamlib.sf.net/faq.html gives some answers to common
43problems. You could also ask around on the hamlib mailing list, see:
44http://lists.sourceforge.net/lists/listinfo/hamlib-developer.
45
46- XLOG USAGE -
47--------------
48For a description on how to use xlog, select help -> Documentation -> Manual
49from the menu.
50
51- DEVELOPMENT -
52---------------
53If you are interested in xlog development, go to
54http://savannah.nongnu.org/projects/xlog. Information about a mailing list for
55xlog development is available on this page, where you can ask questions about
56xlog.
57
58- CONTACT -
59-----------
60The main author can be contacted by e-mail: kb1oiq@arrl.net
61