Subject:
|
Re: Two RCX with one IR-Tower
|
Newsgroups:
|
lugnet.robotics.rcx
|
Date:
|
Wed, 24 Apr 2002 20:47:08 GMT
|
Viewed:
|
2904 times
|
| |
| |
The 'usual' way to get status data is to poll the the RCX memory for status
information, but you can't do that because of the number of RCX bricks; so
how about getting each RCX to send a response message (or series of messages)
to the PC encoding the status information in some bits, and using other bits
to identify the sending RCX eg:
ID in bit 8, status data encoded in bits 1-7:
messages from: 1-127 (0x01->0x7F) are always from RCX 0
messages from: 128-255 (0x80->0xFF) are always from RCX 1
That let's you demultiplex the data in the PC.
As long as each RCX only sends this data in response to a message from the
PC,then you have no collision problems.
Now you have to stop the response messages triggering the other RCX into
taking some action, which is just a case of reserving trigger messages and
not sending them as response messages eg:
Trigger messages:
message 1 triggers RCX 0
message 128 triggers RCX 1
response messages can take any value except these.
HTH,
Phil.
leo wrote:
>
> Hello,
>
> I want to control two RCX with one ir-tower. The problem is that the RCX
>
> should send back status information.
>
> Sending information to the RCX is quite easy: Both RCX receive the message
>
> but only one will perform the command. I found information and samples about
>
> that.
>
> But in my application the RCX has to send back status and position
>
> information.
>
> Is there anybody who has done this before?
>
> leo
|
|
Message is in Reply To:
| | Two RCX with one IR-Tower
|
| Hello, I want to control two RCX with one ir-tower. The problem is that the RCX should send back status information. Sending information to the RCX is quite easy: Both RCX receive the message but only one will perform the command. I found (...) (23 years ago, 11-Apr-02, to lugnet.robotics.rcx)
|
2 Messages in This Thread:
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|