|
#1
|
||||
|
||||
|
Inspection Stories
There was a 2012 thread for this, but I didn't want to necro-post it.
As inspectors, our goal is to get all teams on the field with a legal robot that meets the rules. Sometimes, this requires herculean efforts by the inspection team and the valued and experienced mentors and students that will work with another team's robot with no notice, to make sure everyone gets a chance to compete. Inspectors, what are the crazy things you've dealt with at events? Please share your "war stories" below. |
|
#2
|
|||
|
|||
|
Re: Inspection Stories
Quote:
Team member: Oh, one of those black ones. Me: Oh, a CIM? can I see it? TM: Uh, well, it's all sealed up in the device and kind of hard to get to. It looks just like that motor from the kit, though. Me: Does it look like the motor or is it the motor? Does it have any of these part numbers on it? TM: It's the one that came in the thing. Its from the same motor manufacture and looks like its the right size, so it's close enough, right? Me: ... What ensued was a long meeting with the LRI, me and the team. I don't know what the final call was. we were behind on inspections so I went to look at other teams. They did eventually passed inspection, but I never figured out if they swapped in a legal motor, if the one in the device turned out to be genuinely legal or if the LRI just let it go. It did look legal... Besides that, I think 98% of inspection issues have been about bumpers. No one likes hearing about bumpers not passing, so I'll save those stories. |
|
#3
|
||||
|
||||
|
Re: Inspection Stories
2013 our team used copper tube from the compressor to reduce the chance of heat affecting the vinyl tubing. After the first 6 inches or 1st fitting we used the vinyl. We passed inspection initially then our inspection was revoked. The head person of the event (not inspector) said it was illegal. Could not cite a section in the rule book as to why since it was the proper size and was not unsafe. They made us change it. We changed it and then saw two more robots with the same setup who also passe inspection. They made them change it after we mentioned the other teams. We felt bad pointing out the others but felt it was wrong that we had to change something that was perfectly safe and not illegal in the rules book.
|
|
#4
|
|||
|
|||
|
Re: Inspection Stories
My inspection war stories are coming from a team mentor's perspective, wondering why the inspection takes over an hour when the robot is 100% legal, beautifully wired, and passed at its prior event. Some inspectors just want to chit chat, and others are not familiar with common FRC parts. And then there was the one that had an issue with our bumper pins not being robust enough. After my students refused to change it, and called over the head inspector, lifted the robot by its bumpers, then swiftly kicked it in the side, we were finally passed on it.
They really need to stop hassling 15+ year veteran teams who know what they are doing, and focus on the rookies who need the help. |
|
#5
|
||||
|
||||
|
Re: Inspection Stories
Last year I had to inform a 2nd year team that they had to rewire all of their 40 amp circuits because they were all done with 14 AWG wire. It killed me to do it. Much of their wiring was inaccessible, but the kids took it in stride and had it done 5 minutes before pits closed that night.
|
|
#6
|
||||
|
||||
|
Re: Inspection Stories
Quote:
However, veteran team status does not equal "always complies with all rules". Team leadership changes, both on the student and mentor side. I've called teams with three digit numbers on (admittedly small, yet important nonetheless) items. I've had teams recently in the high 1000s with illegal motors or fans, and teams with low 4000s numbers with massive frame issues. Lastly, passing at a prior event is not evidence of passing at this event. Lots of things can happen in the 6 hour rush of unbag time (for district events), and sometimes inspectors just miss things. EDIT to say that all LRIs would be happy to welcome experienced mentors to help, even if it's only for a few hours during unbag/initial inspection. Last edited by engunneer : 24-01-2017 at 14:59. |
|
#7
|
||||
|
||||
|
Re: Inspection Stories
I'm reasonably certain that I inspected that same team at a later event. They had managed to pass at a previous event with a wacky linear actuator that had an integrated motor. It was not clear if they had disabled it at the previous event, but the team seemed to expect they could use it. I asked them to remove it entirely and find a different way to do the same job, but I think now it should have been ok to let them keep it as a structural member of the robot as long as the wires were never plugged in to anything (though i think an unplugged illegal motor still counts as a motor)
|
|
#8
|
||||
|
||||
|
Re: Inspection Stories
From a team's perspective: My sophomore year of high school our robot was made out of steel. At CVR that year (the first year the event took place, 2012), we got 95% of the way through inspection until one of the inspectors noticed that our frame had current going through it. We looked through the entire robot's electronics, and nothing was contacting the frame. Every piece was isolated. We took apart and rerouted all of our electronics, several inspectors had come by and tried their hand at it, even some of the control systems people from other teams tried their hand at it. It all looked perfectly okay, but the frame still had a charge. They eventually passed us telling us to keep an eye out and the robot worked normally the rest of the event.
|
|
#9
|
||||
|
||||
|
Re: Inspection Stories
Quote:
15 year old teams aren't immune to making mistakes, sorry to tell you. They also aren't immune to turnover - losing one or two key people can send you from being division finalists at champs one year to ranking in the bottom half at both of your regionals the next, with a robot that barely works. I've seen it happen. |
|
#10
|
||||
|
||||
|
Re: Inspection Stories
Quote:
It's all part of, as a volunteer, putting the team experience at events as the top priority, and treating teams fairly while assuming good faith. Just something we all have to keep in mind when inspecting (and I'm sure the vast majority of inspectors do!). |
|
#11
|
||||
|
||||
|
Re: Inspection Stories
Quote:
![]() |
|
#12
|
||||
|
||||
|
Re: Inspection Stories
Quote:
Chris makes a good point though - one that I've seen happen often out in California. Some inspectors out here seem to like giving certain teams a hard time for no better reason other than the fact that they're different from other teams. I was always confused as a student why my barely functioning team flew through inspection at most* events, and while the very well put together team in the pit right next to us (back when pits were in numerical order) was being harassed by an inspector. *see above post of mine for exception |
|
#13
|
|||
|
|||
|
Re: Inspection Stories
Quote:
Also, to jump the gun a bit here, I would say that diligence on the part of the inspector is a service to both the team and the event. For the event, it is making things safer and more consistent. For the team, it's judging the robot's compliance with the rules at a higher level of scrutiny. So long as the inspector isn't inventing rules, I think we should all appreciate attention to detail. |
|
#14
|
||||
|
||||
|
Re: Inspection Stories
This is way snarkier than the post deserved. Clearly his intention isn't to laugh at students, but to allow the students to experience a small, but not crippling, failure and to learn how to deal with the situation. Allowing students to fail in a controlled way is one of many valid approaches to mentoring. It's not like he's erasing parts of the game manual so kids can't read it or something, just not catching every single small mistake the kids make.
|
|
#15
|
||||
|
||||
|
Re: Inspection Stories
Quote:
Quote:
![]() |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|