Quote Originally Posted by prstein View Post
Hi Jerson,

there is a place for PBP interrupts. First, for beginners (and even people who, like me, use the absolute minimum of assembly) it is simple, straightforward, and easy.

[/CODE]

The main loop checks to see if USB (through an FTDI serial converter) is connected,

Incidentally, @ nop and @ sleep are the full extent of my assembly knowledge...8^)

I really end up not using interrupts very much at all (except to wake a sleeping PIC). What I do is look at the interrupt flags when convenient for the code. This keeps it nice and simple and controlled. Like I said before, I am a simple man.

I have a real good time kicking around on my little scooter; it certainly gets me there. If someone told me I had to use ASM ints I would have given up before I started.
Hey Paul

Sorry if I stepped on some toes here. In fact, I was seriously thinking of editiing my post, but, history has had me earlier too So, this is one boo-boo from me to stay here for posterity to see

Ok, I understand the use of ON INTERRUPT as you use it. My point was about driving home the real-time performance hit and how high the latencies can be. Waking a PIC from sleep? LoL You must be doing much more than that for sure.

I do not want my post to sound discouraging. Obviously, that will be the first thing a newbie will try when they want interrupts (because.... it is in the Manual)

I do not have a ferrari either and hope I could buy something better than my old faithful scooter which I have just put up for sale )


Just to make it clear, I learn new things out here almost everyday. Some of the folks who call themselves newbies and amateurs really astonish me with their coding style. If they only start giving back the little they know, I'm sure they will learn a lot more.

But, seriously, if you want good realtime performance out of a PIC, DT_ints is the way to go. One more plug for DT_ints

Cheers