Quote:
Originally Posted by BigJ
I would argue that CAD designs "made public" should also count as COTS.
|
I agree with your assertion in principle simply because it is consistent, but let's be honest, posting software for others to use is much more beneficial to others than posting a mechanical CAD design.
The software may be used by almost anyone; even if it is posted for a language/environment your team does not use. Algorithms and data structures can be translated. Moreover, even if the software runs on a platform other than the cRIO, the platform is very likely available to you (*).
The benefit to other teams if you post your CAD files is predicated on the other teams having access to the same manufacturing facilities as yours. A design of a custom chassis that requires access to a laser cutter, a turret punch, and a CNC brake does not help most other teams. In fact, I'd go as far as to say that posting the CAD design largely benefits the team posting the design since they'd be able to re-use it and others with similar capabilities would do their own thing.
-Scott
(*) If the software runs on a device that is a custom circuit, the rules
that the custom circuit must be fabricated during the build season (assuming the Gerbers, schematics, and other files were posted to make them COTS too). The lead times for affordable PCB manufacture and assembly make this difficult, and that practicality leads implementation towards COTS computing platforms such as the Raspberry PI, BeagleBone, Arduino, etc.