|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: [FRC Blog] Orlando Incident
This is correct...I heard the overall response was pretty positive. It was used for everything from judging to inspecting to the game announcer reading off names.
|
|
#2
|
|||
|
|||
|
Re: [FRC Blog] Orlando Incident
To be completely honest I think the way FIRST (and Frank) handled this problem is unbelievable.
First of all, the "reinspection process" is NOT well-defined in the manual and as such a team has no way of knowing the magnitude of change that requires reinspection (do we need to get an inspector every time we change tread on the wheels?). Team's should not be made to suffer for FIRST's inability and refusal to define many rules properly. A team would have to be obviously and purposefully cheating before I would advocate a ruling like this. Second of all, the media got involved. Every one of us here in the 21st century should know the kind of damage that the media can do to an organization/individual's reputation. We should also be aware that a ruined reputation for a robotics team will interfere with it's ability to gain and retain sponsors as well as their ability to inspire further generations to become involved with STEM (which, may I remind you, is FIRST's entire mission). I think that the way FIRST handled the repercussions of this decision were very inadequate. FIRST needs to write a press release to defend the reputation of these teams as well as writing each of their sponsors to explain the situation. It is FIRST's responsibility to make sure that the damage to a few teams' reputation doesn't cause these teams permanent harm as well a to prevent the bad reputation to spread to other teams and the organization as a whole. |
|
#3
|
|||
|
|||
|
Re: [FRC Blog] Orlando Incident
Quote:
|
|
#4
|
||||
|
||||
|
Re: [FRC Blog] Orlando Incident
I don't think us as outside observers can really adequately judge how local team reputation is affected by local media. Of course you hadn't heard of it, you live in Boston. All it takes is one misunderstood Google search and perhaps a sponsor would look elsewhere for a team to support.
|
|
#5
|
|||
|
|||
|
Re: [FRC Blog] Orlando Incident
Quote:
EDIT: I was typing this as Chris made his post. Exactly my point. |
|
#6
|
|||
|
|||
|
Re: [FRC Blog] Orlando Incident
Quote:
|
|
#7
|
|||
|
|||
|
Re: [FRC Blog] Orlando Incident
Quote:
Apparently Florida Today follows the Pink Team on occasion. They've done a good job of reaching out to the media - back in 2007 when I was on the team, the only reporter we could get to talk to us was a freelance writer who was related to one of our members. Some quick Google searches didn't show anything else that mentioned the incident on the first page, so I don't think that this will be a permanent stain for any of the teams. |
|
#8
|
|||
|
|||
|
Re: [FRC Blog] Orlando Incident
Quote:
Hmm, I don't like a call a ref made, I'ma go whine to my local paper. Do you honestly believe I couldn't spin the facts in a way that could get a sympathetic story in some paper? Every reporter loves a story of a big group negatively impacting children. That sells papers. So, now does FIRST have to address this issue? No. Besides, did FIRST do anything when people on here attack other teams and accuse them of cheating? Or when students are being harassed? Or heck, when volunteers are being harassed? No. They haven't. They've left us out on our own in the past, I don't see why that would change now. |
|
#9
|
||||
|
||||
|
Re: [FRC Blog] Orlando Incident
Quote:
Quote:
And yes, reinspections should include replacing tread on wheels - that is the main part of the robot that interacts with the carpet, and inspectors need to be able to verify that the alteration does not risk significant damage to the carpet. Specifically, if you're attaching it with a pop-rivets, as many teams do, I need to be able to see that the new pop-rivets were installed properly and won't cause an issue. The same could be said of zip ties (where is the head of the zip tie located?) or gluing (are any exposed rims of the wheels properly accounted for? Is the glue dry so it would get all over the field?) or any other attachment method you can think of. These reinspections are not cursory, they are not lighter or less rigorous than the initial inspection. The only difference is the scope - we don't have to worry about the entire robot any more, just the small area where the change was made. |
|
#10
|
||||
|
||||
|
Re: [FRC Blog] Orlando Incident
Quote:
Removing a mechanism present during the original inspection does not trigger a need for re inspection per T8. Adding the ballast to compensate would require reinspection. As a side note reinstalling the mechanism if the ballast + mechanism exceeded the allowed robot weight would probably be against the rules. Last edited by FrankJ : 17-04-2014 at 11:30. |
|
#11
|
|||
|
|||
|
Re: [FRC Blog] Orlando Incident
I missed it? What exactly was the issue with the one robot? Were they out of compliance with robot construction rules, or overweight or something?
|
|
#12
|
||||
|
||||
|
Re: [FRC Blog] Orlando Incident
Quote:
In short... They took off part of their robot and replaced it with 2 FRC batteries to act as ballast. They asked an inspector before they made the modification, and after it was done got reweighed and the inspector said it was all good. They then competed like that in two matches, the opposing alliance challenged it based on their understanding from the rules that having multiple batteries on the robot was illegal, and those involved in the decision (the head ref, FTA, and LRI) were not aware of and had no way to show that the team had passed reinspection - from their point of view, the team competed with an illegal robot, and as a result the alliance was disqualified from the two matches they won, and lost their chance to compete in the semifinals. Read through the thread linked for more information, there are a few posts from the teams involved on both sides,with both alliances unhappy with the eventual outcome. |
|
#13
|
||||
|
||||
|
Re: [FRC Blog] Orlando Incident
Here's my interpretation of the rule.
"If a ROBOT is modified after it has passed Inspection, other than modifications described in T8, that ROBOT must be re-Inspected. " T8 "At the time of Inspection, the ROBOT must be presented with all MECHANISMS (including all COMPONENTS of each MECHANISM), configurations, and decorations that will be used on the ROBOT during the entire competition event. It is acceptable, however, for a ROBOT to play MATCHES with a subset of the MECHANISMS that were present during Inspection. Only MECHANISMS that were present during the Inspection may be added, removed or reconfigured between MATCHES. If MECHANISMS are changed between MATCHES, the reconfigured ROBOT must still meet all Inspection criteria." So, here's a few questions. Does wear and tear on bearings, belts, the stretching of chain, etc count as modification? What about tightening a loose fastener? Making a change to software? Swapping the battery? I sincerely doubt there is a winning alliance anywhere who didn't tighten something or adjust something on their robot between matches. Does that mean that everybody is disqualified? I watched a kid from 118 bend in/adjust the flappy arms on the side of their robot. They did not get reinspected, and no inspector signed a reinspection form. Should they be disqualified too? (I'm not trying to pick on 118, but it was just an example I remember watching. I'm sure every team has done some last minute repairs on their bot during finals) |
|
#14
|
||||
|
||||
|
Re: [FRC Blog] Orlando Incident
Magnets -
Look at it from the perspective of the Robot Rules - if whatever is being done possibly impacts a Robot Rule (from an inspectors perspective), then you need a reinspection. This includes removing item's/material (we need to make sure the removal doesn't create/expose a sharp edge, leave an exposed wire touching the frame, etc), adding items or material (similar concerns as removal, including other concerns like the starting configuration), or performing adjustments to existing items on the robot that have the potential to create an issue (starting configuration, height, safety). So generally speaking, tightening a bolt that has worked its way loose isn't going to be a problem, so long as tightening it does not alter the configuration the robot was inspected in (for example, I can envision a robot design where a bolt can be adjusted to move a piece in or out to alter the configuration, which may expose sharp edges or affect the starting configuration... that would need a reinspection). It is impossible to create a list of what actions do/do not require a reinspection. We trust teams to act in good faith and to generally not make changes at an event that would cause an issue. However, stuff happens, and that's why I always try to have inspectors in high-profile places like queueing and watching the field to help ensure we catch everything as it happens. |
|
#15
|
||||
|
||||
|
Re: [FRC Blog] Orlando Incident
Quote:
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|