Bladerf bandwidth limited to 2 MHz

[andruxa-smirnov]

When i set bladerf bandwidth more, than 2MHz (more 2000000 samples per second), bandwidth all time limited to 2 MHz.

[BatchDrake]

Confirmed, working on it.

[BatchDrake]

I've just commited something to suscan's master branch that may be related to what you are experiencing. I've just checked it out with AirSpy at 6000000 and Bandwidth is limited to 6 MHz (as expected). Rebuild suscan from master and try again. If you still fail to make it work, could you provide a screenshot?

[andruxa-smirnov]

Rebuilding don't solve problem

[BatchDrake]

That's strange, I can increase the bandwidth up to the sample rate. Can you provide some screenshots of what you're attempting? El vie., 23 ago. 2019 21:04, andruxa-smirnov <notifications@github.com> escribió:

…

Rebuilding don't solve problem [image: 2019-08-23 22-01-34] <https://user-images.githubusercontent.com/5259697/63617356-efa6ff80-c5f1-11e9-95e0-e6eb844d9d61.png> — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#13?email_source=notifications&email_token=AAEVET65GHNZKC3ZAQUPR6LQGAYEBA5CNFSM4IOX4GL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5BCG2I#issuecomment-524428137>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEVET2APRMVRTTO7LW4DHLQGAYEBANCNFSM4IOX4GLQ> .

[andruxa-smirnov]

[BatchDrake]

You are not running the latest version of SigDigger (there should be a bandwidth control in the source panel). Pull from master (from SigDigger, not Suscan) and build again. You should be able to adjust the bandwidth dynamically after that.

[andruxa-smirnov]

What i doing not so?
I deleted SigDigger folder. I clone master branch newly, after that i do "qmake", "make" and "sudo make install", but that don't solve problem.
More one intresting thing - i see bladerf device double in sdr sources list. Why?

[BatchDrake]

I've just cloned SigDigger from master. After building I do see the bandwidth adjust widget, look:

Please check again whether you are actually running the right executable. This dynamic bandwidth control feature is already in master.

More one intresting thing - i see bladerf device double in sdr sources list. Why?

This happens if the device label has changed since the last time you plugged it (or if you have two different BladeRF devices, and the one you plugged last time is different from the one you have plugged now). This is the expected behavior. What is not expected is the BladeRF identification string to change between executions.