View Single Post
  #5   Spotlight this post!  
Unread 12-02-2015, 21:02
Siri's Avatar
Siri Siri is offline
Dare greatly
AKA: 1640 coach 2010-2014
no team (Refs & RIs)
Team Role: Coach
 
Join Date: Jan 2008
Rookie Year: 2007
Location: PA
Posts: 1,593
Siri has a reputation beyond reputeSiri has a reputation beyond reputeSiri has a reputation beyond reputeSiri has a reputation beyond reputeSiri has a reputation beyond reputeSiri has a reputation beyond reputeSiri has a reputation beyond reputeSiri has a reputation beyond reputeSiri has a reputation beyond reputeSiri has a reputation beyond reputeSiri has a reputation beyond repute
Send a message via ICQ to Siri
Re: Design and engineering mgmt rules

Quote:
Originally Posted by ToddF View Post
14.b) On CD, don't talk about what you plan to do. Demonstrate what you have done.
21) On the control panel, use switches for state functions (arm in/arm out) and buttons to initiate actions (shoot).
22) Drivers and operators should never need to take their eyes off the robot. Driver's station displays are for troubleshooting, not operations. ...
26) Don't ask your match partners what they can do. Ask your scouts what they have done.
Good list. My personal objections:
14. Feel free to discuss plans on CD.
21. Buttons can be used for state functions when you want positive control. We often do arm in/out on a button because we want "in" to be as fast as "ack! let go!". We also do on/offs when there's a danger or a history of split-second "sure it's on?!" uncertainty. Also, whenever the operator wants it.
22. Drivers can look at the DS for very specific actions. For instance, we did this in 2011 for minibot camera alignment and 2013 for 30-point climb alignment. Operators can look depending on the game, but it should be set up for easy recognition (colors are good). Depending on their skill and technique, my drivers or operators have paid attention to different radii around the robot.
26. Ask your scouts. Ask your partners. Question the differences. Scouts set the high mark, but people can tell you they broke something. They can also explain temporary deficiencies, but my interpretation of this depends very heavily on my relationship with the team and with the coach specifically.

Quote:
Originally Posted by serenagh View Post
Does anyone have a pre-match checklist they're willing to share/ suggestions? This sounds like a really great idea. I can imagine what the pit one would look like/include- what about the one for drivers? Thanks
1640's Abridged Drive Team List from final buzzer to auton/teleop buzzer:
  1. At the final buzzer - coach: do we need to talk to the head ref? Check other field/score issues? Specifics for alliance partners? Our pit crew? Desperate robot unknowns? Specifics for opponents? Scouts? Other teams/coaches?
  2. As Laptop Person packs up - coach: prep someone for question box as necessary, and have someone wait for score screen. Pursue discussions in the above order, congratulating and talking to allies and opponents. Coach restocks coach kit (by year, usually short tether, tape, wire ties, wire cutters, velcro, sharpie). Recover robot when lights go green, quick check as necessary.
  3. On the way or in pit (logistics-dependent): run the powered-off pre-match pit/drive team list again, checking for in-match failures. Simultaneously, plug in the driver's station computer and review logs/errors. Make notes as necessary per year. Ensure at least two charged robot batteries is available. Pull current battery only if it's questionable or something's wrong.
  4. Once pit crew/match observers are back: recap match as drive team with pit crew/match observers as necessary. Pit Captain sets task list with Coach/Pit Supervisor (same person when I did this).
  5. Inter-match: list is executed with continual feedback; coach (at least) meets next alliance and sets strategy. Ensure allies know rules, particularly the HPs. May come back and tweak pit priorities.
  6. Pre-queuing (usually 1-2 matches before first call): check laptop battery, robot battery, motor heat if a concern, and robot maintenance status. May charge pneumatics depending on match pace, how much air we store on board, and if there are leaks. Set autonomous and other scripts if applicable. Put/secure correct bumpers on robot or cart if applicable.
  7. Queued: review and/or alter quasi-play-by-play match strategy and contingencies with alliance and then specifically with drive team. (I also check safety glasses and buttons for everyone on the alliance at this time.) Particularly reiterate match settings: robot location/orientation/presets, DS presets as applicable. Coach uses this time to check on the psychology of everyone involved. Also execute drive team-specific actions: this depends on my drivers, sometimes dancing, joking, talking. Coach watches matches whenever possible, drivers/HP watch if it's good for their performance (sometimes you just need to relax). Last check for anything out of place. LAST ACTION, often on-field: switch battery, replacing it with one that has a white tab in the Anderson. Remove tab and secure battery and tab (we wire tie our tabs to the batteries).
  8. Laptop Person: plug in laptop, check presets and laptop settings as applicable. Communicate on robot alignment by eye and/or camera as applicable. Ensure FMS for self and allies is happening per usual.
  9. Autonomous Aligner and Robot Prepper: Wait for green. Actions are very specific to the robot. 2014: align for autonomous, re-straighten swerve wheels, load ball(s) per procedure, confirm alignment, final check, turn on robot (we had a sensitive gyro).
  10. Cart Person: if time allows, ensure everything's back in place on the cart.
  11. In the Box Pre-Match: coach checks entire alliance station. I look at each person individually (and HPs if not in box) and check for things out of place on the field (I'm also a ref). Drivers both recheck the presets. HP checks HP stuff (move whatever you're allowed to, check game pieces, game dependent). I also typically review the 'first move' with my drivers and each team.
  12. Last seconds of autonomous (e.g. once balls have missed or scored on both sides): last communication with coaches of specifically who will move to what, where, by what route.
__________________