AWR1843: Increase max unambiguous velocity in MRR

By changing the profile configuration you can configure max range, max velocity and resolutions. You can use trial and error using the mmwave sensing estimator 2nd tab or calculate the values using the provided documents 

https://dev.ti.com/gallery/view/mmwave/mmWaveSensingEstimator

C:\ti\mmwave_sdk_03_06_00_00-LTS\docs\mmwave_sdk_user_guide.pdf section Configuration (.cfg) File Format

https://www.tij.co.jp/jp/lit/wp/spyy005a/spyy005a.pdf

Hi Cesar,

We're trying to solve for a bike's rear application wherein we're only concerned with -ve velocities, max range about 80m. We've made changes in the dss for the same, but the issue is that we're seeing ghost detections. I was suspecting that maybe +ve velocities are getting wrapped around and getting reflected as -ve velocities, hence the question on whether we can do away with disambiguation altogether, and if we can take the max velocity to say around 80kmph. 

Another workaround we've tried today is to increase the SNR threshold and that has probably helped but too early to conclude.

Q1: in the disambiguateVel function, if a correct mapping between the two doppler FFTs is not found then the fast chirp velocity is assumed to be correct. Do you have any data points on typically what percentage scenarios this happens (velocity disambiguation is inconclusive).

Q2: is there a higher level tracking based disambiguate function implemented in another lab? It would be great if you can give some pointers. 

Vikas

1. We do not have any percentage figures

2. We have awrl1432 bike bsd binaries on TI developer resource explorer, source code can be provided with NDA

https://dev.ti.com/tirex/explore/node?node=A__AFvj3IEqZ4wAckSgtgVXLg__radar_toolbox__1AslXXD__LATEST

Thanks Zohra. Pls guide on how do we go about the NDA.

Please contact your regional field engineer 

Hi

I've initiated the process for the NDA. In the meanwhile, can you pls help me with the following info for the MRR lab:

• I'm using only SUBFRAME_CONF_MRR and max range 80m in my mrr_config_const.h file. If I want to change the chirp parameters, do I only need to make them in mrr_config_chirp_design_MRR80.h files in the mss and dss folders, and they will work, or do I need to make changes elsewhere too?
• Is there a limit on the PROFILE_MRR_FREQ_SLOPE_VAL for AWR1843 device? As asked earlier - I'm looking to increase the max unambiguous velocity in fast chirp subframe.

Which demo are you using? Is it the Medium Range Radar or MRR beamsteering?

https://dev.ti.com/tirex/explore/node?node=A__ACCD.YxtaQpnE9Sm3Vf20g__radar_toolbox__1AslXXD__LATEST

Hi Zohra,

Thanks for pointing to the user guide, we've already gone through it and wanted to confirm with you. It will be great if you can help with the two specific questions in my previous post. We're exploring both MRR and MRR Beamsteering.