• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 365 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AWRL6432AOPEVM: xWRL6432: calibration using 'measureRangeBiasAndRxChanPhase'

sey k
Prodigy 20 points

Part Number: AWRL6432AOPEVM

Tool/software:

I am developing a product using xWRL6432AOPEVM. There is an angle offset at the output position, so I need help in proceeding with receiving channel calibration.
The development environment analyzes the output results after entering the CLI in order in the matlab using uart in the EVM.
The following contents were carried out in accordance with the steps of the measurement procedure.
The example code used in the measurement is 'high performance presence...' and has been modified from this code to the following.
Set 'measureRangeBiasAndRxChanPhase' to '12.500.1' TCR was positioned 2.5 m.
Set 'ChirpTxMimoPatSel' to '1' for TDM MIMO change.
When changing the environment and settings as above, no output comes out after the change. Request a guide for calibration of the receiving channel.

Applying the equation in the SDK document 'Measure Procedure Implementation' to the received channel data captured using DCA1000 resulted in correction, but the target was divided into two.

  • 0
    TI__Intellectual 2860 points

    Hi Sey,
         Thanks for reaching out us in e2e. Are you able to look at  "Motion_Presence_Detection_Demo_Tuning_Guide" present in docs folder of latest SDK (MMWAVE_L_SDK_05_05_00_02)?

    Thanks and Regards,
    Sivaprasad

  • 0 in reply to Sivaprasad K L
    Prodigy 20 points

    Hi Sivaprasad

    Calibration was conducted using the newly distributed SDK. Unfortunately, however, the value of calibration is unstable.

    By activating "measureRangeBiasAndRxChanPhase", the following procedure is performed by receiving a value of 100 frames, and there is a large deviation between the values, and if the target is detected using it, a lot of angle errors occur.

    1. 100 frame 'RangeBiasAndRxChanPhase' measurement
    2. sort for value
    3. 25th and 75th rank data comparison
    4. Intermittent deviations show stable results with less than 0.05 deviations, but most of them show deviations of more than 1 and output unstable results

    Can you please review it or let me know what you can do about it?

    Thanks and Regards,

  • 0 in reply to sey k
    TI__Intellectual 2860 points

    Hi Sey,
        I have looped in our expert. Please allow us a day or so to provide the response.

    Thanks and Regards,
    Sivaprasad

  • 0 in reply to sey k
    TI__Mastermind 40515 points

    Hi, Sey:

    Based on SDK L Users guide, file:///C:/ti/MMWAVE_L_SDK_05_04_00_01/docs/api_guide_xwrL64xx/MOTION_AND_PRESENCE_DETECTION_DEMO.html#autotoc_md761

    Is your command look like?

    measureRangeBiasAndRxChanPhase  1  2.5 0.5

    1) Make sure the corner reflector is placed at bore sight and is big enough compare to the distance to provide enough SNR. 

    2) The setup is relatively clean. 

    3) Make sure your high pass filter setting is high enough to avoid ADC clipping, because AOP board is shown a much higher TX coupling level than the EVM board.  We recommend to use radar sensing estimator to make sure your settings are good for AOP board. 

    Please let me know if you still see bigger variation after all these checks.

    Best,

    Zigang