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.

IWRL1432BOOST: different calculated vel Resolution between sensing estimator and sdk calculation

Part Number: IWRL1432BOOST
Other Parts Discussed in Thread: IWRL6432


I noticed that  if I want a vel res with 64 chirps in BPM mode, I need to configure the numOfChirpsInBurst to 128, which has explained in ' Parameter Tuning and Customization Guide for the IWRL6432 Motion/Presence Detection Demo.pdf ', page 40

Here is my wave confuration, respectively in mmWave sensing estimator and sdk

mmWave sensing estimator:

chirpComnCfg 8 0 0 256 4 30 0
chirpTimingCfg 6 0 0 15 76
channelCfg 7 3 0
frameCfg 128 0 4800 1 100 0 

ccs sdk:

When debugging the sdk, the calculated doppler step is 0.43. 

When using the sensing estimator, the vel resolution is 0.214

I'm not sure where I made a mistake, is the problem that sdk doesn't consider the fftshift, both positive and negative vel?

Which vel res should I use?