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.

IWR6843AOPEVM: Improving resolution

Part Number: IWR6843AOPEVM
Other Parts Discussed in Thread: IWR6843AOP

Hi Team,

Are there possible ways to improve the radar velocity resolution of the IWR6843AOPEVM? If there is, can you share with us these possible procedures/guidelines?

Thanks in advance!


Kind Regards,

Jejomar

  • HI, Jejomar:

    Please find related e2e thread on this topic:

     

    Best,

    Zigang

  • Hello Zigang,

    Many thanks for looking into this. Our customer uses the IWR6843AOP, with the area scanner. When they process the radar output, the doppler values resolution is quite bad (no more than 4/5 values).
    We find the cfg file and the specific commands and numbers that I need to change. But their question is, how can they calculate the idle time/loop per frame limit? Is there any formula for this?


    Kind Regards,

    Jejomar

  • HI, Jejomar:

    The number of loop per frame is limited by two things:

    1) Radar Cube Memory:  numRangeFFT * numLoop * numTXAnt * numRXAnt * 4 (in Byte) needs to less than 768KByte.   

    2) There is no limit to the idle time, but the total intraFrameTime = (idleTime + rampTime) * numTxAnt * numLoop needs to be less than the desired frame duration.  You also want to leave some time (for example 30ms) for inter frame post processing time.  Note that Frame Duration =  intraFrameTime + interFrameProcessingTime

    Note that when you increase the idle time, you maximum non-ambiguity velocity is also reduced.  

    Best,

    Zigang