Example 1: A 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 made during the competition season – was built from detailed designs developed prior to Kickoff.

Example 2: A team developed an omni-directional drive system for the 2019 competition. In July 2019 they refined and improved the control software, written in C++, to add more precision and capabilities. They decided to use a similar system for the CRESCENDO competition. They copied large sections of unmodified code over into the control software of the new ROBOT, also written in C++. This would be a violation of the schedule constraint and is not allowed.

Example 3: The same team decides to use LabVIEW as their software environment for CRESCENDO. Following Kickoff, they use the previously developed C++ code as a reference for the algorithms and calculations required to implement their omni-directional control solution. Because they developed new LabVIEW code as they ported over their algorithms, this is permitted.

Example 4: 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 publicly available before Kickoff, they can use it on their ROBOT.

Example 5: A team develops a transmission prior to Kickoff. After completing the project, they publish the CAD files on a generally accessible public forum and make them available to all teams. Because they have made the design publicly available before Kickoff, they can use the design to create an identical transmission, fabricated after Kickoff, for use on their CRESCENDO ROBOT.