• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 211 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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: Miss match between Vital signs documents and configurations

Khanh Phan Quang
Prodigy 42 points
Part Number: IWR6843AOPEVM

Tool/software:

Hi everyone,

I noticed a discrepancy between the recommendations in the Vital Signs with People Tracking User Guide and the configuration in the chirp_configs folder for this application.

The User Guide recommends that the NearY value from staticBoundaryBox should be greater than or equal to 2. Moreover, the release notes for this application mention an improvement allowing NearY to be 1 or greater.

Despite this, the configuration for this application does not follow the "greater than or equal to 2" recommendation. Here’s the relevant part of the code:

Note that: staticBoundaryBox [-X] [X] [NearY] [FarY] [-Z] [Z]

%
% Tracker Layer Parameters
% See the Tracking Layer Tuning Guide for more information
% "<RADAR_TOOLBOX_INSTALL_DIR>\source\ti\examples\People_Tracking\docs\3D_people_tracking_tracker_layer_tuning_guide.pdf" 
staticBoundaryBox -1.5 1.5 0.3 1.75 0 3
boundaryBox -1.5 1.5 0.5 2 0 3
sensorPosition 2 0 15
gatingParam 3 2 2 2 10
stateParam 3 3 12 215 50 6000
allocationParam 20 100 0.1 20 0.5 20
trackingCfg 1 2 800 1 46 96 90
presenceBoundaryBox -1.5 1.5 0.3 1.75 0 3
maxAcceleration 0.1 0.1 0.1

Industrial Toolbox version: 4.12.1
Could someone check if this is a missed update in the configuration file or if I am misunderstanding something? Any help would be greatly appreciated.

Best regards,
Khanh

  • 0
    TI__Mastermind 19290 points

    Hello we are looking into this and will need a few days to provide a response; thank you for your patience.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    TI__Genius 11620 points

    Hi

    staticBoundaryBox only determines the area where a track is expected to be stationary. As long as the track is confined within this region you will not see any difference in the behaviour. This CLI does not affect the functioning of the demo but only determines where the likely presence of track 

    You can use the latest demo from radar tool box. You can find the demo in radar tool box at the following location

    radar_toolbox_2_20_00_05\source\ti\examples\Medical\Vital_Signs_With_People_Tracking

    Regards