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

IWR6843ISK: Problem with 3D detection

Mathieu Delaveau
Intellectual 290 points
Part Number: IWR6843ISK

Hi,

I am using IWR6843ISK with sdk_03_02_00_04.

I'm trying to detect an electric pole with the mmWave Demo Visualizer.

My .cfg file :

sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 7 0
adcCfg 2 1
adcbufCfg -1 0 1 1 1
profileCfg 0 61.7 7 6.4 31.4 0 0 14 1 72 3000 0 0 30
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 4
chirpCfg 2 2 0 0 0 0 0 2
frameCfg 0 2 72 0 40 1 0
lowPower 0 0
guiMonitor -1 1 1 1 0 0 1
cfarCfg -1 0 2 8 4 3 0 3 0
cfarCfg -1 1 0 4 2 3 1 15 1
multiObjBeamForming -1 1 0.5
clutterRemoval -1 0
calibDcRangeSig -1 0 -5 8 256
extendedMaxVelocity -1 0
bpmCfg -1 0 0 0
lvdsStreamCfg -1 0 0 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.5 0.2
CQRxSatMonitor 0 3 4 63 0
CQSigImgMonitor 0 127 4
analogMonitor 0 0
aoaFovCfg -1 -90 90 -40 40
cfarFovCfg -1 0 0 10
cfarFovCfg -1 1 -12.5 12.5
sensorStart

The pole is well detected but as you can see the detected points do not represent the pole (no points in elevation)

How can I improve that ?

Thank you,

Mathieu

  • 0
    TI__Prodigy 560 points

    Hi Mathieu,

    The "aoaFovCfg" command limits the elevation and azimuth field of views. It filters out points that fall outside the specified range in the azimuth or elevation plane. It is possible that the points of the pole that you are trying to detect fall outside of your elevation angle range. You could try to increase the minimum and maximum elevation angles (up to -90 and 90).

    Similarly, the "cfarFovCfg" command filters out detected points outside the specified limits in the range direction. Your command limits the range to between 2m and 8m. Depending on your setup and the distance of the sensor from the pole, you could try increasing the maximum limit to be larger than 8m.

    You can refer to the SDK User Guide for more information about the configuration commands.

    Good luck,

    Allison