osmocom-sdr

osmocom-sdr@lists.osmocom.org

1 participants
910 discussions

rtl-entropy, atmospheric radio noise entropy source
by Paul Warren 16 Feb '13

16 Feb '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi guys, I just finished my first go at an entropy gathering tool for rtl-sdr, it's licensed under GPL (will add LICENSE file next!) and available at: https://github.com/pwarren/rtl-entropy My aim was to have a utility that ran with a minimum of dependencies, so it could be done easily on a raspberry pi, and without trying to get a whole gnuradio stack working! I'm not a crypto expert, but I've read enough to know that you really should pass the output through rng-test or similar before using. As I mention in the Readme, I plan on doing these tests and eventually getting it to the stage where the entropy can be plumbed in to /dev/random. So, thanks for making the rtl-sdr libraries and making them easy to work with! Cheers - -- Paul Warren -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlEeKZQACgkQkwz3ZmaDjV4e+QCeMG6rOr+PZ+yHnIeXGFJRnpsr e9oAn3vQBEW7L2mcJLJE0tyNUnZpGori =dlzx -----END PGP SIGNATURE-----

3 2

info
by Massimo Borlis 13 Feb '13

13 Feb '13

Hi, message to the developer, you can also add this device, id: (15a4-9016-00) device: AF15BDA (v7.3.20.1) thanks waiting response. The drive is USB dikom

2 1

Trouble using E4000 on new Dell Vostro
by Ethan Trewhitt 08 Feb '13

08 Feb '13

I have been unable to get basic tuning functionality out of my E4000 on my new laptop, in Ubuntu Precise. I'm running 64-bit Precise with the Osmocom drivers installed via the GNU Radio setup script. When I attempt to use the RTL device in Linux, the following occurs: " $ rtl_test Found 1 device(s): 0: ezcap USB 2.0 DVB-T/DAB/FM dongle Using device 0: ezcap USB 2.0 DVB-T/DAB/FM dongle Found Elonics E4000 tuner Supported gain values (14): -1.0 1.5 4.0 6.5 9.0 11.5 14.0 16.5 19.0 21.5 24.0 29.0 34.0 42.0 Reading samples in async mode... cb transfer status: 1, canceling... Library error 0, exiting... Segmentation fault (core dumped) " When I run the system in GDB and request a backtrace, this is all I get: " Program received signal SIGSEGV, Segmentation fault. 0x00007ffff6ed42e5 in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 (gdb) bt #0 0x00007ffff6ed42e5 in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 #1 0x00007ffff6ed447f in libusb_close () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 #2 0x00007ffff7bc51a9 in rtlsdr_close () from /usr/local/lib/librtlsdr.so.0 #3 0x0000000000401322 in main () " So there is apparently some issue with libusb. This machine has four USB 3.0 ports, and I've tried using all four of them. There's no hub, but nor are there any USB 2.0 ports to try. Here's the relevant output of usb-devices: " T: Bus=03 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=2838 Rev=01.00 S: Manufacturer=Realtek S: Product=RTL2838UHIDIR S: SerialNumber=00000947 C: #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) I: If#= 1 Alt= 0 #EPs= 0 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) " Note that I have had easy success using the dongle in 64-bit Windows 7 (through the Zadig-installed drivers and SDRSharp), as well as in the same version of Ubuntu installed on another laptop (an older HP Envy). So I know the dongle works, and I know it theoretically can work with the Osmocom drivers, albeit in a different machine. Any ideas? Thanks in advance. Ethan

1 0

Multiple dongles 1 rtl-server
by Mathison Ott 05 Feb '13

05 Feb '13

Im hopping to spark up a diolog to help to rewrite the RTL-server that the group has produced... I currently use the RTL-server with the ghpsdr-alex DSP-server. I have some code that alows the RTL-server to see multible dongles... the Problem is that unlike the Softrock-server a qtradio user cant select between the different receivers when connecting. The DSP-server needs mods to accept a tcp packet from a RTL-server with multiple RTL-dongles attached to its hardware. Keep in mind could the user select between dongles using a qt_radio check box, like the gain control. This could help to mange multiple qtradio client connections to a server. Say one receiver is indicated to be In Use, then a client can select the next one that isn't in use. I just found most of the rtl dongles to be usfull because of the vhf uhf spectrum they can receive. I have a few of the DVb units and I realized that i cant run more that one thou a DSP server at a time. Its could become useful to write DSP-server that hosts mixed devices. 73 Mathison KJ6DZB

2 1

Re: osmocom-sdr Digest, Vol 15, Issue 3
by Jeff Murri 04 Feb '13

04 Feb '13

> -Message: 1 > Date: Sat, 2 Feb 2013 22:49:14 +0100 > From: Benedikt Heinz <zn000h(a)gmail.com> > To: osmocom-sdr(a)lists.osmocom.org > Subject: new SDR project (bladeRF) on kickstarter > Message-ID: > <CAFXU+zENpDgdfCTZu-U17GbMw-xg4BifyyPu4BwzTjK9p_mn5Q(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi everyone, > > just stumbled across this SDR on kickstarter: > http://www.kickstarter.com/projects/1085541682/bladerf-usb-30-software-defi… > (found via hackaday) > Maybe this is interesting for some of you. > > Cheers, > > hunz > I saw this too. It looks like a great piece of kit. Doesn't the dollars he's asking seem a bit steep though? Maybe not, and I'm hoping this comes off as a serious question. If it were opened up so that the dollars asked was lower then there'd be a lot of backers, which in turn drives build costs down further? If HackRF is half as good as I think it's going to be, then the $$ is definitely way to high. Just my (possibly uninformed) opinion. --Jeff

3 2

new SDR project (bladeRF) on kickstarter
by Benedikt Heinz 03 Feb '13

03 Feb '13

Hi everyone, just stumbled across this SDR on kickstarter: http://www.kickstarter.com/projects/1085541682/bladerf-usb-30-software-defi… (found via hackaday) Maybe this is interesting for some of you. Cheers, hunz

1 0

Re: any one brave enough to help a newbie with getting started with SDR
by Alan Corey 02 Feb '13

02 Feb '13

Yes, there are a confusing number of Linuxes, that's partly why I avoid them and use OpenBSD. I think Red Hat is only commercial now, try Fedora for the closest. Ubuntu will probably work, I didn't like it because I found it too "dumbed down", meant to appeal to Windows users. Ubuntu is supposedly based on Debian, which I've had installed for a few years and like it much better. Debian is "Deb" and "Ian", Ian is a ham. >The default compiler gcc is probably what you want. You don't mention what software you're trying to build. I had no problem building the Osmocom suite under my old Debian version, no extra libraries needed. But: my understanding from somewhere is that this suite of programs (rtl_*) exists because some ARM machines like the Raspberry Pi couldn't handle Gnuradio. Gnuradio may be what you really want. > >Gnuradio (http://www.gnuradio.org) is very versatile, bordering on confusing. Part of it is the RTLSDR or Osmocom source from Osmocom which connects to the dongle. Then you use the gunradio-companion to drag and drop different signal processing blocks onto a flow graph, the output of that is a Python program which hopefully does what you want. Start at the gnuradio web site and follow the build guide. Most of the work is getting the dependancies you need installed. You don't need the parts for hardware you don't have. > >Makefiles come with various programs, but most of this uses cmake to build the actual makefiles. Typically, you cd into the source directory, mkdir build, cd build, then "cmake ../". Track down things missing/wrong, modify your cmake cache file to fix it up, then when you have no errors, do make and make install. It works pretty well because you can set options in your cache file and they migrate down the line into makefiles. Both the Osmocom stuff and Gnuradio use cmake, but you can avoid it if you want to. > >If you need sensitivity and freedom from spurious noises you might find the NooElec dongle isn't the best way to go. Take a look at >http://wavelab.homestead.com/HF_VHF_multi_index.html >I bought a dozen of the MC13535 chips from http://www.futurlec.com for $1.20 each, plus the ceramic filters, crystals, etc. If you don't need frequency agility they might work out well. Futurlec isn't fast, but they have some good deals. > > Alan > > > >----- >Radio Astronomy - the ultimate DX > > > >>________________________________ >> From: Wayne Sanders <wsanders(a)xplornet.com> >>To: osmocom-sdr(a)lists.osmocom.org >>Sent: Thursday, January 31, 2013 11:40 PM >>Subject: any one brave enough to help a newbie with getting started with SDR >> >>Good day all >> I know that this may nor be the proper or correct place to request some basic assistance but I will tempt the wrath of the few. >> First off has the packaging for Linux changed there are many more versions now compared to 24 years ago when I dabbled with it running a packet radio bbs. It was Red Hat country then. Now ? >> Any way My questions are of the where to start kind. >> >> Step 1 Have selected Ubuntu as the o/s got it installed >> >> step 2 need to know what form of compiler is needed. >> Worked 28 years ago with Borland's C++ >> >> Step 3 what are the liberaies that I require and where may they >> be found. >> >> Step 4 And of course a suitable Make File. >> >> As all can see I am jut renewing a friend ship with a very powerfull o/s and of course are having the steep learning curve all over again. But expect that I will enjoy it. >> Project at this time is using the NooElec R820T SDR & DVB-T >> Dongle to monitor an number of frequencys in the >> analoge area 54mhz up for Pasive radar detection of >> meteors. >>Thanking all in advance. >> If the above questions are deemed off topic again I apoligize and would request that a direct e-mail answer to wsanders(a)xplornet.com be used if it should not be posted >>I remain wayne sanders ve7duc and RDL-OBS observatory >> >> >> >>Wayne Sanders >> >> >> >> > >

1 0

any one brave enough to help a newbie with getting started with SDR
by Wayne Sanders 01 Feb '13

01 Feb '13

Good day all I know that this may nor be the proper or correct place to request some basic assistance but I will tempt the wrath of the few. First off has the packaging for Linux changed there are many more versions now compared to 24 years ago when I dabbled with it running a packet radio bbs. It was Red Hat country then. Now ? Any way My questions are of the where to start kind. Step 1 Have selected Ubuntu as the o/s got it installed step 2 need to know what form of compiler is needed. Worked 28 years ago with Borland's C++ Step 3 what are the liberaies that I require and where may they be found. Step 4 And of course a suitable Make File. As all can see I am jut renewing a friend ship with a very powerfull o/s and of course are having the steep learning curve all over again. But expect that I will enjoy it. Project at this time is using the NooElec R820T SDR & DVB-T Dongle to monitor an number of frequencys in the analoge area 54mhz up for Pasive radar detection of meteors. Thanking all in advance. If the above questions are deemed off topic again I apoligize and would request that a direct e-mail answer to wsanders(a)xplornet.com be used if it should not be posted I remain wayne sanders ve7duc and RDL-OBS observatory Wayne Sanders

1 0

how about: rtl_drm?
by Alan Corey 01 Feb '13

01 Feb '13

Just an idea, really, I don't know how complex the decoding is. Or rtl_fm for Android? Just got an upconverter for my dongle, sitting here listening to music from faraway exotic places on HF. Using rtlsdr.dll with SDR#. Alan ----- Radio Astronomy - the ultimate DX

2 1

rtl_tcp port for Android
by Мартин Маринов 31 Jan '13

31 Jan '13

I am pleased to announce I have released an RTL2832U driver for android for the benefit of all of the developers working on SDR. The app could be found here https://play.google.com/store/apps/details?id=marto.rtl_tcp_andro And the sources are released under GPL2+ here https://github.com/martinmarinov/rtl_tcp_andro- So how do you use it in case you want to develop your own Android application that uses rtl_tcp_andro? It's quite simple, you need to add just one line of code to your existing Android app (assuming the user has the driver installed). *startActivityForResult(new Intent(Intent.ACTION_VIEW).setData(Uri.parse("iqsrc://-a 127.0.0.1 -p 123", START_REQ_CODE);* Where START_REQ_CODE is a random number you assign. This will start rtl_tcp_andro on the localhost at port 123. As you see the thing after iqsrc:// is just the command line arguments you pass to a regular rtl_tcp. If you want to be more fancy and do error capture, you should override this method in your Android activity and perform error detection as so: *@Override* * protected void onActivityResult(final int requestCode, final int resultCode, final Intent data) {* * * * runOnUiThread(new Runnable() {* * * * @Override* * public void run() {* * if (requestCode == START_REQ_CODE) {* * if (resultCode == RESULT_OK) { // rtl_tcp_andro has been started successfully!}* * else {* * * * try {* * switch (data.getIntExtra("marto.rtl_tcp_andro.RtlTcpExceptionId", -1)) {* * case 0:* * // exception - permission denied* * break;* * case 1:* * // exception - root required* * break;* * case 2:* * // exception - no devices found* * break;* * case 4:* * // exception - the user needs to reconnect the device* * break;* * default:* * // unknown exception* * break;* * }* * } catch (Exception e) {}* * }* * }* * }* * });* * }* It is that simple! rtl_tcp_andro will take care of showing different dialogs to the user for device selection. It will also take care of non-rooted devices by communicating with rtl_tcp_androi and sending the appropriate file descriptors, etc. You don't need to worry about all of the magic that is happening in the background - you only need to monitor the result of your intent request. If you get *RESULT_OK* then you are ready to go. Now what remains is to implement your own TCP client that connects to the appropriate host/port number and communicates using the *rtl_tcp* protocol. Make sure you send the additional "exit" command that rtl_tcp_andro has in order not to leave zombie services behind. That's all if you have any questions, feel free to contact me! Sorry for the bad state of the source code of rtl_tcp_andro, I will add comments as time passes by. Hope to see great new projects on the Android platform :) Thanks, Martin

3 2

← Newer
1
...
73
74
75
76
77
78
79
...
91
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-sdr