Re: [Discuss-gnuradio] hier_blocks2 error

[Koslowski, Sebastian (CEL)]

On 08/13/2015 08:38 AM, bob wole wrote:
> I am using gnruadio 3.7.8. I have a module (python) which is working
> well for version 3.6.3. In made necessary changes so that it can work
> with gnuradio 3.7.8. However I am getting following error
>
>   File
> "/usr/local/lib/python2.7/dist-packages/gnuradio/gr/hier_block2.py",
> line 92, in __getattr__
> return getattr(self._impl, name)
> AttributeError: 'hier_block2_sptr' object has no attribute '_hb'
>
>
> I spent a lot of time to figure out this but could not resolve it, so
> I thought to get help from mailing list.
>
> Is this a bug or I am doing something wrong? 

What your seeing is the interface wrapper looking for an attribute in
the wrapped instance 'self._impl' which used to be called 'self._hb'. So
it tries to lookup that first - and fails. Since both _impl and _hb are
marked protected they should not be accessed from outside the wrapper
directly (I remember some WXGUI code did that, but that has been fixed).
In the gnuradio tree I can't seem to find anything like this.

Can you check and see from where this Exception is raised from?

Sebastian

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

Re: [Discuss-gnuradio] error with running wifi_loopback.grc from gr-ieee802-11

[Tian Alvin]

Hi Paul,

Thanks very much for your help! I have disabled logging and debug in OFDM
Parse MAC block, but the error is still there.

Did you also see the below error in your case when (gdb) run
wifi_loopback.py?
[image: Inline image 1]
ImportError: No module named 'libstdcxx'


Thanks


On Wed, Aug 12, 2015 at 9:07 PM, Paul Garver  wrote:

> Tian,
>
> Disable logging and debug in the GRC flowgraph.  See if this solves the
> problem. For reference, see [1].
>
>
> [1]
> https://lists.gnu.org/archive/html/discuss-gnuradio/2015-07/msg00289.html
>
> On 08/12/2015 01:23 PM, discuss-gnuradio-requ...@gnu.org wrote:
>
> Send Discuss-gnuradio mailing list submissions to
>   discuss-gnuradio@gnu.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>   https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> or, via email, send a message with subject or body 'help' to
>   discuss-gnuradio-requ...@gnu.org
>
> You can reach the person managing the list at
>   discuss-gnuradio-ow...@gnu.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Discuss-gnuradio digest..."
>
>
>
> Today's Topics:
>
>1. error with running wifi_loopback.grc from   gr-ieee802-11
>   (Tian Alvin)
>
>
>
> ___
> Discuss-gnuradio mailing 
> listDiscuss-gnuradio@gnu.orghttps://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] error with running wifi_loopback.grc from gr-ieee802-11

[Garver, Paul W]

Make sure logging is disabled on ALL blocks. I haven't seen that libstdcxx 
error before, but I do have the segfaults with the logging in Ubuntu 15.04 with 
pybombs install. 

Paul Garver


> On Aug 13, 2015, at 7:33 AM, Tian Alvin  wrote:
> 
> Hi Paul,
> 
> Thanks very much for your help! I have disabled logging and debug in OFDM 
> Parse MAC block, but the error is still there.
> 
> Did you also see the below error in your case when (gdb) run wifi_loopback.py?
> 
> ImportError: No module named 'libstdcxx'
> 
> 
> Thanks
> 
> 
>> On Wed, Aug 12, 2015 at 9:07 PM, Paul Garver  wrote:
>> Tian,
>> 
>> Disable logging and debug in the GRC flowgraph.  See if this solves the 
>> problem. For reference, see [1].
>> 
>> 
>> [1] https://lists.gnu.org/archive/html/discuss-gnuradio/2015-07/msg00289.html
>> 
>>> On 08/12/2015 01:23 PM, discuss-gnuradio-requ...@gnu.org wrote:
>>> Send Discuss-gnuradio mailing list submissions to
>>> discuss-gnuradio@gnu.org
>>> 
>>> To subscribe or unsubscribe via the World Wide Web, visit
>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>> or, via email, send a message with subject or body 'help' to
>>> discuss-gnuradio-requ...@gnu.org
>>> 
>>> You can reach the person managing the list at
>>> discuss-gnuradio-ow...@gnu.org
>>> 
>>> When replying, please edit your Subject line so it is more specific
>>> than "Re: Contents of Discuss-gnuradio digest..."
>>> 
>>> 
>>> Today's Topics:
>>> 
>>>1. error with running wifi_loopback.grc from gr-ieee802-11
>>>   (Tian Alvin)
>>> 
>>> 
>>> ___
>>> 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] error with running wifi_loopback.grc from gr-ieee802-11

[Bastian Bloessl]

Hi,

I just replied on github

https://github.com/bastibl/gr-ieee802-11/issues/18#issuecomment-130651522

It would be great if you could try what I suggest there.

Best,
Bastian

On 08/13/2015 02:32 PM, Garver, Paul W wrote:

Make sure logging is disabled on ALL blocks. I haven't seen that
libstdcxx error before, but I do have the segfaults with the logging in
Ubuntu 15.04 with pybombs install.

Paul Garver


On Aug 13, 2015, at 7:33 AM, Tian Alvin mailto:tianye000...@gmail.com>> wrote:


Hi Paul,

Thanks very much for your help! I have disabled logging and debug in
OFDM Parse MAC block, but the error is still there.

Did you also see the below error in your case when (gdb) run
wifi_loopback.py?

ImportError: No module named 'libstdcxx'


Thanks


On Wed, Aug 12, 2015 at 9:07 PM, Paul Garver mailto:garv...@gatech.edu>> wrote:

Tian,

Disable logging and debug in the GRC flowgraph.  See if this
solves the problem. For reference, see [1].


[1]
https://lists.gnu.org/archive/html/discuss-gnuradio/2015-07/msg00289.html

On 08/12/2015 01:23 PM, discuss-gnuradio-requ...@gnu.org
 wrote:

Send Discuss-gnuradio mailing list submissions to
discuss-gnuradio@gnu.org  

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
or, via email, send a message with subject or body 'help' to
discuss-gnuradio-requ...@gnu.org  


You can reach the person managing the list at
discuss-gnuradio-ow...@gnu.org  

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Discuss-gnuradio digest..."


Today's Topics:

1. error with running wifi_loopback.grc fromgr-ieee802-11
   (Tian Alvin)


___
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



--
Dipl.-Inform. Bastian Bloessl
Distributed Embedded Systems
University of Paderborn, Germany
http://www.ccs-labs.org/~bloessl/

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

Re: [Discuss-gnuradio] error with running wifi_loopback.grc from gr-ieee802-11

[Bastian Bloessl]

Hi,

yes, this is how it is supposed to look. But please read the posts at 
the bottom of the thread. Actually, it should work without modifications 
now.


Best,
Bastian

On 08/13/2015 04:03 PM, Tian Alvin wrote:

Hi Bastian,

I followed the suggestion on github:

*Use*

"std::string temp = (boost::format("encoding: %1% - length: %2% -
symbols: %3%")
% d_encoding % d_len % d_copy_symbols).str();
//mylog(temp);"

*to change* : in the ofdm_decode_signal.cc# L197&L198
"mylog(boost::format("encoding: %1% - length: %2% - symbols: %3%")
% d_encoding % d_len % d_copy_symbols);"

Now I can get the below result:

Inline image 1

Does this mean the flow graph has been run correctly?

PaulThank you very much for your suggestion and sharing!



On Thu, Aug 13, 2015 at 1:59 PM, Bastian Bloessl mailto:bloe...@ccs-labs.org>> wrote:

Hi,

I just replied on github

https://github.com/bastibl/gr-ieee802-11/issues/18#issuecomment-130651522

It would be great if you could try what I suggest there.

Best,
Bastian

On 08/13/2015 02:32 PM, Garver, Paul W wrote:

Make sure logging is disabled on ALL blocks. I haven't seen that
libstdcxx error before, but I do have the segfaults with the
logging in
Ubuntu 15.04 with pybombs install.

Paul Garver


On Aug 13, 2015, at 7:33 AM, Tian Alvin mailto:tianye000...@gmail.com>
>>
wrote:

Hi Paul,

Thanks very much for your help! I have disabled logging and
debug in
OFDM Parse MAC block, but the error is still there.

Did you also see the below error in your case when (gdb) run
wifi_loopback.py?

ImportError: No module named 'libstdcxx'


Thanks


On Wed, Aug 12, 2015 at 9:07 PM, Paul Garver
mailto:garv...@gatech.edu>
>> wrote:

 Tian,

 Disable logging and debug in the GRC flowgraph.  See if
this
 solves the problem. For reference, see [1].


 [1]

https://lists.gnu.org/archive/html/discuss-gnuradio/2015-07/msg00289.html

 On 08/12/2015 01:23 PM,
discuss-gnuradio-requ...@gnu.org

 > wrote:

 Send Discuss-gnuradio mailing list submissions to
discuss-gnuradio@gnu.org

>

 To subscribe or unsubscribe via the World Wide Web,
visit
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
 or, via email, send a message with subject or body
'help' to
discuss-gnuradio-requ...@gnu.org

>

 You can reach the person managing the list at
discuss-gnuradio-ow...@gnu.org

>

 When replying, please edit your Subject line so it
is more specific
 than "Re: Contents of Discuss-gnuradio digest..."


 Today's Topics:

 1. error with running wifi_loopback.grc from
gr-ieee802-11
(Tian Alvin)


 ___
 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


--
Dipl.-Inform. Bastian Bloessl
Distributed Embedded Sy

Re: [Discuss-gnuradio] error with running wifi_loopback.grc from gr-ieee802-11

[Tian Alvin]

Hi Bastian,

Thanks!

The file ( ofdm_decode_signal.cc) I have downloaded is still written as
(Yes--no mylog(temp) now):

"mylog(boost::format("encoding: %1% - length: %2% - symbols: %3%")
% d_encoding % d_len % d_copy_symbols);"

To make it work, I still need change it to
"std::string temp = (boost::format("encoding: %1% - length: %2% -
symbols: %3%")
% d_encoding % d_len % d_copy_symbols).str();

Actually, I don't really understand the difference between these two. What
does this change mean? Does the problem relate to log4cpp?





On Thu, Aug 13, 2015 at 3:07 PM, Bastian Bloessl 
wrote:

> Hi,
>
> yes, this is how it is supposed to look. But please read the posts at the
> bottom of the thread. Actually, it should work without modifications now.
>
> Best,
> Bastian
>
> On 08/13/2015 04:03 PM, Tian Alvin wrote:
>
>> Hi Bastian,
>>
>> I followed the suggestion on github:
>>
>> *Use*
>>
>> "std::string temp = (boost::format("encoding: %1% - length: %2% -
>> symbols: %3%")
>> % d_encoding % d_len % d_copy_symbols).str();
>> //mylog(temp);"
>>
>> *to change* : in the ofdm_decode_signal.cc# L197&L198
>> "mylog(boost::format("encoding: %1% - length: %2% - symbols: %3%")
>> % d_encoding % d_len % d_copy_symbols);"
>>
>> Now I can get the below result:
>>
>> Inline image 1
>>
>> Does this mean the flow graph has been run correctly?
>>
>> PaulThank you very much for your suggestion and sharing!
>>
>>
>>
>> On Thu, Aug 13, 2015 at 1:59 PM, Bastian Bloessl > > wrote:
>>
>> Hi,
>>
>> I just replied on github
>>
>>
>> https://github.com/bastibl/gr-ieee802-11/issues/18#issuecomment-130651522
>>
>> It would be great if you could try what I suggest there.
>>
>> Best,
>> Bastian
>>
>> On 08/13/2015 02:32 PM, Garver, Paul W wrote:
>>
>> Make sure logging is disabled on ALL blocks. I haven't seen that
>> libstdcxx error before, but I do have the segfaults with the
>> logging in
>> Ubuntu 15.04 with pybombs install.
>>
>> Paul Garver
>>
>>
>> On Aug 13, 2015, at 7:33 AM, Tian Alvin > 
>> >>
>> wrote:
>>
>> Hi Paul,
>>
>> Thanks very much for your help! I have disabled logging and
>> debug in
>> OFDM Parse MAC block, but the error is still there.
>>
>> Did you also see the below error in your case when (gdb) run
>> wifi_loopback.py?
>> 
>> ImportError: No module named 'libstdcxx'
>>
>>
>> Thanks
>>
>>
>> On Wed, Aug 12, 2015 at 9:07 PM, Paul Garver
>> mailto:garv...@gatech.edu>
>> >>
>> wrote:
>>
>>  Tian,
>>
>>  Disable logging and debug in the GRC flowgraph.  See if
>> this
>>  solves the problem. For reference, see [1].
>>
>>
>>  [1]
>>
>> https://lists.gnu.org/archive/html/discuss-gnuradio/2015-07/msg00289.html
>>
>>  On 08/12/2015 01:23 PM,
>> discuss-gnuradio-requ...@gnu.org
>> 
>>  > > wrote:
>>
>>  Send Discuss-gnuradio mailing list submissions to
>> discuss-gnuradio@gnu.org
>> 
>> > >
>>
>>  To subscribe or unsubscribe via the World Wide Web,
>> visit
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>  or, via email, send a message with subject or body
>> 'help' to
>> discuss-gnuradio-requ...@gnu.org
>> 
>> > >
>>
>>  You can reach the person managing the list at
>> discuss-gnuradio-ow...@gnu.org
>> 
>> > >
>>
>>  When replying, please edit your Subject line so it
>> is more specific
>>  than "Re: Contents of Discuss-gnuradio digest..."
>>
>>
>>  Today's Topics:
>>
>>  1. error with running wifi_loopback.grc from
>> gr-ieee802-11
>> (Tian Alvin)
>>
>>
>>  ___
>>

[Discuss-gnuradio] R820T2/RTL2838U

[Antonny Caesar]

Hello, guys.

Please, does someone know if these two RTL devices (R820T2 and RTL2838U)
work fine with Gnuradio? Which is better?

Thanks a lot.

Cheers,
Antony

-- 
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] error with running wifi_loopback.grc from gr-ieee802-11

[Bastian Bloessl]

Hi,

On 08/13/2015 04:20 PM, Tian Alvin wrote:

"mylog(boost::format("encoding: %1% - length: %2% - symbols: %3%")
% d_encoding % d_len % d_copy_symbols);"

To make it work, I still need change it to
"std::string temp = (boost::format("encoding: %1% - length: %2% -
symbols: %3%")
% d_encoding % d_len % d_copy_symbols).str();

Actually, I don't really understand the difference between these two.
What does this change mean? Does the problem relate to log4cpp?


This was suggested to debug the problem, not as a fix.

The problem is described in the issue you referenced (scroll down) and 
hopefully fixed by this commit

https://github.com/bastibl/gr-ieee802-11/commit/77548c73a95b0460250ef477e309190f20bf8d95

Please update the module with git.

Best,
Bastian







On Thu, Aug 13, 2015 at 3:07 PM, Bastian Bloessl mailto:bloe...@ccs-labs.org>> wrote:

Hi,

yes, this is how it is supposed to look. But please read the posts
at the bottom of the thread. Actually, it should work without
modifications now.

Best,
Bastian

On 08/13/2015 04:03 PM, Tian Alvin wrote:

Hi Bastian,

I followed the suggestion on github:

*Use*

"std::string temp = (boost::format("encoding: %1% - length: %2% -
symbols: %3%")
% d_encoding % d_len % d_copy_symbols).str();
//mylog(temp);"

*to change* : in the ofdm_decode_signal.cc# L197&L198
"mylog(boost::format("encoding: %1% - length: %2% - symbols: %3%")
% d_encoding % d_len % d_copy_symbols);"

Now I can get the below result:

Inline image 1

Does this mean the flow graph has been run correctly?

PaulThank you very much for your suggestion and sharing!



On Thu, Aug 13, 2015 at 1:59 PM, Bastian Bloessl
mailto:bloe...@ccs-labs.org>
>> wrote:

 Hi,

 I just replied on github


https://github.com/bastibl/gr-ieee802-11/issues/18#issuecomment-130651522

 It would be great if you could try what I suggest there.

 Best,
 Bastian

 On 08/13/2015 02:32 PM, Garver, Paul W wrote:

 Make sure logging is disabled on ALL blocks. I haven't
seen that
 libstdcxx error before, but I do have the segfaults
with the
 logging in
 Ubuntu 15.04 with pybombs install.

 Paul Garver


 On Aug 13, 2015, at 7:33 AM, Tian Alvin
mailto:tianye000...@gmail.com>
 >
  
>
  
 >
  
 >> wrote:

  Send Discuss-gnuradio mailing list
submissions to
discuss-gnuradio@gnu.org 
 >
 
 >>

   

Re: [Discuss-gnuradio] error with running wifi_loopback.grc from gr-ieee802-11

[Tian Alvin]

Okay. I see. Thank you very much for your help!

On Thu, Aug 13, 2015 at 3:34 PM, Bastian Bloessl 
wrote:

> Hi,
>
> On 08/13/2015 04:20 PM, Tian Alvin wrote:
>
>> "mylog(boost::format("encoding: %1% - length: %2% - symbols: %3%")
>> % d_encoding % d_len % d_copy_symbols);"
>>
>> To make it work, I still need change it to
>> "std::string temp = (boost::format("encoding: %1% - length: %2% -
>> symbols: %3%")
>> % d_encoding % d_len % d_copy_symbols).str();
>>
>> Actually, I don't really understand the difference between these two.
>> What does this change mean? Does the problem relate to log4cpp?
>>
>
> This was suggested to debug the problem, not as a fix.
>
> The problem is described in the issue you referenced (scroll down) and
> hopefully fixed by this commit
>
> https://github.com/bastibl/gr-ieee802-11/commit/77548c73a95b0460250ef477e309190f20bf8d95
>
> Please update the module with git.
>
> Best,
> Bastian
>
>
>>
>>
>>
>>
>> On Thu, Aug 13, 2015 at 3:07 PM, Bastian Bloessl > > wrote:
>>
>> Hi,
>>
>> yes, this is how it is supposed to look. But please read the posts
>> at the bottom of the thread. Actually, it should work without
>> modifications now.
>>
>> Best,
>> Bastian
>>
>> On 08/13/2015 04:03 PM, Tian Alvin wrote:
>>
>> Hi Bastian,
>>
>> I followed the suggestion on github:
>>
>> *Use*
>>
>> "std::string temp = (boost::format("encoding: %1% - length: %2% -
>> symbols: %3%")
>> % d_encoding % d_len % d_copy_symbols).str();
>> //mylog(temp);"
>>
>> *to change* : in the ofdm_decode_signal.cc# L197&L198
>> "mylog(boost::format("encoding: %1% - length: %2% - symbols: %3%")
>> % d_encoding % d_len % d_copy_symbols);"
>>
>> Now I can get the below result:
>>
>> Inline image 1
>>
>> Does this mean the flow graph has been run correctly?
>>
>> PaulThank you very much for your suggestion and sharing!
>>
>>
>>
>> On Thu, Aug 13, 2015 at 1:59 PM, Bastian Bloessl
>> mailto:bloe...@ccs-labs.org>
>> >>
>> wrote:
>>
>>  Hi,
>>
>>  I just replied on github
>>
>>
>> https://github.com/bastibl/gr-ieee802-11/issues/18#issuecomment-130651522
>>
>>  It would be great if you could try what I suggest there.
>>
>>  Best,
>>  Bastian
>>
>>  On 08/13/2015 02:32 PM, Garver, Paul W wrote:
>>
>>  Make sure logging is disabled on ALL blocks. I haven't
>> seen that
>>  libstdcxx error before, but I do have the segfaults
>> with the
>>  logging in
>>  Ubuntu 15.04 with pybombs install.
>>
>>  Paul Garver
>>
>>
>>  On Aug 13, 2015, at 7:33 AM, Tian Alvin
>> mailto:tianye000...@gmail.com>
>>  > >
>>  >  > >  wrote:
>>
>>  Hi Paul,
>>
>>  Thanks very much for your help! I have disabled
>> logging and
>>  debug in
>>  OFDM Parse MAC block, but the error is still there.
>>
>>  Did you also see the below error in your case when
>> (gdb) run
>>  wifi_loopback.py?
>>  
>>  ImportError: No module named 'libstdcxx'
>>
>>
>>  Thanks
>>
>>
>>  On Wed, Aug 12, 2015 at 9:07 PM, Paul Garver
>>  mailto:garv...@gatech.edu>
>> >
>>  >  > >
>>   Tian,
>>
>>   Disable logging and debug in the GRC
>> flowgraph.  See if
>>  this
>>   solves the problem. For reference, see [1].
>>
>>
>>   [1]
>>
>> https://lists.gnu.org/archive/html/discuss-gnuradio/2015-07/msg00289.html
>>
>>   On 08/12/2015 01:23 PM,
>> discuss-gnuradio-requ...@gnu.org
>> 
>>  > >
>>   > 
>>  > >> wrote:

[Discuss-gnuradio] Writing Messages to a File

[Paul Garver]

Does anyone have methods to write messages to a file? My use case is tagging 
baseband sample numbers of the start/end of WLAN packets in gr-ieee80211.  It 
looks like typically people create custom blocks to deal with this such as 
messages to Wireshark.  For general metadata to go along with blobs, I think it 
makes sense to have a (blob,dictionary) pmt tuple as the message, much like 
gr-ieee80211.  I’ve implemented a file message sink block based on this premise 
which takes a list of dictionary keys in such a message and writes them to a 
csv file.  If anyone is interested I can roll it up into a feature request on 
gnuradio.org.

https://github.com/garverp/gnuradio/tree/msg_file_sink 


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

Re: [Discuss-gnuradio] R820T2/RTL2838U

[Jean-Michel FRIEDT]

these are two chips of the same device (RF front end and ADC to USB converter)
and yes, they do work well with the osmosdr source of gnuradio.

JM


Please, does someone know if these two RTL devices (R820T2 and RTL2838U)
work fine with Gnuradio? Which is better?

Thanks a lot.

Cheers,
Antony

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

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





--
JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe,  
25000 Besancon, France



This message was sent using IMP, the Internet Messaging Program.


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

Re: [Discuss-gnuradio] Writing Messages to a File

[Chris Kuethe]

I'd be very interested in seeing in such a block. I wonder if it might
be worth generalizing the file sink block somehow...

On Thu, Aug 13, 2015 at 8:06 AM, Paul Garver  wrote:
> Does anyone have methods to write messages to a file? My use case is tagging
> baseband sample numbers of the start/end of WLAN packets in gr-ieee80211.
> It looks like typically people create custom blocks to deal with this such
> as messages to Wireshark.  For general metadata to go along with blobs, I
> think it makes sense to have a (blob,dictionary) pmt tuple as the message,
> much like gr-ieee80211.  I’ve implemented a file message sink block based on
> this premise which takes a list of dictionary keys in such a message and
> writes them to a csv file.  If anyone is interested I can roll it up into a
> feature request on gnuradio.org.
>
> https://github.com/garverp/gnuradio/tree/msg_file_sink
>
> PWG
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>



-- 
GDB has a 'break' feature; why doesn't it have 'fix' too?

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

Re: [Discuss-gnuradio] Error when running GNU radio built from script

[Marcus Müller]

Hi Hoang,

current UHD master uses the "requests" python library. I think we might
be forgetting to cleanly document and check that requirement; hence,
build-gnuradio doesn't automatically install that library.

I don't know which distribution you are using, but if you're using
fedora, you can "yum install python-requests".

Best regards,
Marcus

On 08/12/2015 01:52 AM, Hoang Nguyen Tran wrote:
> Dear,
> I installed GNU radio from build_gnuradio script successful.
> Then I tried a simple FM receiver and I got this warning :
>
> UHD Warning:
> Could not locate USRP1 firmware. Please run:
>  "/usr/local/lib/uhd/utils/uhd_images_downloader.py"
>
> Then as it said, I tried to run that .py file and got this :
>
> Traceback (most recent call last):
>   File "./uhd_images_downloader", line 26, in 
> import requests
> ImportError: No module named requests
>
> Could you please help me with this ? Im using USRP1.
> Before that, I used to install GNU radio from apt-get, I got exactly
> problem, then I ran uhd_images_downloader from /usr/lib/utils and it
> worked. I also tried this time, it downloaded the images, but when i
> run GNU radio the same thing happen.
>
> Thanks
>
>
> -- 
>  -HoangNT-
> PhoneNo :  +841654248782
> Skype : hoangastro
> FB : https://www.facebook.com/kenshin.rorouni
>
>
> ___
> 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] Error when running GNU radio built from script

[Hoang Nguyen Tran]

Sorry for not reply sooner,
I also figure out that python need request library,
Then  I install it. and the problem was fixed.
following is way I install requests library:

install python pip : sudo apt-get install python-pip
install requests lib :sudo pip install requests

Thank you Marcus

On Thu, Aug 13, 2015 at 1:36 PM, Marcus Müller 
wrote:

> Hi Hoang,
>
> current UHD master uses the "requests" python library. I think we might be
> forgetting to cleanly document and check that requirement; hence,
> build-gnuradio doesn't automatically install that library.
>
> I don't know which distribution you are using, but if you're using fedora,
> you can "yum install python-requests".
>
> Best regards,
> Marcus
>
>
> On 08/12/2015 01:52 AM, Hoang Nguyen Tran wrote:
>
> Dear,
> I installed GNU radio from build_gnuradio script successful.
> Then I tried a simple FM receiver and I got this warning :
>
> UHD Warning:
> Could not locate USRP1 firmware. Please run:
>  "/usr/local/lib/uhd/utils/uhd_images_downloader.py"
>
> Then as it said, I tried to run that .py file and got this :
>
> Traceback (most recent call last):
>   File "./uhd_images_downloader", line 26, in 
> import requests
> ImportError: No module named requests
>
> Could you please help me with this ? Im using USRP1.
> Before that, I used to install GNU radio from apt-get, I got exactly
> problem, then I ran uhd_images_downloader from /usr/lib/utils and it
> worked. I also tried this time, it downloaded the images, but when i run
> GNU radio the same thing happen.
>
> Thanks
>
>
> --
>  -HoangNT-
> PhoneNo :  +841654248782
> Skype : hoangastro
> FB : https://www.facebook.com/kenshin.rorouni
>
>
> ___
> Discuss-gnuradio mailing 
> listDiscuss-gnuradio@gnu.orghttps://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>


-- 
 -HoangNT-
PhoneNo :  +841654248782
Skype : hoangastro
FB : https://www.facebook.com/kenshin.rorouni
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Error when running GNU radio built from script

[Marcus Müller]

Hi!

Don't worry, that's something everyone is happy about when noticed.
For future readers:
sudo apt-get install python-requests
should have worked too (and is preferable, usually, because it allows
your distribution to keep the library up-to-date).

Best regards,
Marcus

On 08/13/2015 07:43 PM, Hoang Nguyen Tran wrote:
> Sorry for not reply sooner,
> I also figure out that python need request library,
> Then  I install it. and the problem was fixed.
> following is way I install requests library:
>
> install python pip : sudo apt-get install python-pip
> install requests lib :sudo pip install requests
>
> Thank you Marcus
>
> On Thu, Aug 13, 2015 at 1:36 PM, Marcus Müller
> mailto:marcus.muel...@ettus.com>> wrote:
>
> Hi Hoang,
>
> current UHD master uses the "requests" python library. I think we
> might be forgetting to cleanly document and check that
> requirement; hence, build-gnuradio doesn't automatically install
> that library.
>
> I don't know which distribution you are using, but if you're using
> fedora, you can "yum install python-requests".
>
> Best regards,
> Marcus
>
>
> On 08/12/2015 01:52 AM, Hoang Nguyen Tran wrote:
>> Dear,
>> I installed GNU radio from build_gnuradio script successful.
>> Then I tried a simple FM receiver and I got this warning :
>>
>> UHD Warning:
>> Could not locate USRP1 firmware. Please run:
>>  "/usr/local/lib/uhd/utils/uhd_images_downloader.py"
>>
>> Then as it said, I tried to run that .py file and got this :
>>
>> Traceback (most recent call last):
>>   File "./uhd_images_downloader", line 26, in 
>> import requests
>> ImportError: No module named requests
>>
>> Could you please help me with this ? Im using USRP1.
>> Before that, I used to install GNU radio from apt-get, I got
>> exactly problem, then I ran uhd_images_downloader from
>> /usr/lib/utils and it worked. I also tried this time, it
>> downloaded the images, but when i run GNU radio the same thing
>> happen.
>>
>> Thanks
>>
>>
>> -- 
>>  -HoangNT-
>> PhoneNo :  +841654248782 
>> Skype : hoangastro
>> FB : https://www.facebook.com/kenshin.rorouni
>>
>>
>> ___
>> 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
>
>
>
>
> -- 
>  -HoangNT-
> PhoneNo :  +841654248782 
> Skype : hoangastro
> FB : https://www.facebook.com/kenshin.rorouni

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

[Discuss-gnuradio] GQRX raw IQ file format / structure ?

[M Dammer]

GQRX has a built-in I/Q recorder (tools menu) to save raw I/Q files. I
would like to process these files with Python and other signal
processing software. Does anybody know the exact format and structure of
these files ? I am only aware of the filename in the format
gqrx_DATE_TIME_FREQ_SAMPLERATE_DEVICE.raw
tnx, Mark

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

Re: [Discuss-gnuradio] GQRX raw IQ file format / structure ?

[Chris Kuethe]

cf32, pairs of 32-bit floats representing I and Q. GnuRadio's file
source can read these directly.

On Thu, Aug 13, 2015 at 11:23 AM, M Dammer  wrote:
> GQRX has a built-in I/Q recorder (tools menu) to save raw I/Q files. I
> would like to process these files with Python and other signal
> processing software. Does anybody know the exact format and structure of
> these files ? I am only aware of the filename in the format
> gqrx_DATE_TIME_FREQ_SAMPLERATE_DEVICE.raw
> tnx, Mark
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio



-- 
GDB has a 'break' feature; why doesn't it have 'fix' too?

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

Re: [Discuss-gnuradio] GQRX raw IQ file format / structure ?

[M Dammer]

Thanks for the quick reply. I tried to use sox to convert the files into
WAV files to read into other software and it worked fine:
sox -t raw -e floating-point -b 32 -c 2 -r 192000
./gqrx_20150812_193915_113821000_192000_fc.raw  test.wav

On 13/08/15 19:28, Chris Kuethe wrote:
> cf32, pairs of 32-bit floats representing I and Q. GnuRadio's file
> source can read these directly.
>
> On Thu, Aug 13, 2015 at 11:23 AM, M Dammer  wrote:
>> GQRX has a built-in I/Q recorder (tools menu) to save raw I/Q files. I
>> would like to process these files with Python and other signal
>> processing software. Does anybody know the exact format and structure of
>> these files ? I am only aware of the filename in the format
>> gqrx_DATE_TIME_FREQ_SAMPLERATE_DEVICE.raw
>> tnx, Mark
>>
>> ___
>> 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] bidirectional with Socket PDU

[Jason Matusiak]

This will probably show my networking ignorance, but is there a way to
use the socket PDU for bi-directional purposes?  I see that it has a PDU
in and out, but I cant' seem to get it to work.

What I am doing is connection netcat to it with the PDU in UDP Server
mode with "nc -u localhost 52001" and I can transmit to it.  But I know
that I cannot open a listening port with "nc -ul localhost 52001" since
the port is bound.

Is there a way to write and listen on the same port, or am I totally
screwing how networking works (the only reason I would think there might
be a way is because the GRC script allows me to connect the PDU in and
out at the same time without throwing an error)?

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

Re: [Discuss-gnuradio] bidirectional with Socket PDU

[Tim]

You should be fine connecting both input and output ports at the same
time for exactly this purpose!
-Tim

On 08/13/2015 03:29 PM, Jason Matusiak wrote:
> This will probably show my networking ignorance, but is there a way to
> use the socket PDU for bi-directional purposes?  I see that it has a PDU
> in and out, but I cant' seem to get it to work.
>
> What I am doing is connection netcat to it with the PDU in UDP Server
> mode with "nc -u localhost 52001" and I can transmit to it.  But I know
> that I cannot open a listening port with "nc -ul localhost 52001" since
> the port is bound.
>
> Is there a way to write and listen on the same port, or am I totally
> screwing how networking works (the only reason I would think there might
> be a way is because the GRC script allows me to connect the PDU in and
> out at the same time without throwing an error)?
>
> ___
> 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] bidirectional with Socket PDU

[Jason Matusiak]

> You should be fine connecting both input and output ports at the same
> time for exactly this purpose!
OK, maybe it is an issue with netcat then.  I don't think one netcat
instance can both transmit and receive, so when I try to run it twice,
that is when it dies. I will have to look for another app that can do
something similar for testing purposes. Thanks Tim.

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

Re: [Discuss-gnuradio] bidirectional with Socket PDU

[Jason Matusiak]

> OK, maybe it is an issue with netcat then. I don't think one netcat
> instance can both transmit and receive, so when I try to run it twice,
> that is when it dies. I will have to look for another app that can do
> something similar for testing purposes. Thanks Tim.

If someone has an alternative, I am all ears (I'm coming up empty).

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

[Discuss-gnuradio] 3.7.8 build problem 'cannot find -lcblas'

[Barry Jackson]

Trying to update our Mageia package to 3.7.8 using the release tarball, 
we are hitting this:


[ 70%] Building CXX object 
gr-wavelet/lib/CMakeFiles/gnuradio-wavelet.dir/wvps_ff_impl.cc.o

Linking CXX shared library libgnuradio-wavelet-3.7.8.so
/usr/bin/ld: cannot find -lcblas
collect2: error: ld returned 1 exit status

Any ideas?

libatlas-devel is installed.

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

Re: [Discuss-gnuradio] FFT Scaling

[Jeff Long]

On 08/12/2015 05:39 PM, West, Nathan wrote:

On Wed, Aug 12, 2015 at 12:31 PM, West, Nathan
mailto:n...@ostatemail.okstate.edu>> wrote:

On Wed, Aug 12, 2015 at 10:51 AM, Gerome Jan L
mailto:geromejanlla...@gmail.com>> wrote:

There is an internal scaling effect of |fftlen| (the length of
your FFT) in the FFT block. How do I unscale or remove the
scaling factor in the python generated by thr GRC? I tried the
one suggested in the faq,

|... forward FFT --> multiply_const_cc(fftlen*[1.0/fftlen,]) -->
reverse FFT ...

|
|but it doesn't seem to work. I know I am missing something. How
do I insert this into this line of code in my python?

1. self.fft_vxx_0 = fft.fft_vcc(1024, True,
(window.rectangular(1024)), True, 1)
|
|or here?
2. self.blocks_complex_to_mag_squared_0 =
blocks.complex_to_mag_squared(1024)

|
|Thank you in advance.
|
|
|
|Attached is my flow graph.


|

Best,

*Gerome Jan M. Llames *


"Design is not just what it looks like and feels like. Design is
how it works."  - Steve Jobs


What do you expect the constant to be? fftlen*[1.0/fftlen,] = [1],
unless I'm having a really slow day.


It's been pointed out to me that I am having a slow day. Taking a step
back... when you say "it doesn't seem to work", what exactly does that
mean? What do you observer that is different from what you expect?



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



Try multiply_const_cc( 1.0/fftlen, vlen=fftlen )

- Jeff




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

Re: [Discuss-gnuradio] 3.7.8 build problem 'cannot find -lcblas'

[Chris Kuethe]

$ dpkg -S /usr/lib/libcblas.*
libatlas-base-dev: /usr/lib/libcblas.a
libatlas-base-dev: /usr/lib/libcblas.so
libatlas3-base: /usr/lib/libcblas.so.3
libatlas3-base: /usr/lib/libcblas.so.3gf

$ dpkg -S /usr/lib/pkgconfig/*blas*pc
libatlas-base-dev: /usr/lib/pkgconfig/blas-atlas.pc
libblas-dev: /usr/lib/pkgconfig/blas-netlib.pc
libopenblas-dev: /usr/lib/pkgconfig/blas-openblas.pc
dpkg-query: no path found matching pattern /usr/lib/pkgconfig/blas.pc
libopenblas-dev: /usr/lib/pkgconfig/lapack-openblas.pc

1) is the correct package installed?
2) is there a libcblas.* in your linker path?
3) did cmake not find the right pkgconfig file?
4) you could rerun make with more verbose output (add "V=1") to see
what exactly failed.

On Thu, Aug 13, 2015 at 4:17 PM, Barry Jackson  wrote:
> Trying to update our Mageia package to 3.7.8 using the release tarball, we
> are hitting this:
>
> [ 70%] Building CXX object
> gr-wavelet/lib/CMakeFiles/gnuradio-wavelet.dir/wvps_ff_impl.cc.o
> Linking CXX shared library libgnuradio-wavelet-3.7.8.so
> /usr/bin/ld: cannot find -lcblas
> collect2: error: ld returned 1 exit status
>
> Any ideas?
>
> libatlas-devel is installed.
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio



-- 
GDB has a 'break' feature; why doesn't it have 'fix' too?

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