Ethical dilemma? You decide.

[BJC]

A lot of teams walk this fine line every year. Many of them are very respected and well-known teams, all have very respectable people on them, and none of whom I would consider to be "cheaters". No matter what is said in this thread, however, it is ultimately your decision what to do. My Advice: Do what would make your grandmother proud.

Sincerely, Bryan Culver

[Tristan Lall]

Strictly speaking, isn't the CNC program the design of the process used to create the robot part, rather than necessarily an element of the design of the part itself? I grant that the design of the part and the design of the CNC program might certainly be codependent, but fundamentally, they're separate things. Completion of one does not necessarily imply completion of the other—it would be quite reasonable to contend that the design of the part depends on the lessons learned from the implementation of the CNC program, and that the "final design" of the part is incomplete until the results of a trial run are analyzed and deemed satisfactory.

And although FIRST hasn't said so explicitly, I give serious credence to the idea that the robot rules must be assumed to only apply to actual parts of the robot, unless otherwise specified. (If you read the LabView example as applying to non-robot code, it opens up a world of unenforceable insanity.)

Put another way, logically, if you were to instantiate the part design, you'd get the part. But if you instantiate the CNC program, you get a machine following a toolpath—and maybe a part as well, but only if you decided to cut metal (or whatever the part is made of) rather than thin air.

And in any event, like Chris and Cory said: if you're still uncomfortable, make any one tiny geometric change, and it's unambiguously no longer the same part. (The old part can rightly be called a prototype, if you happened to make any. Don't use the prototypes in competition.)

Following my own chain of reasoning, I disagree that posting it publicly would be a remedy under the rules—stuff that isn't part of the robot has no particular reason to be (or to become) COTS.

Aside: See here....

[Al Skierkiewicz]

Example: The same TEAM realizes that the transmission designed and built in the fall perfectly fits their need for a transmission to drive the ROBOT arm. They build an exact copy of the transmission from the original design plans, and bolt it to the ROBOT. This would be prohibited, as the transmission – although fabricated during the competition season – was built from detailed designs developed prior to kick-off.

This would seem to say it all in your case, substituting "code" for "plans". As Cory has said, a little examination of the CNC code will show that some improvements can be made in the code. You can move things around, make more efficient use of programming space, etc. The skills are already there, this could be a great opportunity for your students to practice and learn.