Sdrplay Driver Android

1 view

Skip to first unread message

Gaja Starks

unread,

Aug 5, 2024, 2:09:57 PM8/5/24

to fronmembgipet

Beforebuilding the block you have to make sure that all the dependencies (see list of supported devices above) you are intend to work with are properly installed. The build system of gr-osmosdr will recognize them and enable specific source/sink components thereafter.

You can specify the source or sink device using a comma separated string of argument=value pairs. The always-up-to-date block documentation with examples is available [ -osmosdr/tree/grc/gen_osmosdr_blocks.py#n100 right here": -gnuradio]..

The sdrplay source uses a precompiled (closed source) library available from _drivers.html to interface with the hardware. To enable this nonfree driver you have to call cmake with the additional parameter -DENABLE_NONFREE=TRUE

Beware of a little catch, there are some examples floating on the net with "hackrf=1" as the device argument. Device index numbers are 0-based (like with rtlsdr and other drivers), so you'll have to use hackrf=0 if you only have a single device attached, hackrf=1 would be the second device. Before this patch the hackrf gr-osmosdr driver did not care about the parameter at all.

The SDR-IP/NetSDR discovery protocol (UDP broadcast) is implemented, thus specifying the ip & port should not be neccessary. Note: for the receiver to operate properly it is required that the UDP packets (port 50000) carrying the sample data can reach your PC, therefore configure your firewall/router/etc. accordingly...