README: 802.11b sample for Sora SDK RRS feed

  • General discussion

  • The source code of 11b sample is installed to %SORA_ROOT%\src

    Subdirectory Description
    bb      802.11b base band modulation and demodulation (for both user mode and kernel mode)
    driver  NDIS 5.x miniport driver built upon simplified LL, MAC, PHY.
    inc     common include files used by 802.11b sample
    util    some utility libraries used by 802.11b sample

    To build the sample, use the C:\SoraSDK\build\ChkBldEnv.cmd or FreBldEnv.cmd.
    Make sure you have Windows Driver Kit installed. It must be noted that the built
    driver is only for windows XP.

    To run the sample, you need to setup a 802.11b peer of standard wireless card,
    and a Sora peer. Or two Sora peers (Please follow Sora 802.11b Sample Peer Setup).

    Standard peer setup
    You will need a commercial 802.11b card and configure it in ad hoc mode.
    Atheros card and Madwifi in Linux are suggested. Please set the BSSID to “sdr” if you do not want to modify Sora 802.11b sample.
    Also please set static IP address and subnet mask so that the commercial card and Sora are working in the same subnet.

    Sora 802.11b Sample Peer Setup
    After you successfully build the sample, you will get SDRMiniport.sys binary file and
    dot11config.exe configuration tool (at C:\SoraSDK\target\ke). User can install the driver
    with INF file sdr.inf (at C:\SoraSDK\src\driver\SDRMiniport\sys) by
     starting add hardware wizard in control panel. The driver acts as an Ethernet interface
     to avoid the complexity of implementing a real 802.11 miniport driver. So actually
     Ethernet frame is transformed into 802.11 frame before transmitted or 802.11 frame
     to Ethernet frame before indicated up to upper layer.
    After you install Sora Deployment Environment at deployment box (with Windows XP (32) installed),
    perform following steps to run 802.11b sample.
    a)  If HWTest driver is installed, disable it first in device manager.
    b) Add a device through add device wizard with sdr.inf and SDRMiniport.sys . If you
    have other Sora peer, to avoid MAC address conflict, modify NetworkAddress  registry
    value of [SDRMiniport.Reg] section in sdr.inf to  an unique address. 
    If you started adhoc network with other name, instead of "sdr", make sure you change BSSID registry
    value in sdr.inf accordingly.
    c) Configure the interface with IP and subnet mask.
    d) Adjust RX gain through dot11config --rxgain GainValue.  Default setting works for situation
    that distance of two peers is approximately 0.5m.
    e) Adjust data transmission rate by dot11config --datarate;
    f) Run network application to test the interface link;

    When you are trying to set up the link, you are suggested to try the following steps:
    (1) Let the commercial card broadcast in subnet (for example, iperf -c -i 1 -t 1000 -u 11M) and Sora receive. Tune rxpa and rxgain, move antenna, change data rate, until Sora can receive the broadcast packets with low loss rate. Then try the highest data rate.
    (2) Reverse the direction, i.e. let Sora broadcast and commercial card receive.
    (3) Try unicast on both directions.
    (4) Try TCP on both directions.

    Tuesday, July 13, 2010 7:23 AM

All replies

  • hello,Qiufeng:

    would you like to suggest any network application to test the interface link ?

    Also, after we set the commercial card broadcasting in subnet, we have no way to make sora card detect the packet from commercial card. The commercial card we are using is intel pro/wireless 3945ABG, could that be a problem?



    Thursday, July 22, 2010 7:13 PM
  • Dear Adam,

    You can use iperf for your test.

    Please make sure your channel setting is correct. The default channel is 3 in the 802.11b sample and you can change the channel with the dot11config tool.

    Also, you may need to tune the RX gains and move the antenna.



    Monday, August 2, 2010 1:27 PM