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.
Tool/software:
Please help to inform us the following setting of cfarCfg about the applied noise window and cfar rule as the range index at 1~11 or 116~127 at this CFAR-CASO case?
chirpComnCfg 8 0 0 256 0 23 0
chirpTimingCfg 38 20 1 12 61.1
cfarCfg 2 8 4 3 0 8 0 0.95 0 1 1 1
For the cfarCfg set the guard as 4 and window as 8, index 1~11 & 116~127 cannot have fully windows data for their one side window are out of the index of 0~127
HI, there:
Please check the TRM document section 10.2.2.3.
https://www.ti.com/lit/pdf/swru599
Best,
Zigang
Sir, Thanks.
2 further questions need your further help if we apply the following setting at cfg file
cfarCfg 2 8 4 3 0 10 0 0.95 0 1 1 1
1. How about the used left/right window size? Is it 8 for both side?
2. For this non-cyclic setting, if the index 1~11 & 116~127 will have the same window value for all the cases of CFAR-CA, CFAR-CAGO, CFAR-CASO for the other side will not have data will be used?
Hi, Ann:
You can find all the parameter definition in SDL L users guide (search for cfarCfg)
file:///C:/ti/MMWAVE_L_SDK_05_04_00_01/docs/api_guide_xwrL64xx/MOTION_AND_PRESENCE_DETECTION_DEMO.html#autotoc_md777
1) Yes, it is win size is 8 on both size (always the same on both sides)
2) For non-cyclic setting, for index 0-11, the left noise will be ignored, and right noise will be used.
for index 116~127, the right noise will be ignored, and only the left noise will be used.
Best,
Zigang
Sir,
Thanks. For previous item.2 question, does it mean CFAR-CA, CFAR-CAGO, CFAR-CASO will have the same noise average value for only one side data is used, right?
HI, Ann:
That is correct. When only one side noise is available, there is no difference between CFAR-CA, CFAR-CAGO, CFAR-CASO.
Best,
Zigang