Closed ghost closed 9 years ago
can you load the module in an interactive python session please.
python
import ieee802_11
This should give you more debug output than running the flow graph in grc.
Output below - the second is using the Macports python.
$> python
Python 2.7.6 (default, Sep 9 2014, 15:04:36)
[GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.39)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import ieee802_11
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: No module named ieee802_11
>>> ^D
$> /opt/local/bin/python2.7
Python 2.7.9 (default, Dec 13 2014, 15:13:49)
[GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.56)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import ieee802_11
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: No module named ieee802_11
you have to add the install directory of the module to your python path. Use something like export PYTHONPATH=/opt/local/lib/python2.7/site-packages
Ah fantastic! Thank you so much! That solved it :)
$> export PYTHONPATH=/opt/local/lib/python2.7/site-packages
$> gnuradio-companion
Executing: "/home/sharathbabu/gr-ieee802-11/examples/wifi_rx.py"
linux; GNU C++ version 4.8.2; Boost_105400; UHD_003.008.000-6-gbde8e9a3
Traceback (most recent call last):
File "/home/sharathbabu/gr-ieee802-11/examples/wifi_rx.py", line 32, in
what is the solution for this?
adapt your PYTHONPATH. Python can't find the module.
Warning: This flow graph may not have flow control: no audio or RF hardware blocks found. Add a Misc->Throttle block to your flow graph to avoid CPU congestion.
Executing: "/home/sharathbabu/gr-ieee802-11/examples/wifi_loopback.py"
linux; GNU C++ version 4.8.2; Boost_105400; UHD_003.008.000-6-gbde8e9a3
Using Volk machine: sse3_64 OFDM MAPPER: encoding: 0 set_min_output_buffer on block 31 to 96000 set_min_output_buffer on block 33 to 96000 set_min_output_buffer on block 35 to 96000 set_min_output_buffer on block 36 to 96000 set_min_output_buffer on block 39 to 96000 set_min_output_buffer on block 50 to 96000
how can i eliminate the warning? i didn't see the 'Hello World' packets in console...
Executing: "/home/sharathbabu/gr-ieee802-11/examples/wifi_loopback.py"
linux; GNU C++ version 4.8.2; Boost_105400; UHD_003.008.000-6-gbde8e9a3
Using Volk machine: sse3_64 OFDM MAPPER: encoding: 0 set_min_output_buffer on block 31 to 96000 set_min_output_buffer on block 33 to 96000 set_min_output_buffer on block 35 to 96000 set_min_output_buffer on block 36 to 96000 set_min_output_buffer on block 39 to 96000 set_min_output_buffer on block 50 to 96000 gr::vmcircbuf_sysv_shm: shmget (1): Invalid argument gr::vmcircbuf_sysv_shm: shmget (1): Invalid argument gr::vmcircbuf_sysv_shm: shmget (1): Invalid argument gr::buffer::allocate_buffer: failed to allocate buffer of size 48000 KB gr::vmcircbuf_sysv_shm: shmget (1): Invalid argument gr::vmcircbuf_sysv_shm: shmget (1): Invalid argument gr::vmcircbuf_sysv_shm: shmget (1): Invalid argument gr::buffer::allocate_buffer: failed to allocate buffer of size 48000 KB terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc
what is bad_alloc ? please help me in rectifying this.
you can ignore the warning. Concerning the error, did you do this
https://github.com/bastibl/gr-ieee802-11#adjust-maximum-shared-memory
yeah i did... But what is the purpose of wifi loopback in this code? Please reply me with suitable answer or any related video.
i had used pc with ubuntu 14.04 and usrp n210 with an antenna and GB ethernet cable. That's all required or any required hardware is necessary?..
If so i am not getting the wireshark window ater executing wifi_transceiver.grc.
Kindly reply me with the reason.
The loopback flow graph is for loopback testing, without hardware. You will know that everything is installed correctly and that the basic things are working before sending anything over the air. Over the air is generally much harder and there are several pitfalls. So it might make sense to test things locally as a start. Apart from that can the flow graph easily be adapted for doing simulations and studying the performance of the system.
If you use the Wireshark Connector block you have to start Wireshark separately and read from the pipe you create in the flow graph (note file sink is in mode append). Look here to see how to start WIreshark
https://github.com/bastibl/gr-ieee802-11/blob/master/apps/rx_demo.sh#L43
Your hardware is fine, but first you will have to get the loopback flow graph working.
hello , when i execute the wifi_transceiver.grc file in gnuradio v3.7 . As i should get the output as the loopback, but i am getting the blank output in the graph. And continuosly getting DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD......... infinite times. PFA
Can you suggest me how to get the output.... in the above case
...looks like your PC is too slow to process the incoming samples.
http://files.ettus.com/manual/page_general.html#general_ounotes
ok thanks for your reply. Could you suggest me any modification to be done in the code to overcome these overflows....?
I guess the highest optimization potential has sync long and short
Please, can you help me about wifi:loopback.grc? when i run, the output is: OFDM MAPPER: encoding: 0 set_min_output_buffer on block 31 to 96000 set_min_output_buffer on block 33 to 96000 set_min_output_buffer on block 35 to 96000 set_min_output_buffer on block 36 to 96000 set_min_output_buffer on block 39 to 96000 set_min_output_buffer on block 50 to 96000
I tried the instruction: sudo sysctl -w kernel.shmmax=2147483648
but nothing changes
Now my output is
Showing: "/home/aler/gnuradio/gr-ieee802-11/examples/wifi_loopback.grc"
Generating: "/home/aler/gnuradio/gr-ieee802-11/examples/wifi_loopback.py"
Warning: This flow graph may not have flow control: no audio or RF hardware blocks found. Add a Misc->Throttle block to your flow graph to avoid CPU congestion.
Executing: "/home/aler/gnuradio/gr-ieee802-11/examples/wifi_loopback.py"
linux; GNU C++ version 4.6.3; Boost_104800; UHD_003.009.git-217-g012381d9
Using Volk machine: ssse3_32_orc OFDM MAPPER: encoding: 0 set_min_output_buffer on block 31 to 96000 set_min_output_buffer on block 33 to 96000 set_min_output_buffer on block 35 to 96000 set_min_output_buffer on block 36 to 96000 set_min_output_buffer on block 39 to 96000 set_min_output_buffer on block 51 to 96000 thread[thread-per-block[13]: <block ofdm_mac (49)>]: pmt_cdr: wrong_type : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
but i don't see the scope diagram....can you help me please?
the first output you posted is not an error but information.
If you don't see the scope, it's most likely because you installed GNU Radio without WX GUI.
I have gr-wxgui. How is it possible?
I don't know.... what exactly do you mean with "I don't see the scope diagram". The block is not there in GRC, the constellation does not appear, etc.
i am getting the blank output in the graph....why?
....because no frame was detected and, thus, no constellations of carriers are shown
[OS X Yosemite 10.10.1, GNURadio v3.7.5.2] From a fresh Macports (/opt/local/ path) installation I follow the instructions and try to open the wifi_phy_heir example.
It fails to run as the header_formatter variable value, ieee802_11.wifi_signal_field(), raises an error:
Param - Value(value): Value "ieee802_11.wifi_signal_field()" cannot be evaluated: name 'ieee802_11' is not defined
There is a mini-discussion of a workaround here: https://www.ruby-forum.com/topic/4487026 However, it did not fix my problem. I implemented their fix as the following script (note it also fixes a bug for finding the log4cpp library):
Anyone know/have a possible fix?