 | | Re: NXT to NXT communication?
|
|
(...) Hey Ross, With bluetooth built in, there is no real need for any other kind of brick to brick communication to be investigated. Bluetooth is a professional strength protocol with all the necessary networking features. Since it uses gobs of (...) (20 years ago, 3-May-06, to lugnet.robotics)
|
| |
| | Re: My First few NXT MOCs
|
|
(...) I'm confused why this particular post is in the headlines (for a couple days at the time of this response). No one has highlighted it and its only a follow-up. Sorry to beat a dead horse, but deosn't someone watch for stuff like this and tune (...) (20 years ago, 3-May-06, to lugnet.robotics, lugnet.admin.general)
|
| |
| | Re: NXT firmware to be open source
|
|
(...) The LEGO Mindstorms Driver SDK is dual platform (PC and Mac). It is built upon the National Instruments NI-VISA interface. The main driver component is called Fantom. It exposes a set of C functions and C++ classes which let you communicate (...) (20 years ago, 3-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? (...) (20 years ago, 2-May-06, to lugnet.robotics)
|
| |
| | 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 (...) (20 years ago, 2-May-06, to lugnet.robotics)
|
