Accedi
OWRX+ with Pluto+
I'm not entirely sure, so I have to ask here — is Pluto+ supported by OWRX+?
The “old” Adalm Pluto seems to work via the Soapy module, but what about Pluto+?
Thanks and with best regards,
Steffen
Modalità di lettura
text color in opwrx+
Hello everyone,
I saw on a Spanish OPWRX+ WebSDR that the frequencies shown in the "receiver" window were in color. How can we do that? Modify a CSS or is there an easier way?
Thanks
I saw on a Spanish OPWRX+ WebSDR that the frequencies shown in the "receiver" window were in color. How can we do that? Modify a CSS or is there an easier way?
Thanks
Re: [new] Improved OpenWebRX Packages Available
Hi Marat,
I have noticed that if the reception passband is altered by moving the edge of the passband marker, it sticks and cannot be reset by switching between modes, which used to be possible.
Dragging the passband back to the original value is not always possible because of the granularity of the setting. The only method I have found is to clear the browser cookies and restart the instance.
I don't know if this is a deliberate new feature or a bug, but is it easy to restore the default value in some way ?
If not, would it be possible to be able to reset it back to the default value, perhaps by a long click on the mode button, or a shift click or similar ?
Thanks,
Martin
On Mon, Dec 15, 2025 at 07:48 AM, Marat Fayzullin wrote:
Re: DAB with OPWRX 1.3
OK, thanks, but I'm using an RTL-SDR dongle and I've already
tried lowering the gain, but without success.
For now, I've given up on the idea of receiving DAB...
Le 28/12/2025 à 19:44, grem via
groups.io a écrit :
just a note:in my case DAB-Decoder is VERY sensitive to wrong Frequency Setting and strong Signal.so if any problems, try ATT and vary the Frequency a little bit.-> using my cheap RTL Device is perfect for DAB here, with the RSPduo there is no chance, as even a small antenna is overloading the input (~15km direkt line of sight to two Transmitters
Re: DAB with OPWRX 1.3
just a note:
in my case DAB-Decoder is VERY sensitive to wrong Frequency Setting and strong Signal.
so if any problems, try ATT and vary the Frequency a little bit.
-> using my cheap RTL Device is perfect for DAB here, with the RSPduo there is no chance, as even a small antenna is overloading the input (~15km direkt line of sight to two Transmitters
Re: Python error on new install Ubuntu 24.04 server
Did you try Claude AI or ChatGPT?
You will surprise what those can actually do!
I purchase the RX888, and when I try to set 2m frequency, it crash.. But not on the rf. ChatGPT was make me turn around over and over, Claude told me that i need to specify the RF port... Doh! (working after that)
Re: Python error on new install Ubuntu 24.04 server
Where do i find the installation instructions for Ubuntu 24 ?
Re: [new] Improved OpenWebRX Packages Available
The new OpenWebRX+ 1.2.102 is now available from the repository. This is mostly a bugfix release that corrects MQTT initialization order, fixes background SSTV operation, and a few other things. I have also added an option to report ISM signal levels, submitted by Ryan Jacobs. Release news and discussion forum can be found on Telegram. See below for all changes.
- Added MSK144 to WSJT modes received over MQTT.
- Added ISM signal level reporting [Ryan Jacobs].
- Added 27700kHz SSTV frequency to all bandplans.
- Fixed MQTT initialization order [Jan Loewe].
- Fixed background digital mode instantiation.
- Enabled RTTY skimmer to send to PskReporter.
- Extended CB band to 28MHz in all bandplans.
- Removed NOAA satellites from the bandplans.
- Improved HAM callsigns verification.
- Added ISM signal level reporting [Ryan Jacobs].
- Added 27700kHz SSTV frequency to all bandplans.
- Fixed MQTT initialization order [Jan Loewe].
- Fixed background digital mode instantiation.
- Enabled RTTY skimmer to send to PskReporter.
- Extended CB band to 28MHz in all bandplans.
- Removed NOAA satellites from the bandplans.
- Improved HAM callsigns verification.
PS: Short cheat sheet for people who just cannot get things to work:
1) If it does not work for you, reload OpenWebRX page while holding the SHIFT key.
2) If it does not work for you, check "Settings | Feature report" page to see what you are missing.
3) If it does not work for you, wait for a day or two, maybe it starts working or you figure it out.
4) If it does not work for you, create a separate forum thread and explain your problem there. Attach the logs, obtained with "sudo journalctl -u openwebrx". Do not paste the entire log into the message, attach it as a file instead.
Re: [new] Improved OpenWebRX Packages Available
The new OpenWebRX+ 1.2.101 is now available from the repository. It extends CW skimmer functionality, letting it report CW spots via MQTT and PskReporter. The CW skimmer can now run in background, as a service. I have also fixed a rather serious issue with the bandwidth allocation for background services. Release news and discussion forum can be found on Telegram. See below for all changes.
- Fixed bandwidth allocation for services.
- Added callsign spotter to CW/RTTY skimmers.
- Added CW spot reporting to PskReporter.
- Added CW skimmer to band plans.
- Added more checks to callsign-to-country conversion.
- Added MQTT events for downloading data from the web.
- Added timestamps to chat messages.
- Enabled CW/RTTY skimmers as background services.
- Extended CW/RTTY skimmer bandwidth to 96ksps.
- Removed NOAA-15 and NOAA-19 satellite decoders.
- Added callsign spotter to CW/RTTY skimmers.
- Added CW spot reporting to PskReporter.
- Added CW skimmer to band plans.
- Added more checks to callsign-to-country conversion.
- Added MQTT events for downloading data from the web.
- Added timestamps to chat messages.
- Enabled CW/RTTY skimmers as background services.
- Extended CW/RTTY skimmer bandwidth to 96ksps.
- Removed NOAA-15 and NOAA-19 satellite decoders.
PS: Short cheat sheet for people who just cannot get things to work:
1) If it does not work for you, reload OpenWebRX page while holding the SHIFT key.
2) If it does not work for you, check "Settings | Feature report" page to see what you are missing.
3) If it does not work for you, wait for a day or two, maybe it starts working or you figure it out.
4) If it does not work for you, create a separate forum thread and explain your problem there. Attach the logs, obtained with "sudo journalctl -u openwebrx". Do not paste the entire log into the message, attach it as a file instead.
Re: DAB with OPWRX 1.3
Thank you very much Albert !
Le 09/12/2025 à 01:14, Albert Öttl via
groups.io a écrit :
The yellow dotted lines designate the bandwidth of the DAB demodulator.The DAB signal has a bandwidth of approx. 2 MHz and is not in the FM band (87 - 108 MHz), but around 200Mhz.
Here in Vienna we have 3 active DAB+ channels with 40 programs in sum.178.352 MHz (channel 5C)180.064 MHz (channel 5D)211.648 MHz (channel 10B)
Re: DAB with OPWRX 1.3
Hi Robert,
in the small window appears the information about the multiplexer (DAB ensemble) and the list of the available programs.
The yellow dotted lines designate the bandwidth of the DAB demodulator.
The DAB signal has a bandwidth of approx. 2 MHz and is not in the FM band (87 - 108 MHz), but around 200Mhz.
Here in Vienna we have 3 active DAB+ channels with 40 programs in sum.
178.352 MHz (channel 5C)
180.064 MHz (channel 5D)
211.648 MHz (channel 10B)
Albert
Re: DAB with OPWRX 1.3
Albert,
You answered my question about the new DAB function in Openwebrx version 1.3.
However, I think you misunderstood my question, unfortunately.I'm familiar with DAB, but I was asking what should appear in the small window (a screenshot was attached...). I receive many stations here on the FM band.
Also, what are the yellow dotted lines at the top of the waterfall display for?
(Albert, I couldn't open your .tiff file.)
Le 08/12/2025 à 15:32, Albert Öttl via
groups.io a écrit :
Hi Robert,
explanation here: https://en.wikipedia.org/wiki/Digital_Audio_Broadcasting
You have to tune to one of the channels in your region in order to decode the transmissions.
Example:
Regards,Albert
Am 06.12.2025 um 10:43 schrieb ROBERT_FR via groups.io <lavigneroland@...>:
Hello everyone,I just installed the October 11, 2023 version of OpenWebRX.(V1.3.0)
The new feature (for me) is that there's now a "DAB" button that opens a small "Loading" window in the bottom left corner (which is empty).I don't understand how it works. Is there an explanation somewhere?Thanks<DAB_LOADING.png>
Re: DAB with OPWRX 1.3
Hi Robert,
explanation here: https://en.wikipedia.org/wiki/Digital_Audio_Broadcasting
You have to tune to one of the channels in your region in order to decode the transmissions.
Example:
Regards,
Albert
DAB with OPWRX 1.3
Hello everyone,
I just installed the October 11, 2023 version of OpenWebRX.(V1.3.0)
The new feature (for me) is that there's now a "DAB" button that opens a small "Loading" window in the bottom left corner (which is empty).
The new feature (for me) is that there's now a "DAB" button that opens a small "Loading" window in the bottom left corner (which is empty).
I don't understand how it works. Is there an explanation somewhere?
Thanks
Re: FreeDV ?
Is the FreeDV extension in Openwebrx going to be capable of using the RADE mode?
--
Martin
Re: Trying to install via OpenWebRX official stable releases for Ubuntu Jammy Jellyfish
That's an error that typically occurs when you have the wrong repository selected for your distribution. Please make sure to select the correct repository.
Trying to install via OpenWebRX official stable releases for Ubuntu Jammy Jellyfish
Hi,
I'm trying to install from
OpenWebRX Ubuntu Repository
and I get following dependency errors:
The following packages have unmet dependencies:
python3-csdr : Depends: python3 (< 3.11) but 3.12.3-0ubuntu2.1 is to be installed
rtl-connector : Depends: librtlsdr0 (>= 0.6.0) but it is not installable
python3-csdr : Depends: python3 (< 3.11) but 3.12.3-0ubuntu2.1 is to be installed
rtl-connector : Depends: librtlsdr0 (>= 0.6.0) but it is not installable
Huh, being a novice linux user I'm not able to cope/fix this, any hints appreciated !
Best rgds/73
SM0FGT - Keijo
Re: [new] Improved OpenWebRX Packages Available
The new OpenWebRX+ 1.2.100 is now available from the repository. Release news and discussion forum can be found on Telegram. It greatly enhances MQTT functionality. The new privacy options let you disable MQTT reports on server activity. The new subscription options let your server receive MQTT data from other OpenWebRX+ servers and show it on the map. There is also a distributed chat option that enables relaying chat messages between servers. Read more about this functionality in the documentation, by clicking on the question mark icon in the OpenWebRX+ UI. See below for all changes.
- Added option to chat between OWRX+ servers via MQTT.
- Added option to relay WSJT spots between OWRX+ servers.
- Added option to relay APRS/AIS data between OWRX+ servers.
- Added option to relay aircraft data between OWRX+ servers.
- Added number of connected clients to CLIENT MQTT reports.
- Added options to disable RX and CLIENT MQTT reports.
- Fixed MQTT code to work with Paho MQTT 2.x.
- Fixed some maps not wrapping properly.
- Added option to relay WSJT spots between OWRX+ servers.
- Added option to relay APRS/AIS data between OWRX+ servers.
- Added option to relay aircraft data between OWRX+ servers.
- Added number of connected clients to CLIENT MQTT reports.
- Added options to disable RX and CLIENT MQTT reports.
- Fixed MQTT code to work with Paho MQTT 2.x.
- Fixed some maps not wrapping properly.
PS: Short cheat sheet for people who just cannot get things to work:
1) If it does not work for you, reload OpenWebRX page while holding the SHIFT key.
2) If it does not work for you, check "Settings | Feature report" page to see what you are missing.
3) If it does not work for you, wait for a day or two, maybe it starts working or you figure it out.
4) If it does not work for you, create a separate forum thread and explain your problem there. Attach the logs, obtained with "sudo journalctl -u openwebrx". Do not paste the entire log into the message, attach it as a file instead.
Re: DMR simplex
On Fri, Nov 28, 2025 at 07:43 PM, Jakob DD5JFK Ketterl wrote:
It's not as big a loss as you think. Most transmissions you'll be receiving on DMR are going to be coming from a repeater anyway.As I said, it hasn't been analysed, so I can't really give any advice to resolve. Feel free to dig into the code and see for yourself.
I think you're wrong. We use a lot of DMR simplex here. We don't listen to DMR repeaters.
Simplex connections are the best.
I'll try to do something about the code if i can.
Simplex connections are the best.
I'll try to do something about the code if i can.