I have one question regarding the samples captured using usrp_rx_cfile.py
at the receiver. Is there anyway that I let the usrp_rx_cfile.py run
forever, and it will keep on capturing samples through USRP forever, while I
keep on taking out 10K samples (lets say) at a time from that “continuous
capture”, and process them for xyz(…). Then next time I take out the NEXT
10K samples and process them for xyz(…). Meanwhile, the usrp_rx_cfile.py
continuously keeps on capturing the samples off of the air using USRP
The easiest way I think to do this would be just pipe the output of
the gnuradio data into your handler program. Of course this limits
you to the maximum buffer size in the pipe (64KB on linux I think?).
If that’s no good, you would probably be better off simply writing
your own gnuradio block to handle the processing and produce whatever
output you require
Finally, If you absolutely need to process the data outside of
gnuradio for some reason and the tcp_sink/pipe method doesn’t work you
could make a ‘rotating sink’ by following the same directions, but
using the gr_file_sink as a baseline. You could write n samples to a
file, then write n to a second file, then switch back to the first. I
think it would pretty simple to re-write gr_file_sink to do this; just
remember that if have more than one of these sinks active they may not
be exactly in sync.
If none of these are ideal you could let us know your motivation
behind wanting this scheme to work and we might able to present you
with a better way to go about it.