To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.roboticsOpen lugnet.robotics in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / 27313
27312  |  27314
Subject: 
Re: NXT Program: How to avoid stop-and-go? (US-Sensor in angle)
Newsgroups: 
lugnet.robotics
Date: 
Sat, 22 Dec 2007 11:32:12 GMT
Original-From: 
bigboss97 <bigboss97.geo@yahooANTISPAM.com>
Viewed: 
5185 times
  
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 slows down and
sometimes it hits the wall.

My questions:
Why does the sensor detects < 30cm, but misses < 20cm for flat angle?
Shouldn't the sensor be more reliable when the distance is smaller?

Phuoc Can HUA


Brian Davis-3 wrote:

In lugnet.robotics, bigboss97 <bigboss97.geo@yahoo.com> wrote:

But if the Move block is unlimited will the next block
(Wait) be processed?

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 see.



--
View this message in context: http://www.nabble.com/NXT-Program%3A-How-to-avoid-stop-and-go--tp14446433p14468449.html
Sent from the LEGO Robotics mailing list archive at Nabble.com.



Message has 1 Reply:
  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)

Message is in Reply To:
  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)

10 Messages in This Thread:


Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR