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.

IWR6843AOPEVM: Resolution vs Accuracy in range, velocity, and azimuth/elevation

Part Number: IWR6843AOPEVM

Hello,

I was curious to learn more about the relationship between resolution and accuracy and how the chirp parameters can influence accuracy. I'll split this up in three parts: range, velocity, and azimuth/elevation. I realize this is long, but I think there is some fundamental understanding here which I feel is not clear regarding the different between resolution and accuracy and how this is effected in particular configurations.

I would both be interested in explanations as well as pointers to relevant literature. If the description is not clear please say so.

Range

  • Range resolution is given by c / B, so this is directly influence by the chirp design
    • speed of light / bandwidth
  • How does chirp design then play into the accuracy? Hypothetically if we have two objects near one another, if they can't be resolved then one would think the detection would be somewhere in the middle of their actual ranges. If this is the case this causes some discrepancy between the "measured range" and the "actual range".
    • E.g. two objects at 1.1 and 1.2 meters range, if we suppose the range resolution is 0.2m, then what is measured for these two objects, 1.15m?
    • This site has some comments on how range accuracy can be written as a function of the resolution
      • range accuracy = range resolution / sqrt(2 * SNR)

Velocity

  • Velocity resolution is given by lambda / 2T_F
    • wavelength / 2 times frame time
    • where frame time is chirp duration * num chirps
  • Question very similar to range. How is velocity accuracy influenced by resolution/chirp parameters that influence resolution?
    • As an example, take the following image from TI's "The fundamentals of millimeter wave radar sensors"
      • Suppose the radar is moving left and obj1 and obj2 are stationary. The relative velocity of obj1 and obj2 are both due to the radar moving left. If both objects have the same angle to the radar, their doppler should also be the same. These two object should be distinguishable by angle of arrival, but their range and doppler will be the same, how will this be handled?
      • Suppose the radar is moving left and obj1 and obj2 are stationary. Suppose now they have slightly different angles to the radar, such that their dopplers are different. Let's consider this in 2D, if one is at +30 deg and the other at -45deg and the radar moves along 0 deg at 1m/s, their radial speeds will be ~0.86 and ~0.71. How will this be measured? They're at the same distance so range isn't different, and it is definitely possible that velocity resolution is >0.15m/s, but they are 75deg different. Will this result in 2 reflection with range/velocity accuracy to FFT bin width, or will they somehow be merged since velocity, while different, is not actually resolvable?
        • Since all radial speed here is a result of our own motion, there is a ground truth value for any points direction, can we say anything about the accuracy in a case like this?

Azimuth/Elevation

I figure this is one of the simplest of the bunch, given that (as far as I know) neither resolution nor accuracy are affected by chirp.

  • Resolution, according to the a TI intro to mmwave radar videos, is limited by the antenna configuration
  • Accuracy should be, in part, limited by the number of FFT bins (64). E.g. 120 deg FOV / 64 bins results in FFT bin width of 1.875 degrees
  • Hi,

    I can provide a more detailed response on Monday if needed, but I can provide some quick insights and reading for you to look at over the weekend.

    For Azimuth/Elevation

    This article discusses antenna design and improving angular resolution: https://www.ti.com/lit/an/swra554a/swra554a.pdf?ts=1686343783117&ref_url=https%253A%252F%252Fconfluence.itg.ti.com%252F 

    The accuracy can be dependent on some factors such as angle of arrival. Check out this video here for more info: https://www.ti.com/video/5415560018001 

    For Velocity

    https://www.ti.com/video/5415528988001

    For Range

    https://www.ti.com/video/5415203482001

    Please take a look at the Sensing Estimator: https://dev.ti.com/gallery/view/mmwave/mmWaveSensingEstimator/ to understand how different chirp parameters affect the performance of the system.

    Also take a look at our people counting Detection Layer tuning guide for more info on how other parameters can configure the devices performance (keep in mind most of this guide is for the software written for the people counting processing chain, and does not explicitly pertain to the fundamentals of mmWave Radar. Still a good reference, however: https://dev.ti.com/tirex/explore/node?a=1AslXXD__1.10.00.13&node=A__AIQPG9x7K34A8l4ZELgznA__radar_toolbox__1AslXXD__1.10.00.13 

    Please take a look at these resources and if you have any further questions let us know. I can elaborate on your first couple of questions on Monday.

    Regards,

    Tim

  • Hi Tim,

    Thanks for getting back to me, I'll have to review the MIMO radar document in more detail before commenting on it. I have read it before but it's evading my memory a bit now.

    Regarding range and velocity, the videos do not answer the question: which is on accuracy which is not the same. This is demonstrated by the radartutorial.eu link I mentioned in the original post, where they derive a different expression for range resolution and accuracy. One can see they are related, but not equivalent.

    I'll try to reduce the noise and condense this into a simpler case study to ponder. Let us consider the velocity measurement of the following situation
    We can split this in two situations, given v1 and v2 are not necessarily equal in value. The pertinent question in each situation is essentially: How do we evaluate the accuracy of the velocity measurements?

    1. Suppose v1 and v2 are able to be resolved, this means each has a distinct peak in the FFT. Here a potential answer to the question could be that the accuracy is limited by the FFT bin width, I would like to hear your thoughts on this.
    2. Suppose v1 and v2 are not able to be resolved, this means the FFT has one peak. A number of questions arise here
      1. Say v1 is 1m/s and v2 is 1.5m/s, is it reasonable to assume the peak will be at 1.25? Can we even generally say where the one "false" peak should be?
      2. How can we evaluate the velocity estimate accuracy then? I would guess it should be bounded by +- one half the velocity resolution?
      3. Is it not possible to "resolve" them by their azimuth/elevation and backtrack for velocity?

    Generally. what can we say about the velocity measurement accuracy? Hopefully it's not +- half the velocity resolution, as I believe the bin width will quite often be reasonably lower. Also, it would be slightly surprising given the relationship between range resolution and accuracy.

  • Hi,

    1. Yes, the accuracy is limited by the FFT bin width.

    2. 

    a. It's reasonable to assume a peak between 1-1.5, but we can't definitively say it would be at 1.25 because the objects could have different reflectivity/size etc.

    b. Yes, we can essentially think of it as being bounded by the +- 1/2 velocity resolution. Without doing extra processing like doing a Zoom FFT, we can't say more than this.

    c. It is possible to do this. This is what our people counting processing chain does. You can take a look at it and find more information about that in our radar toolbox. 

    Here is a link to the fundamentals of radar document which goes into some more detail from the videos sent earlier.

    https://www.ti.com/lit/wp/spyy005a/spyy005a.pdf?ts=1686584590865&ref_url=https%253A%252F%252Fwww.google.com%252F 

    Also please keep in mind this forum is intended to be used primarily as debugging help with TI devices. I encourage you to work with the device/demos/code that we provide and ask specific questions about them as you go.

    Regards,

    Tim

  • Sorry if it was unclear, all my questions are grounded in the out of box demo pipeline and how measurements from this can be interpreted.

    Here is a link to the fundamentals of radar document which goes into some more detail from the videos sent earlier.

    https://www.ti.com/lit/wp/spyy005a/spyy005a.pdf?ts=1686584590865&ref_url=https%253A%252F%252Fwww.google.com%252F 

    As with the videos this only handles resolution.



    To conclude this thread, is there a better metric for the "accuracy" of a velocity measurement? +- half the resolution seems like a conservative approximation.

  • Hi,

    There is not a particularly better metric for measuring accuracy.

    I am closing this thread for now. But please do return with questions if you have any issues once you start working with our devices.

    Regards,

    Tim