Category: zzz Archives Remote SDR zzz

Remote SDR v2 – Raspberry 4B image installation

Raspberry 4

Obsolete. Go here

Remote SDR version 2.5 available on Github

Here is the detailed procedure to install Remote SDR version 2 on a Raspberry Pi 4B with at least 2 GB of memory. The latest images written for an SD card of 16 GB or more are available on Github.
https://github.com/F1ATB/Remote-SDR/releases

Remote SDR V2

Remote SDR is an application allowing remote control from a web browser of a radio transceiver based on 1 or 2 SDR (Software Design Radio).

The main features are:

  • Compatible with Adalm-Pluto SDR or HackRF One and RTL-SDR
  • Reception in NBFM, WBFM, AM and SSB
  • Transmission in NBFM or SSB with Pluto or HackRF One
  • Full-Duplex transmission and reception
  • Reception spectrum on 2048 FFT points
  • System and SDR observation tools

Installing the image for the Raspberry PI

  • Download the image corresponding to your card on Github https://github.com/F1ATB/Remote-SDR/releases
  • Unzip the image
  • Burn the image on a minimum 16GB micro SD card with PC software such as Win32diskmanager
  • Connect a Pluto or HackRF One SDR and RTL-SDR
  • Connect the Raspberry to the local Ethernet network
  • Power on the Raspberry Pi
  • Go to your box to find the IP address that has been assigned to the Raspberry Pi

Launch of Remote SDR v2

Only one Raspberry PI 4 is necessary with an Adalm-Pluto or a HackRF in transmission and an RTL-SDR in reception.

Rpi4 – Pluto
Rpi4 – HackRF – RTL-SDR

Since Remote SDR version 2.5, two HackRF One can be connected to one Raspberry 4B.

F1ATB QO-100 setup. Raspberry 4 and 2 HackRF One

You launch the application on the address:

http://<ip du Rasperry Pi>

You need a modern browser like Chrome or Edge. These do not give access to the microphone if the site does not have secure access in https. On your local network at home, you generally work in http simply. To get around this difficulty, the solution is to set up a derogation at the level of the web browser by accessing the “flags” parameters. you must type in the address bar:

with Chrome: chrome://flags

with Edge(2020): edge://flags

Look for the heading:

Insecure origins treated as secure

Fill in the form as below with the IP address of the Raspberry PI which provides the pages.

Note that the exchanges are done in http on the usual port 80 for the contents of pages. Ports 8001 to 8003 are used to exchange data with the Raspberry Pi of the reception part. Ports 8004 to 8005 are used to exchange data from the transmit part.

Customization of the installation

The image on Github is configured in English language, GB keyboard and GMT time. Access the Raspberry Pi in ssh (user pi, password: remsdr) and type:

raspi-config

In the ‘Location’ section you can enter your preferences.

You can also access the Raspberry Pi in graphics mode using the VNC extension from chrome or a dedicated application.
user : pi
password : remsdr

All sources are in the folder /var/www/html .

Quick SDR Test

You can do a quick test to verify that the connected SDR (s) are visible to the Raspberry Pi 4. In a Terminal window, make a list of Usb(s ) by typing: lsusb
The devices present should appear.

Adalm-Pluto from Analog Devices connected

Cooling

If you use your Remote SDR application intensely, consider putting a heat sink on the CPU. The processing load is important: around 60%.

Do not display Remote SDR on a monitor connected to the Raspberry and running in the web browser. If feasible, the processing load will be too great and this will result in audio losses and processor overheating.

Also, I recommend a transmitter security system as described here.

Video on Remote SDR V2

Posts about Remote SDR