You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just started trying the bladeRF 2. I'm receiving blocks of 508 samples in CS16 at 55MS/s on a single channel. It seems 508 is a good number to avoid losing samples, not sure why.
I'm getting the right number of samples, but sometimes the corresponding timestamp is huge (and always the same, it seems, while the stream is open). Here is an examples of the timestamps I get:
The 5403559341571466134 seems to mostly appear in the 1st 100 or so blocks of samples. I still get a bunch of it from time to time. Its value changes slightly between runs (eg 5403508717576707884).
The strange timestamp seems to be dependent on the sampling rate:
at 50MS/s it's something like 7788488250102240434, 7788464422105176684, 7788505138102870934
at 40MS/s -4099528598654215607, -4099567862654389607, -4099597736657010357
at 30MS/s 6831683955593752351, 6831575683590478851
at 20MS/s -8199457430324793714, -8199508621324826214
The lower the sampling rate, the lower the number of time I see the strange timestamp.
I also get the following errors from time to time at high sampling rate [ERROR @ host/libraries/libbladeRF/src/streaming/sync.c:306] wait_for_buffer: Timed out waiting for buf_ready after 1000 ms
and [ERROR @ host/libraries/libbladeRF/src/backend/usb/libusb.c:1083] Transfer timed out for buffer 000001653A124120
The text was updated successfully, but these errors were encountered:
Hi,
I'm using a bladeRF 2.0 micro on Win10 through Soapy so I'm not 100% sure if the problem comes from blade or soapy.
I just started trying the bladeRF 2. I'm receiving blocks of 508 samples in CS16 at 55MS/s on a single channel. It seems 508 is a good number to avoid losing samples, not sure why.
I'm getting the right number of samples, but sometimes the corresponding timestamp is huge (and always the same, it seems, while the stream is open). Here is an examples of the timestamps I get:
The 5403559341571466134 seems to mostly appear in the 1st 100 or so blocks of samples. I still get a bunch of it from time to time. Its value changes slightly between runs (eg 5403508717576707884).
The strange timestamp seems to be dependent on the sampling rate:
The lower the sampling rate, the lower the number of time I see the strange timestamp.
I also get the following errors from time to time at high sampling rate
[ERROR @ host/libraries/libbladeRF/src/streaming/sync.c:306] wait_for_buffer: Timed out waiting for buf_ready after 1000 ms
and
[ERROR @ host/libraries/libbladeRF/src/backend/usb/libusb.c:1083] Transfer timed out for buffer 000001653A124120
The text was updated successfully, but these errors were encountered: