#Int_comp info

[Guard]

Hi,

MCU: PIC16f676 PCWH 3.217
Do you know if #int_comp is relative to comparator 1 or 2?

Thank

[libor]

Both.
You will have the interrupt if ANY of the two comparators gets triggered. In the ISR you can check the C1OUT and C2OUT registers to know which comparator caused the interrupt.
The generated interrupt is also independent of the direction of the level change on the comparators. You will get an interrupt in BOTH directions when the comparator output changes. It is the 1 or 0 state of the C1OUT (C2OUT) that shows you the actual state of the comparator output.
So there are 4 states when using both comparators that you should serve in an interrupt service routine.

[Mark]

Note that some of the PICs actually have a separate interrupt for the other comparator. Look at the datasheet. If the PIC only has one interrupt, then #int_comp is it. If it has 2, then the other one is #int_comp2.

[Guard]

Hi,
The PIC16f676 has two flags int for comparators, C1IF and C2IF.
I wrote this code:
//PCWH 3.217
/*
#int_COMP or #int_COMP2
void isr(void)
{

//code

}
but compiler return this errors" Invalid Pre-Processor directive"
may be it has different name?
Thank

[Ttelmah]

[Guard]

Hi.
Sorry , but the target isn't PIC16F676 but PIC16C781.
Where is the case setting ( or case sensitive?) option in the project ?I do use mplab always.
INT_COMP in the header file not exists. I changed name from isr() to isr_comparator(), but it hasn't effect
Thank

[libor]

You can check with chipedt.exe the actual PICs type config data to see what interrupts are actually allowed to be programmed. (and its syntax also) Be sure not to mess up the config file.

[Mark]

Looks like CCS screwed that one up.

[Guard]

[Guard]

Hi,
PCW 3.218 - Mplab 6.60
Target: PIC16c781
Do you know which is the option in device edit, for #int_comp2 ( comparator 2)??
Thank