EJ Kreinar wrote:
You can find the "timeout on chan 0" message implemented in
gr-ettus/lib/rfnoc_block_impl.cc. As you suspected (correctly), it is a harmless output that
can be ignored if no data is actually coming from your RFNoC block. It is driven by
receiving a timeout from the streamer->
On Thu, Mar 15, 2018 at 2:20 PM, EJ Kreinar via USRP-users <
usrp-users@lists.ettus.com> wrote:
> Hi Sebastian,
>
> > Does RFNoC assume that a block always has to output samples within a
> certain time limit? Can someone explain to me, where the timeout is checked
> and raised?
>
> You can find th
Hi Sebastian,
> Does RFNoC assume that a block always has to output samples within a
certain time limit? Can someone explain to me, where the timeout is checked
and raised?
You can find the "timeout on chan 0" message implemented in
gr-ettus/lib/rfnoc_block_impl.cc. As you suspected (correctly),
Hi all,
I have a custom RFNoC block which detects data packets in a stream of
I/Q-samples coming from a file source or the RFNoC Radio block. It only
outputs samples if it detects a packet, otherwise it does not output
anything. This works fine in simulation but when using the synthesized
blo
