Bravo Rauf, I wish you could have affected the IrDA standard; they made theirs much too complicated.

CAVEATS:
========
A quick note though. There are a few things different about IR transmission that should be taken into account.
DROPOUTS:
=========
Unlike a soldered trace connection that we use in typical IIC/I2C links, light links can drop out and be blocked.
Simple IR communications links tend to rely upon a packetized system like the old Z-Modem family of protocols.
Until/if I switch my product to IrDA, I'm using a light link with one of the old modem protocols.

SAVE THE BATTERY:
=================
Another thing about IR communications is the duty cycle of the transmission. While our initial tendency is to drive the IR transceiver directly off the TXD/RXD signal timings... the "ON" time is excessive for the information transfer (even if you invert the MARK/SPACE).

Remember that while your 8051 may run off of wall-power, it may need to communicate with handheld device in the same prototcol.

Laptop and other battery powered designs have used this knowledge for a long time. Rather than illuminating the IR signal for a bit time, they pulse it and thereby save the power/illumination energy.

You can find IR "ENCODER/DECODER" to do this for you. I use one from a company that took a TI low power, low pin micro and programmed it thus.

-Jay C. Box