Thanks George for your inputs.

I have closely been monitoring cgran website. However, every project seems
to be focusing on how well one can use USRP1 or USRP2 as 80211b receiver.
But my goal is to communicate between two USRPs (whether USRP1s or USRP2s)
using bbn 80211b code.

>From the previous discussions on this forum, it seems that quite a few
people were able to communicate and decode packets correctly using two
USRP2s and usrp2_version bbn 80211b code. I am trying to know whether the
usrp2_version code needs any modification or specific command line
arguments.
 

gnychis wrote:
> 
> On Thu, May 20, 2010 at 9:29 PM, Smith L. <kushal.23...@gmail.com> wrote:
> 
>>
>> Hi Colby,
>>
>> Were you able to communicate between two USRP2s using bbn 80211
>> usrp2_version code?
>>
>> I am not able to receive packets using USRP2 receiver even when other
>> USRP2
>> is transmitting. Can you please let me know if there are any changes
>> required to be made in the usrp2_version code or any specific command
>> line
>> parameters to make this work (i.e. to receive 80211b packets with USRP2
>> with
>> another USRP2 transmitting).
>>
>> Currently, I can only receive beacons from nearby access points using
>> USRP2.
>>
>>
> Not an answer to your questions... but another project to suggest:
> https://www.cgran.org/wiki/SPAN80211b
> 
> They had pretty good luck at receiving 802.11b transmissions on USRP1 by
> putting the despreading in the FPGA.  No transmit code though from what I
> remember.
> 
> - George
> 
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 
> 

-- 
View this message in context: 
http://old.nabble.com/BBN-80211b-Transmitter-with-GNURadio-3.2.2-and-USRP1-tp28623863p28629240.html
Sent from the GnuRadio mailing list archive at Nabble.com.


_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to