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.

IWR1443BOOST: Is it possible to do 3D modeling with IWR1443?

Part Number: IWR1443BOOST
Other Parts Discussed in Thread: IWR1443

Hi,

I bought an IWR1443BOOST EVM, and I've successfully got visualized data with mmWave Demo Visualizer.

I found out that the collected data represent one object with a few dots instead of a point cloud that shows the actual size and shape of the object. For example, the mmWave shows a wall with some separated dots rather than a line of dots. 

So my question is: is it possible for the IWR1443 to return such a point cloud as we can get from a laser radar or like Kinect in order to model the scene? Or how can we measure the size of the objects? Are there any available documents?

Thanks a lot. 

  • Hello Junlian Jia,

    So far the Out of box demo has not been tried for such mappng applications.
    The Out of box demo runs the IF signal through CFAR engine which marks the frequency spectrum peaks as distinct objects, that would explain why objects are showing fewer dots.
    CfarCfg arguments can be modified to let more objects be shown in the visualizer. Threshold is one the parameters that can be decreased to see more objects appear.

    Another way to visualize data from 3D sensing is by using the 3D demo which shows a heat map of data collected back along with 3d orientation of objects identified by CFAR steps.



    Regards,
    Vaibhav
  • Hi Junlian,

    As mentioned above, the CFAR detection algorithm (running on the Radar Accelerator) determines which peaks in the range-doppler FFT output are classified as valid objects. You can configure the CFAR thresholds to see more points.

    To evaluate the applicability of TI's mmwave devices and mmwave radar in general for your modelling application, you need to consider the following requirements for your scenario:

    1. Range: Distance from the sensor. What are the minimum and maximum ranges your object can be from the sensor.
    2. Range-resolution: How far two objects (or surfaces, edges etc in your case) need to be in order for the radar to be able to resolve them as two distinct objects. Put differently, how close the two objects can get before the radar is unable to resolve them as two.
    3. Anglular resolution: Similar to range resolution, but for the angle dimension i.e. how close the two objects can be in the angular dimension before the radar is unable to resolve the angle of objects wrt to the sensor.
    4. Range and angle accuracy.
    5. Velocity, velocity resolution.


    With the above requirements listed out, you can start by punching the numbers in the mmwave sensing estimator tool: https://dev.ti.com/gallery/view/1792614/mmWaveSensingEstimator/ to see if this is the right technology for your application.

    Regards

    -Nitin

  • Junlian,

    The following threads may also be of interest to you on this subject:

    1. e2e.ti.com/.../602501
    2. e2e.ti.com/.../600579
    3. e2e.ti.com/.../601043
    4. e2e.ti.com/.../601114

    Regards
    -Nitin
  • Hi Junlian,

    Hope the above response helped answer your question. If you don't have any more questions on this subject, can you please mark the response as a verified answer? Thanks.

    Regards
    -Nitin