stevennoppe:
But also no luck. What am I overseeing?
You are going in the correct direction but you need to post a complete program.
...R
PS. "overseeing" is what a supervisor does when he is checking the work of subordinates. "Overlooking" is what I do when I don't notice a mistake in my program - almost the opposite meaning
I believe you are using the wrong Pin change interrupt vector. For pins 10 and 11 you need PCINT0_vect (see Nick Gammon's Tutorial - easier to make sense of than the Atemga 328 datasheet)
Also, activity on either pin will trigger the same interrupt vector so the code in your ISR needs to use digitalRead() to figure out which pin caused the interrupt.
if you have the option it might be easier to use (say) pin 10 on PCINT0 and one of the pins (0 to 7) that use PCINT2. That way each pin would trigger a separate interrupt.
While it is not directly revelant I would put the code that you have in (for example) doEncoder2A() directly into the ISR rather than wasting CPU cycles calling that function from the ISR. (By the way I do not mean that the existing code is what you need).
Robin2:
You are going in the correct direction but you need to post a complete program.
...R
PS. "overseeing" is what a supervisor does when he is checking the work of subordinates. "Overlooking" is what I do when I don't notice a mistake in my program - almost the opposite meaning