Publicly Shared Pre-Kickoff Code

[pifrc2544]

In accordance with previous FRC policies (rule 4.4.1 R13 of last season's game manual), our team is making its pre-kickoff code publicly available before kickoff so that it can be used by all teams during the build season. The code attached is meant to operate a previously built FRC robot converted into a driveable t-shirt cannon for use at community events and is saved in LabVIEW 2013. The dashboard front panel is rather disorganized, as it was used for testing of various features.

NOTE: File paths saved into the projects are those of the computers that the code was edited and saved on; these may need to be changed for the projects to be used in their current form.

[cgmv123]

Originally Posted by pifrc2544

In accordance with previous FRC policies (rule 4.4.1 R13 of last season's game manual)

We know what R13 is going to be this year:

R13 Software and mechanical/electrical designs created before Kickoff are only permitted if the source files (complete information sufficient to produce the design) are available publicly prior to Kickoff.

[pifrc2544]

You are correct, cgmv123; it is the only rule made available prior to Kickoff at www.usfirst.org/roboticsprograms/frc/blog-some-tidbits-before-kickoff.

[tcjinaz]

Originally Posted by pifrc2544

In accordance with previous FRC policies (rule 4.4.1 R13 of last season's game manual), our team is making its pre-kickoff code publicly available before kickoff so that it can be used by all teams during the build season. The code attached is meant to operate a previously built FRC robot converted into a driveable t-shirt cannon for use at community events and is saved in LabVIEW 2013. The dashboard front panel is rather disorganized, as it was used for testing of various features.

NOTE: File paths saved into the projects are those of the computers that the code was edited and saved on; these may need to be changed for the projects to be used in their current form.

Thanks for sharing something I can read. There are code releases out there that are dependent on FRC2015 LabView. Which leads to this question:

If code made "available publicly prior to Kickoff" is unreadable by any team not in the control system Beta program truly "complete information sufficient to produce the design"? I'll grant the semantic analysis that says the rule was honored; I'm looking for a discussion of the intent of the rule.

Tim

[Qbot2640]

Excellent idea. Our 2014 code was certainly nothing special - but we do not have much programming experience this year, so it may be helpful to be able to build on last year's code. Of course, anyone who can use something here is welcome!