osmocom-sdr

osmocom-sdr@lists.osmocom.org

1 participants
910 discussions

bug report
by Al Smith 14 Feb '14

14 Feb '14

I'm getting some errors when using gnuradio-companion with the osmocom source that I think might be a bug related to this patch: cgit.osmocom.org/gr-osmosdr/commit/?id=e5f7b28093c10f05d272bcf12c6c4b6583af… This is the output I get: Using Volk machine: avx_32_mmx_orc gr-osmosdr v0.1.0-66-g154c4ddd (0.1.1git) gnuradio 3.7.1 built-in source types: file fcd rtl_tcp bladerf rfspace [bladeRF source] Using nuand LLC bladeRF #0 SN 909d...c10c FW v1.6.1 FPGA v0.0.2 Failed to set out of bound frequency: 1.37912e+08 aUaUaUaUaUaUaU When I look at the patch in the commit I linked above that error relates to setting the input frequency. There are 2 expected parameters get_freq_range( chan ).start() get_freq_range( chan ).stop() but in the GUI osmocom source there is only Ch0 Frequency (center) and Ch0 Bandwidth, both of which I have set. I don't see a way to define the start and stop frequency which seems to be generating this error.

3 4

rtl_fm question
by Keith Conger 12 Feb '14

12 Feb '14

Hi, I would love to see rtl_fm get support to connect to a rtl_tcp server. Are there any plans to add this? Thanks -- Keith Conger keith DOT conger AT gmail DOT com http://thecongers.org

3 2

how to build gr-osmosdr for GnuRadio wheezy-raspbian distribution on Raspberry Pi
by Murat Toloğlu 11 Feb '14

11 Feb '14

Hi All, I have easily and smoothly installed GnuRadio 3.7.2.1 on Raspberry Pi with this procedure: 1. Add the following entry to the /etc/apt/sources.list file: deb http://mirrordirector.raspbian.org/raspbian/ jessie main contrib non-free rpi (reboot after modification) 2. sudo apt-get update 3. sudo apt-get install gnuradio Installation completed in about 1 hour and GnuRadio together with GnuRadio Companion Works on my RPi. However, when it comes to build Gr-Osmosdr trouble starts. I couldn't pass the CMAKE stage of Gr-Osmosdr build process. I remembered and applied the classical "export PATH, PYTHOPATH, LD_LIBRARY_PATH, PKG_CONFIG_PATH correction" and added necessary lines at the end of ./.bashrc . My install directory was /usr (without /local) !?? anyway I've added /usr/bin, /usr/lib ..etc. to appropriate places but this couldn't be a solution. Cmake couldn't find GnuradioConfig.cmake file, I found this file of the same version on my other computer running without problem and copied the missed file into correct directory on Rpi. This couldn't be the solution either. Then, Cmake couldn't locate gnuradio-runtime.pc file, similarly I copied gnuradio-runtime.pc of same version from another computer to RPi but this couldn't be a solution either. Now I get the same error message of this : http://gnuradio.org/redmine/issues/591 (Unable to compile out of tree projects due to wrong FindGnuradio.cmake) I am really tired. I have enough experience on installing - uninstalling Gnuradio building from the source, I have made this install uninstall building process several times but I am first time trying installation of a built gnuradio. Is there a way of recovering the existing install and continue building out of tree projects ? I appreciate your help, Kind regards 73 Murat TA1DB

1 0

odd results working at 250ksp/s
by David Jacobowitz 10 Feb '14

10 Feb '14

Hi, I've been working on a project the involves tuning VOR signals. They are narrow band signals. > 25 kHz. For that, the wide bandwidth of the RTL dongles isn't that helpful to me. (and actually a hindrance when two signals are inside the sample range but widely different strengths) Anyway, the lowest I can get my dongles (R820T) to go is 250ksps, which is fine. I've been working at that frequency for awhile, but getting some strange results. For example, if I tune in to 116.8 MHz, which should be the OAK VOR, it works fine. But if I tune to 115.8 MHz, which should be the SFO VOR I get ... the OAK VOR. That is, there is a perfect copy of the OAK signal 1 MHz shifted down. If I switch the sample rate to 1.024Msps or 900ksps, I don't get this problem. I don't understand what is happening here. 1 MHz is an even multiple of 250kHz, so maybe I'm getting an image of OAK overpowering the relatively weaker SFO signal. But should there not be filters that manage this? I guess I was expecting that if the device is set to 250ksps, then it would "close down" filters appropriately to reject signals out of that band. But maybe the filters don't work properly below a certain sample rate? Like the rtl2832 can sample down to 250ksps, but the 820T tuner was not designed for it? Or perhaps I'm doing something wrong? Can I control the filters directly? I'm glad I find this issue because I was going nuts thinking my software had some mysterious bug. But I can reproduce this issue just with SDR# or whatever. :-) Regards. Dave J

6 14

pfb_decimator_ccf(13): insufficient connected input ports (5 needed, 1 connected)
by JIANG Pin A 10 Feb '14

10 Feb '14

Hi, all I try to re-structure the osmo-tetra to work with GNU Radio 3.7. The osmo-tetra is based on GNU Radio 3.6. The original code has tuner, resampler, demodulater three modules which connected sequentially. The resampler is based on function pfb_decimator_ccf which changes from 3.6 to 3.7. The pfb_decimator_ccf only take single parameter decimation, which changes in 3.7, After reading the manual of 3.7, I made following changes to the python script : Add a low-pass filter " taps = filter.firdes.low_pass_2(1, fs, options.low_pass, options.low_pass * 0.2, attenuation_dB=ATT, window=filter.firdes.WIN_BLACKMAN_hARRIS) " Change "self.resamp = blks2.pfb_decimator_ccf(int(rerate)) " to " self.resamp = filter.pfb_decimator.ccf(int(rerate), taps, 0) " But error still occurs when connecting modules " self.connect(self.src, self.tuner, self.resamp, self.demod, self.output) " : Traceback (most recent call last): File "./osmosdr-tetra_demod_fft.py", line 264, in <module> tb.Run(True) File "/usr/local/lib/python2.7/dist-packages/grc_gnuradio/wxgui/top_block_gui.py", line 82, in Run self.Start(start, max_nouts) File "/usr/local/lib/python2.7/dist-packages/grc_gnuradio/wxgui/top_block_gui.py", line 73, in Start self.start() File "/usr/local/lib/python2.7/dist-packages/gnuradio/gr/top_block.py", line 103, in start top_block_start_unlocked(self._tb, max_noutput_items) File "/usr/local/lib/python2.7/dist-packages/gnuradio/gr/runtime_swig.py", line 4612, in top_block_start_unlocked return _runtime_swig.top_block_start_unlocked(*args, **kwargs) RuntimeError: pfb_decimator_ccf(13): insufficient connected input ports (5 needed, 1 connected) Does it indicate pfb_decimator_ccf take 5 inputs ? It puzzled me. Best Regards, Jiang Pin

1 0

OsmoDevCon 2014: CFP
by Sylvain Munaut 05 Feb '14

05 Feb '14

Dear all, Time has come to fill out the "Talks/Discussions/Workshop / Hacking" section of the wiki page. If you have something you'd like to present, talk about or hack on, add it there. A simple descriptive title along with an estimated duration is enough. I guess we'll collect those for 2/3 weeks and then start making the schedule. Cheers, Sylvain

1 0

UNSUBSCRIBE
by Jeff Miller 01 Feb '14

01 Feb '14

Jeff Miller 360.630.5073 _____ No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4259 / Virus Database: 3684/7048 - Release Date: 01/31/14

1 0

new FM demodulator
by Anders Lynge Esbensen 01 Feb '14

01 Feb '14

Hi and thanks for a great tool set. I've implemented a faster FM demodulator for rlt_fm. Its an instantaneous frequency demodulator, like the already implemented atan method, but it uses some math tricks to get rid of the the actual atan calculation. Feel free to use it if you wish Best regards Anders

10 22

RE: kalibrate-rtl results...
by Jiao Xianjun 31 Jan '14

31 Jan '14

Though GSM spec has frequency hopping option, it can be switched on or off by operator. Yes, most operator switch it on. I think You too are talking different thing. GSM doesn't hops inside each 200khz channel. It hops among multiple 200khz channel. There is an exception: The downlink broadcasting carrier which carries FCCH SCH BCCH etc doesn't hop, and accordingly uplink RACH carrier doesn't hop either. These two uplink and downlink carrier frequency have a fixed 45MHz spacing if I recall correctly. I think most of calibration programs use downlink broadcasting carrier to calibrate the dongle, because it doesn't hop and is easy to be captured. You may also try my matlab calibration tool: https://github.com/JiaoXianjun/multi-rtl-sdr-calibration -----Original Message----- From: "Nikos Balkanas" <nikos.balkanas(a)eyeonix.com> Sent: ‎2014/‎1/‎31 19:13 To: "Ralph A. Schmid, dk5ras" <ralph(a)schmid.xxx> Cc: "osmocom-sdr(a)lists.osmocom.org" <osmocom-sdr(a)lists.osmocom.org>; "Richard Koch" <n1gp(a)hotmail.com> Subject: Re: kalibrate-rtl results... On Fri, Jan 31, 2014 at 12:47 PM, Ralph A. Schmid, dk5ras <ralph(a)schmid.xxx> wrote: GSM does not hop around inside its channel, this is wrong, the frequency is +- some Hz accurate, at least in normal western European commercial GSM networks. Are you sure about that? Check it out: https://svn.berlin.ccc.de/projects/airprobe/wiki/A Legend of first picture. If still in doubt that *most" GSM carriers are hoppers, use rtl_power to scan your region ;-) Nikos Ralph. From: osmocom-sdr-bounces(a)lists.osmocom.org [mailto:osmocom-sdr-bounces@lists.osmocom.org] On Behalf Of Nikos Balkanas Sent: Thursday, January 30, 2014 7:35 PM To: Richard Koch Cc: osmocom-sdr(a)lists.osmocom.org Subject: Re: kalibrate-rtl results... On Thu, Jan 30, 2014 at 8:21 PM, Richard Koch <n1gp(a)hotmail.com> wrote: I'm attempting to calibrate my RTL dongles. I notice they are all about 2-4khz off if I compare against a known broadcast station's frequency. I am trying out kalibrate-rtl and am getting varied results. I am in the US, so I did a 'kal -s EGSM -g 20' and got the following: chan: 991 (928.4MHz + 26.986kHz) power: 448020.99 chan: 1002 (930.6MHz - 5.631kHz) power: 320357.07 chan: 1003 (930.8MHz + 16.192kHz) power: 109489.92 Then 'kal -c CHANNELNUM -g 20' for each channel number. I then get the results below which the average frequency error looks different for each channel. It is consistent though if I run them multiple times. I would have expected less frequency error since I know that it is really only about 4Khz off. Or am I not reading the results correctly? Results seem OK. Do not forget that most BSTs hop around in their allotted 20 Khz channel. So a result of +/- 20 Khz shouldn't surprise you. Best calibrate against "anchor" BSTs that are steady. And yes, recommendation is to calibrate against 3 BSTs and correct for the average or stddev if you wish... Nikos -Rick Using device 0: Generic RTL2832U OEM Found Fitipower FC0013 tuner Exact sample rate is: 270833.002142 Hz Setting gain: 100.0 dB kal: Calculating clock frequency offset. Using E-GSM-900 channel 991 (928.4MHz) average [min, max] (range, stddev) + 21.342kHz [17837, 27433] (9596, 3402.206299) overruns: 0 not found: 199 average absolute error: -22.988 ppm Using device 0: Generic RTL2832U OEM Found Fitipower FC0013 tuner Exact sample rate is: 270833.002142 Hz Setting gain: 100.0 dB kal: Calculating clock frequency offset. Using E-GSM-900 channel 1002 (930.6MHz) average [min, max] (range, stddev) - 11.529kHz [-15293, -5679] (9614, 3640.780273) overruns: 0 not found: 194 average absolute error: 12.389 ppm Using device 0: Generic RTL2832U OEM Found Fitipower FC0013 tuner Exact sample rate is: 270833.002142 Hz Setting gain: 100.0 dB kal: Calculating clock frequency offset. Using E-GSM-900 channel 1003 (930.8MHz) average [min, max] (range, stddev) + 14.283kHz [9462, 19098] (9636, 4777.044922) overruns: 0 not found: 126 average absolute error: -15.345 ppm

1 0

RE: How to get IQ samples from multiple rtl-sdr dongles inasynchronized manner?
by Jiao Xianjun 31 Jan '14

31 Jan '14

while, I can try it, and let's see. Actually, maybe I will turn it to C some time in the future. -----Original Message----- From: "Ron Senykoff" <rsenykoff(a)gmail.com> Sent: ‎2014/‎1/‎30 23:04 To: "Jiao Xianjun" <putaoshu(a)gmail.com> Cc: "jdow" <jdow(a)earthlink.net>; "osmocom-sdr(a)lists.osmocom.org" <osmocom-sdr(a)lists.osmocom.org> Subject: Re: How to get IQ samples from multiple rtl-sdr dongles inasynchronized manner? Hi Jiao, Thanks for your work on this. I'm curious if Octave could be used for some of this. -Ron / KB1UMH On Wed, Jan 29, 2014 at 10:14 PM, Jiao Xianjun <putaoshu(a)gmail.com> wrote: > Hi everybody, > > Let me report current progress of this thread. > > Now my matlab program can detect and correct sampling and carrier (both > phase and frequency) error for dongles, and show the sampling phase > difference between two dongles (at 8X oversampling rate) after correction. > > You can try it by yourself here : > https://github.com/JiaoXianjun/multi-rtl-sdr-calibration > > Some runs results have also been attached here. (time location of FCCH SCH > and BCCH have also been shown there in different color) > > In the attached pictures, you may find that from the GSM frame point of view > those FCCH, SCH and BCCH from two dongles seem almost in the same time > location. (this needs to be verified further by check/demodulate information > carried in SCH and BCCH, which is still under development). But if we > inspect the time location in a 8X oversampling scale (zoom-in), there is a > fixed sampling phase difference between two dongles (after correction > respectively). > > Unfortunately, this fixed sampling phase difference may vary from run to run > (one rum means we restart rtl_tcp). > Fortunately, it remains fixed in a single run. This offers us a opportunity > to track continuous input I&Q (don't re-run rtl_tcp!) from multiple dongles, > and needn't worry about phase/sampling jumping/discontinuous things. > > Why do carrier and sampling error estimation and correction respectively? > Inspired by James Peroulas james(a)peroulas.com (author of Lte-Cell-Scanner), > for example, when there is a non-coherent up/down-converter used outside > dongle (like MMDS LNB used by Omri Iluz omri(a)iluz.net to detect 2.4GHz band > signal), there won't be strict relationship between sampling error (which is > in baseband) and carrier error (which may be located in inside dongle or > outside dongle mixer). > > But for my in-hands dongles, sampling error and carrier seems have > relationship. This may be because they have common clock source inside > dongle. > > Which I detected by my matlab program gsm_sync_demod.m: > dongle 1: sampling PPM 27.1739, carrier PPM -28.513 > dongle 2: sampling PPM 116.3043, carrier PPM -118.4247 > > In my program a positive sampling PPM means sampling clock is slower than > standard/ideal source (in our case, this source is GSM base-station). If LO > of mixer uses the same clock as sampling, that may cause a lower LO in > mixer/down-converter. I guess the LO frequency of mixer in dongle is higher > than input antenna RF frequency, which means for mixer: output = LO - input. > Thus a lower LO generates a lower input into baseband, that's why I get a > negative carrier PPM (negative carrier PPM means detected carrier frequency > is lower than standard/ideal source). > I don't know if my guess is correct. Anyone is familiar with the hardware > architecture of the 820t dongle? > > BR > > Jiao Xianjun > > > > > On Wed, Jan 8, 2014 at 5:23 PM, jdow <jdow(a)earthlink.net> wrote: >> >> The last I looked rtl_tcp did not allow full control over the dongle. But, >> then, to do what I really want has required bypassing rtlsdr to go >> directly to the usb library so I can access the underlying USB system >> directly for a specific feature. (A feed through feature in rtlsdr's >> shared library would be nice when trying to nail down the dongle's >> identity for restoring context on program startup.) >> >> (Building an SDR program without multi-threading is rather like trying >> to build a bicycle without chains or cables. It can be done. But it's >> a pathetic tool when you get done with it. Erm, but I do note gear >> driven bikes need less maintenance under adverse conditions. Been there >> done that - MANY decades ago.) >> >> {^_^} Joanne/W6MKU >> >> >> On 2014/01/07 23:32, Jiao Xianjun wrote: >>> >>> Good idea. >>> >>> Thanks for your advice! >>> >>> But that seems we will do some repeating works. >>> >>> rtl_tcp already use mutiple buffers and multi-threading. So why not use >>> it >>> directly as a reliable relay. >>> >>> >>> On Tue, Jan 7, 2014 at 1:51 AM, jdow <jdow(a)earthlink.net >>> <mailto:jdow@earthlink.net>> wrote: >>> >>> Have you tried using ping-pong buffers? Process on one buffer and >>> receive >>> to another. You may have to use multi-threading to make this work >>> nicely. >>> >>> {^_^} Joanne/W6MKU >>> >>> >>> >>> On 2014/01/06 01:34, Jiao Xianjun wrote: >>> >>> Hi, >>> >>> Today I did some experiments using CW signal which is generated >>> by signal >>> generator. The conclusion is a little bit sad. >>> >>> sync read and UDP lose samples/data high probably: >>> 1. If there are some other operations (which costs some time) >>> between two >>> successive sync reads, some samples will be lost. >>> 2. Some times, UDP packets are just lost. >>> >>> So, seems that I have two choices: >>> 1. struggle to use async read mode. >>> 2. use rtl_tcp utility directly, which is offered with rtl-sdr >>> code. This >>> program use async mode and TCP, which has avoided the two >>> shortcomings I >>> addressed. >>> >>> I will try the 2nd method, and try to move on with calibration. >>> >>> BR >>> >>> Jiao Xianjun >>> >>> >>> >>> On Sat, Jan 4, 2014 at 8:34 PM, Jiao Xianjun <putaoshu(a)gmail.com >>> <mailto:putaoshu@gmail.com> >>> <mailto:putaoshu@gmail.com <mailto:putaoshu@gmail.com>>> wrote: >>> >>> Hi, >>> >>> I have questions on usage of rtlsdr_read_sync(dev, buffer, >>> out_block_size, >>> &n_read): >>> >>> For example, if sampling rate is 1Msps, and out_block_size >>> is 1000000, >>> question is: >>> >>> 1. the rtlsdr_read_sync() will cost 1s exactly? Or is there >>> any >>> lower level >>> device/driver buffer, which perhaps feed rtlsdr_read_sync() >>> with >>> history >>> data quickly and makes rtlsdr_read_sync() return in a time >>> shorter >>> than 1s? >>> >>> 2. in this infinite processing loop: >>> while(1) >>> { >>> rtlsdr_read_sync(dev, buffer, out_block_size, &n_read); >>> processing_function(buffer); // let's assume that this cost >>> 0.001s >>> } >>> Those samples during the 0.001s processing period will be >>> losted or >>> not? Is >>> there any method to not lost them? >>> >>> Thanks very much! >>> >>> BR >>> >>> Jiao Xianjun >>> >>> >>> >>> On Thu, Jan 2, 2014 at 9:25 PM, Jiao Xianjun >>> <putaoshu(a)gmail.com >>> <mailto:putaoshu@gmail.com> >>> <mailto:putaoshu@gmail.com <mailto:putaoshu@gmail.com>>> >>> wrote: >>> >>> I see some UDP packet performance issues in my laptop >>> (but not >>> in my >>> desktop computer). Will the common (interleave multiple >>> receives) UDP >>> link helps? >>> >>> The issue is that fread for the second dongle in matlab >>> get >>> less data >>> than expectation sometimes. Seem that fread for the >>> first >>> dongle works well. >>> >>> >>> ------------------------------__------------------------------__-------------------- >>> >>> From: Sdr Guru <mailto:sdrguru1@gmail.com >>> <mailto:sdrguru1@gmail.com>> >>> >>> Sent: 2014/1/2 5:39 >>> >>> To: osmocom-sdr(a)lists.osmocom.org >>> <mailto:osmocom-sdr@lists.osmocom.org> >>> <mailto:osmocom-sdr@lists.__osmocom.org >>> >>> <mailto:osmocom-sdr@lists.osmocom.org>> >>> >>> >>> Subject: Re: How to get IQ samples from multiple rtl-sdr >>> dongles in >>> asynchronized manner? >>> >>> Hi >>> >>> rtl-sdr-relay >>> Some of the recommendations. >>> Please add PPM error calculation, exactly like new >>> rtl_test -p >>> but multiple receivers simultaneously. >>> It provides immediate information if something is wrong >>> with >>> USB or dongles. >>> >>> https://github.com/keenerd/__rtl-sdr/commit/__b5f89dcf40463130e717b6c9bb3a3… >>> >>> <https://github.com/keenerd/rtl-sdr/commit/b5f89dcf40463130e717b6c9bb3a39a3c…> >>> https://github.com/keenerd/__rtl-sdr/blob/master/src/rtl___test.c >>> >>> <https://github.com/keenerd/rtl-sdr/blob/master/src/rtl_test.c> >>> >>> Please add automatic eeprom PPM calibration >>> >>> https://github.com/keenerd/__rtl-sdr/commit/__ecf267737ca52f5005b7a12a35230… >>> >>> >>> <https://github.com/keenerd/rtl-sdr/commit/ecf267737ca52f5005b7a12a352307e8c…> >>> >>> default sample rate 2.4M (28.8/12) or 1.2M (28.8/24), >>> probably >>> lower jitter >>> MAX_NUM_DEV 4->16 :) >>> >>> Some nice to have features. >>> ip binding >>> multicast support >>> one common (interleaved) stream of all the receivers >>> timestamped stream >>> >>> I'm trying to convert MATLAB script to Ocatve. >>> >>> SG >>> >>> On Mon, Dec 30, 2013 at 9:38 AM, Jiao Xianjun >>> <putaoshu(a)gmail.com <mailto:putaoshu@gmail.com> >>> <mailto:putaoshu@gmail.com <mailto:putaoshu@gmail.com>>> >>> wrote: >>> >>> Hi guys, >>> >>> For the multiple dongles synchronization in signal >>> level >>> instead of >>> bits/packets level, I setup a working repo in >>> github, and >>> write a >>> initial demo framework. See below: >>> >>> https://github.com/__JiaoXianjun/multi-rtl-sdr-udp-__relay.git >>> >>> <https://github.com/JiaoXianjun/multi-rtl-sdr-udp-relay.git> >>> >>> You may find information and instruction of demo >>> quickly by >>> reading >>> the README. >>> >>> My initial purpose is performing in-fly calibration >>> for >>> multiple >>> dongles according to some pre-known signal (GSM, >>> ADS-B?) to >>> let them >>> work together coherently. >>> >>> An ideal scheme may be that we should generate a >>> very >>> narrow band >>> and very week signal in (or just located at the edge >>> of) target >>> working band of dongles, and perform the software >>> in-fly >>> calibration >>> in background (or driver level). This would be user >>> friendly. >>> >>> I know it is far from final state currently, and >>> many >>> things are not >>> clear yet (See TODO). But please join me if you also >>> think >>> this is a >>> good idea. Just check out the demo and run it to >>> have a look. >>> >>> Currently I just test the demo in Ubuntu-Linux. >>> >>> BR >>> >>> Jiao Xianjun > >

1 0

← Newer
1
...
52
53
54
55
56
57
58
...
91
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-sdr