osmocom-sdr

osmocom-sdr@lists.osmocom.org

1 participants
910 discussions

Airspy patch to enable USB bit packing
by Martin Smith 29 Feb '16

29 Feb '16

Last July there were several changes made to the Airspy firmware and libairspy that added support for a new bit packing mode where 4 sets of 12 bit samples are packed into 3 sets of 16 bits for the transfer across the USB bus ( https://i.imgur.com/qXnWoEK.png?1 ). 25% less data is transferred across the bus and this is good for some computers with cheap USB chipsets. There is an overhead of extra memory bandwidth required on the host side to unpack the data into a useful format, so for optimal performance bit packing is disabled by default. The data is automatically unpacked within libairspy before being passed along, so no changes are required anywhere else if packing is enabled (or not enabled). Airspy firmware older than v1.0.0-rc6 does not have the function, but that is detected and handled by libairspy. I wrote the attached patch to enable packing in gr-osmosdr, which I tested and it works. It is basically a clone of the bias=0|1 lines as pack=0|1 and calls the needed libairspy function. ref: https://github.com/airspy/firmware/commit/7e1806b https://github.com/airspy/firmware/commit/5b7dcab https://github.com/airspy/host/commit/a51eccb --- Do some Baseline test with Airspy command line tools to have something to compare USB throughput results -------------------------------------------------------------------------------------------------------- $ sudo mount -t debugfs none /sys/kernel/debug $ sudo modprobe usbmon $ wireshark -i usbmod3 & $ airspy_info ; sleep 120 ; \ airspy_rx -t 4 -r /dev/null -n 2400000000 ; sleep 120 ; \ airspy_rx -t 4 -r /dev/null -p 1 -n 2400000000 ; sleep 120 ; \ airspy_info Wireshark->Statistics->IO Graph The Bytes/Tick are double the actual data rate because of way wireshark collects the USB packets, I could have added a filter to fix this. But the relationship is valid 25% less with packing enabled. The data rate in the IO Grahp drops from 80MB/sec (in+out) [really 40MB/sec] to 60MB/second (in+out) [really 30MB/sec] from unpacked to packed. 10MSPS no packing, packing https://i.imgur.com/pA9LPdE.png?1 2.5MSPS no packing, packing https://i.imgur.com/lA8q5aq.png?1 Verification test with my patched gr-osmosdr -------------------------------------------- $ sudo mount -t debugfs none /sys/kernel/debug $ sudo modprobe usbmon $ wireshark -i usbmod3 & $ osmocom_fft -a "airspy=0" -s 10000000 --fft-rate=1 $ osmocom_fft -a "airspy=0,pack=1" -s 10000000 --fft-rate=1 $ osmocom_fft -a "airspy=0" -s 2500000 --fft-rate=1 $ osmocom_fft -a "airspy=0,pack=1" -s 2500000 --fft-rate=1 $ osmocom_fft -a "airspy=0" -s 2500000 --fft-rate=1 $ osmocom_fft -a "airspy=0,pack=0" -s 2500000 --fft-rate=1 I ran all of the above tests and the wireshark USB throughput graphs showed exactly what was expected. 40MB/sec(10MSPS+normal),30MB/sec(10MSPS+packing),10MB/sec(2.5MSPS+normal),7.5MB/sec(2.5MSPS+packing),10MB/sec(2.5MSPS+normal),10MB/sec(2.5MSPS+normal). 25% less when packing was enabled and if you did not specify the "pack=1", then no bit packing is performed by libairspy. All the magnitudes within the FFT windows looked exactly the same as they do without bit packing.

2 1

rtl_test
by Ashish Kurian 25 Feb '16

25 Feb '16

Hi, When I run the command rtl_test I get the message like Reading samples in async mode and then there is no output. But when I give commands like rtl_test -p I get the expected output. Please help me in fixing this issue. Best Regards, Ashish Kurian

1 0

Building rtl-sdr under mingw64
by Momchil Ivanov 22 Feb '16

22 Feb '16

Hi, I was trying to build rtl-sdr on windows using mingw64 and stumbled upon the error described here [1] [ 40%] Building C object src/CMakeFiles/rtl_adsb.dir/rtl_adsb.c.o Linking C executable rtl_adsb.exe libconvenience_static.a(convenience.c.o):convenience.c:(.text+0x1e5): undefined reference to `rtlsdr_set_tuner_gain_mode' libconvenience_static.a(convenience.c.o):convenience.c:(.text+0x1e5): relocation truncated to fit: R_X86_64_PC32 against undefined symbol `rtlsdr_set_tuner_gain_mode' libconvenience_static.a(convenience.c.o):convenience.c:(.text+0x1fb): undefined reference to `rtlsdr_get_tuner_gains' libconvenience_static.a(convenience.c.o):convenience.c:(.text+0x1fb): relocation truncated to fit: R_X86_64_PC32 against undefined symbol `rtlsdr_get_tuner_gains' and so on.... I was able to build rtl-sdr using the attached patch. I exchange the order of linking libraries. 1: http://lists.osmocom.org/pipermail/osmocom-sdr/2015-April/000048.html Greetings, Momchil

1 0

Status of Hardware
by Mark Richards 19 Feb '16

19 Feb '16

Greetings. As I am looking to build a multi-channel NBFM communications recording device for a public service event, I'd like to know the status of the Osmocom hardware. I can use the RTL-SDR, but perhaps a board with more horsepower would be good. /K1MGY

2 1

[patch]: rtl_sdr, fix -n parameter
by Henk 08 Feb '16

08 Feb '16

Fix bytes_to_read adjustment in callback. For example bug exposes itself with: rtl_sdr -f 100e6 -s 2048000 -n 245.76e6 /tmp/100M.iq and does not terminate after the expected 245.76e6 samples. Which is an exact multiple of "out_block_size". Signed-off-by: Henk vergonet <henk.vergonet(a)gmail.com>

1 1

Ubuntu+Windows binaries for GNURadio/GrOsmo
by Josh Blum 31 Jan '16

31 Jan '16

Hey list, This is an update and an announcement: Alexandru Csete and I have been maintaining an Ubuntu PPA for SDR community software for some time. We just updated to GNU Radio 3.7.9 and GrOsmoSDR with RedPitaya support. The goal of the PPA is to have have recent releases of community software (SDR drivers, GNU Radio, and related projects) across several versions of Ubuntu. Simply follow the apt-get instructions here: http://wiki.myriadrf.org/Packaging I figure that a lot of people (both developers and users) can benefit from the shared effort. If you find a bug, have a request, or want to get involved; please let us know, we would love to hear it: https://discourse.myriadrf.org/c/projects/packaging On the windows side of things, I am pleased to announce the PothosSDR installer/development environment; which now includes around 40 open source projects. We just updated to the latest GNURadio/GrOsmoSDR, and recently additions include GQRX, gr-rds, and zeromq support. Instructions for GNURadio/GRC and GQRX users: https://github.com/pothosware/PothosSDR/wiki/GNURadio https://github.com/pothosware/PothosSDR/wiki/GQRX Special thanks to Andrew Back and Myriadrf for all of the support and hosting the software! Thanks, -josh

1 0

Distinction between librtlsdr and rtl-sdr repositories
by Murat Tologlu 25 Jan '16

25 Jan '16

Hi, I appreciate very much to receive your comments on the distinctions between steve-m/libsrtlsdr and keenerd/rtl-sdr (forked from pinkavaj/rtl-sdr 129 commit ago and maintained). Both have very similar structure, flies, purpose but the software is not exactly same. There are something attractive for me in one of them while the other one is also good. İs it possible to create patch from one of them and apply to the other to merge two repos together?? Why I am asking is, rtl-sdr has a new agc - aggressive agc option which is useful for me but I prefer to stay on librtlsdr; is there a solution? Thanks in advance, Murat.

1 0

peekSDR
by Magnus Paulsson 16 Jan '16

16 Jan '16

I’ve been playing with a python application to scan, find and record strong signals. I attached the code with the hope that someone would like to improve it … maybe put it on sourceforge or github. I will not have time to do anything about it for a few weeks. Works at least with linux … haven’t tried OSX or win. Needs: numpy, scipy, matplotlib, npyscreen (https://pypi.python.org/pypi/npyscreen/), pyrtlsdr (https://github.com/roger-/pyrtlsdr/releases [use the old release, new code python 3 only]) start with: python peekSDR.py -d (in one window to start database) python peekSDR.py -vr (in one window to start radio scanning) python peekSDR.py -g (in one window to start user interface) [can be run on different computers as long as you have the same filesystem and stand in the same directory] in the user interface “f” plots ffts of recorded signals. “1” starts gqrx with the recorded signal. Best wishes - Magnus

1 0

Re: [rtl-sdr][PATCH 1/2] rtl_fm: Add scanner progress
by Nikolay Dimitrov 16 Jan '16

16 Jan '16

Oops, forgot to CC the mailing list. On 09/21/2015 12:47 PM, Nikolay Dimitrov wrote: > Hi Dimitri, > > On 07/04/2015 03:42 PM, Nikolay Dimitrov wrote: >> Add scanner progress, including signal and squelch levels. >> Rename demod_state->conseq_squelch to demod_state->squelch_conseq. >> >> The scanner progress feature can be tested like this: >> >> ./rtl_fm -f 144.000M:146.000M:25k -M fm -s 48k -l 100 -t 5 | aplay \ >> -r 48k -f S16_LE -t raw -c 1 >> >> Signed-off-by: Nikolay Dimitrov <picmaster(a)mail.bg> >> --- >> src/rtl_fm.c | 43 +++++++++++++++++++++++++++++-------------- >> 1 file changed, 29 insertions(+), 14 deletions(-) > > Can you please take a look at this patch and decide whether it's worthy > of applying to the rtl-sdr tree? > > Thanks in advance. Regards, > Nikolay

1 1

[PATCH] clear warnings about compare signed-unsigned values
by P 11 Jan '16

11 Jan '16

This just removes few annoying warnings. About the conversion of string to signed int. - dev_index = boost::lexical_cast< unsigned int >( hackrf_serial ); + dev_index = boost::lexical_cast< int >( hackrf_serial ); hackrf_device_list_open checks if value of dev_index is out of range (eg negative) and returns proper error. In future negative value can be used for something so this check is not necessary nor wanted. P

2 1

← Newer
1
...
41
42
43
44
45
46
47
...
91
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-sdr