Thursday, November 27, 2025

Re: Discuss-gnuradio Digest, Vol 277, Issue 7

HOW TO UNSUBSCRIBE??

On Thu, Nov 27, 2025 at 10:33 PM <discuss-gnuradio-request@gnu.org> wrote:
Send Discuss-gnuradio mailing list submissions to
        discuss-gnuradio@gnu.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
or, via email, send a message with subject or body 'help' to
        discuss-gnuradio-request@gnu.org

You can reach the person managing the list at
        discuss-gnuradio-owner@gnu.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Discuss-gnuradio digest..."


Today's Topics:

   1. Re: Endian-ness of USRP x410 device (Martin Braun)
   2. Issues with NI / Ettus E320 not faced before on the E310 or
      B210 (Indrajit Bhattacharyya)


----------------------------------------------------------------------

Message: 1
Date: Thu, 27 Nov 2025 11:59:16 +0100
From: Martin Braun <martin.braun@ettus.com>
Cc: discuss-gnuradio@gnu.org
Subject: Re: Endian-ness of USRP x410 device
Message-ID:
        <CAFOi1A7sUW_6SLH8efWmzm-pGXKNgzQJQm1iTkKy_vYamdaWcQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hey Jons,

our mailing list server is having some issues. Our maintainer knows
about this, but I can't give you a timeline for when it'll be up again.

Like Marcus says, don't worry about the network endianness. We have a bunch
of things going on to flip bytes around (among other things, it saves us
some CPU load when receiving data), but you need to worry about the
Noc-Shell interface. I recommend looking at some of our existing blocks as
examples.

--M

On Wed, Nov 26, 2025 at 4:01 PM Marcus Müller <mmueller@gnuradio.org> wrote:

> Hi Jons,
>
> On 2025-11-26 9:17 AM, Jons wrote:
> > Hi all,
> > This is a specific question about USRP devices and I am posting it here
> because I am
> > unable to send it to the usrp-users mail chain.
>
> Uh, I'm not with Ettus anymore, but that's no good. All you should need to
> do is send an
> email from your email address to usrp-users-join@lists.ettus.com ; after
> you've gotten a
> confirmation email and confirmed, you should be able to post there.
>
> > I am trying to integrate a custom noc
> > block into the x410 device and when going through the email archive and
> a doc in the
> > github repo I saw that the OTW data transmission is in Big Endian.
>
> I'll go with: that's a time-honoured tradition :D
>
> > Can someone help me out
> > in understanding how it will affect a noc block?
>
> Not at all – you're not interfacing with the network directly, but with
> your nocshell, and
> your verilog module / VHDL arch sees the sample data as sample-wide array
> (CHDR_W is the
> naming convention for the width parameter, if you want to look through the
> source code of
> Ettus' blocks), typically.
>
> Best,
> Marcus
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20251127/e2312016/attachment.htm>

------------------------------

Message: 2
Date: Thu, 27 Nov 2025 12:26:16 +0000
From: Indrajit Bhattacharyya
        <Indrajit.Bhattacharyya@kratosdefense.com>
To: "discuss-gnuradio@gnu.org" <discuss-gnuradio@gnu.org>
Subject: Issues with NI / Ettus E320 not faced before on the E310 or
        B210
Message-ID:
        <PH1P110MB1156EC1145B632DBF8AA8C8885DFA@PH1P110MB1156.NAMP110.PROD.OUTLOOK.COM>

Content-Type: text/plain; charset="utf-8"

Hello All,



We recently had to upgrade the receivers on our products to the E320 due to
the obsolescence of the E310.



While running the same program on the E320 I observed the following issues:



1.      AD9361 temperature - on the E310, B210 this temperature used to be
around 40 to 45 C, with all channels operating - namely 2 Tx and 2 Rx. MCR
of 16 MHz.
On the E320, the temperature has jumped to 74C when only the Rx channels are
operating, while it goes up to 85C-90C when the Tx channels (i.e. all 4
channels - 2 Tx, 2Rx) are also operating. Is this normal ?
2.      E320 specific issue - when streaming data to the host PC, stopping
the stream during times of inactivity [self.uhd_usrp_source_0.stop()]
actually causes the temperature of the AD9361 to creep up over time.
3.      E320 specific issue - when streaming data, reading of the new set of
mother board sensors available on the E320 (e.g. FPGA temperature, fan,
ref_locked etc) causes the stream to stop, to process the sensor query - is
this normal. This does not happen when processing the AD9361 sensor data.



UHD version 4.8.0.0

GNU Radio version 3.10.12.0

Python 3.12.9



I would love it if it is something I am doing wrong.



All data processing is done on the host, as I understand that the E320 does
not support RFNOC updates with a free licence of Vivaldi (unlike the E310).
So, the E320 is only being used as a layer between the AD9361 and the SFP
module.



Thanks,



Indrajit.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20251127/9bcbe9f6/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6758 bytes
Desc: not available
URL: <https://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20251127/9bcbe9f6/attachment.bin>

------------------------------

Subject: Digest Footer

_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


------------------------------

End of Discuss-gnuradio Digest, Vol 277, Issue 7
************************************************

Issues with NI / Ettus E320 not faced before on the E310 or B210

Hello All,

 

We recently had to upgrade the receivers on our products to the E320 due to the obsolescence of the E310.

 

While running the same program on the E320 I observed the following issues:

 

  1. AD9361 temperature – on the E310, B210 this temperature used to be around 40 to 45 C, with all channels operating – namely 2 Tx and 2 Rx. MCR of 16 MHz.
    On the E320, the temperature has jumped to 74C when only the Rx channels are operating, while it goes up to 85C-90C when the Tx channels (i.e. all 4 channels – 2 Tx, 2Rx) are also operating. Is this normal ?
  2. E320 specific issue – when streaming data to the host PC, stopping the stream during times of inactivity [self.uhd_usrp_source_0.stop()] actually causes the temperature of the AD9361 to creep up over time.
  3. E320 specific issue – when streaming data, reading of the new set of mother board sensors available on the E320 (e.g. FPGA temperature, fan, ref_locked etc) causes the stream to stop, to process the sensor query – is this normal. This does not happen when processing the AD9361 sensor data.

 

UHD version 4.8.0.0

GNU Radio version 3.10.12.0

Python 3.12.9

 

I would love it if it is something I am doing wrong.

 

All data processing is done on the host, as I understand that the E320 does not support RFNOC updates with a free licence of Vivaldi (unlike the E310). So, the E320 is only being used as a layer between the AD9361 and the SFP module.

 

Thanks,

 

Indrajit.

Re: Endian-ness of USRP x410 device

Hey Jons,

our mailing list server is having some issues. Our maintainer knows about this, but I can't give you a timeline for when it'll be up again.

Like Marcus says, don't worry about the network endianness. We have a bunch of things going on to flip bytes around (among other things, it saves us some CPU load when receiving data), but you need to worry about the Noc-Shell interface. I recommend looking at some of our existing blocks as examples.

--M

On Wed, Nov 26, 2025 at 4:01 PM Marcus Müller <mmueller@gnuradio.org> wrote:
Hi Jons,

On 2025-11-26 9:17 AM, Jons wrote:
> Hi all,
> This is a specific question about USRP devices and I am posting it here because I am
> unable to send it to the usrp-users mail chain.

Uh, I'm not with Ettus anymore, but that's no good. All you should need to do is send an
email from your email address to usrp-users-join@lists.ettus.com ; after you've gotten a
confirmation email and confirmed, you should be able to post there.

> I am trying to integrate a custom noc
> block into the x410 device and when going through the email archive and a doc in the
> github repo I saw that the OTW data transmission is in Big Endian.

I'll go with: that's a time-honoured tradition :D

> Can someone help me out
> in understanding how it will affect a noc block?

Not at all – you're not interfacing with the network directly, but with your nocshell, and
your verilog module / VHDL arch sees the sample data as sample-wide array (CHDR_W is the
naming convention for the width parameter, if you want to look through the source code of
Ettus' blocks), typically.

Best,
Marcus

Wednesday, November 26, 2025

Re: Endian-ness of USRP x410 device

Hi Jons,

On 2025-11-26 9:17 AM, Jons wrote:
> Hi all,
> This is a specific question about USRP devices and I am posting it here because I am
> unable to send it to the usrp-users mail chain.

Uh, I'm not with Ettus anymore, but that's no good. All you should need to do is send an
email from your email address to usrp-users-join@lists.ettus.com ; after you've gotten a
confirmation email and confirmed, you should be able to post there.

> I am trying to integrate a custom noc
> block into the x410 device and when going through the email archive and a doc in the
> github repo I saw that the OTW data transmission is in Big Endian.

I'll go with: that's a time-honoured tradition :D

> Can someone help me out
> in understanding how it will affect a noc block?

Not at all – you're not interfacing with the network directly, but with your nocshell, and
your verilog module / VHDL arch sees the sample data as sample-wide array (CHDR_W is the
naming convention for the width parameter, if you want to look through the source code of
Ettus' blocks), typically.

Best,
Marcus

Endian-ness of USRP x410 device

Hi all,
This is a specific question about USRP devices and I am posting it here because I am unable to send it to the usrp-users mail chain. I am trying to integrate a custom noc block into the x410 device and when going through the email archive and a doc in the github repo I saw that the OTW data transmission is in Big Endian. Can someone help me out in understanding how it will affect a noc block? will the CHDR packets be in BE format and should I be accounting for this change by repacking the bits before processing? I was initially of the impression that it would be Little Endian throughout.
I am using the Simple AXI-Stream Data protocol for streaming.

Thank you for the help :)

Monday, November 17, 2025

IQ Correction Manual Offset isn't working

I am attempting to use the IQ correction to correct for images in my project. Specifically for the attached flowgraph I want to replace the scheme I now have in place using the 3 Multiply Constant blocks and the Add block. This scheme results in am image that is –44 dBc down. Uncorrected the image is –20dBc.
 
I tried using the IQ Correction block but nothing changed from the uncorrected image. I tried small values for the correction such as I am now using. When that didn't improve things. I tried increasingly larger values.
 
Nothing changed.
 
What am I doing wrong?
 
Jim Elmore

Virus-free.www.avg.com

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