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: AWR1642BOOST : Obstacle detection

Part Number: AWR1642BOOST

Hallo,

is the obstacle detection in mmwave_automotive_toolbox_2_9_1 intended for AWR1642Boost or AWR1642ODS? the correct result is shown for which AWR (boost or ODS)

Thanks in advance

Walid

  • Hi

    it is 1642BOOST-ODS

    this information is provided in the release notes

    mmwave_automotive_toolbox_2_9_1__win\mmwave_automotive_toolbox_2_9_1\labs\lab0004_obstacle_detection\docs

    thank you

    Cesar

  • Hello Cesar,


    thanks for your quick reply but in docs it says:
    This lab demonstrates the use of TI mmWave sensors to detect objects that are within close proximity of a vehicle. Using the AWR1642-ODS EVM, algorithms run onboard the single-chip device to create Range-Azimuth and Range-Elevation heatmaps, then performs object detection with CFAR, angle of arrival estimation and clustering on configured range rows in the heatmaps.

    So stands for AWR1642-ODS. 

    if I try this with awr1642boost, strange objects are detected

    Many thanks
    Walid

  • Yes,
     
    Sorry for the confusion.
     
    The official name of the ODS board is AWR1642BOOST-ODS not AWR1642-ODS
     
    Here is the link
     
     
    Thank you
    Cesar
  • Hallo,

    Thank you for your answer.

    I have just read the document about obstacle detection and have the following questions about the topic:
    the text says:
    1) To provide a field of view of +/- 70 degrees in azimuth and a field of view of +/- 40 degrees in height, the AWR1642BOOST-ODS EVM must be placed with an antenna on top, as shown in this image.

    first question:

    the field of view is +/- 70 degrees in azimuth, how can the gui be defined from 0 to 180 degrees, is that correct? actually this should be between +/- 70 degrees in azimuth (i.e. 140 degrees) and more should not be detected.

    2) Detected objects and clusters are displayed by default. Detected objects are displayed in 3D space as points and clusters as boxes.

    second question:
    i don't quite understand what the difference between a point and a cluster is, if the point is a detected object what is a cluster? also a detected object and why it is shown as a cluster and not as a point.

    third question:

    the maximum detection range here is in gui up to 3m, but for me only objects up to 2m are no longer detected, I do not know why.

    I made a change to cfg file and read the mmwave_sdk_user_guide under section 3.4 (C: \ ti \ mmwave_sdk_02_01_00_04 \ docs) and could not change that. and then took a shower with mmWaveSensingEstimator and unfortunately it didn't work.
    could you please give me a tip where I can change the maximum range.

    Thanks in advance

    Walid

  • 1) The gui is a simple PC host application and can be defined in any way. In this case it was defined 0-180 in order to make it more generic.

    2) Clustering algorithm is dbscan clustering algorithm, please read more in academic litterature

    3) The detection depends on several factors: FOV, RCS of object, movement, static...

    In your application the objects may not have sufficient RCS to be detected. Try other metal objects that may have more reflectivitiy. Also detection is much better if object is moving

    good luck with your project

    thank you

    Cesar

  • Thank you very much for your detailed answer:).

         
    to question 3:


    I wanted to know how you can change the maximum range, our example is limited to 3 m but I want to change the maximum range and I tried the following:
    I made a change to the cfg file and read the mmwave_sdk_user_guide under section 3.4 (C: \ ti \ mmwave_sdk_02_01_00_04 \ docs) and could not change this. and then showered with mmWaveSensingEstimator and unfortunately it didn't work.


    Could you please give me a tip on where I can change the maximum range?

    thank you in advance

    Walid 

  • Hi,

    please search this forum about how the maximum range is computed.

    Once you understand which RF chirp parameters define the maximum range, please update them in the chirp configuration provided in

    mmwave_automotive_toolbox_2_9_1\labs\lab0004_obstacle_detection\chirp_configs\ods_default_config.cfg

    The format used is the same as the mmwave sdk demo. The mmwave sdk demo UG will help to understand what each number corresponds to

    thank you

    Cesar