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

Original question:

AWR1843BOOST: How to port Area Scanner Demo firmware from IWR6843 to AWR1843?

AWR1843BOOST: Area Scanner: what's the explanation of this output?

Mostafa Besar
Intellectual 470 points
Part Number: AWR1843BOOST
Other Parts Discussed in Thread: AWR1843

I am using AWR1843 & Industrial toolbox 4_7_0 & SDK 3_5_0_4 

I am showing the behavior of this demo indoor in two videos

First video: drive.google.com/.../view

In this test case no moving objects on front of the radar, so it's showing only static objects.

Q1. What's the flickering object showed GUI less than 2 meter refer to?

Q2. why there are some static objects still visualized even I they are not existed any more?

Second video: drive.google.com/.../view

In this test case, there is one person moving on front of radar although visualizer shows two tracked objects in different way, one tracked object truly represent the person and the second tracked object has no meaning. What's the explanation of that?

Thanks,

  • 0
    TI__Mastermind 23725 points

    Hello

    In order to debug the results you may want to isolate the issue to the signals that are leading to the detection, you want to try the OOB demo to view what a simpler version of  processing algorithm shows for the exact same scene.

    Signal related:

    1. Understand the location/d3d co-ordinates of the points

    2.  Do the Range FFT, Doppler fft - heat map map plots show higher intensity in the range/doppler region of interest -- This can be done  via OOB demo : See  mmwave demo UG or 5.7 Getting Up and Running with TI's mmWave Sensors

    3. For further  RF data debug analyze using DCA1000 + mmWave studio to see what mmWave data look like for the scene of interest.

    Use demo knobs:

    Each of the  demo provided  for mmWvae devices provide knobs to adjust  algorithm, detection parameters. You may want to understand the available knobs and see what role it plays for  detection of objects in your scene. Some common parameters to look for are:

    1. CFAR thresholds - these decide what intensities get detected as objects vs not. https://en.wikipedia.org/wiki/CFAR

    2. Demo specific knobs :  Tracker thresholds,  static on/off, peak grouping.,  History of scene- area scanner.

    Please see the UG specific to demo and SDK UG for  explanation of these knobs.

    Considering you have ported this demo from xWR6843 version to xWR1843 you may have  to take into account what the corresponding Chirp/RF parameters  and see if they meet the  range/resolution needs of your scene.

    Hope this helps you tune/debug further.

    Thank you,

    Vaibhav