View Single Post
  #2   Spotlight this post!  
Unread 19-05-2010, 14:18
mwtidd's Avatar
mwtidd mwtidd is offline
Registered User
AKA: mike
FRC #0319 (Big Bad Bob)
Team Role: Mentor
 
Join Date: Feb 2005
Rookie Year: 2003
Location: Boston, MA
Posts: 714
mwtidd has a reputation beyond reputemwtidd has a reputation beyond reputemwtidd has a reputation beyond reputemwtidd has a reputation beyond reputemwtidd has a reputation beyond reputemwtidd has a reputation beyond reputemwtidd has a reputation beyond reputemwtidd has a reputation beyond reputemwtidd has a reputation beyond reputemwtidd has a reputation beyond reputemwtidd has a reputation beyond repute
Re: Learning Autonomous Mode?

Quote:
Originally Posted by John_1102 View Post
It is possible to put a robot in Autonomous Mode and have it learn the correct path to take and remember it for future reference.
This is definitely possible, it may not be exactly the same each time but it will be close. As far as LabView goes I'm not sure, but with java or c++ you could log what your driver does, and then replay it.

Also due to the inaccuracies of wheels, I would recommend logging the gyro too. The combination of js inputs and a gyro should be pretty solid.

Quote:
Originally Posted by John_1102 View Post
Maybe a combination of sonar and encoders could help avoid unnecessary collisions in AUTO mode.
This is the problem with a sequential taught algorithm though, once you get off track, if it is simply a sequential memorized steps, it most likely won't be able to find its way back to that sequential path.

That being said here is a clip from our 2006 robot. http://video.google.com/videoplay?do...3997861101882#
We used sequential (dead reckoning) to get to the goal, and then a state machine once we were there (finding, aiming, and shooting).

What this allowed us to do was change the angle we pointed it for the initial approach, and that's how we were able to dodge the robot who was going to block us. However if we were bumped during the sequential phase or changed the angle too much, we were done for (why we lost the finals
http://video.google.com/videoplay?do...66434275131148)

What you are proposing works well for accomplishing goals like this years where you did not have to be overly accurate and there was not much defense. Also it would have been good if you wanted several approach paths in '06, you could quickly record them and rerun them. However if accuracy is an issue, or there is a ton of defense ('09) a state machine may be better.

A sequential set of state machines would have worked well for this year. Sequential for driving, a state machine for ball detection and kicking.

So I would say sequential is good for joystick logs, encoders, dead reckoning, accelerometers, and gyros.

If you are using any other sensors they should be in a state machine.
__________________
"Never let your schooling interfere with your education" -Mark Twain

Last edited by mwtidd : 19-05-2010 at 14:22.