• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 621 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.

AWR1843: Why block points cloud when range less than 0.25m in SDK demo

Wesley He
Expert 6205 points
Part Number: AWR1843

Hi team,

I saw here's a range limited in SDK3.1.1.2 1843 OOB demo. Why adding a 0.25m limited in the default setting?

I always get some noise point under 0.25m if I remove this limitation. 

Could you please clarify why you did this limitation? Is it because the software bugs or it's a required option?

Thanks.

The below configuration is from "C:\ti\mmwave_sdk_03_01_01_02\packages\ti\demo\xwr18xx\mmw\profiles\profile_2d.cfg"

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 100 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

Regards,

Wesley

  • 0
    TI__Mastermind 22155 points
    Wesley,

    Will check this and get back to ASAP.

    -Raghu
  • 0
    TI__Mastermind 21025 points

    Hi Wesley,

    As noted in the SDK user guide for the "calibDcRangeSig" CLI command:

    Antenna coupling signature dominates the range bins close to the radar. These are the bins in the range FFT output located around DC...

    Because of this energy, the demo provides a few ways to compensate for it.  The calibDcRangeSig CLI command is one method.  If the extreme near-range FFT bins are not required, it is more efficient to simply ignore them. Which is what the cfarFovCfg CLI command does. So if you want to detect less than 0.25, you'll need to enable calibDcRangeSig and change cfarFovCfg.

      -dave