Re: [Discuss-gnuradio] INFO: Detected an invalid packet at item INFO: Parser returned #f

2015-01-29 Thread Bastian Bloessl
Hi, On 01/29/2015 03:13 PM, zs wrote: Can you tell me,for general,in which circumstance,the packet header maybe corrupt? This is very hard to tell since I don't know what you are doing. I guess you use a header_formatter in your flow graph and (for whatever reason) its header_parse method

Re: [Discuss-gnuradio] USRP B200 host BW with USB 3.0/2.0

2015-01-29 Thread Jorge Gallo
Martin, The alternative of a USB 3.0 is not having 5 USRPs. It is just reading 5 times at different centrer frequencies in order to get 40MHz information although that information will not be gathered at the same time. For my application I just need to see the sprectrum. I do not need to

[Discuss-gnuradio] Issue with Results from GR-CDMA

2015-01-29 Thread Frank Pinto
Hello sorry for the last message thought i attached my screenshot results at first. I am having some problems as to whether the information from the cdma transmission and reception are accurate. I have posted my screenshots for clarification

Re: [Discuss-gnuradio] Asking help about gr-ieee802-11

2015-01-29 Thread Bastian Bloessl
Either python3 is selected by cmake or (maybe) your swig version does not work. The first problem should have been fixed with the most recent commit (3 days ago). On 29 Jan 2015, at 09:15, Activecat active...@gmail.com wrote: Dear Sir, Thank you very much for your prompt response. I

Re: [Discuss-gnuradio] help

2015-01-29 Thread Tom Rondeau
On Tue, Jan 27, 2015 at 3:26 AM, mery diana merydiana1...@gmail.com wrote: dear all members of milist i have tried to build aistx module using gr-moodtool, i got the source from github where using gnuradio 3.6 and i have modified to gnuradio 3.7 as instruction in

Re: [Discuss-gnuradio] Asking help about gr-ieee802-11

2015-01-29 Thread Bastian Bloessl
Hi, On 29 Jan 2015, at 08:37, Activecat active...@gmail.com wrote: error messages: Param - Value(value): Value ieee802_11.wifi_signal_field() cannot be evaluated: name 'ieee802_11' is not defined Please start an interactive python session and ‘import ieee802_11’. This will

Re: [Discuss-gnuradio] Asking help about gr-ieee802-11

2015-01-29 Thread Activecat
Dear Sir, Thank you very much for your prompt response. I really appreciate your help. Refer below result: sgku@mmu2: ~ $ ipython Python 2.7.3 (default, Mar 14 2014, 11:57:14) Type copyright, credits or license for more information. IPython 0.13.1 -- An enhanced Interactive Python. ?

Re: [Discuss-gnuradio] Asking help about gr-ieee802-11

2015-01-29 Thread Activecat
Dear Bastian, Yes, this solves all the problems. I just get the current commit and recompile, everything works ! Thank you very much. On Thu, Jan 29, 2015 at 4:20 PM, Bastian Bloessl bloe...@ccs-labs.org wrote: Either python3 is selected by cmake or (maybe) your swig version does not work.

Re: [Discuss-gnuradio] QTGUI Issue

2015-01-29 Thread Tom Rondeau
On Wed, Jan 28, 2015 at 2:06 PM, Richard Bell richard.be...@gmail.com wrote: If I attempt to manually configure the pyqt4 source that pybombs installed to pybombs/src/pyqt4, by executing the configure command I found in pyqt4's recipe file, the following errors occur: *[tsvcis@tsvtester

Re: [Discuss-gnuradio] INFO: Detected an invalid packet at item INFO: Parser returned #f

2015-01-29 Thread Bastian Bloessl
Hi, On 01/29/2015 01:03 PM, zs wrote: Detected an invalid packet at item INFO: Parser returned #f. The answer may be RF settings are distorting your signal or others.I want to ask a question.Which block in gnuradio give us this hint.Where is the source code of the block?And have someone can

Re: [Discuss-gnuradio] USRP B200 host BW with USB 3.0/2.0

2015-01-29 Thread Ralph A. Schmid, dk5ras
I made tests with the bladeRF at 30 MHz bandwidth, and I was able to see the spectrum just fine, not matter if I used a USB2 or a USB3 cable. No hacks, no switching chunks of the spectrum, just using a standard receiver program. The lost samples are not a problem as longs as you do not want to

Re: [Discuss-gnuradio] USRP B200 host BW with USB 3.0/2.0

2015-01-29 Thread Martin Braun
On 01/29/2015 01:48 PM, Jorge Gallo wrote: I understand the given values of host bandwidth for each protocol: USB 2.0 8 (MS/s @ 16-bit I/Q) If you go down to 8-bit IQ, you will get twice that amount, if that's any help. USB 3.061.44 (MS/s @ 16-bit I/Q)

[Discuss-gnuradio] INFO: Detected an invalid packet at item INFO: Parser returned #f

2015-01-29 Thread zs
Hi all: Thank you in advance.I have searched the questionINFO: Detected an invalid packet at item INFO: Parser returned #f. The answer may be RF settings are distorting your signal or others.I want to ask a question.Which block in gnuradio give us this hint.Where is the source code of

[Discuss-gnuradio] USRP B200 host BW with USB 3.0/2.0

2015-01-29 Thread Jorge Gallo
I understand the given values of host bandwidth for each protocol: USB 2.0 8 (MS/s @ 16-bit I/Q) USB 3.061.44 (MS/s @ 16-bit I/Q) However I would like to process 40MHz of analogue BW in GNURadio over USB 2.0 I fully understand a continuous reception is not

Re: [Discuss-gnuradio] USRP B200 host BW with USB 3.0/2.0

2015-01-29 Thread Ralph A. Schmid, dk5ras
I understand his question that he just wants to let the whole thing pump out samples, and he takes only a portion of it. I have no idea if this works in a controlled manner, but at least for spectrum display this works just fine, the lost samples are not a big issue. Ralph. -Original

Re: [Discuss-gnuradio] INFO: Detected an invalid packet at item INFO: Parser returned #f

2015-01-29 Thread zs
Hi Bastian: Thank you so much for your kindly reply.Can you tell me,for general,in which circumstance,the packet header maybe corrupt? Thank you so much. Best regards, zs At 2015-01-29 20:44:13, Bastian Bloessl bloe...@ccs-labs.org wrote: Hi, On 01/29/2015

Re: [Discuss-gnuradio] USRP B200 host BW with USB 3.0/2.0

2015-01-29 Thread Jorge Gallo
How is that possible since only 8MHz can be placed over USB 2.0 ? On one hand I have a B200 which is supposed to deliver 56 MHz. On the other hand, for my final application, I am thinking of a low-cost host (such as BeagleBone Black) which I am afraid only has USB 2.0 My question was about

[Discuss-gnuradio] [coproc] Scheduling next CoProc WG Call

2015-01-29 Thread Douglas Geiger
I've been a bit slow about organizing the first working group call of 2015, so let's get things rolling: I've selected a couple times in early Feb., and for those that are interested in helping to close out the outstanding issues created after GrCon'14, please indicate what times are good for you:

[Discuss-gnuradio] OOT Python Block

2015-01-29 Thread Richard Bell
I've created a python block that I've tested via command line. It passes all qa tests. I've also created an xml file for it and installed it. I followed every step the OOT Python Tutorial explains. I see the category and block in gnuradio-companion. When I use my block in a flowgraph, upon to

Re: [Discuss-gnuradio] INFO: Detected an invalid packet at item INFO: Parser returned #f

2015-01-29 Thread zs
Hi Bastian: Thank you so much.I use the ofdm example,and I think maybe the crc is wrong as you said,thank you. Best regards, zs At 2015-01-30 00:43:12, Bastian Bloessl bloe...@ccs-labs.org wrote: Hi, On 01/29/2015 03:13 PM, zs wrote: Can you tell me,for general,in which

Re: [Discuss-gnuradio] USRP B200 host BW with USB 3.0/2.0

2015-01-29 Thread Ralph A. Schmid, dk5ras
To be honest, I have no idea :) However I did not yet test this with the B210, as now USB3 works flawless. In the beginning the BladeRF was not compatible with my USB3 setup for whatever reason, so I had to stay with USB2 for a while until those issues were sorted out both in BladeRF software

Re: [Discuss-gnuradio] OOT Python Block

2015-01-29 Thread Ludwig Stephan (CR/AEH4)
Hi Richard, I noticed the same problem with some blocks in my own OOT module. I do not know why, but if you change the lines in the GRC file to (if not already done) import import my_module.my_block_name_here/import makemy_module.my_block_name_here.my_block_name_here(…)/make (note the double