 | | Re: NXT Ultrasonic reporting wrong values
|
|
(...) No, is not. I am in "desperate mode", so, by now I am using only the NXT brick and the US, and trying to figure out more information about this condition... I realize now that the black grid in front of the right "eye" of the sensor is turned (...) (20 years ago, 15-Oct-06, to lugnet.robotics.nxt)
|
| |
| | Re: NXT Ultrasonic reporting wrong values
|
|
(...) Yes, "stationary" is the correct word... The problem that i bought this one in UK, but i live in Brazil. No one here have this set (Actualy, i don´t know anybody who plays with LEGO mindstorms also...) With BrickxCC watching this sensor I get (...) (20 years ago, 15-Oct-06, to lugnet.robotics, lugnet.robotics.nxt)
|
| |
| | Re: Managing Memory
|
|
(...) I've tested some, but not a lot (speed of execution I've tested more). Yes, NXT-G is not memory-friendly, *but*... (URL) biggest first problem is putting a bunch of nice sound files on-board (and especially not deleting them later). The nest (...) (20 years ago, 15-Oct-06, to lugnet.robotics.nxt)
|
| |
| | Re: NXT Ultrasonic reporting wrong values
|
|
(...) Is this sensor mounted on a robot? Make sure you don't have anything anywhere in front of the robot. Steve (20 years ago, 15-Oct-06, to lugnet.robotics.nxt)
|
| |
| | Re: NXT Ultrasonic reporting wrong values
|
|
(...) I'm not sure what you mean by "completely stopped" - stationary? I suppose it's possible that you actually have a bad US sensor. If you can find someone with a working one, try swapping sensors with them and see if the problem is isolated to (...) (20 years ago, 15-Oct-06, to lugnet.robotics, lugnet.robotics.nxt)
|
