Between the sync header and the actual code of the IR there is a signature stream to distinguish between the remotes and to discriminate the other remotes.

You have to carefully decode for the signature as well or your receiver will be picking IR from other remotes as well giving you non-sense data.

There is a slight difference to decode for the signature and to capture the button data for decision making.

The technique works equally good for RF serial data communication like the key chain RF transmitters (carrier of 350 MHz).

I agree with Jay, its only good for a couple of bytes to capture the data by sampling and not good for proper serial communication, as after a couple of bytes the sych will be out and you will get only the garbage.

Hi Daxx, any luck. I can send you the schematics for the IR decoder and full code in hex/bin for you. But its always half cooked. I have to cook it according to the type of remote.

Mind you there is a variety of IR remotes which change there data. When you press a button they give out a certain data but surprisingly on the next press of same button the data is different. Changing alternately. Does not make sense to me. what kind of format is it and why ??

For this you have to have an analyzer which could give you the snap shot of not just the bits but of the entire stream.

I have made the code for this analyzer also, its simple just from start of the IR stream start sampling the bit at a reasonable rate and keep storing the bits in your RAM. fix a reasonable limit of RAM also. Then send the entire RAM bit by bit (0 or 1) to your terminal. You will see the entire IR stream off your remote. If your remote is one of mutating type you will see and accordingly you can devise a decoding scheme.

Good Luck

Simon