AWR1843AOP: Detection at very close ranges

Hi,

Are you trying to detect static objects or moving objects?

Detection at a range of centimeters requires to takes several things into consideration

• Is the object stationary or moving
  • detection of stationary objects is more challenging and will be dependent on the Rx/Tx coupling in the first range bins
  • detection of moving objects is easier because there is not high leakage of the Rx/Tx coupling in the doppler bins neighbor of zero doppler bin

• Do we need to increase the range resolution by using a high resolution algorithm such as Zoom FFT?

• calibration must be performed: Range Bias and Rx Channel Gain/Offset Compensation 

Thank you

Cesar

Hello,

Our expectation is that the objects will likely be stationary and it will be the sensor that is moving. Is it fair to simplify that and say we care about moving objects?

Thanks

Yes,

Relative mouvement is what matters.

What chirp configuration are you using for your testing.

Please see the following FAQ that shows how to compute max range and range resolution

https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1050220/faq-computing-maximum-range-velocity-and-resolution-mmwave-system

Thank you

Cesar

Thanks for that resource.

I've tried a couple of different approaches to finding a chirp configuration that works for what I need. I've tried using the demo visualizer default configuration and adjusting the toggles to maximize range resolution. I've also tried modifying that default config file using the values for the USRR application in this link https://www.ti.com/solution/automotive-ultra-short-range-radar#referencedesigns. 

Are there any specifications you can share with me about the minimum range, and the precision and accuracy we can expect to achieve if the sensor is within about a meter of an object? 

Thanks for those suggestions, I have a couple of follow up questions. 

1) For the range bias calculation, the sdk instructions mention that the Demo console should print out some values that should be added to the cfg file for future use. But the console, at least for me, prints out unreadable values. Here is an excerpt "¢»­¦e{‰‚?•›Ï?·õ½"  do you know what might be causing this?

2)In the high accuracy lab from the industrial toolbox, one section mentions a tradeoff in latency and resolution between different devices. Is there a resource you can point me to to help understand how different datapath configurations and chirp profiles effect latency? What would the expected latency be for the AWR1843AOP if we were to use a zoom FFT similar to that lab? How does that compare to the typical?

Thanks

Thanks,

For question 1, I could not figure out a solution on the web-based version, but the downloaded version of the demo visualizer worked fine with the same configurations, so that solves my issue well enough. 

Will follow up if needed on question 2 in a new thread. 

Thanks