[srslte-users] Problem with srsLTE captures using bladerf

[Ismael Gomez]

Hi,

It could also be the LO leakage. I think you can mitigate that by adding
some frequency offset to the frequency tunning process. You can play with
the bladeRF driver as much as you want. The interface is implemented in
srslte/lib/rf/src/rf_blade_imp.c

Hope that helps, let me know if you need any further info

Cheers
Ismael

On Tue, 22 Mar 2016 at 17:24 Nicola Bui <nicola.bui at imdea.org> wrote:

> Dear all,
>
> first of all let me thanks the team for the great job and the support they
> gave me throughout my development.
> I am capturing some lte traces with both a bladerf x40 and usrp x310. Both
> are fine in most of the cases, but I found the bladerf x40 to introduce
> some high power noise inband. You can find attached two pictures related to
> similar captures:
> - frequency 1854.1 MHz
> - samplerate 11.52 Msps
> - resource blocks 50
> As you can see the bladerf capture shows two high power carrier on the
> right side of the spectrum, which, usually are not a big problem, but when
> I try to decode DCIs using that part of the spectrum (ncce 5, 24, etc.)
>
> I tried a similar capture with bladeRF-cli and gnuradio (osmosdr
> interface): the former got the same problem, the latter did not. My guess,
> it is something related to how the bladerf is opened (I am thinking about
> how the signal is filtered), but I have no clue on how to test it.
>
> Is there any way to control the bladerf configuration from within pdsch_ue
> or usrp_capture_sync?
>
> Thanks a lot,
> Nicola Bui
>
> Research Engineer
> IMDEA Networks Institute
> Av. Mar del Mediterraneo, 22
> 28918 - Leganés (Madrid) - Spain
> mobile: +34 657 633 987
> phone: +34 91 481 6986
> fax: +34 481 6965
> _______________________________________________
> srslte-users mailing list
> srslte-users at lists.softwareradiosystems.com
> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20160322/584c55b3/attachment.htm>