 | | Re: NXT to NXT communication?
|
|
(...) I am not certain but I believe that the NXT does not allow direct slave-slave communication. An NXT can be both a master and a slave in a hierarchical array of NXTs (to the best of my knowledge) but two slave NXTs cannot directly communicate (...) (20 years ago, 4-May-06, to lugnet.robotics)
|
| |
| | Re: NXT memory limits
|
|
(...) The documentation on the LEGO website is a good source: (URL) chip is the Atmel AT91SAM7S256 (URL) this helps, John Hansen (20 years ago, 4-May-06, to lugnet.robotics)
|
| |
| | NXT memory limits
|
|
Now that the NDA has been lifted, can anyone confirm how much memory is available on the NXT? Also, can anyone confirm what CPU they are using (i.e. what flavor of ARM chip etc?) (20 years ago, 4-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) Thank you, Kevin - yes, I should have said John Hansen. My fault entirely, sorry about that John. (20 years ago, 4-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) I a slight mis-statement. John Hansen is the NBC guy. Kevin (20 years ago, 4-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) John Barnes and others have been working on that. He has out a beta of a "Nxt Byte Code" (NBC) assembler, and he's dug into a *lot* of firmware and software details. See the following (& John's website) for more details. (URL) not as sure (...) (20 years ago, 4-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) Yes, that's a tough one... (...) I've played around with a few ideas using bluetooth. In addition to the NXT->NXT remote, I wrote a program for my Bluetooth enabled PDA using eVB. Jim Kelly actually has a screenshot in his blog (URL) under (...) (20 years ago, 4-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) Yes. NXT1 will be connected via connection 0 from NXT0 NXT1 will be connected via connection 1 to NXT2 NXT1 will be connected via connection 2 to NXT3 NXT1 will be connected via connection 3 to NXT4 NXT1 can send a message to connection 0,1,2, (...) (20 years ago, 4-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) Steve, your remote is pretty cool. It’s a great idea if you have more than one NXT. I checked with my purchasing manager (my wife) and I don’t think my request for capital expenditure will be approved for more than one NXT this year. With that (...) (20 years ago, 4-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) A little - the next question of course is: Can NXT1 be both slave (to NXT0) and master (to NXT2, NXT3, NXT4) at the same time? Or does that require sneaky protocol to switch between the 2? ROSCO (20 years ago, 4-May-06, to lugnet.robotics)
|
| |
| | Re: My First few NXT MOCs
|
|
(...) Dave (20 years ago, 4-May-06, to lugnet.robotics, FTX)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) Dave, I don't know a whole lot about BT (beyond the little I've found out because of this project), but your assessment is correct. The protocol is implemented according to BT spec, so all communication is done through master-slave (...) (20 years ago, 4-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) Ok after actually reading the other threads in this post, it looks like TLG decided to develop its own BT profile just for the NXT. The messaging mechanism described by Brian and Steve looks like it will allow direct slave-slave communication, (...) (20 years ago, 4-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) Quite muddy! Why only three connections and what about specification adherence? Are they trying to limit its potential applications or were they just trying to get out a production-ready implementation? In other words are there plans for an (...) (20 years ago, 4-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) I can't speak for the NXT, but knowing that it has BT, and should be adhering to the specs, then the answer would be yes. The master-slave communication is coordinated via time slots within a piconet. This would avoid message collisions. In (...) (20 years ago, 4-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) That's one possibility. (...) OK, that's a much better way of phrasing that :). The thing that's a little confusing (to me) is that means that if the NXT named "Ann" wants to communicate with one named "Ben", you can establish a BT connection (...) (20 years ago, 4-May-06, to lugnet.robotics)
|
| |
| | Re: Port types (Re: NXT to NXT communication?)
|
|
(...) Erm, can I clarify here; The digital sensor port which is part of the motor port is not the same as the digital port which is part of the main sensor ports. The two digital wires which are part of the motor port are input only, whereas the (...) (20 years ago, 3-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) So they could potentially be programmed to provide force or shudder feedback? (...) Yes, but I'm interested to know: Are these multiple connections available via the LEGO retail software, or did you program your pair some other way? It's just (...) (20 years ago, 3-May-06, to lugnet.robotics)
|
| |
| | Port types (Re: NXT to NXT communication?)
|
|
(...) Not exactly. There was talk about that early on. You can not use the sensor port to drive a motor, and you can not use the motor port to read an analog (old style) sensor. The hardware specs may have changed, so I may not be 100% on this, but (...) (20 years ago, 3-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) So you can use a motor port as a sensor input and/or use a motor as an input device (and vice-versa)? -Rob www.brickmodder.net (20 years ago, 3-May-06, to lugnet.robotics)
|
