FreeDV
/
freedv-gui
mirror of https://github.com/drowe67/freedv-gui.git
1
0
Fork 0
Code Issues Releases Wiki Activity

latest user manual PDF

pull/109/head
Mooneer Salem 2021-03-25 08:23:13 +00:00
parent 921dff5b19
commit a2ad8e1152
2 changed files with 155 additions and 151 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

306
USER_MANUAL.html
View File

@ -5,11 +5,11 @@
<p>This section contains instructions to help you get started.</p>
<h2 id="sound-card-configuration"><span class="header-section-number">2.1</span> Sound Card Configuration</h2>
<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>The second sound card is often a set of USB headphones or your computer's internal sound card.</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>
<h2 id="receive-only-one-sound-card"><span class="header-section-number">2.2</span> Receive Only (One Sound Card)</h2>
<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>
<ol style="list-style-type: decimal">
<ol type="1">
<li>Open the <em>Tools - Audio Config</em> Dialog</li>
<li>At the bottom select <em>Receive</em> Tab</li>
<li>In <em>Input To Computer From Radio</em> select your default sound input device (usually at the top)</li>
@ -20,10 +20,10 @@
<li>Press OK to close the dialog</li>
</ol>
<p>When you press Start FreeDV will start decoding any incoming signals on the microphone input, playing the decoded audio out of your speaker. If no valid FreeDV signals are received, no audio will be played.</p>
<p>If you connect the microphone input on your computer to your radio receiver, you can decode off air signals. If you have a rig interface, try configuring that as the <em>From Radio To Computer</em> device, with your computer's sound card as the <em>From Computer To Speaker/Headphone</em> device.</p>
<p>If you don't have anyone to transmit FreeDV signals to you, try the test wave files in the next section.</p>
<p>If you connect the microphone input on your computer to your radio receiver, you can decode off air signals. If you have a rig interface, try configuring that as the <em>From Radio To Computer</em> device, with your computer’s sound card as the <em>From Computer To Speaker/Headphone</em> device.</p>
<p>If you don’t have anyone to transmit FreeDV signals to you, try the test wave files in the next section.</p>
<h2 id="test-wave-files"><span class="header-section-number">2.3</span> Test Wave Files</h2>
<p>In https://github.com/drowe67/freedv-gui/tree/master/wav are audio files containing off-air FreeDV modem signals. There is one for each FreeDV mode. Select a FreeDV mode and press Start. Choose a file using &quot;Tools - Start/Stop Play File From Radio&quot;. You should hear decoded FreeDV speech.</p>
<p>In https://github.com/drowe67/freedv-gui/tree/master/wav are audio files containing off-air FreeDV modem signals. There is one for each FreeDV mode. Select a FreeDV mode and press Start. Choose a file using “Tools - Start/Stop Play File From Radio”. You should hear decoded FreeDV speech.</p>
<p>These files will give you a feel for what FreeDV signals sound like, and for the basic operation of the FreeDV software.</p>
<h2 id="transmitreceive-two-sound-cards"><span class="header-section-number">2.4</span> Transmit/Receive (Two Sound Cards)</h2>
<p>For Tx/Rx operation you need to configure two sound cards, by setting up Tools - Audio Config <em>Transmit</em> and <em>Receive</em> Tabs.</p>
@ -31,9 +31,9 @@
<p>When transmitting, FreeDV takes your voice <strong>from</strong> the microphone, and encodes it to a FreeDV signal in you computer which is sent <strong>to</strong> your radio for transmission over the air.</p>
<table>
<colgroup>
<col width="14%" />
<col width="42%" />
<col width="42%" />
<col style="width: 14%" />
<col style="width: 42%" />
<col style="width: 42%" />
</colgroup>
<thead>
<tr class="header">
@ -66,17 +66,17 @@
</tbody>
</table>
<h2 id="changing-audio-devices"><span class="header-section-number">2.5</span> Changing Audio Devices</h2>
<p>If you change audio devices (e.g. add or remove sound cards, USB hardware), it's a good idea to check the Tools/Audio Config dialog before pressing <strong>Start</strong>, to verify the audio devices are as expected. This is particularly important if any audio devices e.g. Headsets, USB Sound Cards, or Virtual Cables have been disconnected since the last time FreeDV was used.</p>
<p>If you change audio devices (e.g. add or remove sound cards, USB hardware), it’s a good idea to check the Tools/Audio Config dialog before pressing <strong>Start</strong>, to verify the audio devices are as expected. This is particularly important if any audio devices e.g. Headsets, USB Sound Cards, or Virtual Cables have been disconnected since the last time FreeDV was used.</p>
<p>Hitting <strong>Refresh</strong> in the lower left hand corner of the Tools/Audio Config will normally update the audio devices list. Keeping a screen shot of a known working configuration will be useful for new users. Unexpected audio configuration changes may also occur following a Windows updates.</p>
<p>Another solution is to re-start FreeDV and check Tools/Audio Config again after changing any audio hardware.</p>
<p>If you change/remove USB audio devices without refreshing Tools/Audio Config, FreeDV may crash.</p>
<h2 id="sound-card-levels"><span class="header-section-number">2.6</span> Sound Card Levels</h2>
<p>Sound card levels are generally adjusted in the computer's Control Panel or Settings, or in some cases via controls on your rig interface hardware or menus on your radio.</p>
<p>Sound card levels are generally adjusted in the computer’s Control Panel or Settings, or in some cases via controls on your rig interface hardware or menus on your radio. In-app adjustments can also be done by using the ‘TX Level’ slider at the bottom of the main screen; anything below 100% attenuates the transmit signal.</p>
<p>When FreeDV is running, you can observe the sound card signals in the main window tabs (From Radio, From Mic, To Speaker).</p>
<ol style="list-style-type: decimal">
<ol type="1">
<li><p>On receive, FreeDV is not very sensitive to the <strong>From Radio</strong> level, adjust so it is mid-range and not clipping. FreeDV uses phase shift keying (PSK) so is not sensitive to amplitude.</p></li>
<li><p>The transmit level from your computer to your radio is important. On transmit, adjust your level so that the ALC is <strong>just</strong> being nudged. More <strong>is not better</strong> with the FreeDV transmit signal. Overdriving your transmitter will lead to a distorted transit signal, and a poor SNR at the receiver. This is a very common problem.</p></li>
<li><p>FreeDV 700D and 700E can drive your transmitter at an average power of 40% of it's peak power rating. For example 40W RMS for a 100W PEP radio. Make sure your transmitter can handle continuous power output at these levels, and reduce the power if necessary.</p></li>
<li><p>FreeDV 700D and 700E can drive your transmitter at an average power of 40% of it’s peak power rating. For example 40W RMS for a 100W PEP radio. Make sure your transmitter can handle continuous power output at these levels, and reduce the power if necessary.</p></li>
<li><p>Adjust the microphone audio so the peaks are not clipping, and the average is about half the maximum.</p></li>
</ol>
<h2 id="audio-processing"><span class="header-section-number">2.7</span> Audio Processing</h2>
@ -84,7 +84,7 @@
<ul>
<li><p>On receive, DSP noise reduction should be off.</p></li>
<li><p>On transmit, speech compression should be off.</p></li>
<li><p>Keep the receive audio path as &quot;flat&quot; as possible, no special filters.</p></li>
<li><p>Keep the receive audio path as “flat” as possible, no special filters.</p></li>
<li><p>FreeDV will not work any better if you band pass filter the off air received signals. It has its own, very tight filters in the demodulator.</p></li>
</ul>
<h2 id="ptt-configuration"><span class="header-section-number">2.8</span> PTT Configuration</h2>
@ -95,46 +95,46 @@
<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>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>
<h2 id="hamlib"><span class="header-section-number">2.9</span> HamLib</h2>
<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>
<p>When <strong>Test</strong> is pressed, the “Serial Params” 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>
<h2 id="icom-radio-configuration"><span class="header-section-number">2.10</span> Icom Radio Configuration</h2>
<p>If using an Icom radio, Hamlib will use the radio's default CI-V address when connecting. If this has been changed, you can specify the correct address in the &quot;Radio Address&quot; field (valid values are 00 through FF in hexadecimal).</p>
<p>Note that &quot;00&quot; is the &quot;wildcard&quot; CI-V address. Your radio must have the &quot;CI-V Transceive&quot; option enabled in order for it to respond to commands to that address. Otherwise, FreeDV must be configured to use the same CI-V address as configured in the radio. For best results, ensure that there are no other Icom/CI-V capable devices in the chain if &quot;00&quot;/&quot;CI-V Transceive&quot; is used.</p>
<p>If using an Icom radio, Hamlib will use the radio’s default CI-V address when connecting. If this has been changed, you can specify the correct address in the “Radio Address” field (valid values are 00 through FF in hexadecimal).</p>
<p>Note that “00” is the “wildcard” CI-V address. Your radio must have the “CI-V Transceive” option enabled in order for it to respond to commands to that address. Otherwise, FreeDV must be configured to use the same CI-V address as configured in the radio. For best results, ensure that there are no other Icom/CI-V capable devices in the chain if “00”/“CI-V Transceive” is used.</p>
<h2 id="changing-com-port-on-windows"><span class="header-section-number">2.11</span> Changing COM Port On Windows</h2>
<p>If you change the COM port of a USB-Serial device in Device Manager, please unplug and plug back in the USB device. Windows/FreeDV won't recognise the device on the new COM Port until it has been unplugged/plugged.</p>
<p>If you change the COM port of a USB-Serial device in Device Manager, please unplug and plug back in the USB device. Windows/FreeDV won’t recognise the device on the new COM Port until it has been unplugged/plugged.</p>
<h2 id="usb-or-lsb"><span class="header-section-number">2.12</span> USB or LSB?</h2>
<p>On bands below 10 MHz, LSB is used for FreeDV. On 10MHz and above, USB is used. After much debate, the FreeDV community has adopted the same conventions as SSB, based on the reasoning that FreeDV is a voice mode.</p>
<p>As an aid to the above, FreeDV will show the current mode on the bottom of the window upon pressing the Start button if Hamlib is enabled and your radio supports retrieving frequency and mode information over CAT. If your radio is using an unexpected mode (e.g. LSB on 20 meters), it will display that mode on the bottom of the window next to the Clear button in red letters. When a session is not active, Hamlib isn't enabled, or if your radio doesn't support retrieving frequency and mode over CAT, it will remain grayed out with &quot;unk&quot; displaying instead of the mode (for &quot;unknown&quot;).</p>
<p>As an aid to the above, FreeDV will show the current mode on the bottom of the window upon pressing the Start button if Hamlib is enabled and your radio supports retrieving frequency and mode information over CAT. If your radio is using an unexpected mode (e.g. LSB on 20 meters), it will display that mode on the bottom of the window next to the Clear button in red letters. When a session is not active, Hamlib isn’t enabled, or if your radio doesn’t support retrieving frequency and mode over CAT, it will remain grayed out with “unk” displaying instead of the mode (for “unknown”).</p>
<h1 id="common-problems"><span class="header-section-number">3</span> Common Problems</h1>
<h2 id="overdriving-transmit-level"><span class="header-section-number">3.1</span> Overdriving Transmit Level</h2>
<p>This is a very common problem for first time FreeDV users. Adjust your transmit levels so the ALC is just being nudged. More power is not better with FreeDV. An overdriven signal will have poor SNR at the receiver. For FreeDV 700D/700E operation with the clipper, make sure your transmitter can sustain high average power levels without damage (e.g. 40W RMS on a 100W PEP radio).</p>
<h2 id="i-cant-set-up-freedv-especially-the-sound-cards"><span class="header-section-number">3.2</span> I can't set up FreeDV, especially the Sound Cards</h2>
<p>This is a very common problem for first time FreeDV users. Adjust your transmit levels so the ALC is just being nudged. More power is not better with FreeDV. An overdriven signal will have poor SNR at the receiver. For FreeDV 700D/700E operation with the clipper, make sure your transmitter can sustain high average power levels without damage (e.g. 40W RMS on a 100W PEP radio).</p>
<h2 id="i-cant-set-up-freedv-especially-the-sound-cards"><span class="header-section-number">3.2</span> I can’t set up FreeDV, especially the Sound Cards</h2>
<p>This can be challenging the first time around:</p>
<ol style="list-style-type: decimal">
<ol type="1">
<li><p>Try a receive only (one audio card) set up first.</p></li>
<li><p>Ask someone who already runs FreeDV for help.</p></li>
<li><p>If you don't know anyone local, ask for help on the digital voice mailing list. Be specific about the hardware you have and the exact nature of your problem.</p></li>
<li><p>If you don’t know anyone local, ask for help on the digital voice mailing list. Be specific about the hardware you have and the exact nature of your problem.</p></li>
</ol>
<h2 id="hamlib-does-not-work-with-my-icom-radio"><span class="header-section-number">3.3</span> Hamlib does not work with my Icom radio</h2>
<p>The most common issue with Icom radios is that the CI-V address configured in FreeDV does not match the address configured in the radio. Ensure that the CI-V address in both FreeDV and on the radio are the same. If &quot;00&quot; is used on the FreeDV side, ensure that the &quot;CI-V Transceive&quot; option is enabled on the radio or else the radio will not respond to requests directed to that address.</p>
<p>The most common issue with Icom radios is that the CI-V address configured in FreeDV does not match the address configured in the radio. Ensure that the CI-V address in both FreeDV and on the radio are the same. If “00” is used on the FreeDV side, ensure that the “CI-V Transceive” option is enabled on the radio or else the radio will not respond to requests directed to that address.</p>
<h2 id="i-need-help-with-my-radio-or-rig-interface"><span class="header-section-number">3.4</span> I need help with my radio or rig interface</h2>
<p>There are many radios, many computers, and many sound cards. It is impossible to test them all. Many radios have intricate menus with custom settings. It is unreasonable to expect the authors of FreeDV to have special knowledge of your exact hardware.</p>
<p>However someone may have worked through the same problem as you. Ask on the digital voice mailing list.</p>
<h2 id="cant-hear-anything-on-receive"><span class="header-section-number">3.5</span> Can't hear anything on receive</h2>
<h2 id="cant-hear-anything-on-receive"><span class="header-section-number">3.5</span> Can’t hear anything on receive</h2>
<p>Many FreeDV modes will not play any audio if there is no valid signal. You may also have squelch set too high. In some modes the <strong>Analog</strong> button will let you hear the received signal from the SSB radio.</p>
<p>Try the Test Wave Files above to get a feel for what a FreeDV signal looks and sounds like.</p>
<h2 id="the-signal-is-strong-but-freedv-wont-get-sync-and-decode"><span class="header-section-number">3.6</span> The signal is strong but FreeDV won't get sync and decode</h2>
<h2 id="the-signal-is-strong-but-freedv-wont-get-sync-and-decode"><span class="header-section-number">3.6</span> The signal is strong but FreeDV won’t get sync and decode</h2>
<p>Do you have the correct sideband? See USB or LSB section.</p>
<p>Is it a FreeDV signal? SSTV uses similar frequencies. To understand what FreeDV sounds like, see the Test Wave Files section.</p>
<h2 id="trouble-getting-sync-with-700d"><span class="header-section-number">3.7</span> Trouble getting Sync with 700D</h2>
<p>You need to be within +/- 60 Hz on the transmit signal. It helps if both the Tx and Rx stations tune to known, exact frequencies such as exactly 7.177MHz. On channels with fast fading sync may take a few seconds.</p>
<h2 id="ptt-doesnt-work.-it-works-with-fldigi-and-other-hamlib-applications."><span class="header-section-number">3.8</span> PTT doesn't work. It works with Fldigi and other Hamlib applications.</h2>
<h2 id="ptt-doesnt-work.-it-works-with-fldigi-and-other-hamlib-applications."><span class="header-section-number">3.8</span> PTT doesn’t work. It works with Fldigi and other Hamlib applications.</h2>
<p>Many people struggle with initial PTT setup:</p>
<ol style="list-style-type: decimal">
<ol type="1">
<li><p>Read the PTT Configuration section above.</p></li>
<li><p>Try the Tools - PTT Test function.</p></li>
<li><p>Check your rig serial settings. Did you change them from defaults for another program?</p></li>
@ -156,21 +156,18 @@ FMA - Supports FMA extensions using YMM state</code></pre>
<p>You may need to clean out the previous configuration. Try Tools - Restore Defaults. Set up your sound cards again with Tools - Audio Config.</p>
<h2 id="freedv-crashes-when-i-press-start"><span class="header-section-number">3.12</span> FreeDV crashes when I press Start</h2>
<p>Have you removed/changed USB audio devices? If you remove/change USB audio devices without pressing Tools - Audio Config, FreeDV may crash. See Changing Audio Devices above.</p>
<h2 id="freedv-cant-be-opened-on-osx-because-the-developer-cannot-be-verified"><span class="header-section-number">3.13</span> FreeDV can't be opened on OSX because the developer cannot be verified</h2>
<h2 id="freedv-cant-be-opened-on-osx-because-the-developer-cannot-be-verified"><span class="header-section-number">3.13</span> FreeDV can’t be opened on OSX because the developer cannot be verified</h2>
<p>From January 2020 Apple is enforcing notarization for all OSX applications. The FreeDV developers do not wish to operate within the Apple ecosystem due to the cost/intrusiveness of this requirement.</p>
<div class="figure">
<img src="contrib/osx_notarization1.png" alt="Notarization Error" />
<p class="caption">Notarization Error</p>
</div>
<figure>
<img src="contrib/osx_notarization1.png" alt="Notarization Error" /><figcaption>Notarization Error</figcaption>
</figure>
<p>Security &amp; Privacy shows the Open Anyway option for FreeDV:</p>
<div class="figure">
<img src="contrib/osx_notarization2.png" alt="Security and Privacy" />
<p class="caption">Security and Privacy</p>
</div>
<div class="figure">
<img src="contrib/osx_notarization3.png" alt="Open FreeDV" />
<p class="caption">Open FreeDV</p>
</div>
<figure>
<img src="contrib/osx_notarization2.png" alt="Security and Privacy" /><figcaption>Security and Privacy</figcaption>
</figure>
<figure>
<img src="contrib/osx_notarization3.png" alt="Open FreeDV" /><figcaption>Open FreeDV</figcaption>
</figure>
<p>Or you can use command line options:</p>
<pre><code>xattr -d com.apple.quarantine FreeDV.app</code></pre>
<p>or</p>
@ -181,111 +178,119 @@ FMA - Supports FMA extensions using YMM state</code></pre>
<p>The wave file for the voice keyer should be in 8kHz mono 16 bit sample form (16 kHz for 2020). Use a free application such as Audacity to convert a file you have recorded to this format.</p>
<h1 id="psk-reporter-experimental"><span class="header-section-number">5</span> PSK Reporter (Experimental)</h1>
<p>FreeDV has the ability to send FreeDV signal reports to <a href="https://pskreporter.info/">PSK Reporter</a> by enabling the option in Tools-Options and specifying your callsign and grid square. When enabled, this causes FreeDV to disable the free form <strong>Txt Msg</strong> field and only transmit the <strong>Callsign</strong> field.</p>
<p>FreeDV validates the received information before submitting a position report to PSK Reporter. This is to ensure that FreeDV does not report invalid callsigns to the service (e.g. ones that don't exist or that correspond to real non-FreeDV users). However, all received text will display in the main window even if it has errors.</p>
<p>Reports sent to PSK Reporter will display using the mode &quot;FREEDV&quot; for ease of filtering. The user's current mode (e.g. 700D, 1600, etc.) will also appear in the &quot;Using&quot; field when hovering over or clicking on a reception report.</p>
<p>Note that Hamlib must be enabled so PSK Reporter can read your radio's frequency. A message will appear on pushing Start if this is not the case.</p>
<h1 id="freedv-modes"><span class="header-section-number">6</span> FreeDV Modes</h1>
<p>FreeDV validates the received information before submitting a position report to PSK Reporter. This is to ensure that FreeDV does not report invalid callsigns to the service (e.g. ones that don’t exist or that correspond to real non-FreeDV users). However, all received text will display in the main window even if it has errors.</p>
<p>Reports sent to PSK Reporter will display using the mode “FREEDV” for ease of filtering. The user’s current mode (e.g. 700D, 1600, etc.) will also appear in the “Using” field when hovering over or clicking on a reception report.</p>
<p>Note that Hamlib must be enabled so PSK Reporter can read your radio’s frequency. A message will appear on pushing Start if this is not the case.</p>
<h1 id="multiple-mode-support-experimental"><span class="header-section-number">6</span> Multiple Mode Support (Experimental)</h1>
<p>FreeDV can simultaneously decode the following modes when selected prior to pushing “Start”:</p>
<ul>
<li>2020</li>
<li>700C/D/E</li>
<li>1600</li>
</ul>
<p>In addition, FreeDV can allow the user to switch between the above modes for transmit without having to push “Stop” first. These features can be enabled by going to Tools-&gt;Options-&gt;Modem and checking the “Simultaneously Decode All HF Modes” option. Note that this may consume significant additional CPU resources, which can cause decode problems. In addition, these features are automatically disabled if 800XA or 2400B are selected before pushing “Start” due to the significant additional CPU resources required to decode these modes.</p>
<h1 id="freedv-modes"><span class="header-section-number">7</span> FreeDV Modes</h1>
<p>The following table is a guide to the different modes, using analog SSB and Skype as anchors for a rough guide to audio quality:</p>
<table>
<thead>
<tr class="header">
<th>Mode</th>
<th align="center">Min SNR</th>
<th align="center">Fading</th>
<th align="center">Latency</th>
<th align="center">Speech Bandwidth</th>
<th align="center">Speech Quality</th>
<th style="text-align: center;">Min SNR</th>
<th style="text-align: center;">Fading</th>
<th style="text-align: center;">Latency</th>
<th style="text-align: center;">Speech Bandwidth</th>
<th style="text-align: center;">Speech Quality</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>SSB</td>
<td align="center">0</td>
<td align="center">8/10</td>
<td align="center">low</td>
<td align="center">2600</td>
<td align="center">5/10</td>
<td style="text-align: center;">0</td>
<td style="text-align: center;">8/10</td>
<td style="text-align: center;">low</td>
<td style="text-align: center;">2600</td>
<td style="text-align: center;">5/10</td>
</tr>
<tr class="even">
<td>1600</td>
<td align="center">4</td>
<td align="center">3/10</td>
<td align="center">low</td>
<td align="center">4000</td>
<td align="center">4/10</td>
<td style="text-align: center;">4</td>
<td style="text-align: center;">3/10</td>
<td style="text-align: center;">low</td>
<td style="text-align: center;">4000</td>
<td style="text-align: center;">4/10</td>
</tr>
<tr class="odd">
<td>700C</td>
<td align="center">2</td>
<td align="center">6/10</td>
<td align="center">low</td>
<td align="center">4000</td>
<td align="center">3/10</td>
<td style="text-align: center;">2</td>
<td style="text-align: center;">6/10</td>
<td style="text-align: center;">low</td>
<td style="text-align: center;">4000</td>
<td style="text-align: center;">3/10</td>
</tr>
<tr class="even">
<td>700D</td>
<td align="center">-2</td>
<td align="center">4/10</td>
<td align="center">high</td>
<td align="center">4000</td>
<td align="center">3/10</td>
<td style="text-align: center;">-2</td>
<td style="text-align: center;">4/10</td>
<td style="text-align: center;">high</td>
<td style="text-align: center;">4000</td>
<td style="text-align: center;">3/10</td>
</tr>
<tr class="odd">
<td>700E</td>
<td align="center">1</td>
<td align="center">7/10</td>
<td align="center">medium</td>
<td align="center">4000</td>
<td align="center">3/10</td>
<td style="text-align: center;">1</td>
<td style="text-align: center;">7/10</td>
<td style="text-align: center;">medium</td>
<td style="text-align: center;">4000</td>
<td style="text-align: center;">3/10</td>
</tr>
<tr class="even">
<td>2020</td>
<td align="center">4</td>
<td align="center">4/10</td>
<td align="center">high</td>
<td align="center">8000</td>
<td align="center">7/10</td>
<td style="text-align: center;">4</td>
<td style="text-align: center;">4/10</td>
<td style="text-align: center;">high</td>
<td style="text-align: center;">8000</td>
<td style="text-align: center;">7/10</td>
</tr>
<tr class="odd">
<td>Skype</td>
<td align="center">-</td>
<td align="center">-</td>
<td align="center">medium</td>
<td align="center">8000</td>
<td align="center">8/10</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">-</td>
<td style="text-align: center;">medium</td>
<td style="text-align: center;">8000</td>
<td style="text-align: center;">8/10</td>
</tr>
</tbody>
</table>
<p>The Min SNR is roughly the SNR where you cannot converse without repeating yourself. The numbers above are on channels without fading (AWGN channels like VHF radio). For fading channels the minimum SNR is a few dB higher. The Fading column shows how robust the mode is to HF Fading channels, higher is more robust.</p>
<p>The more advanced 700D and 2020 modes have a high latency due to the use of large Forward Error Correction (FEC) codes. They buffer many frames of speech, which combined with PC sound card buffering results in end-to-end latencies of 1-2 seconds. They may take a few seconds to sync at the start of an over, especially in fading channels.</p>
<h2 id="freedv-700d"><span class="header-section-number">6.1</span> FreeDV 700D</h2>
<h2 id="freedv-700d"><span class="header-section-number">7.1</span> FreeDV 700D</h2>
<p>In mid 2018 FreeDV 700D was released, with a new OFDM modem, powerful Forward Error Correction (FEC) and optional interleaving. It uses the same 700 bit/s speech codec at 700C. It operates at SNRs as low as -2dB, and has good HF channel performance. It is around 10dB better than FreeDV 1600 on fading channels, and is competitive with SSB at low SNRs. The FEC provides some protection from urban HF noise.</p>
<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>
<h2 id="freedv-700e"><span class="header-section-number">6.2</span> FreeDV 700E</h2>
<h2 id="freedv-700e"><span class="header-section-number">7.2</span> FreeDV 700E</h2>
<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 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>
<h2 id="freedv-2020"><span class="header-section-number">6.3</span> FreeDV 2020</h2>
<h2 id="freedv-2020"><span class="header-section-number">7.3</span> FreeDV 2020</h2>
<p>FreeDV 2020 was developed in 2019. It uses an experimental codec based on the LPCNet neural net (deep learning) synthesis engine developed by Jean-Marc Valin. It offers 8 kHz audio bandwidth in an RF bandwidth of just 1600 Hz. FreeDV 2020 employs the same OFDM modem and FEC as 700D.</p>
<p>The purpose of FreeDV 2020 is to test neural net speech coding over HF radio. It is highly experimental, and possibly the first use of neural net vocoders in a real world, over the air system.</p>
<p>FreeDV 2020 is designed for slow fading HF channels with a SNR of 10dB or better. It is not designed for fast fading or very low SNRs like 700D. It is designed to be a high quality alternative to SSB in channels where SSB is already an &quot;arm-chair&quot; copy. On an AWGN (non- fading channel), it will deliver reasonable speech quality down to 2dB SNR.</p>
<p>FreeDV 2020 is designed for slow fading HF channels with a SNR of 10dB or better. It is not designed for fast fading or very low SNRs like 700D. It is designed to be a high quality alternative to SSB in channels where SSB is already an “arm-chair” copy. On an AWGN (non- fading channel), it will deliver reasonable speech quality down to 2dB SNR.</p>
<p>FreeDV 2020 Tips:</p>
<ol style="list-style-type: decimal">
<li>It requires a modern (post 2010) Intel CPU with AVX support. If you don't have AVX the FreeDV 2020 mode button will be grayed out.</li>
<ol type="1">
<li>It requires a modern (post 2010) Intel CPU with AVX support. If you don’t have AVX the FreeDV 2020 mode button will be grayed out.</li>
<li>Some voices may sound very rough. In early testing about 90% of speakers tested work well.</li>
<li>Like 700D, you must tune within -/+ 60Hz for FreeDV 2020 to sync.</li>
<li>With significant fading, sync may take a few seconds.</li>
<li>There is a 2 second end-to-end latency. You are welcome to try tuning this (Tools - Options - FIFO size, also see Sound Card Debug section below).</li>
<li>The voice keyer file must be 16 kHz mono 16 bit sample format.</li>
</ol>
<h1 id="tools-menu"><span class="header-section-number">7</span> Tools Menu</h1>
<h2 id="tools---filter"><span class="header-section-number">7.1</span> Tools - Filter</h2>
<h1 id="tools-menu"><span class="header-section-number">8</span> Tools Menu</h1>
<h2 id="tools---filter"><span class="header-section-number">8.1</span> Tools - Filter</h2>
<p>This section describes features on Tools-Filter.</p>
<table>
<colgroup>
<col width="27%" />
<col width="73%" />
<col style="width: 26%" />
<col style="width: 73%" />
</colgroup>
<thead>
<tr class="header">
@ -309,12 +314,12 @@ FMA - Supports FMA extensions using YMM state</code></pre>
<li><a href="http://www.rowetel.com/?p=6778">Blog Post on Auto EQ Part 1</a></li>
<li><a href="http://www.rowetel.com/?p=6860">Blog Post on Auto EQ Part 2</a></li>
</ul>
<h2 id="tools---options"><span class="header-section-number">7.2</span> Tools - Options</h2>
<h3 id="freedv-700-cde-options"><span class="header-section-number">7.2.1</span> FreeDV 700 C/D/E Options</h3>
<h2 id="tools---options"><span class="header-section-number">8.2</span> Tools - Options</h2>
<h3 id="freedv-700-cde-options"><span class="header-section-number">8.2.1</span> FreeDV 700 C/D/E Options</h3>
<table>
<colgroup>
<col width="28%" />
<col width="71%" />
<col style="width: 28%" />
<col style="width: 71%" />
</colgroup>
<thead>
<tr class="header">
@ -341,35 +346,34 @@ FMA - Supports FMA extensions using YMM state</code></pre>
</tr>
</tbody>
</table>
<h3 id="ofdm-modem-phase-estimator-options-experimental"><span class="header-section-number">7.2.2</span> OFDM Modem Phase Estimator Options (Experimental)</h3>
<h3 id="ofdm-modem-phase-estimator-options-experimental"><span class="header-section-number">8.2.2</span> OFDM Modem Phase Estimator Options (Experimental)</h3>
<p>These options apply to the FreeDV 700D and 2020 modes that use the OFDM modem:</p>
<ol style="list-style-type: decimal">
<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>
<ol type="1">
<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 options.</p>
<h1 id="helping-improve-freedv"><span class="header-section-number">8</span> Helping Improve FreeDV</h1>
<h1 id="helping-improve-freedv"><span class="header-section-number">9</span> Helping Improve FreeDV</h1>
<p>If you have an interesting test case, for example:</p>
<ol style="list-style-type: decimal">
<ol type="1">
<li>FreeDV working poorly with a particular person or microphone.</li>
<li>Poor over the air performance on a fast fading channel.</li>
<li>Problems with sync on strong signals.</li>
<li>A comparison with SSB.</li>
</ol>
<p>Please send the developers an off air recording of the signal. FreeDV can record files from your radio using Tools-Record File from Radio. A recording of 30 to 60 seconds is most useful.</p>
<p>With a recording we can reproduce your exact problem. If we can reproduce it we can fix it. Recordings are much more useful than anecdotes or subjective reports like &quot;FreeDV doesn't work&quot;, &quot;SSB is better&quot;, or &quot;On 23 December it didn't work well on grid location XYZ&quot;. With subjective reports problems are impossible to reproduce, cannot be fixed, and you are unlikely to get the attention of the developers.</p>
<h1 id="multiple-panes-in-gui-window"><span class="header-section-number">9</span> Multiple Panes in GUI window</h1>
<p>With a recording we can reproduce your exact problem. If we can reproduce it we can fix it. Recordings are much more useful than anecdotes or subjective reports like “FreeDV doesn’t work”, “SSB is better”, or “On 23 December it didn’t work well on grid location XYZ”. With subjective reports problems are impossible to reproduce, cannot be fixed, and you are unlikely to get the attention of the developers.</p>
<h1 id="multiple-panes-in-gui-window"><span class="header-section-number">10</span> Multiple Panes in GUI window</h1>
<p>It is possible to have multiple panes opened within the GUI window for example, to observe both the Waterfall and Spectrum Tabs. New panes may be added above, below, left or right of existing panes.</p>
<p>A new visible pane is created by hovering the cursor over the required Tab, click and hold the left mouse button and drag the Tab to the required position and releasing the mouse button. If currently two panes are stacked vertically a third pane may be added either beside either pane or to the left/right of both panes. If the Tab is required adjacent to both panes then it must be dragged to the left/right of the junction of the existing Tabs.</p>
<p>As the Tab is dragged into position a faint blue/grey image will show the position to be occupied by the pane. Panes may be relocated back to the menu bar by a similar process.</p>
<p>Tabs can be resized as required by hovering the cursor over the border and clicking and holding the left mouse button and dragging to required size.</p>
<p>The layout is not saved when the program is exited and must be recreated next time the program is started</p>
<div class="figure">
<img src="contrib/multiple_panes.png" alt="Multiple Panes" />
<p class="caption">Multiple Panes</p>
</div>
<h1 id="advanceddeveloper-features"><span class="header-section-number">10</span> Advanced/Developer Features</h1>
<h2 id="stats-window"><span class="header-section-number">10.1</span> Stats Window</h2>
<figure>
<img src="contrib/multiple_panes.png" alt="Multiple Panes" /><figcaption>Multiple Panes</figcaption>
</figure>
<h1 id="advanceddeveloper-features"><span class="header-section-number">11</span> Advanced/Developer Features</h1>
<h2 id="stats-window"><span class="header-section-number">11.1</span> Stats Window</h2>
<p>Located on the lower left hand side of the main screen.</p>
<table>
<thead>
@ -410,30 +414,30 @@ FMA - Supports FMA extensions using YMM state</code></pre>
</tbody>
</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>
<h2 id="timing-delta-tab"><span class="header-section-number">10.2</span> Timing Delta Tab</h2>
<h2 id="timing-delta-tab"><span class="header-section-number">11.2</span> Timing Delta Tab</h2>
<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>
</ul>
<h2 id="udp-messages"><span class="header-section-number">10.3</span> UDP Messages</h2>
<p>When FreeDV syncs on a received signal for 5 seconds, it will send a &quot;rx sync&quot; UDP message to a port on your machine (localhost). An external program or script listening on this port can then take some action, for example send &quot;spotting&quot; information to a web server or send an email your phone.</p>
<p>Enable UDP messages on Tools-Options, and test using the &quot;Test&quot; button.</p>
<h2 id="udp-messages"><span class="header-section-number">11.3</span> UDP Messages</h2>
<p>When FreeDV syncs on a received signal for 5 seconds, it will send a “rx sync” UDP message to a port on your machine (localhost). An external program or script listening on this port can then take some action, for example send “spotting” information to a web server or send an email your phone.</p>
<p>Enable UDP messages on Tools-Options, and test using the “Test” button.</p>
<p>On Linux you can test reception of messages using netcat:</p>
<pre><code> $ nc -ul 3000</code></pre>
<p>A sample script to email you on FreeDV sync: <a href="src/send_email_on_sync.py">send_email_on_sync.py</a></p>
<p>Usage for Gmail:</p>
<pre><code>python send_email_on_sync.py --listen_port 3000 --smtp_server smtp.gmail.com \
--smtp_port 587 your@gmail.com your_pass</code></pre>
<h2 id="sound-card-debug"><span class="header-section-number">10.4</span> Sound Card Debug</h2>
<h2 id="sound-card-debug"><span class="header-section-number">11.4</span> Sound Card Debug</h2>
<p>These features were added for FreeDV 700D, to help diagnose sound card issues during development.</p>
<h3 id="tools---options-dialog"><span class="header-section-number">10.4.1</span> Tools - Options dialog:</h3>
<h3 id="tools---options-dialog"><span class="header-section-number">11.4.1</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>
<p>Check these counters by pressing Start, then Reset them and observe the counters for 30 seconds.</p>
<p>If the PortAudio counters are incrementing on receive try:</p>
<ol style="list-style-type: decimal">
<ol type="1">
<li><p>Adjusting framesPerBuffer; try 0, 128, 256, 512, 1024.</p></li>
<li><p>Shut down other applications that might be using audio, such as Skype or your web browser.</p></li>
<li><p>A different sound card rate such as 44.1kHz instead of 48kHz.</p></li>
@ -441,19 +445,19 @@ FMA - Supports FMA extensions using YMM state</code></pre>
<p>If the outempty1 counter is incrementing on transmit try increasing the FifoSize.</p>
<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>
<h2 id="test-frame-histogram"><span class="header-section-number">10.5</span> Test Frame Histogram</h2>
<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 “outfifo1” being incremented on the “Fifo” line during tx. Try increasing the FifoSize.</p>
<h2 id="test-frame-histogram"><span class="header-section-number">11.5</span> Test Frame Histogram</h2>
<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>Displays BER of each carrier when in “test frame” 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>
<p>Suggested usage:</p>
<ol style="list-style-type: decimal">
<ol type="1">
<li><p>Transmit FreeDV in test frame mode. Use a 2nd rx (or get a friend) to monitor your rx signal with FreeDV in test frame mode.</p></li>
<li><p>Adjust your rx SNR to get a BER of a few % (e.g. reduce tx power, use a short antenna for the rx, point your beam away, adjust rx RF gain).</p></li>
<li><p>Adjust your rx SNR to get a BER of a few % (e.g. reduce tx power, use a short antenna for the rx, point your beam away, adjust rx RF gain).</p></li>
<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>
<h2 id="full-duplex-testing-with-loopback"><span class="header-section-number">10.6</span> Full Duplex Testing with loopback</h2>
<h2 id="full-duplex-testing-with-loopback"><span class="header-section-number">11.6</span> Full Duplex Testing with loopback</h2>
<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>
@ -463,20 +467,20 @@ FMA - Supports FMA extensions using YMM state</code></pre>
In Tools - Audio Config - Receive Tab - From Radio select -&gt; Loopback: Loopback PCM (hw:1,0)
- Transmit Tab - To Radio select -&gt; Loopback: Loopback PCM (hw:1,1)</code></pre>
<h1 id="tips"><span class="header-section-number">11</span> Tips</h1>
<ol style="list-style-type: decimal">
<h1 id="tips"><span class="header-section-number">12</span> Tips</h1>
<ol type="1">
<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>
<h1 id="converting-this-document-to-pdf"><span class="header-section-number">12</span> Converting this document to PDF</h1>
<h1 id="converting-this-document-to-pdf"><span class="header-section-number">13</span> Converting this document to PDF</h1>
<p>For the Linux inclined:</p>
<pre><code>$ pandoc USER_MANUAL.md -o USER_MANUAL.pdf &quot;-fmarkdown-implicit_figures -o&quot; \
--from=markdown -V geometry:margin=.4in --toc --highlight-style=espresso</code></pre>
<h1 id="glossary"><span class="header-section-number">13</span> Glossary</h1>
<table style="width:100%;">
<h1 id="glossary"><span class="header-section-number">14</span> Glossary</h1>
<table>
<colgroup>
<col width="7%" />
<col width="92%" />
<col style="width: 7%" />
<col style="width: 93%" />
</colgroup>
<thead>
<tr class="header">
@ -499,50 +503,50 @@ FMA - Supports FMA extensions using YMM state</code></pre>
</tr>
</tbody>
</table>
<h1 id="release-notes"><span class="header-section-number">14</span> Release Notes</h1>
<h2 id="v1.5.2-january-2021"><span class="header-section-number">14.1</span> V1.5.2 January 2021</h2>
<ol style="list-style-type: decimal">
<h1 id="release-notes"><span class="header-section-number">15</span> Release Notes</h1>
<h2 id="v1.5.2-january-2021"><span class="header-section-number">15.1</span> V1.5.2 January 2021</h2>
<ol type="1">
<li>Updates storage for sound card configuration to use device names instead of IDs.</li>
<li>Detects changes to computer sound card configuration and notifies user when devices go away.</li>
</ol>
<h2 id="v1.5.1-january-2021"><span class="header-section-number">14.2</span> V1.5.1 January 2021</h2>
<ol style="list-style-type: decimal">
<h2 id="v1.5.1-january-2021"><span class="header-section-number">15.2</span> V1.5.1 January 2021</h2>
<ol type="1">
<li>Experimental support for reporting to <a href="https://pskreporter.info">PSK Reporter</a> added.</li>
<li>Bug fixes with audio configuration to allow mono devices to be used along with stereo ones.</li>
<li>Tweaks to user interface and record/playback functionality to improve usability.</li>
<li>Bug fixes and tweaks to improve voice keyer support.</li>
</ol>
<h2 id="v1.5.0-december-2020"><span class="header-section-number">14.3</span> V1.5.0 December 2020</h2>
<ol style="list-style-type: decimal">
<h2 id="v1.5.0-december-2020"><span class="header-section-number">15.3</span> V1.5.0 December 2020</h2>
<ol type="1">
<li>FreeDV 700E, better performance than 700D on fast fading channels</li>
<li>FreeDV 700D/700E clipper to increase average transmit power by 6dB</li>
</ol>
<h2 id="v1.4.3-august-2020"><span class="header-section-number">14.4</span> V1.4.3 August 2020</h2>
<ol style="list-style-type: decimal">
<h2 id="v1.4.3-august-2020"><span class="header-section-number">15.4</span> V1.4.3 August 2020</h2>
<ol type="1">
<li>Maintenance Release (no major new features)</li>
<li>Changes to support wxWidgets 3.1 (but Windows versions built against wxWidgets 3.0)</li>
<li>Under the hood - OFDM modem has been refactored, shouldn't affect freedv-gui operation</li>
<li>Under the hood - OFDM modem has been refactored, shouldn’t affect freedv-gui operation</li>
</ol>
<h2 id="v1.4.2-july-2020"><span class="header-section-number">14.5</span> V1.4.2 July 2020</h2>
<ol style="list-style-type: decimal">
<h2 id="v1.4.2-july-2020"><span class="header-section-number">15.5</span> V1.4.2 July 2020</h2>
<ol type="1">
<li>Maintenance Release (no major new features)</li>
<li>Improved squelch/audio pass through on 700D/2020/2400B</li>
<li>Under the hood - Codec2 library has been refactored, shouldn't affect freedv-gui operation</li>
<li>Under the hood - Codec2 library has been refactored, shouldn’t affect freedv-gui operation</li>
<li>Removed Project Horus support (now being maintained outside of Codec2/FreeDV)</li>
</ol>
<h2 id="v1.4-june-october-2019"><span class="header-section-number">14.6</span> V1.4 June-October 2019</h2>
<ol style="list-style-type: decimal">
<h2 id="v1.4-june-october-2019"><span class="header-section-number">15.6</span> V1.4 June-October 2019</h2>
<ol type="1">
<li>FreeDV 2020, Project Horus Binary Modes.</li>
<li><a href="http://www.rowetel.com/?p=6824">Improved OFDM Modem Acquisition</a>, this will improve sync time on FreeDV 700D and 2020 on HF fading channels, and can also handle +/- 60 Hz frequency offsets when tuning.</li>
<li>Fixed FreeDV 700C frequency offset bug fix, was losing sync at certain frequency offsets.</li>
<li>Wide bandwidth phase estimation and DPSK for OFDM modes (700D/2020) for fast fading/QO-100 channels (Tools-Options)</li>
<li>Better speech quality on FreeDV 700C/700D with Auto equaliser (Tools-Filter)</li>
</ol>
<h2 id="v1.3-may-2018"><span class="header-section-number">14.7</span> V1.3 May 2018</h2>
<h2 id="v1.3-may-2018"><span class="header-section-number">15.7</span> V1.3 May 2018</h2>
<ul>
<li>FreeDV 700D</li>
</ul>
<h1 id="references"><span class="header-section-number">15</span> References</h1>
<h1 id="references"><span class="header-section-number">16</span> References</h1>
<ul>
<li><a href="http://freedv.org">FreeDV Web site</a></li>
<li><a href="https://github.com/drowe67/codec2/blob/master/README_freedv.md">FreeDV Technology Overview</a></li>

BIN
USER_MANUAL.pdf
View File

Binary file not shown.