 | | Re: Hi-speed port communication
|
|
(...) Cool! I wonder if you could daisy-chain NXTs using this technique, and if so, how many you could connect? ROSCO (17 years ago, 4-Jan-08, to lugnet.robotics.nxt)
|
| |
| | Hi-speed port communication
|
|
I've been getting a number of emails from some people who want to know how to use the hi-speed RS-485 port 4 functionality in the NXT using the standard firmware. With John Barnes' help I now know how to get it to work correctly. Here is a simple (...) (17 years ago, 4-Jan-08, to lugnet.robotics.nxt)
|
| |
| | Re: designing new NXT parts (propeller and motor) using rapid prototyping
|
|
(...) Indeed, this 180mA limitation is the one of the 4.3V power supply, that feeds the sensors and the motor position encoders. The motors themselves can receive a much higher current, limited by their own thermal protection and by the maximum (...) (17 years ago, 31-Dec-07, to lugnet.robotics.nxt)
|
| |
| | NXT iterate files
|
|
I wrote some NXC code that runs on the enhanced NBC/NXC firmware. It demonstrates how to iterate files on the filesystem. Let me know if you have any questions. John Hansen #define LOADER_HANDLE(_x) (_x&0xff) #define LOADER_ERR_BYTE(_x) (...) (17 years ago, 30-Dec-07, to lugnet.robotics.nxt, lugnet.robotics)
|
| |
| | Re: NXC problem
|
|
(...) Remove the #include "NXCDefs.h" line since recent versions of the compiler do not require that you explicitly include this file. Make sure you are running the latest BricxCC and NBC/NXC compiler. The lastest version of the compiler is (...) (17 years ago, 30-Dec-07, to lugnet.robotics.nxt)
|
| |
| | Re: designing new NXT parts (propeller and motor) using rapid prototyping
|
|
(...) Nice looking parts! One of those times I wish I had a access to such equipment. (...) A nice idea, and well-written. There are a few interesting points that I thought of while reading through it. First, you mention the NXT limits the total (...) (17 years ago, 30-Dec-07, to lugnet.robotics.nxt)
|
| |
| | designing new NXT parts (propeller and motor) using rapid prototyping
|
|
Dear all, For those interested, I have been exploring the use of rapid prototyping technology in building new parts for the NXT. I attempted to build a propeller brick in combination with a more powerful motor. Read my results on (...) (17 years ago, 30-Dec-07, to lugnet.robotics.nxt)
|
| |
| | NXC problem
|
|
I've tried to install Bricx and NXC but when I try to compile a simple program I get an error like "Unable to find include file: "NXCDefs.h". I figure I probably just have something configured incorrectly but can't find any guidance as to what I (...) (17 years ago, 28-Dec-07, to lugnet.robotics.nxt)
|
| |
| | Re: NXT Program: How to avoid stop-and-go? (US-Sensor Test Values)
|
|
I tried to use a program to log the distance while the US-sensor is moving forward. Unfortunately, it doesn't go straight all the time. So, I simply display the US value and put the vehicle in different position manually. Here are my test values for (...) (17 years ago, 27-Dec-07, to lugnet.robotics)
|
| |
| | Individual Power-Functions elements now available
|
|
Individual Power-Functions elements now available on H@H: battery box, both motor types, IR receiver and transmitter, and a Power-Function to 9V converter cable. Listed as shipping later in January. (17 years ago, 26-Dec-07, to lugnet.technic, lugnet.robotics)
|
| |
| | Re: NXT Program: How to avoid stop-and-go? (US-Sensor in angle)
|
|
(...) That is a very interesting site, with some interesting information... but you might like to do those experiments yourself. For instance, the odd "ledge" in their data at 48 cm is not a feature with my US sensors - they may have been working (...) (17 years ago, 25-Dec-07, to lugnet.robotics)
|
| |
| | Re: NXC: How to read the distance of US-sensor?
|
|
I found a piece of codes in a forum: (URL) guess I can assume it's returning cm. (...) (17 years ago, 24-Dec-07, to lugnet.robotics)
|
| |
| | Re: robolabatceeo/college/tutorials Is not working
|
|
(...) I have contacted Tuffs via e-mail. I will be calling them soon. Thanks for your guidance. Tom (17 years ago, 24-Dec-07, to lugnet.robotics.rcx.robolab)
|
| |
| | NXC: How to read the distance of US-sensor?
|
|
I'm new in NXC. In the NXC-guide, I found SensorUS() returning a value from US-sensor. But in the LEGO software I can select inch/cm. Questions: What value is it returning, inch or cm? Can I set it to inch or cm? thanks Phuoc Can HUA (17 years ago, 24-Dec-07, to lugnet.robotics)
|
| |
| | Re: NXT Program: How to avoid stop-and-go? (US-Sensor in angle)
|
|
(...) (17 years ago, 24-Dec-07, to lugnet.robotics)
|
| |
| | Re: NXT Program: How to avoid stop-and-go? (US-Sensor in angle)
|
|
Strangely, it slows down, i.e. it detects the further distance (less reflection?) in the same angle. I tried to put the US-sensor vertically. It still shows the same effect. I also notice the closer it comes the larger angle it needs to get a (...) (17 years ago, 23-Dec-07, to lugnet.robotics)
|
| |
| | Re: NXT Program: How to avoid stop-and-go? (US-Sensor in angle)
|
|
(...) At a glancing angle (not approaching the wall "head on" at 90°, but at an angle) very little sound energy will be reflected back towards the sensor. If there isn't enough energy reflected back for the sensor to "hear" the echo, it won't detect (...) (17 years ago, 22-Dec-07, to lugnet.robotics)
|
| |
| | Re: NXT Program: How to avoid stop-and-go? (US-Sensor in angle)
|
|
Brian, It works fantastic. Thanks. Now I've put 2 US Wait blocks. The 1st one to slow down for < 30cm and the 2nd one to turn for < 20cm. This works pretty well when the vehicle runs ~90 degree toward the wall. But when the angle is flat it only (...) (17 years ago, 22-Dec-07, to lugnet.robotics)
|
| |
| | Re: mindscript (NBC NXC)
|
|
(...) If you are running on a Windows platform then you can start with Bricx Command Center (BricxCC). It is an integrated development environment (IDE) that supports Not eXactly C (NXC) and NeXT Byte Codes (NBC) for the NXT brick running either the (...) (17 years ago, 21-Dec-07, to lugnet.robotics)
|
| |
| | Re: NXT Program: How to avoid stop-and-go?
|
|
(...) Yes. Move (unlimited) Starts the motors and *leaves them running* while progressing on to the next block in a sequence. The motor state will then remain unchanged until some other block (like a later Move or Motor block) changes it. Try it an (...) (17 years ago, 21-Dec-07, to lugnet.robotics)
|
