latest user manual PDF

USER_MANUAL.html

@@ -6,7 +6,7 @@
 <p>FreeDV GUI can be challenging to set up. The easiest way is to find a friend who has set up FreeDV and get them to help. Alternatively, this section contains several tips to help you get started.</p>
 <h3 id="sound-card-configuration"><span class="header-section-number">1.2.1</span> Sound Card Configuration</h3>
 <p>For Receive only operation you just need one sound card; this is a great way to get started.</p>
-<p>For Tx/Rx operation you need two sound cards. One connects to your radio, and one for the operator. The sound card connecting to the radio can be a rig interface device like a Signalink, Rigblaster, your radio's internal USB sound card, or a home brew rig interface.</p>
+<p>For Tx/Rx operation you need two sound cards. One connects to your radio, and one for the operator. The sound card connecting to the radio can be a rig interface device like a Signalink, RIGblaster, your radio's internal USB sound card, or a home brew rig interface.</p>
 <p>The second sound card is often a set of USB headphones or your computer's internal sound card.</p>
 <h3 id="receive-only-one-sound-card"><span class="header-section-number">1.2.2</span> Receive Only (One Sound Card)</h3>
 <p>Start with just a receive only station. You just need the basic sound hardware in your computer, for example a microphone/speaker on your computer.</p>
@@ -87,13 +87,13 @@
 <p>The Tools - PTT dialog supports three different ways to control PTT on your radio:</p>
 <ul>
 <li>VOX: sends a tone to the left channel of the Transmit/To Radio sound card</li>
-<li>HamLib: support for many different radios via the HamLib library and a serial port</li>
+<li>Hamlib: support for many different radios via the Hamlib library and a serial port</li>
 <li>Serial Port: direct access to the serial port pins</li>
 </ul>
 <p>Once you have configured PTT, try the <strong>Test</strong> button.</p>
 <p>Serial PTT support is complex. We get many reports that FreeDV PTT doesn't work on a particular radio, but may work fine with other programs such as Fldigi. This is often a mis-match between the serial parameters Hamlib is using with FreeDV and your radio. For example you may have changed the default serial rate on your radio. Carefully check the serial parameters on your radio match those used by FreeDV in the PTT Dialog.</p>
 <p>Also see <a href="#common-problems">Common Problems</a> section of this manual.</p>
-<h3 id="hamlib"><span class="header-section-number">1.5.1</span> HamLib</h3>
+<h3 id="hamlib"><span class="header-section-number">1.5.1</span> Hamlib</h3>
 <p>Hamlib comes with a default serial rate for each radio. If your radio has a different serial rate change the Serial Rate drop down box to match your radio.</p>
 <p>When <strong>Test</strong> is pressed, the &quot;Serial Params&quot; field is populated and displayed. This will help track down any mismatches between Hamlib and your radio.</p>
 <p>If you are really stuck, download Hamlib and test your radio's PTT using the command line <code>rigctl</code> program.</p>
@@ -256,7 +256,7 @@ FMA             -       Supports FMA extensions using YMM state</code></pre>
 <p>FreeDV 700D is sensitive to tuning. To obtain sync you must be within +/- 60Hz of the transmit frequency. This is straightforward with modern radios which are generally accurate to +/-1 Hz, but requires skill and practice when used with older, VFO based radios.</p>
 <h3 id="freedv-700e"><span class="header-section-number">1.8.2</span> FreeDV 700E</h3>
 <p>FreeDV 700E was developed in December 2020 using lessons learned from on air operation of 700C and 700D. A variant of 700D, it uses a shorter frame size (80ms) to reduce latency and sync time. It is optimised for fast fading channels channels with up to 4Hz Doppler spread and 6ms delay spread. FreeDV 7000E uses the same 700 bit/s codec as FreeDV 700C and 700D. It requires about 3dB more power than 700D, but can operate reliably on fast fading channels.</p>
-<p>The 700E release also includes optional compression (clipping) of the 700D an 700E transmit waveforms to reduce the Peak to Average Power Ratio to about 4dB. For example a 100W PEP transmitter can be driven to about 40W RMS. This is an improvement of 6dB over previous releases of FreeDV 700D. Before enabling the clipper make sure your transmitter is capable of handling sustained high average power without damage.</p>
+<p>The 700E release also includes optional compression (clipping) of the 700D and 700E transmit waveforms to reduce the Peak to Average Power Ratio to about 4dB. For example a 100W PEP transmitter can be driven to about 40W RMS. This is an improvement of 6dB over previous releases of FreeDV 700D. Before enabling the clipper make sure your transmitter is capable of handling sustained high average power without damage.</p>
 <p>Clipping can be enabled via Tools-Options.</p>
 <p>On good channels with high SNR clipping may actually reduce the SNR of the received signal. This is intentional - we are adding some pre-distortion in order to increase the RMS power. Forward error correction (FEC) will clean up any errors introduced by clipping, and on poor channels the benefits of increased signal power outweigh the slight reduction in SNR on good channels.</p>
 <h3 id="freedv-2020"><span class="header-section-number">1.8.3</span> FreeDV 2020</h3>
@@ -332,7 +332,7 @@ FMA             -       Supports FMA extensions using YMM state</code></pre>
 <li><p>The High Bandwidth option gives better performance on channels where the phase changes quickly, for example fast fading HF channels and the Es'Hail 2 satellite. When unchecked, the phase estimator bandwidth is automatically selected. It starts off high to enable fast sync, then switches to low bandwidth to optimise performance for low SNR HF channels.</p></li>
 <li><p>The DPSK (differential PSK) checkbox has a similar effect - better performance on High SNR channels where the phase changes rapidly. This option converts the OFDM modem to use differential PSK rather than coherent PSK. DPSK is used by earlier FreeDV modes such as FreeDV 1600. It affects the Tx and Rx side, so both sides must select DPSK.</p></li>
 </ol>
-<p>If you have problems with 700D or 2020 sync even though you have a strong signal - try these option.</p>
+<p>If you have problems with 700D or 2020 sync even though you have a strong signal - try these options.</p>
 <h2 id="helping-improve-freedv"><span class="header-section-number">1.11</span> Helping Improve FreeDV</h2>
 <p>If you have an interesting test case, for example:</p>
 <ol style="list-style-type: decimal">
@@ -386,7 +386,7 @@ FMA             -       Supports FMA extensions using YMM state</code></pre>
 </table>
 <p>The sample clock offset is the estimated difference between the modulator (tx) and demodulator (rx) sample clocks. For example if the transmit station sound card is sampling at 44000 Hz and the receive station sound card 44001 Hz, the sample clock offset would be ((44000-44001)/44000)*1E6 = 22.7 ppm.</p>
 <h3 id="timing-delta-tab"><span class="header-section-number">1.12.2</span> Timing Delta Tab</h3>
-<p>This indicates the symbol timing estimate of the demodulator, in the range of +/- 0.5 of a symbol. With off air signals this will have a saw tooth appearance, as the demod tracks the modulator sample clock. The steeper the slope, the greater the sample clock offset.</p>
+<p>This indicates the symbol timing estimate of the demodulator, in the range of +/- 0.5 of a symbol. With off air signals this will have a sawtooth appearance, as the demod tracks the modulator sample clock. The steeper the slope, the greater the sample clock offset.</p>
 <ul>
 <li><a href="http://www.rowetel.com/?p=6041">FreeDV 1600 Sample Clock Offset Bug</a></li>
 <li><a href="http://www.rowetel.com/?p=2433">Testing a FDMDV Modem</a></li>
@@ -402,7 +402,7 @@ FMA             -       Supports FMA extensions using YMM state</code></pre>
 --smtp_port 587 your@gmail.com your_pass</code></pre>
 <h3 id="sound-card-debug"><span class="header-section-number">1.12.4</span> Sound Card Debug</h3>
 <p>These features were added for FreeDV 700D, to help diagnose sound card issues during development.</p>
-<p>Tools - Options dialog:</p>
+<h3 id="tools---options-dialog"><span class="header-section-number">1.12.5</span> Tools - Options dialog:</h3>
 <p>Debug FIFO and PortAudio counters: used for debugging audio problems on 700D. During beta testing there were problems with break up in the 700D Tx and Rx audio on Windows.</p>
 <p>The PortAudio counters (PortAudio1 and PortAudio2) should not increment when running in Tx or Rx, as this indicates samples are being lost by the sound driver which will lead to sync problems.</p>
 <p>The Fifo counter outempty1 counter should not increment during Tx, as this indicates FreeDV is not supplying samples fast enough to the PortAudio drivers. The results will be resyncs at the receiver.</p>
@@ -417,7 +417,7 @@ FMA             -       Supports FMA extensions using YMM state</code></pre>
 <p>The txThreadPriority checkbox reduces the priority of the main txRx thread in FreeDV which may help the sound driver thread process samples.</p>
 <p>The txRxDumpTiming check box dumps timing information to a console that is used for debugging the rx break up problem on 700D. Each number is how many ms the txRxThread took to run.</p>
 <p>The txRxDumpTiming check box dumps the number of samples free in the tx FIFO sending samples to the Tx. If this hits zero, your tx audio will break up and the rx will lose sync. Tx audio break up will also occur if you see &quot;outfifo1&quot; being incremented on the &quot;Fifo&quot; line during tx. Try increasing the FifoSize.</p>
-<h3 id="test-frame-histogram"><span class="header-section-number">1.12.5</span> Test Frame Histogram</h3>
+<h3 id="test-frame-histogram"><span class="header-section-number">1.12.6</span> Test Frame Histogram</h3>
 <p>This feature was developed for testing FreeDV 700C. Select the Test Frame Histogram tab on Front Page</p>
 <p>Displays BER of each carrier when in &quot;test frame&quot; mode. As each QPSK carrier has 2 bits there are 2*Nc histogram points.</p>
 <p>Ideally all carriers will have about the same BER (+/- 20% after 5000 total bit errors), however problems can occur with filtering in the tx path. If one carrier has less power, then it will have a higher BER. The errors in this carrier will tend to dominate overall BER. For example if one carrier is attenuated due to SSB filter ripple in the tx path then the BER on that carrier will be higher. This is bad news for DV.</p>
@@ -428,7 +428,7 @@ FMA             -       Supports FMA extensions using YMM state</code></pre>
 <li><p>Monitor the error histogram for a few minutes, until you have say 5000 total bit errors. You have a problem if the BER of any carrier is more than 20% different from the rest.</p></li>
 <li><p>A typical issue will be one carrier at 1.0 and the others at 0.5, indicating the poorer carrier BER is twice the larger.</p></li>
 </ol>
-<h3 id="full-duplex-testing-with-loopback"><span class="header-section-number">1.12.6</span> Full Duplex Testing with loopback</h3>
+<h3 id="full-duplex-testing-with-loopback"><span class="header-section-number">1.12.7</span> Full Duplex Testing with loopback</h3>
 <p>Tools - Options - Half Duplex check box</p>
 <p>FreeDV GUI can operate in full duplex mode which is useful for development or listening to your own FreeDV signal as only one PC is required. Normal operation is half duplex.</p>
 <p>Tx and Rx signals can be looped back via an analog connection between the sound cards.</p>
@@ -440,7 +440,7 @@ FMA             -       Supports FMA extensions using YMM state</code></pre>
                           - Transmit Tab - To Radio select   -&gt; Loopback: Loopback PCM (hw:1,1)</code></pre>
 <h2 id="tips"><span class="header-section-number">1.13</span> Tips</h2>
 <ol style="list-style-type: decimal">
-<li>The space-bar can be used to toggle PTT.</li>
+<li>The space bar can be used to toggle PTT.</li>
 <li>You can left click on the main window to adjust tuning, the vertical red line on the frequency scale will show the current centre frequency. FreeDV will automatically track any drift once it syncs.</li>
 </ol>
 <h2 id="converting-this-document-to-pdf"><span class="header-section-number">1.14</span> Converting this document to PDF</h2>