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.

IWR6843ISK: People count demo does not work when large number is set to maxNumTracks parameter.

Part Number: IWR6843ISK

Hi,

I am running people count demo in the following folder.

    "mmwave_industrial_toolbox_3_4_0__win\mmwave_industrial_toolbox_3_4_0\labs\lab0020_pplcount_Overhead\GUI_A_base_no_logic"

When I set 64 to maxNumPoints parameter in mmw_pplcount_demo_default.cfg as below, the demo doesn't run.

    trackingCfg 1 2 250 64 200 100 90

I looked at the source code of gtrack library and found a comment line saying that maxNumPoints can be 250 at maximum.

Compared to 250, 64 is smaller.

Why does this parameter cause demo not running?

Thank you. 

  • Hi User,

    I will need to talk to my team about this but we should have an answer for you sometime next week.

    Cheers,

    Akash

  • Hi User,

    This command is setting the number of points GTrack expects to 64, as well as the number of points the MSS is allocating space for to 64.  The DSS is still sending up to 250 points, so we are indexing outside of the point array when the MSS copies the points from the DSS. 

    Why do you need to limit the number of points?

    Regards,

    Justin

  • Hi Justin,

    I am sorry! I made a mistake in the post above.

    I was trying to say "maxNumTracks", not "maxNumPoints".

    Here shows the default parameter that TI recommends, and my parameter.

        TI recommended parameter : trackingCfg 1 2 250 20 200 100 90

        my parameter : trackingCfg 1 2 250 64 200 100 90

    As you can see above, I changed "maxNumTracks" parameter from 20 to 64.

    I expected gtrack to create and handle 64 tracks at maximum by this parameter change, which means it can detect 64 people at maximum.

    However, when I applied this parameter change, the demo does not run.

    Why is this so?

    Thank you.

  • Hi Fields,

    GTrack allocates memory for each track.  The device does not have enough memory available on the cortex R4F to allocate for 64 tracks.  If you run the demo in debug mode, you can see in the code composer studio console output that will show memory being allocated during the gtrack initialization process.  This will allow you to determine the maximum number of tracks you could allocate.

    Regards,

    Justin