• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 293 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.

AWR1642BOOST: Problem for tracking after 80 meter

florian even
Prodigy 240 points

Part Number: AWR1642BOOST

Hi,

I used the demo "traffic monitoring" and after 80 meters the tracking doesn't work. I think it's a problem of settings but I don't arrive to solve this problem. In my configuration i can detect the point until 180 meters. Did you have a solution ? 

SIncerly,

FE

  • 0
    TI__Mastermind 28055 points

    Hi Florian,

    Are you aware of the Scenery parameters? These set limits on the valid tracking area. Most likely there is a line in your cfg file that says:

    SceneryParams -40 40 0 80 - or something similar. The key is as follows:

    SceneryParams <Left Limit> <Right Limit> <Close Limit> <Far Limit> - a box is formed from these vales. For Left and Right limits, left is negative, right is positive.

    Regards,

    Justin

  • 0 in reply to Justin Curewitz
    Prodigy 240 points

    H, 

    thanks for your answer,

    this is my.cfg :

    sensorStop
    flushCfg
    dfeDataOutputMode 1
    channelCfg 15 1 0
    adcCfg 2 1
    adcbufCfg 0 1 1 1
    profileCfg 0 76 2 5 52.62 0 0 4.007 1 256 6250 0 0 48
    chirpCfg 0 0 0 0 0 0 0 1
    frameCfg 0 0 118 0 50 1 0
    lowPower 0 1
    guiMonitor 1 0 0 0
    cfarCfg 4 12 2 16 8 4 0 63 63 0 1
    doaCfg 3 0 1047 3 600 10 100
    %for 18xx board SN4855900006
    compRangeBiasAndRxChanPhase -0.0438848 0.12320 -0.62793 0.08932 -0.50342 -0.03458 -0.58853 0.06812 -0.69101 -0.79391 -0.60803 -0.63580 -0.45255 -0.70901 -0.26627 -0.73044 -0.46078
    sceneryParam 1 -2 15 10.0 170 0 0 0 0 1 1.25 11.0 20.0 160 0 0 0 0
    gatingParam 12 8 4 0
    stateParam 3 10 20 2000 10
    allocationParam 60 60 1.0 3 2.8 2.0
    variationParam 1.15 0.433 1.0
    trackingCfg 1 1 250 20 189 330 50 90
    sensorStart

    I didn't arrived to found wich parameters correspond to wich number. Where can I found  informations about that ? I have a file "chirpParams_TMdemo.xls" but without information about ScenaryParam.

    Regards,

    FE

  • 0 in reply to florian even
    TI__Mastermind 28055 points

    Hi FE,

    This may not be properly documented. You can check the cli command in the source in this case:

    From mss/cli.c, line 584:

    cliCfg.tableEntry[10].cmd = "sceneryParam";
    cliCfg.tableEntry[10].helpString = "<numBoundaryBox> <Left1> <Right1> <Bottom1> <Top1> <Left2> <Right2> <Bottom2> <Top2> <numStaticBox> <Left1> <Right1> <Bottom1> <Top1> <Left2> <Right2> <Bottom2> <Top2>";
    cliCfg.tableEntry[10].cmdHandlerFxn = MmwDemo_CLISceneryParamCfg;

    Boundary boxes are the first 9 arguments - you can set 0, 1, or 2 for number of boundary boxes. If 0, there is no boundary and anything can be tracked. Arguments 2 - 5 (Left1 - Top1) set the first boundary box limits. Args 6- 9 set the second boundary box limits. Static boxes are set the same way as boundary boxes, and govern where an object that is static (no points detected and 0 velocity) will be maintained. For now leave this default or set it to be equal to the boundary box.

    Bottom is the closest an object can be tracked to the radar, Top is the farthest an object can be tracked from the radar. The current top value is 170 - so this isn't the reason you are dropping objects at 80 meters. You can try increasing the Left1, as this -2 is very small and is probably causing the issue. Try -15 instead.

    Regards,

    Justin

  • 0 in reply to Justin Curewitz
    Prodigy 240 points

    Thanks for those informations.