Re: Receiving on two channels with E310/E312

my@comp:/usr/local/lib/uhd/examples$ ./rx_multi_samples --args="addr=192.168.10.43" --rate=1000000 --channels="0,1"

Creating the usrp device with: addr=192.168.10.43...

[INFO] [UHD] linux; GNU C++ version 9.4.0; Boost_107100; UHD_4.1.0.HEAD-0-g6bd0be9c

[INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=192.168.10.43,type=e3xx,product=e310_sg3,serial=31F3C12,fpga=n/a,claimed=False,addr=192.168.10.43

[INFO] [MPM.PeriphManager] Found 1 daughterboard(s).

[INFO] [MPM.PeriphManager] init() called with device args `fpga=n/a,mgmt_addr=192.168.10.43,product=e310_sg3'.

[WARNING] [UDP] The recv buffer could not be resized sufficiently.

Target sock buff size: 2500000 bytes.

Actual sock buff size: 212992 bytes.

See the transport application notes on buffer resizing.

Please run: sudo sysctl -w net.core.rmem_max=2500000

[WARNING] [UDP] The send buffer could not be resized sufficiently.

Target sock buff size: 2500000 bytes.

Actual sock buff size: 212992 bytes.

See the transport application notes on buffer resizing.

Please run: sudo sysctl -w net.core.wmem_max=2500000

[WARNING] [UDP] The current recv_buff_size of 212992 is less than the minimum recommended size of 816000 and may result in dropped packets on some NICs

[WARNING] [UDP] The current send_buff_size of 212992 is less than the minimum recommended size of 307200 and may result in dropped packets on some NICs

[INFO] [0/Radio#0] Performing CODEC loopback test on channel 0 ...

[INFO] [0/Radio#0] CODEC loopback test passed

[INFO] [0/Radio#0] Performing CODEC loopback test on channel 1 ...

[INFO] [0/Radio#0] CODEC loopback test passed

Using Device: Single USRP:

Device: E300-Series Device

Mboard 0: e310_sg3

RX Channel: 0

RX DSP: n/a

RX Dboard: A

RX Subdev: E3xx

RX Channel: 1

RX DSP: n/a

RX Dboard: A

RX Subdev: E3xx

TX Channel: 0

TX DSP: n/a

TX Dboard: A

TX Subdev: E3xx

TX Channel: 1

TX DSP: n/a

TX Dboard: A

TX Subdev: E3xx

Setting RX Rate: 1.000000 Msps...

Actual RX Rate: 1.000000 Msps...

Setting device timestamp to 0...

[WARNING] [UDP] The recv buffer could not be resized sufficiently.

Target sock buff size: 2500000 bytes.

Actual sock buff size: 212992 bytes.

See the transport application notes on buffer resizing.

Please run: sudo sysctl -w net.core.rmem_max=2500000

[WARNING] [UDP] The send buffer could not be resized sufficiently.

Target sock buff size: 2500000 bytes.

Actual sock buff size: 212992 bytes.

See the transport application notes on buffer resizing.

Please run: sudo sysctl -w net.core.wmem_max=2500000

[WARNING] [UDP] The current recv_buff_size of 212992 is less than the minimum recommended size of 307200 and may result in dropped packets on some NICs

[WARNING] [UDP] The current send_buff_size of 212992 is less than the minimum recommended size of 307200 and may result in dropped packets on some NICs

[WARNING] [UDP] The recv buffer could not be resized sufficiently.

Target sock buff size: 2500000 bytes.

Actual sock buff size: 212992 bytes.

See the transport application notes on buffer resizing.

Please run: sudo sysctl -w net.core.rmem_max=2500000

[WARNING] [UDP] The send buffer could not be resized sufficiently.

Target sock buff size: 2500000 bytes.

Actual sock buff size: 212992 bytes.

See the transport application notes on buffer resizing.

Please run: sudo sysctl -w net.core.wmem_max=2500000

[WARNING] [UDP] The current recv_buff_size of 212992 is less than the minimum recommended size of 307200 and may result in dropped packets on some NICs

[WARNING] [UDP] The current send_buff_size of 212992 is less than the minimum recommended size of 307200 and may result in dropped packets on some NICs

Begin streaming 10000 samples, 1.500000 seconds in the future...

Received packet: 364 samples, 1 full secs, 0.500000 frac secs

Received packet: 364 samples, 1 full secs, 0.500364 frac secs

Received packet: 364 samples, 1 full secs, 0.500728 frac secs

Received packet: 364 samples, 1 full secs, 0.501092 frac secs

Received packet: 364 samples, 1 full secs, 0.501456 frac secs

Received packet: 364 samples, 1 full secs, 0.501820 frac secs

Received packet: 364 samples, 1 full secs, 0.502184 frac secs

Received packet: 364 samples, 1 full secs, 0.502548 frac secs

Received packet: 364 samples, 1 full secs, 0.502912 frac secs

Received packet: 364 samples, 1 full secs, 0.503276 frac secs

Received packet: 364 samples, 1 full secs, 0.503640 frac secs

Received packet: 364 samples, 1 full secs, 0.504004 frac secs

Received packet: 364 samples, 1 full secs, 0.504368 frac secs

Received packet: 364 samples, 1 full secs, 0.504732 frac secs

Received packet: 364 samples, 1 full secs, 0.505096 frac secs

Received packet: 364 samples, 1 full secs, 0.505460 frac secs

Received packet: 364 samples, 1 full secs, 0.505824 frac secs

Received packet: 364 samples, 1 full secs, 0.506188 frac secs

Received packet: 364 samples, 1 full secs, 0.506552 frac secs

Received packet: 364 samples, 1 full secs, 0.506916 frac secs

Received packet: 364 samples, 1 full secs, 0.507280 frac secs

Received packet: 364 samples, 1 full secs, 0.507644 frac secs

Received packet: 364 samples, 1 full secs, 0.508008 frac secs

Received packet: 364 samples, 1 full secs, 0.508372 frac secs

Received packet: 364 samples, 1 full secs, 0.508736 frac secs

Received packet: 364 samples, 1 full secs, 0.509100 frac secs

Received packet: 364 samples, 1 full secs, 0.509464 frac secs

Received packet: 172 samples, 1 full secs, 0.509828 frac secs

Done!

my@comp:/usr/local/lib/uhd/examples$

On 2022-07-27 14:22, Lipski, Michael Victor wrote:

Sure, screenshot of flowgraph is included. GRC version is 3.8, UHD is 4.1.0.

The E310 is being used in networking mode for some very basic testing. I have an E312 set up as to transmit a sine wave output (USRP Sink), which is connected over SMA to the E310 Rx ports (USRP Source). This works fine with a single Rx channel, and I can split the output of the transmitter and feed it to two different E310s, which works just fine as well. However, if I try to receive them both on the same E310, I get an error.

From: Discuss-gnuradio <discuss-gnuradio-bounces+mvl5023=psu.edu@gnu.org> on behalf of Marcus D. Leech <patchvonbraun@gmail.com>
Sent: Wednesday, July 27, 2022 1:58 PM
To: discuss-gnuradio@gnu.org <discuss-gnuradio@gnu.org>
Subject: Re: Receiving on two channels with E310/E312

On 2022-07-27 13:40, Lipski, Michael Victor wrote:

I tried both options; "A:A A:B" was invalid; it seems to accept "A:0 A:1", except that it gives me the same error message: "Runtime Error: port number 1 exceeds max of 0."

Everything works fine with a single receive channel. I have also tried streaming a single receive channel from two different E310s, which works just fine as well. As soon as I try to add a second Rx channel, the flowgraph stops working.

Could you perhaps share the flow-graph with the list, and which version of UHD, Gnu Radio you're using? Are you running on the E310 itself, or using
"network mode" ?

This may be a bug in gr-uhd, not sure.

What happens if you use one of the UHD-only example apps, like "rx_multi_samples" ? ?

From:	Lipski, Michael Victor
Subject:	Re: Receiving on two channels with E310/E312
Date:	Thu, 28 Jul 2022 15:22:06 +0000