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.
Hi
In the below image, used cfg:PresenceDetect.cfg
MAx Velocity is calculated as 17.009
Vel Resolution is given as (2* Max Vel)/Num of chirps loops
This is normal mode as numOfBurstsInFrame=1 and numOfChirpsInBurst=8
Which gives um of chirps loops=8*1=8
Vel Resolution comes out as=(2*17.009)/8=4.252 as shown below.
For another config:TrackingClassification_HighBw_4Ant.cfg
MAx Velocity is calculated as 6.133
Vel Resolution is given as (2* Max Vel)/Num of chirps loops
This is burstl mode as numOfBurstsInFrame=64 and numOfChirpsInBurst=2
Which gives um of chirps loops=64*2=128
Vel Resolution comes out as=(2*6.133)/128=0.095 not matching
But if we use 64, chrips per frame per tx antenna then its matching
Why this ambiguity is there in the two modes?
Hi,
I am still looking into this. Allow me to get back to you next Monday. Thanks for your patience.
Regards,
Luke
By looking at the source for the calculator I see this:
Here, sdkVersion == '1' when using the IWRL6432. Though the tooltip is not properly documenting this, and I will make sure that gets corrected, you can see that when using burst mode, you divide by the number of bursts in a frame rather than the number of chirp loops.
Regards,
Luke
Hi Luke
Thanks for the information.
Can you tell which src file is this?
Yes. The easiest method is to view all the source from inspecting element on the application in your browser:
As a second option, you can download the application to your local machine from dev.ti.com's gallery: Search results for "Sensing Estimator" · Gallery
Regards,
Luke