To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.org.ca.rtltorontoOpen lugnet.org.ca.rtltoronto in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Organizations / Canada / rtlToronto / 15708
15707  |  15709
Subject: 
Re: event driven vs. timing driven code...
Newsgroups: 
lugnet.org.ca.rtltoronto
Date: 
Mon, 20 Feb 2006 00:20:58 GMT
Viewed: 
654 times
  
In lugnet.org.ca.rtltoronto, Chris Magno wrote:

Rob, do you have other code that keeps it looking for the light after
your first spin?


Yep Chris - it is a basic line follower type routine, with the only sneaky thing
being that it always looks for the light staying the same or getting brighter
(as it gets closer).  If it looses the light in its FOV then it will reset an go
back to the full circle.

right now, I am working on "perfecting" code that will "square up" so
that if the bot approached than T.O. on an angle, then it will back up,
and try to get itself more centered.

My prototype dispenser is narrow with the hopes that I will be lined up and be
able to put a block into the holde from a fairly wide angle.


lot more difficult than it seems. Im using a combo of WAIT's and other
sensors feedback.

maybe you could just rely on pushing the other bot square with yourself (or vice
versa)?

-Rob A>



Message is in Reply To:
  Re: event driven vs. timing driven code...
 
Rob Antonishen wrote: ing the state. Works OK, but you can still (...) COOL!!!! i might just have to do a short video myself. it would seem that the "spin" idea works well. Rob, do you have other code that keeps it looking for the light after your (...) (19 years ago, 19-Feb-06, to lugnet.org.ca.rtltoronto)

7 Messages in This Thread:


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

Custom Search

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