• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 41 subscribers
  • Views 470 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TIDA-00480: How the latency is calculted/identified in the TIDA-00480?

Charkaoui Abdelmouneim
Prodigy 50 points
Part Number: TIDA-00480

Dear TI Expert, 

I was looking at the promo video of TIDA-00480 at http://www.ti.com/tool/TIDA-00480?DCMP=halls&HQS=HallEncoder#supportandcommunity 

Could you please tell me how TI quantifies this parameter "Latency"? or please redirect me to some TI App Notes that I can check out for more information regarding this topic. 

  • 0
    TI__Mastermind 21336 points
    Hi Charkaoui,

    I am not the person that worked on this design but I opened up the code from the design which can be found on the product page:

    www.ti.com/.../TIDA-00480

    The way the code operates is that first the watchdog is set-up, the outputs are set-up, and the 7-segments displays are initialized. Then the code goes into a large while loop that repeats indefinitely.

    Inside the big loop all the current values are read and then compared to the previous values, and lastly the display is updated. This repeats over and over again. My guess is that they measured how fast the loop could run and then set the latency based on that. This makes sense since the time between adjacent measurements would also be the maximum time that an event could go unnoticed.

    Lastly, this latency number will be completely dependent on the microcontroller used and how the code is set up. These inputs could be set to an interrupt or they could be polled. The faster the clock frequency of the micro, or the more efficiently it can execute the loop that monitors the input will lower the latency of the system.

    Please let us know if you have any more questions,

    John