This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

WL1837MOD: With Calibrator tool, MCS8 is transmitting at 72Mbps

Part Number: WL1837MOD

While testing the Tx power with LitePoint setup using the Calibrator tool for MCS8 datarate, I am seeing in the LitepOint WLAN tester the data rate as 72Mbps. Not the data rate of MCS8.

The command used with the script is as below

-sh-3.2# ./wifi_test_start.sh 6 20 0 20000

setting Channel 6, Data Rate: 20 = MCS8/MCS4 at 40Mhz, Bandwidth: 0 = 20Mhz

Calibrator:: Starting TX Simulation (delay=500, rate=20, size=500, mode=0

                                     data_type=0, BW=0, gi=1, opt1=0x0, opt2=0x2

                                  

 Can you tell me what is wrong I am doing ?

  • Hi Brad,

    MCS8 is MIMO only which means you will need to adjust the antenna configuration accordingly - more info can be found in section 3.7.

    I recommend using the following command examples:

    Let me know if that works for you.

  • we had tried below script.. when use it, only  MCS8 its transmit at different rate, MCS9-MCS15 it works fine. 

    calibrator wlan0 wl18xx_plt stop_tx
    calibrator wlan0 wl18xx_plt tune_channel 6 0 0
    calibrator wlan0 wl18xx_plt set_tx_power 20000 0 0 6 0 3 0 1 0 0 0 0
    calibrator wlan0 wl18xx_plt start_tx 500 20 500 0 0 1 0 2 ea:2e:9c:d5:35:f2 00:24:9B:6A:8B:87 0

  • Hey Dino,

    Can you try this script?

    calibrator wlan0 wl18xx_plt stop_tx
    calibrator wlan0 wl18xx_plt tune_channel 6 0 0
    calibrator wlan0 wl18xx_plt set_tx_power 20000 0 0 6 0 0 0 1 0 0 0 0
    calibrator wlan0 wl18xx_plt start_tx 500 20 500 0 0 1 0 0 ea:2e:9c:d5:35:f2 00:24:9B:6A:8B:87 0

    Let me know how that goes - in the meantime I will try to get a set up procured in case I need to try and replicate the issue.

    Edit: Also, I wanted to ask - with that last script what was the data rate you were getting?

  • With our initial script we were seeing a data rate of 72 Mbps and with the script you suggested we are also seeing the same rate of 72 Mbps

  • Hi Rishab,

    What'd the model number for your litepoint and are you doing this testing on the WL1837MODCOM8I EVM?

  • The evm is WL1837MODGIMOCR and the model number is iqxel-mw 7g

  • Hi Rishab,

    Thanks for the info, I'm going to try and locate a similar model Litepoint for testing. Can you provide me with the script used for MCS15 that worked and the data rate it was working at?

  • Here's the script,

    calibrator wlan0 wl18xx_plt stop_tx
    calibrator wlan0 wl18xx_plt tune_channel 6 0 1
    calibrator wlan0 wl18xx_plt set_tx_power 20000 0 0 6 0 0 0 1 0 0 0 0
    calibrator wlan0 wl18xx_plt start_tx 500 27 500 0 0 1 0 0 00:11:22:33:44:55 01:02:03:04:05:06 0

    This was working at the data rate of 144 Mbps

  • Hi Rishab,

    Thanks for the info. I'm going to run some tests of my own to see if I can replicate this issue. Please give me a few days to provide some results.

  • Hi Rishab,

    I wanted to check if you have the latest FW and INI files downloaded. Secondly, is it possible for you to run these tests using RTTT?

  • Hello,

    we are using in two differnet product two versiosn as below

    [ 7.686025] wlcore: PHY firmware version: Rev 8.2.0.0.240
    [ 7.799218] wlcore: firmware booted (Rev 8.9.0.0.76)

    and 

    [   66.658326] wlcore: PHY firmware version: Rev 8.2.0.0.245
    [   66.763403] wlcore: firmware booted (Rev 8.9.0.0.86)

    both behaving the same

    RTTT we need to connect using the UART right, wer do not have that in our board as of now, with the calibrator tool, is there any issue at your side also?

  • Hi Dino,

    Could you download the most up do date firmware for me - https://git.ti.com/cgit/wilink8-wlan/wl18xx_fw/log/

    I'm using RTTT for the testing which provides an intuitive GUI, but it will essentially function like calibrator tool. I just wanted to check in case I need to share a screenshot, I didn't want you to be confused by what you were looking at.

    I'm currently waiting to get updated firmware for litepoint. I had to check out a different litepoint tester to perform MIMO testing. The GUI to run the tester unfortunately requires Adobe Flash which has EOL'd for some time now which is why I need a new firmware to operate it. I should have something in the next few days so I can update you on my findings then.

    I will note that I ran some tests just using 1 ANT while configuring it into MCS 8 and I was seeing the MCS 7 data rate. This is originally what I thought you were facing, but if the higher MCS values are working then that shouldn't be the case.

  • Hi Dino,

    I was able to see similar results as you during this testing. I adjusted a few settings to see what was causing this behavior. Could you do me a favor and run the script below to see if it works on your end?

    calibrator wlan0 wl18xx_plt stop_tx
    calibrator wlan0 wl18xx_plt tune_channel 6 0 0
    calibrator wlan0 wl18xx_plt set_tx_power 20000 0 0 6 0 0 0 1 0 0 0 0
    calibrator wlan0 wl18xx_plt start_tx 500 20 500 0 0 0 0 0 ea:2e:9c:d5:35:f2 00:24:9B:6A:8B:87 0

  • hello Dylan,

     yes with the above script its working, i can see MCS8 with guard interval Long. Comparing the differnece and trying which value is making the data rate work, i found is the guard interval, when i set the quard interval to 0-long, it works

    calibrator wlan0 wl18xx_plt start_tx 500 20 500 0 0 1 0 0 ea:2e:9c:d5:35:f2 00:24:9B:6A:8B:87 0 - Not working, ie MCS7 data rate i am seeing
    calibrator wlan0 wl18xx_plt start_tx 500 20 500 0 0 0 0 2 ea:2e:9c:d5:35:f2 00:24:9B:6A:8B:87 0 - Working MCS8
    calibrator wlan0 wl18xx_plt start_tx 500 20 500 0 0 0 0 0 ea:2e:9c:d5:35:f2 00:24:9B:6A:8B:87 0 - Working MCS8

    so what is happening with the firmware when the GI is 0-Long ? how do we fix this issue ? 

  • Hey Dino,

    This is also what I was seeing on RTTT so I wanted to make sure you got the same result with Calibrator tool. I've reached out to our Software experts to see what can be causing this. Please give a few days for me to receive their feedback and I'll let you know how to address this.