View Single Post
  #16   Spotlight this post!  
Unread 07-12-2011, 23:29
Nemo's Avatar
Nemo Nemo is offline
Team 967 Mentor
AKA: Dan Niemitalo
FRC #0967 (Iron Lions)
Team Role: Coach
 
Join Date: Nov 2009
Rookie Year: 2009
Location: Iowa
Posts: 804
Nemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond repute
Re: Custom Vs. COTS Transmissions

Quote:
Originally Posted by sst.thad View Post
If you look at the big blue box under R22 this year, it says that if designs are posted publicly they are allowed to be reused because they are considered cots parts
This has been said repeatedly, but it is false. You are thinking of the following section, which only refers to software:

"Example: A different team develops a similar solution during the fall, and plans to use the developed software on their competition ROBOT. After completing the software, they post it in a generally accessible public forum and make the code available to all teams. Because they have made their software generally available (per the Blue Box in the definition of COTS, it is considered COTS software and they can use it on their ROBOT."

Edit: Maybe I'm wrong. I looked up the COTS definition and found this:

"Example 3: a team obtains openly available design drawings from a professional publication during the pre-season, and uses them to fabricate a gearbox for their ROBOT during the build period following kick-off. The design drawings would be considered a COTS item, and may be used as “raw material” to fabricate the gearbox. The finished gearbox itself would be a FABRICATED ITEM, and not a COTS item.)"

Last edited by Nemo : 07-12-2011 at 23:32.