This article shows how to install FT8Call on Ubuntu. But first things first. Some intro into the topic.
Chances are if you read this you probably know FT8 well enough. This mode became very popular in mid 2017 on HF/VHF/UHF gaining solid base of users. As there are dedicated fans of FT8 there are also avid opponents of this transmission mode that claim that this are computers talking – QSO is made by PC – not people. I personally disagree with this statement but there are people that taken the extra step and implemented a transmission mode that addresses this issue. It is called FT8Call.
Jordan KN4CRD, FT8Call author says: “It is an experiment to test the feasibility of a digital mode with the robustness of FT8, combined with a messaging and network protocol layer for weak signal communication on HF, using keyboard-to-keyboard style interface”.
So it’s main differentiator is free text communication as opposed to FT8 where texts are fixed. FT8Call came to light in the summer of 2018. It’s too early to call it FT8 successor this early but it has some cool features and we can freely experiment with this mode.
Keep in mind that FT8Call is still in early development phase so instructions available here might get outdated. At the time of writing this article the latest version of FTCall is 0.6.3. It is worth noting that until the general release of FT8Call development versions only carry a 14 day lifespan. When your version expires you are required to upgrade to the latest version of the application available.
Links and download
Home for FT8Call is firstname.lastname@example.org website. It contains links to documentation (which is quite good by the way) and FT8Call binaries download but unfortunately you need to login with google or facebook account. There is also detailed design document on FT8Call by its author Jordan Sherer (KN4CRD). As this is open source you can grab the sources, read them or modify and contribute.
The latest builds of FT8Call are version 0.6.3:
- Desktop Linux (64-bit x86_64, Ubuntu AppImage)
- Desktop Linux (64-bit x86_64, Ubuntu 18.04 deb)
- Desktop Linux (64-bit x86_64, Ubuntu 16.04 deb)
- Desktop Linux (32-bit i386, deb)
- Raspbian Stretch (armv7, AppImage)
- Raspbian Stretch (armv7, deb)
- Windows 7-10 (win32_64)
- Mac OS 10.11+ (64-bit x86_64)
You can go with appimage build or regular deb file. I pick Desktop Linux (64-bit x86_64, Ubuntu 18.04 deb).
$ wget https://www.dropbox.com/s/54nquai0yvsqeu6/ft8call_0.6.3-devel_18.04_amd64.deb --2018-09-15 09:40:04-- https://www.dropbox.com/s/54nquai0yvsqeu6/ft8call_0.6.3-devel_18.04_amd64.deb Resolving www.dropbox.com (www.dropbox.com)... 126.96.36.199 Connecting to www.dropbox.com (www.dropbox.com)|188.8.131.52|:443... connected. ... HTTP request sent, awaiting response... 200 OK Length: 7723152 (7.4M) [application/x-debian-package] Saving to: ‘ft8call_0.6.3-devel_18.04_amd64.deb’ ft8call_0.6.3-devel_18.04_amd64.deb 100% [=============================================================================>] 7.37M 8.63MB/s in 0.9s 2018-09-15 09:40:07 (8.63 MB/s) - ‘ft8call_0.6.3-devel_18.04_amd64.deb’ saved [7723152/7723152]
$ sudo dpkg -i ft8call_0.6.3-devel_18.04_amd64.deb Selecting previously unselected package ft8call. (Reading database ... 210728 files and directories currently installed.) Preparing to unpack ft8call_0.6.3-devel_18.04_amd64.deb ... Unpacking ft8call (0.6.3-devel) ... Setting up ft8call (0.6.3-devel) ... Processing triggers for gnome-menus (3.13.3-11ubuntu1.1) ... Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.1) ... Processing triggers for mime-support (3.60ubuntu1) ...
Thats it! No missing dependencies and hassle. Good job.
What and where did it install?
$ dpkg -L ft8call /opt /opt/ft8call /opt/ft8call/bin /opt/ft8call/bin/fcal /opt/ft8call/bin/fmeasure /opt/ft8call/bin/fmtave /opt/ft8call/bin/ft8call /opt/ft8call/bin/ft8code /opt/ft8call/bin/jt4code /opt/ft8call/bin/jt65code /opt/ft8call/bin/jt9 /opt/ft8call/bin/jt9code /opt/ft8call/bin/message_aggregator /opt/ft8call/bin/msk144code /opt/ft8call/bin/qra64code /opt/ft8call/bin/qra64sim /opt/ft8call/bin/rigctl-wsjtx /opt/ft8call/bin/rigctld-wsjtx /opt/ft8call/bin/udp_daemon /opt/ft8call/bin/wspr_fsk8d /opt/ft8call/bin/wsprd /opt/ft8call/share /opt/ft8call/share/doc /opt/ft8call/share/doc/FT8Call /opt/ft8call/share/doc/FT8Call/AUTHORS /opt/ft8call/share/doc/FT8Call/BUGS /opt/ft8call/share/doc/FT8Call/COPYING /opt/ft8call/share/doc/FT8Call/INSTALL /opt/ft8call/share/doc/FT8Call/NEWS /opt/ft8call/share/doc/FT8Call/README /opt/ft8call/share/doc/FT8Call/THANKS /opt/ft8call/share/doc/FT8Call/changelog.Debian.gz /opt/ft8call/share/doc/FT8Call/copyright /opt/ft8call/share/ft8call /opt/ft8call/share/ft8call/JPLEPH /usr /usr/bin /usr/share /usr/share/applications /usr/share/applications/ft8call.desktop /usr/share/pixmaps /usr/share/pixmaps/ft8call_icon.png /usr/bin/ft8call
Keep in mind that FT8Call depends on accurate time keeping same way FT8 does. More on the subject in Time Synchronization on Ubuntu article.
First thing we see is development warning
Next configuration window pops up. It’s very similar to the one in WSJT-X.
This is how to configure IC-7300 control.
It somewhat resembles WSJT-X layout. It’s different though and I still learn how to use it.
Configuration file is located here ~/.config/FT8Call.ini in case you want to see what’s there. The directory into which FT8Call writes its data is located in ~/.local/share/FT8Call/.
~/.local/share/FT8Call/ ├── ALL.TXT ├── FoxQSO.txt ├── jt9_wisdom.dat ├── save │ ├── 180914_164915.wav │ ├── messages │ └── samples ├── timer.out └── wsjtx_wisdom.dat
I must say that at the time of writing of this article – September 2018 – there are not too many stations using FT8Call. Looking at the traffic on the group this may quickly change. Hope this helps. Have fun experimenting!
More: See my post on running WSJT-X on Ubuntu.
One thought on “FT8Call on Ubuntu 18.04”
Thanks for the helpful wsjt-x setup information on Ubuntu 18.04. I have the mcHF QRP SDR radio and a desktop PC rebuilt with a fresh copy of Ubuntu 18.04. After manually installing wsjt-x 1.9.1 I was getting hamlib error’s when testing the CAT control. Turn’s out that I needed to add dialout and audio to the id then CAT started working under the Yeasu 817 radio configuration.
I could not have succeeded without the information found on this website.