• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 1870 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.

Original question:

AWR1243BOOST: 8RX MIMO configuration with radarstudio

IWR1443BOOST: MIMO configuration with radarstudio and data collection

WEIHUA JIANG
Prodigy 190 points
Part Number: IWR1443BOOST
Other Parts Discussed in Thread: IWR1443

Hi,

I am now trying to get the raw data about MIMO system using IWR1443. Actually, with radar studio, I can get the bin format data  and matlab runtime can plot the result figures.

But I notice that the Azimuth-Range heatmap in 'mmWave Demo Visualizer' is totally different with the result shown in radar studio 'matlab runtime', when the parameter is the same in this two conditions. ( the parameter setting refers to this question 'https://e2e.ti.com/support/sensor/mmwave_sensors/f/1023/t/624663?tisearch=e2e-quicksearch&keymatch=mimo'

I have tried the 1*4 and 2*4(TDM) MIMO, but it still has the problems. I think it may have the problem in parameters setting or the difference of data processing in 'mmWave Demo Visualizer' and radar studio 'matlab runtime' , but I can not figure it out. So could you help me, and tell me what caused it? 

Thanks,

Weihua

  • 0
    TI__Mastermind 21295 points
    Hello Weihua,

    Could you give more detail about the differences you are seeing between the Azimuth-Range heatmap in 'mmWave Demo Visualizer' and the one in mmWave/Radar Studio? Could you send a picture of each plot while using the exact same chirp configuration and scene?

    Regards,
    John
  • 0 in reply to JohnH
    Prodigy 190 points
    The above is the Radar studio parameter setting, result and Visualizer parameter setting, result figures about 1*4 MIMO system. Could you help me to check it out? Further, do you have the guide examples which I can follow?
  • 0 in reply to WEIHUA JIANG
    TI__Mastermind 21295 points
    If the device configuration and scene are identical then the main difference in the plots may be the scaling on the plot itself.

    You can look through the mmWave Demo Visualizer console (or save the .cfg file to your hard drive with the button near the bottom) to see the actual CLI commands sent to the device to configure it. The CLI command format is described in the the mmWave SDK user guide. This would allow you to compare the actual chirp configuration parameters used by the mmWave Demo Visualizer to the parameters setup in mmWave Studio.

    Please mark the thread as answered if your question is resolved or reply if more support is required.

    Regards,
    John
  • 0 in reply to JohnH
    Prodigy 190 points

    Hi,

    According to your reply, I have already checked the parameters from the Visualizer .cfg file. But the results are always different between Visualizer and Studio. Does it have the effect on data collection when the data  need to go through TSW1400, compare to directly process in IWR1443. Besides, do you have the examples which I can follow(have the comparision beween Visualizer and Studio)?

    Thanks,

    Weihua

  • 0 in reply to WEIHUA JIANG
    TI__Mastermind 21295 points

    The raw data is the same regardless if it is collected via the TSW1400 or used directly by the post-processing on the IWR1443.  There is no published example of a comparison between the Azimuth-Range plots on the mmWave Demo Visualizer and mmWave Studio.

    After contacting the designers of both tools the explanation for difference between the plots you sent seems to be in the plot scaling.  The mmWave Demo Visualizer plots the absolute value of the Azimuth FFT whereas mmWave Studio plots the logarithmic value (20*log10()).

    Regards,

    John