Remote SDR V5 -Raspberry 4B or Orange Pi Image Installation
Here is the detailed procedure to install Remote SDR in version 5, on a Raspberry Pi 4B with at least 2 GB of memory or an Orange Pi Zero 2. The latest images written for an SD card of 16 GB or more are available on Github.
Installing the image
- Upload the image corresponding to your card on Github
- Unzip the image
- Burn the image to a minimum 16GB micro SD card with PC software like Win32diskmanager
- Connect an SDR Pluto or HackRF One and RTL-SDR or SDR Play
- Connect the Raspberry/Orange to the local ethernet network
- Power on the Raspberry/Orange
- Go to your box to find the IP address that has been assigned to the Raspberry/Orange Pi
- All Remote SDR source codes are in /remsdr folder
Only one Raspberry PI 4 is necessary with an Adalm-Pluto or a HackRF in transmission and an RTL-SDR in reception.
Since version 2.5 of Remote SDR, it is possible to connect 2 HackRF One to a single Raspberry.
Other SDRs such as RSP1 or RSP1A are also treated.
Launching Remote SDR
You launch the application on the address of the receiver. You need a recent browser like Chrome, Chromium or Edge. Don’t use Firefox.
http://<ip of the Rasperry Pi>
Note that all exchanges (video, audio) from version 5, are done in https on the usual port 443.
In parallel, it is possible to interface with Gpredict via port 8006 for the receiver and 8007 for the transmitter.
It is also possible to connect via VSPE with standard Omnirig interfaces.
Access is via the secure https protocol in order to be able to access the microphone and some signal processing functions of the browser. When you first connect, you will get a security alert message because of a self-signed security certificate and not certified by an accredited organization..
Do not worry and click on advanced settings.
The Settings page allows you to define the parameters of your transceiver. You must enter an access key (1234 by default) to be able to modify them. It is important to define the model of the connected SDR.
Similarly, you must enter the access key to be able to transmit.
Adaptation to QO-100
To compensate for LNB frequency drift, Remote SDR can lock onto QO-100 beacons and compensate for the drift. To facilitate the acquisition of beacons, it is necessary to give a search frequency range compatible with the drifts of your installation with summer or winter temperatures. For example +-30kHz and put that in the RX configuration / Frequency Bands table.
It is possible to share the receiver between several users. But only one person can drive the audio channel fader. It is entitled to green light on “SDR RX Pilot”. The other people connected are red.
The system owner can force his pilot position. To define yourself as the owner, you must enter in the “Settings” page an access key identical to that of the AccessKey.txt file in the /remsdr folder. By default “1234”, but it is recommended to customize it.
SDR Rapid Test
You can do a quick test to verify that the connected SDR(s) are visible to the Raspberry/Orange Pi. Go to the Tools page and click on “List USB devices”.
Reset Old Configurations
It is not impossible that an old configuration disturbs the first start of Remote SDR V5. In this case, perform a “Reset” of the settings saved locally in your browser.
System Setup Customization
You can, but do not have to, customize the installation of the system on your Raspberry/Orange Pi. The image on Github is configured in English language, US keyboard and GMT time. Access the Raspberry (user pi, password: remsdr) or the Orange Pi (user root, password: remsdr) by ssh and type:
raspi-config ou armbian-config
In the ‘Location’ section you can enter your preferences.
You can also access the Raspberry/Orange Pi in graphical mode using the VNC chrome extension or a dedicated application.
user: root for the Orange Pi and port 5901
All source files are in the /remsdr folder.
If you use your Remote SDR application intensely, consider putting a heatsink on the CPU. The charging rate is significant: around 60%.
Do not view Remote SDR on a monitor connected to the Raspberry/Orange and running in the web browser. If this is possible, the computational load will be too great and this will result in audio dropouts and CPU overheating.
I recommend that you install a safety device on the power supply of the amplifiers as described here.
From this version 5, the updates, as far as possible, will be done directly by an online download. To check your configuration and the latest available, click on the “Look for updates” button.