The code works fine, now I need to manage a bit the code flow to keep everything working, since the interrupts are kind of messing up the code.
By the way, I've missed that in the later version i made the "results" an array too. Don't know if it is much useful - I hardly can imagine that 2 interrupt handlers run simultaneously - but as for me it's a bit more clear when every pin has its own "results" var.
Speaking about interrupts, I believe it's more efficient to use them rather then checking in loop (as in IRremote's demo), because we work with events here, so no need to disturb the processor while events not happening.
I'm tryngo to blink an LED according to the status of the receiver, but their blink is really low.
Do you have any idea of why is this happening?
What status is it? If you mean "slow", and if you try to blink every time getIRcode is executed, maybe, just maybe, the board doesn't always manage to blink the LED - the interrupt handler must always work very quick. You can change some variable in the handler, then check it in the main loop and turn the LED on, respectively.
For sure I'm more newbie than you!
Well, programming is my job (although not C language), but electronic - aah, it's terra incognita.
By the way, what Arduino do you use? I'm trying to understand if the 3.3V/8MHz board is suitable to send and receive IR codes. I've asked about it in "Project guidance", but got no answer. Maybe nobody has tried, or maybe my english is a bit poor
Generally, for what purposes the 8MHz duino is not quick enough?