AWR1843: Detections have range bin spreading

Frank L1

Part Number: AWR1843

Hi Team,

I have a question about the AWR1843. We notice that the the range bins of the detections will spread when we turn off the peak grouping. Can you please explain this phenomenon? What has possibly caused this range bin spreading issue?

Thanks,

Frank

over 4 years ago

0 Cesar over 4 years ago

TI__Guru*** 140514 points

Hi,

What sw are you using?

thank you

Cesar

0 Frank L1 over 4 years ago in reply to Cesar

Intellectual 610 points

Hi Cesar,

We use our own visualizer to check the detections.

Thanks,

Frank

0 Cesar over 4 years ago in reply to Frank L1

TI__Guru*** 140514 points

What about the code that runs on the EVM?

thank you

Cesar

0 Cesar over 4 years ago in reply to Cesar

TI__Guru*** 140514 points

Sorry

TI Thinks Resolved was checked by mistake

Cesar

0 Frank L1 over 4 years ago in reply to Cesar

Intellectual 610 points

Hi Cesar,

This will happen when the peak grouping is off.

Thanks,

Frank

0 Cesar over 4 years ago in reply to Frank L1

TI__Guru*** 140514 points

Are you using the mmWave SDK demo or another demo?

thank you

Cesar

0 Frank L1 over 4 years ago in reply to Cesar

Intellectual 610 points

Hi Cesar,

We are using mmwave SDK demo on TI AWR1843 Evm. Below are the heatmap results from mmWave Demo visualizer.

1. Without peak grouping

2. Range peak grouping is on

3. Range and Doppler peak grouping are both on.

Our configuration is

sensorStop

flushCfg

dfeDataOutputMode 1

channelCfg 15 5 0

adcCfg 2 1

adcbufCfg -1 0 1 1 1

lowPower 0 0

profileCfg 0 77 7 3 39 0 0 30 1 256 7200 0 0 30

chirpCfg 0 0 0 0 0 0 0 1

chirpCfg 1 1 0 0 0 0 0 4

frameCfg 0 1 32 0 100 1 0

guiMonitor -1 1 1 1 0 0 1

cfarCfg -1 0 2 8 4 3 0 1200 0

cfarCfg -1 1 0 4 2 3 1 1200 0

multiObjBeamForming -1 1 0.5

calibDcRangeSig -1 0 -5 8 256

clutterRemoval -1 0

compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0

measureRangeBiasAndRxChanPhase 0 1. 0.2

aoaFovCfg -1 -90 90 -90 90

cfarFovCfg -1 0 0.25 8.64

cfarFovCfg -1 1 -10.59 10.59

sensorStart

Thanks,

Frank

0 Cesar over 4 years ago in reply to Frank L1

TI__Guru*** 140514 points

Hi,

Thank you for the clarifications.

I think it will be helpful to review the peak grouping example provided in the SDK documentation

I have found the best documentation in SDK 2.1

If you don't have it installed, you may install it from the SDK download page. (there is a link for older releases at the bottom of the page)

I have attached a snapshot of the documentation in case you don't want to install the SDK

thank you

CesarPeakGrouping.pdf

0 Frank L1 over 4 years ago in reply to Cesar

Intellectual 610 points

Hi Cesar,

Actually, we use approach 2 for peak grouping. But independent of peak grouping we notice that when we disable PG, pedestrian detection range spread is 3 meters for 400 MHz bandwidth. Is that expected?

Thanks,

Frank

0 Cesar over 4 years ago

TI__Guru*** 140514 points

How many range bins is 3m?

Thank you

Cesar

0 Frank L1 over 4 years ago in reply to Cesar

Intellectual 610 points

7 range bins.

0 Frank L1 over 4 years ago in reply to Cesar

Intellectual 610 points

Hi Cesar,

Any update?

Thanks,

Frank

0 Cesar over 3 years ago in reply to Frank L1

TI__Guru*** 140514 points

Hi,

Sorry for the delay

I have discussed this question with the developer of the demo and here is some feedback:

It looks CFAR CASO option is being used in range direction, Noise window is 8, and guard length is 4. So the point in the valley in figure below (denoted as CUT) could also be detected, if the average of the noise samples on the left, since it is less than the right side, (plus threshold) is below CUT. And it looks CFAR threshold is 0 dB, so CFAR is just comparing CUT against average noise samples. So you can disable CASO and increase noise threshold and the spread may be less and two peaks may be separated.

Does this answer your question?

thank you

Cesar

Sensors

Sensors forum

AWR1843: Detections have range bin spreading