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), 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->recv() function -- it looks like the timeout defaults to 0.1 seconds. I'm not familiar with the second error, however :) Sorry! EJ On Thu, Mar 15, 2018 at 1:55 PM, Sebastian Leutner via USRP-users < usrp-users@lists.ettus.com> wrote: > 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 > block, I get "timeout on chan 0" messages as soon as there is nothing > detected and thus no output from my block. I suppose this principle is > relevant for any radio receiver implementation in RFNoC. I am using the > X310 with UHD 4.0.0.rfnoc-devel-409-gec9138eb. > > I have problems figuring out how this timeout is implemented exactly. 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? Is the ZPU responsible for this? > > Just ignoring the timeout messages works up to a certain point where I get > the following error messages. Valid data samples are not processed any > more after this happens. > [ERROR] [X300] x300 fw communication failure #1 EnvironmentError: > IOError: x300 fw poke32 - reply timed out > [ERROR] [X300] x300 fw communication failure #2 EnvironmentError: > IOError: x300 fw poke32 - reply timed out > [ERROR] [X300] x300 fw communication failure #3 EnvironmentError: > IOError: x300 fw poke32 - reply timed out > [ERROR] [UHD] An unexpected exception was caught in a task loop.The > task loop will now exit, things may not work. x300 fw communication failure > #3 EnvironmentError: IOError: x300 fw poke32 - reply timed out > > Any help or ideas appreciated! > > Best regards, > Sebastian > > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > >
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
