Hi Victor,
VK> GW> If that is the case why wait in the timer interrupt? Just exit the
VK> GW> timer interrupt handler and deal with it next time round...
VK>Ok I think this thread should stop pretty soon, two reasons: 1. It's off
VK>topic, and 2. I have already solved the problem by
VK>populating the main code with calls to the routine that was
VK>previously the timer ISR, and timed too.
Fair enough.
VK>The reason for waiting in the ISR and not skipping until
VK>the next one was because the next one occured 55ms later
VK>which was too much of a delay to be acceptable.
There are other ways round that. Reprogram the timer to run at twice the
rate, or even four times, and only chain on to the original interrupt
handler at the appropriate rate (every 2 or four interrupts).
VK>Thanks to everyone who has helped with this, took me a
VK>while to see that there really was a more reliable(albeit
VK>not so nice) way of doing it.
I'm glad you have found an alternative way of implementing the code that
removes the problems of the original method.
George
 * SLMR 2.1a * Wastebasket: Something to throw things near.
--- Maximus/2 3.01
---------------