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.

IWR6843: Effect of change in FOV on range of radar

Part Number: IWR6843

Hi,

If we modify FOV of azimuth and elevation, then will it effect on range of radar.

For e.g. 

Azimuth -90 to 90 degrees

Elevation -90 to 90 degrees

Range 59.99m

Doppler -30 to 30

Above configuration is as per 50m 2d LRPD config.

So, if I change azimuth to -40 to 40 degrees then this will affect the range of 59.99m? If yes then how this effect will take place whether range will increase or decrease?

Thanks,

Manoj

  • Hello.

    Changing the FOV will not have any impact on the maximum range of the chirp.  For more info on how these parameters are calculated, you can check out this document on programming chirp parameters.

    Sincerely,

    Santohs

  • Hi Santosh,

    Thank you for your response. I am using long range people detection binary and 50m 2d LRPD config file. I tried testing it without modifying any parameters in it. I found that sometimes IWR6843 doesn't detect objects. For few seconds it shows no object on mmWave Industrial radar tool and then again starts detecting objects, and it happened frequently.

    Baud rate I have used is 921600.

    Let me know your inputs on this.

    Thanks,

    Manoj

  • Any suggestions on this?

  • Hello.

    Apologies on the delay in response; my response for some reason did not get sent yesterday.  There are a variety of factors that may be causing this difference in performance, including the surrounding environment.  Are you trying to detect humans or different objects?  It is also possible that the SNR from these points are lower, and so the CFAR threshold needs to be lowered to be able to detect these points more consistently.

    Sincerely,

    Santosh

  • Hi Santosh,

    I have some observations. I have added config file in "Long range people detection" firmware by referring this document  Hard Coded Config (ti.com). I have added hardcode config file using "Editing the cli.c File" method. I have used "6843_50m_2D" config file.

    And I found that a slight difference in object detection in application. 

    Scenario 1: If I select and send config file using industrial visualizer then application shows boundary around radar and also detects objects with rectangle shapes.

    Scenario 2: Since I have hardcoded same config file used in Scenario 1 and I run visualizer using "Run without sending config file" option then radar is able to detect the objects but don't show boundary around radar and no rectangle shapes for objects. It shows dots only.

    Thanks,
    Manoj

  • Hello Manoj.

    The boundary boxes shown on the visualizer are extracted from the configuration file as this info is not being sent by UART to the visualizer.  I believe you could still load the configuration file without starting it if you wanted to get the boundary boxes drawn on.

    This question has deviated from the original topic of the question regarding the effect of changing the FOV on the radar.  For future questions, please submit a new question on E2E.

    Sincerely,

    Santosh

  • Hi Santosh,

    Sorry for deviating from the original topic. I will create a new question on E2E and closing this thread. 

    Thank you,

    Manoj