IWR1642: Traffic Monitoring Demo cannot detect points in near areas(0~6m from radar).

Hi Fields,

I'll need to ask an expert about this but we should have an answer for you sometime next week.

Cheers,

Akash

Hi, Amanda.

I recognize that the BoundaryBox parameter is for Gtrack(clustering), and it has nothing to do with point cloud data that has not yet been passed to Gtrack.

Even if some points are outside the boundary and cluster will not be allocated from these points, I would still have to be able to see the point cloud data on matlab gui app, wouldn't I?

I would like to see the point cloud data, not tracks.

About the mounting position and FOV...

I waved my hand in front of the radar(5 cm away from radar). This MUST be inside the FOV.

The matlab app displayed many points at the range of 10 m~40 m, so it seems to be detecting my hand somehow.

However, it doesn't display points at the range of 5 cm.

My expectation is that the matlab gui app displays points at 5 cm.

Best regards,

Fields

Hello,

If you are primarily interested in point cloud data I would suggest using the mmWave SDK demo and the online visualizer. This will enable you to try different configurations with shorter range and tune detection thresholds. 

http://dev.ti.com/tirex/explore/node?node=AKI2vzjJPKr9w.81p19MhQ__VLyFKFf__LATEST

As to why you are not seeing points in the near range when you wave your hands this could be for a few reasons:

1. The range resolution of the MIMO configuration is only 0.25m. In the processing chain, the first few range bins are discarded from detection due to FFT leakage. You can see this effect if you look at the OOB demo and the range profile. For this reason, for short range applications it is better to design a short range, better range resolution chirp configuration.

2. The plots being plotted in the TM GUI are scaled by SNR - it is possible that the SNR of your hand is very low so the point is not visually visible. You can check if there's detection by changing to a fixed point size in the GUI source code.

In general, if you are interested in short and long range detection I would suggest considering using multiple chirp profiles for each sensing case as this would enable a rich point cloud in the short range while maintaining long range detection.

Amanda

Hi, Amanda.

I am little confused about mmWave SDK demo.

I was thinking that the mmWave SDK demo for IWR1642 is placed in "C:\ti\mmwave_sdk_03_02_01_02\packages\ti\demo\xwr16xx\mmw".

However, the link above leads me to "C:\ti\mmwave_industrial_toolbox_3_6_2__win\mmwave_industrial_toolbox_3_6_2\labs\demo0005-mmwave-sdk-16xx\demo0005_mmwave_sdk_16xx_pjt".

How are they different?

In "C:\ti\mmwave_sdk_03_02_01_02\docs\mmwave_sdk_user_guide.pdf", there is an instruction how to build demo.

In "C:\ti\mmwave_industrial_toolbox_3_6_2__win\mmwave_industrial_toolbox_3_6_2\labs\demo0005-mmwave-sdk-16xx\demo0005_mmwave_sdk_16xx_pjt\mmw_16xx_user_guide.pdf", there is also an instruction how to build demo.

How are the two binaries different?

Best regards,

Fields.