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: Fall detection ( front view)

Part Number: IWR6843AOP

Hello everyone,

Currently iam testing the fall detection algorithm and i found some problems which leads to false detections or no detection. 

Question 1

1. When iam in front of the sensor when iam falling forward with a normal speed, the "person" goes under the bottom plane and dissapears. this
only happens when iam falling toward or away from the sensor. If i try this again with a lower speed, the person doesn't dissapear and stays in de scene. 

If iam falling sideways it detects much better and stays in the scene. 

Here is the example: 

note: ignore the screen block (TID 16)

Mounting:

2.3m (on wall) 
Elevation ( 15 degrees )

Config settings:

% SDK Parameters
% See the SDK user's guide for more information
% "C:\ti\mmwave_sdk_[VER]\docs\mmwave_sdk_user_guide.pdf"
resetDevice
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 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\mmwave_industrial_toolbox_[VER]\labs\people_counting\docs\3D_people_counting_tracker_layer_tuning_guide.pdf"
staticBoundaryBox {xMin} {xMax} {yMin} {yMax} {zMin} {zMax}
boundaryBox {xMin} {xMax} {yMin} {yMax} {zMin} {zMax}
sensorPosition 2.3 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

I tried to change the frameCfg, see below. All of this had no effect on the problem.. 

    <numLoops>  224

    <framePeriodiocity> 120

    <frameTriggerDelay> 10 ms

Question 2

2. When iam further away from the sensor 3/4 meter, the height of the person isn't correct ( lower) . Is there a parameter in the config file
that i need to tune, or is there another solution?

Does anyone knows how i fix this issues, maybe with tuning other config settings?

Kind regards, 

Marnick

  • Hi Marnick,

    Thanks for your query. Please allow us a couple of days to respond to your question

  • Hi,

    1. When iam in front of the sensor when iam falling forward with a normal speed, the "person" goes under the bottom plane and dissapears. this
    only happens when iam falling toward or away from the sensor. If i try this again with a lower speed, the person doesn't dissapear and stays in de scene. 

    Can you make the zMin argument of the boundary box and the static boundary box lower? 

    2. When iam further away from the sensor 3/4 meter, the height of the person isn't correct ( lower) . Is there a parameter in the config file
    that i need to tune, or is there another solution?

    You may need to tune the algorithm for your use-case if performance isn't meeting your expectations. This is done in the software, not the config file.

    Best,

    Nate