SDRplay Community Forum

yes, that libusb error will be a problem - that is saying that something else has grabbed the device. Using lsmod, check to see if there is anything like msi001, msi2500 or sdr_msi3101 loaded - these will cause a problem and will need to be blacklisted. If not, then you need to make sure only 1 appl...

You need to build SoapySDR and SoapySDRPlay before SoapySDR will work - if you have a 32bit OS that might be why SoapySDR didn't work after the API install - we only distribute the 64bit version.

Best regards,

SDRplay Support

In the code I posted -b is not used and the bandwidth is fixed at 1.536MHz - using -s of anything less than 2 is not a valid state so this maybe why you are getting strange buffer sizes being malloc'd? The code was an example and needs more work to be robust. I'm happy to update the github repositor...

For 16bit output the 2nd parameter in the fwrite statement should be a 2 otherwise it's only writing 8 bits of the buffer value.

Best regards,

SDRplay Support

it's signed (short)

Best regards,

SDRplay Support

I'm not sure about the post processing - what is the -r option in sox doing? The sample rate used in the play_sdr is 2MHz - are you taking that into account anywhere?

Best regards,

SDRplay Support

If you want a 16 bit output, don't do the right shift and change the output buffer to 16 bits instead of 8

Best regards,

SDRplay

Hi,

The best supported option is CubicSDR (the API installation will also contain SoapySDR/SoapySDRPlay which you need to communicate with the RSP)

http://cubicsdr.com - it's still in development but already becoming pretty popular.

Best regards,

SDRplay Support

The output of the RSP is 16 bits. To be compatible with the RTL code you need to remove the top 8 bits which is what...

>> 8

is doing

In the ADS-B code we have to do >> 8 + 127

so you can try with that as well.

Hope that helps,

Best regards,

SDRplay Support

The lilbusb -6 error means that a driver has already grabbed the USB port, so the RSP API cannot get access to it. I would check to see if you have any kernel drivers loaded that have done that by usng lsmod (you are looking for something like msi001, msi2500 or sdr_msi3101) - if that's the case you...