From laforge at gnumonks.org  Wed Mar  1 10:41:05 2017
From: laforge at gnumonks.org (Harald Welte)
Date: Wed, 1 Mar 2017 11:41:05 +0100
Subject: [hari.blogscripts@gmail.com: reg. a deadlink]
Message-ID: <20170301104105.qg6eaz6fwvob3jnp@nataraja>

FYI, this was in my personal inbox but is probably better adressed by
the people on this list.

Regards,
	Harald
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)
-------------- next part --------------
An embedded message was scrubbed...
From: Hari prasad <hari.blogscripts at gmail.com>
Subject: reg. a deadlink
Date: Wed, 1 Mar 2017 14:20:14 +0530
Size: 4081
URL: <http://lists.osmocom.org/pipermail/osmocom-sdr/attachments/20170301/54abc4b1/attachment.eml>

From martin.m at suddenlink.net  Sat Mar 11 20:57:31 2017
From: martin.m at suddenlink.net (Martin McCormick)
Date: Sat, 11 Mar 2017 14:57:31 -0600
Subject: Recording rtl_fm output
Message-ID: <E1cmo4x-0001vj-FW@localhost>

	Something I am doing is not quite right. The following
example works almost perfectly but please read on.

rtl_fm -f 88.3e6 -M wbfm -s 215000 -r 44100 - | aplay -r 44.1k -f S16_LE

The audio from the sound card is nearly excellent.

	To record this stream, I do the following:

rtl_fm -f 88.3e6 -M wbfm -s 215000 -r 44100 testfile.bin

I get a file so it would appear that the following should sound
just like the stream I am listening to using the pipe in the
first example.

aplay -r 44.1k -f S16_LE testfile.bin

	The pitch of the audio is fine but instead of almost dead
silence between words, there is a lot of hiss and 
distortion. In theory, I should hear the same mostly noiseless
audio I hear in the first example when playing from the file.

	This is really not a DSP issue but maybe I have saved the
audio as unsigned and am trying to play it signed which would
preserve the pitch but be a cause for a lot of distortion.
Besides, it is apparently signed when piped in to aplay.

	I am mystified.

	Thanks.

Martin McCormick


From martin.m at suddenlink.net  Tue Mar 14 01:59:23 2017
From: martin.m at suddenlink.net (Martin McCormick)
Date: Mon, 13 Mar 2017 20:59:23 -0500
Subject: Recording rtl_fm output Solved
In-Reply-To: <E1cmo4x-0001vj-FW@localhost>
References: <E1cmo4x-0001vj-FW@localhost>
Message-ID: <E1cnbkB-0003nA-Rh@localhost>

	I made a mistake, all right. We have a radio station
affiliated with a university, here. There is a transmitter meant
for this city on 88.3 MHZ and another transmitter on 91.7 MHz
serving Oklahoma City. Both transmitters are easily receivable
here but the 88.3 MHZ transmitter is much stronger. If I use that
transmitter and attach any kind of antenna to the dongle, the
audio is distorted, apparently because it overloads the device.
There was also an audible whine on either signal which wasn't too
loud, but was distracting.

	I finally discovered that I could get an almost perfect
signal from the nearer 88.3 MHZ transmitter and the whine went
away if I changed the 200 KHZ output sample rate to 215 KHZ.

	FM stations in North America often transmit a digital
stream containing a digital version of their analog signal plus a
second unrelated digital stream of classical music or alternative
program material.

	The carrier for this digital stream is near 200 KHZ and I
think the 200 KHZ sampling frequency heterodynes with the data
carrier.

	If one sets this sampling rate to 500 KHZ, for example,
you can hear the data carrier mixed in with the audio. What you
hear is a noise like an electric motor running in the background.

	I set the shell script that directly feeds the stream to
the sound card to listen to our 88.3 MHZ signal and forgot to
change the recording script also to 88.3. It was still on 91.7
and I just missed that omission since I see both 88.3 and 91.7 a
lot when experimenting with the scripts.

	After discovering the mistake and setting the record
script to 88.3 MHZ, the data recorded are producing sound that is
the same, now as one would expect.

	I was using a very limited antenna for reception of the
local signal so the more distant signal was audible but just
barely.

Martin


From james.clark131 at gmail.com  Thu Mar  9 15:49:17 2017
From: james.clark131 at gmail.com (James Clark - KC3CDV)
Date: Thu, 9 Mar 2017 10:49:17 -0500
Subject: Technical help, umm I think?
Message-ID: <613DEAA7-CAFB-4B40-A3EB-C53DED4815BF@gmail.com>

Hello all, not sure if this will go through or if Ive to subscribe or even if this is the rite place for help like this.
 I am on a mac running the latest OSX updates and I am waiting for my new SDR to get to me from amazon, Ive got CubicSDR and also Gqrx on the system, well my question is will I be able to just plug and play or will I have to install macports and all that other stuff that goes over my head.
Do I have to use turminal? Me trying to use that thing is like a fish trying to live out of water for a year, its vary unlikely it will happen effectivly.
 Also let me say rite up front please don?t post any photos because I cant see your photos.

 I hope this is the rite place to ask this question, thank you in advanced.


 
  
May Peace Be With You.  Active skywarn severe weather spotter and Community Collaborative Rain, Hail & Snow Network operative. 
@HomefrontHugs  Volunteer for our Troops and Families



From qiuyuexue at icloud.com  Thu Mar  9 15:39:34 2017
From: qiuyuexue at icloud.com (XueQiuyue)
Date: Thu, 09 Mar 2017 23:39:34 +0800
Subject: Questions about error when using Osmocom sink
Message-ID: <0F4738A9-A401-40A3-BB06-B8F7EC6E541D@icloud.com>

Dear Mr/Ms,

I meet errors when use osmocom sink and source in GNU Radio, I have tried BladeRF and HackRF, and I use Ubuntu 16.04.

1.When I use BladeRF, I set the parameters as 
"bladerf=701c2ce1da297914cb29695ba79fac54,fpga=<'/Users/qiuyuexue/Documents/BladeRF/hostedx115-latest.rbf'>,fpga-reload=1,buffers=32,buflen=4096,transfers=16,stream_timeout_ms=3000,loopback=none,verbosity=silent,xb200.?

and I got error as:
?(top_block.py:4795): IBUS-WARNING **: The owner of /home/ceca_517/.config/ibus/bus is not root!
gr-osmosdr v0.1.4-86-ge9dde9af (0.1.5git) gnuradio 3.7.10
built-in sink types: hackrf bladerf redpitaya file 
Opening nuand bladeRF with device identifier string: "*:serial=701c2ce1da297914cb29695ba79fac54"
[bladeRF sink] Loading FPGA bitstream </home/ceca_517/LPWAN/SOAR at PKU/LPWAN/BladeRF/hostedx115-latest.rbf>...
[bladeRF sink] bladerf_load_fpga has failed with -11
[bladeRF sink] Warning: 'loopback' has been specified on a bladeRF sink, and will have no effect. This parameter should be specified on the associated bladeRF source."




2.when I use HackRF, I set the parameter as 
"hackrf=393b4b,bias=1,bias_tx=1,buffers=32.?

and I got error as:
"(top_block.py:5108): IBUS-WARNING **: The owner of /home/ceca_517/.config/ibus/bus is not root!
gr-osmosdr v0.1.4-86-ge9dde9af (0.1.5git) gnuradio 3.7.10
built-in sink types: hackrf bladerf redpitaya file 

FATAL: bad lexical cast: source type value could not be interpreted as target

Trying to fill up 1 missing channel(s) with null sink(s).
This is being done to prevent the application from crashing
due to gnuradio bug #528.?

I want to know if I set the parameters wrong? Or anything else? Thanks a lot for your help and your time!  Thanks very much!!


Best,
Qiuyue



From andreas.eriksen at icloud.com  Fri Mar 10 06:55:57 2017
From: andreas.eriksen at icloud.com (Andreas Eriksen)
Date: Fri, 10 Mar 2017 07:55:57 +0100
Subject: RTL-SDR and RTL-TCP drivers
Message-ID: <358BBC38-BA06-4F26-B168-E43AA6C50AF7@icloud.com>

Thank you for these patches, indeed they fixed my problems with gqrx :-)


From laforge at gnumonks.org  Fri Mar 17 20:17:19 2017
From: laforge at gnumonks.org (Harald Welte)
Date: Fri, 17 Mar 2017 21:17:19 +0100
Subject: git.osmocom.org cgit improvements
Message-ID: <20170317201719.r3d6n3ab35wke4mu@nataraja>

Hi all,

today I've deployed some cgit improvements on https://git.osmocom.org/,
in the hope that it makes this tool even more useful:

1) syntax highlighting of source code (requested by Hoernchen)

The source code is now highlighted by pygments.  I don't really
understand why somebody would want to look at source code a lot in a
browser, but well, it was as easy as to enable the existing pygments
based filter plugin.


2) rendering of "about" page from README.md

As you might have noticed, I've introduced a README.md in a number of
repositoires, and cgit is now rendering an about page for every
repository, e.g. at http://git.osmocom.org/libosmo-abis/about/


3) gerrit change-ID hyperlink generation

All gerrit Change-IDs in commit messages are now automatically converted
to hyperlinks to the respective gerrit change, see e.g. the below
example:
http://git.osmocom.org/openbsc/commit/?id=6dd0fc685b7149f67a5fe17a5bce55c446aa563c

Please note that this works for the "Change-Id" line of the actual
change, but also for change-ids in the free text (e.g. "this depends on
change-id ... in libosmocore")


4) Osmocom ticket/issue hyperlink generation

Any Line that matches the "^((Relate|Close|Fixe)[ds]):" prefix is
scanned for occurrences of "OS#(\d+)" which are then amended with
hyperlinks to the respective issue on osmocom.org

Please note the OS# prefix is mandatory, so things like "OS#1614, 1615"
will not work, as can be seen at
http://git.osmocom.org/osmo-pcu/commit/?id=0a8fae8d141c2cfa4387ffe9b35402d5b8cc85cd

Please format your commit messages accordingly.

Regards,
	Harald
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)


From horiz0n at gmx.net  Sun Mar 19 11:31:18 2017
From: horiz0n at gmx.net (Dimitri Stolnikov)
Date: Sun, 19 Mar 2017 12:31:18 +0100
Subject: Questions about error when using Osmocom sink
In-Reply-To: <0F4738A9-A401-40A3-BB06-B8F7EC6E541D@icloud.com>
References: <0F4738A9-A401-40A3-BB06-B8F7EC6E541D@icloud.com>
Message-ID: <op.yxciagj2vay7ep@wopr.artelis.net>

Hi Qiuyue,

On Thu, 09 Mar 2017 16:39:34 +0100, XueQiuyue <qiuyuexue at icloud.com> wrote:

> Dear Mr/Ms,
>
> I meet errors when use osmocom sink and source in GNU Radio, I have  
> tried BladeRF and HackRF, and I use Ubuntu 16.04.
>
> 1.When I use BladeRF, I set the parameters as
> "bladerf=701c2ce1da297914cb29695ba79fac54,fpga=<'/Users/qiuyuexue/Documents/BladeRF/hostedx115-latest.rbf'>,fpga-reload=1,buffers=32,buflen=4096,transfers=16,stream_timeout_ms=3000,loopback=none,verbosity=silent,xb200.?

You have to remove <' and '> from the filename.

> 2.when I use HackRF, I set the parameter as
> "hackrf=393b4b,bias=1,bias_tx=1,buffers=32.?
>
> and I got error as:
> "(top_block.py:5108): IBUS-WARNING **: The owner of  
> /home/ceca_517/.config/ibus/bus is not root!
> gr-osmosdr v0.1.4-86-ge9dde9af (0.1.5git) gnuradio 3.7.10
> built-in sink types: hackrf bladerf redpitaya file
>
> FATAL: bad lexical cast: source type value could not be interpreted as  
> target

Remove the dot after 32, its supposed to be an integer value.

Best regards,
Dimitri


From holger at freyther.de  Sun Mar 19 20:57:57 2017
From: holger at freyther.de (Holger Freyther)
Date: Sun, 19 Mar 2017 21:57:57 +0100
Subject: git.osmocom.org cgit improvements
In-Reply-To: <20170318150931.GB3272@my.box>
References: <20170317201719.r3d6n3ab35wke4mu@nataraja>
 <20170318150931.GB3272@my.box>
Message-ID: <9437479C-B7C9-4603-B01D-EC775130F164@freyther.de>


> On 18 Mar 2017, at 16:09, Neels Hofmeyr <nhofmeyr at sysmocom.de> wrote:
> 
> 

Hi,


> All in all these are excellent improvements!
> Holger, what's the status of your promise, made one day in a chat, to make
> redmine catch the OS#123s?

lol, I love how we go from a private chat to this CC list. I have not looked at it but maybe this is something for an afternoon at Osmodevcon. It should be fairly simple with redmine.

holger