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.

AWR1443BOOST: cfar threshold scale

Part Number: AWR1443BOOST
Other Parts Discussed in Thread: AWR1443

Hello Sir,

 We are collecting radar raw data with AWR1443 boost and sending data over uart  to PC. In the application we are performing 1D FFT, 2FFT ,CFAR and extracting raw data using range index and doppler index using cfarobjptr.  In the cfar configuration command the threshold scale is set to 1200. So could you please help us to solve following queries:-

1) How the cfar works with the threshold scale?

2) Is there any chances of identifying a CUT as detected object if the peak value of CUT is below the threshold scale set in cfar configuration command?

3) How is the comparison of threshold and peak value of CUT is done?

Thanks and regards

KK

  • Hi,

    I recommend you search on the web regarding general information about the CFAR algorithm.

    Usually the CFAR threshold is provided in dB. The CFAR is usually applied to an energy heatmap. If a peak in this heatmap has higher value than the threshold, than it is detected.

    Thank you

    Cesar

  • If you are not trying to do a sort of bit exact simulation of the HWA based OOB demo processing chain in the PC, then you should ignore the cli format and decide what makes sense for your processing chain, you know what you are implementing so you will know how best to express the threshold scale. If you are trying to emulate or understand what the threshold scale means for the OOB implementation, refer to the SDK [assuming you are using 2.x because of 1443] UG cli documentation which documents the command (that will answer your Q1 and Q3) and has a formula to convert from the desired threshold in dB to what the cli expects [for the implementation]. To understand why the formula that that expresses the Tcli in terms of desired TdB is what it is, see the documentation of the 1443 demo by locating it in the module documentation html in the docs/ directory in your SDK installation. FYI in 3.x release (you can read its UG), we directly allow TdB [as float in a Q format] configuration in the cli so user does not need to translate unlike the 2.x release, but 3.x releases do not support 1443.