deadline extension: FOSDEM 2026 (Feb. 1 2026): call for contributions on SDR/DSP (deadlineDec. 1 2025)

The Software Defined Radio/Digital Signal Processing (SDR/DSP) devroom
is being organized for the 2026 FOSDEM held in Brussels (Belgium) Sunday
Feb. 1, 2026.

Any topic or achievement from the last year that you would be proud to
share with the community? A few slots for the SDR/DSP devroom are still
available, so the submission deadline is extended by a couple of weeks.

We are seeking contributions discussing FOSS software for
(radiofrequency) discrete time digital signal processing/software
defined radio (SDR) including digital communication and data integrity
(CRC calculation, Forward Error Correction -- FEC), communication
channel characterization, navigation and positioning, target ranging and
velocity measurement, and signal characteristics extraction from raw IQ
collected from single or multiple antennas, as well as software
frameworks easing such applications including GNU Radio, FutureSDR,
Pothosware or custom frameworks. Novel openhardware description,
possibly including the latest acceleration peripherals including FPGA
and GPUs (or others), is encouraged, especially if using FOSS
frameworks, but maybe also demonstrating how a radiofrequency grade
oscilloscope can make an excellent (discontinuous stream) SDR receiver.

Proposals should be submitted through
https://pretalx.fosdem.org/fosdem-2026/
December 1st at latest, or 2 weeks from now.

See you in Brussels, Jean-Michel

--

deadline reminder: FOSDEM 2026 (Feb. 1 2026): call for contributions on SDR/DSP (deadline Nov. 15 2025)

Reminder: tomorrow is the deadline for the call for contributions.

The Software Defined Radio/Digital Signal Processing (SDR/DSP) devroom
is being organized for the 2026 FOSDEM held in Brussels (Belgium) Sunday
Feb. 1, 2026.

We are seeking contributions discussing FOSS software for
(radiofrequency) discrete time digital signal processing/software
defined radio (SDR) including digital communication and data integrity
(CRC calculation, Forward Error Correction -- FEC), communication
channel characterization, navigation and positioning, target ranging and
velocity measurement, and signal characteristics extraction from raw IQ
collected from single or multiple antennas, as well as software
frameworks easing such applications including GNU Radio, FutureSDR,
Pothosware or custom frameworks. Novel openhardware description,
possibly including the latest acceleration peripherals including FPGA
and GPUs (or others), is encouraged, especially if using FOSS
frameworks, but maybe also demonstrating how a radiofrequency grade
oscilloscope can make an excellent (discontinuous stream) SDR receiver.

Proposals should be submitted through
https://pretalx.fosdem.org/fosdem-2026/
November 15 at latest, or 2 weeks from now.

See you in Brussels, Jean-Michel

Improper BER running flowgraph example from GNURadio Wiki

Hi all,

I am not sure if this is already discussed or if I am missing something but here is my question - when I run a flowgraph that I put together with the transmitter-receiver example from the Gnuradio Wiki, I get inconsistent BER readouts. BER also seems to change when I change either packet length or the modulation parameters of payload.

The connection between the TX-RX blocks is via a wire and not a channel model, so I assume the BER should be close to nil?

Thanks in advance :)

QT GUI Push Button, QT GUI Toggle Switch, QT GUI LED Indicator, Logical

Hello,

there is a problem with the initialisation of

<QT GUI Toggle Switch>.

In the meantime, I find out self what happens.

The problem is the <QT GUI Toggle Switch>.

The <QT GUI Toggle Switch> is NOT properly initialised

on startup, so it gives an error message

if you reference it in another block for example in

a Boolean expression like x = a | b.

The initialisation of <QT GUI Toggle Switch>

is only done if you activate it the first time.

The you can reference it without problems.

The workaround is, an intermediate variable

between the button and the LED.

See flowgraph.

I think, this must be fix in the future...

(The same problem is also on <QT GUI Check Box>)

 

FOSDEM 2026 (Feb. 1 2026): call for contributions on SDR/DSP (deadline Nov. 15 2025)

The Software Defined Radio/Digital Signal Processing (SDR/DSP) devroom
is being organized for the 2026 FOSDEM held in Brussels (Belgium)
Sunday Feb. 1, 2026.

We are seeking contributions discussing FOSS software for
(radiofrequency) discrete time digital signal processing/software
defined radio (SDR) including digital communication and data integrity
(CRC calculation, Forward Error Correction -- FEC), communication
channel characterization, navigation and positioning, target ranging and
velocity measurement, and signal characteristics extraction from raw IQ
collected from single or multiple antennas, as well as software
frameworks easing such applications including GNU Radio, FutureSDR,
Pothosware or custom frameworks. Novel openhardware description,
possibly including the latest acceleration peripherals including FPGA
and GPUs (or others), is encouraged, especially if using FOSS
frameworks, but maybe also demonstrating how a radiofrequency grade
oscilloscope can make an excellent (discontinuous stream) SDR receiver.

Proposals should be submitted through https://pretalx.fosdem.org by
November 15 at latest, or 2 weeks from now.

See you in Brussels, Jean-Michel

QT GUI Push Button, QT GUI Toggle Switch, QT GUI LED Indicator, Logical problem

Hello,

 

I'm using GnuRadio 3.11 on Ubunu 2025.10

and I run into a logical problem with

 

QT GUI Push Button

QT GUI Toggle Switch

QT GUI LED Indicator

 

I have configured in the LED Indicator block

  state = button | switch

 

With this configuration, the using behaviour

after startup is different for

  a) first button then switch (works fine)

but the sequence

  b) first switch then button (give me an error message)

 

I have isolate this in the flowgraph ButtonAndSwitchTest.grc

I need this to activate something steady or temporarly...

 

Is this a mistake from me?

It seems to be, a problem in the initialisation.

And is there a workaround for that?

 

Thanks