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.

AWR1843AOPEVM: How to Enable Auto-Start Data Transmission on Power-Up in ODS AOP Application

Part Number: AWR1843AOPEVM
Other Parts Discussed in Thread: AWR1843AOP,

Tool/software:

Hello TI team,

I am currently working with the "obstacle_detection_aop" application from the following path:

\ti\radar_toolbox_2_20_00_05\radar_toolbox_2_20_00_05\source\ti\examples\Automotive_Body_Sensors

In the current setup, I am using the "ods_3d_visualizer.exe" tool to upload the configuration file via UART after powering up the radar, after which the radar starts transmitting data.

My requirement is:

I want the radar to start transmitting data automatically on power-up, without the need to upload the configuration through the visualizer.

Could you please guide me on how to modify the application or integrate the configuration in the code so that the radar starts data transmission automatically after power-on?

Thank you for your support.

Thanks

Mitesh

  • Hi,

    Our support team recommends NOT using the ODS demo but instead using the mmWave SDK 3.6 Out of Box demo

    This demo has support for starting the data on power up.

    thank you
    Cesar

  • Hello Cesar,

    Thank you for your response.

    Could you please confirm if the out-of-box demo binary for the AWR1843AOP is located at:

    C:\ti\mmwave_sdk_03_06_02_00-LTS\packages\ti\demo\xwr18xx\mmw\xwr18xx_mmw_aop_demo.bin

    Additionally, could you provide details on the detection range and field of view (FOV) supported by this demo?

    Thank you,



    Thank you
    Mitesh


  • Yes, this is the correct demo.

    The detection range for the OOB demo will be the same as the ODS demo because it is MIMO based (1Tx enabled at a time)

    FOV of OOB demo is also the same as ODS demo.

    So, the performance should be similar

    thank you
    Cesar

  • Thank you for your response.

    Could you please share the links or documents that mention the detection range and field of view (FOV) details for the OOB demo or ODS application?

    Thanks

    Mitesh

  • Hi,

    The FOV information is provided in the EVM UG, Section "2.4 AWR1843AOPEVM Antenna"

    https://www.ti.com/lit/ug/spruix8/spruix8.pdf

    Information about detected objects can be found in this TI Design Report. See Section "1.2 Key System Specifications"

    https://www.ti.com/lit/ug/tiduf00/tiduf00.pdf

    Thank you
    Cesar

  • Hello Cesar,

    Thank you very much for sharing the documents earlier.

    I was going through the following document:
    TI AoP Parking Application User Guide, which discusses the AoP Automated Parking Application, highlighting two different profile configurations: SHORT RANGE and ULTRA-SHORT RANGE.

    I would like to clarify the following:

    1. The demo you suggested:
      C:\ti\mmwave_sdk_03_06_02_00-LTS\packages\ti\demo\xwr18xx\mmw\xwr18xx_mmw_aop_demo.bin
      — is this the same AoP automated parking application referred to in the document?

    2. If yes, could you please share the profile configuration files for both SHORT RANGE and ULTRA-SHORT RANGE modes?

    3. More importantly, is there a single configuration file or mechanism within the demo that allows us to run both modes (short range and ultra-short range) by uploading one unified configuration file, or do we need to switch between two separate .cfg files manually

    Looking forward to your clarification.

    Best regards,
    Mitesh Rajpurohit



  • HI,

    The demo is the same, only the configurations are different.

    The Automated Parking configuration is provided in the Radar Toolbox

    C:\data-nobackup\2025\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\automated_parking

    Please read provided User Guide for information on how to run the demo. 

    As the TI Design User Guide explains, there is a single configuration file and two subframes are used, one for SRR and one for USRR, the frames run alternatively.

    The demo you suggested:
    C:\ti\mmwave_sdk_03_06_02_00-LTS\packages\ti\demo\xwr18xx\mmw\xwr18xx_mmw_aop_demo.bin
    — is this the same AoP automated parking application referred to in the document?

    Thank you
    Cesar