• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 31 subscribers
  • Views 478 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.

Original question:

IWR6843ISK-ODS: IWR6843 ODS ES 2.0 sensor sending bad packets often

IWR6843ISK-ODS: How to tune the IWR6843 ODS ES 2.0 for the new 3D demo?

radha
Intellectual 905 points
Part Number: IWR6843ISK-ODS

Hi all,

I'm working on the new 3D demo available in ITB 4.1 for ODS sensor. I'm having trouble with understanding the staticBoundaryBox and boundaryBox parameters and tuning the sensor with those parameters. They aren't the same as old SceneryParam.

I have referred the new documentation which states:

  1. staticBoundaryBox [-X] [X] [NearY] [FarY] [-Z] [Z]
    • This sets boundaries where static points can be used by the tracker and tracks are allowed to become static. Each value denotes an edge of the 3D cube. Currently, it is recommend to keep NearY greater than or equal to 2.
  2. boundaryBox [-X] [X] [NearY] [FarY] [-Z] [Z]
    • This sets boundaries where tracks can exists. Only points inside the box will be used by the tracker. Each value denotes an edge of the 3D cube.

but I'm still confused. I also don't need my targets to be static so how do I eliminate that parameters or how do I unset it? 

Can anyone help me with this?

Regards,

radha.

  • 0
    TI__Mastermind 28055 points

    Hi Radha,

    Only targets in the boundary box will be tracked, so that should be set to the area you care about.

    Since you do not want to track static targets, set the FarY value to be smaller than the Near Y value - if static boxes is set to zero, then everywhere is considered inside the static box - unfortunately, we have not yet built in a static box disable to the software. The workaround is to design the static box so that the target could never actually be in the box, I suggest doing this by setting FarY less than NearY. The target must have Y greater than NearY and smaller than FarY, which will be impossible in this configuration - note that the GUI will still draw the box.

    Regards,

    Justin

  • 0 in reply to Justin Curewitz
    Intellectual 905 points

    Hi Justin,

    Thanks for your details. Here are my parameters in .cfg file

    staticBoundaryBox -2 2 4 2 -2 2
    boundaryBox -1 1 0 8 -2 0

    So this should track the targets in boundaryBox zone and static targets should be disabled right? But that doesn't happen and I see that the below config is sent to the sensor from python GUI.

    b'staticBoundaryBox -0.5 0.5 0.5 7.5 -1.5 1.5 \n'
    b'Done \n'
    b'\rmmwDemo:/>boundaryBox -1.0 1.0 0.0 8.0 -2 2 \n'
    b'Done \n'

    Why is my staticBoundaryBox parameter changed to some other value? 

    Regards,

    radha.

  • 0 in reply to radha
    TI__Mastermind 28055 points

    Hi Radha,

    After selecting the chirp config with the gui, it will populate the boundary and static box parameters. It will send the parameters in the box. Please check to make sure these are correct. Otherwise, ensure you are sending the right chirp config.

    Regards,

    Justin

  • 0 in reply to Justin Curewitz
    Intellectual 905 points

    Hi Justin,

    The boundaryBox value doesn't change but the staticBoundaryBox changes to some other value that is not set in cfg file. I have verified that I'm loading the correct cfg file.  Why is this occuring? 

    I'm using gui from ITB 4.1.0. Is there any changes in latest ITB 4.2.0?

    Thanks,

    radha.

  • 0 in reply to radha
    Intellectual 905 points

    Hi Justin,

    The issue that I stated above has been fixed in the latest GUI from latest ITB 4.2. 

    Thanks for your help.

    Thanks,

    radha.