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: Issue on TARGET LIST generated based on overhead people counting lab

Part Number: IWR6843AOP

Hi Teams,

1. I did the several experiments and found the result that the TARGET LIST was very difficult generated   

    when walking along with +Z axis to -Z axis in walking speed about 0.3 Meter / sec

    there are two Test Cases as followings,

    Test Case 1: when walking from +Z axis (+3 Meter)  to -Z axis (-3 Meter)

                         the POINT CLOUD can found on location of Z = +3M but TARGET LIST did NOT be generated

                         until walking to location of Z = +1.5M then the TARGET LIST can be generated

    Test Case 2: reversed the walking direction, when walking from -Z axis (-3 M) to +Z (+3 M) axis

                         the POINT CLOUD can be found on location of Z = -3M and TARGET LIST be generated both at the same time

                         performance better than Test Case 1 

2. Any suggestion?

   may possible fine tune configuration parameters to fixed this issue?

3. My working environment as followings,

   - CCS 8.3.1

   - SDK 3.5.0.4

   - Industrial Tool 4.8.0

   - Lab: Overhead 3D People Counting

   - Hardware: IWR6843AOP

   - Config File: "C:\ti\mmwave_industrial_toolbox_4_8_0\labs\people_counting\overhead_3d_people_counting\

                         chirp_configs\pc_6843_3d_aop_overhead_3m_radial.cfg"

Regards,

Kevin

  • Hello Kevin,

    What do you mean by the Z direction? The orientation of the coordinates can shift depending on the world vs sensor coordinates. I think you mean the elevation direction of the sensor. 

    Either way, please see the tracking tuning guide. You may need to reduce the SNR threshold for the tracker or the min points for allocation. Please see the allocationParams and trackingCfg parameters in the following document.

    3D_people_counting_tracker_layer_tuning_guide.pdf

    Regards,

    Jackson

  • Hi Jackson,

    1. The Z axis is the value which had been computed by range and sine of elevation as followings, 

        based on SENSOR view with celling mounted  (not WORLD view here)

      Based on IWR6843 3D(r, az, el) -> (x, y, z)
    r : range
    el: elevation φ az: azimuth θ z = r * sin(φ) x = r * cos(φ) * sin(θ) y = r * cos(φ) * cos(θ)




    2. the key issue on Target List generated is NOT symmetric performance on both sides of Z axis
    above mentioned Test Case 2 is better than Test Case 1

    3. I had tested some parameters on what you mentioned that tuning on allocationParams but not significant improvement

    Any method to tune as symmetric performance on Target List generated?


    Regards,
    Kevin
  • Ok thank you for the clarification, I understand now. The matlab visualizer should save a .mat file named fhist_xx.mat. If you look at this it should show you the data of the point cloud. Then you can calculate whether there is a difference in point cloud strength on one side or the other.

    One thing to check, is if the issue is related to scene clutter. Have you tried testing in a different environment or rotating the device 90 or 180 degrees? Sometimes there can be some clutter or items causing reflections that will cause these differences in point cloud density or SNR or other metrics. Have you done this?

    Regards,

    Jackson

  • Hi Jackson,

    I had rotated the device in different degree of 180 degree then the result is still the same as before

    not  SYMMMETRIC performance along with Z-axis.

    (1) Worse Case:

          If a man stands at the location of  "Z = +3.0 Meter" then lots of point cloud can be seen but the TARGET LIST

          could not be generated until walking approach to "Z = +1.5 Meter" I can see one TRAGET be genrated

    (2) Better Case:

         If a man stands at the location of  "Z = -3.0 Meter" then lots of point cloud can be seen and the TARGET LIST

         could be generated I can see one TRAGET be genrated

     

    Why does the device have the unSymmetric beharivor?      

    Regards,

    Kevin

  • Hi Kevin,

    This is difficult to say. Do you have the saved fHist file with the pointcloud and tracking data? If you can upload that here I can take a look in more detail.

    Regards,

    Jackson

  • Hi Jackson,

    The logged file(fHistRT_0001.mat) and snapshots as followings,

    (1) upload file fHistRT_0001.mat

         Please let me know whether upload success ? (by using drag and drop method,  drag file over to the "Description" box on E2E)

    (2) walikng direction from +Z to -Z axis (worse case, Target List Generated started from +1 M)

    (3) walikng direction from -Z to +Z axis (better case, Target List Generated started from -2 M)

    Regards,

    Kevin

  • Hi Kevin,

    Looks like it didn't upload properly. Try using the insert>file. I can't tell much from the images.

    Thanks,

    Jackson

  • Hi Jackson,

    reSend attached file,

    Regards,

    Kevin

  • Hi Kevin,

    Unfortunately, I can't access dropbox or other filesharing applications. The best way is to attach the file here. Did you try using the insert>file option? That has worked for me before.

    Regards,
    Jackson

  • Hi Jackson,

    Try to using insert>file option

    It is not allowed to be inserted see following,

    Regards,

    Kevin

  • Hi Kevin,

    I think instead of copying in the file location, if you click the upload button it will let you choose. If not, please try adding it to a zip file and uploading here. Not sure why it isn't working for the other methods.

    Regards,

    Jackson

  • Hi Jackson,

    Do you have another way to load file of 'fHistRT_0001.mat'?

    Reagrds,

    Keivn

  • Did you try putting it in a zip file?

    Also please make sure you are trying this on Google Chrome browser.

  • Also, it seems you might be trying to upload the link from dropbox. Please make sure it is a file located on your local machine.

  • Hi Jackson,

    It seems accept ZIP file format, see following,

    fHistRT_0001.zip

    Regards,

    Kevin

  • Hi Kevin,

    It looks like your tracks are more uniformly allocating at shorter distances. Try 2 things.

    Decrease the TX backoff power in the profileCfg. You can probably set this to 0 for testing, as this should increase the pointcloud response at higher ranges.

    Decrease the allocation SNR thresholds. They are set right now to 20dB SNR, but can be decreased. This is common behavior to have fewer points at higher angles and distances, so the cumulative SNR would be lower. I suggest lowering them to 5 or 10 and check for improvement. This is snrThres and snrThreshObscurred in allocationParams.

    Regards,

    Jackson

  • Hi Jackson,

    I had changed parameter on TX backoff power in the profileCfg as 0 which had slight improvement 

    But changed on snrThres as 5 and snrThreshObscurred as 10  in allocationParams seems not quiet improvement

    I would like to close this thread here and thanks for help

    Regards,

    Kevin