mirror of
https://github.com/ok2cqr/cqrlog.git
synced 2024-09-21 10:27:17 +00:00
9fedad69d7
- changed version number to 2.5.0 in main help page. - changed OH7AN to OK2CQR in all help pages as understood from your web pages "OK2CQR is back" that you returned to your old callsign. - went through https://github.com/ok2cqr/cqrlog/commits/master and added some lines to CHANGELOG. I'm still sure that not all things are in the list. Perhaps it would be good idea to add a changelog line as the first line of pull request text. Then it would be easier to collect them afterwards. This is not complete list. I would be happy to see more additions or fixes to current CHANGELOG also from others!
111 lines
5.0 KiB
HTML
111 lines
5.0 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
|
<html lang="en-us">
|
|
<head>
|
|
<title>CQRLOG - cwdaemon setup</title></head>
|
|
<body>
|
|
<table border="0" cellpadding="5" cellspacing="2" width="100%">
|
|
<tbody>
|
|
<tr>
|
|
<td valign="top"><img src="img/exc.png"></td>
|
|
<td align="justify" bgcolor="ffffcc" valign="top"><strong>
|
|
<font color="red">WARNING!</font></strong>
|
|
Backup your data often! BACKUP your log directory at the end of EVERY session!
|
|
All that you need to backup and store in a safe place is the log database directory
|
|
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
|
|
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
|
|
<tbody>
|
|
<tr>
|
|
<td align="left" width="33%"> <<a href="h26.html"> Prev</a></td>
|
|
<td align="center" width="33%">[<a href="index.html" target="_top">Menu</a>]</td>
|
|
<td align="right" width="33%"><a href="h26.html">Next </a>></td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
<br>
|
|
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR & OK1RR</strong></div>
|
|
<p align="center"><img src="img/line.png"></p>
|
|
<strong>cwdaemon setup</strong><br><br>
|
|
<div align="justify">cwdaemon is a very good software trick which does a good job if
|
|
you build your own kernel and you also don't need to fire it up separately with root
|
|
privileges if you have an addition in your start-up scripts.<br><br>
|
|
|
|
<strong>Poor sounding CW </strong><br><br>
|
|
Sloppy CW from the cwdaemon it depends on kernel settings. I tested it thoroughly because I love CW at higher
|
|
speeds. Latency of 1000 Hz helped a bit, I was able to run at usual contest speeds up to 36 wpm. Since kernel 2.6.23
|
|
the problem seems cured with tickless kernel. Here is an excerpt from my config:
|
|
</div>
|
|
<pre>
|
|
# # Processor type and features #
|
|
CONFIG_TICK_ONESHOT=y
|
|
CONFIG_NO_HZ=y
|
|
CONFIG_HIGH_RES_TIMERS=y
|
|
CONFIG_SMP=y
|
|
CONFIG_X86_PC=y
|
|
....</pre>
|
|
|
|
<div align="justify">Now I can go up to 60 WPM and the resulting CW is excellent,
|
|
however I'm using cwdaemon 0.9.4beta1. Versions below 0.8 are actually useless,
|
|
the worst CW I ever heard was produced by cwdaemon 0.5 and an unmodified kernel.<br><br>
|
|
|
|
The newest cwdaemon 0.9.4 depends on unixcw version 2.3 (or above) which won't
|
|
compile on my Slackware system (and I was not patient enough to track all the dependencies),
|
|
therefore not tested. I believe that the new dependency was a bad step back...
|
|
I hope that new versions of cwdaemon will continue the way set by the 0.9.4beta1 version
|
|
(source download here). Anyway, with this version of cwdaemon and custom made kernel 2.6.23
|
|
(and higher) I am fully satisfied. I am convinced that any development of CW related
|
|
software should be thoroughly tested by high speed freaks, it is rather bad if a developer
|
|
or tester means he did well if he is limited by 25 WPM... <br><br></div>
|
|
|
|
<strong>Start-up without root privileges </strong><br><br>
|
|
|
|
<div align="justify">There is no need to start cwdaemon separately with root privileges.
|
|
Put a little addition in your start-up script and cwdaemon will start without any keystroke.
|
|
It is a good solution for a ham radio machine, however you may have some problems if you want
|
|
to use your parallel port for printing or other purposes. <br><br>
|
|
|
|
I added two simple blocks to the <font face=Courier,Courier New>/etc/rc.d/rc.local</font>
|
|
which applies to Slackware GNU/Linux, however your preferred distribution may use another
|
|
name and location.<br><br>
|
|
|
|
The first block is used to load parport and parport_pc modules which are essential to
|
|
cwdaemon. The second block actually loads cwdaemon. First, it stops the module which
|
|
can block your parallel port - here it was cups. cwdaemon also won't work if the lp module
|
|
is loaded, so unload it if necessary. Next, a device node is created and cwdaemon is loaded.
|
|
</div>
|
|
|
|
<pre>#load parport, parport_pc
|
|
modprobe parport
|
|
modprobe parport_pc
|
|
|
|
# Load cwdaemon
|
|
echo "starting cwdaemon"
|
|
/etc/rc.d/rc.cups stop
|
|
# rmmod lp
|
|
cd /dev
|
|
mknod -m 0660 parport0 c 99 0
|
|
/usr/local/sbin/cwdaemon -x n </pre>
|
|
|
|
Remember the cwdaemon options:<br><br>
|
|
<img src="img/cwdaem.png"><br><br>
|
|
I find it useful to start cwdaemon without any sidetone, it seems much better to use
|
|
the sidetone of your radio rather than the PC speaker.
|
|
|
|
<p align="center"><img src="img/line.png"></p>
|
|
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
|
|
<tbody>
|
|
<tr>
|
|
<td align="left" width="33%"> <<a href="h26.html"> Prev</a></td>
|
|
<td align="center" width="33%">[<a href="index.html" target="_top">Menu</a>]</td>
|
|
<td align="right" width="33%"><a href="h26.html">Next </a>></td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
<br>
|
|
</body>
|
|
</html>
|