hassenplug wrote:inxt-generation wrote:Originally, the rules stated that the robot must wait at least two seconds before starting to climb. Of course, after seeing Steve's robot, they abolished it
.
Well, I didn't write the rules, but there are four things they say the robot
must do, and one thing is
should do. Initially, I had planned to do the same type of timer you did, using that same motor. I did that a few years ago, and it worked very well.
OOOOOOHH. Arrgghh, why didn't I notice that? I'm usually really good with that kind of wording tricks. I will edit the post.
hassenplug wrote:That's a very nice write up for your robots.
So, what advice would you offer to others, trying to make stuff to do as well as you did?
Steve
Thanks!
Well, first I would say to just build! See what works and what doesn't. Try a few mechanisms. W.E.D.G.E. went through about 5 major (read: complete disassembly) revisions, as I thought of ways to improve it, and found flaws. You learn from your mistakes.
See what other people have done. Try their designs, see if you can improve them. Or, just learn about what techniques they used.
Look for loop-holes in the rules, as you (Steve) have definitely shown the advantage of. Try to think of things that no one else would, a unique design that works differently from the rest.
And, most important of all, [rant]ditch NXT-G!!!! It's the hardest software to work with there is!!! Get RobotC, or NXC, or anything as long as it's not NXT-G!!!!![/rant]
There. I am done now.
A.K.A. NeXT-Generation.
"A kingdom of heaven for RobotC now has recursion!"