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.

IWR6843AOP: 3d People Tracking Distance Measurement

Part Number: IWR6843AOP

Hello,

I'm using the IWR6843AOPEVM with the MMICWAVEICBOOST with the 3D People Tracking software from mmwave_sdk_03_06_01_00-LTS. I'm using the industrial analyzer to capture the TLV data.

I would like to use the part to measure targets at distances up to 30 m. I have successfully measured targets beyond 30 meters, but there appears to be a bug in the sdk software that limits the reported distance to 16.3 meters. When targets are at distances greater than 16.3 meters the distance wraps around and the reported distance is: (actual target distance) - n * 16.3. I have observed cases where n is 1 and 2. 

I'm using the document below to read the TLV. 

<install folder>/radar_toolbox_1_30_01_03/source/ti/examples/People_Tracking/3D_People_Tracking/docs/3d_people_tracking_user_guide.html

I'm monitoring rangeUnit variable (float, 4 Bytes), and the range variable (int16_t, 2 Bytes). I'm reading the range variable as an unsigned int. I see the range variable approach 65535 (max value for a 2 byte unsigned int), and then as the target gets farther away I see the range variable go to a small number around 1000. The rangeUnit variable does not change. 

See the plot below for an example of the distance wrap reported in the point cloud TLV. Between 40 seconds and 70 seconds the target is slowly walking away from the radar at an azimuth of 0 degrees, then from 70 seconds to 100 seconds the target walks back towards the radar. While walking away and returning the target stops for 2 to 3 seconds at about 9 meters.

I can provide the binary files collected during this test if that will be helpful. Please let me know if there is anything I'm doing incorrectly in interpreting the TLV data.

Thank You,

David

  • Hi David,

    The behavior you're experiencing here seems plausible to me. When I look in mss_main.c, on line 1731, the rangeUnit is set to 0.0025. When this reaches the limit for the range variable (65535), their product is around 16.3 meters. So, I think you could get around this by reducing the rangeUnit from 0.0025 to say 0.000625, which should increase the maximum range by a factor of 4. Let me know if this works.

    Best,

    Nate

  • Thanks Nathan, I'll test this and get back to you.

  • Hi Nathan,

    I had a chance to run some tests on this item today. The rangeUnit was originally set to 0.00025 when I was seeing the wrap at about 16.3 meters. I changed it to 0.000125 and saw the wrap at about 8.1 meters. I changed it to 0.00075 and see accurate distances beyond 16 meters. I have not had a chance to test out to 50 meters where I expect it to wrap with the latest setting, but this issue is now resolved. Thanks for your insight on this.

    Regards,

    David