Common problems are:- wiring / circuit / buggy 'C' code- cheap IR receiver- batteries in remote control- not close enough to receiver (or too close)Never buy electronic components if you cannot get a data sheet for it. I am pretty sure there is a reason sellers do not provide the model number of a component.Regarding using a photo sensor to receive an IR signal: Yes its possible, but is likely to be a lower quality receiver than the one you already have. It will suffer from lots of inteference from ambient light and more. It is much cheaper just to buy a quality IR receiver.
Regarding the signals you are gettingCode: [Select]FD08F7DEE522C1FD08F7FFFFFFFFThe valid signals will be the ones with the last 2 hex bytes inverted.so '08' is the inverse of 'F7' aboveYou could use that trick to only recognise signals which pass this error check (or ignore ones that don't).In your case the FD is an ID code and should be the first HEX byte of every valid signal. If you check that the last 2 HEX bytes are inverted, you have a way of ensuring you only detect valid signals - even with this receiver.
Also the FFFFFFFF is just a repeat signal for the NEC protocol, if you keep a key pressed the code is sent once and then the repeat code is sent until you release the key..
ahh, it's possible the transmitter (on a remote control) is faulty, even if i press a key just briefly, i'm getting the 'FFFFFFFF' codes - loose button, or 'debouncing' ?
Quoteahh, it's possible the transmitter (on a remote control) is faulty, even if i press a key just briefly, i'm getting the 'FFFFFFFF' codes - loose button, or 'debouncing' ?No - that is normal, even with a short press you can get the FFFFFFFF repeat codes.
In most cases just ignore the FFFFFFFF codes in this NEC protocol, unless using VOL+/VOL- or brightness in the case of lights.