Quote:
|
Originally Posted by Tom Bottiglieri
Is there any info on the main program loop used in your library? (mean execution time, resources used.. etc..)
|
The traditional program loop is buried in the library. Timer 1 runs continously at 1ms intervals. Each interrupt it checks if there is master data that needs to be exchanged with the user processor and does it in the background. So there is no getdata/putdata that is exposed to the "user" program.
I will say that the overhead of the interrupt service routines are pretty high - about 54us of time to save and restore the context because of the need to save the mathdata and tempdata sections in the interrupt handler. But in spite of that, it seems to be able to handle the camera and gear-tooth sensors running at the same time.