-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bladerf_set_sample_rate failed when using dump1090 with bladeRF xA5 #172
Comments
Can you report this to nuand? I don't have equivalent hardware to test on, and this seems like a hardware or libbladeRF problem. |
I exchanged a few emails with their support. They suspect it is related to this section: Lines 267 to 280 in a13356d
Can I assist by providing access to the hardware? |
That code is not reached in your case - on your system it's failing earlier, here: Lines 231 to 234 in a13356d
I think the calibration that times out is triggered automatically within libbladeRF. |
the same problem also happens with the xA9
|
Can you raise this with Nuand as AFAIK dump1090 is using their API correctly and the failure is internal to their library. |
already did, and they replied: |
Okay. I'm not gonna get into a blame game with nuand. dump1090 is calling a regular libbladerf function which then fails with an unexpected error; if nuand can't help you further with where the problem lies, I'm not sure I can help. |
Can you formally remove support for bladeRF in that case? I do not disagree that Nuand has been uncooperative but, despite your assertion, the situation is in a stalemate due to deflection on both sides. I regret making a decision to buy into the bladeRF platform which was partly driven by (what I thought was) dump1090 support. I am glad to provide access to my bladeRF hardware or anything else you think that would be helpful to break the deadlock, I hate to just complain. |
We actually use the bladeRF code on older bladerf hardware that's out in the field, so I can't just remove support outright. I can add a note to the README noting that there are some problems with newer hardware (or maybe a newer lib?) if you like? Maybe the path forward is to build a minimal standalone demo of the problem (it should just be a case of running the same API calls that dump1090 executes in a little test app -- the failure happens early on, so this should be straightforward) and pass that on to nuand so there's no ambiguity around "but our ADS-B stuff works!". If there's something wrong in how dump1090 is using the API then I'm happy to fix that but currently I have no information about what needs to be changed. |
While trying to use dump1090 with a bladeRF 2.0 micro xA5 I am getting multiple errors, seemingly related to the sample rate. I've tried with both the hostedxA5-latest and adsbxA5.rbf bitstreams.
I have compiled dump1090 from source as I am using the latest libbladeRF version that is not packaged for Debian bullseye.
This is the error out with the hostedxA5-latest.rbf bitstream:
Same error output with the adsbxA5.rbf bitstream:
Device and version info:
dump1090-fa version:
I am able to use bladeRF-adsb without issue on the same setup but ideally would like to run everything within dump1090.
The text was updated successfully, but these errors were encountered: