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.

AWR1642: different frame config result in different result wehn PostProc in mmwave studio

Part Number: AWR1642

                                                                                                              (1) method 1 

                                                                                                                              (2)result of method 1

                                                                                                                                      fig 1

                                                                                                          (1)  method 2

                                                                                                                          (2) result of method 2 

                                                                                                                                         fig2 

 i am using AWR1642+TSW1400 to capture adc data.

When i post process adc data using mmwave studio , i find different result, seeing fig1 and fig2.

I ues 2 different way to config a frame. the frame has 128( same )chirp.

 method1 is fig1. And after postproc, i get 2D FFT Amplitude profile, Range-Angle plot,Detection & Angle estimation Results and so on.

But methor2, i can not get 2D FFT Amplitude profile and Range-Angle plot.... PostProcessing tells me "not enough chirps to perform..."

Where am i wrong? 

The method2 is a wrong config frame way?

  • Hi,

    I agree with you. I do not see any reason there should be a difference in terms of overall frame construction or number of frames between the two methods. So both methods should allow you to post post-process the resulting samples in the same manner.

    I will bring this up with the mmWave studio developers. It will probably take me a few days before I can get back to you with a reply.

    Thank you,
    Randy
  • Hi Rongjiang,

    After confirming with our mmwave studio designers I think I have an answer for you. When you construct a frame using chirp-profiles the post processing script does not assume that every chirp is identical in construction. There is a feature in the post-processing GUI meant to support cases like yours where the chirps are identical, or you just want to ignore differences in chirp to chirp construction. This is under ‘Miscellaneous options’-> ‘More miscellaneous’ tab. The option is called ‘multi-profile processing’. See excerpt below. 

    Selecting the option "Chirp configs with dissimilar profileID are processed separately" should let you process both frame constructions. 

    Please let me know if that answers all of your questions on this topic. 

    Thank you,

    Randy

  • thanks Randy.

    follow your steps in Miscellaneous options, i get the same result. But a few question i want to ask further to understand the principle.

    1/"When you construct a frame using chirp-profiles the post processing script does not assume that every chirp is identical in construction. "

    Does it mean the post processing script assmues every chirp is not identical in any construction case( including my case here) ?  the post processing script does not care whether the chirps are really identical or not?

    2/ "cases like yours where the chirps are identical, or you just want to ignore differences in chirp to chirp construction."

    I want to conform "ignore differences " 's meaning:

    The right understand i think :

    Here the chirps are identical in my case, but  the the post processing script takes the chirps differently. So "ignore differences " means telling  the the post processing script  ignores the difference which the script itself causes.

    Not this understanding:

     when chirps are different(different parameter/ differernt profile id or any way),  the post processing script porcesss takes all the chirps as one same parameter. The same parameter comes from one of all chirps.

    3/" Selecting the option "Chirp configs with dissimilar profileID are processed separately""

    According to question1, "the post processing script does not assume that every chirp is identical in construction" means even i config the chirps the same profileID in mmwave studio, the post processing script itself labels every chirp different feature when processing data ?

    4/ Using you steps in Miscellaneous options, i  get the same result.it seems the key point lies in how to set miscellaneous options. this relates to postprocess, not relates to config in mmwave studio.

    Now problem is :

    i use the programme in swra581-xWR1xxx ADC Raw Data Captur to process the adc data and encounter the same problem.

    the programme can get the plot for the case1 in fig1.

    But it can not get the plot for the case2 in fig2.

    How can i solve the problem? ADC dada is same, the key point is what is the difference before/after setting miscellaneous to the process programme? it relates to how to read and process the data.

     

    5/Now that "the post processing script does not assume that every chirp is identical in construction" , it means the post processing script knows how many chirps it processes or it knows how many chirps i config in the mmwave studio.

     Why the result only show 1chirp ( txEnable=1 0 0) in the right side of  postproc plot in the thread

    https://e2e.ti.com/support/sensor/mmwave_sensors/f/1023/t/718418 ?

    set miscellaneous options to ignore differences in chirp to chirp construction, how does postproc show me the two chirp in the right side of postproc plot.

    (I do not know whether I reply the post here is suitable or not.)

  • Sorry, revise some something in the last post.
    7/ i can plot the map following your steps for fig1 and fig2 in this thread.
    But the problem is still not OK in the thread e2e.ti.com/.../718418
    the mmave studio cannot still show me the right different chirps information for TDM MIMOframe.

    Maybe mmwave stuido can not show the right different chirps information , i can just ignore the bug.
    Am i right

    However, i suggest mmwave studio in the next version can add the function which mmwave studio can shows me the frame construction information and each chirp parameter infromation either in some mmwave studio tap or in the postproc windows.

    i think this additional function can re-confirm the configurated frame and chirp in the mmwave studio corresponds to what i want in my mind.
  • Hi Rongjiang,

    If I am understanding your response, it sounds like your initial problem was eliminated by following the suggestions in my first response, but you are now running into further issues.

    Please confirm that your initial problem was solved.

    I do see that the differences between this thread and thread e2e.ti.com/.../718418. I will follow-up on that other thread.

    Can you please open up a new thread to discuss the further issues you are encountering? To make this forum as useful as possible to everyone, we need to try to limit each thread to as narrow a topic set as possible.

    Thank you,
    Randy
  • Thanks Randy,i post a new thread and re-edit my question.
    e2e.ti.com/.../720655
  • Hi, Randy.

    for the problem the miscellaneous option, i find new further problem.

    And i have post it itn the thread e2e.ti.com/.../721535.

    Please follow-up.

    Thanks.

  • Also a more complete description for showing wrong information in the miscellaneous option, i post a thead:
    e2e.ti.com/.../721630