|
Re: Did you automate any robot processes (in teleop)?
My rule for automation that takes control away from the drivers is that the software should only make things the driver can do faster. If a driver is not capable of doing something manually at all (or is really slow at it) it's probably more of a mechanical or strategy problem than a software problem.
For example: bringing the arm to a preset scoring position with a button press: good. The driver can do it but control makes it faster and more accurate.
Trying to use sensors to fix the fact your drivers can't pick up a tube across the field: not so good. This is a hack to fix inherently broken mechanical device or strategy. Software can fix this in a pinch, but it would be better as the software person to preach to your team early on for non-reliance on software. This seems backwards coming from a software engineer, but you'll end up with a better robot and it means less frustration for you.
__________________
Team 254 | San Jose, CA | Mentor (2010 - Present)
Team 125 | Boston, MA | College Student (2007 - 2011)
Team 195 | Southington, CT | Student (2002 - 2006)
|