Quote:
Originally Posted by Matt Krass
You have nothing to be ashamed of. ...
If anyone disagrees with, bring it on 
Matt |
ORIGNAL POST: (but I embolded key phrases):
"I know this is nothing more than speculation, but it's
extremely fishy. While our team was at the Finger Lake Regional in New York, several teams had their robots suddenly act erratically during teleop, sometimes in a
very suspicious manner."
Curiosity is one thing: casting aspersions as to a significant likelyhood of intentional unfairness perpetrated by someone is something else. It calls into question the fairness and the legitimacy of the entire competition.
I thnk Brandon no longer thinks such sentiments are appropriate to a large public forum without greater evidence.
The gracious thing is to assume a team's problems are it's own fault and to ask for help isolating them and not assume someone associated with FIRST or attending FIRST is out to get them by nefarious means.
The volunteer field crews work very hard. I know from personal experience that if a robot "misbehaves" on the competition field but does not misbehave on the practice field or on tether, it can be very frustrating. Isolating the cause of the difference of behavior can sometimes be very hard.
As demonstrated in Update #17, the technical staff is working quite hard to help teams identify issues with their robot prior to connecting to the FMS.
Teams should also know how and be ready to reset their robot if it "bricks" on the competition field.
We weren't.