View Single Post
  #18   Spotlight this post!  
Unread 13-03-2016, 22:32
Abrakadabra Abrakadabra is offline
Here We Go !!!
AKA: Scott Kukshtel, Mr. K
FRC #3467 (The Windham Windup!)
Team Role: Mentor
 
Join Date: Jan 2007
Rookie Year: 2002
Location: Windham, New Hampshire
Posts: 159
Abrakadabra has a brilliant futureAbrakadabra has a brilliant futureAbrakadabra has a brilliant futureAbrakadabra has a brilliant futureAbrakadabra has a brilliant futureAbrakadabra has a brilliant futureAbrakadabra has a brilliant futureAbrakadabra has a brilliant futureAbrakadabra has a brilliant futureAbrakadabra has a brilliant futureAbrakadabra has a brilliant future
Re: Banging the driver station

Quote:
Originally Posted by bdaroz View Post
Let me ask a rookie team question....
If you are low-bar capable, one thing you could do is always ask your alliance partners if you can have the low bar spot - it never hurts to ask. And if one of them has a low-bar autonomous that does more than cross (i.e. also scores) then you should consider not running auto that match or else just run a short distance for the 2 point REACH.
Another thing you can try without adding any additional sensors is reading the current from your speed controllers directly from the PDP. Presumably you will see a spike in current as your bot climbs over the defense, then it will level out once it reaches the other side. Just do a moving average of the current over time and stop when you see it going down.
If you can add encoders to one or both sides, then you can better measure distance traveled, and again, averaging over time will give you velocity. When you see the bot speed up after the defense, then shut it down. (of course, this presumes that your wheels don't slip excessively while crossing).
In the future, you might want to consider an ultrasonic sensor (relatively cheap, but prone to signal scatter from the diamond plate walls) or for a little more money, one of the new compact LIDAR units.

Quote:
Originally Posted by alicen View Post
I just wanna touch on this one tiny thing - sometimes you think your auto is right, then it's not. If a student makes a small error, should they be yellow carded immediately for it?
A Yellow card is meant to be a warning - there is no immediate penalty, but it is a strong incentive to not do it again. Giving an "extra strike" as Greying Jay suggests would be difficult to track unless FIRST goes to a 3 card system.
I am of the school that believes no code should be run on the field unless it has been duly checked out on the practice field, and if that can't be done before a match, then you just have to forego the potential auto points until you can. Of course, there are always things that can go wrong due to unforeseen special circumstances (see 3467's whirling dervish can grabbers from last year), but the Yellow card warning would be a strong incentive to figure out why it happened (as we did) and make sure it never happens again.
__________________
[2002-2005]: FLL Coach
[2007-2010]: Mentor FRC 241
[2011-current]: Lead Advisor
FRC 3467 - The Windham Windup // 3467 on TBA
Windup Robotics 4-H Club
Reply With Quote