Re: [Discuss-gnuradio] pybombs bombs

[Mike]

Hi Michael,

That worked perfectly thanks.

Mike

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] Announcing GNU Radio Conference 2015

[John Malsbury]

Greetings,

We are happy and excited to finally announce GNU Radio Conference 2015!
GRCon15 is the next installment of the fastest growing SDR-focused
conference in the world.  GRCon is becoming the go-to event for for
beginners, advanced users, and core developers to exchange ideas and
information related to SDR.

Here are some brief details:

*Dates & Location*

There are several other conferences occurring in September this year.  To
avoid conflicts with those, we’ve decided to hold the conference on *August
24-28*, a bit earlier than last year.

While it has taken us some time to settle on a venue that is a good match
for this event, it was time well spent and we are very excited about the
result. The conference will be held at the Center for Strategic &
International Studies

in Washington DC.  Counting the areas designated for vendor booths, demos,
and hands-on-tutorials, the total event space is ~3 times larger than the
venue used for GRCon14.  This modern venue gives us plenty of room for
growth and comfort, is conveniently accessible by DC Metro, and is located
near many hotels and notable landmarks.

We expect about 250 attendees this year.

*The Program*

This conference is focused on practical deployment of SDR, with a heavy
focus on professional interaction and exchange.  Here’s a rough overview of
what we are planning:


   -

   An agenda packed with sessions on exciting & unique applications, new
   SDR hardware, and tutorials on new features
   -

   Several hands-on tutorials from beginner level through advanced (e.g.,
   FPGA targeting)
   -

   Multiple networking events
   -

   Working groups and hackerspaces
   -

   Vendor booths, demos, and more...


*Call for Presentations and Tutorials*

If you would like to showcase your latest work with GNU Radio and
software-defined radio please submit an abstract
.  This year, we are using
EasyChair to facilitate review and selection.  You will need to create an
account, which takes a few minutes.  The submission period will close
on *Friday,
May 8, 2015.*

*Call for Sponsors*

The year-over-year growth of GRCon since 2012 is a testament to the success
and drive of this community.  If you are in the business of
software-defined radio, do not miss out on this great opportunity to
showcase your products and services.  If you are interested in sponsoring
GRCon15, please contact us directly.

A preliminary agenda, conference info, and registration will be posted on
the web in the coming weeks.  In the meantime, help us spread the word!

Best Regards,

John Malsbury

Michael Dickens

Tom Rondeau
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Installing GNU Radio blocks as a regular user

[Martin Braun]

On 08.04.2015 06:23, Leonardo S. Cardoso wrote:

The pybombs solution looks a lot like what I was cooking up from my
side. It boils down to changing the paths (PYTHONPATH, LD_LIBRARY_PATH,
PKG_CONFIG_PATH, etc..) and installing OOT modules in a prefix in the
users’s home.

Is there anything else to pybombs that I’m missing? I there any other
advantage in using the pybombs framework that I might have missed?


Leonardo,

you might even want to install even GNU Radio yourself (i.e., your IT 
department installs nothing except for the build tools; gcc, cmake, 
boost...). With PyBOMBS, that's really easy to do. It also allows you to 
update GNU Radio versions at any time, and, more importantly, on a 
user-by-user basis. This is nice when one user needs new features from 
latest GNU Radio, but others don't want to update in order to not having 
to change their own stuff.


Cheers,
Martin


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] pccc encoder

[Achilleas Anastasopoulos]

Since your constellation is complex, then its dimensionality (in the
chunks_to_symbos block, as well as in the PCCC decoder block)
should be set to 1 (you are now have it at 2).

The convention is that the chunks_to_symbols array is arranged as

a11, a12, ... a1d, a21 a22,...,a2d,... aM1, aM2, ...aMd

so that it is to be understood as the 2 D array

a11, a12, ... a1d,
a21 a22,...,a2d,
...
aM1, aM2, ...aMd

with dimensionality d.
Then, at each instance, it outputs the "row" that is indexed by the input
symbol.


Achilleas

PS: I also suggest you make a variable "constellation" and put in there
your constellation and then input it in both
the chunks_to_symbols AND the PCCC decoder block so that you are sure you
are consistent.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] DVB-T/T2

[Ralph A. Schmid, dk5ras]

Hi,

 

Don't be worried by the Us, I am running the whole thing in a virtual machine 
that lives on a Windows tablet PC, so it is normal that Linux stutters a bit 
when Windows claims its rights. I just must not touch Windows, and everything 
is fine. 

 

OK, so I just need to set the correct bitrate, and the stream should run. 
Great. Can I keep frame rate as it is from the original video? And what do the 
stream ID fields for video and audio mean?

 

My version of the specs does not have the mentioned chapters, but I have 
already guessed something like this. It just made me curious because the 
constellation plots in the specs do not show this. Ah, here, the stuff linked 
in Wikipedia is what you referred to. My documents seem newer, but different. 
tr_101190v010302p.pdf and ts_102831v010201p.pdf


Ralph.

 

 

 

From: Bogdan Diaconescu [mailto:b_diacone...@yahoo.com] 
Sent: Wednesday, April 8, 2015 17:13
To: Ralph A. Schmid, dk5ras; 'Ron Economos'; discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] DVB-T/T2

 

Hi Ralf,

 

having Us when moving the mouse does not looks good. Can you show a picture 
taken with htop (on Linux).

 

the coding is a setting of the transmitter and receiver and it just need to be 
the same on both. It does impact the maximum bitrate of the stream as in the 
table.

 

Look into the 4.5.4 and 4.5.5 chapters. It says that reference information is 
sent at "boosted" power level with imaginary equal zero. This is what you see 
in the two dots on left and right.

 

Bogdan

 

 

 

 

 

 

 

On Wednesday, April 8, 2015 5:34 PM, "Ralph A. Schmid, dk5ras" 
 wrote:

 

Hi, 

 

The Us are when I do something else with the machine. They do not show when I 
keep my fingers off the mouse, so no reason to worry, it runs for ages without 
a single U when the machine is kept alone. 



 

I already found out about the rate. The coding also needs to be reflected by 
the transport stream, or just regarding the bitrate? I did not find a setting 
for that, but I will look deeper into it during the next days, when I find some 
time. My first test trying to set identical settings like from the working test 
stream brought just a black picture. 

 

Another question...when looking into the constellation, what are the two dot 
clouds on the X/I-axis, outside the expected 4*4 cloud matrix? Some embedded 
BPSK? I could not find this in the DVB-T specs at first glance...

 

Ralph.

 

 

From: Bogdan Diaconescu [mailto:b_diacone...@yahoo.com] 
Sent: Wednesday, April 8, 2015 2:57 PM
To: Ralph A. Schmid, dk5ras; 'Ron Economos'; discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] DVB-T/T2

 

Hi Ralph,

 

DVB-T.png shows some u's on the command line which means the whole flowgraph do 
not provide data to USRP at the right speed. It basically mean the computer 
cannot cope with the required processing requirement.

 

As for the video parameters, in the DVB-T specs 
(http://www.etsi.org/deliver/etsi_en/300700_300799/300744/01.06.01_60/en_300744v010601p.pdf)
 you will find Table 17 where the rates are presented. FYI, the settings you 
have used are 8Mhz bandwidth, QAM-16 constellation, coding 1/2, guard interval 
1/32. The video should be constant bit rate but it is not a hard requirement 
(see below).

 

If you just broadcast video from a file and not plan to use a live streaming 
from camera, the rate should not matter too much. The video is sent at the rate 
of the DVB-T according to it's parameters and with RTL2832 receiver it is 
buffered and played at the correct speed (at least for short files like 
test.ts).

 

Bogdan

 

 

On Wednesday, April 8, 2015 11:55 AM, "Ralph A. Schmid, dk5ras" 
 wrote:

 

Yep, this would be quite useful!

Bogdan, as you are here, too - I don't know very much about all the crazy video 
file stuff, but maybe you can give me some basic parameters I need to comply 
with for a transport stream, to be able to transmit it with your package?! I 
need to use Windows for the conversion, as my Linux installation is only on a 
virtual machine, with limited space and power. A capable looking Windows 
program is available, but there are so many options I have no clue about :(

 

I modified your flow graph according to Rons hints, and now I have a stable and 
reliable DVB-T transmission path with your package. See 
http://dk5ras.dyndns.org/tmp/DVB/ with a screenshot. I am using the Ettus B210, 
and for reception a second PC with DVB-T stick, or a DVB-x tester that does 
them all, DVB-C/S/S2/T/T2. 

 

You and Ron really did a great job with coding those DVB-x packages!

 

Ralph.

 

From: discuss-gnuradio-bounces+ralph=schmid@gnu.org 
[mailto:discuss-gnuradio-bounces+ralph=schmid@gnu.org] On Behalf Of Bogdan 
Diaconescu
Sent: Wednesday, April 8, 2015 8:01 AM
To: Ron Economos; discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] DVB-T/T2

 

Ok, it would be useful to have receivers too like for the DVB-T. 

 

Bogdan

 

 

On Tuesday, April 7, 2

Re: [Discuss-gnuradio] Installing GNU Radio blocks as a regular user

[Richard Bell]

Pybombs also makes updating to newer versions as they come out easy.

./pybombs update

Rich

On Wed, Apr 8, 2015 at 6:54 AM, Marcus Müller 
wrote:

>  Well, it's a great way to install popular OOTs :)
>
> On 04/08/2015 03:23 PM, Leonardo S. Cardoso wrote:
>
> Hi Marcus,
>
>  Thanks for the quick reply. The IT dept. can install any version of GNU
> Radio so no problem there :)
>
>  The pybombs solution looks a lot like what I was cooking up from my
> side. It boils down to changing the paths (PYTHONPATH, LD_LIBRARY_PATH,
> PKG_CONFIG_PATH, etc..) and installing OOT modules in a prefix in the
> users’s home.
>
>  Is there anything else to pybombs that I’m missing? I there any other
> advantage in using the pybombs framework that I might have missed?
>
>  Thanks again
>
>  BR,
>
>  Leonardo
>
>
>
>  On 08 Apr 2015, at 12:18 , Marcus Müller 
> wrote:
>
> Hi Leonardo,
>
> So this depends on your situation: If you're allowed to get arbitrary
> software installed by asking IT, I'd ask them to install a recent
> version of GNU Radio (at *least* 3.7.2, the newer, the better).
> Possibly, only outdated versions are in your IT's software package
> repositories, so you might need them to build and install from source;
> they might refuse.
>
> If that's the case, or you can't ask for arbitrary software:
> use pyBombs[1]! It allows installation in a directory prefix of your
> choice. Choose "src" as only viable method of software installation.
> After pybombs has finished doing its thing, you get a shell script that
> you can use to modify the environment variables, so that if you just use
> that script in your ~/.bashrc, you will have a system that has a working
> GNU Radio, completely without leaving the boundaries of your non-root
> user. Downside is that everything that's not on your system (or in an
> outdated version) has to be built from source, which will take quite
> some time and storage. Afterwards, if all these PCs are the same, you
> can just copy the prefix folder to every user's home directory.
>
> Either way, you'll (hopefully) have a working GNU Radio installation
> afterwards.
> Now, if you used pybombs, you'll already have a prefix directory in your
> user's home where your OS will look for when loading libraries etc.
> Otherwise, use pybombs now (./pybombs config; ./pybombs env; echo
> "source $prefix/setup_env.sh" >> ~/.bashrc) to generate the empty
> directory and generate a path-bending script.
>
> When building your student's OOT's, you'd go the normal "cd gr-mymodule;
> mkdir build; cd build; cmake ..; make; make install;" route, only that
> you'd replace "cmake .." with "cmake
> -DCMAKE_INSTALL_PREFIX=/home/userXYZ/prefixdirectory .."; afterwards,
> "make install" will install the things into prefixdirectory; awesome!
>
> Best regards,
> Marcus
>
> [1]http://gnuradio.org/redmine/projects/pybombs/wiki/QuickStart
>
> On 04/08/2015 11:52 AM, Leonardo S. Cardoso wrote:
>
> Hi everyone,
>
> We’re trying to implement a GNU Radio course here in Lyon (France) where
> we take the students step-by-step into coding GR modules. At some point
> we’d like them to follow the out-of-tree modules tutorial but we’ve
> stumbled upon an unfortunate limitation: the IT guys of our university wont
> allow root access on any computer, meaning that we can compile but cannot
> install the blocks...
>
> I come to you guys, to ask for advices on how to implement this. I have
> some ideas already but I’d like to see if there is any “best practice” ways
> to do this.
>
> Best regards,
>
> Leonardo Cardoso
>
>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] DVB-T/T2

[Bogdan Diaconescu]

Hi Ralf,
having Us when moving the mouse does not looks good. Can you show a picture 
taken with htop (on Linux).

the coding is a setting of the transmitter and receiver and it just need to be 
the same on both. It does impact the maximum bitrate of the stream as in the 
table.

Look into the 4.5.4 and 4.5.5 chapters. It says that reference information is 
sent at "boosted" power level with imaginary equal zero. This is what you see 
in the two dots on left and right.
Bogdan





 


 On Wednesday, April 8, 2015 5:34 PM, "Ralph A. Schmid, dk5ras" 
 wrote:
   

 #yiv2904105420 #yiv2904105420 -- _filtered #yiv2904105420 
{font-family:Helvetica;panose-1:2 11 6 4 2 2 2 2 2 4;} _filtered #yiv2904105420 
{panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv2904105420 
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}#yiv2904105420 
#yiv2904105420 p.yiv2904105420MsoNormal, #yiv2904105420 
li.yiv2904105420MsoNormal, #yiv2904105420 div.yiv2904105420MsoNormal 
{margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;}#yiv2904105420 a:link, 
#yiv2904105420 span.yiv2904105420MsoHyperlink 
{color:blue;text-decoration:underline;}#yiv2904105420 a:visited, #yiv2904105420 
span.yiv2904105420MsoHyperlinkFollowed 
{color:purple;text-decoration:underline;}#yiv2904105420 
p.yiv2904105420msonormal, #yiv2904105420 li.yiv2904105420msonormal, 
#yiv2904105420 div.yiv2904105420msonormal 
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv2904105420 
p.yiv2904105420msoacetate, #yiv2904105420 li.yiv2904105420msoacetate, 
#yiv2904105420 div.yiv2904105420msoacetate 
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv2904105420 
p.yiv2904105420balloontext, #yiv2904105420 li.yiv2904105420balloontext, 
#yiv2904105420 div.yiv2904105420balloontext 
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv2904105420 
p.yiv2904105420msochpdefault, #yiv2904105420 li.yiv2904105420msochpdefault, 
#yiv2904105420 div.yiv2904105420msochpdefault 
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv2904105420 
p.yiv2904105420msonormal1, #yiv2904105420 li.yiv2904105420msonormal1, 
#yiv2904105420 div.yiv2904105420msonormal1 
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv2904105420 
p.yiv2904105420msoacetate1, #yiv2904105420 li.yiv2904105420msoacetate1, 
#yiv2904105420 div.yiv2904105420msoacetate1 
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv2904105420 
p.yiv2904105420balloontext1, #yiv2904105420 li.yiv2904105420balloontext1, 
#yiv2904105420 div.yiv2904105420balloontext1 
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv2904105420 
p.yiv2904105420msochpdefault1, #yiv2904105420 li.yiv2904105420msochpdefault1, 
#yiv2904105420 div.yiv2904105420msochpdefault1 
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv2904105420 
span.yiv2904105420msohyperlink {}#yiv2904105420 
span.yiv2904105420msohyperlinkfollowed {}#yiv2904105420 
span.yiv2904105420msohyperlink1 {}#yiv2904105420 
span.yiv2904105420msohyperlinkfollowed1 {}#yiv2904105420 
span.yiv2904105420sprechblasentextzchn1 {}#yiv2904105420 
span.yiv2904105420e-mailformatvorlage191 {}#yiv2904105420 
span.yiv2904105420e-mailformatvorlage201 {}#yiv2904105420 
span.yiv2904105420e-mailformatvorlage231 {}#yiv2904105420 
span.yiv2904105420e-mailformatvorlage241 {}#yiv2904105420 
span.yiv2904105420e-mailformatvorlage39 {}#yiv2904105420 
p.yiv2904105420msonormal2, #yiv2904105420 li.yiv2904105420msonormal2, 
#yiv2904105420 div.yiv2904105420msonormal2 
{margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;}#yiv2904105420 
span.yiv2904105420msohyperlink2 
{color:blue;text-decoration:underline;}#yiv2904105420 
span.yiv2904105420msohyperlinkfollowed2 
{color:purple;text-decoration:underline;}#yiv2904105420 
p.yiv2904105420msonormal3, #yiv2904105420 li.yiv2904105420msonormal3, 
#yiv2904105420 div.yiv2904105420msonormal3 
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv2904105420 
p.yiv2904105420msoacetate2, #yiv2904105420 li.yiv2904105420msoacetate2, 
#yiv2904105420 div.yiv2904105420msoacetate2 
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv2904105420 
p.yiv2904105420balloontext2, #yiv2904105420 li.yiv2904105420balloontext2, 
#yiv2904105420 div.yiv2904105420balloontext2 
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv2904105420 
p.yiv2904105420msochpdefault2, #yiv2904105420 li.yiv2904105420msochpdefault2, 
#yiv2904105420 div.yiv2904105420msochpdefault2 
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv2904105420 
p.yiv2904105420msonormal11, #yiv2904105420 li.yiv2904105420msonormal11, 
#yiv2904105420 div.yiv2904105420msonormal11 
{margin:0cm;margin-bottom:.0001pt;font-size:11.0pt;color:black;}#yiv2904105420 
span.yiv2904105420msohyperlink11 
{color:blue;text-decoration:underline;}#yiv2904105420 
span.yiv2904105420msohyperlinkfollowed11 
{color:purple;text-decoration:underline;}#yiv2904105420 
p.yiv2904105420msoacetate11, #yiv2904105420 li.yiv2904105420msoacetate11, 
#yiv2904105420 div.yiv2904105420msoacetate11 
{margin:0cm;margin-bottom:.0001pt;font-size

[Discuss-gnuradio] X Window System error

[Activecat]

Dear Sir,

I've just install gnuradio using pybombs, and manually install the missing
python-opengl using apt-get.
Unfortunately below error occurs when I execute a flowgraph.

  Executing:
"/home/sgku/Dropbox/gnuradio/gr-activecat/examples/jitter/top_block.py"
  Using Volk machine: avx_64_mmx
  The program 'python2' received an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 2351 error_code 8 request_code 70 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the --sync command line
 option to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error()
function.)


Please advise if you have a quick fix to this.
My system and version info is available at [1].
Thank you very much.

[1]. https://github.com/activecat/gnuradio/blob/master/system_info.txt
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] DVB-T/T2

[Ralph A. Schmid, dk5ras]

Hi, 

 

The Us are when I do something else with the machine. They do not show when I 
keep my fingers off the mouse, so no reason to worry, it runs for ages without 
a single U when the machine is kept alone. 

 

I already found out about the rate. The coding also needs to be reflected by 
the transport stream, or just regarding the bitrate? I did not find a setting 
for that, but I will look deeper into it during the next days, when I find some 
time. My first test trying to set identical settings like from the working test 
stream brought just a black picture. 

 

Another question...when looking into the constellation, what are the two dot 
clouds on the X/I-axis, outside the expected 4*4 cloud matrix? Some embedded 
BPSK? I could not find this in the DVB-T specs at first glance...

 

Ralph.

 

 

From: Bogdan Diaconescu [mailto:b_diacone...@yahoo.com] 
Sent: Wednesday, April 8, 2015 2:57 PM
To: Ralph A. Schmid, dk5ras; 'Ron Economos'; discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] DVB-T/T2

 

Hi Ralph,

 

DVB-T.png shows some u's on the command line which means the whole flowgraph do 
not provide data to USRP at the right speed. It basically mean the computer 
cannot cope with the required processing requirement.

 

As for the video parameters, in the DVB-T specs 
(http://www.etsi.org/deliver/etsi_en/300700_300799/300744/01.06.01_60/en_300744v010601p.pdf)
 you will find Table 17 where the rates are presented. FYI, the settings you 
have used are 8Mhz bandwidth, QAM-16 constellation, coding 1/2, guard interval 
1/32. The video should be constant bit rate but it is not a hard requirement 
(see below).

 

If you just broadcast video from a file and not plan to use a live streaming 
from camera, the rate should not matter too much. The video is sent at the rate 
of the DVB-T according to it's parameters and with RTL2832 receiver it is 
buffered and played at the correct speed (at least for short files like 
test.ts).

 

Bogdan

 

 

On Wednesday, April 8, 2015 11:55 AM, "Ralph A. Schmid, dk5ras" 
mailto:ra...@schmid.xxx> > wrote:

 

Yep, this would be quite useful!

Bogdan, as you are here, too - I don't know very much about all the crazy video 
file stuff, but maybe you can give me some basic parameters I need to comply 
with for a transport stream, to be able to transmit it with your package?! I 
need to use Windows for the conversion, as my Linux installation is only on a 
virtual machine, with limited space and power. A capable looking Windows 
program is available, but there are so many options I have no clue about :(

 

I modified your flow graph according to Rons hints, and now I have a stable and 
reliable DVB-T transmission path with your package. See 
http://dk5ras.dyndns.org/tmp/DVB/ with a screenshot. I am using the Ettus B210, 
and for reception a second PC with DVB-T stick, or a DVB-x tester that does 
them all, DVB-C/S/S2/T/T2. 

 

You and Ron really did a great job with coding those DVB-x packages!

 

Ralph.

 

From: discuss-gnuradio-bounces+ralph=schmid@gnu.org 
  
[mailto:discuss-gnuradio-bounces+ralph=schmid@gnu.org] On Behalf Of Bogdan 
Diaconescu
Sent: Wednesday, April 8, 2015 8:01 AM
To: Ron Economos; discuss-gnuradio@gnu.org  
Subject: Re: [Discuss-gnuradio] DVB-T/T2

 

Ok, it would be useful to have receivers too like for the DVB-T. 

 

Bogdan

 

 

On Tuesday, April 7, 2015 11:23 PM, Ron Economos mailto:w...@comcast.net> > wrote:

 

Only transmitter implementations for now. They are here:

https://github.com/drmpeg/gr-dvbs2

https://github.com/drmpeg/gr-dvbt2

The DVB-T2 implementation supports T2-Lite, tone reservation PAPR reduction and 
MISO processing.

Ron

On 04/07/2015 06:38 AM, Bogdan Diaconescu wrote:

Hi Ron,

 

I have not followed the development of DVB-T2/S2 lately. Are there receiver 
implementations for the T2/S2 or just transmitters?

 

Thanks,

Bogdan

 

 

On Tuesday, April 7, 2015 1:32 PM, "Ralph A. Schmid, dk5ras"  
  wrote:

 

Great to hear that you work finds its way into the official thing! 

 

At the moment, as the RF stuff works, I am trying to learn about all this crazy 
video file stuff, for being able to create transport streams with my own 
content. Up to now I am still testing with the cartoon .ts :) Still my laptop 
(with DVBViewer software) will not decode the audio, while the DVB tester 
decodes audio just fine. 

 

Ralph.

  

 

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org  
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

 

 

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] pybombs bombs

[Tom Rondeau]

On Wed, Apr 8, 2015 at 2:43 AM, Mike Willis  wrote:

> Hi Tom,
>
>
>
> I understand your point and it’s a general problem with modules in the
> recipes that are included by default that if any one of them fails to
> build, so does the system. Imagine if I had no USRP and didn’t even know
> what one was. If I came to install Gnuradio it would fail under this
> system. I would need to know there is a USRP list and subscribe to it, even
> without any usrp. So, really the issue is the pybombs recipe including
> things that are not part of gnuradio by default. Effectively they become
> part of the system by doing that.
>
>
>
> Mike
>

Hi Mike, I know no one likes to be told that they've asked the question in
the wrong place like this -- I've been there before myself. But you asked a
question that could be better answered elsewhere, so that's where I pointed
you. I wasn't trying to be dismissive.

Tom




>
>
> *From:* trond...@trondeau.com [mailto:trond...@trondeau.com] *On Behalf
> Of *Tom Rondeau
> *Sent:* 08 April 2015 00:32
> *To:* Mike Willis
> *Cc:* Richard Bell; GNURadio Discussion List
> *Subject:* Re: [Discuss-gnuradio] pybombs bombs
>
>
>
> On Tue, Apr 7, 2015 at 7:12 PM, Mike Willis  wrote:
>
> Hi Tom.
>
>
>
> I think this is the right place as UHD is part of the standard Gnuradio
> build, so it doesn’t really matter if you have a usrp or not, it will crash
> the build.
>
>
>
> Mike
>
>
>
> It's technically an optional dependency, required only for gr-uhd. The
> failure you're experiencing it happening when building libuhd, which is not
> a GNU Radio project.
>
>
>
> As I said, if this is a failure in the PyBOMBS uhd recipe, that's our
> concern. A problem in libuhd itself is something that the usrp-users list
> would be much better place to get help on this problem.
>
>
>
> Tom
>
>
>
>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Installing GNU Radio blocks as a regular user

[Marcus Müller]

Well, it's a great way to install popular OOTs :)

On 04/08/2015 03:23 PM, Leonardo S. Cardoso wrote:
> Hi Marcus,
>
> Thanks for the quick reply. The IT dept. can install any version of
> GNU Radio so no problem there :)
>
> The pybombs solution looks a lot like what I was cooking up from my
> side. It boils down to changing the paths (PYTHONPATH,
> LD_LIBRARY_PATH, PKG_CONFIG_PATH, etc..) and installing OOT modules in
> a prefix in the users’s home.
>
> Is there anything else to pybombs that I’m missing? I there any other
> advantage in using the pybombs framework that I might have missed?
>
> Thanks again
>
> BR, 
>
> Leonardo
>
>
>
>> On 08 Apr 2015, at 12:18 , Marcus Müller > > wrote:
>>
>> Hi Leonardo,
>>
>> So this depends on your situation: If you're allowed to get arbitrary
>> software installed by asking IT, I'd ask them to install a recent
>> version of GNU Radio (at *least* 3.7.2, the newer, the better).
>> Possibly, only outdated versions are in your IT's software package
>> repositories, so you might need them to build and install from source;
>> they might refuse.
>>
>> If that's the case, or you can't ask for arbitrary software:
>> use pyBombs[1]! It allows installation in a directory prefix of your
>> choice. Choose "src" as only viable method of software installation.
>> After pybombs has finished doing its thing, you get a shell script that
>> you can use to modify the environment variables, so that if you just use
>> that script in your ~/.bashrc, you will have a system that has a working
>> GNU Radio, completely without leaving the boundaries of your non-root
>> user. Downside is that everything that's not on your system (or in an
>> outdated version) has to be built from source, which will take quite
>> some time and storage. Afterwards, if all these PCs are the same, you
>> can just copy the prefix folder to every user's home directory.
>>
>> Either way, you'll (hopefully) have a working GNU Radio installation
>> afterwards.
>> Now, if you used pybombs, you'll already have a prefix directory in your
>> user's home where your OS will look for when loading libraries etc.
>> Otherwise, use pybombs now (./pybombs config; ./pybombs env; echo
>> "source $prefix/setup_env.sh" >> ~/.bashrc) to generate the empty
>> directory and generate a path-bending script.
>>
>> When building your student's OOT's, you'd go the normal "cd gr-mymodule;
>> mkdir build; cd build; cmake ..; make; make install;" route, only that
>> you'd replace "cmake .." with "cmake
>> -DCMAKE_INSTALL_PREFIX=/home/userXYZ/prefixdirectory .."; afterwards,
>> "make install" will install the things into prefixdirectory; awesome!
>>
>> Best regards,
>> Marcus
>>
>> [1]http://gnuradio.org/redmine/projects/pybombs/wiki/QuickStart
>>
>> On 04/08/2015 11:52 AM, Leonardo S. Cardoso wrote:
>>> Hi everyone,
>>>
>>> We’re trying to implement a GNU Radio course here in Lyon (France)
>>> where we take the students step-by-step into coding GR modules. At
>>> some point we’d like them to follow the out-of-tree modules tutorial
>>> but we’ve stumbled upon an unfortunate limitation: the IT guys of
>>> our university wont allow root access on any computer, meaning that
>>> we can compile but cannot install the blocks...
>>>
>>> I come to you guys, to ask for advices on how to implement this. I
>>> have some ideas already but I’d like to see if there is any “best
>>> practice” ways to do this.
>>>
>>> Best regards,
>>>
>>> Leonardo Cardoso
>>>
>>>
>>>
>>> ___
>>> Discuss-gnuradio mailing list
>>> Discuss-gnuradio@gnu.org 
>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>>
>> ___
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org 
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Installing GNU Radio blocks as a regular user

[Leonardo S. Cardoso]

Hi Marcus,

Thanks for the quick reply. The IT dept. can install any version of GNU Radio 
so no problem there :)

The pybombs solution looks a lot like what I was cooking up from my side. It 
boils down to changing the paths (PYTHONPATH, LD_LIBRARY_PATH, PKG_CONFIG_PATH, 
etc..) and installing OOT modules in a prefix in the users’s home.

Is there anything else to pybombs that I’m missing? I there any other advantage 
in using the pybombs framework that I might have missed?

Thanks again

BR, 

Leonardo



> On 08 Apr 2015, at 12:18 , Marcus Müller  wrote:
> 
> Hi Leonardo,
> 
> So this depends on your situation: If you're allowed to get arbitrary
> software installed by asking IT, I'd ask them to install a recent
> version of GNU Radio (at *least* 3.7.2, the newer, the better).
> Possibly, only outdated versions are in your IT's software package
> repositories, so you might need them to build and install from source;
> they might refuse.
> 
> If that's the case, or you can't ask for arbitrary software:
> use pyBombs[1]! It allows installation in a directory prefix of your
> choice. Choose "src" as only viable method of software installation.
> After pybombs has finished doing its thing, you get a shell script that
> you can use to modify the environment variables, so that if you just use
> that script in your ~/.bashrc, you will have a system that has a working
> GNU Radio, completely without leaving the boundaries of your non-root
> user. Downside is that everything that's not on your system (or in an
> outdated version) has to be built from source, which will take quite
> some time and storage. Afterwards, if all these PCs are the same, you
> can just copy the prefix folder to every user's home directory.
> 
> Either way, you'll (hopefully) have a working GNU Radio installation
> afterwards.
> Now, if you used pybombs, you'll already have a prefix directory in your
> user's home where your OS will look for when loading libraries etc.
> Otherwise, use pybombs now (./pybombs config; ./pybombs env; echo
> "source $prefix/setup_env.sh" >> ~/.bashrc) to generate the empty
> directory and generate a path-bending script.
> 
> When building your student's OOT's, you'd go the normal "cd gr-mymodule;
> mkdir build; cd build; cmake ..; make; make install;" route, only that
> you'd replace "cmake .." with "cmake
> -DCMAKE_INSTALL_PREFIX=/home/userXYZ/prefixdirectory .."; afterwards,
> "make install" will install the things into prefixdirectory; awesome!
> 
> Best regards,
> Marcus
> 
> [1]http://gnuradio.org/redmine/projects/pybombs/wiki/QuickStart
> 
> On 04/08/2015 11:52 AM, Leonardo S. Cardoso wrote:
>> Hi everyone,
>> 
>> We’re trying to implement a GNU Radio course here in Lyon (France) where we 
>> take the students step-by-step into coding GR modules. At some point we’d 
>> like them to follow the out-of-tree modules tutorial but we’ve stumbled upon 
>> an unfortunate limitation: the IT guys of our university wont allow root 
>> access on any computer, meaning that we can compile but cannot install the 
>> blocks...
>> 
>> I come to you guys, to ask for advices on how to implement this. I have some 
>> ideas already but I’d like to see if there is any “best practice” ways to do 
>> this.
>> 
>> Best regards,
>> 
>> Leonardo Cardoso
>> 
>> 
>> 
>> ___
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 
> 
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] DVB-T/T2

[Bogdan Diaconescu]

Hi Ralph,
DVB-T.png shows some u's on the command line which means the whole flowgraph do 
not provide data to USRP at the right speed. It basically mean the computer 
cannot cope with the required processing requirement.

As for the video parameters, in the DVB-T specs 
(http://www.etsi.org/deliver/etsi_en/300700_300799/300744/01.06.01_60/en_300744v010601p.pdf)
 you will find Table 17 where the rates are presented. FYI, the settings you 
have used are 8Mhz bandwidth, QAM-16 constellation, coding 1/2, guard interval 
1/32. The video should be constant bit rate but it is not a hard requirement 
(see below).

If you just broadcast video from a file and not plan to use a live streaming 
from camera, the rate should not matter too much. The video is sent at the rate 
of the DVB-T according to it's parameters and with RTL2832 receiver it is 
buffered and played at the correct speed (at least for short files like 
test.ts).
Bogdan
 


 On Wednesday, April 8, 2015 11:55 AM, "Ralph A. Schmid, dk5ras" 
 wrote:
   

 #yiv3233999861 #yiv3233999861 -- _filtered #yiv3233999861 
{font-family:Helvetica;panose-1:2 11 6 4 2 2 2 2 2 4;} _filtered #yiv3233999861 
{panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv3233999861 
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}#yiv3233999861 
#yiv3233999861 p.yiv3233999861MsoNormal, #yiv3233999861 
li.yiv3233999861MsoNormal, #yiv3233999861 div.yiv3233999861MsoNormal 
{margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;}#yiv3233999861 a:link, 
#yiv3233999861 span.yiv3233999861MsoHyperlink 
{color:blue;text-decoration:underline;}#yiv3233999861 a:visited, #yiv3233999861 
span.yiv3233999861MsoHyperlinkFollowed 
{color:purple;text-decoration:underline;}#yiv3233999861 
p.yiv3233999861msonormal, #yiv3233999861 li.yiv3233999861msonormal, 
#yiv3233999861 div.yiv3233999861msonormal 
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv3233999861 
p.yiv3233999861msoacetate, #yiv3233999861 li.yiv3233999861msoacetate, 
#yiv3233999861 div.yiv3233999861msoacetate 
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv3233999861 
p.yiv3233999861balloontext, #yiv3233999861 li.yiv3233999861balloontext, 
#yiv3233999861 div.yiv3233999861balloontext 
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv3233999861 
p.yiv3233999861msochpdefault, #yiv3233999861 li.yiv3233999861msochpdefault, 
#yiv3233999861 div.yiv3233999861msochpdefault 
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv3233999861 
span.yiv3233999861msohyperlink {}#yiv3233999861 
span.yiv3233999861msohyperlinkfollowed {}#yiv3233999861 
span.yiv3233999861sprechblasentextzchn {}#yiv3233999861 
span.yiv3233999861e-mailformatvorlage19 {}#yiv3233999861 
span.yiv3233999861e-mailformatvorlage20 {}#yiv3233999861 
span.yiv3233999861e-mailformatvorlage23 {}#yiv3233999861 
span.yiv3233999861e-mailformatvorlage24 {}#yiv3233999861 
p.yiv3233999861msonormal1, #yiv3233999861 li.yiv3233999861msonormal1, 
#yiv3233999861 div.yiv3233999861msonormal1 
{margin:0cm;margin-bottom:.0001pt;font-size:11.0pt;color:black;}#yiv3233999861 
span.yiv3233999861msohyperlink1 
{color:blue;text-decoration:underline;}#yiv3233999861 
span.yiv3233999861msohyperlinkfollowed1 
{color:purple;text-decoration:underline;}#yiv3233999861 
p.yiv3233999861msoacetate1, #yiv3233999861 li.yiv3233999861msoacetate1, 
#yiv3233999861 div.yiv3233999861msoacetate1 
{margin:0cm;margin-bottom:.0001pt;font-size:8.0pt;color:black;}#yiv3233999861 
span.yiv3233999861sprechblasentextzchn1 {color:black;}#yiv3233999861 
span.yiv3233999861e-mailformatvorlage191 {color:windowtext;}#yiv3233999861 
span.yiv3233999861e-mailformatvorlage201 {color:#1F497D;}#yiv3233999861 
p.yiv3233999861balloontext1, #yiv3233999861 li.yiv3233999861balloontext1, 
#yiv3233999861 div.yiv3233999861balloontext1 
{margin:0cm;margin-bottom:.0001pt;font-size:11.0pt;color:black;}#yiv3233999861 
span.yiv3233999861e-mailformatvorlage231 {color:#1F497D;}#yiv3233999861 
span.yiv3233999861e-mailformatvorlage241 {color:#1F497D;}#yiv3233999861 
p.yiv3233999861msochpdefault1, #yiv3233999861 li.yiv3233999861msochpdefault1, 
#yiv3233999861 div.yiv3233999861msochpdefault1 
{margin-right:0cm;margin-left:0cm;font-size:10.0pt;}#yiv3233999861 
span.yiv3233999861E-MailFormatvorlage39 {color:#1F497D;}#yiv3233999861 
.yiv3233999861MsoChpDefault {font-size:10.0pt;} _filtered #yiv3233999861 
{margin:70.85pt 70.85pt 2.0cm 70.85pt;}#yiv3233999861 
div.yiv3233999861WordSection1 {}#yiv3233999861 Yep, this would be quite useful!

Bogdan, as you are here, too - I don't know very much about all the crazy video 
file stuff, but maybe you can give me some basic parameters I need to comply 
with for a transport stream, to be able to transmit it with your package?! I 
need to use Windows for the conversion, as my Linux installation is only on a 
virtual machine, with limited space and power. A capable looking Windows 
program is available, but there are so many options I have no clue about :(  I 
modified your flow graph according to Rons hints, a

Re: [Discuss-gnuradio] Installing GNU Radio blocks as a regular user

[Marcus Müller]

Hi Leonardo,

So this depends on your situation: If you're allowed to get arbitrary
software installed by asking IT, I'd ask them to install a recent
version of GNU Radio (at *least* 3.7.2, the newer, the better).
Possibly, only outdated versions are in your IT's software package
repositories, so you might need them to build and install from source;
they might refuse.

If that's the case, or you can't ask for arbitrary software:
use pyBombs[1]! It allows installation in a directory prefix of your
choice. Choose "src" as only viable method of software installation.
After pybombs has finished doing its thing, you get a shell script that
you can use to modify the environment variables, so that if you just use
that script in your ~/.bashrc, you will have a system that has a working
GNU Radio, completely without leaving the boundaries of your non-root
user. Downside is that everything that's not on your system (or in an
outdated version) has to be built from source, which will take quite
some time and storage. Afterwards, if all these PCs are the same, you
can just copy the prefix folder to every user's home directory.

Either way, you'll (hopefully) have a working GNU Radio installation
afterwards.
Now, if you used pybombs, you'll already have a prefix directory in your
user's home where your OS will look for when loading libraries etc.
Otherwise, use pybombs now (./pybombs config; ./pybombs env; echo
"source $prefix/setup_env.sh" >> ~/.bashrc) to generate the empty
directory and generate a path-bending script.

When building your student's OOT's, you'd go the normal "cd gr-mymodule;
mkdir build; cd build; cmake ..; make; make install;" route, only that
you'd replace "cmake .." with "cmake
-DCMAKE_INSTALL_PREFIX=/home/userXYZ/prefixdirectory .."; afterwards,
"make install" will install the things into prefixdirectory; awesome!

Best regards,
Marcus

[1]http://gnuradio.org/redmine/projects/pybombs/wiki/QuickStart

On 04/08/2015 11:52 AM, Leonardo S. Cardoso wrote:
> Hi everyone,
>
> We’re trying to implement a GNU Radio course here in Lyon (France) where we 
> take the students step-by-step into coding GR modules. At some point we’d 
> like them to follow the out-of-tree modules tutorial but we’ve stumbled upon 
> an unfortunate limitation: the IT guys of our university wont allow root 
> access on any computer, meaning that we can compile but cannot install the 
> blocks...
>
> I come to you guys, to ask for advices on how to implement this. I have some 
> ideas already but I’d like to see if there is any “best practice” ways to do 
> this.
>
> Best regards,
>
> Leonardo Cardoso
>
>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] Installing GNU Radio blocks as a regular user

[Leonardo S. Cardoso]

Hi everyone,

We’re trying to implement a GNU Radio course here in Lyon (France) where we 
take the students step-by-step into coding GR modules. At some point we’d like 
them to follow the out-of-tree modules tutorial but we’ve stumbled upon an 
unfortunate limitation: the IT guys of our university wont allow root access on 
any computer, meaning that we can compile but cannot install the blocks...

I come to you guys, to ask for advices on how to implement this. I have some 
ideas already but I’d like to see if there is any “best practice” ways to do 
this.

Best regards,

Leonardo Cardoso



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] DVB-T/T2

[Ralph A. Schmid, dk5ras]

Yep, this would be quite useful!

Bogdan, as you are here, too - I don't know very much about all the crazy video 
file stuff, but maybe you can give me some basic parameters I need to comply 
with for a transport stream, to be able to transmit it with your package?! I 
need to use Windows for the conversion, as my Linux installation is only on a 
virtual machine, with limited space and power. A capable looking Windows 
program is available, but there are so many options I have no clue about :(

 

I modified your flow graph according to Rons hints, and now I have a stable and 
reliable DVB-T transmission path with your package. See 
http://dk5ras.dyndns.org/tmp/DVB/ with a screenshot. I am using the Ettus B210, 
and for reception a second PC with DVB-T stick, or a DVB-x tester that does 
them all, DVB-C/S/S2/T/T2. 

 

You and Ron really did a great job with coding those DVB-x packages!

 

Ralph.

 

From: discuss-gnuradio-bounces+ralph=schmid@gnu.org 
[mailto:discuss-gnuradio-bounces+ralph=schmid@gnu.org] On Behalf Of Bogdan 
Diaconescu
Sent: Wednesday, April 8, 2015 8:01 AM
To: Ron Economos; discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] DVB-T/T2

 

Ok, it would be useful to have receivers too like for the DVB-T. 

 

Bogdan

 

 

On Tuesday, April 7, 2015 11:23 PM, Ron Economos mailto:w...@comcast.net> > wrote:

 

Only transmitter implementations for now. They are here:

https://github.com/drmpeg/gr-dvbs2

https://github.com/drmpeg/gr-dvbt2

The DVB-T2 implementation supports T2-Lite, tone reservation PAPR reduction and 
MISO processing.

Ron

On 04/07/2015 06:38 AM, Bogdan Diaconescu wrote:

Hi Ron,

 

I have not followed the development of DVB-T2/S2 lately. Are there receiver 
implementations for the T2/S2 or just transmitters?

 

Thanks,

Bogdan

 

 

On Tuesday, April 7, 2015 1:32 PM, "Ralph A. Schmid, dk5ras"  
  wrote:

 

Great to hear that you work finds its way into the official thing! 

 

At the moment, as the RF stuff works, I am trying to learn about all this crazy 
video file stuff, for being able to create transport streams with my own 
content. Up to now I am still testing with the cartoon .ts :) Still my laptop 
(with DVBViewer software) will not decode the audio, while the DVB tester 
decodes audio just fine. 

 

Ralph.

  

 

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org  
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

 

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio