+
FreeDV GUI (or just FreeDV) is a GUI program for Linux, Windows, and macOS for running FreeDV on a desktop PC or laptop.
-This is a live document. Notes on new FreeDV features are being added as they are developed.
-FreeDV GUI (or just FreeDV) is a GUI program for Linux, Windows, and +macOS for running FreeDV on a desktop PC or laptop.
+This is a live document. Notes on new FreeDV features are being added +as they are developed.
+This section contains instructions to help you get started.
-Upon starting FreeDV for the first time, the Easy Setup dialog will appear. This is a streamlined setup process for FreeDV optimized for hardware commonly used by amateur radio operators and is divided into three sections:
+Upon starting FreeDV for the first time, the Easy Setup dialog will +appear. This is a streamlined setup process for FreeDV optimized for +hardware commonly used by amateur radio operators and is divided into +three sections:
These sections are shown below:
+
Note that you can always return to this dialog by going to Tools - Easy Setup.
-To configure your sound card(s) using Easy Setup, simply select the sound device associated with your radio and the microphone and speaker devices you wish to use to hear decoded audio as well as to transmit audio. If you’re setting up a receive-only station, you can choose “None” for the transmit audio device.
-Additionally, if you are using a Flex 6000 series radio on the Windows platform, FreeDV will automatically select the DAX TX sound device. It is necessary only to select the correct “slice” for the radio sound device and the two devices to use for analog receive and transmit (e.g. your computer’s built in microphone and speaker devices).
-Note that some configurations (for example, SDR setups involving multiple radio sound devices) may not be able to be configured with Easy Setup. For those, you can choose the “Advanced” button and proceed to “Advanced Setup” below.
-Note that you can always return to this dialog by going to Tools +- Easy Setup.
+To configure your sound card(s) using Easy Setup, simply select the +sound device associated with your radio and the microphone and speaker +devices you wish to use to hear decoded audio as well as to transmit +audio. If you’re setting up a receive-only station, you can choose +“None” for the transmit audio device.
+Additionally, if you are using a Flex 6000 series radio on the +Windows platform, FreeDV will automatically select the DAX TX sound +device. It is necessary only to select the correct “slice” for the radio +sound device and the two devices to use for analog receive and transmit +(e.g. your computer’s built in microphone and speaker devices).
+Note that some configurations (for example, SDR setups involving +multiple radio sound devices) may not be able to be configured with Easy +Setup. For those, you can choose the “Advanced” button and proceed to +“Advanced Setup” below.
+Easy Setup supports three methods of radio control:
Simply select the option that matches your radio setup and the required fields will appear. For Hamlib, these are typically the type of radio you’re using as well as the serial port it’s connected to (or TCP/IP hostname:port). Serial port PTT control requires the serial port your radio is using as well as whether your radio’s PTT is triggered via the RTS or DTR pin (and the required polarity for either).
-If required, the “Advanced” button in this section will allow you to configure PTT input (e.g. for a footswitch) and additional VOX related options. The “Test” button will emit a constant carrier on the selected radio sound device as well as enable PTT to allow you to adjust your radio sound levels (see “Sound Card Levels” below).
-While not required, it is recommended to enable reporting so that others can see who is currently receiving them. This also allows the FreeDV application to control the radio’s frequency and mode. Both sides of a contact must have this enabled in order for contacts to be reported. To configure reporting, simply enable the feature here and enter your callsign and current grid square/locator.
-For more information about the reporting feature, see the “FreeDV Reporting” section below.
-For this setup, you just need the basic sound hardware in your computer, for example a microphone/speaker on your computer.
+Simply select the option that matches your radio setup and the +required fields will appear. For Hamlib, these are typically the type of +radio you’re using as well as the serial port it’s connected to (or +TCP/IP hostname:port). Serial port PTT control requires the serial port +your radio is using as well as whether your radio’s PTT is triggered via +the RTS or DTR pin (and the required polarity for either).
+If required, the “Advanced” button in this section will allow you to +configure PTT input (e.g. for a footswitch) and additional VOX related +options. The “Test” button will emit a constant carrier on the selected +radio sound device as well as enable PTT to allow you to adjust your +radio sound levels (see “Sound Card Levels” below).
+While not required, it is recommended to enable reporting so that +others can see who is currently receiving them. This also allows the +FreeDV application to control the radio’s frequency and mode. Both sides +of a contact must have this enabled in order for contacts to be +reported. To configure reporting, simply enable the feature here and +enter your callsign and current grid square/locator.
+For more information about the reporting feature, see the “FreeDV +Reporting” section below.
+For this setup, you just need the basic sound hardware in your +computer, for example a microphone/speaker on your computer.
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.
-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 From Radio To Computer device, with your computer’s sound card as the From Computer To Speaker/Headphone device.
-If you don’t have anyone to transmit FreeDV signals to you, try the test wave files in the next section.
-For TX/RX operation you need to configure two sound cards, by setting up Tools - Audio Config Transmit and Receive Tabs.
-When receiving, FreeDV off-air signals from your radio are decoded by your computer and sent to your speaker/headphones, where you can listen to them.
-When transmitting, FreeDV takes your voice from the microphone, and encodes it to a FreeDV signal in you computer which is sent to your radio for transmission over the air.
+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.
+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 From Radio To Computer device, with +your computer’s sound card as the From Computer To +Speaker/Headphone device.
+If you don’t have anyone to transmit FreeDV signals to you, try the +test wave files in the next section.
+For TX/RX operation you need to configure two sound cards, by setting +up Tools - Audio Config Transmit and Receive Tabs.
+When receiving, FreeDV off-air signals from your +radio are decoded by your computer and sent to your +speaker/headphones, where you can listen to them.
+When transmitting, FreeDV takes your voice from the +microphone, and encodes it to a FreeDV signal in you computer which is +sent to your radio for transmission over the air.
| Receive Tab | Input To Computer From Radio | -The off air FreeDV signal from your radio rig interface to your computer | +The off air FreeDV signal from your radio rig +interface to your computer |
| Receive Tab | @@ -84,37 +148,94 @@|||
| Transmit Tab | Output From Computer To Radio | -The FreeDV signal from your computer sent to your rig interface for TX | +The FreeDV signal from your computer sent to your +rig interface for TX |
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 Start, 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.
-Hitting Refresh 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.
-Another solution is to re-start FreeDV and check Tools/Audio Config again after changing any audio hardware.
-The Tools->CAT and PTT Config dialog supports three different ways to control PTT on your radio:
+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 Start, 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.
+Hitting Refresh 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.
+Another solution is to re-start FreeDV and check Tools/Audio Config +again after changing any audio hardware.
+The Tools->CAT and PTT Config dialog supports three different ways +to control PTT on your radio:
You may also optionally configure a second serial port for PTT input. This can be useful for interfacing devices like foot switches to FreeDV. If configured, FreeDV will switch into transmit mode (including sending the needed Hamlib or serial commands to initiate PTT) when it detects the configured signal.
-Once you have configured PTT, try the Test button.
-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 mismatch 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.
-Also see Common Problems section of this manual.
-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.
-When Test is pressed, the “Serial Params” field is populated and displayed. This will help track down any mismatches between Hamlib and your radio.
-If you are really stuck, download Hamlib and test your radio’s PTT using the command line rigctl program.
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).
-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.
-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 recognize the device on the new COM Port until it has been unplugged/plugged.
-In the installation are audio files containing off-air FreeDV modem signals. There is one file per FreeDV mode and are in the following locations depending on platform:
+You may also optionally configure a second serial port for PTT input. +This can be useful for interfacing devices like foot switches to FreeDV. +If configured, FreeDV will switch into transmit mode (including sending +the needed Hamlib or serial commands to initiate PTT) when it detects +the configured signal.
+Once you have configured PTT, try the Test +button.
+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 mismatch 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.
+Also see Common Problems section of +this manual.
+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.
+When Test is pressed, the “Serial Params” field is +populated and displayed. This will help track down any mismatches +between Hamlib and your radio.
+If you are really stuck, download Hamlib and test your radio’s PTT
+using the command line rigctl program.
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).
+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.
+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 +recognize the device on the new COM Port until it has been +unplugged/plugged.
+In the installation are audio files containing off-air FreeDV modem +signals. There is one file per FreeDV mode and are in the following +locations depending on platform:
| Platform | @@ -136,31 +257,77 @@
|---|
To play these files, first select a FreeDV mode and press Start. Then choose a file using “Tools - Start/Stop Play File From Radio”. You should then hear decoded FreeDV speech.
-These files will give you a feel for what FreeDV signals sound like, and for the basic operation of the FreeDV software.
-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 0 dB attenuates the transmit signal.
-When FreeDV is running, you can observe the sound card signals in the main window tabs (From Radio, From Mic, To Speaker).
+To play these files, first select a FreeDV mode and press Start. Then +choose a file using “Tools - Start/Stop Play File From Radio”. You +should then hear decoded FreeDV speech.
+These files will give you a feel for what FreeDV signals sound like, +and for the basic operation of the FreeDV software.
+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 0 dB attenuates the transmit signal.
+When FreeDV is running, you can observe the sound card signals in the +main window tabs (From Radio, From Mic, To Speaker).
On receive, FreeDV is not very sensitive to the From Radio level, adjust so it is mid-range and not clipping. FreeDV uses phase shift keying (PSK) so is not sensitive to amplitude.
The transmit level from your computer to your radio is important. On transmit, adjust your level so that the ALC is just being nudged. More is not better 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.
FreeDV 700D and 700E can drive your transmitter at an average power of 40% of its 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.
Adjust the microphone audio so the peaks are not clipping, and the average is about half the maximum.
On receive, FreeDV is not very sensitive to the From +Radio level, adjust so it is mid-range and not clipping. FreeDV +uses phase shift keying (PSK) so is not sensitive to amplitude.
The transmit level from your computer to your radio is important. +On transmit, adjust your level so that the ALC is just +being nudged. More is not better 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.
FreeDV 700D and 700E can drive your transmitter at an average +power of 40% of its 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.
Adjust the microphone audio so the peaks are not clipping, and +the average is about half the maximum.
FreeDV likes a clean path through your radio. Turn all audio processing OFF on transmit and receive:
+FreeDV likes a clean path through your radio. Turn all audio +processing OFF on transmit and receive:
On receive, DSP noise reduction should be off.
On transmit, speech compression should be off.
Keep the receive audio path as “flat” as possible, no special filters.
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.
Keep the receive audio path as “flat” as possible, no special +filters.
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.
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.
-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”).
-For most FreeDV use, your radio’s receive and transmit filters should be set to the widest possible (typically around 3 kHz). This allows easy switching between analog mode as well as the various FreeDV modes. There has not been any testing done to definitively confirm whether narrower bandwidths help with reception of FreeDV. Additionally, FreeDV already performs its own transmit filtering, so using additional narrow filtering on the radio will likely have little benefit (again, untested).
-For reference, the channel widths of the currently supported modes are below:
+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.
+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”).
+For most FreeDV use, your radio’s receive and transmit filters should +be set to the widest possible (typically around 3 kHz). This allows easy +switching between analog mode as well as the various FreeDV modes. There +has not been any testing done to definitively confirm whether narrower +bandwidths help with reception of FreeDV. Additionally, FreeDV already +performs its own transmit filtering, so using additional narrow +filtering on the radio will likely have little benefit (again, +untested).
+For reference, the channel widths of the currently supported modes +are below:
The Voice Keyer Button on the front page puts FreeDV and your radio into transmit, reads a wave file of your voice to call CQ, and then switches to receive to see if anyone is replying. If you press the space bar or click the PTT button, the voice keyer stops. If a signal with a valid sync is received for a few seconds the voice keyer also stops.
-The Audio tab inside Tools-Options can be used to select the wave file, set the RX delay, and number of times the TX/RX cycle repeats.
-Additional options are also available if you right-click on the Voice Keyer button:
+The Voice Keyer Button on the front page puts FreeDV and your radio +into transmit, reads a wave file of your voice to call CQ, and then +switches to receive to see if anyone is replying. If you press the space +bar or click the PTT button, the voice keyer stops. If a signal with a +valid sync is received for a few seconds the voice keyer also stops.
+The Audio tab inside Tools-Options can be used to select the wave +file, set the RX delay, and number of times the TX/RX cycle repeats.
+Additional options are also available if you right-click on the Voice +Keyer button:
FreeDV has the ability to monitor transmit audio. This can be useful for adjusting microphone filters when your radio is plugged into a dummy load. To enable this, right-click on the PTT button and choose “Monitor transmitted audio”. A checkmark will appear next to this menu option when enabled.
-To quickly record incoming signals from the radio, a ‘Record’ button is provided in the main window. Clicking this button will create a file beginning with the name “FreeDV_FromRadio” and containing the current date and time. Clicking ‘Record’ again will stop recording.
-The Audio tab inside Tools-Options allows control of where these recordings are saved. By default, this is inside the current user’s Documents folder.
-By default, FreeDV uses the following locations to store configuration:
+FreeDV has the ability to monitor transmit audio. This can be useful +for adjusting microphone filters when your radio is plugged into a dummy +load. To enable this, right-click on the PTT button and choose “Monitor +transmitted audio”. A checkmark will appear next to this menu option +when enabled.
+To quickly record incoming signals from the radio, a ‘Record’ button +is provided in the main window. Clicking this button will create a file +beginning with the name “FreeDV_FromRadio” and containing the current +date and time. Clicking ‘Record’ again will stop recording.
+The Audio tab inside Tools-Options allows control of where these +recordings are saved. By default, this is inside the current user’s +Documents folder.
+By default, FreeDV uses the following locations to store +configuration:
If you’d like to store the configuration in another location (or store multiple configurations), FreeDV accepts the -f (or –config) command line arguments to provide an alternate location. An absolute path is recommended here; however, if only a relative path is provided, it will be relative to the following locations:
+If you’d like to store the configuration in another location (or +store multiple configurations), FreeDV accepts the -f (or –config) +command line arguments to provide an alternate location. An absolute +path is recommended here; however, if only a relative path is provided, +it will be relative to the following locations:
On Windows, you can create shortcuts to FreeDV with different file names for the “-f” command line option as described above. To create a shortcut, right-click on the Desktop or in File Explorer and choose New->Shortcut. Click on Browse and navigate to one of the following paths:
+On Windows, you can create shortcuts to FreeDV with different file +names for the “-f” command line option as described above. To create a +shortcut, right-click on the Desktop or in File Explorer and choose +New->Shortcut. Click on Browse and navigate to one of the following +paths:
Click Next and give the shortcut a unique description (e.g. “FreeDV IC-7300”). Then push Finish to create the shortcut.
-Once the shortcut has been created, right-click it and choose Properties. Find the Shortcut tab in the resulting dialog box and add “-f” followed by the desired filename to the end of the text in the Target field. Do not add any other quote marks.
-For example, to use a file called IC7300.conf stored in the Hamradio directory on the C drive the Target field should appear as follows:
-“C:\Program Files\FreeDV [version]\bin\freedv.exe” -f C:\Hamradio\IC7300.conf
-FreeDV has the ability to send FreeDV signal reports to various online spotting services by enabling the option in Tools-Options (in the Reporting tab) and specifying your callsign and Maidenhead grid square. When enabled, this causes FreeDV to disable the free form Txt Msg field and only transmit the Callsign field. As this uses a different encoding format from the free-form text field, both sides of the contact must have this enabled for the contact to be reported.
-FreeDV validates the received information before submitting a position report. 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, if the reporting function is disabled, all received text will display in the main window even if it has errors.
-The following services are currently supported and can be individually enabled or disabled along with the reporting feature as a whole:
+Click Next and give the shortcut a unique description (e.g. “FreeDV +IC-7300”). Then push Finish to create the shortcut.
+Once the shortcut has been created, right-click it and choose +Properties. Find the Shortcut tab in the resulting dialog box and add +“-f” followed by the desired filename to the end of the text in the +Target field. Do not add any other quote marks.
+For example, to use a file called IC7300.conf stored in the Hamradio +directory on the C drive the Target field should appear as follows:
+“C:\Program Files\FreeDV [version]\bin\freedv.exe” -f +C:\Hamradio\IC7300.conf
+FreeDV has the ability to send FreeDV signal reports to various +online spotting services by enabling the option in Tools-Options (in the +Reporting tab) and specifying your callsign and Maidenhead grid square. +When enabled, this causes FreeDV to disable the free form Txt +Msg field and only transmit the Callsign +field. As this uses a different encoding format from the free-form text +field, both sides of the contact must have this enabled for the contact +to be reported.
+FreeDV validates the received information before submitting a +position report. 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, if the reporting function is +disabled, all received text will display in the main window even if it +has errors.
+The following services are currently supported and can be +individually enabled or disabled along with the reporting feature as a +whole:
The frequency that FreeDV reports is set by changing the “Report Frequency” drop down box in the main window. This is either in kilohertz (kHz) or megahertz (MHz) (configurable by going to Tools->Options->Rig Control and checking or unchecking “Frequency entry in kHz”) and will turn red if the entered value is invalid. If Hamlib support is also enabled, this frequency will automatically remain in sync with the current VFO on the radio (i.e. if the frequency is changed in the application, the radio will also change its frequency). Double-clicking on users in the Tools->FreeDV Reporter window will also cause this frequency to change to match the other user.
-Note: in some setups (such as when using ALE), it is not preferred to have the reporting frequency automatically be in sync with the radio. For example, in the case of ALE, the radio’s frequency changes multiple times per second while waiting for a contact, which is faster than FreeDV can pull the latest from the radio (every five seconds). This can be disabled by enabling “Manual Frequency Reporting” in Tools->Options.
-FreeDV will also show the callsigns of previously received signals. To view those, click on the arrow next to the last received callsign at the bottom of the window. These are in descending order by time of receipt (i.e. the most recently received callsign will appear at the top of the list).
-FreeDV can simultaneously decode the following modes when selected prior to pushing “Start”:
+The frequency that FreeDV reports is set by changing the “Report +Frequency” drop down box in the main window. This is either in kilohertz +(kHz) or megahertz (MHz) (configurable by going to +Tools->Options->Rig Control and checking or unchecking “Frequency +entry in kHz”) and will turn red if the entered value is invalid. If +Hamlib support is also enabled, this frequency will automatically remain +in sync with the current VFO on the radio (i.e. if the frequency is +changed in the application, the radio will also change its frequency). +Double-clicking on users in the Tools->FreeDV Reporter window will +also cause this frequency to change to match the other user.
+Note: in some setups (such as when using ALE), it is not +preferred to have the reporting frequency automatically be in sync with +the radio. For example, in the case of ALE, the radio’s frequency +changes multiple times per second while waiting for a contact, which is +faster than FreeDV can pull the latest from the radio (every five +seconds). This can be disabled by enabling “Manual Frequency Reporting” +in Tools->Options.
+FreeDV will also show the callsigns of previously received signals. +To view those, click on the arrow next to the last received callsign at +the bottom of the window. These are in descending order by time of +receipt (i.e. the most recently received callsign will appear at the top +of the list).
+FreeDV can simultaneously decode the following modes when selected +prior to pushing “Start”:
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->Options->Modem and checking the “Simultaneously Decode All HF Modes” option. Note that this may consume significant additional CPU resources, which can cause decode problems.
-By default, FreeDV will use as many threads/cores in parallel as required to decode all supported HF modes. On some slower systems, it may be necessary to enable the “Use single thread for multiple RX operation” option as well. This results in FreeDV decoding each mode in series and additionally short circuits the list of modes to be checked when in sync.
-Additionally, the squelch setting with simultaneous decode enabled is relative to the mode that supports the weakest signals (currently 700D). The squelch for other modes will be set to a value higher than the slider (which is calculated by adding the difference between the “Min SNR” of 700D and the mode in question; see “FreeDV Modes” below). For example, the squelch for 700E when the squelch slider is set to -2.0 becomes 1.0dB. This is designed to reduce undesired pops and clicks due to false decodes.
-The following table is a guide to the different modes, using analog SSB and Skype as anchors for a rough guide to audio quality:
+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->Options->Modem and checking the +“Simultaneously Decode All HF Modes” option. Note that this may consume +significant additional CPU resources, which can cause decode +problems.
+By default, FreeDV will use as many threads/cores in parallel as +required to decode all supported HF modes. On some slower systems, it +may be necessary to enable the “Use single thread for multiple RX +operation” option as well. This results in FreeDV decoding each mode in +series and additionally short circuits the list of modes to be checked +when in sync.
+Additionally, the squelch setting with simultaneous decode enabled is +relative to the mode that supports the weakest signals (currently 700D). +The squelch for other modes will be set to a value higher than the +slider (which is calculated by adding the difference between the “Min +SNR” of 700D and the mode in question; see “FreeDV Modes” below). For +example, the squelch for 700E when the squelch slider is set to -2.0 +becomes 1.0dB. This is designed to reduce undesired pops and clicks due +to false decodes.
+The following table is a guide to the different modes, using analog +SSB and Skype as anchors for a rough guide to audio quality:
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.
-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.
-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.
-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.
-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 optimized 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.
-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.
+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.
+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.
+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.
+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.
+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 optimized 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.
+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.
Clipping can be enabled via Tools-Options.
-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.
-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.
-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.
-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.
+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.
+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.
+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.
+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.
FreeDV 2020 Tips:
Experimental mode developed in February 2022. The goal of this mode is to improve the performance of FreeDV 2020 over HF channels.
-Here are the three main innovations, and the theoretical improvements:
+Experimental mode developed in February 2022. The goal of this mode +is to improve the performance of FreeDV 2020 over HF channels.
+Here are the three main innovations, and the theoretical +improvements:
This modes is under development and may change at any time. If you experience comparability issues with another operator - check your Git Hash values on the Help-about menu to ensure you are running the same versions of LPCNet and codec2.
-It is recommended that multi-RX be disabled when using 2020B. This mode is not supported by multi-RX, you will need to manually coordinate the mode with other stations.
-This modes is under development and may change at any time. If you +experience comparability issues with another operator - check your Git +Hash values on the Help-about menu to ensure you are running the same +versions of LPCNet and codec2.
+It is recommended that multi-RX be disabled when using 2020B. This +mode is not supported by multi-RX, you will need to manually coordinate +the mode with other stations.
+This section describes features on Tools-Filter.
| Noise Suppression | -Enable noise suppression, de-reverberation, AGC of mic signal using the Speex pre-processor | +Enable noise suppression, de-reverberation, AGC of mic signal using +the Speex pre-processor |
| 700C/700D Auto EQ | -Automatic equalization for FreeDV 700C and FreeDV 700D Codec input audio | +Automatic equalization for FreeDV 700C and FreeDV 700D Codec input +audio |
Auto EQ (Automatic Equalization) adjusts the input speech spectrum to best fit the speech codec. It can remove annoying bass artifacts and make the codec speech easier to understand.
-Bass/Mid/Treble (for both microphone and speaker) can also be adjusted here, either with the arrow keys or your mouse. A graph displaying the frequency response of the signal based on your current settings will display in this window as well.
+Auto EQ (Automatic Equalization) adjusts the input speech spectrum to +best fit the speech codec. It can remove annoying bass artifacts and +make the codec speech easier to understand.
+Bass/Mid/Treble (for both microphone and speaker) can also be +adjusted here, either with the arrow keys or your mouse. A graph +displaying the frequency response of the signal based on your current +settings will display in this window as well.
| Clipping | -Increases the average power. Ensure your transmitter can handle high RMS powers before using! | +Increases the average power. Ensure your transmitter can handle high +RMS powers before using! |
| 700C Diversity Combine | -Combining of two sets of 700C carriers for better fading channel performance | +Combining of two sets of 700C carriers for better fading channel +performance |
| TX Band Pass Filter | @@ -416,7 +768,8 @@
If you have an interesting test case, for example:
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.
-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.
-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.
-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.
-As the Tab is dragged into position a faint blue/gray image will show the position to be occupied by the pane. Panes may be relocated back to the menu bar by a similar process.
-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.
-By default, the tab layout is not saved. However, by enabling experimental features (see “Advanced/Developer Features”), experimental support for saving and restoring the tab layout will be enabled. This has not been well tested and may have hidden bugs or other issues.
+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.
+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.
+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.
+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.
+As the Tab is dragged into position a faint blue/gray image will show +the position to be occupied by the pane. Panes may be relocated back to +the menu bar by a similar process.
+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.
+By default, the tab layout is not saved. However, by enabling +experimental features (see “Advanced/Developer Features”), experimental +support for saving and restoring the tab layout will be enabled. This +has not been well tested and may have hidden bugs or other issues.
+
Located on the lower left hand side of the main screen.
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.
-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.
+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.
+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.
These features were added for FreeDV 700D, to help diagnose sound card issues during development.
-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.
-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.
-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.
-Check these counters by pressing Start, then Reset them and observe the counters for 30 seconds.
+These features were added for FreeDV 700D, to help diagnose sound +card issues during development.
+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.
+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.
+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.
+Check these counters by pressing Start, then Reset them and observe +the counters for 30 seconds.
If the PortAudio counters are incrementing on receive try:
Adjusting framesPerBuffer; try 0, 128, 256, 512, 1024.
Shut down other applications that might be using audio, such as Skype or your web browser.
A different sound card rate such as 44.1kHz instead of 48kHz.
Shut down other applications that might be using audio, such as +Skype or your web browser.
A different sound card rate such as 44.1kHz instead of +48kHz.
If the outempty1 counter is incrementing on transmit try increasing the FifoSize.
-The txThreadPriority checkbox reduces the priority of the main txRX thread in FreeDV which may help the sound driver thread process samples.
-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.
-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.
-This feature was developed for testing FreeDV 700C. Select the Test Frame Histogram tab on Front Page
-Displays BER of each carrier when in “test frame” mode. As each QPSK carrier has 2 bits there are 2*Nc histogram points.
-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.
+If the outempty1 counter is incrementing on transmit try increasing +the FifoSize.
+The txThreadPriority checkbox reduces the priority of the main txRX +thread in FreeDV which may help the sound driver thread process +samples.
+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.
+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.
+This feature was developed for testing FreeDV 700C. Select the Test +Frame Histogram tab on Front Page
+Displays BER of each carrier when in “test frame” mode. As each QPSK +carrier has 2 bits there are 2*Nc histogram points.
+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.
Suggested usage:
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.
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).
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.
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.
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.
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).
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.
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.
Tools - Options - Half Duplex check box
-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.
-TX and RX signals can be looped back via an analog connection between the sound cards.
+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.
+TX and RX signals can be looped back via an analog connection between +the sound cards.
On Linux, using the ALSA loopback module:
$ sudo modprobe snd-aloop
$ ./freedv
In Tools - Audio Config - Receive Tab - From Radio select -> Loopback: Loopback PCM (hw:1,0)
- Transmit Tab - To Radio select -> Loopback: Loopback PCM (hw:1,1)Occasionally there are some features that may be unstable or otherwise not ready to officially be released. To experiment with these features, you can go to Tools->Options->Debugging and enable “Enable Experimental Features”. Note that if you have problems after enabling this setting, it is recommended to disable it again to verify that an experimental feature is not causing trouble. (Additionally, if you’re able to confirm that an experimental feature is causing problems, please file a bug report!)
-Occasionally there are some features that may be unstable or +otherwise not ready to officially be released. To experiment with these +features, you can go to Tools->Options->Debugging and enable +“Enable Experimental Features”. Note that if you have problems after +enabling this setting, it is recommended to disable it again to verify +that an experimental feature is not causing trouble. (Additionally, if +you’re able to confirm that an experimental feature is causing problems, +please file a bug report!)
+By default, FreeDV attempts to set the radio’s mode to DIGU/USB-D (or LSB equivalent for 40 meters and below). Some radios do not support data modes and only have USB and LSB. For these, you can go to Tools->Options->Rig Control and check the “Use USB/LSB instead of DIGU/DIGL” option. This will cause FreeDV to use the standard USB and LSB modes for rig control instead.
-Note that for best results, your radio should have all processing disabled if you’re using the standard USB/LSB modes. This disabling of processing typically takes place when using data mode.
-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).
-By default, FreeDV attempts to set the radio’s mode to DIGU/USB-D (or +LSB equivalent for 40 meters and below). Some radios do not support data +modes and only have USB and LSB. For these, you can go to +Tools->Options->Rig Control and check the “Use USB/LSB instead of +DIGU/DIGL” option. This will cause FreeDV to use the standard USB and +LSB modes for rig control instead.
+Note that for best results, your radio should have all processing +disabled if you’re using the standard USB/LSB modes. This disabling of +processing typically takes place when using data mode.
+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).
+This can be challenging the first time around:
Try a receive only (one audio card) set up first.
Ask someone who already runs FreeDV for help.
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.
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.
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.
-On newer radios (e.g. 7300, 7610), you may also need to set “CI-V USB Echo Back” to ON as this may be set to OFF by default.
-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.
-However someone may have worked through the same problem as you. Ask on the digital voice mailing list.
-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 Analog button will let you hear the received signal from the SSB radio.
-Try the Test Wave Files above to get a feel for what a FreeDV signal looks and sounds like.
-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.
+On newer radios (e.g. 7300, 7610), you may also need to set “CI-V USB +Echo Back” to ON as this may be set to OFF by default.
+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.
+However someone may have worked through the same problem as you. Ask +on the digital voice mailing list.
+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 +Analog button will let you hear the received signal +from the SSB radio.
+Try the Test Wave Files above to get a feel for what a FreeDV signal +looks and sounds like.
+Do you have the correct sideband? See USB or LSB section.
-Is it a FreeDV signal? SSTV uses similar frequencies. To understand what FreeDV sounds like, see the Test Wave Files section.
-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.
-Is it a FreeDV signal? SSTV uses similar frequencies. To understand +what FreeDV sounds like, see the Test Wave Files section.
+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.
+Many people struggle with initial CAT control and PTT setup:
Read the “CAT/PTT Configuration” section above.
Try the “Test PTT” button inside Tools->CAT and PTT Config.
Check your rig serial settings. Did you change them from defaults for another program?
Linux version: do you have permissions for the serial port? Are you a member of the dialout group?
Try the “Test PTT” button inside Tools->CAT and PTT +Config.
Check your rig serial settings. Did you change them from defaults +for another program?
Linux version: do you have permissions for the serial port? Are
+you a member of the dialout group?
Ask someone who already uses FreeDV to help.
Contact the digital voice mailing list. Be specific about your hardware, what you have tried, and the exact nature of the problem.
Contact the digital voice mailing list. Be specific about your +hardware, what you have tried, and the exact nature of the +problem.
Please verify that you are running the correct drivers for the USB to serial adapter that you’re using. Information and download links for the drivers used by the most common devices can be found here.
-While it is preferred to use devices that use authorized/original versions of the various USB to serial chipsets, it is possible to use some cloned devices with older drivers. When doing this, you may also need to force Windows to use an older version of a driver instead of automatically updating the driver on reboot. See here for instructions on doing so in Windows 10. For Windows 8:
+Please verify that you are running the correct drivers for the USB to +serial adapter that you’re using. Information and download links for the +drivers used by the most common devices can be found here.
+While it is preferred to use devices that use authorized/original +versions of the various USB to serial chipsets, it is possible to use +some cloned devices with older drivers. When doing this, you may also +need to force Windows to use an older version of a driver instead of +automatically updating the driver on reboot. See here +for instructions on doing so in Windows 10. For Windows 8:
In order to use FreeDV 2020 mode, you must have both of the following:
+In order to use FreeDV 2020 mode, you must have both of the +following:
AES - Supports AES extensions
AVX * Supports AVX instruction extensions
FMA - Supports FMA extensions using YMM stateOn Linux, you can check for avx in the flags section of /proc/cpuinfo or the output of the lscpu command:
On Linux, you can check for avx in the
+flags section of /proc/cpuinfo or the
+output of the lscpu command:
lscpu | grep -o "avx[^ ]*"will display avx (or avx2) if your CPU supports the instructions.
will display avx (or avx2) if your CPU
+supports the instructions.
If your system does not meet either (1) or (2), the 2020 option will be grayed out.
-You may need to clean out the previous configuration. Try Tools - Restore Defaults. Set up your sound cards again with Tools - Audio Config.
-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.
-From January 2020 Apple is enforcing notarization for all macOS applications. The FreeDV developers do not wish to operate within the Apple ecosystem due to the cost/intrusiveness of this requirement.
+If your system does not meet either (1) or (2), the 2020 option will +be grayed out.
+You may need to clean out the previous configuration. Try Tools - +Restore Defaults. Set up your sound cards again with Tools - Audio +Config.
+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.
+From January 2020 Apple is enforcing notarization for all macOS +applications. The FreeDV developers do not wish to operate within the +Apple ecosystem due to the cost/intrusiveness of this requirement.
+
Security & Privacy shows the Open Anyway option for FreeDV:
+
+
Or you can use command line options:
xattr -d com.apple.quarantine FreeDV.appor
xattr -d -r com.apple.quarantine FreeDV.appmacOS has a longstanding issue that prevents certain audio devices from appearing. More info here.
-macOS has a longstanding issue that prevents certain audio devices +from appearing. More info here.
+For the Linux inclined:
$ pandoc USER_MANUAL.md -o USER_MANUAL.pdf "-fmarkdown-implicit_figures -o" \
--from=markdown -V geometry:margin=.4in --toc --highlight-style=espresso| AWGN | -Additive White Gaussian Noise - a channel with just noise and no fading (like VHF) | +Additive White Gaussian Noise - a channel with just noise and no +fading (like VHF) |
| FEC | -Forward Error Correction - extra bits to we send to protect the speech codec bits | +Forward Error Correction - extra bits to we send to protect the +speech codec bits |
| LDPC | @@ -642,26 +1199,37 @@ FMA - Supports FMA extensions using YMM state
Note: Official Windows releases are now signed using Software Freedom Conservancy’s code certificate. To validate that the installers and binary files are properly signed, right-click on the file, choose Properties and go to the ‘Digital Signatures’ tab.
-See this for more information about changes in versions prior to v1.9.0.
-Note: Official Windows releases are now signed using Software +Freedom Conservancy’s code certificate. To validate that the installers +and binary files are properly signed, right-click on the file, choose +Properties and go to the ‘Digital Signatures’ tab.
+See this +for more information about changes in versions prior to v1.9.0.
+