 | | Re: NXT to NXT communication?
|
|
(...) 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 (...) (20 years ago, 3-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) Yep (at least that's one way to do it). I tried making a X-Y joystick, but the mechnical slop was more than I liked, so I've got one with two paddles and a thumbwheel (slightly different from Steve's) (...) Not too bad. The NXT motors are not (...) (20 years ago, 3-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) they when you do that? Also, I noticed at one point you scooted the controller closer to the car. Was that because it had lost the signal? What is the effective range, anyway? I also wonder what happens when you have more than two NXT bricks (...) (20 years ago, 3-May-06, to lugnet.robotics)
|
| |
| | Re: NXT Programming with Next Byte Codes
|
|
(...) The NQC compiler in some form or other is headed for NXT support but for a number of reasons I needed to produce a functional assembler first. Now that it is mostly complete I will be trying to shift gears and work on NQC. I will post several (...) (20 years ago, 3-May-06, to lugnet.robotics)
|
| |
| | Re: NXT Programming with Next Byte Codes
|
|
(...) Great news! I look forward to seeing more. Can you post some complete example programs? Also, is there a C syntax commandline alternative in the works? (20 years ago, 3-May-06, to lugnet.robotics)
|
| |
| | NXT Programming with Next Byte Codes
|
|
I am pleased to announce that I have posted a beta of a command line compiler for a new programming language for the LEGO Mindstorms NXT programmable brick called Next Byte Codes (NBC). NBC is modelled after traditional assembly language. It is (...) (20 years ago, 3-May-06, to lugnet.announce, lugnet.robotics)
|
| |
| | Re: NXT encoders: absolute or relative? (was Re: The NXT NDA is relaxed...)
|
|
(...) relative. As you suggested, if you turn off the NXT, it will loose track of it's current location. Steve (20 years ago, 3-May-06, to lugnet.robotics, FTX)
|
| |
| | Re: My First few NXT MOCs
|
|
My BrickShelf NXT folder is now Public! (URL) (20 years ago, 3-May-06, to lugnet.robotics)
|
| |
| | NXT encoders: absolute or relative? (was Re: The NXT NDA is relaxed...)
|
|
(...) I have a question about the encoders on the NXT motor. I read that they're supposed to report the shaft position to within 1 degree. But looking at the encoder wheel actually inside the device, I don't see how that can be. It looks to me like (...) (20 years ago, 3-May-06, to lugnet.robotics, FTX)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) Rosco, The NXT to NXT communication works very well, and is easy to use. Here's some video of an NXT controller for an NXT robot... (URL) (20 years ago, 3-May-06, to lugnet.robotics)
|
| |
| | 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)
|
| |
| | Re: NXT firmware to be open source
|
|
(...) I'd be interested to know if the MUPs or MDPs have any further info on these developer kits, or have any further info they can share? I assume the dev environment is Windows based, it would be interesting to know what it's written in, and if (...) (20 years ago, 2-May-06, to lugnet.robotics, FTX)
|
| |
| | NXT to NXT communication?
|
|
Hi all you M[U|D]Ps I know most of the MDPs probably only have 1 NXT, but I'm hoping someone out there has 2, and has investigated NXT-NXT communication. Is it possible? How hard is it? I'm currently thinking Bluetooth, but is there any other way? (...) (20 years ago, 2-May-06, to lugnet.robotics)
|
| |
| | Re: NXT connectors and recepticles
|
|
(...) Hi Ben. Yes, we (HiTechnic) are busy researching this issue. As and when we uncover a viable source of supply, I'll be in a position to help. JB HiTechnic (20 years ago, 2-May-06, to lugnet.robotics)
|
| |
| | NXT connectors and recepticles
|
|
I have a question I'm hoping somebody from the NXT team can answer. According to the 'open source' press release: (URL) The schematics and configuration for the new NXT connectors will be released in August. My question is this - Since the (...) (20 years ago, 2-May-06, to lugnet.robotics)
|
| |
| | Clean that mess!
|
|
After much pressure from various people wanting to know what I have made with my NXT; I would like to present my non violent robot. This robot is ~VERY~ simple, only uses a handful of components, 2 motors, and 2 sensors. As this will be no huge (...) (20 years ago, 2-May-06, to lugnet.org.ca.rtltoronto, lugnet.robotics) !
|
