 | | RE: IR Problems
|
|
Are you sure your problem isn't interference? How did you "lock out" the RCS 1.0 from receiving (and responding) to the direct commands? You have two RCXs turned on and sending direct commands from the PC. They will both try to respond to the (...) (18 years ago, 2-Apr-07, to lugnet.robotics.rcx)
|
| |
| | Re: IR Problems
|
|
(...) Thanks for your reply. I had to return the 1.0 RCX and motor back to school today. Those things are like gold. The 1.0 faces the 2.0 and is not in direct line of sight of the tower. The 1.0 is just to the side of the tower. I think my problem (...) (18 years ago, 2-Apr-07, to lugnet.robotics.rcx)
|
| |
| | RE: IR Problems
|
|
RCX IR does not require direct line of sight. All sorts of reflections will work. Especially if you're in a "smallish" (bedroom, home office) room. The RCX firmware always has the IR turned off. "Wait for mail" and "send mail" is just a higher (...) (18 years ago, 2-Apr-07, to lugnet.robotics.rcx)
|
| |
| | RE: IR Problems
|
|
IR communication is no where near the reliability like a tcp/ip. You can easily lose a message ... so program must be either extremely simple one way communication. The sender should be programmed to handle message loss. What I had the kids done was (...) (18 years ago, 2-Apr-07, to lugnet.robotics.rcx)
|
| |
| | RE: IR Problems
|
|
Elizabeth is quite right. It's easy to get collisions on the IR "bus" if two devices are sending (or replying) simultaneously. What I've done in the past with two RCXs is define one RCX as primary that is periodically (every 100 to 250 milliseconds (...) (18 years ago, 2-Apr-07, to lugnet.robotics.rcx)
|
| |
| | Re: IR Problems
|
|
(...) Thank you for the excellent information concerning communication with more than one RCX. Last night in a dream I realized that I could just bypass communication placing two push button sensors where needed driving the additional RCX. The (...) (17 years ago, 13-Apr-07, to lugnet.robotics.rcx)
|
