Robotics : 25849


Robotics / 25849

Re: NXT to NXT communication? —Steve Hassenplug

(...) The motors offer little resistance when used this way. However, there's something else which I think is kind of cool. If you look close, when I let go of the controller, the paddles return to the middle, and the car stops. Using just one block (...) (19 years ago, 3-May-06, to lugnet.robotics)

Re: NXT to NXT communication? —Rob Hendrix

(...) 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 (19 years ago, 3-May-06, to lugnet.robotics)

Port types (Re: NXT to NXT communication?) —Steve Hassenplug

(...) 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 (...) (19 years ago, 3-May-06, to lugnet.robotics)

Re: Port types (Re: NXT to NXT communication?) —John Barnes

(...) 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 (...) (19 years ago, 3-May-06, to lugnet.robotics)

Re: NXT to NXT communication? —Ross Crawford

(...) 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 (...) (19 years ago, 3-May-06, to lugnet.robotics)

Re: NXT to NXT communication? —Brian Davis

(...) 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 (...) (19 years ago, 4-May-06, to lugnet.robotics)

Re: NXT to NXT communication? —David Hurley

(...) 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 (...) (19 years ago, 4-May-06, to lugnet.robotics)

Re: NXT to NXT communication? —Brian Davis

(...) 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 (...) (19 years ago, 4-May-06, to lugnet.robotics)

Re: NXT to NXT communication? —Kevin L. Clague

(...) I a slight mis-statement. John Hansen is the NBC guy. Kevin (19 years ago, 4-May-06, to lugnet.robotics)

Re: NXT to NXT communication? —Brian Davis

(...) Thank you, Kevin - yes, I should have said John Hansen. My fault entirely, sorry about that John. (19 years ago, 4-May-06, to lugnet.robotics)

Re: NXT to NXT communication? —John Hansen

(...) As Brian already mentioned I have produced a compiler for a text-based language (assembly) which is called Next Byte Codes (NBC) for a number of complicated reasons. Michael Barrett Anderson, who is the father of LASM and the RCX firmware, has (...) (19 years ago, 4-May-06, to lugnet.robotics)

Re: NXT to NXT communication? —Tim Byrne

(...) 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 (...) (19 years ago, 4-May-06, to lugnet.robotics)

Re: NXT to NXT communication? —Steve Hassenplug

(...) 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 (...) (19 years ago, 4-May-06, to lugnet.robotics)

Re: NXT to NXT communication? —Dick Swan

I haven't seen any discussion on the performance of the bluetooth messaging. I've measured PC to NXT round trip (send message and receive acknowledgement) as typically being 30 milliseconds. Has anyon else done these measurements and were your (...) (19 years ago, 5-May-06, to lugnet.robotics)

Re: NXT to NXT communication? —Brian Davis

(...) I can't figure out a easy way for me to test PC-to-NXT timelag, but I tried some simple bench tests on NXT-to-NXT. This is just the old standard of two timed loops (10,0000 interations), one empty, and one with a single block (or two), and (...) (19 years ago, 5-May-06, to lugnet.robotics)

Re: NXT to NXT communication? —David Hurley

(...) <snipity> Jim (...) Did you say SDK?? Please elaborate on this... (19 years ago, 6-May-06, to lugnet.robotics)

Re: NXT to NXT communication? —Ross Crawford

(...) (URL) (19 years ago, 6-May-06, to lugnet.robotics)

Re: NXT to NXT communication? —John Hansen

(...) Hmmm... Speaking of SDK, based on a preliminary version of the Hardware SDK documentation the NXT is not capable of being both a master and a slave at the same time so a network of NXTs is limited to one master and three slaves and that's it. (...) (19 years ago, 11-May-06, to lugnet.robotics)

Re: NXT to NXT communication? —Ross Crawford

(...) Sounds like it's a firmware block though, so hopefully it can be overcome with "NxtOS" or whatever in future. ROSCO (19 years ago, 11-May-06, to lugnet.robotics)

Re: NXT to NXT communication? —Kevin McClure

(...) Very cool- the differential is very well designed, especially using only parts from the NXT. (...) Thats what I can't figure out how to do. I made a (modded) version of Brian Davis' DAZLR and using my grandfather's NXT have made a Remote (...) (18 years ago, 15-Jul-06, to lugnet.robotics)