osmocom-sdr

osmocom-sdr@lists.osmocom.org

917 discussions

Status of Hardware
by Mark Richards 18 Feb '16

18 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 24 Jan '16

24 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 15 Jan '16

15 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 10 Jan '16

10 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

gr-osmosdr setting value in destructor
by P 10 Jan '16

10 Jan '16

Hi, there is in gr-osmosdr a lot of code like: hackrf_source_c::~hackrf_source_c () { ... free(_buf); _buf = NULL; } } Setting value in destructor have sense in two case: - they are used in some way in destructor of parent class - You set then to something like 0xDEADBEEF and when pointer from already destroyed class is used it will cause segfault. Setting value to NULL is contraproductive because there is a lot of checks if value is not NULL, this actually can hide some troubles of calling something using already freed pointer. I'm suggesting to remove this kind of code. I will prepare patch but now I'm waiting if those two pending patches I have send before would be accepter or not. Is there any opinion which oppose previous claim? With best regards, JP.

2 1

gr-osmosdr broken on OSX due to MSG_NOSIGNAL
by Elliot Saba 10 Jan '16

10 Jan '16

It looks like the block to redefine MSG_NOSIGNAL as SO_NOSIGPIPE inside of redpitaya_common.cc needs to be copied into redpitaya_sinc_c.cc as well. -E

4 3

osmocom_fft won't tune BladeRF lower than 300MHz
by Ben Z en de rest 29 Dec '15

29 Dec '15

Hi. Today I installed latest gr-osmosdr. I want to run osmocom_fft and view the recorded file in "inspectrum". Osmocom_fft starts, runs, knows there is a BladeRF available and does work. only thing is that it does not allow tuning lower then 300 MHz as if the transverterboard is unknown to the osmocom_fft. I tried to start osmocom_fft with -a balderf but that does not help. If I set it to for example 145M it gives this message: Failed to set out of bound frequency: 1.45e+08 libbladerf is updated last weekend. Any ideas on this ? Thanks, Ben

1 0

← Newer
1
...
42
43
44
45
46
47
48
...
92
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-sdr