Yes, correct.

 

My host is 10.22.128.1 though, and the usrp (dest) is 10.22.128.3.

 

So from wireshark I read that last control packet as host->usrp?

 

These are the current routes:

 

connections:

  - { srcblk: radio0,     srcport: out_0,    dstblk: ep0,       dstport: in0}

  - { srcblk: radio0,     srcport: out_1,    dstblk: _device_,  dstport: _none_}

  - { srcblk: radio1,     srcport: out_0,    dstblk: ep2,       dstport: in0}

  - { srcblk: radio1,     srcport: out_1,    dstblk: _device_,  dstport: _none_}

 

  - { srcblk: _device_,   srcport: _none_,   dstblk: radio0,    dstport: in_0 }

  - { srcblk: _device_,   srcport: _none_,   dstblk: radio0,    dstport: in_1 }

  - { srcblk: _device_,   srcport: _none_,   dstblk: radio1,    dstport: in_0 }

  - { srcblk: _device_,   srcport: _none_,   dstblk: radio1,    dstport: in_1 }

 

  # multiddc connections

  - { srcblk: ep6,        srcport: out0,     dstblk: multiddc0, dstport: in_0 }

  - { srcblk: multiddc0,  srcport: out_0,    dstblk: ep7,       dstport: in0 }

 

Changing ep7 to ep6 doesn’t work either although I believe that should be valid 
too.

 

From: Martin Braun <martin.br...@ettus.com> 
Sent: Tuesday, 29 July 2025 09:46
Cc: usrp-users@lists.ettus.com
Subject: [USRP-users] Re: [EXTERNAL]Re: remote streaming starts, but stops 
after a few packets received

 

 

 

On Mon, Jul 28, 2025 at 4:14 PM Kevin Williams <kevin.willi...@vastech.co.za 
<mailto:kevin.willi...@vastech.co.za> > wrote:

 

Changing the destination EP to a new one, ep7, worked again.

 

>From the RFNoC 4 workshop slides I was under the impression blocks could start 
>and end on the same SEP?

 

They can, and even should, but how are you doing remote streaming in this case? 
Are you connecting radio -> DDC -> remote streamer?

 

--M

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com

Reply via email to