Raspberry / Orange Pi not starting
After burning an image to an SD card, the processor does not start.
Very often, it is a weak 5v supply that is the source of this blockage. Change the power supply to a model that provides a little more than 5v (5.1v to 5.3v) and that’s fine.
Twice I had corrupted files on the SD card. You must either:
- redo the image
- update/rewrite the sources in the /var/www/html folder via an SSH connection. Do not forget to open the rights on the files.
Error in browser console or empty parameter fields
jquery-3.4.1.min.js:2 Uncaught TypeError: Cannot read properties of undefined (reading ‘enumerateDevices’)
at Init_Sliders_TX_Audio (remote_TX_audio.js:536:25)
Malfunction when switching from Windows 10 to Windows 11.
Declaration secure IP address in chrome://flags or edge://flags missing. See https://f1atb.fr/index.php/2022/01/06/microphone-and-signal-processing-authorization/
A bad connection between the Raspberry and the PC can give a choppy transmission with loss of audio signals.
Try switching to wired ethernet. In version 4.5, the size of the input buffer will be increased to 2s max to better absorb these bit rate bursts. This brings delay, but in the event of a good link, the size of the buffer gradually decreases to around 200ms.
Hack RF One ou Pluto
Crashes or connection difficulties.
There are 2 potential sources of difficulty.
- A poor quality power supply. Change power supply for your processor and Hack RF. Differences are visible between an output at 5v or rather 5v3.
- The quality of the USB cable. The flow being important, there can be cuts with badly shielded cables. Try other cables.
Remember to take a look at the “Tools” page to check that all USB devices are visible.
HackRF One and RTL-SDR
HackRF and RTL-SDR conflicts. The HackRF does not transmit. The 2 SDRs using the same drivers, the Raspberry does not know which is the transmitter.
Change the order of the USB ports or preferably put in the TX.js configuration file the last 4 digits of the HackRF serial number.
The Pluto is visible in the list of devices connected via USB, but the TX or RX LED does not turn green.
In the Tools page, do a Pluto Reboot
For unmodified Adalm Plutos that cannot go below 325MHz, you need to correct the startup frequency value in GNU Radio which are around 144MHz and put them around 434 MHz. Version Remote SDR 4.5 and below.
The system does not start at the correct frequency in reception and no transmission.
Open GNU-Radio and load the files pluto-rx_sanw_v3.grc and pluto_tx_ssbnbfm_v3.grc. In the properties (right click), put a frequency around 434,000,000 Hz for the following blocks:
Once modified, save the files and generate the executable files in python by pressing the small screen. Close the application and relaunch Remote SDR.
Remote SDR saves your last chosen configurations, such as USB mode, frequency band, audio level etc., in the local storage area of the web browser. This allows you to find the configurations when your system restarts.
The web page loads incompletely due to errors, the SDR RX On light does not turn green. This follows an update, changes to the configurationRX.js or configurationTX.js files.
Go to the “Tools” page and select “Reset Local Storage in browser” at the bottom of the page. This resets all initial settings and avoids configuration conflicts.
If the “Tools” page does not load correctly, go to the console (Ctrl+Shift+I) and clear all settings under the application/local storage tab.
The page loads incompletely due to errors, the SDR RX On light does not turn green. This follows an update and cached data of the browser in an old version not compatible with the rest.
It is necessary to force the reloading of all the files by the browser. Press CTL-F5 repeatedly.