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.

AWRL6432BOOST: About the Range-Doppler Detection Matrix in examples\mmw_demo\gesture_recognition

Part Number: AWRL6432BOOST
Other Parts Discussed in Thread: AWRL6432

Hi experts,

I have questions on Range-Doppler Detection Matrix
Q1: Does this matrix look like this? detMatrix.data[numRangeBins][numDopplerBins]
Q2: How do I map row and column indices of a matrix to range/doppler indices?(Doppler may have negative values)
Q3: How to convert bins in matrix to actual range(meter) and speed(m/s)

  • HI, there:

    Which demo you are looking at for AWRL6432? Can you provide the demo location? 

    Usually: 

    Q1: Range Doppler detection matrix is a 2D matrix [numRangeBins][numDopplerBins], which is non-coherent combination from the 2D FFT output across different antennas.   

    Here is some documentation from SDK out-of-box demo.  file:///C:/ti/mmwave_sdk_03_05_00_04/packages/ti/datapath/dpc/dpu/cfarcaproc/docs/doxygen/html/index.html

    Q2: Here is some doppler FFT documentation file:///C:/ti/mmwave_sdk_03_05_00_04/packages/ti/datapath/dpc/dpu/dopplerproc/docs/doxygen/html/index.html.  

    Q3:  range =  rangeBin * rangeResolution; and velocity = DopplerBin * dopplerResolution.  (nagetive Doppler bins needs to be wrapped around), range resolution and doppler resolution can be derived from chirp parameters and the equation can be found at: www.ti.com/.../swra553a.pdf

    Best

    Zigang