• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 179 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AWRL6844: Static clutter removal does not function properly

Shige
Prodigy 60 points
Part Number: AWRL6844


Tool/software:

Hi,

I have 2 questions.

1. I enabled static clutter removal in the mmWave demo of the SDK06.00.04, but the values around 0 doppler remain high, making it appear as though stationary objects are not being removed.

    Could you please advise me on any reason, limitations and workarounds?

    The following is the configuration and the detmatrix at that time.

<Configuration>

sensorStop 0
chirpComnCfg 50 0 0 128 1 40 0
chirpTimingCfg 6 10 0 50 60
channelCfg 153 255 0
frameCfg 4 0 1000 16 500 0
adcDataDitherCfg 0
gpAdcMeasConfig 0 0
guiMonitor 1 0 0 0 0 0
cfarProcCfg 0 2 8 4 3 0 12.0 0
cfarProcCfg 1 2 4 2 2 0 12.0 0
cfarFovCfg 0 0.25 3.5
cfarFovCfg 1 -1.0 1.0
aoaProcCfg 64 64
aoaFovCfg -60 60 -60 60
clutterRemoval 1
factoryCalibCfg 1 0 38 2 0x1ff000
runtimeCalibCfg 0
antGeometryTX 3 0 2 0 1 0 0 0
antGeometryRX 0 0 0 1 0 2 0 3
antGeometryDist 2.54 2.54
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  1 0 1 0 -1 0 -1 0
adcDataSource 0 adc_test_data_0001.bin
adcLogging 0
lowPowerCfg 0
sensorStart 0 0 0 0

<detMatrix>

2. When the configuration was changed to BPM mode from the above, the detMatrix showed similar results, but the CFAR output did not detect any peaks.

    I would like to know the reason why no peaks were detected in BPM mode.

<detMatrix>

<CFAR output>

Thank you for your support.

Best regards,

Shige

  • 0
    TI__Mastermind 40825 points

    HI, Shige:

    To verify whether the clutter removal works, I would suggest you to:

    1) Setup this experiments with clutter removal in a clean environment, like anechoic chamber, without any moving object, and check whether result (detMatrix) makes sense.

    2) Check the results without clutter removal enable and see whether you see a big difference in detMatrix?  

    It will be great if you can post both results,

    Best,

    Zigang

  • 0 in reply to zigang Yang
    Prodigy 60 points

    Hi, Zigang

    I sincerely apologize for the delay.

    I measured both of them in aanechoic chamber without any moving object.

    I think the values around 0 doppler remain high, making it appear as though stationary objects are not being removed.

    I would like to know the causes of the above 1 and 2.

    Enable static clutter removal

    Disable static clutter removal

    Thank you for your support.

    Best regards,

    Shige

  • 0 in reply to Shige
    TI__Mastermind 40825 points

    Hi, Shige:

    Your chirp configuration below does not look very good to me.  

    chirpComnCfg 50 0 0 128 1 40 0
    chirpTimingCfg 6 10 0 50 60
    frameCfg 4 0 1000 16 500 0

    If you check the tuning guide in SDK mmWave_Demo_Tuning_Guide.pdf.   You can see the following guidance on what is the minimum skip samples.  When the number of samples is not correct, you will see big variations between chirps.

    In addition, we usually suggest the hpf setting to be at least 1 to avoid ADC clipping.  

    I would suggest you check the ADC samples to make sure the ADC samples looks good.  If you have a DCA1000 board, you can apply this chirp configuration in mmWave studio and check the ADC samples. 

    Best,

    Zigang