| |
[Cross-posted to lugnet.robotics as it's on-topic there]
In lugnet.technic, Duane Hess wrote:
> Is there a way that I can easily chain two NXT's in series to have a
> total of six outputs?
There's no absolutely transparent way to make a program running on one NXT
address the sensor or motor ports of a 2nd (or 3rd, or 4th) NXT. However, a lot
of solutions to this problem were worked out in the RCX, such as:
1) Using face-to-face light sensors to binary-signal between the NXTs
2) Hooking two motors together (on the NXT), so that a rotation by one is "seen"
by the other, and vis-versa (but keep the two NXTs from both trying to "drive"
the connection at the same time!)
3) Exchange simple messages, allowing one NXT to "command" the 2nd NXT to run
its motors, read its sensors, etc. On the RCX you did this with one of 256
(8-bit) IR "messages", while on the NXT, you could individually address up to
three "slave" NXTs with secure BT channels, and the messages you could send are
almost unlimited (since you can send some fairly long text strings).
--
Brian Davis
|
|
Message has 1 Reply:
 | | Re: NXT's in Series
|
| I suspect that with the proper software (and maybe a special cable), the I2C protocol can be used to network between NXT controllers. I2C is a multi master bus with collision detection, so it "should" work. It's just a SMOP [Small Matter of (...) (17 years ago, 18-Sep-07, to lugnet.robotics)
|
Message is in Reply To:
| | NXT's in Series
|
| OK, I've scoured the 'net for a good 90 seconds and can't find what I'm looking for. Here's what I'm trying to do: I have an application where I need at least four different outputs. The NXT only has three. Is there a way that I can easily chain two (...) (17 years ago, 17-Sep-07, to lugnet.technic)
|
6 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
