If you are using RFNoC capable USRPs, it is the UHD 'block controllers' that propagate a command (or swallow it, if they want) to the next upstream block controller. Thus if you develop a custom block (and custom block controller), you can decide if/how you want to propagate properties, commands, etc. Rob
On Tue, Apr 4, 2023 at 3:06 PM Rob Kossler <rkoss...@nd.edu> wrote: > It is really the opposite, the cmd propagation flows upstream (from the > rx_streamer to the DDC to the Radio). > Rob > > On Tue, Apr 4, 2023 at 3:00 PM yan zhang <yanzhan...@gmail.com> wrote: > >> So in general, we can just issue stream cmd to one source rfnoc block and >> the cmd will propagates to all down stream blocks. Is this understanding >> correct? >> >> Thanks! >> >> On Tue, Apr 4, 2023 at 11:27 AM Rob Kossler <rkoss...@nd.edu> wrote: >> >>> issue_stream_cmd() tells the Rx radio to start sending samples. You >>> typically call this as rx_streamer->issue_stream_cmd(), and then the >>> command "propagates" to all the blocks in the graph (such as DDC and then >>> ultimately the Rx Radio). Without this command, the Rx radio will not >>> begin streaming such that your call to "recv()" will timeout for lack of >>> samples. >>> Rob >>> >>> On Tue, Apr 4, 2023 at 10:58 AM <yanzhan...@gmail.com> wrote: >>> >>>> Hi all, >>>> >>>> Does anyone know the purpose of issue_stream_cmd() for the rx_streamer? >>>> When I use the rx_streamer to stream data to the host, I just call the >>>> recv() method. >>>> >>>> >>>> The question is what is the purpose of issue_stream_cmd() for >>>> rx_streamer in uhd? >>>> >>>> >>>> Thanks, >>>> >>>> Yan >>>> _______________________________________________ >>>> USRP-users mailing list -- usrp-users@lists.ettus.com >>>> To unsubscribe send an email to usrp-users-le...@lists.ettus.com >>>> >>>
_______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
