| | Moving NXT motors by hand
|
|
Hi: Sometimes my son and I move the NXT motors by hand, for instance, by attaching something to the holes in the orange hubs to act as a crank. We wonder if that's bad for the motors. Does anyone have an opinion? Regards, John and Will (17 years ago, 28-May-07, to lugnet.robotics.nxt)
|
|
| | robosoccer ball problem
|
|
Hi all, I am trying to get some middle school kids playing a bit with the robosoccer idea. I don't want to frustrate them with the fluctuating IR ball. So, I am planning to find a constant "lighted" ball for them instead, but no luck. Wonder if (...) (18 years ago, 28-May-07, to lugnet.robotics.nxt)
|
|
| | Gripper/Register for Light Sensor Experiment
|
|
I want to create a platform for experimenting with the light sensor. At the moment, I'm thinking of cutting off the gray-scale and color bars off the NXT Test Pad that comes from the commercial kit. The strip would then be mounted on some device, (...) (18 years ago, 26-May-07, to lugnet.robotics.nxt)
|
|
| | Re: Using NXT Port 4 EIA-485
|
|
(...) Does anybody have an NXC program that demonstrates the use of RS485 communications? (18 years ago, 25-May-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
|
| | Re: bitwise operators
|
|
(...) ...and if you are talking about NXT-G, there is a bitwise manipulation block, written by Mike Gasperi and Steve Hassenplug, available here: (URL) list of available blocks is here: (URL) (18 years ago, 25-May-07, to lugnet.robotics.nxt)
|
|
| | Re: bitwise operators
|
|
(...) Are you talking about NXC or NBC or some other programming language? The standard NXT firmware does support bitwise logical operators such as and, or, and xor. In both NXC and NBC you can use these operations as you would expect in a C-like (...) (18 years ago, 24-May-07, to lugnet.robotics.nxt)
|
|
| | bitwise operators
|
|
I looked thru the doc, it looks like it does not allow bitwise operators like IOR, XOR, AND, etc. Is this correct? Or, I have overlooked something? --thanks Elizabeth (18 years ago, 24-May-07, to lugnet.robotics.nxt)
|
|
| | RE: determine the degree of turning by using ultrasonic sensor
|
|
Ok... I wrap every sequence of motion control with mutex. I created a movement macro which basically just wrap the command(s) around with acquire and release. By the way, would someone tells me how I'll find out how the mutex datatype implemented. (...) (18 years ago, 22-May-07, to lugnet.robotics.nxt)
|
|
| | RE: determine the degree of turning by using ultrasonic sensor
|
|
Found it... RotateMotor(OUT_C, 100, turn); x = MotorRotationCount(OUT_C); --E -----Original Message----- From: news-gateway@lugnet.com [mailto:news-gateway...ugnet.com] On Behalf Of Elizabeth Mabrey Sent: Tuesday, May 22, 2007 12:57 PM To: (...) (18 years ago, 22-May-07, to lugnet.robotics.nxt)
|
|
| | determine the degree of turning by using ultrasonic sensor
|
|
Is it quick way to determining the # of degree or some value which will help to calculate the distance travelled. more or less like the x= rotation-click.. Is it a way to read how much the motor has turned from a certain point. - Reset motor/sensor (...) (18 years ago, 22-May-07, to lugnet.robotics.nxt)
|
|
| | Introduction of LEJOS OSEK
|
|
Hello everyone and special thanks to LEJOS developers, I would like to introduce a new project that is standing on the shoulders of giants. LEJOS OSEK (URL) is an open source firmware for LEGO Mindstorms NXT. LEJOS OSEK consists of I/O driver of (...) (18 years ago, 22-May-07, to lugnet.robotics.nxt)
|
|
| | Re: NXC - embedded functions failed
|
|
(...) I think having NXC generate a compiler error is a great idea. :-) I will work that into the next beta release (b30). I just released beta 29 today. It has a number of important fixes and enhancements but I just noticed that it has a few new (...) (18 years ago, 22-May-07, to lugnet.robotics.nxt)
|
|
| | RE: NXC - embedded functions failed
|
|
Hi John, Will throwing in a compilation error be a viable option? --Elizabeth -----Original Message----- From: news-gateway@lugnet.com [mailto:news-gateway...ugnet.com] On Behalf Of Elizabeth Mabrey Sent: Sunday, May 20, 2007 1:19 PM To: (...) (18 years ago, 21-May-07, to lugnet.robotics.nxt)
|
|
| | Re: pbLua PCF8574 SOLVED !
|
|
(...) Let me say thanks to Dick as well. I think that the NXT firmware does what's called a repeat start in the I2C definition... Here's the part in the I2C spec that is required: (URL) And with pictures: (URL) Hope this helps... Ralph (18 years ago, 21-May-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
|
| | Re: pbLua PCF8574 SOLVED !
|
|
(...) Hi Dick, your answer solves my knot :D It's a NXT specific behaviour and all alternatives NXT-OSes which uses original Lego-Source-Lowlevel routines have this feature ? Thanks for your answer Bye Christian (18 years ago, 21-May-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
|
| | RE: pbLua PCF8574 SOLVED ?
|
|
(...) This is the excepted behavior. When you want to read from I2C device, the NXT firmware first sends a write message to load the internal index "pointer" for the I2C device and then sends a read message that will read the requested number of (...) (18 years ago, 21-May-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
|
| | Re: pbLua PCF8574 SOLVED ?
|
|
(...) Hi, or was it a quirk at my brain to address the i2c-read-address and hope to receive usefull data ? Currently it works for me when using allways the i2c-write address... Are the any demos or samples for NXC, using the PCF8574 ? 1. setting (...) (18 years ago, 21-May-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
|
| | Re: NXC - embedded functions failed
|
|
(...) This is definitely a problem in NXC. The problem is that the value of arg "a" (33) to the function Max is being replaced during the second call to Max since it passes 5 into arg "a". It looks like I need to figure out a decent way to implement (...) (18 years ago, 21-May-07, to lugnet.robotics.nxt)
|
|
| | Re: pbLua PCF8574 SOLVED
|
|
(...) Hi, we solved the problem... Lego-Firmware has own brain and handle read/write with own mechanisms ;-( The last read/write bit is handled automatically by lowlevel routines. Reading the same address like writing solves the problem. (...) (18 years ago, 21-May-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
|
| | NXC - embedded functions failed
|
|
#include "NXCDefs.h" int Max(int a,int b){ if (a>b) return a; else return b; } task main(){ int Prob=0; Prob = Max(33, Max(5,15)); NumOut(5,LCD_LINE2,false,Prob); //returns 15 WRONG ---...--- Prob = Max(5,15); Prob = Max(33,Prob); (...) (18 years ago, 20-May-07, to lugnet.robotics.nxt)
|