Hi, Craig!

 

The fix you requested is now in OWRX+ 1.2.120. Please, check at some point that 1.2.120+ OWRX instances are no longer sending 3rd party or TCP packets to APRS-IS.

Well explained, fully understood. Many thanks for quick response.

 

Kind regards,

Arek

Background decoding, when enabled, will automatically decode anything that is available, that means: anything that is registered in the bandplan, is enabled, and is available on a currently running profile.

 

I suppose your device is decoding on profiles that are being used by clients, or you have the "keep device running at all time" option checked, in which case it will just continue decoding on the last profile used on the device. The schedule is a feature that will take control of the device if no clients are using the device any more, it just gives you more control over what the device should do while idle.

 

PSKreporter on the other hand has its own configuration, where it can be en- or disabled separately.

Hello. I have a very interesting issue regarding background decoding. After selecting the "Enable background decoding services" option, the server immediately begins decoding WSPR (which is the only mode I have selected) and sending spots to PSKReporter simultaneously on the 40m and 20m bands. What makes this particularly interesting is that my SDR profiles do not have the "Run background services on this device" option enabled, nor do I have a "Scheduler" configured. Decoding starts immediately upon checking the "Enable background..." option. I cannot understand why it specifically targets the 20m and 40m bands, or why it begins decoding and spotting straight away. I have three devices plugged to RPi4: one RTL and two Sdrplay's. The RTL profile covers only VHF/UHF; the first Sdrplay (RSP1) has profiles: 160m, 80/60m, 40m, 30m, ..., 6m; and the second Sdrplay (RSPa1) has profiles for 20m, 15m, and 10m. It is worth noting that the first profile on the RSP1 is 160m, while the first profile on the RSPa1 is 20m. The server is not open in a web browser. Thanks for any opinions and help to understand this ironically issue.

 

73

Arek

Hello. I forgot my password on receiverbook.de. When I click on forgot password, the system does not send the ID for password reset. What is the problem? Best regards.

Thanks for the reply. I had an issue with the PPM setting that needed adjustment. I also need to find a solution for the high gain. I added a blacklist entry that frees up the receiver, decoupling it from the DVB-T receiver.

First create the following file (copy past from sudo all the way to last EOF)

sudo tee /etc/modprobe.d/exclusions-rtl2832.conf <<EOF
# Blacklist host from loading modules for RTL-SDRs to ensure they
# are left available for the Docker guest.

blacklist dvb_core
blacklist dvb_usb_rtl2832u
blacklist dvb_usb_rtl28xxu
blacklist dvb_usb_v2
blacklist r820t
blacklist rtl2830
blacklist rtl2832
blacklist rtl2832_sdr
blacklist rtl2838

Do you mean OpenWebRX+ 1.2.117 SD Card Image for 64bit Raspberry Pi ?

 

RasPi 3 probably doesn't have enough processing power, and although it has 64-bit ARM core with a 32-bit GPU, the usual RasPi OS is only 32-bit.

 

I'd suggest minimum RasPi 4 (or even better a 5) hardware, to be able to take full advantage of OWR+.

 

 

On Tue, Aug 4, 2026 at 05:26 AM, GEORGE-SV1GGY wrote:

Good evening to the group. I have an RPi 3B and installed OpenWebRx from the official site (dated 11/10/2023), and it works very well. However, when I installed OpenWebRx version 1.2.117 from LZ2SSL, I get no VHF/UHF/HF reception at all. In the first instance, the system recognizes the SDR as an RTL-SDR, whereas in the second, it recognizes it as a DVB TV receiver. Does anyone have any idea what I should do? The waterfall display is blue, but there is no signal reception. All settings seem to work, yet there is no reception. Thanks in advance.

The issue is that 32 bit installations are not compatible with the C FREEDV RADE decoder. 
I re-installed OpenWebRX+ as 64bit and RADEL/RADEU was included by default. 

73 

I am running openwebrx+ on my Debian box (AMD64) and I was able to compile the software into a .deb file, then install the deb.  I'm not related to the project at all, but I'll try to help if I can.  

 

At https://github.com/peterbmarks/radae_decoder  I followed the instructions under "Install dependencies (Debian/Ubuntu)".  I then followed the "quick build" under  "Debian Package for webrx_rade_decode" .

 

A .deb file was built, then I used dpkg to install it.

 

It installed a file /usr/bin/webrx_rade_decode

 

I restarted openwebrx+ and boom!  there were new modes listed as "RADEU" and "RADEL".  I tried using it a bit on what I thought were FreeDV signals and it did not seem to be working.  No sound.  But maybe the signal was too weak or somthing because as I was scanning the bands last night, I ran across the Tuesday night FreeDV net and it worked flawlessly.

 

I don't know what platform you're trying to run openwebrx+ on, but it looks like the RADE decoder page has good instructions for MAC also.  If on a Raspberry PI, then I'm guessing the Debian instructions MAY work on there.  I don't know.  I hope this is of some help.