Time to build cRIO LabVIEW code

[Dave Scheck]

I would also like to voice my concerns.

There were two occasions at MWR where we were helping a team with autonomous code in LabView before a match. In one instance, we started helping them about 20 minutes before match time. The changes were in place and ready to go, but the lengthy build and deploy times were such that we were unable to get them on the field for the match. In the second case, we had a similar situation, but we got them to the field only because the match before us was foghorned which bought us a little more time.

I find this to be completely unacceptable. How can we reliably be helping people in the pits if it runs the risk of them not being able to compete in a match?

What happens in the case where a team wants to tweak something in elims during a timeout? The timeout is much shorter than the build time so don't bother.

Issues like these make me glad that we decided to stay with what would benefit our students the most, C++. They also make it less likely that I will be helping teams with LabView any time near a match.

As a fun fact, the NI rep at MWR made a comment to me that the FPGA code takes 24 hours to build...let's hope that they recognize that as an issue rather than industry standard.....