[Discuss-gnuradio] gnuradio on android

2015-08-24 Thread Mostafa Alizadeh 
Hi

I'm looking for "GNURadio on android" applications. I mean what kind stuffs
already can I do with GNURadio on android? I have not tried the process of
making GNURadio on a mobile device since I don't know what's its
application.

To be specific, is it possible to, for instance, use mobile (or tablet)
hardware to capture or send signals with GNURadio on it (instead of using
an external USRP)?

Thanks in advance for any clarification,
Mostafa

-- 
***
Department of Electrical Engineering
Aboureyhan Building
MMWCL LAB
Amirkabir University Of Technology
Tehran
IRAN
Tel: +98 (919) 158-7730
LAB: http://ele.aut.ac.ir/~mmwcl/?page_id=411
Homepage: http://ele.aut.ac.ir/~alizadeh/
***
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] cygwin compile of 3.7.8

2015-08-24 Thread Matt Dunford 
Has anyone had any luck compiling the latest 3.7.8 on cygwin?  I'm running
into the following:

[ 14%] Built target pygen_python_volk_modtool_95e3e
[ 14%] Built target pmt_generated
[ 15%] Built target gnuradio-pmt
Scanning dependencies of target gnuradio-runtime
[ 15%] Building CXX object
gnuradio-runtime/lib/CMakeFiles/gnuradio-runtime.dir/thread/thread.cc.o
/home/matt/src/gnuradio-3.7.8/gnuradio-runtime/lib/thread/thread.cc:245:23:
fatal error: sys/prctl.h: No such file or directory
 #include 
   ^
compilation terminated.

I don't believe sys/prctl.h exists in cygwin (or even all flavors of
unix).  Am I missing something obvious?

-- 
-- Matt Dunford -- zenma...@gmail.com
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] ofdm mod error

2015-08-24 Thread Patrcia Wonder 
I'm using ZedBoard by ADI as my dev board and this is their instructions 
for installing everything...

http://wiki.analog.com/resources/tools-software/linux-software/zynq_images

I did everything in here...

It seems everything about the OFDM blocks have similar problem...

-- 
Posted via http://www.ruby-forum.com/.

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

Re: [Discuss-gnuradio] Executing the flow graph: window closes immediatly

2015-08-24 Thread Marcus Müller 
That does sound correct; so we need to really look deeper into what goes
wrong in your flowgraph. Which one from that tutorial are we talking
about specifically? Can you share the .grc file?

Best regards,
Marcus

On 08/24/2015 08:26 AM, nick_mey...@telenet.be wrote:
> Hi Marcus,
>
> I installed the gnu radio from the command "sudo apt-get install
> gnuradio" trough the terminal.  
>
> This installation went smooth and I did not observe any problems.  
>
> After this I started to follow the tutorial
> ( http://gnuradio.org/redmine/projects/gnuradio/wiki/Guided_Tutorial_GRC )
> but on step 2.1.2 the cmake command failed so i needed to install the
> cmake and doxygen packages.  
>
> Best regards,
>
> Nick
>
> 
> *Van: *"Marcus Müller" 
> *Aan: *discuss-gnuradio@gnu.org
> *Verzonden: *Zondag 23 augustus 2015 22:28:38
> *Onderwerp: *Re: [Discuss-gnuradio] Executing the flow graph: window
> closes immediatly
>
> Hi Nick,
>
> segmentation fault is a severe error; it means that the program you
> generated tried to access memory that wasn't there. The error really
> doesn't say anything more.
> We haven't seen such error in released GNU Radio versions lately.
>
> My guess therefore is that there might be something wrong with your
> set up instead.
> How did you install GNU Radio? If you've installed it from source, or
> build-gnuradio, or pybombs you *must not* install gnuradio from
> Ubuntu's package archives.
>
> Best regards,
> Marcus
>
> On 23.08.2015 22:05, nick_mey...@telenet.be wrote:
>
> Hello,
>
> I'm totally new to the gnu radio project and trying my first steps
> into the world of SDR.  
>
> At this moment i ran into a problem:  I followed the steps of the
> tutorial
> at http://gnuradio.org/redmine/projects/gnuradio/wiki/Guided_Tutorial_GRC
>
> I made the flowchart exactly as described in the tutorial, but
> when i try to execute the flow graph, a window appears and
> directly closes.  
>
> When I try to run the code directly from the terminal i get
> following message: Segmentation fault (core dumped)
>
> I'm running Ubuntu 14.04 LTS.  
>
> How can I fix this issue?
>
> Regards
>
> Nick
>
>
> ___
> 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] Executing the flow graph: window closes immediatly

2015-08-24 Thread nick_meynen 
I followed the tutorial on gnuradio.org (correct link: 
http://gnuradio.org/redmine/projects/gnuradio/wiki/Guided_Tutorial_GRC ) 

This is the particular flowchart we're talking about: 
https://raw.githubusercontent.com/gnuradio/gr-tutorial/master/examples/tutorial2/images/tutorial_two_1.png
 

In attachment is the .grc file. 

Best regards, 

Nick 

- Oorspronkelijk bericht -

Van: "Marcus Müller"  
Aan: "nick meynen" , "GNURadio Discussion List" 
 
Verzonden: Maandag 24 augustus 2015 15:17:40 
Onderwerp: Re: [Discuss-gnuradio] Executing the flow graph: window closes 
immediatly 

That does sound correct; so we need to really look deeper into what goes wrong 
in your flowgraph. Which one from that tutorial are we talking about 
specifically? Can you share the .grc file? 

Best regards, 
Marcus 

On 08/24/2015 08:26 AM, nick_mey...@telenet.be wrote: 



Hi Marcus, 

I installed the gnu radio from the command "sudo apt-get install gnuradio" 
trough the terminal. 

This installation went smooth and I did not observe any problems. 

After this I started to follow the tutorial ( 
http://gnuradio.org/redmine/projects/gnuradio/wiki/Guided_Tutorial_GRC ) but on 
step 2.1.2 the cmake command failed so i needed to install the cmake and 
doxygen packages. 

Best regards, 

Nick 

- Oorspronkelijk bericht -

Van: "Marcus Müller"  
Aan: discuss-gnuradio@gnu.org 
Verzonden: Zondag 23 augustus 2015 22:28:38 
Onderwerp: Re: [Discuss-gnuradio] Executing the flow graph: window closes 
immediatly 

Hi Nick, 

segmentation fault is a severe error; it means that the program you generated 
tried to access memory that wasn't there. The error really doesn't say anything 
more. 
We haven't seen such error in released GNU Radio versions lately. 

My guess therefore is that there might be something wrong with your set up 
instead. 
How did you install GNU Radio? If you've installed it from source, or 
build-gnuradio, or pybombs you *must not* install gnuradio from Ubuntu's 
package archives. 

Best regards, 
Marcus 

On 23.08.2015 22:05, nick_mey...@telenet.be wrote: 



Hello, 

I'm totally new to the gnu radio project and trying my first steps into the 
world of SDR. 

At this moment i ran into a problem: I followed the steps of the tutorial at 
http://gnuradio.org/redmine/projects/gnuradio/wiki/Guided_Tutorial_GRC 

I made the flowchart exactly as described in the tutorial, but when i try to 
execute the flow graph, a window appears and directly closes. 

When I try to run the code directly from the terminal i get following message: 
Segmentation fault (core dumped) 

I'm running Ubuntu 14.04 LTS. 

How can I fix this issue? 

Regards 

Nick 


___
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 







Tutorial 2.grc
Description: XML document
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] ofdm mod error

2015-08-24 Thread Marcus Müller 
The point is that what you're seeing is clearly a Python telling you
that it can't find the crc32_bb module nor the constellation_psk object
where they should be, on a proper installation of GNU Radio.
This is not a problem of these examples, but of your installation; as
Martin hinted, we need to solve that first.

Best regards,
Marcus

On 08/24/2015 07:44 AM, Patrcia Wonder wrote:
> I'm using ZedBoard by ADI as my dev board and this is their instructions 
> for installing everything...
>
> http://wiki.analog.com/resources/tools-software/linux-software/zynq_images
>
> I did everything in here...
>
> It seems everything about the OFDM blocks have similar problem...
>


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

Re: [Discuss-gnuradio] gnuradio on android

2015-08-24 Thread Marcus Müller 
Hi Mostafa,

> To be specific, is it possible to, for instance, use mobile (or
> tablet) hardware to capture or send signals with GNURadio on it
> (instead of using an external USRP)?  
no, mobile phones don't have "raw" sample access to their radio chips,
since these were generally not designed to do that.

Best regards,
Marcus

On 08/24/2015 09:37 AM, Mostafa Alizadeh wrote:
> Hi 
>
> I'm looking for "GNURadio on android" applications. I mean what kind
> stuffs already can I do with GNURadio on android? I have not tried the
> process of making GNURadio on a mobile device since I don't know
> what's its application.
>
> To be specific, is it possible to, for instance, use mobile (or
> tablet) hardware to capture or send signals with GNURadio on it
> (instead of using an external USRP)?  
>
> Thanks in advance for any clarification,
> Mostafa
>
> -- 
> ***
> Department of Electrical Engineering
> Aboureyhan Building
> MMWCL LAB
> Amirkabir University Of Technology
> Tehran
> IRAN
> Tel: +98 (919) 158-7730
> LAB: http://ele.aut.ac.ir/~mmwcl/?page_id=411
> 
> Homepage: http://ele.aut.ac.ir/~alizadeh/
> 
> ***
>
>
> ___
> 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] OOT Module Attribute Error module object has no attribute 'blockname'

2015-08-24 Thread Washbourne, Logan 
Patrick and All,

I figured out my original error. In my XML file I was trying to use a
variable without including it in the line:

ACK.Text_Sanitize($msg)

the $msg is what I added and that error no longer occurs.

This error: RuntimeError: attempt to set_msg_handler() on bad input message
port!

still occurs, but that's just going to take some time for me to learn about
PMTs and PDUs.

Thanks for everyone's help!


Logan Washbourne
Electrical Engineering Graduate Student
(Electromagnetics)


On Sat, Aug 22, 2015 at 1:57 PM, Washbourne, Logan <
lwas...@ostatemail.okstate.edu> wrote:

> Patrick,
>
> Thanks for the advice! So I added that string parameter(or char array) to
> the Top_Block.py file
>
> the new line looks like this:self.ACK_Text_Sanitize_0 =
> ACK.Text_Sanitize("String").
>
> When I run "python top_block.py" this error occurs:
>
> comm1@comm1:~/Logan/Thesis$ python top_block.py
> Traceback (most recent call last):
>   File "top_block.py", line 92, in 
> tb = top_block()
>   File "top_block.py", line 65, in __init__
> self.ACK_Text_Sanitize_0 = ACK.Text_Sanitize("String")
>   File "/usr/local/lib/python2.7/dist-packages/ACK/ACK_swig.py", line 399,
> in make
> return _ACK_swig.Text_Sanitize_make(*args, **kwargs)
> RuntimeError: attempt to set_msg_handler() on bad input message port!
>
>
> My XML file can be found here:
> https://gist.github.com/loganwashbourne/68367a93b7fe9bf28bce
>
> So the RuntimeError seems to be the problem, I'm leaning towards the idea
> that I am not handling the PMT's correctly. Thoughts?
>
> Richard,
>
> I appreciate the advice, I've been pretty diligent about using sudo
> ldconfig after I read that not using it could create problems. All advice
> helps!
>
>
>
> Logan Washbourne
> Electrical Engineering Graduate Student
> (Electromagnetics)
>
>
> On Fri, Aug 21, 2015 at 4:37 PM, Patrick Sathyanathan 
> wrote:
>
>> I see the following in the output of "nm -C -u":
>>
>>  U gr::ACK::Text_Sanitize_impl::forecast(int, std::vector> std::allocator >&)
>>
>> This was the undefined symbol that was causing the module import to
>> fail... as you have discovered yourself. Now that the module import has
>> succeeded you are seeing a different error.
>>
>> This error is because of the following in the generated python file:
>>
>>self.ACK_Text_Sanitize_0 = ACK.Text_Sanitize()
>>
>> Note that this will invoke "Text_Sanitize::make" which expects a "char *
>> message" argument. That causes the error message below. For some reason GRC
>> is not adding that parameter in the above statement. Did you add a
>> declaration for that parameter in the XML file ?
>>
>> To verify that the XML file is the issue just try editing the generated
>> python file and changing the above to:
>>
>>self.ACK_Text_Sanitize_0 = ACK.Text_Sanitize("some string")
>>
>> and running it from the command line (run "python top_block.py" in a
>> terminal window).
>>
>> --Patrick
>>
>> --
>> Date: Thu, 20 Aug 2015 11:08:56 -0500
>> From: lwas...@ostatemail.okstate.edu
>> To: discuss-gnuradio@gnu.org
>>
>> Subject: Re: [Discuss-gnuradio] OOT Module Attribute Error module object
>> has no attribute 'blockname'
>>
>> Nathan and Patrick,
>>
>> Thanks for the tips!
>>
>> I started with running: nm -C -u libgnuradio-.so
>>
>> and the results of that can be found here:
>> https://gist.github.com/loganwashbourne under the *nm -C -u
>> libgnuradio-.so*
>>  file. (I
>> think github thinks I'm a robot so I can't link to the direct page yet).
>>
>> I'll be honest, I'm not really sure what I'm looking at in this return, I
>> do see some error statements but I'm not sure if they are just stating how
>> it would handle an error or if it is an actual error.
>>
>> I really don't think I have any callbacks in my XML code, I just
>> reference certain input variables in the XML code.
>>
>> Next, the ACK_swig.i file can be found here :
>> https://gist.github.com/loganwashbourne under the same file name. I
>> checked it against the gr-tutorial swig file and the only difference was
>> that the ACK_swig.i file included a magic2 function call for each of my OOT
>> blocks(check and Text_Sanitize), while the gr-tutorial didn't.
>>
>> Last thing, I realized that I am creating the forecast function in the
>> Text_Sanitize_impl.h file but not referencing it it the .cc file (I
>> commented it out). I tried commenting out the void deceleration of the
>> forecast function in the .h file but then I get a new error when I try to
>> run the grc file(which is just a constant int source connected to my
>> Text_Sanitize block, which is connected the the message debug "print" port).
>>
>> The new error is :
>>
>> Traceback (most recent call last):
>>   File "/home/comm1/Logan/Thesis/top_block.py", line 92, in 
>> tb = top_block()
>>   File "/home/comm1/Logan/Thesis/top_block.py", line 65, in __init__
>> self.ACK_Text_Sanitize_0 = ACK.Text_Sanitize

Re: [Discuss-gnuradio] ofdm mod error

2015-08-24 Thread nick_meynen 
Marcus,

I just saw i was still running a 32 bit installation of linux.  I just removed 
my old installation and busy reinstalling a fresh Ubuntu 14.04 LTS.

What instalation way is best?  Installing by the sudo apt-get install command 
or just build my own version?

best regards,

Nick

- Oorspronkelijk bericht -
Van: "Marcus Müller" 
Aan: discuss-gnuradio@gnu.org
Verzonden: Maandag 24 augustus 2015 16:59:13
Onderwerp: Re: [Discuss-gnuradio] ofdm mod error

The point is that what you're seeing is clearly a Python telling you
that it can't find the crc32_bb module nor the constellation_psk object
where they should be, on a proper installation of GNU Radio.
This is not a problem of these examples, but of your installation; as
Martin hinted, we need to solve that first.

Best regards,
Marcus

On 08/24/2015 07:44 AM, Patrcia Wonder wrote:
> I'm using ZedBoard by ADI as my dev board and this is their instructions 
> for installing everything...
>
> http://wiki.analog.com/resources/tools-software/linux-software/zynq_images
>
> I did everything in here...
>
> It seems everything about the OFDM blocks have similar problem...
>


___
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] Executing the flow graph: window closes immediatly

2015-08-24 Thread Marcus Müller 
Hi Nick,

I don't know whether this is good or bad news: On my machine, this runs
beautifully.
I don't have Ubuntu 14.04 LTS at hand, but since that is one of the main
platforms that people use to work with GNU Radio, a systematic error in
GNU Radio would most likely have been spotted already.

Now, I'd like to ask you to run the flowgraph with GDB, to get more
debugging info. Is that alright with you?

sudo apt-get install gdb #if you don't have gdb installed
gdb python /path/to/flowgraph.py #path is displayed in the GRC console
when you hit the "generate" button.
(gdb) run

Best regards,
Marcus

On 08/24/2015 05:48 PM, nick_mey...@telenet.be wrote:
> I followed the tutorial on gnuradio.org (correct link: 
> http://gnuradio.org/redmine/projects/gnuradio/wiki/Guided_Tutorial_GRC )
>
> This is the particular flowchart we're talking about: 
> https://raw.githubusercontent.com/gnuradio/gr-tutorial/master/examples/tutorial2/images/tutorial_two_1.png
>
> In attachment is the .grc file. 
>
> Best regards,
>
> Nick
>
> 
> *Van: *"Marcus Müller" 
> *Aan: *"nick meynen" , "GNURadio Discussion
> List" 
> *Verzonden: *Maandag 24 augustus 2015 15:17:40
> *Onderwerp: *Re: [Discuss-gnuradio] Executing the flow graph: window
> closes immediatly
>
> That does sound correct; so we need to really look deeper into what
> goes wrong in your flowgraph. Which one from that tutorial are we
> talking about specifically? Can you share the .grc file?
>
> Best regards,
> Marcus
>
> On 08/24/2015 08:26 AM, nick_mey...@telenet.be wrote:
>
> Hi Marcus,
>
> I installed the gnu radio from the command "sudo apt-get install
> gnuradio" trough the terminal.  
>
> This installation went smooth and I did not observe any problems.  
>
> After this I started to follow the tutorial
> ( http://gnuradio.org/redmine/projects/gnuradio/wiki/Guided_Tutorial_GRC )
> but on step 2.1.2 the cmake command failed so i needed to install
> the cmake and doxygen packages.  
>
> Best regards,
>
> Nick
>
> 
> *Van: *"Marcus Müller" 
> *Aan: *discuss-gnuradio@gnu.org
> *Verzonden: *Zondag 23 augustus 2015 22:28:38
> *Onderwerp: *Re: [Discuss-gnuradio] Executing the flow graph:
> window closes immediatly
>
> Hi Nick,
>
> segmentation fault is a severe error; it means that the program
> you generated tried to access memory that wasn't there. The error
> really doesn't say anything more.
> We haven't seen such error in released GNU Radio versions lately.
>
> My guess therefore is that there might be something wrong with
> your set up instead.
> How did you install GNU Radio? If you've installed it from source,
> or build-gnuradio, or pybombs you *must not* install gnuradio from
> Ubuntu's package archives.
>
> Best regards,
> Marcus
>
> On 23.08.2015 22:05, nick_mey...@telenet.be wrote:
>
> Hello,
>
> I'm totally new to the gnu radio project and trying my first
> steps into the world of SDR.  
>
> At this moment i ran into a problem:  I followed the steps of
> the tutorial
> at 
> http://gnuradio.org/redmine/projects/gnuradio/wiki/Guided_Tutorial_GRC
>
> I made the flowchart exactly as described in the tutorial, but
> when i try to execute the flow graph, a window appears and
> directly closes.  
>
> When I try to run the code directly from the terminal i get
> following message: Segmentation fault (core dumped)
>
> I'm running Ubuntu 14.04 LTS.  
>
> How can I fix this issue?
>
> Regards
>
> Nick
>
>
> ___
> 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] Executing the flow graph: window closes immediatly

2015-08-24 Thread nick_meynen 
Hi Marcus, 

I'm sorry i made just a terrible mistake: i reply'd to the wrong tread. 

This was my answer: 

Marcus, 

I just saw i was still running a 32 bit installation of linux. I just removed 
my old installation and busy reinstalling a fresh Ubuntu 14.04 LTS. 

What instalation way is best? Installing by the sudo apt-get install command or 
just build my own version? 

best regards, 

Nick 



- Oorspronkelijk bericht -

Van: "Marcus Müller"  
Aan: "nick meynen"  
Cc: "GNURadio Discussion List"  
Verzonden: Maandag 24 augustus 2015 18:32:58 
Onderwerp: Re: [Discuss-gnuradio] Executing the flow graph: window closes 
immediatly 

Hi Nick, 

I don't know whether this is good or bad news: On my machine, this runs 
beautifully. 
I don't have Ubuntu 14.04 LTS at hand, but since that is one of the main 
platforms that people use to work with GNU Radio, a systematic error in GNU 
Radio would most likely have been spotted already. 

Now, I'd like to ask you to run the flowgraph with GDB, to get more debugging 
info. Is that alright with you? 

sudo apt-get install gdb #if you don't have gdb installed 
gdb python /path/to/flowgraph.py #path is displayed in the GRC console when you 
hit the "generate" button. 
(gdb) run 

Best regards, 
Marcus 

On 08/24/2015 05:48 PM, nick_mey...@telenet.be wrote: 



I followed the tutorial on gnuradio.org (correct link: 
http://gnuradio.org/redmine/projects/gnuradio/wiki/Guided_Tutorial_GRC ) 

This is the particular flowchart we're talking about: 
https://raw.githubusercontent.com/gnuradio/gr-tutorial/master/examples/tutorial2/images/tutorial_two_1.png
 

In attachment is the .grc file. 

Best regards, 

Nick 

- Oorspronkelijk bericht -

Van: "Marcus Müller"  
Aan: "nick meynen"  , "GNURadio Discussion List" 
 
Verzonden: Maandag 24 augustus 2015 15:17:40 
Onderwerp: Re: [Discuss-gnuradio] Executing the flow graph: window closes 
immediatly 

That does sound correct; so we need to really look deeper into what goes wrong 
in your flowgraph. Which one from that tutorial are we talking about 
specifically? Can you share the .grc file? 

Best regards, 
Marcus 

On 08/24/2015 08:26 AM, nick_mey...@telenet.be wrote: 



Hi Marcus, 

I installed the gnu radio from the command "sudo apt-get install gnuradio" 
trough the terminal. 

This installation went smooth and I did not observe any problems. 

After this I started to follow the tutorial ( 
http://gnuradio.org/redmine/projects/gnuradio/wiki/Guided_Tutorial_GRC ) but on 
step 2.1.2 the cmake command failed so i needed to install the cmake and 
doxygen packages. 

Best regards, 

Nick 

- Oorspronkelijk bericht -

Van: "Marcus Müller"  
Aan: discuss-gnuradio@gnu.org 
Verzonden: Zondag 23 augustus 2015 22:28:38 
Onderwerp: Re: [Discuss-gnuradio] Executing the flow graph: window closes 
immediatly 

Hi Nick, 

segmentation fault is a severe error; it means that the program you generated 
tried to access memory that wasn't there. The error really doesn't say anything 
more. 
We haven't seen such error in released GNU Radio versions lately. 

My guess therefore is that there might be something wrong with your set up 
instead. 
How did you install GNU Radio? If you've installed it from source, or 
build-gnuradio, or pybombs you *must not* install gnuradio from Ubuntu's 
package archives. 

Best regards, 
Marcus 

On 23.08.2015 22:05, nick_mey...@telenet.be wrote: 



Hello, 

I'm totally new to the gnu radio project and trying my first steps into the 
world of SDR. 

At this moment i ran into a problem: I followed the steps of the tutorial at 
http://gnuradio.org/redmine/projects/gnuradio/wiki/Guided_Tutorial_GRC 

I made the flowchart exactly as described in the tutorial, but when i try to 
execute the flow graph, a window appears and directly closes. 

When I try to run the code directly from the terminal i get following message: 
Segmentation fault (core dumped) 

I'm running Ubuntu 14.04 LTS. 

How can I fix this issue? 

Regards 

Nick 


___
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] RTL SDR and GRC3.7.8 problem: format error

2015-08-24 Thread John Petrich 
Ever since I updated to GRC3.7.8 none of my RTL SDR demos will run in GRC.
The error messages are the same: " list contains an invalid format".
Attached is the .grc file of a basic RTL Qt test flow graph authored using
GRC3.7.8, and the .odt file with the complete error message.  GRC detects
the RTL device, and cites format errors.   Are others having this problem
with GRC3.7.8?  I am anxious to resolve this problem because I have
scheduled a GRC presentation in the near future.

 

Regards,

John Petrich



RTL Qt test.grc
Description: Binary data


Error message.odt
Description: application/vnd.oasis.opendocument.text
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] RTL SDR and GRC3.7.8 problem: format error

2015-08-24 Thread Marcus D. Leech 

On 08/24/2015 02:26 PM, John Petrich wrote:


Ever since I updated to GRC3.7.8 none of my RTL SDR demos will run in 
GRC.  The error messages are the same: “ list contains an invalid 
format”.  Attached is the .grc file of a basic RTL Qt test flow graph 
authored using GRC3.7.8, and the .odt file with the complete error 
message.  GRC detects the RTL device, and cites format errors.   Are 
others having this problem with GRC3.7.8?  I am anxious to resolve 
this problem because I have scheduled a GRC presentation in the near 
future.


Regards,

John Petrich


Did you re-build gr-osmosdr against 3.7.8?  My suspicion is that the 
gr-osmosdr you're using is out-of-date with respect to the GR that is 
calling it.


Also, you have a throttle block in between your hardware source, and 
your Qt GUI block.  Don't do that.  You never need a throttle when 
you're using

  real hardware.


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

[Discuss-gnuradio] VOLK Release v1.1

2015-08-24 Thread West, Nathan 
Greetings, have a VOLK!

Release v1.1 is now available through github and tarballs via the website.
Release notes are available in the usual places (website, this email, and
git tag description)

Contributors


The following authors have contributed code to this release:

 * Doug Geiger 
 * Elliot Briggs 
 * Marcus Mueller 
 * Nathan West 
 * Pascal Giard 
 * Tom Rondeau 

Changes
===

This release contains all of the bug fixes from v1.0.1
and v1.0.2 as well as new features and other changes that
didn't belong on maint. The following is a summary of
non-maint changes.

Architectures
-

New architectures exist for the AVX2 and FMA ISAs. Along
with the build-system support the following kernels have
no proto-kernels taking advantage of these architectures:

 * 32f_x2_dot_prod_32f
 * 32fc_x2_multiply_32fc
 * 64_byteswap
 * 32f_binary_slicer_8i
 * 16u_byteswap
 * 32u_byteswap

QA/profiler
---

The profiler now generates buffers that are vlen + a tiny
amount and generates random data to fill buffers. This is
intended to catch bugs in protokernels that write beyond
num_points.

Miscellaneous
-

 * All builds now use '-Wall'
 * Removed stray references to PCC and Altivec

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

Re: [Discuss-gnuradio] Executing the flow graph: window closes immediatly

2015-08-24 Thread Marcus Müller 
Hi Nick,

I'd personally say that the GNU Radio packages in Ubuntu should be
pretty up to date (thanks, Maitland!), but the UHD in Ubuntu is
extremely old, so if you want to use USRPs, you can't use Ubuntu's GNU
Radio.
Since building isn't that hard nowadays, and you had bad experiences
with the Ubuntu package, I'd just try using pybombs [1]:

git clone --recursive https://github.com/pybombs/pybombs.git && cd pybombs && 
./pybombs install gnuradio 

You should be able to answer all questions with the default (just
 your way through the dialog), then after everything is complete:

./pybombs env

and add the generated file to your bashrc:

echo "source /setup_env.sh" >> ~/.bashrc

Open up a new terminal and run gnuradio-companion.

Best regards,
Marcus

[1] http://pybombs.info

On 24.08.2015 18:38, nick_mey...@telenet.be wrote:
> Hi Marcus,
>
> I'm sorry i made just a terrible mistake:  i reply'd to the wrong tread.
>
> This was my answer:  
>
> Marcus,
>
> I just saw i was still running a 32 bit installation of linux.  I just
> removed my old installation and busy reinstalling a fresh Ubuntu 14.04
> LTS.
>
> What instalation way is best?  Installing by the sudo apt-get install
> command or just build my own version?
>
> best regards,
>
> Nick
>
>
>
> 
> *Van: *"Marcus Müller" 
> *Aan: *"nick meynen" 
> *Cc: *"GNURadio Discussion List" 
> *Verzonden: *Maandag 24 augustus 2015 18:32:58
> *Onderwerp: *Re: [Discuss-gnuradio] Executing the flow graph: window
> closes immediatly
>
> Hi Nick,
>
> I don't know whether this is good or bad news: On my machine, this
> runs beautifully.
> I don't have Ubuntu 14.04 LTS at hand, but since that is one of the
> main platforms that people use to work with GNU Radio, a systematic
> error in GNU Radio would most likely have been spotted already.
>
> Now, I'd like to ask you to run the flowgraph with GDB, to get more
> debugging info. Is that alright with you?
>
> sudo apt-get install gdb #if you don't have gdb installed
> gdb python /path/to/flowgraph.py #path is displayed in the GRC console
> when you hit the "generate" button.
> (gdb) run
>
> Best regards,
> Marcus
>
> On 08/24/2015 05:48 PM, nick_mey...@telenet.be wrote:
>
> I followed the tutorial on gnuradio.org (correct link: 
> http://gnuradio.org/redmine/projects/gnuradio/wiki/Guided_Tutorial_GRC
> )
>
> This is the particular flowchart we're talking about: 
> 
> https://raw.githubusercontent.com/gnuradio/gr-tutorial/master/examples/tutorial2/images/tutorial_two_1.png
>
> In attachment is the .grc file. 
>
> Best regards,
>
> Nick
>
> 
> *Van: *"Marcus Müller" 
> *Aan: *"nick meynen" , "GNURadio
> Discussion List" 
> *Verzonden: *Maandag 24 augustus 2015 15:17:40
> *Onderwerp: *Re: [Discuss-gnuradio] Executing the flow graph:
> window closes immediatly
>
> That does sound correct; so we need to really look deeper into
> what goes wrong in your flowgraph. Which one from that tutorial
> are we talking about specifically? Can you share the .grc file?
>
> Best regards,
> Marcus
>
> On 08/24/2015 08:26 AM, nick_mey...@telenet.be wrote:
>
> Hi Marcus,
>
> I installed the gnu radio from the command "sudo apt-get
> install gnuradio" trough the terminal.  
>
> This installation went smooth and I did not observe any
> problems.  
>
> After this I started to follow the tutorial
> ( 
> http://gnuradio.org/redmine/projects/gnuradio/wiki/Guided_Tutorial_GRC )
> but on step 2.1.2 the cmake command failed so i needed to
> install the cmake and doxygen packages.  
>
> Best regards,
>
> Nick
>
> 
> 
> *Van: *"Marcus Müller" 
> *Aan: *discuss-gnuradio@gnu.org
> *Verzonden: *Zondag 23 augustus 2015 22:28:38
> *Onderwerp: *Re: [Discuss-gnuradio] Executing the flow graph:
> window closes immediatly
>
> Hi Nick,
>
> segmentation fault is a severe error; it means that the
> program you generated tried to access memory that wasn't
> there. The error really doesn't say anything more.
> We haven't seen such error in released GNU Radio versions lately.
>
> My guess therefore is that there might be something wrong with
> your set up instead.
> How did you install GNU Radio? If you've installed it from
> source, or build-gnuradio, or pybombs you *must not* install
> gnuradio from Ubuntu's package archives.
>
> Best regards,
> Marcus
>
> On 23.08.2015 22:05, nick_mey...@telenet.be wrote:
>
> Hello,
>
> I'm totally new to the gnu radio project and trying my
> first steps into the worl

[Discuss-gnuradio] Setting up a simple packet radio in 3.7.7.2

2015-08-24 Thread Patel, Priyank 
Hello,



I am trying to get a simple packet radio GRC working but so far have had no 
luck with the following scheme:



tcp-source (port 9000) -> packet encoder -> gmsk mod -> gmsk demod -> packet 
decoder -> tcp-sink (port 9001)



If I remove the encoder/decoder and the gmsk mod/demod and go directly between 
the ports, then I am able to clearly see everything (I am using two terminals, 
one for tcp source and one for tcp sink).  If I add back in the gmsk mod/demod 
I see stuff in my other terminal window (although it is garbled).  Once I add 
the packet encoder nothing gets through again.



I've been trying to follow some examples of this done in the past, but they 
were with much older versions of GNU radio and some of them used GR-extras 
which is no longer supported in GnuRadio 3.7.



Any help would be greatly appreciated.



Thanks!

Priyank Patel

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

Re: [Discuss-gnuradio] Setting up a simple packet radio in 3.7.7.2

2015-08-24 Thread julian . arnold 
Hi Priyank,

The packet decoder is checking for a preamble sequence in the data stream.
If there is no output coming from the decoder the preamble is probably not 
being detected. 
How does the output of the gmsk demod look like?
Also, are you transmitting the signal or are you just simulating locally?

Cheers,
Julian 

> Am 24.08.2015 um 21:05 schrieb Patel, Priyank :
> 
> Hello,
>  
> I am trying to get a simple packet radio GRC working but so far have had no 
> luck with the following scheme:
>  
> tcp-source (port 9000) -> packet encoder -> gmsk mod -> gmsk demod -> packet 
> decoder -> tcp-sink (port 9001)
>  
> If I remove the encoder/decoder and the gmsk mod/demod and go directly 
> between the ports, then I am able to clearly see everything (I am using two 
> terminals, one for tcp source and one for tcp sink).  If I add back in the 
> gmsk mod/demod I see stuff in my other terminal window (although it is 
> garbled).  Once I add the packet encoder nothing gets through again. 
>  
> I've been trying to follow some examples of this done in the past, but they 
> were with much older versions of GNU radio and some of them used GR-extras 
> which is no longer supported in GnuRadio 3.7.
>  
> Any help would be greatly appreciated.
>  
> Thanks!
>  
> Priyank Patel
>  
> ___
> 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] gnuradio on android

2015-08-24 Thread Marcus Müller 
Hi Mostafa,
having read the feature sheet of QXDM, it says it can analyze the
strength of specific preambles, and configure Qualcom chipsets; I really
don't see how this matches up very well with what SDR is in the context
of GNU Radio. It really seems more like a statistical/administration
tool than a radio interface.

However, if you have experience with the protocols and interfaces that
QXDM is based upon, obviously, GNU Radio can only profit from having
interfaces to more hardware :) so go wild and write something that makes
GNU Radio talk to Qualcomm chipsets! Be very aware, however, that
Android is very strict with giving applications access to raw hardware,
so this might not be something that the average user might ever run on
his/her handset.

Best regards,
Marcus

On 24.08.2015 21:20, Mostafa Alizadeh wrote:
> Thank you for your response. I don't want to discuss something here
> that are out of scope of GNURadio, however, I found some useful
> Qualcomm drivers (software) such as: "QXDM" which make it possible to
> analyze (I really thing everything is possible) different signals
> (from GSM to LTE or 4G).
> For information see [1] and the attachment .
>
> any idea?
>
>
> Best,
> Mostafa
>
> [1] https://en.wikipedia.org/wiki/Qualcomm 
>
>
>
>
> On Mon, Aug 24, 2015 at 7:31 PM, Marcus Müller
> mailto:marcus.muel...@ettus.com>> wrote:
>
> Hi Mostafa,
>
>> To be specific, is it possible to, for instance, use mobile (or
>> tablet) hardware to capture or send signals with GNURadio on it
>> (instead of using an external USRP)?  
> no, mobile phones don't have "raw" sample access to their radio
> chips, since these were generally not designed to do that.
>
> Best regards,
> Marcus
>
>
> On 08/24/2015 09:37 AM, Mostafa Alizadeh wrote:
>> Hi 
>>
>> I'm looking for "GNURadio on android" applications. I mean what
>> kind stuffs already can I do with GNURadio on android? I have not
>> tried the process of making GNURadio on a mobile device since I
>> don't know what's its application.
>>
>> To be specific, is it possible to, for instance, use mobile (or
>> tablet) hardware to capture or send signals with GNURadio on it
>> (instead of using an external USRP)?  
>>
>> Thanks in advance for any clarification,
>> Mostafa
>>
>> -- 
>> ***
>> Department of Electrical Engineering
>> Aboureyhan Building
>> MMWCL LAB
>> Amirkabir University Of Technology
>> Tehran
>> IRAN
>> Tel: +98 (919) 158-7730
>> LAB: http://ele.aut.ac.ir/~mmwcl/?page_id=411
>> 
>> Homepage: http://ele.aut.ac.ir/~alizadeh/
>> 
>> ***
>>
>>
>> ___
>> 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
>
>
>
>
> -- 
> ***
> Department of Electrical Engineering
> Aboureyhan Building
> MMWCL LAB
> Amirkabir University Of Technology
> Tehran
> IRAN
> Tel: +98 (919) 158-7730
> LAB: http://ele.aut.ac.ir/~mmwcl/?page_id=411
> 
> Homepage: http://ele.aut.ac.ir/~alizadeh/
> 
> ***

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

[Discuss-gnuradio] RTL SDR and GRC3.7.8 problem: format error

2015-08-24 Thread John Petrich 
Thanks Marcus yet again.  In the past gr-osmosdr simply built seamlessly
along with gnuradio.  Not this time.  Don't know why.  My solution was to
delete the gr-osmosdr files from the home directory and git clone from the
Osmosdr website.  The installation went smoothly and the RTL SDR receiver
demos all run as expected.  Just in time.  And, I'll not throttle again
against the Qt GUI block.

Regards,
John Petrich

Ever since I updated to GRC3.7.8 none of my RTL SDR demos will run in GRC.
The error messages are the same: " list contains an invalid format".
Attached is the .grc file of a basic RTL Qt test flow graph authored using
GRC3.7.8, and the .odt file with the complete error message.  GRC detects
the RTL device, and cites format errors.   Are others having this problem
with GRC3.7.8?  I am anxious to resolve this problem because I have
scheduled a GRC presentation in the near future.
 
Regards,
John Petrich

Marcus Leech:

Did you re-build gr-osmosdr against 3.7.8?  My suspicion is that the
gr-osmosdr you're using is out-of-date with respect to the GR that is
calling it.

Also, you have a throttle block in between your hardware source, and your Qt
GUI block.  Don't do that.  You never need a throttle when you're using
  real hardware.


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

[Discuss-gnuradio] Padding burtsy blocks

2015-08-24 Thread devin kelly 
I have a flowgraph that I'm trying to develop in simulation first before
deploying to some sort of hardware like a USRP.  The flowgraph begins with
a ZMQ Pull Source and then I have all my signal processing blocks
afterwards (eventually there would be a UHD Sink).  The ZMQ block only
produces samples when it receives a message so when it doesn't receive
samples the flowgraph doesn't run.

If the work function for any block is only called when there are samples in
the input buffer I don't see how adding any blocks after my ZMQ Pull Source
could help.  So that leaves making my own ZMQ Pull Source that emits zeros
when it has no other message.  Do I have any other options?  If I add a
this feature would be useful to merge back into GR or is this not really an
intended use case for GR?

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

[Discuss-gnuradio] flags / xml to supress Add throttle warning ?

2015-08-24 Thread Tom McDermott 
I've built an OOT for some physical SDR hardware.
However, when compiling a flowgraph in gnruradio-companion
it prints a warning message about no audio or rf sink, so please
insert a throttle.

Since my module actually paces the samples in hardware, I don't
want a throttle.  How can I supress the warning message?

Looking through some GRC blocks, I've found two tags:

1

and another is

throttle

Reading the documentation that discusses XML tags in the block,
http://gnuradio.org/redmine/projects/gnuradio/wiki/GNURadioCompanion#Creating-the-XML-Block-Definition
it doesn't mention these tags, or what they do. Is one of these the
correct way to suppress the flowgraph compile warning?

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

Re: [Discuss-gnuradio] flags / xml to supress Add throttle warning ?

2015-08-24 Thread Marcus D. Leech 

On 08/24/2015 11:26 PM, Tom McDermott wrote:

I've built an OOT for some physical SDR hardware.
However, when compiling a flowgraph in gnruradio-companion
it prints a warning message about no audio or rf sink, so please
insert a throttle.

Since my module actually paces the samples in hardware, I don't
want a throttle.  How can I supress the warning message?

Looking through some GRC blocks, I've found two tags:

1

and another is

throttle

Reading the documentation that discusses XML tags in the block,
http://gnuradio.org/redmine/projects/gnuradio/wiki/GNURadioCompanion#Creating-the-XML-Block-Definition
it doesn't mention these tags, or what they do. Is one of these the
correct way to suppress the flowgraph compile warning?

-- Tom, N5EG





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

I think the newer way is to use throttle

But for backwards compat, you can use 1

It's an indicator to GRC that this block provides a flow-regulated data 
stream.



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

Re: [Discuss-gnuradio] flags / xml to supress Add throttle warning ?

2015-08-24 Thread Tom McDermott 
Thanks.   throttle it will be ...  (works fine).

-- Tom, N5EG



On Mon, Aug 24, 2015 at 8:59 PM, Marcus D. Leech  wrote:

> On 08/24/2015 11:26 PM, Tom McDermott wrote:
>
> I've built an OOT for some physical SDR hardware.
> However, when compiling a flowgraph in gnruradio-companion
> it prints a warning message about no audio or rf sink, so please
> insert a throttle.
>
> Since my module actually paces the samples in hardware, I don't
> want a throttle.  How can I supress the warning message?
>
> Looking through some GRC blocks, I've found two tags:
>
> 1
>
> and another is
>
> throttle
>
> Reading the documentation that discusses XML tags in the block,
>
> http://gnuradio.org/redmine/projects/gnuradio/wiki/GNURadioCompanion#Creating-the-XML-Block-Definition
> it doesn't mention these tags, or what they do. Is one of these the
> correct way to suppress the flowgraph compile warning?
>
> -- Tom, N5EG
>
>
>
>
>
> ___
> Discuss-gnuradio mailing 
> listDiscuss-gnuradio@gnu.orghttps://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
> I think the newer way is to use throttle
>
> But for backwards compat, you can use 1
>
> It's an indicator to GRC that this block provides a flow-regulated data
> stream.
>
>
>
> ___
> 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] Capturing DMR (MOTOTRBO) data with gnuradio

2015-08-24 Thread Sergei Franco 
Hello there,

I am trying to capture DMR/MOTOTRBO data packets (not voice) with gnuradio.
I have found gr-dsd block that successfully decodes the signal in question.
Only problem is that gr-dsd does not "unpack" the data packets, it only
outputs voice audio (float).

All I get from gr-dsd (apart from voice) is output like this (in terminal):

[slot0]  slot1   Slot idle
 slot0  [slot1]  CSBK
[slot0]  slot1   Slot idle
 slot0  [slot1]  CSBK
[slot0]  slot1   Slot idle
 slot0  [slot1]  RATE 1/2 DATA
[slot0]  slot1   Slot idle
 slot0  [slot1]  CSBK
[slot0]  slot1   Slot idle
 slot0  [slot1]  RATE 1/2 DATA
...

The target system is Ubuntu 14.04LTS (if it makes any difference).
Another option is not to use gr-dsd, but plainly demodulate the signal with
C4FM/4FSK (for which I am yet to find a stand alone demodulator that works
with current gnuradio), and then cut out the data in "post".

I have looked at the gr-dsd source and it is way too complicated for my
skill set to modify it to output data as byte stream.

I have tried to install gr-op25 (just so I can use 4FSK demod block), but
it was way too "heavy" (way too many dependencies).
I failed to install gr-fsk4 (
http://vk2lk.com/Wireless/Franks/GnuradioFourLevelFSK.html), it looks like
it is incompatible with current gnuradio (it fails on missing
gnuradio-core).

I suspect it is possible to come up with 4FSK demod with just using
standard gnuradio blocks, my understanding of signal processing is very
limited...

TL;DR: how can I extract the byte contents out of DMR data packets with
gnuradio?


Thanks a lot!

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

Re: [Discuss-gnuradio] Padding burtsy blocks

2015-08-24 Thread Marcus Müller 
Hi Devin,

the "padding with zeros unless samples occur within a specific time" job
can be done with gr-eventstream [1] [2] , but:

If you're going to use USRP sink anyway, what about using tagged stream
blocks[3]?
You could replace your "Pull Source" with a "Pull Message Source" ->
"PDU to tagged stream"->signal processing->"USRP Sink" (with "packet
length tag name" set accordingly)

Best regards,
Marcus

[1] https://github.com/osh/gr-eventstream
[2] http://oshearesearch.com/tag/gr-eventstream/
[3] https://gnuradio.org/doc/doxygen/page_tagged_stream_blocks.html
On 25.08.2015 04:00, devin kelly wrote:
> I have a flowgraph that I'm trying to develop in simulation first
> before deploying to some sort of hardware like a USRP.  The flowgraph
> begins with a ZMQ Pull Source and then I have all my signal processing
> blocks afterwards (eventually there would be a UHD Sink).  The ZMQ
> block only produces samples when it receives a message so when it
> doesn't receive samples the flowgraph doesn't run.  
>
> If the work function for any block is only called when there are
> samples in the input buffer I don't see how adding any blocks after my
> ZMQ Pull Source could help.  So that leaves making my own ZMQ Pull
> Source that emits zeros when it has no other message.  Do I have any
> other options?  If I add a this feature would be useful to merge back
> into GR or is this not really an intended use case for GR?
>
> Thanks,
> Devin
>
>
> ___
> 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