 | | Re: NXT to NXT communication?
|
|
(...) Yep. I'm not at all sure about hardwiring two NXT's together - to be honest, I've not even thought about it, because BT connections are so easy and secure. Early on I investigated the BT option by sending simple numbers between two NXT's. But (...) (19 years ago, 2-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) What about multiple NXTs? How well does Bluetooth handle message collisions? Does the NXT have anything built-in to handle them, or would I need to program some kind of re-try protocol? I assume it also has no built-in addressing protocol? (...) (19 years ago, 2-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 (...) (19 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, (...) (19 years ago, 4-May-06, to lugnet.robotics)
|
| |
| | 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 (...) (19 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 (19 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, (...) (19 years ago, 4-May-06, to lugnet.robotics)
|
| |
| | 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 (...) (19 years ago, 4-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) So, if any NXT can be both master and slave, could you hook 3 of them up in a triangle? A is master over B, B over C, and C over A? (19 years ago, 5-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) Or even A master over B, B over A? ROSCO (19 years ago, 5-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) OK...it looks like this messaging mechanism in (URL) is a little confusing. Steve cleared this up a bit in (URL) In the hierarchy he discussed, N0 has to go through N1 to talk to N2-4. This model can be extended to higher levels in a tree (...) (19 years ago, 5-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) Yes just kinda murky now! There are still good opportunities for a wireless network of NXT's! One could write a program on a single master and control as many lower level NXT's as you could bring together! Like one general commanding three (...) (19 years ago, 5-May-06, to lugnet.robotics)
|
