Accedi
Re: APRS packet errors
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.
Modalità di lettura
2.5 Admins 311: Couch Cushions
Microsoft restored an account including files that it initially claimed wasn’t possible, Apple might lock down phones if people don’t keep up their lease payments, ZFS scrubs shouldn’t be painful, and accessing another network from a locked-down work machine.
Plugs
Support us on patreon and get an ad-free RSS feed with some early episodes
ZFS vs Ceph: Do You Actually Need Ceph?
News/discussion
Microsoft restores player’s 25-year-old account following widespread backlash
iOS 27 code suggests Apple could restrict leased devices after missed payments
If Scrubs Hurt, Your ZFS Design Is Broken
Free consulting
We were asked about accessing another network from a locked-down work machine.
Linux After Dark – Episode 120
Re: [new] Improved OpenWebRX Packages Available
The new OpenWebRX+ 1.2.120, available from the repository, adds bubble display of bookmarks, as they get selected, as well as improvements to APRS reporting. See below for all changes.
- Added bookmark info bubbles when clicked.
- Fixed reporting third party APRS packets.
- Disabled reporting non-reportable APRS packets.
- Fixed typo in APRS "adressee" name.
- Stripped whitespace from APRS addressee.
- Fixed reporting third party APRS packets.
- Disabled reporting non-reportable APRS packets.
- Fixed typo in APRS "adressee" name.
- Stripped whitespace from APRS addressee.
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: Background decoding - interesting problem
Well explained, fully understood. Many thanks for quick response.
Kind regards,
Arek
Re: Background decoding - interesting problem
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.
Proton sta sviluppando un browser web (basato su Chromium)
Proton sta lavorando a un proprio browser web. L’azienda svizzera famosa per i suoi prodotti Proton VPN e Proton Mail, è alla ricerca di sviluppatori per creare un browser incentrato sulla tutela della privacy degli utenti. A rivelarlo è un annuncio di lavoro comparso sul sito di Proton nel quale si cerca un ingegnere software […]
L'articolo Proton sta sviluppando un browser web (basato su Chromium) proviene da Marco's Box.
Background decoding - interesting problem
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
Il sintetizzatore software Xfer Serum 2 sbarca su Linux
Xfer, creatrice dei popolari sintetizzatori software VST Serum e Serum 2, ha pubblicato sul proprio forum una beta per Linux. Per chi produce musica al computer è un’ottima notizia: questo plugin non ha mai funzionato in modo affidabile con Wine/Yabridge ed è spesso indicato come uno dei motivi per cui molti evitano di passare a […]
L'articolo Il sintetizzatore software Xfer Serum 2 sbarca su Linux proviene da Marco's Box.
