IR remote control...
Wagner Lipnharski email (remove spam text)
Robert E. Griffith wrote:
> This was alluded to by others, but to put it in simple terms... If
> you are not constantly sending IR data to the models, (bandwidth is
> not tight), but rather are sending short commands every once in a
> while (like turn, stop, go, etc...), then you can just include a
> device address with each IR command. All receivers listen to every
> command, but respond only to the ones with the address set to their
> own address. If two transmitters transmit a command at the same
> time, they will interfere with each other and neither will be
> received. The operator would just resend the command.
> Most consumer IR protocols dedicate some bits to identify the device
> so that, for example, your DVD remote does not control your VCR.
... except if transmitter A starts to send the packet, receiver A decodes
its own address and starts to receive. In middle of the A data frame,
transmitter B starts to transmit and garble all A reception...
There is a simple (?) way, collision detection, a transmitter can only
start to send IR if there is no IR being transmitted. Even so, there is a
chance of collision, it is not that difficult two operators press the key
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads
See also: www.piclist.com/techref/io/irs.htm?key=ir
You must be a member of the
piclist mailing list
(not only a www.piclist.com member) to post to the