usrp-users@lists.ettus.com
Discussion and technical support related to USRP, UHD, RFNoC
View all threadsToo Many Samples in a Single Burst
Hello,
In trying to test the ‘rx_multi_samples’ example with all four channels on an n310. I run into an error of “Requesting too many samples in a single burst” when I attempt a longer record (really anything over a few seconds). Seems to be my nsamps value, but I am unsure how to remedy the issue. Below is my argument and the terminal output for an attempt to receive for 10 seconds:
./rx_multi_samples --args "type=n3xx,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo" --rate 6.25e6 --subdev "A:0 A:1 B:0 B:1" --channels "0,1,2,3" --nsamps 625000000
Creating the usrp device with: type=n3xx,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo...
[INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501; UHD_3.15.0.HEAD-0-gaea0e2de
[INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=192.168.10.2,type=n3xx,product=n310,serial=3218B5F,claimed=False,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo
[INFO] [MPM.PeriphManager] init() called with device args `clock_source=gpsdo,time_source=gpsdo,product=n310,mgmt_addr=192.168.10.2'.
[INFO] [0/Replay_0] Initializing block control (NOC ID: 0x4E91A00000000004)
[INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/FIFO_0] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_1] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_2] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_3] Initializing block control (NOC ID: 0xF1F0000000000000)
Using Device: Single USRP:
Device: N300-Series Device
Mboard 0: ni-n3xx-3218B5F
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 1
RX DSP: 1
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 2
RX DSP: 0
RX Dboard: B
RX Subdev: Magnesium
RX Channel: 3
RX DSP: 1
RX Dboard: B
RX Subdev: Magnesium
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 1
TX DSP: 1
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 2
TX DSP: 0
TX Dboard: B
TX Subdev: Magnesium
TX Channel: 3
TX DSP: 1
TX Dboard: B
TX Subdev: Magnesium
Setting RX Rate: 6.250000 Msps...
Actual RX Rate: 6.250000 Msps...
Setting device timestamp to 0...
Begin streaming 625000000 samples, 1.500000 seconds in the future...
[ERROR] [RFNOC RADIO] Requesting too many samples in a single burst! Requested 12500000000, maximum is 268435455.
[INFO] [RFNOC RADIO] Note that a decimation block will increase the number of samples per burst by the decimation factor. Your application may have requested fewer samples.
Error: ValueError: Requested too many samples in a single burst.
Thanks,
Jonathan
On 08/06/2021 07:26 PM, Jonathan Tobin wrote:
Hello,
In trying to test the ‘rx_multi_samples’ example with all four
channels on an n310. I run into an error of “Requesting too many
samples in a single burst” when I attempt a longer record (really
anything over a few seconds). Seems to be my nsamps value, but I am
unsure how to remedy the issue. Below is my argument and the terminal
output for an attempt to receive for 10 seconds:
./rx_multi_samples --args
"type=n3xx,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo"
--rate 6.25e6 --subdev "A:0 A:1 B:0 B:1" --channels "0,1,2,3" --nsamps
625000000
Creating the usrp device with:
type=n3xx,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo...
[INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501;
UHD_3.15.0.HEAD-0-gaea0e2de
[INFO] [MPMD] Initializing 1 device(s) in parallel with args:
mgmt_addr=192.168.10.2,type=n3xx,product=n310,serial=3218B5F,claimed=False,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo
[INFO] [MPM.PeriphManager] init() called with device args
`clock_source=gpsdo,time_source=gpsdo,product=n310,mgmt_addr=192.168.10.2'.
[INFO] [0/Replay_0] Initializing block control (NOC ID:
0x4E91A00000000004)
[INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/FIFO_0] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_1] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_2] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_3] Initializing block control (NOC ID: 0xF1F0000000000000)
Using Device: Single USRP:
Device: N300-Series Device
Mboard 0: ni-n3xx-3218B5F
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 1
RX DSP: 1
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 2
RX DSP: 0
RX Dboard: B
RX Subdev: Magnesium
RX Channel: 3
RX DSP: 1
RX Dboard: B
RX Subdev: Magnesium
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 1
TX DSP: 1
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 2
TX DSP: 0
TX Dboard: B
TX Subdev: Magnesium
TX Channel: 3
TX DSP: 1
TX Dboard: B
TX Subdev: Magnesium
Setting RX Rate: 6.250000 Msps...
Actual RX Rate: 6.250000 Msps...
Setting device timestamp to 0...
Begin streaming 625000000 samples, 1.500000 seconds in the future...
[ERROR] [RFNOC RADIO] Requesting too many samples in a single burst!
Requested 12500000000, maximum is 268435455.
[INFO] [RFNOC RADIO] Note that a decimation block will increase the
number of samples per burst by the decimation factor. Your application
may have requested fewer samples.
Error: ValueError: Requested too many samples in a single burst.
Thanks,
Jonathan
That looks like a bug--have you tried this on UHD 4.recent?
Hi Marcus,
No, I have not attempted on UHD 4+. Due to some other software constraints I am only able to use 3.15 at the moment.
Thanks,
Jonathan
From: Marcus D. Leech patchvonbraun@gmail.com
Sent: Friday, August 6, 2021 3:56 PM
To: usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: [USRP-users] Re: Too Many Samples in a Single Burst
On 08/06/2021 07:26 PM, Jonathan Tobin wrote:
Hello,
In trying to test the ‘rx_multi_samples’ example with all four channels on an n310. I run into an error of “Requesting too many samples in a single burst” when I attempt a longer record (really anything over a few seconds). Seems to be my nsamps value, but I am unsure how to remedy the issue. Below is my argument and the terminal output for an attempt to receive for 10 seconds:
./rx_multi_samples --args "type=n3xx,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo" --rate 6.25e6 --subdev "A:0 A:1 B:0 B:1" --channels "0,1,2,3" --nsamps 625000000
Creating the usrp device with: type=n3xx,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo...
[INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501; UHD_3.15.0.HEAD-0-gaea0e2de
[INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=192.168.10.2,type=n3xx,product=n310,serial=3218B5F,claimed=False,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo
[INFO] [MPM.PeriphManager] init() called with device args `clock_source=gpsdo,time_source=gpsdo,product=n310,mgmt_addr=192.168.10.2'.
[INFO] [0/Replay_0] Initializing block control (NOC ID: 0x4E91A00000000004)
[INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/FIFO_0] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_1] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_2] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_3] Initializing block control (NOC ID: 0xF1F0000000000000)
Using Device: Single USRP:
Device: N300-Series Device
Mboard 0: ni-n3xx-3218B5F
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 1
RX DSP: 1
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 2
RX DSP: 0
RX Dboard: B
RX Subdev: Magnesium
RX Channel: 3
RX DSP: 1
RX Dboard: B
RX Subdev: Magnesium
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 1
TX DSP: 1
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 2
TX DSP: 0
TX Dboard: B
TX Subdev: Magnesium
TX Channel: 3
TX DSP: 1
TX Dboard: B
TX Subdev: Magnesium
Setting RX Rate: 6.250000 Msps...
Actual RX Rate: 6.250000 Msps...
Setting device timestamp to 0...
Begin streaming 625000000 samples, 1.500000 seconds in the future...
[ERROR] [RFNOC RADIO] Requesting too many samples in a single burst! Requested 12500000000, maximum is 268435455.
[INFO] [RFNOC RADIO] Note that a decimation block will increase the number of samples per burst by the decimation factor. Your application may have requested fewer samples.
Error: ValueError: Requested too many samples in a single burst.
Thanks,
Jonathan
That looks like a bug--have you tried this on UHD 4.recent?
On 08/06/2021 10:47 PM, Jonathan Tobin wrote:
Hi Marcus,
No, I have not attempted on UHD 4+. Due to some other software
constraints I am only able to use 3.15 at the moment.
Thanks,
Jonathan
Does reducing nsamps help? What about channel count?
Just looking for clues as to what might be going on. Looking at the
code, nothing really leaps out at me. You're using rx_multi_samples
"out of the box" or with modifications?
From: Marcus D. Leech patchvonbraun@gmail.com
Sent: Friday, August 6, 2021 3:56 PM
To: usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: [USRP-users] Re: Too Many Samples in a Single Burst
On 08/06/2021 07:26 PM, Jonathan Tobin wrote:
Hello,
In trying to test the ‘rx_multi_samples’ example with all four
channels on an n310. I run into an error of “Requesting too many
samples in a single burst” when I attempt a longer record (really
anything over a few seconds). Seems to be my nsamps value, but I am
unsure how to remedy the issue. Below is my argument and the terminal
output for an attempt to receive for 10 seconds:
./rx_multi_samples --args
"type=n3xx,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo"
--rate 6.25e6 --subdev "A:0 A:1 B:0 B:1" --channels "0,1,2,3"
--nsamps 625000000
Creating the usrp device with:
type=n3xx,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo...
[INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501;
UHD_3.15.0.HEAD-0-gaea0e2de
[INFO] [MPMD] Initializing 1 device(s) in parallel with args:
mgmt_addr=192.168.10.2,type=n3xx,product=n310,serial=3218B5F,claimed=False,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo
[INFO] [MPM.PeriphManager] init() called with device args
`clock_source=gpsdo,time_source=gpsdo,product=n310,mgmt_addr=192.168.10.2'.
[INFO] [0/Replay_0] Initializing block control (NOC ID:
0x4E91A00000000004)
[INFO] [0/Radio_0] Initializing block control (NOC ID:
0x12AD100000011312)
[INFO] [0/Radio_1] Initializing block control (NOC ID:
0x12AD100000011312)
[INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/FIFO_0] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_1] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_2] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_3] Initializing block control (NOC ID: 0xF1F0000000000000)
Using Device: Single USRP:
Device: N300-Series Device
Mboard 0: ni-n3xx-3218B5F
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 1
RX DSP: 1
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 2
RX DSP: 0
RX Dboard: B
RX Subdev: Magnesium
RX Channel: 3
RX DSP: 1
RX Dboard: B
RX Subdev: Magnesium
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 1
TX DSP: 1
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 2
TX DSP: 0
TX Dboard: B
TX Subdev: Magnesium
TX Channel: 3
TX DSP: 1
TX Dboard: B
TX Subdev: Magnesium
Setting RX Rate: 6.250000 Msps...
Actual RX Rate: 6.250000 Msps...
Setting device timestamp to 0...
Begin streaming 625000000 samples, 1.500000 seconds in the future...
[ERROR] [RFNOC RADIO] Requesting too many samples in a single burst!
Requested 12500000000, maximum is 268435455.
[INFO] [RFNOC RADIO] Note that a decimation block will increase the
number of samples per burst by the decimation factor. Your
application may have requested fewer samples.
Error: ValueError: Requested too many samples in a single burst.
Thanks,
Jonathan
That looks like a bug--have you tried this on UHD 4.recent?
Reducing nsamps to below 268435455/2 works - but at 6.25Msps for all four channels (two daughterboards) this is very short amount of time. I can try changing channels but for my application I do need all four channels receiving - though this will have to be on Monday.
Yes, rx_multi_samples "out of the box" (no modifications to the example).
Thanks,
Jonathan
From: Marcus D. Leech patchvonbraun@gmail.com
Sent: Saturday, August 7, 2021 5:30 AM
To: Jonathan Tobin Tobin@augustusaero.com; usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Too Many Samples in a Single Burst
On 08/06/2021 10:47 PM, Jonathan Tobin wrote:
Hi Marcus,
No, I have not attempted on UHD 4+. Due to some other software constraints I am only able to use 3.15 at the moment.
Thanks,
Jonathan
Does reducing nsamps help? What about channel count?
Just looking for clues as to what might be going on. Looking at the code, nothing really leaps out at me. You're using rx_multi_samples
"out of the box" or with modifications?
From: Marcus D. Leech patchvonbraun@gmail.commailto:patchvonbraun@gmail.com
Sent: Friday, August 6, 2021 3:56 PM
To: usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: [USRP-users] Re: Too Many Samples in a Single Burst
On 08/06/2021 07:26 PM, Jonathan Tobin wrote:
Hello,
In trying to test the ‘rx_multi_samples’ example with all four channels on an n310. I run into an error of “Requesting too many samples in a single burst” when I attempt a longer record (really anything over a few seconds). Seems to be my nsamps value, but I am unsure how to remedy the issue. Below is my argument and the terminal output for an attempt to receive for 10 seconds:
./rx_multi_samples --args "type=n3xx,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo" --rate 6.25e6 --subdev "A:0 A:1 B:0 B:1" --channels "0,1,2,3" --nsamps 625000000
Creating the usrp device with: type=n3xx,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo...
[INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501; UHD_3.15.0.HEAD-0-gaea0e2de
[INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=192.168.10.2,type=n3xx,product=n310,serial=3218B5F,claimed=False,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo
[INFO] [MPM.PeriphManager] init() called with device args `clock_source=gpsdo,time_source=gpsdo,product=n310,mgmt_addr=192.168.10.2'.
[INFO] [0/Replay_0] Initializing block control (NOC ID: 0x4E91A00000000004)
[INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/FIFO_0] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_1] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_2] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_3] Initializing block control (NOC ID: 0xF1F0000000000000)
Using Device: Single USRP:
Device: N300-Series Device
Mboard 0: ni-n3xx-3218B5F
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 1
RX DSP: 1
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 2
RX DSP: 0
RX Dboard: B
RX Subdev: Magnesium
RX Channel: 3
RX DSP: 1
RX Dboard: B
RX Subdev: Magnesium
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 1
TX DSP: 1
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 2
TX DSP: 0
TX Dboard: B
TX Subdev: Magnesium
TX Channel: 3
TX DSP: 1
TX Dboard: B
TX Subdev: Magnesium
Setting RX Rate: 6.250000 Msps...
Actual RX Rate: 6.250000 Msps...
Setting device timestamp to 0...
Begin streaming 625000000 samples, 1.500000 seconds in the future...
[ERROR] [RFNOC RADIO] Requesting too many samples in a single burst! Requested 12500000000, maximum is 268435455.
[INFO] [RFNOC RADIO] Note that a decimation block will increase the number of samples per burst by the decimation factor. Your application may have requested fewer samples.
Error: ValueError: Requested too many samples in a single burst.
Thanks,
Jonathan
That looks like a bug--have you tried this on UHD 4.recent?
On 08/07/2021 12:23 PM, Jonathan Tobin wrote:
Reducing nsamps to below 268435455/2 works - but at 6.25Msps for all
four channels (two daughterboards) this is very short amount of time.
I can try changing channels but for my application I do need all four
channels receiving - though this will have to be on Monday.
Yes, rx_multi_samples "out of the box" (no modifications to the example).
Thanks,
Jonathan
Given that rx_multi_samples doesn't actually DO anything with the
samples, I'm curious about how it's actually useful for you in any
production sense--it is just a demo app to show some of the API usage.
It may be the case that this example needs to be updated because it's
mis-using the API in some what that isn't immediately obvious to me.
But again, it doesn't actually DO anything with the samples, so I
don't know how it's useful other than as a learning tool...
From: Marcus D. Leech patchvonbraun@gmail.com
Sent: Saturday, August 7, 2021 5:30 AM
To: Jonathan Tobin Tobin@augustusaero.com;
usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Too Many Samples in a Single Burst
On 08/06/2021 10:47 PM, Jonathan Tobin wrote:
Hi Marcus,
No, I have not attempted on UHD 4+. Due to some other software
constraints I am only able to use 3.15 at the moment.
Thanks,
Jonathan
Does reducing nsamps help? What about channel count?
Just looking for clues as to what might be going on. Looking at the
code, nothing really leaps out at me. You're using rx_multi_samples
"out of the box" or with modifications?
From: Marcus D. Leech patchvonbraun@gmail.com
mailto:patchvonbraun@gmail.com
Sent: Friday, August 6, 2021 3:56 PM
To: usrp-users@lists.ettus.com mailto:usrp-users@lists.ettus.com
usrp-users@lists.ettus.com mailto:usrp-users@lists.ettus.com
Subject: [USRP-users] Re: Too Many Samples in a Single Burst
On 08/06/2021 07:26 PM, Jonathan Tobin wrote:
Hello,
In trying to test the ‘rx_multi_samples’ example with all four
channels on an n310. I run into an error of “Requesting too many
samples in a single burst” when I attempt a longer record (really
anything over a few seconds). Seems to be my nsamps value, but I am
unsure how to remedy the issue. Below is my argument and the
terminal output for an attempt to receive for 10 seconds:
./rx_multi_samples --args
"type=n3xx,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo"
--rate 6.25e6 --subdev "A:0 A:1 B:0 B:1" --channels "0,1,2,3"
--nsamps 625000000
Creating the usrp device with:
type=n3xx,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo...
[INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501;
UHD_3.15.0.HEAD-0-gaea0e2de
[INFO] [MPMD] Initializing 1 device(s) in parallel with args:
mgmt_addr=192.168.10.2,type=n3xx,product=n310,serial=3218B5F,claimed=False,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo
[INFO] [MPM.PeriphManager] init() called with device args
`clock_source=gpsdo,time_source=gpsdo,product=n310,mgmt_addr=192.168.10.2'.
[INFO] [0/Replay_0] Initializing block control (NOC ID:
0x4E91A00000000004)
[INFO] [0/Radio_0] Initializing block control (NOC ID:
0x12AD100000011312)
[INFO] [0/Radio_1] Initializing block control (NOC ID:
0x12AD100000011312)
[INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/FIFO_0] Initializing block control (NOC ID:
0xF1F0000000000000)
[INFO] [0/FIFO_1] Initializing block control (NOC ID:
0xF1F0000000000000)
[INFO] [0/FIFO_2] Initializing block control (NOC ID:
0xF1F0000000000000)
[INFO] [0/FIFO_3] Initializing block control (NOC ID:
0xF1F0000000000000)
Using Device: Single USRP:
Device: N300-Series Device
Mboard 0: ni-n3xx-3218B5F
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 1
RX DSP: 1
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 2
RX DSP: 0
RX Dboard: B
RX Subdev: Magnesium
RX Channel: 3
RX DSP: 1
RX Dboard: B
RX Subdev: Magnesium
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 1
TX DSP: 1
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 2
TX DSP: 0
TX Dboard: B
TX Subdev: Magnesium
TX Channel: 3
TX DSP: 1
TX Dboard: B
TX Subdev: Magnesium
Setting RX Rate: 6.250000 Msps...
Actual RX Rate: 6.250000 Msps...
Setting device timestamp to 0...
Begin streaming 625000000 samples, 1.500000 seconds in the future...
[ERROR] [RFNOC RADIO] Requesting too many samples in a single burst!
Requested 12500000000, maximum is 268435455.
[INFO] [RFNOC RADIO] Note that a decimation block will increase the
number of samples per burst by the decimation factor. Your
application may have requested fewer samples.
Error: ValueError: Requested too many samples in a single burst.
Thanks,
Jonathan
That looks like a bug--have you tried this on UHD 4.recent?
I was just using it more as an example. The same error occurs when using txrx_loopback_to_file - but I can provide that output and more info on that come Monday.
Thanks,
Jonathan
From: Marcus D. Leech patchvonbraun@gmail.com
Sent: Saturday, August 7, 2021 7:16 AM
To: Jonathan Tobin Tobin@augustusaero.com; usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Too Many Samples in a Single Burst
On 08/07/2021 12:23 PM, Jonathan Tobin wrote:
Reducing nsamps to below 268435455/2 works - but at 6.25Msps for all four channels (two daughterboards) this is very short amount of time. I can try changing channels but for my application I do need all four channels receiving - though this will have to be on Monday.
Yes, rx_multi_samples "out of the box" (no modifications to the example).
Thanks,
Jonathan
Given that rx_multi_samples doesn't actually DO anything with the samples, I'm curious about how it's actually useful for you in any
production sense--it is just a demo app to show some of the API usage.
It may be the case that this example needs to be updated because it's mis-using the API in some what that isn't immediately obvious to me.
But again, it doesn't actually DO anything with the samples, so I don't know how it's useful other than as a learning tool...
From: Marcus D. Leech patchvonbraun@gmail.commailto:patchvonbraun@gmail.com
Sent: Saturday, August 7, 2021 5:30 AM
To: Jonathan Tobin Tobin@augustusaero.commailto:Tobin@augustusaero.com; usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Too Many Samples in a Single Burst
On 08/06/2021 10:47 PM, Jonathan Tobin wrote:
Hi Marcus,
No, I have not attempted on UHD 4+. Due to some other software constraints I am only able to use 3.15 at the moment.
Thanks,
Jonathan
Does reducing nsamps help? What about channel count?
Just looking for clues as to what might be going on. Looking at the code, nothing really leaps out at me. You're using rx_multi_samples
"out of the box" or with modifications?
From: Marcus D. Leech patchvonbraun@gmail.commailto:patchvonbraun@gmail.com
Sent: Friday, August 6, 2021 3:56 PM
To: usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: [USRP-users] Re: Too Many Samples in a Single Burst
On 08/06/2021 07:26 PM, Jonathan Tobin wrote:
Hello,
In trying to test the ‘rx_multi_samples’ example with all four channels on an n310. I run into an error of “Requesting too many samples in a single burst” when I attempt a longer record (really anything over a few seconds). Seems to be my nsamps value, but I am unsure how to remedy the issue. Below is my argument and the terminal output for an attempt to receive for 10 seconds:
./rx_multi_samples --args "type=n3xx,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo" --rate 6.25e6 --subdev "A:0 A:1 B:0 B:1" --channels "0,1,2,3" --nsamps 625000000
Creating the usrp device with: type=n3xx,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo...
[INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501; UHD_3.15.0.HEAD-0-gaea0e2de
[INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=192.168.10.2,type=n3xx,product=n310,serial=3218B5F,claimed=False,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo
[INFO] [MPM.PeriphManager] init() called with device args `clock_source=gpsdo,time_source=gpsdo,product=n310,mgmt_addr=192.168.10.2'.
[INFO] [0/Replay_0] Initializing block control (NOC ID: 0x4E91A00000000004)
[INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/FIFO_0] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_1] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_2] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_3] Initializing block control (NOC ID: 0xF1F0000000000000)
Using Device: Single USRP:
Device: N300-Series Device
Mboard 0: ni-n3xx-3218B5F
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 1
RX DSP: 1
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 2
RX DSP: 0
RX Dboard: B
RX Subdev: Magnesium
RX Channel: 3
RX DSP: 1
RX Dboard: B
RX Subdev: Magnesium
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 1
TX DSP: 1
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 2
TX DSP: 0
TX Dboard: B
TX Subdev: Magnesium
TX Channel: 3
TX DSP: 1
TX Dboard: B
TX Subdev: Magnesium
Setting RX Rate: 6.250000 Msps...
Actual RX Rate: 6.250000 Msps...
Setting device timestamp to 0...
Begin streaming 625000000 samples, 1.500000 seconds in the future...
[ERROR] [RFNOC RADIO] Requesting too many samples in a single burst! Requested 12500000000, maximum is 268435455.
[INFO] [RFNOC RADIO] Note that a decimation block will increase the number of samples per burst by the decimation factor. Your application may have requested fewer samples.
Error: ValueError: Requested too many samples in a single burst.
Thanks,
Jonathan
That looks like a bug--have you tried this on UHD 4.recent?
Hi Marcus,
Here is the output from a simple run of txrx_loopback_to_file "out of the box." As can be seen, the same error occurs (along with dropped packets this time).
./txrx_loopback_to_file --tx-args "addr=192.168.10.2" --rx-args "type=n3xx,addr=192.168.10.2,time_source=internal,clock_source=internal" --rx-freq 2500e6 --rx-rate 6.25e6 --rx-subdev "A:0 A:1 B:0 B:1" --rx-channels "0,1,2,3" --rx-gain 60 --nsamps 62500000 --tx-rate 6.25e6 --tx-freq 2500e6
Creating the transmit usrp device with: addr=192.168.10.2...
[INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501; UHD_3.15.0.HEAD-0-gaea0e2de
[INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=192.168.10.2,type=n3xx,product=n310,serial=3218B5F,claimed=False,addr=192.168.10.2
[INFO] [MPM.PeriphManager] init() called with device args `product=n310,mgmt_addr=192.168.10.2,time_source=internal,clock_source=internal'.
[INFO] [0/Replay_0] Initializing block control (NOC ID: 0x4E91A00000000004)
[INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/FIFO_0] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_1] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_2] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_3] Initializing block control (NOC ID: 0xF1F0000000000000)
Creating the receive usrp device with: type=n3xx,addr=192.168.10.2,time_source=internal,clock_source=internal...
Using TX Device: Single USRP:
Device: N300-Series Device
Mboard 0: ni-n3xx-3218B5F
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 1
RX DSP: 1
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 2
RX DSP: 0
RX Dboard: B
RX Subdev: Magnesium
RX Channel: 3
RX DSP: 1
RX Dboard: B
RX Subdev: Magnesium
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 1
TX DSP: 1
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 2
TX DSP: 0
TX Dboard: B
TX Subdev: Magnesium
TX Channel: 3
TX DSP: 1
TX Dboard: B
TX Subdev: Magnesium
Using RX Device: Single USRP:
Device: N300-Series Device
Mboard 0: ni-n3xx-3218B5F
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 1
RX DSP: 1
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 2
RX DSP: 0
RX Dboard: B
RX Subdev: Magnesium
RX Channel: 3
RX DSP: 1
RX Dboard: B
RX Subdev: Magnesium
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 1
TX DSP: 1
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 2
TX DSP: 0
TX Dboard: B
TX Subdev: Magnesium
TX Channel: 3
TX DSP: 1
TX Dboard: B
TX Subdev: Magnesium
Setting TX Rate: 6.250000 Msps...
Actual TX Rate: 6.250000 Msps...
Setting RX Rate: 6.250000 Msps...
Actual RX Rate: 6.250000 Msps...
Setting TX Freq: 2500.000000 MHz...
Actual TX Freq: 2500.000000 MHz...
Configuring RX Channel 0
Setting RX Freq: 2500.000000 MHz...
Actual RX Freq: 2500.000000 MHz...
Setting RX Gain: 60.000000 dB...
Actual RX Gain: 60.000000 dB...
Configuring RX Channel 1
Setting RX Freq: 2500.000000 MHz...
Actual RX Freq: 2500.000000 MHz...
Setting RX Gain: 60.000000 dB...
Actual RX Gain: 60.000000 dB...
Configuring RX Channel 2
Setting RX Freq: 2500.000000 MHz...
Actual RX Freq: 2500.000000 MHz...
Setting RX Gain: 60.000000 dB...
Actual RX Gain: 60.000000 dB...
Configuring RX Channel 3
Setting RX Freq: 2500.000000 MHz...
Actual RX Freq: 2500.000000 MHz...
Setting RX Gain: 60.000000 dB...
Actual RX Gain: 60.000000 dB...
Checking TX: all_los: locked ...
Checking RX: all_los: locked ...
Setting device timestamp to 0...
[ERROR] [RFNOC RADIO] Requesting too many samples in a single burst! Requested 1250000000, maximum is 268435455.
[INFO] [RFNOC RADIO] Note that a decimation block will increase the number of samples per burst by the decimation factor. Your application may have requested fewer samples.
LLLLLLLLLLLLLLLLLLLError: ValueError: Requested too many samples in a single burst.
Thanks,
Jonathan
From: Marcus D. Leech patchvonbraun@gmail.com
Sent: Saturday, August 7, 2021 7:16 AM
To: Jonathan Tobin Tobin@augustusaero.com; usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Too Many Samples in a Single Burst
On 08/07/2021 12:23 PM, Jonathan Tobin wrote:
Reducing nsamps to below 268435455/2 works - but at 6.25Msps for all four channels (two daughterboards) this is very short amount of time. I can try changing channels but for my application I do need all four channels receiving - though this will have to be on Monday.
Yes, rx_multi_samples "out of the box" (no modifications to the example).
Thanks,
Jonathan
Given that rx_multi_samples doesn't actually DO anything with the samples, I'm curious about how it's actually useful for you in any
production sense--it is just a demo app to show some of the API usage.
It may be the case that this example needs to be updated because it's mis-using the API in some what that isn't immediately obvious to me.
But again, it doesn't actually DO anything with the samples, so I don't know how it's useful other than as a learning tool...
From: Marcus D. Leech patchvonbraun@gmail.commailto:patchvonbraun@gmail.com
Sent: Saturday, August 7, 2021 5:30 AM
To: Jonathan Tobin Tobin@augustusaero.commailto:Tobin@augustusaero.com; usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Too Many Samples in a Single Burst
On 08/06/2021 10:47 PM, Jonathan Tobin wrote:
Hi Marcus,
No, I have not attempted on UHD 4+. Due to some other software constraints I am only able to use 3.15 at the moment.
Thanks,
Jonathan
Does reducing nsamps help? What about channel count?
Just looking for clues as to what might be going on. Looking at the code, nothing really leaps out at me. You're using rx_multi_samples
"out of the box" or with modifications?
From: Marcus D. Leech patchvonbraun@gmail.commailto:patchvonbraun@gmail.com
Sent: Friday, August 6, 2021 3:56 PM
To: usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: [USRP-users] Re: Too Many Samples in a Single Burst
On 08/06/2021 07:26 PM, Jonathan Tobin wrote:
Hello,
In trying to test the ‘rx_multi_samples’ example with all four channels on an n310. I run into an error of “Requesting too many samples in a single burst” when I attempt a longer record (really anything over a few seconds). Seems to be my nsamps value, but I am unsure how to remedy the issue. Below is my argument and the terminal output for an attempt to receive for 10 seconds:
./rx_multi_samples --args "type=n3xx,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo" --rate 6.25e6 --subdev "A:0 A:1 B:0 B:1" --channels "0,1,2,3" --nsamps 625000000
Creating the usrp device with: type=n3xx,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo...
[INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501; UHD_3.15.0.HEAD-0-gaea0e2de
[INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=192.168.10.2,type=n3xx,product=n310,serial=3218B5F,claimed=False,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo
[INFO] [MPM.PeriphManager] init() called with device args `clock_source=gpsdo,time_source=gpsdo,product=n310,mgmt_addr=192.168.10.2'.
[INFO] [0/Replay_0] Initializing block control (NOC ID: 0x4E91A00000000004)
[INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/FIFO_0] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_1] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_2] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_3] Initializing block control (NOC ID: 0xF1F0000000000000)
Using Device: Single USRP:
Device: N300-Series Device
Mboard 0: ni-n3xx-3218B5F
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 1
RX DSP: 1
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 2
RX DSP: 0
RX Dboard: B
RX Subdev: Magnesium
RX Channel: 3
RX DSP: 1
RX Dboard: B
RX Subdev: Magnesium
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 1
TX DSP: 1
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 2
TX DSP: 0
TX Dboard: B
TX Subdev: Magnesium
TX Channel: 3
TX DSP: 1
TX Dboard: B
TX Subdev: Magnesium
Setting RX Rate: 6.250000 Msps...
Actual RX Rate: 6.250000 Msps...
Setting device timestamp to 0...
Begin streaming 625000000 samples, 1.500000 seconds in the future...
[ERROR] [RFNOC RADIO] Requesting too many samples in a single burst! Requested 12500000000, maximum is 268435455.
[INFO] [RFNOC RADIO] Note that a decimation block will increase the number of samples per burst by the decimation factor. Your application may have requested fewer samples.
Error: ValueError: Requested too many samples in a single burst.
Thanks,
Jonathan
That looks like a bug--have you tried this on UHD 4.recent?
Meant late packets.
From: Jonathan Tobin Tobin@augustusaero.com
Sent: Monday, August 9, 2021 5:41 AM
To: Marcus D. Leech patchvonbraun@gmail.com; usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Too Many Samples in a Single Burst
Hi Marcus,
Here is the output from a simple run of txrx_loopback_to_file "out of the box." As can be seen, the same error occurs (along with dropped packets this time).
./txrx_loopback_to_file --tx-args "addr=192.168.10.2" --rx-args "type=n3xx,addr=192.168.10.2,time_source=internal,clock_source=internal" --rx-freq 2500e6 --rx-rate 6.25e6 --rx-subdev "A:0 A:1 B:0 B:1" --rx-channels "0,1,2,3" --rx-gain 60 --nsamps 62500000 --tx-rate 6.25e6 --tx-freq 2500e6
Creating the transmit usrp device with: addr=192.168.10.2...
[INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501; UHD_3.15.0.HEAD-0-gaea0e2de
[INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=192.168.10.2,type=n3xx,product=n310,serial=3218B5F,claimed=False,addr=192.168.10.2
[INFO] [MPM.PeriphManager] init() called with device args `product=n310,mgmt_addr=192.168.10.2,time_source=internal,clock_source=internal'.
[INFO] [0/Replay_0] Initializing block control (NOC ID: 0x4E91A00000000004)
[INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/FIFO_0] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_1] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_2] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_3] Initializing block control (NOC ID: 0xF1F0000000000000)
Creating the receive usrp device with: type=n3xx,addr=192.168.10.2,time_source=internal,clock_source=internal...
Using TX Device: Single USRP:
Device: N300-Series Device
Mboard 0: ni-n3xx-3218B5F
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 1
RX DSP: 1
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 2
RX DSP: 0
RX Dboard: B
RX Subdev: Magnesium
RX Channel: 3
RX DSP: 1
RX Dboard: B
RX Subdev: Magnesium
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 1
TX DSP: 1
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 2
TX DSP: 0
TX Dboard: B
TX Subdev: Magnesium
TX Channel: 3
TX DSP: 1
TX Dboard: B
TX Subdev: Magnesium
Using RX Device: Single USRP:
Device: N300-Series Device
Mboard 0: ni-n3xx-3218B5F
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 1
RX DSP: 1
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 2
RX DSP: 0
RX Dboard: B
RX Subdev: Magnesium
RX Channel: 3
RX DSP: 1
RX Dboard: B
RX Subdev: Magnesium
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 1
TX DSP: 1
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 2
TX DSP: 0
TX Dboard: B
TX Subdev: Magnesium
TX Channel: 3
TX DSP: 1
TX Dboard: B
TX Subdev: Magnesium
Setting TX Rate: 6.250000 Msps...
Actual TX Rate: 6.250000 Msps...
Setting RX Rate: 6.250000 Msps...
Actual RX Rate: 6.250000 Msps...
Setting TX Freq: 2500.000000 MHz...
Actual TX Freq: 2500.000000 MHz...
Configuring RX Channel 0
Setting RX Freq: 2500.000000 MHz...
Actual RX Freq: 2500.000000 MHz...
Setting RX Gain: 60.000000 dB...
Actual RX Gain: 60.000000 dB...
Configuring RX Channel 1
Setting RX Freq: 2500.000000 MHz...
Actual RX Freq: 2500.000000 MHz...
Setting RX Gain: 60.000000 dB...
Actual RX Gain: 60.000000 dB...
Configuring RX Channel 2
Setting RX Freq: 2500.000000 MHz...
Actual RX Freq: 2500.000000 MHz...
Setting RX Gain: 60.000000 dB...
Actual RX Gain: 60.000000 dB...
Configuring RX Channel 3
Setting RX Freq: 2500.000000 MHz...
Actual RX Freq: 2500.000000 MHz...
Setting RX Gain: 60.000000 dB...
Actual RX Gain: 60.000000 dB...
Checking TX: all_los: locked ...
Checking RX: all_los: locked ...
Setting device timestamp to 0...
[ERROR] [RFNOC RADIO] Requesting too many samples in a single burst! Requested 1250000000, maximum is 268435455.
[INFO] [RFNOC RADIO] Note that a decimation block will increase the number of samples per burst by the decimation factor. Your application may have requested fewer samples.
LLLLLLLLLLLLLLLLLLLError: ValueError: Requested too many samples in a single burst.
Thanks,
Jonathan
From: Marcus D. Leech patchvonbraun@gmail.com
Sent: Saturday, August 7, 2021 7:16 AM
To: Jonathan Tobin Tobin@augustusaero.com; usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Too Many Samples in a Single Burst
On 08/07/2021 12:23 PM, Jonathan Tobin wrote:
Reducing nsamps to below 268435455/2 works - but at 6.25Msps for all four channels (two daughterboards) this is very short amount of time. I can try changing channels but for my application I do need all four channels receiving - though this will have to be on Monday.
Yes, rx_multi_samples "out of the box" (no modifications to the example).
Thanks,
Jonathan
Given that rx_multi_samples doesn't actually DO anything with the samples, I'm curious about how it's actually useful for you in any
production sense--it is just a demo app to show some of the API usage.
It may be the case that this example needs to be updated because it's mis-using the API in some what that isn't immediately obvious to me.
But again, it doesn't actually DO anything with the samples, so I don't know how it's useful other than as a learning tool...
From: Marcus D. Leech patchvonbraun@gmail.commailto:patchvonbraun@gmail.com
Sent: Saturday, August 7, 2021 5:30 AM
To: Jonathan Tobin Tobin@augustusaero.commailto:Tobin@augustusaero.com; usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Too Many Samples in a Single Burst
On 08/06/2021 10:47 PM, Jonathan Tobin wrote:
Hi Marcus,
No, I have not attempted on UHD 4+. Due to some other software constraints I am only able to use 3.15 at the moment.
Thanks,
Jonathan
Does reducing nsamps help? What about channel count?
Just looking for clues as to what might be going on. Looking at the code, nothing really leaps out at me. You're using rx_multi_samples
"out of the box" or with modifications?
From: Marcus D. Leech patchvonbraun@gmail.commailto:patchvonbraun@gmail.com
Sent: Friday, August 6, 2021 3:56 PM
To: usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: [USRP-users] Re: Too Many Samples in a Single Burst
On 08/06/2021 07:26 PM, Jonathan Tobin wrote:
Hello,
In trying to test the ‘rx_multi_samples’ example with all four channels on an n310. I run into an error of “Requesting too many samples in a single burst” when I attempt a longer record (really anything over a few seconds). Seems to be my nsamps value, but I am unsure how to remedy the issue. Below is my argument and the terminal output for an attempt to receive for 10 seconds:
./rx_multi_samples --args "type=n3xx,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo" --rate 6.25e6 --subdev "A:0 A:1 B:0 B:1" --channels "0,1,2,3" --nsamps 625000000
Creating the usrp device with: type=n3xx,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo...
[INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501; UHD_3.15.0.HEAD-0-gaea0e2de
[INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=192.168.10.2,type=n3xx,product=n310,serial=3218B5F,claimed=False,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo
[INFO] [MPM.PeriphManager] init() called with device args `clock_source=gpsdo,time_source=gpsdo,product=n310,mgmt_addr=192.168.10.2'.
[INFO] [0/Replay_0] Initializing block control (NOC ID: 0x4E91A00000000004)
[INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/FIFO_0] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_1] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_2] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_3] Initializing block control (NOC ID: 0xF1F0000000000000)
Using Device: Single USRP:
Device: N300-Series Device
Mboard 0: ni-n3xx-3218B5F
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 1
RX DSP: 1
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 2
RX DSP: 0
RX Dboard: B
RX Subdev: Magnesium
RX Channel: 3
RX DSP: 1
RX Dboard: B
RX Subdev: Magnesium
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 1
TX DSP: 1
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 2
TX DSP: 0
TX Dboard: B
TX Subdev: Magnesium
TX Channel: 3
TX DSP: 1
TX Dboard: B
TX Subdev: Magnesium
Setting RX Rate: 6.250000 Msps...
Actual RX Rate: 6.250000 Msps...
Setting device timestamp to 0...
Begin streaming 625000000 samples, 1.500000 seconds in the future...
[ERROR] [RFNOC RADIO] Requesting too many samples in a single burst! Requested 12500000000, maximum is 268435455.
[INFO] [RFNOC RADIO] Note that a decimation block will increase the number of samples per burst by the decimation factor. Your application may have requested fewer samples.
Error: ValueError: Requested too many samples in a single burst.
Thanks,
Jonathan
That looks like a bug--have you tried this on UHD 4.recent?
Just as an additional update - I was able to test with UHD 4.1 and there is no issue - seems to be something with UHD 3.15 then.
Thanks,
Jonathan
From: Jonathan Tobin Tobin@augustusaero.com
Sent: Monday, August 9, 2021 5:42 AM
To: Marcus D. Leech patchvonbraun@gmail.com; usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Too Many Samples in a Single Burst
Meant late packets.
From: Jonathan Tobin Tobin@augustusaero.com
Sent: Monday, August 9, 2021 5:41 AM
To: Marcus D. Leech patchvonbraun@gmail.com; usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Too Many Samples in a Single Burst
Hi Marcus,
Here is the output from a simple run of txrx_loopback_to_file "out of the box." As can be seen, the same error occurs (along with dropped packets this time).
./txrx_loopback_to_file --tx-args "addr=192.168.10.2" --rx-args "type=n3xx,addr=192.168.10.2,time_source=internal,clock_source=internal" --rx-freq 2500e6 --rx-rate 6.25e6 --rx-subdev "A:0 A:1 B:0 B:1" --rx-channels "0,1,2,3" --rx-gain 60 --nsamps 62500000 --tx-rate 6.25e6 --tx-freq 2500e6
Creating the transmit usrp device with: addr=192.168.10.2...
[INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501; UHD_3.15.0.HEAD-0-gaea0e2de
[INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=192.168.10.2,type=n3xx,product=n310,serial=3218B5F,claimed=False,addr=192.168.10.2
[INFO] [MPM.PeriphManager] init() called with device args `product=n310,mgmt_addr=192.168.10.2,time_source=internal,clock_source=internal'.
[INFO] [0/Replay_0] Initializing block control (NOC ID: 0x4E91A00000000004)
[INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/FIFO_0] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_1] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_2] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_3] Initializing block control (NOC ID: 0xF1F0000000000000)
Creating the receive usrp device with: type=n3xx,addr=192.168.10.2,time_source=internal,clock_source=internal...
Using TX Device: Single USRP:
Device: N300-Series Device
Mboard 0: ni-n3xx-3218B5F
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 1
RX DSP: 1
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 2
RX DSP: 0
RX Dboard: B
RX Subdev: Magnesium
RX Channel: 3
RX DSP: 1
RX Dboard: B
RX Subdev: Magnesium
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 1
TX DSP: 1
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 2
TX DSP: 0
TX Dboard: B
TX Subdev: Magnesium
TX Channel: 3
TX DSP: 1
TX Dboard: B
TX Subdev: Magnesium
Using RX Device: Single USRP:
Device: N300-Series Device
Mboard 0: ni-n3xx-3218B5F
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 1
RX DSP: 1
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 2
RX DSP: 0
RX Dboard: B
RX Subdev: Magnesium
RX Channel: 3
RX DSP: 1
RX Dboard: B
RX Subdev: Magnesium
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 1
TX DSP: 1
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 2
TX DSP: 0
TX Dboard: B
TX Subdev: Magnesium
TX Channel: 3
TX DSP: 1
TX Dboard: B
TX Subdev: Magnesium
Setting TX Rate: 6.250000 Msps...
Actual TX Rate: 6.250000 Msps...
Setting RX Rate: 6.250000 Msps...
Actual RX Rate: 6.250000 Msps...
Setting TX Freq: 2500.000000 MHz...
Actual TX Freq: 2500.000000 MHz...
Configuring RX Channel 0
Setting RX Freq: 2500.000000 MHz...
Actual RX Freq: 2500.000000 MHz...
Setting RX Gain: 60.000000 dB...
Actual RX Gain: 60.000000 dB...
Configuring RX Channel 1
Setting RX Freq: 2500.000000 MHz...
Actual RX Freq: 2500.000000 MHz...
Setting RX Gain: 60.000000 dB...
Actual RX Gain: 60.000000 dB...
Configuring RX Channel 2
Setting RX Freq: 2500.000000 MHz...
Actual RX Freq: 2500.000000 MHz...
Setting RX Gain: 60.000000 dB...
Actual RX Gain: 60.000000 dB...
Configuring RX Channel 3
Setting RX Freq: 2500.000000 MHz...
Actual RX Freq: 2500.000000 MHz...
Setting RX Gain: 60.000000 dB...
Actual RX Gain: 60.000000 dB...
Checking TX: all_los: locked ...
Checking RX: all_los: locked ...
Setting device timestamp to 0...
[ERROR] [RFNOC RADIO] Requesting too many samples in a single burst! Requested 1250000000, maximum is 268435455.
[INFO] [RFNOC RADIO] Note that a decimation block will increase the number of samples per burst by the decimation factor. Your application may have requested fewer samples.
LLLLLLLLLLLLLLLLLLLError: ValueError: Requested too many samples in a single burst.
Thanks,
Jonathan
From: Marcus D. Leech patchvonbraun@gmail.com
Sent: Saturday, August 7, 2021 7:16 AM
To: Jonathan Tobin Tobin@augustusaero.com; usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Too Many Samples in a Single Burst
On 08/07/2021 12:23 PM, Jonathan Tobin wrote:
Reducing nsamps to below 268435455/2 works - but at 6.25Msps for all four channels (two daughterboards) this is very short amount of time. I can try changing channels but for my application I do need all four channels receiving - though this will have to be on Monday.
Yes, rx_multi_samples "out of the box" (no modifications to the example).
Thanks,
Jonathan
Given that rx_multi_samples doesn't actually DO anything with the samples, I'm curious about how it's actually useful for you in any
production sense--it is just a demo app to show some of the API usage.
It may be the case that this example needs to be updated because it's mis-using the API in some what that isn't immediately obvious to me.
But again, it doesn't actually DO anything with the samples, so I don't know how it's useful other than as a learning tool...
From: Marcus D. Leech patchvonbraun@gmail.commailto:patchvonbraun@gmail.com
Sent: Saturday, August 7, 2021 5:30 AM
To: Jonathan Tobin Tobin@augustusaero.commailto:Tobin@augustusaero.com; usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Too Many Samples in a Single Burst
On 08/06/2021 10:47 PM, Jonathan Tobin wrote:
Hi Marcus,
No, I have not attempted on UHD 4+. Due to some other software constraints I am only able to use 3.15 at the moment.
Thanks,
Jonathan
Does reducing nsamps help? What about channel count?
Just looking for clues as to what might be going on. Looking at the code, nothing really leaps out at me. You're using rx_multi_samples
"out of the box" or with modifications?
From: Marcus D. Leech patchvonbraun@gmail.commailto:patchvonbraun@gmail.com
Sent: Friday, August 6, 2021 3:56 PM
To: usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: [USRP-users] Re: Too Many Samples in a Single Burst
On 08/06/2021 07:26 PM, Jonathan Tobin wrote:
Hello,
In trying to test the ‘rx_multi_samples’ example with all four channels on an n310. I run into an error of “Requesting too many samples in a single burst” when I attempt a longer record (really anything over a few seconds). Seems to be my nsamps value, but I am unsure how to remedy the issue. Below is my argument and the terminal output for an attempt to receive for 10 seconds:
./rx_multi_samples --args "type=n3xx,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo" --rate 6.25e6 --subdev "A:0 A:1 B:0 B:1" --channels "0,1,2,3" --nsamps 625000000
Creating the usrp device with: type=n3xx,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo...
[INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501; UHD_3.15.0.HEAD-0-gaea0e2de
[INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=192.168.10.2,type=n3xx,product=n310,serial=3218B5F,claimed=False,addr=192.168.10.2,time_source=gpsdo,clock_source=gpsdo
[INFO] [MPM.PeriphManager] init() called with device args `clock_source=gpsdo,time_source=gpsdo,product=n310,mgmt_addr=192.168.10.2'.
[INFO] [0/Replay_0] Initializing block control (NOC ID: 0x4E91A00000000004)
[INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD100000011312)
[INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000002)
[INFO] [0/FIFO_0] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_1] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_2] Initializing block control (NOC ID: 0xF1F0000000000000)
[INFO] [0/FIFO_3] Initializing block control (NOC ID: 0xF1F0000000000000)
Using Device: Single USRP:
Device: N300-Series Device
Mboard 0: ni-n3xx-3218B5F
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 1
RX DSP: 1
RX Dboard: A
RX Subdev: Magnesium
RX Channel: 2
RX DSP: 0
RX Dboard: B
RX Subdev: Magnesium
RX Channel: 3
RX DSP: 1
RX Dboard: B
RX Subdev: Magnesium
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 1
TX DSP: 1
TX Dboard: A
TX Subdev: Magnesium
TX Channel: 2
TX DSP: 0
TX Dboard: B
TX Subdev: Magnesium
TX Channel: 3
TX DSP: 1
TX Dboard: B
TX Subdev: Magnesium
Setting RX Rate: 6.250000 Msps...
Actual RX Rate: 6.250000 Msps...
Setting device timestamp to 0...
Begin streaming 625000000 samples, 1.500000 seconds in the future...
[ERROR] [RFNOC RADIO] Requesting too many samples in a single burst! Requested 12500000000, maximum is 268435455.
[INFO] [RFNOC RADIO] Note that a decimation block will increase the number of samples per burst by the decimation factor. Your application may have requested fewer samples.
Error: ValueError: Requested too many samples in a single burst.
Thanks,
Jonathan
That looks like a bug--have you tried this on UHD 4.recent?