Skip to main content

Install WSJT-X and fldigi on Raspberry pi

Nowadays, digital communication is popular in amateur radio. JT65 and FT8 are capable of DX communication with weak signals.

In the era of urbanization, the space for installing antennas is gradually diminishing. So we seem to prefer communications that can be transmitted away with weak signals.

Install wsjtx, the most representative software for weak signal digital communication, in Raspberry Pi.

The basic setting for Raspberry Pie is 'Raspberry pi 3 Setup (basic)' on this blog.

If the installation order changes, it may not work normally or you see the many erros because wsjtx uses other libraries.

0.Turn on Raspberry PI

1.apt-get update
  Click Terminal Icon on taskbar
  type 'sudo apt-get update' [enter]

2.Click Raspberry pi Icon on taskbar -> Preferences -> Click Add/Remove Software

3.type 'fldigi' enter on left top edit box

4. Check all items

5.Press [OK] Button

6.wait moment, then type password for user pi
  default password of pi is 'raspberry'

7.wait for install complete (2~5 minute)

8.When all the installation is finished, the Add/Remove Software window is closed.
  You can see the installed amateur radio related software like blow image

  click Raspberry pi icon on taskbar -> Hamradio

9.apt-key update
type 'sudo apt-key adv –keyserver –recv-keys 862549F9' inter terminal

type 'sudo nano /etc/apt/sources.list'
add 1 line
deb trusty main

9.1 apt-get update 
  Click Terminal Icon on taskbar
  type 'sudo apt-get update' [enter]

10.Install wsjtx
Click Raspberry pi icon on taskbar -> Preferences -> click Add/Remove Software

type 'wsjtx' [Enter]

11.Check item  (Version check -> 1.8.0)

12.Click OK Button, and type password for pi -> click ok button
  pi ha default password as 'raspberry'

13.complete install wsjtx, you can see the wsjtx icon

14.Run wsjtx
perhap you will see Error dialog boxs. - no problem
Click to OK Buttons

15.Clieck Settings menu (File -> Settings)

16.input your Callsign and Grid

If you do not know your grid, see below link.


17.Set Audio
Depending on your audio settings, it may look different from the screen below.

In my case, I used an external USB ($1 in aliexpress) card and it worked when I set it like above.

18.All installations are complete.
  WSJT-X restart and enoy


  1. root@FriendlyELEC:~# apt-key adv -keyserver recv-keys 862549F9
    Executing: /tmp/tmp.vkYCdEMhRB/ -keyserver

  2. Err:1 trusty InRelease
    The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5794D54C862549F9
    Reading package lists... Done
    W: GPG error: trusty InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5794D54C862549F9
    E: The repository ' trusty InRelease' is not signed.
    N: Updating from such a repository can't be done securely, and is therefore disabled by default.
    N: See apt-secure(8) manpage for repository creation and user configuration details.

    1. Fix for the error above.

      sudo apt-get install wsjtx
      E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
      udo dpkg --configure -a

      sudo apt-get install wsjtx


Post a Comment

Popular posts from this blog

How to upgrade uBITX Firmware

uBITX is based on Arduino Nano. So uBITX's firmware upgrade method is the same as Arduino.
There are two ways to upgrade the firmware of uBITX.

The first is to compile the source from the Arduino IDE, and the second is to upload the compiled hex file using the Firmware Upgrade Tool.

I'll show you how to upload a compiled hex file as a second method.

1.Connect the uBITX's USB cable to the computer.

2.Run Device Manager on your computer.
  The way to open the Device Manager for each OS Version differs slightly.
  In most Windows, you can easily launch the Device Manager by running.

  On your computer, press the Windows key + R.

 Type devmgmt.msc and press OK Button.

On most operating systems, there will be a serial port named Ports with CH340. If so, the next step is skipped.

If the serial port is not installed as below, you need to install the driver.

Included in uBITX is the Adonano, which uses the CH340 USB To UART part.

Download the latest CH340 driver from the Internet.

CAT Support uBITX Firmware CEC Version 1.06 Release (Added WSPR)

uBITX Firmware CEC Version v1.06 (changed v1.061)

I deployed 1.06 and received feedback from WSPR's beta tester, Philip (G7JUR).
It was a problem that the LPF was not automatically selected according to band selection during WSPR transmission.

Version 1.08 has been released.

I modified it soon and changed uBITX Firmware CEC Version to 1.061.
uBITX Manager also changed Version to 1.01.


I released version 1.06 which added WSPR function to uBITX.
Beta testers have been very helpful when embedding WSPR functionality. WSPR will continue to improve in the future.

By using WSPR before and after QSO, you can check where your uBITX is spreading all over the world.  If uBITX Manager is used to put WSPR information into uBITX, uBITX no longer needs any external device to transmit WSPR.

The uBITX group's excellent tester also shared a …

CAT Support uBITX Firmware CEC Version 1.01 Release(Changed from v1.0)

CAT Support uBITX Firmware CEC Version 1.01  Release (Changed from v1.0)

uBITX Firmware CEC Version 1.06 has been released.
Please click the link below.

This version of the concept is an upgrade without hardware modifications. No hardware modifications are required to use this firmware. Continuous release and testing has been done in the uBITX group. I tried to put only the basic functions that an HF transceiver should have. The features have been upgraded with the advice of people who have great ideas in the uBITX group.
It was a project that started to contribute to the original source in github. The project was intended to fix some simple bugs and request merge to the original source. And I was planning to delete the project. At the beginning of the project there was a bit of discussion about this in the uBITX group.
Since then, I've keeping the original source type to allow code share with any user fork…