• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 209 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.

AWR1843AOPEVM: Ghost object mintigation using calibDcRangeSig

Tanoop Rajan
Intellectual 331 points
Part Number: AWR1843AOPEVM
Other Parts Discussed in Thread: AWR1843AOP

Tool/software:

I am running the obstacle detection lab on the AWR1843AOP. I flashed the prebuilt binary and loaded the predefined configuration files through the visualizer.

While doing so, I observed constant ghost points at 0.5m. After further investigation, I found that these could be due to antenna coupling (RX-TX). To mitigate this, I added the calibDcRangeSig command to the configuration file, as the predefined configuration did not include it.

However, after adding the following command:

calibDcRangeSig -1 1 0 20 256

The radar is now detecting a constant object at 1m along the center of the radar.

I have read all available guides, including the SDK documentation and forum discussions, but I am still unable to resolve this issue.

I executed this command when no objects were present in the boresight of the radar for more than a minute.

I also ran the Out_of_the_box demo and sent calibDcRangeSig -1 1 0 20 256 through CLI, but still seeing some ghost at 0.5 m

calibDcRangeSig -1 1 0 22 256

  • 0
    TI__Genius 12986 points

    Hello,

    Thank you for your question regarding ghosting. First of all, I'm not sure how many total range bins your configuration has, but using 21 positive range bins in the DC range calibration may be overcompensating. We typically use the first 9 positive range bins, so try lowering it down to 5 to 10 positive range bins instead. We also usually use the last 5 negative range bins, so consider including some 3 to 5 negative range bins.

    I would also recommend calibrating the sensor to compensate for bias in the range estimation and receive channel gain and phase imperfections and see if that helps. I have included a screenshot with calibration instructions taken from the mmWave SDK Module Documentation for the mmw Demo under <MMWAVE_SDK_INSTALL_DIR>/packages/ti/demo/xwr64xx/mmw/docs/doxygen/html/index.html.

    If you could share your configuration file, I might be able to offer other suggestions as well, but hopefully this helps get you started.

    Regards,

    Kristien