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.

IWR6843AOPEVM: 3D People Counting Lab stops working

Part Number: IWR6843AOPEVM

Hello, I want to improve the range of 3D People Counting Lab by giving the below cli commands suggested by mmwave sensing estimator.

profileCfg 0 60 2 4 20.95 0 0 13.76 1 128 8027 0 0 30
channelCfg 15 7 0
adcbufCfg -1 0 1 1 1
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 2
chirpCfg 2 2 0 0 0 0 0 4
frameCfg 0 2 66 0 40 1 0

But when I am changing the parameters like freq slope, no. of adc samples and the sampling rate from the above profilecfg to the default cfg file for 3D People counting Lab, the python gui stops working. Could someone explain what the problem is?

  • Hi,

    Can you use TeraTerm to send the .cfg file to debug? It should give an error message. Additionally, you could start with a working config file and make incremental changes to understand what breaks it. Let us know how that goes and what more info you can get.

    Best,

    Nate

  • Hi Nathan,

    Thanks for the response. 

    The built in cfg for 3D People Counting is working perfectly using tera term. But when I am making changes only to the profilecfg and framecfg parameters with the values from mmwave estimator to improve the range I am getting an error message '-1' when I am starting the sensor. 

    Default config:
    profileCfg 0 60.75 30.00 25.00 59.10 394758 0 54.71 1 96 2950.00 2 1 36
    frameCfg 0 2  96  0 55.00 1 0
    Improved config from estimator:
    profileCfg 0 60 2 4 20.95 0 0 13.76 1 128 8027 0 0 30
    frameCfg 0 2 66 0 40 1 0
    Could you help me with the issue please?


  • Hi Jomin,

    Can you make the changes one at a time so we can see which parameter breaks this?

    You can also find the acceptable values and limits for the parameters here in the user guide PDF

    C:\ti\mmwave_sdk_03_06_00_00-LTS\docs

    Best,

    Nate

  • Hi Nathan,

    But these values in profileCfg and frameCfg are inter-depended. So will it be a good idea to change one at a time?

    Thanks,

    Jomin

  • HI Jomin,

    Some of the values are interdependent, but others may be changed sequentially. You can also put the device in debug mode to see more detailed output.

    I have found that the below configuration works. I would be willing to bet you're not allocating enough ramp end time. Put it in debug mode to get the exact error message.

    % SDK Parameters
    % See the SDK user's guide for more information
    % "C:\ti\mmwave_sdk_[VER]\docs\mmwave_sdk_user_guide.pdf"
    sensorStop
    flushCfg
    dfeDataOutputMode 1
    channelCfg 15 7 0
    adcCfg 2 1
    adcbufCfg -1 0 1 1 1
    lowPower 0 0
    
    % Detection Layer Parameters
    % See the Detection Layer Tuning Guide for more information
    % "<RADAR_TOOLBOX_INSTALL_DIR>\source\ti\examples\People_Tracking\docs\3D_people_tracking_detection_layer_tuning_guide.pdf"
    profileCfg 0 60 2 4 59.10 0 0 13.76 1 128 8027 0 0 30
    %profileCfg 0 60 2 4 20.95 0 0 13.76 1 128 8027 0 0 30
    
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 2
    chirpCfg 2 2 0 0 0 0 0 4
    frameCfg 0 2 66 0 40 1 0
    dynamicRACfarCfg -1 4 4 2 2 8 12 4 12 5.00 8.00 0.40 1 1
    staticRACfarCfg -1 6 2 2 2 8 8 6 4 8.00 15.00 0.30 0 0
    dynamicRangeAngleCfg -1 0.75 0.0010 1 0
    dynamic2DAngleCfg -1 3.0 0.0300 1 0 1 0.30 0.85 8.00
    staticRangeAngleCfg -1 0 8 8
    antGeometry0 -1 -1 0 0 -3 -3 -2 -2 -1 -1 0 0
    antGeometry1 -1 0 -1 0 -3 -2 -3 -2 -3 -2 -3 -2
    antPhaseRot 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1
    fovCfg -1 70.0 70.0
    compRangeBiasAndRxChanPhase 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
    
    % Tracker Layer Parameters
    % See the Tracking Layer Tuning Guide for more information
    % "C:\ti\radar_toolbox_[VER]\source\ti\examples\People_Tracking\docs\3D_people_tracking_tracker_layer_tuning_guide.pdf" 
    staticBoundaryBox -3 3 0.5 7.5 0 3
    boundaryBox -4 4 0 8 0 3
    sensorPosition 2 0 15
    gatingParam 3 2 2 3 4
    stateParam 3 3 12 500 5 6000
    allocationParam 20 100 0.1 20 0.5 20
    maxAcceleration 0.1 0.1 0.1
    trackingCfg 1 2 800 30 46 96 55
    presenceBoundaryBox -3 3 0.5 7.5 0 3
    sensorStart
    

    Best,

    Nate