• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 831 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

IWR1642: Unable to detect object inside a cardboard box

Vikas Dubey
Intellectual 390 points
Part Number: IWR1642
Other Parts Discussed in Thread: DCA1000EVM, MMWAVE-STUDIO

Hi,

We are trying to detect static objects inside a cardboard box. Dimensions of cardboard box are 0.5mx0.5x0.5m.
1642 EVM is placed on top of the cardboard box(antenna is facing downwards inside cardboard box).

1. When object is placed in the line of sight of antenna the object is detected
2. When object is slightly moved away from LOS it is not detected by EVM.
3. We are using binary which is provided with sdk 2.0.0.4


We have following queries regarding this

a) We are getting some extra points on scatter plot we think these are reflections from side walls. Is there any solution to get rid of these extra points? For example do we need to have coating of non reflective material in order to detect objects accurately.
b) How can we cover entire box volume inside FOV?


Regards
Vikas

  • 0
    TI__Mastermind 25825 points
    Hello,

    Have you explored "Static clutter removal" option in the SDK?
    You may have to disable this option to see static objects. Please refer to below E2E thread.
    e2e.ti.com/.../641579

    You may also consider, increase the number of chirps per frame, which increases the SNR of the detection..
    There is a upper bound for the memory in the silicon i.e. 768kB of L3 RAM. For the Chirp configuration you may want to look at the below E2E thread.
    e2e.ti.com/.../2363042

    It also depends upon RCS of the object inside the box, if object is very weak w.r.t to clutter then it would be difficult to distinguish from other strong reflecting elements.

    You may want to look at the sensing estimator from the link below to identify SNR needed for the detection threshold.
    dev.ti.com/.../


    You are right, there could be multi-path, If you are sure based on the distance of the cardboard w.r.t Radar then you could gate the range . However with-in range gates multi-paths are difficult to suppress. If absolutely necessary you may have to use mmWave absorbed material, fitted inside the box which absorbs the mmWave signals, But this would be expensive proposition.

    Thanks and regards,
    CHETHAN KUMAR Y.B.
  • 0 in reply to CHETHAN KUMAR Y.B.
    Intellectual 390 points

    Hi Chetan,

    I used mmwave estimator tool to generate my chirp configuration, the screenshot for the same is pasted below

    Based upon above configuration I modified my .cfg file contents of which is shown below

    sensorStop
    flushCfg
    dfeDataOutputMode 1
    channelCfg 15 3 0
    adcCfg 2 1
    adcbufCfg -1 0 0 1 0
    profileCfg 0 77 339.79 7 57.14 0 0 7038 1 256 3000 0 0 30
    chirpCfg 0 0 0 0 0 7 6.4 1
    chirpCfg 1 1 0 0 0 7 6.4 2
    frameCfg 0 1 32 0 100 1 0
    lowPower 0 0
    guiMonitor -1 1 1 0 1 0 0
    cfarCfg -1 0 0 8 4 4 0 3414
    cfarCfg -1 1 0 4 2 3 0 3414
    peakGrouping -1 1 1 1 1 255
    multiObjBeamForming -1 1 0.5
    clutterRemoval -1 0
    calibDcRangeSig -1 0 -5 8 256
    extendedMaxVelocity -1 0
    bpmCfg -1 0 0 1
    lvdsStreamCfg -1 0 0 0
    nearFieldCfg -1 0 0 0
    compRangeBiasAndRxChanPhase 0.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 5 123 0
    CQSigImgMonitor 0 127 4
    analogMonitor 1 1
    sensorStart

    However these settings are not being configured in the device and I am getting following error

    mmwDemo:/>sensorStart
    Error -1

    Can you please take a look and point out what is wrong with my .cfg file. My SDK Version is 2.0.0.4 and we are using IWR1642 OOB demo.

    regards

    Vikas

  • 0 in reply to Vikas Dubey
    TI__Mastermind 21295 points
    Hello Vikas,

    The processing chain in the mmWave SDK mmw (out-of-box ) demo only supports a subset of the possible chirp configurations that the mmWave Sensing Estimator can generate. Normally, the out-of-box demo is only used with the mmWave Demo Visualizer since it will only generate chirp configurations that are valid for the demo processing chain.

    For more flexibility in configuring the device and capturing/analyzing the raw data you may want to use the DCA1000EVM along with MMWAVE-STUDIO.

    Regards,
    John
  • 0 in reply to JohnH
    TI__Mastermind 25825 points
    Hello,

    Please refer to the below link with the chirp database, this has several configurations depending upon various parameters such as max range, range resolution, Max Velocity, Velocity resolution, update rate etc.

    dev.ti.com/.../

    And you could download the configuration files directly from the above link and use it.

    Thanks and regards,
    CHETHAN KUMAR Y.B.