IWR6843AOPEVM: Changing the profile configuration in the configuration file

Hi,

Poorneka T said:

Currently we are working on the overhead people counting demo using the industrial toolbox 4_9_0 (since it has a GUI for this demo)

In more recent versions of the toolbox you can use the industrial visualizer with the overhead 3D People Tracking software running on the device.

Poorneka T said:

When I tried using this, the radar hung up after the sensorStart. Can you please comment on this?

It looks like you have a typo in line 19. You have 10 where I think you should have 1 0. This is telling the device to look for a chirp that is not defined.

Poorneka T said:

b)Then, I tried to change the parameters like the ramp constant, number of ADC samples and the sampling rate to observe some changes in the detection. But this time also the radar hangs up after the sensorStart.

I am not sure if the 3D People Counting demo supports multiple different chirps, though I think it's unlikely given it doesn't support advanced frame configuration. The out of box demo certainly should. Can you try to make a configuration with multiple chirps that does not error out on out-of-box and see if it then works for people counting?

Best,

Nate

Hi Nate,

I have the following questions:

1) Changing the parameters in the profileCfg makes the radar hang up. While checking in the firmware, I found a comment like " User need to fill gMmwMssMCB.cfg.ctrlCfg and add profiles/chirp to mmWave before calling this function" in the mss_main.c in the Pcount3DDemo_configSensor.

Can you give me an explanation over this?

2)Next, I changed the config parameters like the staticBoundaryBox, boundaryBox and gatingParams. This time the firmware throwed the assertion error and runtime error and terminated the execution.

Is it like the config parameters are fixed for this hardware and the demo? 

It will be great if you give me s detailed info over this.

Thanks Nate,

Poorneka

Hi Poorneka,

Poorneka T said:

1) Changing the parameters in the profileCfg makes the radar hang up. While checking in the firmware, I found a comment like " User need to fill gMmwMssMCB.cfg.ctrlCfg and add profiles/chirp to mmWave before calling this function" in the mss_main.c in the Pcount3DDemo_configSensor.

What is the configuration file you're using? It sounds like it might be invalid.

Poorneka T said:

2)Next, I changed the config parameters like the staticBoundaryBox, boundaryBox and gatingParams. This time the firmware throwed the assertion error and runtime error and terminated the execution.

It's unlikely that changing these parameters would lead to this result. Can you give me the cfg file used?

Best,

Nate

The configuration file used is:

~/mmwave_industrial_toolbox_4_9_0\labs\people_counting\68xx_3D_people_counting\chirp_configs\AOP_6m_default.cfg

% 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
% "C:\ti\mmwave_industrial_toolbox_[VER]\labs\people_counting\docs\3D_people_counting_detection_layer_tuning_guide.pdf"
profileCfg 0 60.75 30.00 25.00 59.10 394758 0 54.71 1   96 2950.00 2 1 36 
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  96  0 55.00 1 0
dynamicRACfarCfg -1 4 4 2 2 8 12 4 8 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 1.5 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 20.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\mmwave_industrial_toolbox_[VER]\labs\people_counting\docs\3D_people_counting_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 2 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

This is the config file used for our testing.

Hi Poorneka,

Are you telling me that the default configuration isn't working? Because that is what is copied above. Or are you telling me that when you change the configuration it doesn't work. If so, please send me the changes you made such that the configuration no longer works. Please make the minimal number of changes to be sure we're talking about the same bug.

Best,

Nate