Re: Pulse Gen

Jon E wrote:

>In this case, profiling it for time spent in a particular section of
>code may not really spot the problem. In this case, the resolution
>of the pulse timing is what is critical, not necessarily the amount
>of CPU resources it takes to do that part.

Exactly right. Good point!

>I can easily see an interrupt-driven, "pulse or no pulse this tick"
>type of routine that would NOT take much CPU resources, but would
>give very poor step pulse timing.
>Jon

Maybe! Depends on the resolution of the "this tick". As I have
pointed out (in past posts), and as Art F is doing, the "tick" of the
pentium RDTSC instruction IS the processor clock speed! Could be as
high as 1GIGahertz! And 'typical' is prob'ly 233+ mhz.

Of course, the rest of the system (port access/write timing) will
come into play, but Art IS doing it and reporting GREAT results!

Hope this helps.

Ballendo