• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 32 subscribers
  • Views 1019 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.

AWR1642: Relationship between Active Frame Time and Measurement Rate

William List
Expert 6985 points
Part Number: AWR1642
Other Parts Discussed in Thread: AWR1443

Hi, I would like to understand how the Measurement Rate Scene Parameter is validated by the mmWave Sensing Estimator. It seems to share a relationship with the Active Frame Time, but does it rely also on other factors?

In an example I put together using the estimator, the Active Frame Time (ms) is 15.76. The Measurement Rate I selected is 32, which the tool says is too high. 32 frames would be a total of 504.32 ms, which is just over 50% duty cycle. The tool says that a measurement rate of 31 is acceptable, which is 488.56 ms. Is there some minimum inter-frame spacing that must be honored? Other constraints that I am not factoring in? Thanks.

Bill

  • 0
    TI__Guru 58035 points
    Hello Bill,
    Could you provide the exact snapshot of the configuration you are trying on the sensing estimator ?

    regards,
    Vivek
  • 0 in reply to Vivek Dham
    TI__Expert 6985 points

    Hi Vivek, I lost my previous configuration, but here is another example with AWR1443 instead. In this case, the Active Frame Time x Measurement Rate comes to 503.37 ms. If I choose 118 as the Rate, the configuration checks out. There seems to be a threshold of 500 ms that the tool has from the experiments I've done so far. 

  • 0 in reply to William List
    TI__Mastermind 23725 points
    Hi Bill,

    The Active Frame Time value constraints the update rate. It keeps twice as much time between two consecutive (measurement) updates.
    For Active Frame Time of 4.23ms and time between two updates should be 8.5ms or higher, this should constrain the measurement rate of 117Hz or slower.

    Please try the above values. We will add a not the user's guide and update the error message.

    Thank you,
    Vaibhav