Go to Post Yes, a big part of FIRST is learning from others. But a just as important part of FIRST is learning from discovery. - [more]
Home
Go Back   Chief Delphi > FIRST > General Forum
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Reply
Thread Tools Rating: Thread Rating: 19 votes, 5.00 average. Display Modes
  #1   Spotlight this post!  
Unread 03-16-2015, 03:35 PM
Cory's Avatar
Cory Cory is offline
Registered User
AKA: Cory McBride
FRC #0254 (The Cheesy Poofs)
Team Role: Engineer
 
Join Date: May 2002
Rookie Year: 2001
Location: Redwood City, CA
Posts: 6,785
Cory has a reputation beyond reputeCory has a reputation beyond reputeCory has a reputation beyond reputeCory has a reputation beyond reputeCory has a reputation beyond reputeCory has a reputation beyond reputeCory has a reputation beyond reputeCory has a reputation beyond reputeCory has a reputation beyond reputeCory has a reputation beyond reputeCory has a reputation beyond repute
Send a message via AIM to Cory
Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams

A Q&A was posted as a spinoff from the ramps thread to clarify whether it would be legal to give other teams fabricated parts/assemblies that were 1) bagged with the giving team's robot at a previous event 2) brought into the event as part of the giving team's witholding allowance, or 3) fabricated at the event by the giving team.

That Q&A has been answered and seems to set a dangerous precedent that is contrary to FIRST's goals.

Things that are now seemingly illegal:
  • Providing a battery to another team with leads installed (maybe not...the rules state that such assemblies do not have to be part of a witholding allowance and can be made prior to the start of the 6 week build season...but there is no specific exemption that says they do not count as ASSEMBLIES made by a giving team, per the Q&A response).
  • Loaning an assembled COTS transmission to another team (versaplanetary, AM planetary, toughbox, etc)
  • Loaning any motor with leads soldered to it or terminals attached to integral leads
  • Loaning a speed controller with terminals attached to the output side
  • Loaning a speed controller which has had the leads shortened
  • Loaning any COTS item that has been modified (gear, sprocket, spacer, etc)
  • Loaning a pneumatic cylinder with fittings attached
  • Any part fabricated solely by the FIRST provided machine shop at the event (yeah, that sounds alarmist, but that Q&A specifically states that any fabricated part at the event that goes on their ROBOT must be fabricated by that team)
  • Any part made by a giving team that brings portable drill presses/bandsaws/sanders/lathes/mills in their pit

That's just the list of things I could think of in about a minute. I'm sure there's countless other things you could add to it. Examples from previous years would include premade bumper segments for use by teams with non-compliant bumpers, or as Karthik has pointed out, making bumpers entirely for another team at the event.

It seems really hard to believe FIRST actually wants to be as harsh as they have indicated they will be. The easy answer is "stop lawyering the rules, clearly FIRST doesn't want to ban teams from loaning out the reasonable things listed above", but unfortunately the blanket statement as applied in the Q&A ruling makes that necessary.

Last year Team 1678 had an inbounder assist device they worked to modify many partners with to increase their ability to contribute to an alliance. They were widely (and rightfully) hailed for helping teams be competitive on the field. Other teams loaned spare shot blockers to their third partners in eliminations. In 2013 teams loaned out full court shooter blockers. There are plenty of other examples of teams loaning assemblies or fabricated parts to their partners (who can later become their opponents) going back to the beginning of FIRST.

I can understand if FIRST wanted to avoid a situation where a third partner on an eliminations alliance is asked to sit in a corner with a ramp tethered to them...but the answer they gave seems far too draconian and will only serve to further widen the gap between struggling teams and high performing teams. At the same time, FIRST also should not have created a game which basically encourages two high performing teams to either turn their third partner into a paperweight or take them off the field entirely.
__________________
2001-2004: Team 100
2006-Present: Team 254
Reply With Quote
  #2   Spotlight this post!  
Unread 03-16-2015, 03:39 PM
notmattlythgoe's Avatar
notmattlythgoe notmattlythgoe is offline
Flywheel Police
AKA: Matthew Lythgoe
FRC #2363 (Triple Helix)
Team Role: Mentor
 
Join Date: Feb 2010
Rookie Year: 2009
Location: Newport News, VA
Posts: 1,712
notmattlythgoe has a reputation beyond reputenotmattlythgoe has a reputation beyond reputenotmattlythgoe has a reputation beyond reputenotmattlythgoe has a reputation beyond reputenotmattlythgoe has a reputation beyond reputenotmattlythgoe has a reputation beyond reputenotmattlythgoe has a reputation beyond reputenotmattlythgoe has a reputation beyond reputenotmattlythgoe has a reputation beyond reputenotmattlythgoe has a reputation beyond reputenotmattlythgoe has a reputation beyond repute
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams

Quote:
The easy answer is "stop lawyering the rules..."
This, this, and so much more this. All it does is lead to a very confusing and super strict ruleset.
Reply With Quote
  #3   Spotlight this post!  
Unread 03-16-2015, 03:43 PM
wireties's Avatar
wireties wireties is offline
Principal Engineer
AKA: Keith Buchanan
FRC #1296 (Full Metal Jackets)
Team Role: Mentor
 
Join Date: Jan 2006
Rookie Year: 2004
Location: Rockwall, TX
Posts: 1,168
wireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond repute
Send a message via AIM to wireties
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams

Quote:
Originally Posted by Cory View Post
[*]Providing a battery to another team with leads installed
Yikes, the team behind us in the pits played with our batteries all weekend! And we recharged batteries between matches for them.
__________________
Fast, cheap or working - pick any two!
Reply With Quote
  #4   Spotlight this post!  
Unread 03-16-2015, 03:43 PM
mwmac's Avatar
mwmac mwmac is offline
JWBWIFWWWADD
AKA: Mike MacLean
FRC #2122 (Team Tators)
Team Role: Mentor
 
Join Date: Apr 2011
Rookie Year: 2008
Location: "Wasteland", Idaho
Posts: 657
mwmac has a reputation beyond reputemwmac has a reputation beyond reputemwmac has a reputation beyond reputemwmac has a reputation beyond reputemwmac has a reputation beyond reputemwmac has a reputation beyond reputemwmac has a reputation beyond reputemwmac has a reputation beyond reputemwmac has a reputation beyond reputemwmac has a reputation beyond reputemwmac has a reputation beyond repute
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams

Could not agree more. What happened to the notion of no robot left behind? RIPBumpbox! https://www.youtube.com/watch?v=Ofefwcw56Ow
__________________
2016 Carson W 2122, 2052, 3538, 41, AZ North W 2122, 125, 498, MQA, Idaho F 2122, 3250, 3513, MQA, CCC W 2122, 9122, 6174, ICA
2015 Tesla SF IDA 2122, 3360, 2960, 1311 IRI SF 2338, 2122, 107, 234 UT F 2122, 3230, 3405, EEA, WFFA, AZ West W 2122, 3309, 5059, ICA
2014 Galileo QF 1717, 2122, 3683, 193 UT W 2122, 2996, 3191, ICA, CCC W 1678, 2122, 9073, ICA
2013 CalGames W 2122, 1678, 4171, Judges Award
2012 Newton QF 2122, 610, 488 Spokane W 2122, 1983, 4082, EEA
2011 Newton SF 1730, 2122, 11 IRI F 3138, 16, 2122, 1730, UT W 2122, 399, 3239, MQA, Seattle F 2122, 488, 2850, MQA
2010 Galileo SF 78, 51, 2122 UT W 1696, 2122, 3405, IDA, Sacramento F 2122, 2035, 1834, IDA,
2009 Sacramento F 2144, 692, 115, 2122, MQA
2008 Newton Sacramento W 2122, 1662, 115, CA
2007 PNW Regional Highest Rookie Seed
"Enjoying traveling to more distant events" since 2007
Reply With Quote
  #5   Spotlight this post!  
Unread 03-16-2015, 03:44 PM
Cory's Avatar
Cory Cory is offline
Registered User
AKA: Cory McBride
FRC #0254 (The Cheesy Poofs)
Team Role: Engineer
 
Join Date: May 2002
Rookie Year: 2001
Location: Redwood City, CA
Posts: 6,785
Cory has a reputation beyond reputeCory has a reputation beyond reputeCory has a reputation beyond reputeCory has a reputation beyond reputeCory has a reputation beyond reputeCory has a reputation beyond reputeCory has a reputation beyond reputeCory has a reputation beyond reputeCory has a reputation beyond reputeCory has a reputation beyond reputeCory has a reputation beyond repute
Send a message via AIM to Cory
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams

Quote:
Originally Posted by notmattlythgoe View Post
This, this, and so much more this. All it does is lead to a very confusing and super strict ruleset.
So do you intend to lend any of the items I've listed to other teams? If so, please explain how you feel your team will not be breaking the rules, as written?
__________________
2001-2004: Team 100
2006-Present: Team 254
Reply With Quote
  #6   Spotlight this post!  
Unread 03-16-2015, 03:45 PM
Andrew Schreiber Andrew Schreiber is offline
Data Nerd
FRC #0079
 
Join Date: Jan 2005
Rookie Year: 2000
Location: Misplaced Michigander
Posts: 4,055
Andrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond repute
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams

Quote:
Originally Posted by Cory View Post
I can understand if FIRST wanted to avoid a situation where a third partner on an eliminations alliance is asked to sit in a corner with a ramp tethered to them...but the answer they gave seems far too draconian and will only serve to further widen the gap between struggling teams and high performing teams. At the same time, FIRST also should not have created a game which basically encourages two high performing teams to either turn their third partner into a paperweight or take them off the field entirely.
Not only is it mildly draconian, I'd argue that the Q&A response is BARELY supported by the rules. Saying it's a violation of R1 is pretty much invoking the "I'll know it when I see it" defense.

What draws the line? — "Well, the other team's student put in a rivet on this part, so they helped build it AT the event." It's unenforceable and can only lead to more stupid calls.

If FIRST doesn't like the fact that their game encourages bad behavior like that... well, I hope they learn their lesson for next year.



Edit: How will I lend those items to other teams without breaking the rule? I won't, I'll just break the rule and clear it with the LRI prior doing it.
__________________




.

Last edited by Andrew Schreiber : 03-16-2015 at 03:47 PM.
Reply With Quote
  #7   Spotlight this post!  
Unread 03-16-2015, 03:46 PM
Thad House Thad House is online now
Volunteer, WPILib Contributor
no team (Waiting for 2021)
Team Role: Mentor
 
Join Date: Feb 2011
Rookie Year: 2010
Location: Thousand Oaks, California
Posts: 1,070
Thad House has a reputation beyond reputeThad House has a reputation beyond reputeThad House has a reputation beyond reputeThad House has a reputation beyond reputeThad House has a reputation beyond reputeThad House has a reputation beyond reputeThad House has a reputation beyond reputeThad House has a reputation beyond reputeThad House has a reputation beyond reputeThad House has a reputation beyond reputeThad House has a reputation beyond repute
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams

This could get ugly real quick. That seems like a catch all that has much higher implementations then FIRST expected.

Also, the thing about lawyering the rules is that it kind of has to be done, especially with the way Q&A likes to answer. If they would give straightforward answers, maybe there would be less lawyering.
__________________
All statements made are my own and not the feelings of any of my affiliated teams.
Teams 1510 and 2898 - Student 2010-2012
Team 4488 - Mentor 2013-2016
Co-developer of RobotDotNet, a .NET port of the WPILib.
Reply With Quote
  #8   Spotlight this post!  
Unread 03-16-2015, 03:50 PM
Brandon Holley's Avatar
Brandon Holley Brandon Holley is offline
Chase perfection. Catch excellence.
AKA: Let's bring CD back to the way it used to be
FRC #0125 (NU-TRONs, Team #11 Alumni (GO MORT))
Team Role: Engineer
 
Join Date: Jan 2004
Rookie Year: 2001
Location: Boston, MA
Posts: 2,590
Brandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond repute
Send a message via AIM to Brandon Holley
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams

Some of the most inspirational in-competition moments have occurred from loaning parts/assemblies. I know we personally have helped dozens of our elimination alliance partners in the past enhance capability, whether it be through speeding up intake mechanisms, autonomous changes, added structural support or even sometimes completely new mechanisms.

What I do not understand is the ridiculous emphasis on mechanical components. This is why I feel the ruling is not promoting the intent/underlying message of the rule it is trying to enforce. If we essentially didn't want other team's intellectual property on another teams robot- then this rule would also apply to software, or sensor integration. Instead its focused purely on spare parts and components?

I feel that sometimes the baby is tossed with the bath water in these rulings. Everyone jumps to the powerhouses of the world trying to add to their alliances firepower. What about the rookie team who arrives with nothing but a box of parts? Well if we followed the letter of the rule, this team may have a tough time gathering the components necessary to take the field.

Why is it an issue for a team with additional resources to try to enhance the capability of their potential partners (or even opponents)?


This is just a big departure from what I've come to expect from FRC teams at events. The collaboration sometimes is the best part.
__________________
MORT (Team 11) '01-'05 :
-2005 New Jersey Regional Chairman's Award Winners
-2013 MORT Hall of Fame Inductee

NUTRONs (Team 125) '05-???
2007 Boston Regional Winners
2008 & 2009 Boston Regional Driving Tomorrow's Technology Award
2010 Boston Regional Creativity Award
2011 Bayou Regional Finalists, Innovation in Control Award, Boston Regional Finalists, Industrial Design Award
2012 New York City Regional Winners, Boston Regional Finalists, IRI Mentor of the Year
2013 Orlando Regional Finalists, Industrial Design Award, Boston Regional Winners, Pine Tree Regional Finalists
2014 Rhode Island District Winners, Excellence in Engineering Award, Northeastern University District Winners, Industrial Design Award, Pine Tree District Chairman's Award, Pine Tree District Winners
2015 South Florida Regional Chairman's Award, NU District Winners, NEDCMP Industrial Design Award, Hopper Division Finalists, Hopper/Newton Gracious Professionalism Award
Reply With Quote
  #9   Spotlight this post!  
Unread 03-16-2015, 03:52 PM
Kris Verdeyen's Avatar
Kris Verdeyen Kris Verdeyen is offline
LSR Emcee/Alamo Game Announcer
FRC #0118 (Robonauts)
Team Role: Engineer
 
Join Date: Jun 2001
Rookie Year: 2001
Location: Houston, TX
Posts: 696
Kris Verdeyen has a reputation beyond reputeKris Verdeyen has a reputation beyond reputeKris Verdeyen has a reputation beyond reputeKris Verdeyen has a reputation beyond reputeKris Verdeyen has a reputation beyond reputeKris Verdeyen has a reputation beyond reputeKris Verdeyen has a reputation beyond reputeKris Verdeyen has a reputation beyond reputeKris Verdeyen has a reputation beyond reputeKris Verdeyen has a reputation beyond reputeKris Verdeyen has a reputation beyond repute
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams

Quote:
Originally Posted by notmattlythgoe View Post
This, this, and so much more this. All it does is lead to a very confusing and super strict ruleset.
Don't hate the player, hate the game.

This is something we've done for years. Encouraging well-established and -funded teams to help struggling teams has been called out as the point of, among other things: the alliance system, the serpentine draft, and the chairman's award. It's not "lawyering" to wonder if this is what FRC wants us to stop.

Maybe this goes hand in hand with a game that makes it hard for an alliance's merely mobile third member to contribute meaningfully? If a robot that doesn't move is more valuable than one that does, are the established teams off the hook?
__________________
...Only a few people are awake and they live in a state of constant total amazement. -JP Shanley, Joe vs. the Volcano
Reply With Quote
  #10   Spotlight this post!  
Unread 03-16-2015, 03:54 PM
Libby K's Avatar
Libby K Libby K is offline
Always a MidKnight Inventor.
FRC #1923 (The MidKnight Inventors)
Team Role: Mentor
 
Join Date: Mar 2006
Rookie Year: 1992
Location: West Windsor, NJ
Posts: 1,578
Libby K has a reputation beyond reputeLibby K has a reputation beyond reputeLibby K has a reputation beyond reputeLibby K has a reputation beyond reputeLibby K has a reputation beyond reputeLibby K has a reputation beyond reputeLibby K has a reputation beyond reputeLibby K has a reputation beyond reputeLibby K has a reputation beyond reputeLibby K has a reputation beyond reputeLibby K has a reputation beyond repute
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams

The best stories that come out of FIRST events are teams helping each other succeed. Looks (from this Q&A) like FIRST wants to squash that?! I don't like this one at all. Teams that, as Cory said, were previously hailed for being so helpful are now risking getting in trouble for their incredible work within their community.

I really, sincerely hope they revisit the intent behind this wording.
__________________
Libby Kamen
Team 1923: The MidKnight Inventors
2006-2009: Founder, Captain, Operator, Regional Champion.
2010-Always: Proud Alumni, Mentor & Drive Coach. 2015 Woodie Flowers Finalist Award.

-
229: Division By Zero / 4124: Integration by Parts
2010-2013: Clarkson University Mentor for FLL, FTC & FRC

-
FIRST Partner Associate, United Therapeutics
#TeamUnither | facebook, twitter & instagram | @unitherFIRST

-
questions? comments? concerns? | twitter: @libbyk | about.me/libbykamen
Reply With Quote
  #11   Spotlight this post!  
Unread 03-16-2015, 03:54 PM
FrankJ's Avatar
FrankJ FrankJ is offline
Robot Mentor
FRC #2974 (WALT)
Team Role: Mentor
 
Join Date: Feb 2011
Rookie Year: 2009
Location: Marietta GA
Posts: 1,886
FrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond repute
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams

I see you point but it is a little alarmist.

  • Batteries are not part of the robot.
  • Assembled transmissions. Technically correct. Hopefully inspectors will be rational.
  • leads on motor controllers/motors are allowed while maintaining their cots status.
  • Nasa machine shop /team shops would presumably working with team input: legal parts.

Without the rule being like it is... A far sited mega team could bring in 2 40 lb ramp manipulators complete with can motor controllers in their bagged allotment in addition to their 120 lb robot. Strip the 2nd pick donor bot add the ramps, connect the canbus and power to the donor bot, load new software in the RoboRio & have a ramp bot that the 3rd team had nothing to do with. Probably not GP. I am not suggesting that a team would do this.

Teams helping other teams are so ingrained in First culture I don't see this as being aimed at that.
__________________
If you don't know what you should hook up then you should read a data sheet

Last edited by FrankJ : 03-16-2015 at 03:59 PM.
Reply With Quote
  #12   Spotlight this post!  
Unread 03-16-2015, 03:58 PM
Jon Stratis's Avatar
Jon Stratis Jon Stratis is offline
Electrical/Programming Mentor
FRC #2177 (The Robettes)
Team Role: Mentor
 
Join Date: Feb 2007
Rookie Year: 2006
Location: Minnesota
Posts: 3,720
Jon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond repute
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams

Apparently I don't read the ruling at all the way you did. Let's break it down...

Quote:
A. R1 (R15, R17 & T7 may also apply) is specific that the ROBOT that a team uses in competition was built by that team.
This seems like a rather obvious statement that in no way changes how anything is ruled.

Quote:
R1 A Team must submit their ROBOT for Inspection. The ROBOT must be built by the FRC Team to perform specific tasks when competing in RECYCLE RUSH. The ROBOT must include all of the basic systems required to be an active participant in the game – power, communications, control, and movement. The ROBOT implementation must obviously follow a design approach intended to play RECYCLE RUSH (e.g. a box of unassembled parts placed on the FIELD, or a ROBOT designed to play a different game does not satisfy this definition).
This is just a restatement of R1, nothing new or earth shattering here.

Quote:
We strongly encourage you to provide support to all teams (especially those with limited resources) at your events, whether that is helping fabricate elements, assisting in construction, assisting in writing software or development of game strategy.
Clearly stated that you can help teams at events, no big surprise - this is something we actively encourage just to get everyone on the field and moving!
Quote:
As always, teams may work on their ROBOT while at events during the time that the pits are open per R15. Withholding allowance is determined at the time that team loads in per R17. No other FABRICATED PARTS may be brought into the venue after that time.
This makes sense, and I hope everyone recognizes that this has always been the case.
Quote:
Elements and assemblies built at the event by one team to give to another do not satisfy R1 above.
This might be where you have a problem with the answer. What they're saying here is that my team can't build something, hand it to your team and say "put this on your robot so you can now do X." It's easy to take that to extremes... But combined with the previous statement about helping teams it's clear that it shouldn't be taken to extremes. I can help you by giving you a COTS part, even if there may have been a slight modification or two (like attaching connectors, assembling a gearbox in the standard, intended way, etc). In that case I'm not building anything, I'm giving you a COTS part that may be slightly used. But I can't build a ramp and give it to you to attach to your robot. I can't give you a specially designed winch to use to lift totes. That's going way, WAY beyond helping by supplying a few COTS pieces.

Quote:
Please remember that the addition of any item to any ROBOT requires re-Inspection prior to any MATCH in which that ROBOT competes per T10. That re-Inspection also requires an update to the team's BOM reflecting the the change in ROBOT parts.
Reinspection is a well known aspect of competition, even if teams sometimes forget about it.
Quote:
So, to answer your questions by number: 1) No. 2) No. 3) No, but you may certainly assist another team in building new parts for their ROBOT at the event, and we encourage that.
Please note that, per this year's rules (for batteries) and last year's (for bumpers), batteries and bumpers are not part of the robot. That exempts them from a lot of rules, like being included in the withholding allowance or needing to be constructed after kickoff.

Keep in mind that it's ALWAYS been legal to have others machine stuff for you - you can give a CAD file to a machine shop during the season and collect parts later for use in the robot. How is that different than utilizing a machine shop at an event, or a team's tabletop bandsaw?
__________________
2007 - Present: Mentor, 2177 The Robettes
LRI: North Star 2012-2016; Lake Superior 2013-2014; MN State Tournament 2013-2014, 2016; Galileo 2016; Iowa 2017
2015: North Star Regional Volunteer of the Year
2016: Lake Superior WFFA
Reply With Quote
  #13   Spotlight this post!  
Unread 03-16-2015, 03:59 PM
Nate Laverdure's Avatar
Nate Laverdure Nate Laverdure is offline
Registered User
FRC #2363
Team Role: Coach
 
Join Date: Apr 2005
Rookie Year: 1999
Location: Newport News, VA
Posts: 831
Nate Laverdure has a reputation beyond reputeNate Laverdure has a reputation beyond reputeNate Laverdure has a reputation beyond reputeNate Laverdure has a reputation beyond reputeNate Laverdure has a reputation beyond reputeNate Laverdure has a reputation beyond reputeNate Laverdure has a reputation beyond reputeNate Laverdure has a reputation beyond reputeNate Laverdure has a reputation beyond reputeNate Laverdure has a reputation beyond reputeNate Laverdure has a reputation beyond repute
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams

Quote:
Originally Posted by FrankJ View Post
Nasa machine shop /team shops would presumably working with team input: legal parts.
Just recognize all teams as sponsors of all other teams. <R11>, baby.
Reply With Quote
  #14   Spotlight this post!  
Unread 03-16-2015, 04:05 PM
SenorZ's Avatar
SenorZ SenorZ is offline
Physics Teacher
AKA: Tom Zook
FRC #4276 (Surf City Vikings)
Team Role: Teacher
 
Join Date: Jan 2011
Rookie Year: 2011
Location: Huntington Beach, California
Posts: 888
SenorZ has a reputation beyond reputeSenorZ has a reputation beyond reputeSenorZ has a reputation beyond reputeSenorZ has a reputation beyond reputeSenorZ has a reputation beyond reputeSenorZ has a reputation beyond reputeSenorZ has a reputation beyond reputeSenorZ has a reputation beyond reputeSenorZ has a reputation beyond reputeSenorZ has a reputation beyond reputeSenorZ has a reputation beyond repute
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams

I see this being a correct ruling for the following example:

Team A is a high seeded alliance, and picks team B to be their 3rd alliance partner in the elims. Team A then sends their pit crew to team B's pit and adds components that team A built, so that team B can do what team A wants.

I've seen this happen, and I think THAT is against the spirit of FIRST. Essentially it is one team making a second robot on top of another team's chassis. This is very RARE, but I feel it is wrong.
__________________
2013-present: FRC Team 4276, Surf City Vikings
2011-2012: FRC Team 3677, The Don Bots
Reply With Quote
  #15   Spotlight this post!  
Unread 03-16-2015, 04:05 PM
Brandon Holley's Avatar
Brandon Holley Brandon Holley is offline
Chase perfection. Catch excellence.
AKA: Let's bring CD back to the way it used to be
FRC #0125 (NU-TRONs, Team #11 Alumni (GO MORT))
Team Role: Engineer
 
Join Date: Jan 2004
Rookie Year: 2001
Location: Boston, MA
Posts: 2,590
Brandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond repute
Send a message via AIM to Brandon Holley
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams

Quote:
Originally Posted by Jon Stratis View Post
This might be where you have a problem with the answer. What they're saying here is that my team can't build something, hand it to your team and say "put this on your robot so you can now do X." It's easy to take that to extremes... But combined with the previous statement about helping teams it's clear that it shouldn't be taken to extremes. I can help you by giving you a COTS part, even if there may have been a slight modification or two (like attaching connectors, assembling a gearbox in the standard, intended way, etc). In that case I'm not building anything, I'm giving you a COTS part that may be slightly used. But I can't build a ramp and give it to you to attach to your robot. I can't give you a specially designed winch to use to lift totes. That's going way, WAY beyond helping by supplying a few COTS pieces.
I guess this is where the debate will diverge for people. To me, you've made a lot of assumptions in here about COTS parts, slightly modified COTS parts that are not outlined by a rule somewhere.

Why is the mechanical structure the end all be all? A can hook could be as simple as a tube with a bent piece of sheet metal on it. What about the software to control it in both teleop and autonomous? There is often a lot more work than 'here put this on' even if a team was given a complete mechanical solution.

I'm not condoning the above action, I just think the trivialization of integrating even the most simple mechanisms is a little much.

-Brando
__________________
MORT (Team 11) '01-'05 :
-2005 New Jersey Regional Chairman's Award Winners
-2013 MORT Hall of Fame Inductee

NUTRONs (Team 125) '05-???
2007 Boston Regional Winners
2008 & 2009 Boston Regional Driving Tomorrow's Technology Award
2010 Boston Regional Creativity Award
2011 Bayou Regional Finalists, Innovation in Control Award, Boston Regional Finalists, Industrial Design Award
2012 New York City Regional Winners, Boston Regional Finalists, IRI Mentor of the Year
2013 Orlando Regional Finalists, Industrial Design Award, Boston Regional Winners, Pine Tree Regional Finalists
2014 Rhode Island District Winners, Excellence in Engineering Award, Northeastern University District Winners, Industrial Design Award, Pine Tree District Chairman's Award, Pine Tree District Winners
2015 South Florida Regional Chairman's Award, NU District Winners, NEDCMP Industrial Design Award, Hopper Division Finalists, Hopper/Newton Gracious Professionalism Award
Reply With Quote
Reply


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 02:48 AM.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi