197 |
Your hamlib port can be configured in the hamlib page of the the preferences |
Your hamlib port can be configured in the hamlib page of the the preferences |
198 |
dialog. You can enter things like: rts_state=ON,timeout=600,serial_speed=19200 |
dialog. You can enter things like: rts_state=ON,timeout=600,serial_speed=19200 |
199 |
here. |
here. |
200 |
|
|
201 |
|
----- TESTING HAMLIB ----- |
202 |
|
At his point you should probably read your rig's manual, to see how you |
203 |
|
should hook up your rig to the serial port. For my kenwood rig, I need |
204 |
|
a standard serial cable with two 9-pin connectors. You also need write |
205 |
|
permission to the serial port. On my system, this means I need to add |
206 |
|
myself to the dialout group, with a command like: |
207 |
|
|
208 |
|
adduser 'username' dialout |
209 |
|
|
210 |
|
Next, you can test hamlib with rigctl, a binary distributed with hamlib. |
211 |
|
See which rigs are supported: |
212 |
|
|
213 |
|
rigctl --list |
214 |
|
|
215 |
|
Then start rigctl with your model number, e.g. '210' for a kenwood TS-870S, |
216 |
|
hooked up to COM2: |
217 |
|
|
218 |
|
rigctl -r /dev/ttyS1 -m 210 |
219 |
|
|
220 |
|
Now you can check out if mode, PTT, frequency, signal strength and power |
221 |
|
(all used by xlog) are retrieved. At the 'Rig command:' prompt, type: |
222 |
|
|
223 |
|
'f': retrieve frequency |
224 |
|
'm': retrieve mode |
225 |
|
't': retrieve PTT (TX/RX mode) |
226 |
|
'l' and then 'STRENGTH': retrieve signal strength (-54=S0 and 0=S9) |
227 |
|
'l' and then 'RFPOWER': retrieve rig power (0.39 = 100 Watts) |
228 |
|
|
229 |
|
The hamlib FAQ at http://hamlib.sf.net/faq.html gives some answers to common |
230 |
|
problems. You could also ask around on the hamlib mailing list, see: |
231 |
|
http://lists.sourceforge.net/lists/listinfo/hamlib-developer. |
232 |
|
|
233 |
----- DATA EXCHANGE ----- |
----- DATA EXCHANGE ----- |
234 |
xlog can exchange data with twpsk (version 2.0 and higher) by WA0EIR. When a |
xlog can exchange data with twpsk (version 2.0 and higher) by WA0EIR. When a |
235 |
callsign is entered, it will show up in twpsk's send widget (where you type |
callsign is entered, it will show up in twpsk's send widget (where you type |
261 |
This file can be completed by adding entries to |
This file can be completed by adding entries to |
262 |
/usr/[local/]share/xlog/dxcc/xlog.dat. |
/usr/[local/]share/xlog/dxcc/xlog.dat. |
263 |
|
|
264 |
----- SEE ALSO ----- |
----- FONTS AND THEMING ----- |
265 |
The provided README for more information in setting up hamlib and the FAQ for a |
Xlog fonts are handled by the GTK theme engine. When you use the gnome2 desktop, |
266 |
list of frequently asked questions. |
start up gnome-font-properties. Otherwise, edit ~/.gtkrc-2.0 and add a line |
267 |
|
like: |
268 |
|
|
269 |
|
gtk-font-name = "Times New Roman 14" |
270 |
|
|
271 |
|
Or whatever. GNOME 2 applies its own settings to GTK2 programs with the |
272 |
|
gnome-settings-daemon. When the daemon is running, GTK2 programs will use the |
273 |
|
GNOME settings instead of those present in .gtkrc-2.0. |
274 |
|
|
275 |
|
There is also an application called gtk-theme-switch2, which you can use to |
276 |
|
adjust both appearance and font, whether you use gnome or not. |
277 |
|
|
278 |
----- AUTHORS ----- |
----- AUTHORS ----- |
279 |
xlog was written by Joop Stakenborg <pg4i at amsat.org> aka <pa3aba at |
xlog was written by Joop Stakenborg <pg4i at amsat.org> aka <pa3aba at |
280 |
debian.org> and Stephane Fillod <f8cfe at free.fr>. |
debian.org> and Stephane Fillod <f8cfe at free.fr>. There were contributions |
281 |
|
by many people see the THANKS file. |