Which chip do i use?

[tenaja]

Hmm. Im making lights dim. I would say the timing is pretty important on that and the hardware interrupt looks like it would work best.

What i want is serin2 to wait to serial data forever (or until it gets some data).

If RB0/INT goes low then i want to run a sub.

Does what you said mean that the data coming in from serin2 could be currupted?

Im not really sure what to do now. Ive been reading through those 2 links but they arnt making much sense to me and i cant relate them to what im doing

You can't use serin2 and hardware interrupts at the same time. The serin2 command is a software loop watching for the pin to toggle. If you interrupt out of that, then you lose bits or bytes. If you must watch RB0, then you also must use the hardware usart with a hserin command.

If you are using RB0 as an interrupt, then you could use a loop to watch for the uart buffer to be full. Using the usart gives you the advantage of a 1.9 byte buffer. I say 1.9 because you get one full byte, plus however long it takes to receive another byte and move it there before its overwritten.

You really should get a development board and play with the serial inputs and the interrupts to see how it works. If you don't do that, then you'll be depending on the board to write your code.

[The Master]

I dont want anyone to write all my code for me but a few examples would be nice.

So, I cant use serin2 like i normally would. The rest of that bit is a bit confusing. Are you saying that i should have a main loop that keeps an eye on serial data coming in and when it reaches a certain length then deal with it however i would if it had just come from serin2? Then in the background i should have RB0 interrupt the code and run the PWM sequence?

Im sorry im not getting it. There must be a few ppl sat at home shouting at their PCs "I cant believe he still doesnt understand!!!" lol. I have a feeling that eventually something will click and suddenly it will all seem really simple

[mackrackit]

"regular" interrupts will see the event happen be it an internal timer or change on a pin. Then it waits until the program is finished doing what ever then goes to the interrupt routine. This is the timing issue spoke of. That is where the clock programs come in for an explanation, there is only so much time between interrupt events.

If the program is in the middle of a serial command and an interrupt flag is set, the interrupt will not run until the serial routine is finished.

Here is a recent thread where an interrupt is being worked out.
http://www.picbasic.co.uk/forum/showthread.php?t=7490

[mister_e]

When dealing with interrupts and critical stuff... you don't want to use anything else than a REAL USART. Select a PIC with a EUSART/USART, use it and forget SERIN/SERIN2/DEBUG.