Marks256
New Member
What would be the best way to communicate via IR (infrared) between two microcontrollers(basic stamps, or a computer)? I am talking more along the software side of things...
For those of you that need to know exactly what i am doing; I have an old 486 Compaq Laptop, and a tower server. I want to connect the two via infrared for simple data transfer (text files, maybe some data from the internet)
First off, how should the signal be sent? if pulses are sent out, wouldn't the room lighting "confuse" the receiver? I really know nothing about wireless data transfer, so this is new to me.
Second, how should the receiver algorithm be setup? I am guessing that there would be quite a few errors in the transmission(s) due to random sources of infrared, so how should the algorithm be made to compensate for these errors?
Also, what about CPU processing power? I don't like the idea of the CPU being bogged down continuously searching for a signal that may not be there for a long time... I am not worried about the laptop, for it will be running MS-DOS, but the server will be running windows (xp or 2k, probably xp), so the server can not be bogged down too much (i guess the algorithm could be put into a thread, just so it doesn't kill the CPU)
if none of this makes sense right now, i am sorry.
It is late, i am tired, and i am sure there are a few things in this text that do not make sense, so, bare with me, i will try to fix it up a bit tomorrow. 
For those of you that need to know exactly what i am doing; I have an old 486 Compaq Laptop, and a tower server. I want to connect the two via infrared for simple data transfer (text files, maybe some data from the internet)
First off, how should the signal be sent? if pulses are sent out, wouldn't the room lighting "confuse" the receiver? I really know nothing about wireless data transfer, so this is new to me.
Second, how should the receiver algorithm be setup? I am guessing that there would be quite a few errors in the transmission(s) due to random sources of infrared, so how should the algorithm be made to compensate for these errors?
Also, what about CPU processing power? I don't like the idea of the CPU being bogged down continuously searching for a signal that may not be there for a long time... I am not worried about the laptop, for it will be running MS-DOS, but the server will be running windows (xp or 2k, probably xp), so the server can not be bogged down too much (i guess the algorithm could be put into a thread, just so it doesn't kill the CPU)
if none of this makes sense right now, i am sorry.