(1) From examining the code, I find that I can read the rssi/clipping
indicator register associated with ADC n with
usrp._u._read_fpga_reg( n+5 )
where usrp is an instance of usrp.source_s.
Question: Is there a better/preferred/higher-level function to access
(2) When I use the above to poll the rssi/clipping register while using
usrp.source I get glitches (at the rate of several per minute) in the
data stream. A modified version of test_counting.py (attached) shows
several types of errors. In order of decreasing frequecy, they are:
single-bit errors; (b) multiple-bit errors within each 16-bit value
never multiple bit errors spanning consecutive 16-bit values); © two
values missing; (d) one count value missing; (e) random value inserted
count sequence; and (f) multiple instances of 0 or 0xffff inserted in
sequence. Eventually (usually within an hour) the program will
with “usb_reap_async: timeout error”.
This happens on Windows XP/SP2 with either MSYS/MinGW or Cygwin.
is AMD Sempron 3100+. GNU Radio is latest svn version.
Request: Would a few people be willing to try this short test program
what it does on their system? (It should produce a few lines of
“gr_check_counting” messages as it starts then produce nothing else
you kill it.)
This appears to be a USB problem, except that none of the usrp requests
usrp._u.set_pga( which, 0. ) usrp._u.read_aux_adc( 0, 0 ) usrp._u.noverruns()
cause problems, while the request
usrp._u._read_fpga_reg( 4 )
seems to produce “usb_reap_async: timeout error” the first time it is
if the flow graph is running (but executes ok before the flow graph is
Questions: Should we expect usrp register read requests to interfere
data transfers? Is there a better way to access the rssi/clipping
indicator? Will mblocks allow internal USRP information (such as the
registers) to be included in data packets read from the USRP?
Thanks for any help (and thanks, Eric, for pointing to
– Don W.