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.

IWR1642: How to change People counting chirp/frame settings?

Part Number: IWR1642

Hello,

I would like to make changes to the chirp/frame used for the people counting demo. For example, I would like to use the fine motion chirp setting included in the industrial toolbox chirps database. However, some of the commands in the people counting configuration file use different format than the mmWave SDK. Is there way to do this?

Thanks!

Mustafa

  • Hi Mustafa,

    Please refer to the People Counting Lab customization guide provided under C:\ti\mmwave_industrial_toolbox_3_1_1\labs\lab0011-pplcount\docs\pplcount_customization_guide.pdf to understand the various commands and how to customize the demo.

    Thanks
    -Nitin
  • Hi Nitin,
    I am familiar with that document but it only talks about the gtrack specific commands (ex: SceneryParam, Gating Param, etc.). I have already made the necessary adjustments for these commands but what I wish to do is to make changes to the radar front end chirp settings (ex: chirp time, bandwidth, number of chirps per frame, etc). However, for some reason which I don't know why, the CLI commands syntax used in people counting demo is not exactly the same as the SDK command syntax which prevent me from just taking one of the chirp settings listed under the industrial toolbox database and just paste it in the .cfg file for people counting. Am I missing something here or do I need to look in the code and manually interpret people counting CLI commands? If I did that, would I be able to change the chirp settings or is there something in the people counting demo that expect the chip settings not to change? Mustafa
  • Hi Mustafa,

    The following configuration parameters are defined at the SDK level in: mmwave_sdk_03_01_01_02\packages\ti\utils\cli\src\cli_mmwave.c and are shared across all demos:

    flushCfg
    dfeDataOutputMode 1
    channelCfg 15 5 0
    adcCfg 2 1
    adcbufCfg 0 1 1 1
    profileCfg 0 60.6 30 10 62 0 0 53 1 128 2500 0 0 30
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 4
    frameCfg 0 1 128 0 50 1 0
    lowPower 0 1


    Other commands in the config demos are defined uniquely for each demo. Please check the configuration you have tried to load to ensure that the commands in the configuration are the same as the commands in the default people counting configurations.

    Regards,
    Justin
  • Thanks Justin. I got myself familiar with the above commands and was able to make the modifications I needed except for the following two commands:
    "cfarCfg 6 4 4 4 4 16 16 4 4 50 62 0"
    "doaCfg 600 1875 30 1"
    Do you know where can I get the documentations for these commands? They were not listed under the CLI or mmWave SDK user guide unless I am missing something. Thanks!
  • Hi Mustafa,

    Please see the attached spreadsheet for info on these chirp parameters.

    Regards,

    JustinchirpParams.xlsx

  • Hi Justin,
    Thanks for providing the spreadsheet. For <cfarMethod>, the command specifying a value of 6 but the it looks like the acceptable values are either 3 (for 1 pass) or 4 (for 2 pass). Not clear how the 6 was computed. Also for <cfarDiscardRangeLeft> and <cfarDiscardRangeRight>, I thought the guard cells are the ones discarded so I am not sure what are these cells? Finally, how is the threshold value calculated? Is it the same how is it listed in the SDK (CUT > Threshold scale + (noise sum / 2^x))? Thanks. Mustafa
  • Hi Mustafa,

    I have left out the option for 6 in the document regarding the CFAR types - please see the if statements starting at line 185 in lab0015/src/common/radarProcess.c - this is where the CFAR type is selected.

    Regards,
    Justin
  • Thank Justin. It seems this mode (6) enable CASO-CFAR for range and azimuth. Also. I am infuring from the code that <cfarDiscardRangeLeft> and <cfarDiscardRangeRight> are the cells to discard around the edges while the guard cells are the ones to discard during the search. I am still not clear on the threshold calculation but I think I will figure it out once I do more reading. Thanks! Mustafa