Jeff Epler wrote: > Parameters like these > 32769 s32 RO 0 lowpass.0.time > 32769 s32 RW 0 lowpass.0.tmax > allow you to scope the execution time of HAL functions.0'. They exist > for all HAL components, not just those created with 'comp'. They're > automatically created by hal for each function. "time" is the number of > CPU cycles it took to execute that function the last time it was > created, and "tmax" is the maximum number of CPU cycles it took to > execute that function. "tmax" is a writable pin so that a user can > manually set it to 0 to get rid of the effects of first-time > initialization on the function's execution time. > Hmmm, cool! I wonder, though, for many of the simpler HAL functions, if aquiring the data and loading these parameters actually takes more time than the HAL component itself! It obviously requires a kernel function, while most of these components are just a single line of C code.
I'll have to check these out, a lot easier than hooking up a logic analyzer to time the execution of the PID. Jon ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
