From loic.cloatre at amossys.fr Fri Jul 1 13:19:14 2016 From: loic.cloatre at amossys.fr (loic.cloatre) Date: Fri, 01 Jul 2016 13:19:14 -0000 Subject: [Help] first steps with sdrangelove Message-ID: Hello, I have installed all the thing and I get the main API: How to configure in order to see LoRa trafic? (if I click on aquisition, I get an error message "no sample source configured") Maybe a quickstart help exists? Thanks, Lo?c From mail at mueller-martin.net Tue Jul 19 22:06:44 2016 From: mail at mueller-martin.net (=?utf-8?Q?Martin_M=C3=BCller?=) Date: Wed, 20 Jul 2016 00:06:44 +0200 Subject: [Help] first steps with sdrangelove In-Reply-To: References: Message-ID: > Hello, Hi! > I have installed all the thing and I get the main API: What do you mean by ?get the main API?? > How to configure in order to see LoRa trafic? If you mean LoRaWAN (I never looked at it before) I think you should expect the signal to be around 868 MHz if you?re in Europe and 915 MHz in the US [1]. You have to set this frequency in the rotary digit display on the left either by typing, scrolling the mouse wheel while hovering the mouse pointer over a digit by or selecting a digit and using the up or down arrow keys. (Note: You have to enter the frequency in kHz!) But this first requires sample acquisition to be running which comes to you error message: > (if I click on aquisition, I get an error message "no sample source configured?) The error message you get on starting sample acquisition probably means that there was no SDR device found. What software defined radio device are you using? > Maybe a quickstart help exists? I fear there is no more information available than provided on the sparse website :( Maybe posting relevant output in the console might help. Regards Martin From lucas at teske.net.br Fri Jul 22 17:55:23 2016 From: lucas at teske.net.br (Lucas Teske) Date: Fri, 22 Jul 2016 14:55:23 -0300 Subject: post a new release In-Reply-To: <56DBB263.3020301@teske.net.br> References: <22229.11656.562788.73052@airborne.nrl.navy.mil> <56DB2C77.6030005@teske.net.br> <56DB9518.6010200@teske.net.br> <56DBB263.3020301@teske.net.br> Message-ID: Ok so I merged two PRs in the repository that contains the Infrared APIs. I tested and works fine, might be usefull. Since we added features since the original branch, I made a PR to change the version to 0.6 ( https://github.com/librtlsdr/librtlsdr/pull/12 ) What do you think guys? Lucas On 06/03/2016 01:30, Lucas Teske wrote: > Ok so I had some spare time now and I decided to add the Bandwidth > parameters to rtl_tcp and rtl_fm, since they are very usefull to > reduce out-of-band noises. I made a Pull Request from my BWChanges > Branch to the Development Branch. If anyone is available to review my > Pull Request, it is here: > > https://github.com/librtlsdr/librtlsdr/pull/1 > > I hope it helps :D > > Lucas > > Em 05/03/2016 23:25, Lucas Teske escreveu: >> Ok so I merged some forks into mine. I'll wait for Joseph to add me >> as a librtlsdr organization member to merge it with the organization >> repo. >> >> https://github.com/racerxdl/librtlsdr >> >> So basically I added the SDR# manual gains change to the librtlsdr ( >> from https://sourceforge.net/projects/sdrr820tmanualgainsettings/ ) >> Then I merged Hayati changes to the DC Filter from >> https://github.com/hayguen/librtlsdr >> >> I am taking a look into Alexander Kurpiers changes ( >> https://github.com/dl8aau/librtlsdr/tree/devel1 ) before merging >> because he did a lot more commits and also he also added the Manual >> Gains to the code. So I will take a look and test both codes. >> >> Lucas >> >> Em 05/03/2016 15:59, Lucas Teske escreveu: >>> Sure! That is good! :D >>> >>> If you can add me, I will in a few hours have some free time to >>> merge my fork changes into it. >>> >>> Also anyone that have a working fork please send the link to the >>> repos so I can check it. >>> >>> On 05/03/2016 14:47, Joseph Poirier wrote: >>>> fyi - I just created a librtlsdr organization on github >>>> (github.com/librtlsdr ) and cloned >>>> https://github.com/steve-m/librtlsdr to it. >>>> >>>> It would be nice to aggregate a list of the most interesting forks >>>> and attempt to merge some of the features and/or fixes in, and >>>> possibly get this fork tagged as the canonical fork for packages, >>>> users, etc. If we can get some sort of a majority approval that is. >>>> >>>> I'll be more than happy to add permissions for people and/or pass >>>> it off to someone that might have more time than myself to manage. >>>> >>>> cheers, >>>> joe >>>> >>>> On Mon, Feb 29, 2016 at 11:50 PM, A. Maitland Bottoms >>>> wrote: >>>> >>>> Henk writes: >>>> > Oeps, sorry forgot to quote the original post of joseph. >>>> > >>>> > +1 >>>> > Hmm in my opinion rtl_sdr is the next best thing since the >>>> invention >>>> > of canned beer :) since it liberated the airwaves for allot >>>> of users. >>>> > >>>> > Regards, >>>> > henk >>>> > >>>> > On Sun, Feb 28, 2016 at 7:11 PM, Joseph Poirier >>>> > wrote: >>>> > > If would be nice to have a newer official release >>>> available; installation >>>> > > using the package manager on many Linux distros gets a two >>>> year old >>>> > > librtlsdr that's missing the rtlsdr_set_tuner_bandwidth >>>> function (added >>>> > > about nine months ago), as well as, other nice updates and >>>> fixes. >>>> > > >>>> > > cheers, >>>> > > joe >>>> >>>> Oh yes, Debian Jessie did not release with rtlsdr bandwidth >>>> setting code. >>>> But, the rtl-sdr currently available in Debian unstable, >>>> testing and >>>> jessie-backports include current git HEAD code - >>>> v0.5.3-12-ge3c03f7. >>>> (based upon git://git.osmocom.org/rtl-sdr.git >>>> ) >>>> >>>> So, while the Debian source package starts from the v0.5.3 tag, >>>> I use >>>> the 3.0 (quilt) source format to also include more recent git >>>> commits. >>>> https://sources.debian.net/src/rtl-sdr/0.5.3-5/debian/patches/ >>>> >>>> Ubuntu Wily Werewolf and Xenial Xerus also contain rtl-sdr based on >>>> v0.5.3-12-ge3c03f7. >>>> >>>> A release would be good. I'd be happy to reduce the amount of stuff >>>> in the debian/ packaging directory - the various man pages could >>>> be adopted upstream, as well as the improve-librtlsdr-pc-file and >>>> improve-scanning-range-parsing patches. >>>> >>>> And a gpg signed tarball release, or even just a gpg signed tag >>>> would be a help in establishing source code integrity. A new >>>> release >>>> for osmocom might indeed help synchronize the various >>>> distributions. >>>> >>>> Thanks for keeping me informed, >>>> -Maitland >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chibill110 at gmail.com Sun Jul 31 23:24:41 2016 From: chibill110 at gmail.com (Bill Gaylord) Date: Sun, 31 Jul 2016 18:24:41 -0500 Subject: Compiling rtlsdr for windows. Message-ID: I know there is a precompiled binary but it is 2 years out of date. Anyone have any luck compiling it for 32 bit windows? (I need some functionality that was just recently added in) -------------- next part -------------- An HTML attachment was scrubbed... URL: From f.meyer-hermann at gsg-elektronik.de Mon Jul 25 11:13:13 2016 From: f.meyer-hermann at gsg-elektronik.de (f.meyer-hermann at gsg-elektronik.de) Date: Mon, 25 Jul 2016 13:13:13 +0200 Subject: PATCH: Fixed arbitrary resampling in rtl_fm Message-ID: <20160725111313.GA15278@gsg-elektronik.de> As already on github, I fixed rtl_fm's arbitrary resampling by fixing the output buffer length and allowing upsampling by copying the audio data since the algorithm cannot work in-place. I have attached a patch, if you are interested to integrate it into the official branch. Regards, Ferdinand Meyer-Hermann