 | | 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)
|
| |
| | Re: NXT Program: How to avoid stop-and-go?
|
|
But if the Move block is unlimited will the next block (Wait) be processed? and when it goes to Wait block isn't that mean Move block is done and it will stay in the Wait block for ever, because the vehicle is not moving? (...) (17 years ago, 21-Dec-07, to lugnet.robotics)
|
| |
| | Re: NXT Program: How to avoid stop-and-go?
|
|
(...) Try a Move block set to "unlimited": that will turn the motors on and let them run. Then have a Wait block to wait for the US sensor to report an object, or something similar inside a Loop. When an object (like a wall) is detected, the next (...) (17 years ago, 21-Dec-07, to lugnet.robotics)
|
| |
| | NXT Program: How to avoid stop-and-go?
|
|
I've just started with my very first vehicle according to the instruction. Then I added the distance sensor. So, my car will turn when it come too close to an obstacle. I use a loop with distance as exit condition, i.e. the loop repeats the forward (...) (17 years ago, 20-Dec-07, to lugnet.robotics)
|
