for_developers:timing_measurement
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| for_developers:timing_measurement [2016/10/24 07:55] – [Implementation] graf | for_developers:timing_measurement [2016/10/24 07:57] – [Using built in timer for measuring real time performance] graf | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Using built in timer for measuring real time performance | + | ====== Using Periodic Counter to measure Realtime Performance |
| ===== How the timer works ===== | ===== How the timer works ===== | ||
| Line 55: | Line 55: | ||
| - | ==== Explanation of the implementation ==== | + | If the executor has a small cycle time (less than 1 second) it is not advisable to update the log output each time. In the example the output is only updated after 1000 cycles. Depending on the cycle time, this number can be adjusted.\\ |
| - | If the executor has a small cycle time (less than 1 second) it is not advisable to update the log output each time. In the implementation of the code example the output is only updated after 1000 cycles. Depending on the cycle time, this number can be adjusted | + | |
| Line 7 defines which date should be written to the terminal output. Following options are available for //run// time and //period// time: | Line 7 defines which date should be written to the terminal output. Following options are available for //run// time and //period// time: | ||