Bruce Partridge wrote :

> I have other things going on in the isr.

I think that's one of your problems, having to much "going on"
in your ISR.

As have been said before, you can not get things done faster by
moving code into the ISR, you just make things harder and you
probably just lock up the CPU on a single task for a to long time.

Using short/fast ISR's, you have less chance having *other*
interrupts beeing delayed for to long.

> It reads sensors, fires a
> solenoid,  shows several different displays.  Some of the
> displays have to flash to show error conditions.  Its not an
> impossible solution, but its not great either.


Now, I *have* noticed that you code in C, and my experiences
are from using ASM, so perhaps I'd better quit this thread here...

Regards
Jan-Erik.

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body