for_developers:timing_measurement
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| for_developers:timing_measurement [2016/08/15 14:01] – gehrig | for_developers:timing_measurement [2016/08/15 16:43] – [Accuracy of the measurement] gehrig | ||
|---|---|---|---|
| Line 9: | Line 9: | ||
| ===== Accuracy of the measurement ===== | ===== Accuracy of the measurement ===== | ||
| - | This measurement provides only statistical data over 1000 (or 100) cycles at a time and not for each iteration. To measure jitter for each iteration use the //signalProbeBlock//. | + | This measurement provides only statistical data over 1000 (or 100) cycles at a time and not for each iteration. To measure jitter for each iteration use the [[: |
| It is possible to measure a 15% CPU load and over 300us run time per 1ms period. This indicates, that the run time measurement is not accurate. | It is possible to measure a 15% CPU load and over 300us run time per 1ms period. This indicates, that the run time measurement is not accurate. | ||