hamradio/cqrlog
1
0
Fork 0
mirror of https://github.com/ok2cqr/cqrlog.git synced 2024-09-21 02:17:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

dUtils:bandToFrequency->630M missing. Updated some help files

Browse Source
This commit is contained in:
OH1KH 2017-11-04 11:16:52 +02:00
parent dff5678ce7
commit b6a3ffc5cd
38 changed files with 536 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
CqrlogAdditions2.pdf
View File

Binary file not shown.

135
help/fldxml.html Normal file
View File

@ -0,0 +1,135 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>CQRLOG - Supported Radio Types</title>
</head>
<body>
<script>
function goForward() {
window.history.forward();
}
function goBack() {
window.history.back();
}
</script>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><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 width="33%" align="left">&nbsp;&lt;<a href="h1.html#ch2"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h1.html#ch3">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<a name=fl1><h2><strong>fldigi XmlRpc remote</strong></h2></a>
<ul style="margin-left: 40px;">
<li><a href="fldxml.html#fl2">Settings</a></li>
<li><a href="fldxml.html#fl3">Use</a></li>
<li><a href="fldxml.html#fl4">Some notes</a></li>
<li><a href="fldxml.html#fl5">Starting fldigi and wsjt-x via cqrlog</a></li>
</ul>
<p>XmlRpc remote connection to fldigi is an alternative way to transfer qso data to cqrlog.</br>
With XmlRpc cqrlog acts as client what is opposite way compared to wsjt-x remote where cqrlog acts like
server. Because of this cqrlog can not know if “save to log” button is pressed at fldigi because it tells it’s information only
when asked.</br>
This leads to situation where fldigi logging can not be used to act like indicator to cqrlog to save qso and <b>saving must be done by operator on cqrlogs side</b>.
<p>There are two ways to save qso:</br><ul>
<li/>Press “save qso” on cqrlog’s NewQSO form <b>and</b> press save on fldigi. You get entry to both logs.</br>
<li/>Press “Save this qso” on cqrlog XmlRpc form. You get qso <b>saved to cqrlog</b> and fldigi entry is <b>cleared</b>, but <b>not saved</b>.</br>
</ul>
</p>
<p>When using XmlRPC:</br><ul>
<li/> You get qrz/HamQth data immediately after adding call to fldigi’s call field</br>
<li/> You see qso before/dxcc statistics from cqrlog before firing TX the first time</br>
<li/> You can run fldigi on other computer than cqrlog if they have common network. WiFi, wired, or even internet(when you should use openVPN to make secured tunnel between sites)</br>
</ul>
</p>
<a name=fl2><h3>Settings</h3></a>
<p><img src="img/fxml5.png" width="401" height="281">
<br clear="left"/>
</img>
In cqrlog’s preferences/fldigi/wsjt interface there are some new settings. Port and Address for fldigi network connection and
selection to use XmlRpC.</br>With selection you can choose “the old way” for fldigi remote, or the XmlRpc way. Port number should be ok, but IP address may change depending your needs.
</br>Address is normally 127.0.0.1 (localhost) if you run fldigi on same PC than cqrlog.
</br>If you have fldigi running on other PC put here the IP address of fldigi-PC. There is no IP address validation, so you have to type correctly formatted
address.</br>
If you use fldigi on other PC remember to open firewall at fldigi-PC side for TCP traffic to port 7362 from your local network.</p>
<p>Parameter &quot;Drop after SyncErr &gt;&quot; automates remote mode closing when fldigi is closed. But as it may affect also (in slow PCs) fldigi started by cqrlog it can be changed. 0 disables, 1-20 means timer rounds until drop.
When closing happens it leaves text &quot;Socket error, check fldigi!&quot; to NewQSO field &quot;Comment QSO&quot;.
</p><p> In all cases fldigi must be started from command line with parameter: <b>fldigi --xmlrpc-server-port 7362</b>
</br>When closing fldgi properly and answering YES to save setup changes the next start should open xmlrpc server without parameters from usual icon.</p>
<a name=fl3><h3>Use</h3></a>
<p><img src="img/fxml9.png" width="446" height="117">
<br clear="left"/>
</img>
</p>
<p>When you have activated fldigi remote and checked “Use XmlRpc” at preferences, texts that you type to
fldigi logging sheet (or select from monitor with right click) are transferred to cqrlog by polling fldigi with speed you have set on
preferences “Try to load QSO from fldigi every X seconds”.
</br>When remote for fldigi is opened a new status form is shown. It shows data that have been received from
fldigi. If you can’t see any changes you have to check port and address settings (both fldigi and cqrlog) and firewall settings.
</br>There is more information about XmlRpc
at:<br/>
<a href="http://www.w1hkj.com/FldigiHelp-3.21/html/xmlrpc_control_page.html">http://www.w1hkj.com/FldigiHelp-3.21/html/xmlrpc_control_page.html</a></p>
<p>If everything is OK you should see something like this:</br>
<p><img src="img/fxml8.png" width="643" height="274">
<br clear="left"/>
</img>
</p>
<a name=fl4><h3>Some notes</h3></a>
<ul>
<li/>fldigi’s <b>pr </b>(Province) is transferred to cqrlog’s <b>County</b></br>
<li/>fldigi’s Country is not transferred</br>
<li/><b>Save this qso</b> is <b>shown after</b> you have <b>call, time on, rst_in, rst_out</b> and <font color="#ff0000">TX fired once </font>it hides again when qso data is cleared.</br>
<li/><b>Save this qso</b> <font color="#ff0000"><b>saves only to cqrlog</b></font>, fldigi’s qso data is just cleared.</br>
</ul>
<a name=fl5><h3>Starting fldigi and wsjt-x via cqrlog</h3></a>
<p>You can set preferences so that cqrlog will start fldigi and/or wsjt-x programs for you when you enter remote mode. This is very handy, but doing that has also one risk.
<br/>When fldigi or wsjt-x has been started as a child process of cqrlog they will die at the moment cqrlog crashes for some reason.
<br/>If you start them manually as processes of their own and then activate remote mode from cqrlog they keep on running if cqrlog
dies. You can finish your ongoing qso, start cqrlog again, set remote mode on and then log the qso in normal manner.</p>
<p align=center><img src=img/line.png></p>
<br>
<table width="100%" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h1.html#ch2"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h1.html#ch3">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body>
</html>

4
help/h1.html
View File

@ -57,6 +57,7 @@
<li><a href="h1.html#bh4">LoTW support</a></li>
<li><a href="h1.html#ch1">CW interface</a></li>
<li><a href="h1.html#ch2">fldigi interface</a></li>
<li><a href="fldxml.html">fldigi XmlRpc remote</a></li>
<li><a href="h1.html#ch3">Auto backup</a></li>
<li><a href="h1.html#ch4">External viewers</a></li>
<li><a href="h1.html#ch5">Callbook support</a></li>
@ -502,6 +503,9 @@ There are no known dependencies issues.<br><br>
need to watch the logger, except the QSO list in the upper portion of the logging screen.
When logging/saving a contact, frequency, mode and RST should appear correctly in this QSO list.
If you choose the CQRLOG option, you must set the mode in CQRLOG which seems less sensible.
<br><br>See also:<a href="fldxml.html#fl1"> Using fldigi withXmlRpc remote mode</a><br>
<a name=ch3><h2><strong>Auto backup</strong></h2></a>
To increase the safety of your log data, CQRLOG is equipped with an <em>Auto backup</em>
option which allows you to export (ADIF) and store the log data in a safe location.

23
help/h20.html
View File

@ -304,20 +304,27 @@
The CAT (radio computer control) is turned off. Other fields and log
actions are the same. If you uncheck the 'Offline' box, CQRLOG returns
to the online mode.<br><br></div>
<a name="ah33"><h2><strong>Digital modes (including RTTY)</strong></h2></a>
CQRLOG employs <em>fldigi</em> by Dave Freese, W1HKJ. We believe that this is the
best digimode software available. To use <em>fldigi</em>, CQRLOG must be switched
to Remote mode using Ctrl+M (or from the menu File -> Remote mode for fldigi).<br><br>
<a name="ah33"><h2><strong>Digital modes </strong></h2></a>
CQRLOG employs <em>fldigi</em> by Dave Freese, W1HKJ and <em>WSJT-X</em> by Joe Taylor, K1JT. We believe that these are the
best digimode softwares available.<br>
<br>The most important thing is a <a href="h1.html#ch2">proper setup</a> of the remote mode. For <em>fldigi<em> you have 2 different ways to setup remote .<br>
For <em>wsjt-x</em>, setup is done at same tab of preferences as <em>fldigi<em>. For operating with wsjt-x see: <a href="wsjt.html">Wsjt-x operation</a>
<br><br> To use <em>fldigi</em>, CQRLOG must be switched to Remote from the menu File -> Remote mode for fldigi(or CTRL+M).
<br> To use <em>wsjt-x</em>, CQRLOG must be switched to Remote from the menu File -> Remote mode for wsjt.<br><br>
<img src="img/h104.png"><br><br>
The logging screen changes to indicate that CQRLOG is now working in remote mode and
The logging screen changes to indicate that CQRLOG is now working in 'Remote mode!' and
can be controlled either from <em>fldigi</em> or can "dictate" the mode and frequency
and <em>fldigi</em> now serves as the remote input device.<br><br>
and <em>fldigi</em> now serves as the remote input device.
<br> With wsjt-x the text 'Wsjtx remote ' includes also last received datagrams number and changes color in every receive to easily see that UDP link is alive between cqrlog and wsjt-x.
<br><br>
<img src="img/h103.png"><br><br>
Now, use <em>fldigi</em> in its normal way and your contacts will go directly to CQRLOG.
The most important thing is a <a href="h1.html#ch2">proper setup</a> of the remote mode
(frequency and mode). See fldigi help and the Beginners Guide on the W1HKJ site
See fldigi help and the Beginners Guide on the W1HKJ site
<a href=http://www.w1hkj.com/beginners.html>
strong>http://www.w1hkj.com/beginners.html</strong></a>.
<br>
<p align=center><img src=img/line.png></p>
<table width="100%" border="0" cellpadding="2" cellspacing="2">
<tbody>

41
help/h21.html
View File

@ -44,6 +44,28 @@ The color coding and spot filtering is set up in the
cluster node by simply clicking the 'Connect' button. You should see the cluster node
messages indicating progress. You can enter any command into the 'Command' field
(ie. SH/DX to display last spots, SH/U to see the users connected to the node etc.).
<h3><a name="m4"></a>DXCluster Chat</h3>
<p><img src="img/misc12.png" name="12" width="458" height="388">
</img>
<br/>DXCluster window has now “overlay” as chat RX window. All lines that begins with “YOURCALL DE”, but do not end to cluster prompt “&gt;” are copied to this window.<br/>
Time(your local PC time) and caller’s call are added in from of text line. This works only in Telnet session, not Web session<br/>
No more lost chats that are run over with the flood of DxSpots while you are visiting kitchen to get a cup of coffee. DXChat uses the call you have used for logging in to DXCluster (that can be different as your current log settings call).</p>
<p><img src="img/misc14.png" name="14" width="362" height="307">
</img>
<br/>The size of Chat window, relative to Dx spot window can be adjusted pressing first button “Preferences” and then selecting “Chat size” from there. After doing that “Command:”-cell at bottom of window is replaced with size slider.<br/>
<img src="img/misc13.png" name="13" width="209" height="121">
</img>
<br/>Pressing the slider knob with mouse-left button and moving slider will reduce the size of chat window. When mouse button is released “Command:”-cell returns and Chat window remains selected size.</p>
<p><font color="#ff0066">If you have never used Chat window before default size </font><font color="#ff0066">will be </font><font color="#ff0066">2 (=invisible)</font>.<br/>
Resize via “preferences”-button if you want to see it. <br/>
If you do not like this Chat window you can move/leave it to minimum size (2). Then it takes just horizontal 2px amount from DXSpot window.</p>
<p>While minimized to up Chat window still receives all lines addressed to your logon call (and not having “&gt;”-prompt at the end of line).<br/>
So any time you like you can make it larger and chat lines are there to check.</p>
<br><br>
<table border="0" cellpadding="5" cellspacing="2">
<tbody>
@ -158,13 +180,30 @@ messages indicating progress. You can enter any command into the 'Command' field
<td valign="top">
<a name="ch20"><h2><strong>Propagation indicator</strong></h2></a>
<img src="img/h110.png" border="0"></td>
<td valign="top">
</img>
<td valign="top">
<div align="justify"><br><br>
There is a simple window providing propagation indices as provided by the NOAA Space
Weather Center. CQRLOG does not include a propagation forecast module but keen users
can estimate many parameters just from the supplied data.
</div>
</td>
<td valign="top">
<h3 ><a name="m1"></a>Prop_DK0WCY</h3>
<p><img src="img/misc3.png" name="3" width="150" height="226">
</img>
</td>
<td valign="top">
<div align="justify"><br><br>
This propagation form is an alternative showing details from dk0wcy page with 3 hour graphical
display of K-index. The Kiel information is lot more exact for use in Europe than Boulder’s.
As Boulder information at dk0wcy is one days old, top of form shows time when information is
read from dk0wcy web page.
” Indices of”- shows the age of Boulder data. Kiel information is up to date as they are produced by dk0wcy. There is also
link to dk0wcy web page. By clicking it page opens to default browser.
</div>
</td>
</tr>
</tbody>
</table>

6
help/h26.html
View File

@ -59,7 +59,11 @@
</tr>
</tbody>
</table>
<br>
<p><img src="img/misc8.png" name="8" width="500" height="85">
</img>
<br/>CW keys from has new buttons PgUp and PgDn that are not configurable. They alter CW speed in same way as keyboard keys PgUp and PgDn that some, specially laptop computers, do not have.</p>
<p>When using external keyboard, and CW keys-form with mouse, you always have to first focus NewQso-form to be active and then press PgUp / PgDn keys. Now you can do it from same focused CW-keys form that you launch memories with mouse.</p>
Another option 'CW type' is a powerful keyboard keyer with 3 operation modes:<br><br>
<img src=img/h98.png><br><br>
<ul>

BIN
help/img/fxml5.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 49 KiB

BIN
help/img/fxml8.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 228 KiB

BIN
help/img/fxml9.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 56 KiB

BIN
help/img/h101.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 14 KiB

After

Width:  |  Height:  |  Size: 92 KiB

BIN
help/img/h104.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 6.2 KiB

After

Width:  |  Height:  |  Size: 13 KiB

BIN
help/img/misc12.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 63 KiB

BIN
help/img/misc13.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 5.3 KiB

BIN
help/img/misc14.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 94 KiB

BIN
help/img/misc3.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 18 KiB

BIN
help/img/misc5.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 64 KiB

BIN
help/img/misc8.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 16 KiB

BIN
help/img/wkdgrid10.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 34 KiB

BIN
help/img/wkdgrid11.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 38 KiB

BIN
help/img/wkdgrid9.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 65 KiB

BIN
help/img/wsjt1.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 51 KiB

BIN
help/img/wsjt15.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 22 KiB

BIN
help/img/wsjt16.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 25 KiB

BIN
help/img/wsjt17.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 36 KiB

BIN
help/img/wsjt18.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 5.8 KiB

BIN
help/img/wsjt19.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 28 KiB

BIN
help/img/wsjt2.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 68 KiB

BIN
help/img/wsjt20.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 8.7 KiB

BIN
help/img/wsjt21.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 25 KiB

BIN
help/img/wsjt27.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 3.4 KiB

BIN
help/img/wsjt28.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 3.9 KiB

BIN
help/img/wsjt4.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 104 KiB

5
help/index.html
View File

@ -133,7 +133,9 @@ and
<li><a href="h20.html#ah16">Keys and Shortcuts</a></li>
<li><a href="h20.html#ah17">New QSO</a> (online logging)</li>
<li><a href="h20.html#ah18">New QSO</a> (offline logging, ie. from paper log etc.)</li>
<li><a href="h20.html#ah33">Digital modes</a> (<em>fldigi</em> interface)</li>
<li><a href="h20.html#ah33">Digital modes:</a> <em>fldigi</em></li>
<li><a href="fldxml.html">Digital modes:</a> <em>fldigi XmlRpc</em></li>
<li><a href="wsjt.html">Digital modes:</a> <em>wsjt-x</em></li>
<li><a href="h25.html">QSO record edit</a></li>
<li><a href="h25.html#grp">Group edit</a></li>
<li><a href="h21.html#ah19">DX Cluster Operation</a></li>
@ -149,6 +151,7 @@ and
<li><a href="h21.html#ch21">Additional notes to a callsign</a></li>
<li><a href="h24.html#ah23">Statistics</a></li>
<li><a href="contest.html">Contest</a></li>
<li><a href="remi.html">Reminder</a></li>
</ul>
<strong><h3>Advanced operations</h3></strong>
<ul>

54
help/remi.html Normal file
View File

@ -0,0 +1,54 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>CQRLOG - Supported Radio Types</title>
</head>
<body>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><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 width="33%" align="left">&nbsp;&lt;<a href="h5.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h7.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<h3 ><a name="m3"></a>Reminder</h3>
<p><img src="img/misc5.png" name="5" width="516" height="128">
</img>
<br/>Reminder is a pop-up form that is <b>off</b> by default at program start. You may initiate reminding based on UTC time or based on passed minutes, but not both.<br/>
Closing form will initiate the timer. If your linux has several desktops this pop-up will show up on the top of current desktop. No matter on what desktop your cqrlog is open.<</p>
<p>You can also write something useful to ”Remember to:” memo. ( 255 characters, one line ). For example ”Sked on 20m with OH1XYZ” or ” Call wife” or ”Pick kids from school” to remember what to do at right time while you are busy with your qsos. All settings are saved over program restart.</p>
<p align=center><img src=img/line.png></p>
<br>
<table width="100%" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="index.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h20.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body>
</html>

27
help/wkdgrid.html Normal file
View File

@ -0,0 +1,27 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8"/>
<title></title>
<meta name="generator" content="LibreOffice 5.3.6.1 (Linux)"/>
<meta name="created" content="2017-10-30T15:20:07.459999558"/>
<meta name="changed" content="2017-10-30T15:26:24.409268862"/>
</head>
<body lang="fi-FI" dir="ltr">
<h3>Worked grids</h3>
<p ><img src="img/wkdgrid9.png" name="9" width="643" height="394">
</img>
<br/>Worked grids map gives graphical view of locators worked in addition of cqrlog's own text based information. As for JT-mode workers this map us useful also for V-,U-,SHF workers who are collecting locator grids.<br/>
<br/>Map shows worked grids on selected band and mode, or all bands and modes. Or you can select ”Follow rig” and then map follows band and mode that rig is sending to cqrlog via rigctld.<br/>
<br/>Confirmed main grids show up as green, unconfirmed as red. Subgrids show up with dots inside main grid with coresponding colors. You can click any main grid to zoom it. Again colors tell you about confirmation.</p>
<p ><img src="img/wkdgrid10.png" name="10" width="549" height="339">
</img>
<br/>Clicking again on zoomed main grid brings back whole map.
</p>
<p><img src="img/wkdgrid11.png" name="11" width="521" height="319" border="0"/>
<br/>By selecting ”Show worked only” removes grids that are not worked from map. At any time you are able to save currently shown map as an image for other purposes.</p>
<p>Grid map, unfortunately, does not scale. So size is what it is and you have to accept that. Sorry, but it simplified a lot the production of graphics.</p>
</body>
</html>

244
help/wsjt.html Normal file
View File

@ -0,0 +1,244 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>CQRLOG - Supported Radio Types</title>
</head>
<body>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><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 width="33%" align="left">&nbsp;&lt;<a href="h20.html#ah33"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h25.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<h2 >Wsjt remote mode</h2>
<ul style="margin-left: 40px;">
<li><a href="wsjt.html#w1">Wsjt-x CQ-monitor</a></li>
<li><a href="wsjt.html#w2">Colors &amp; fonts</a></li>
<li><a href="wsjt.html#w3">Alerts</a></li>
<li><a href="wsjt.html#w4">Starting qso from wsjtx-monitor</a></li>
<li><a href="wsjt.html#w5">Logging qso to cqrlog</a></li>
<li><a href="wsjt.html#w6">Starting fldigi and wsjt-x via cqrlog</a></li>
</ul>
<p>From New QSO / File select 'Remote mode for wsjt'</p>
<img src="img/wsjt2.png" name="2" width="139" height="238" border="0"/>
<p> Remote mode for WSJT-X-communication is made via UDP dtatgrams that and is supported from WSJT-X 1.5.0 program upwards.<br/>
Cqrlog supports WSJT-X UDP remote mode since version 1.9.1
</p>
<img src="img/wsjt18.png" name="18" width="144" height="137" border="0"/>
<p > When remote mode is selected it shows last received WSJT-X packet type
number after text “Wsjt-x remote” text. Also color of text changes while receiving packets.<br/>
These will show you that UDP link is alive between these programs.</font></p>
<p>New QSO / Window list</p>
<img src="img/wsjt1.png" name="1" width="140" height="282" border="0"/>
<p>“ Wsjtx monitor “ is visible only if WSJT-X remote mode is selected. Others can be found from there all the time.</font></p>
<h3><a name="w1"></a>Wsjt-x CQ-monitor</h3>
<p ><img src="img/wsjt16.png" name="16" width="363" height="282">
</img>
</p>
<p >Wsjt-x CQ-monitor form opens when you select ”Remote mode for wsjtx” from ”File” of NewQSO window.</p>
<p >You can close this window and reopen it later via NewQSO/Window/Wsjt-x monitor that is visible only when
remote mode is selected. While it is closed it will not update it’s contents.<br/>
Only remote logging and call qrz/hamqth seek are used then.</p>
<p ><img src="img/wsjt20.png" name="20" width="353" height="83">
</img></p>
Top line will show band and mode that is in use, Checking ”<b>no history”</b> will clean monitor on every decoded RX-period. If not checked form will show also older Cqs (scrolling) to see what you missed while having a coffee break :). Only 15 lines, how ever.
If you do not want any information texts, just alerts, you can check “<b>noTxt”</b> to prevent richmemo text updates and minimize window (or drop it completely down with (<b>_</b>) while alerts are still working.</p>
<p ><img src="img/wsjt21.png" name="21" width="363" height="282">
</img></p>
Checking <b>“flw”</b> new part of monitor opens. This will make easier to follow a DX who does not stay on same frequency, but jumps around answering to callers.
</br>You are able to type a callsing, a part of it (text-in-text search) or you can push right mouse button down and paint any call from wsjtx main screen or from CQ-monitor and drag and drop callsing to the left side
edit box.
</br> After pressing <b>“Follow”</b> (turns green) the call is checked to be written in upcase letters and spaces are trimmed from start and end. Next decoding periods will show a line at right side box if that call is as originating (2nd) callsign and the line is not CQ or for YOUR Call.
That box uses same font and size as CQ-monitor.
</br></br>Line contains: <b>decoding_period_time</b> | <b>delta_frequency</b> | <b>the_message</b>.
</br>Alerts are not connected to this line. Follow and flw states and callsing are saved over program restart.
<p>Line of CQ-monitor contains:
<ul>
<li/> time</br>
<li/> mode symbol. Same that wsjt-x uses.</br>
<li/> callsign with color and low/Upcase coding.</br>
<li/> locator grid with color and low/Upcase coding </br>
<li/> country name (cut to 15chrs). Overlayed with “CQ:xx” and <b>different color</b> if station is calling directed CQ like: CQ DX, AS, AF, OC, NA, SA .. or CQ CALLSIGN DX.<br/>
This is set as warning for you to check that you are in directed area before answering to his/her CQ.<br/>
I.E. <b>In case of </b><i><b>CQ DX</b></i> <b>you should be in DIFFERENT CONTINENT as the CQ caller </b>to be a valid DX for him. Program does not warn you if it thinks you are real DX for caller. Otherwise it does.</br>
<li/> information of DXCC status compared to your logged qsos.</br>
</ul></p>
<h3><a name="w2"></a>Colors &amp; fonts</h3>
<p>
CQ-monitor has a new design. Window is adjustable and font + size can be changed.<br/>
Font style can not be changed as now “Qso never” (default Green) is printed also with bold while all other texts are in normal style.</p>
<img src="img/wsjt15.png" name="15" width="418" height="183">
</img>
<img src="img/wsjt17.png" name="17" width="344" height="203" border="0">
<img/></br>
Colors, that user can now change, will tell if station is worked
before on <font color="#ff0066"><b>this band and mode</b></font><font color="#ff0066">,</font>
<font color="#cc66ff">this band </font><font color="#cc66ff"><b>but
not this mode,</b></font> <font color="#cc9900">some </font><font color="#cc9900"><b>other
band/mode</b></font> and <font color="#00cc00"><b>never</b></font><font color="#00cc00">
on any band/mode</font>.</p>
<p>Same color coding is applied also for locator grid.<br/>
Full locator (means 4 first characters of locator) worked before on <b>this band
and mode</b>, this band <b>but not this mode, </b>some <b>other band/mode </b>and <b>never</b> on any band/mode.
<br/>
If no hits found for full locator then main locator (2 first
letters) are checked same way next . Worked before on <b>this band
and mode</b>, this band <b>but not this mode, </b>some <b>other
band/mode </b>and <b>never</b> on any band/mode.
</p><p>
Calls and locators that are <font color="#ff0066">worked before on
</font><font color="#ff0066"><b>this band and mode</b></font><font color="#ff3333">
</font>are also printed in <b>lowercase</b> letters while all others
are printed with <b>UPPERCASE</b>.</p>
<p >
<img src="img/wsjt19.png" name="19" width="262" height="213" border="0">
<img/>
</br><b>NOTE:</b> Using monospace fonts will keep monitor columns in
order.</p>
<h3><a name="w3"></a></a>Alerts</h5>
</p>
<p>At bottom there are 3 alerts to select. The priority of alerts is same as numbering here. Smaller number overrides previous having
highest priority. Alert is executed only once per every decoding section.</p>
<ol>
<li/>”<b>My Alert</b>” will alert if someone answers your
cq-call. It is useful if you are reading your mails, Facebook or
what ever on another desktop while calling CQ with Wsjt-x :)</br>
<li/>“<b>All</b>”will extend “MyAlert” so that all lines that start with your
callsign give alerts. There are stations that answer to CQ directly
with report, so this wakes you up also then. When using FT8 this
might be little annoying but is easy to check off.</br>
<li/>”<b>Text [ ]Alert</b>” will alert if text-in-text if typed text, case
sensitive, compared to complete monitor line.
<br/> <b>Example:</b> alert from new country by setting “w c” string to text alert. It fits
in to the middle of “New country” string. Text can have spaces,
but not at start or at end.<br/>
Press button <b>“Text”</b> to change to call alerts.<br/>
”<b>Call [ ]Alert</b>” will alert if text-in-text if typed text, upcase, fits callsign of
monitor line. As option, one asterisk can be used at start or end to
indicate starts-with or ends-with search. Several search strings can
be inserted with comma separation.<br/>
Press button <b>“Call”</b> to change to text alerts.</p>
<p>Text you have typed is read only after you leave edit box. Then
spaces from start and end are removed and in case of “call alert”
text is changed uppercase.<br/>
To activate alert press ”<b>Alert</b>”
to turn it’s text green. (it also takes you away from edit box)</p>
<p><img src="img/wsjt27.png" name="27"" width="441" height="47">
</img><br/>
<img src="img/wsjt28.png" name="28" width="442" height="42">
</img></p>
<li/>”<b>Loc Alert</b>” will alert when there is new main grid that you have not worked.
<li/></ol></p>
<p >To make alerts do something you have to
add a script file ~/.config/cqrlog/voice_keyer/voice_alert.sh<br/>
This
script gets parameter $1 of “my”,”loc”,”text” or “call”
depending of alert given.<br/>
By using these parameters with your
script you can play sound that you want, or do anything else you like
to happen when alert is issued.<br/>
<br/>
<b>NOTE: Try to keep
script running time as short as possible.</b></p>
<p >voice_alert.sh:<br/>
--------------------------------------------------------------------------<br/>
#!/bin/bash<br/>
#
//audio file name (prefix) played on alert<br/>
# //can be:'my' =
ansver to my cq,<br/>
# // 'loc' = new main grid,<br/>
# // 'text'=
text found from monitor line <br/>
# // 'call'= text fits to the
callsign<br/>
# // create files you want to be played<br/>
# scirpt
is seeking names with '.wav' suffix! Change if needed <br/>
#select
audio card(if needed) and play alert message</p>
<p>aplay ~/.config/cqrlog/voice_keyer/$1.wav</p>
<h3><a name="w4">Starting qso from wsjtx-monitor</h3>
<p>You can start Wsjt-x qso by double click a CQ-monitor’s line. Wsjt-x will move to callers QRG and initiate TX.</p>
<p><img src="img/wsjt4.png" name="4" width="466" height="353">
</img><br/>
This requires Wsjt-x's <b>Configuration/Settings/Reporting</b> to have <font color="#ff0066">at
least</font> “<b>Accept</b> <b>UDP requests</b>” selected.
<br/>Setting also “ Accepted UDP request restores window” will return focus from CQ-monitor back to wsjt-x main window.<br/>
<br/>
A line when someone has answered to you (your call is first at Wsjt-x data line) has ”<b>=</b>” sign just at start of callsign and
locator is marked <b>&lt;!!&gt;.
<br/> </b>Clicking that line again does not continue qso.<br/>
Wsjt-x remote does not allow this kind of command preventing automated qsos. So at this case you have
to go to Wsjt-x screen and initiate report sending by yourself. Or set “auto seg” at wsjt-x/FT8.</p>
<p>Either qso is started from CQ-monitor, or Wsjt-x screen itself, the opponent callsign is added right away to New QSO's callsign
field. This way you can see right away if you have had qso with this station on other modes/bands and also all other information like DXCC
status, QRZ/HamQTH information etc.</p>
<h3><a name="w5"></a></a>Logging qso to cqrlog</h5>
<p>
When you <font color="#ff0066"> either press “Log QSO”</font> at wsjt-x main window,<font color="#ff0066"> or
</font>get it open automatic when sending 73 by <font color="#ff0066">checking Wsjt-x's </font>
<font color="#ff0066"><b>Configuration/Settings/Reporting/Prompt me to log qso</b></font> ,you will have wsjt-x's logging form open.
<br/>Check it’s information, add power and remarks if needed. After finishing with it <font color="#ff0066">press it’s OK-button</font><u>Then information is transferred to cqrlog.</u> <br/>
<br/>
</u><b>NOTE: </b><font color="#ff0066"><b>DO NOT press</b></font> cqrlog/NewQSO/Save QSO [enter] - button to save qso!</p>
<p>
If you have enabled auto search from QRZ.com/HamQth.com in cqrlog's preferences all information is fetched during your first transmit (report sending period).<br/>
You may alter that information in NewQSO form and it is saved along with wsjt-x logging information.<br/>
<br/>
In case that fetched data has same, but longer locator than wsjt-x qso data has the longer is logged to cqrlog.<br/>
<b>I.E </b>wsjt-x data gives KP01, but QRZ.com KP01TN, the longer (more complete) is logged.<br/>
If locators differ wsjt-x data is used as it might be a portable or other special qth.</p>
<a name="w6"><h3>Starting fldigi and wsjt-x via cqrlog</h3></a>
<p>You can set preferences so that cqrlog will start fldigi and/or wsjt-x programs for you when you enter remote mode. This is very handy, but doing that has also one risk.
<br/>When fldigi or wsjt-x has been started as a child process of cqrlog they will die at the moment cqrlog crashes for some reason.
<br/>If you start them manually as processes of their own and then activate remote mode from cqrlog they keep on running if cqrlog
dies. You can finish your ongoing qso, start cqrlog again, set remote mode on and then log the qso in normal manner.</p>
</body>
</html>
<p align=center><img src=img/line.png></p>
<br>
<table width="100%" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h20.html#ah33"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h25.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body>
</html>

3
src/CHANGELOG
View File

@ -3,6 +3,9 @@ Legend:
+ new feature
- bugfix
--------------------
2.1.0 (04.11.2017)
#fixed some help files to be a bit more up to date (Saku, OH1KH)
-dUtils: BandToFrequency: 630M definition was missing. (Saku, OH1KH)
2.1.0 (29.10.2017)
+coped "Show only active band" checkbox to Band map filter for quick access. (Saku, OH1KH)
+Added "Re/Set" button to Export "Choose fields to export" dialog for set/reset all check boxes in one go. (Saku, OH1KH)

5
src/dUtils.pas
View File

@ -1163,6 +1163,11 @@ begin
Result := '0.139';
exit;
end;
if band = '630M' then
begin
Result := '0.472';
exit;
end;
if band = '160M' then
begin
if (mode = 'CW') then