i am using AWR1642+TSW1400 to capture and process adc data.
Some kinds of configuration for the same frame results in different plot in the postproc, see fig1 and fig2 in the thread https://e2e.ti.com/support/sensor/mmwave_sensors/f/1023/t/718405
Thanks for Randy to tell me how to resolve the problem.
But I can not understand its principle. So I need to ask more to understand further.
Re-writhe Randy’s reply in that thread:
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.
According his reply, my questions are:
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 configuration case (not just for my 2 methods)?
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 :
In method 1 and method 2, the chirps are identical, but the post processing script adds the chirps some different labels. So "ignore differences " means telling the post processing script ignores the different labels which the script itself causes.
Not this understanding:
when chirps are different (different parameter/ differernt profile id or any way), the post processing script takes all the chirps as one chirp’s parameter.
3/" Selecting the option "Chirp configs with dissimilar profileID are processed separately""
It seems the mutli-profile processing’s 2 options:
“chirp configs are processed separately” is for similar profileID.
"Chirp configs with dissimilar profileID are processed separately" is for dissimilar profileID.
In my case, method 1 and method 2 are the same profileID. I think I should choose “chirp configs are processed separately”.
Why here I have to select “dissimilar profileID?
4/ Using Randy’s steps in Miscellaneous options, i get the same result.it seems the key point lies in how to set miscellaneous options. In other words, it relates to postprocess, not relates to config in mmwave studio.
Now problem is :
i use the matlab script in swra581-xWR1xxx ADC Raw Data Captur to process the adc data and encounter the same problem of method1 and method2.
the programme can get the plot for the method 1 in fig1.
But it can not get the plot for the method 2 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?
