TIDEP-01012: Processor SDK RADAR usecases(MIMO and TXBF) cannot detect beyond 15 meters

Hi,

We need your help to understand some details of your issue.

Did you try to capture raw data with the imaging kit?

Is this use case working. Or do you see the same behavior?

Using the Proc SDK is a completely different use case where the demo code runs on the target.

Thank you

Cesar

Hi, Cesar. 

I'm not sure I understand what do you mean by capturing raw data with the imaging kit. However, if you're talking about capturing raw data from mmWave Studio, then yes we did capture some scenarios with that. The output didn't make much sense. 

I put 2 corner reflectors at boresight at 20m and 40m and using the MATLAB script provided for MIMO post-processing, this is what I see as output:

The parameters we used are shown below:

We also tried the OOB settings you provided on the other forum posts for MIMO but the range readings are all messed up as well on that one. 

Asher,

As a starting point would be good to first solve the issue where the data is captured from the cascade radar setup and then process the raw data offline using PC. Once you have confidence on the data being processed by the PC, the next step is to recreate the same scenario with the TDA2 processing the raw data and then seeing if you are able to proceed.

Thanks and Regards

Piyali

Piyali,

I looked around in the source code and hardcoded the chirp parameters in the file "chains_common_cascade_ar12xx_config_mimo.c". Putting the chirp parameters provided by Cesar for MRR in this file allowed the Radar to see up to 15 meters on range doppler heatmap ONLY. This would suggest that choosing any profile in the script doesn't make a difference and MATLAB is unable to write or overwrite chirp parameters from the script. 

Is there a way to establish trust after using the script? I mean, can we print out the current chirp parameters as well as the CFAR parameters and verify that those parameters are the ones we're using? 

I have stopped believing that the serial terminal changes the CFAR parameters effectively and I'll try to hardcode them as well. Can we be sure that the serial terminal doesn't show similar behaviour as MATLAB?

Hi Asher,

We provide a GUI tool (mmWave Studio) for mmWave product to configure the device and capture the raw ADC data to PC using TIDEP-01012 hardware (AWR1243Px4 + TDA2x).

You can download the mmWave Studio tool from this link

http://software-dl.ti.com/ra-processors/esd/MMWAVE-STUDIO/latest/index_FDS.html

Please go over the user guide (docs\mmwave_studio_cascade_user_guide.pdf) available in this package. This way you can configure the required setting to each of the AWR devices and capture the ADC data then copy it to PC, further do the processing. This tool provides the basic tool to do the post-processing of this data.

Regards,

Jitendra

Asher Farooqui said:

Hi, Cesar. 

I'm not sure I understand what do you mean by capturing raw data with the imaging kit. However, if you're talking about capturing raw data from mmWave Studio, then yes we did capture some scenarios with that. The output didn't make much sense. 

I put 2 corner reflectors at boresight at 20m and 40m and using the MATLAB script provided for MIMO post-processing, this is what I see as output:

The parameters we used are shown below:

We also tried the OOB settings you provided on the other forum posts for MIMO but the range readings are all messed up as well on that one. 

Hi Jitendra, This is my output from mmWave studio. 

Hi Asher,

If you have captured the raw adc data from mmWave Studio, then please share the LUA script which we can try at our end.

As we have tried in the past to look at a much longer distances using the Cascade board.

Regards,

Jitendra

Hello Jitendra,

Here are my cascade_capture and Cascade_configuration .lua files

Cascade_Configuration_MIMO.zip

The Matlab script we're using is located here 

C:\ti\mmwave_studio_02_01_00_00\mmWaveStudio\MatlabExamples\4chip_cascade_MIMO_example\main\cascade

Please share your results and the test conditions so that we can do the same on our end and compare the results. 

Thank you. 

Hi Asher, 

Based on our call, we need to discuss how exactly to modify the MIMO example processing. I am working on setting up an example for this. 

Thank you,

-Randy

Hi, Randy. 
Thank you for the call as well as making this example for us. We're looking forward to it.