Re: [Discuss-gnuradio] USRP tx_time tags and late packets

2017-05-09 Thread U L
I'm surprised no one responded to this. My group has had some experience with this. We found latency can be extremely large for packetized transmits, especially if the packets are small. Without modification, there is a minimum buffer size GNURadio sets regardless of the buffer size settings in

Re: [Discuss-gnuradio] ImportError: No module named _osmosdr_swig

2017-05-09 Thread Cinaed Simson
On 05/09/2017 12:23 AM, Fernando wrote: > > > > On 09/05/17 07:02, Cinaed Simson wrote: >> On 05/08/2017 03:44 PM, Fernando wrote: >>> My GRC crashes when I place a osmocom source and osmocon sink. >>> >>> Doing some research I have found that is a python problem with _osmosdr_swig >>> >>>

Re: [Discuss-gnuradio] The low performance of gr-ieee-802.11 running on b210 ????

2017-05-09 Thread Marcus Müller
Hi Siyu, well, transceiver performance depends effectively on bit error rate of the underlying transport – and that error rate might be limited by noise, by interference, or by effects like clipping and saturation, overly large clock offset and much more. I'd say: add a time and a frequency sink

[Discuss-gnuradio] The low performance of gr-ieee-802.11 running on b210 ????

2017-05-09 Thread zhan siyu
Hi all, Recently, I bought two b210 usrps. And I just successfully setup the usrps to run the gr-ieee802.11, written by Bastian. I used 2 desktops connected to usrp and run the transceiver.py program. I can ping from one to the other. I 'm so excited as I finally made it. However, I used the

[Discuss-gnuradio] DARPA Hackfest roadshow announcement

2017-05-09 Thread Tom Rondeau
Hey everyone. On my flight into Denver last night, I realized that I hadn't gotten the word out here on my current tour. DARPA is holding a large Hackfest in November this year at NASA Ames, and there's a number of aspects to it. One includes a teaming "hackathon" event, and for that, we're

Re: [Discuss-gnuradio] ImportError: No module named _osmosdr_swig

2017-05-09 Thread Michael Dickens
Hi Fernando - I've seen this issue on some older Mac OS X installs (e.g., 10.7 or 10.8 from 2011/2012). I have yet to figure out what's going on, and it works for MacOS X 10.9 and newer 100% as far as I can tell so I'm not concentrating efforts on the older no-longer- supported OSs. Your Opensuse

Re: [Discuss-gnuradio] gr_ieee-80211 receiver

2017-05-09 Thread Bastian Bloessl
> On 9. May 2017, at 08:26, LiLi wrote: > > If we want to capture frames from a route, we should change the codes. > The codes on github can capture frames which generate by the wifi_tx codes > bacause the value of FCS is constant. After we change the value OF FCS to be

Re: [Discuss-gnuradio] OOT Module using external function

2017-05-09 Thread Ali
Hi to all, I found the below conversation. As Nathan said and explained in the link, we should write the names of .cpp files inside the CMakesList.txt file and then apply make, make install things later. It seems that we do not need to link .obj files, .cpp files are enough.

Re: [Discuss-gnuradio] ImportError: No module named _osmosdr_swig

2017-05-09 Thread Fernando
On 09/05/17 07:02, Cinaed Simson wrote: > On 05/08/2017 03:44 PM, Fernando wrote: >> My GRC crashes when I place a osmocom source and osmocon sink. >> >> Doing some research I have found that is a python problem with _osmosdr_swig >> >> fernando@andromeda:~> python -c 'import osmosdr' Traceback