[Unexas]

Originally Posted by Greg McKaskle

I also wanted to make sure that you are aware that Edit/Build/Run is not a very effective way to develop code, especially in LV.

The run button on Robot Main should be used anytime you are not sure that your code is perfect. Why? Because when you build and deploy, you are building and delivering a finished and optimized EXE and it is difficult/impossible to view and debug stuff. While it is possible to change the settings to allow for debugging of a built app, there is a much better way.

Open the Robot Main and click the run arrow. If it is broken, it will explain why and help you to fix the issues. If it is not broken, it will deploy each VI into memory and allow you to open panels, probe wires, breakpoint and pause, and more generally let you interact with code that is not final. When you see that your logic is off, or your constant needs to change, you abort RobotMain using the stop button, make the change, Save, click the run button again, and the in-memory roboRIO stuff if updated with the minimal download, and you are back to testing the functionality.

On the flip-side. You will be required to build and deploy to run at an official FRC event, so definitely learn how to do that as well. Just don't use it as your only development technique.

Greg McKaskle

I am trying to build the default program just so the drive team is able to drive later today. And i have tried building from FRC boot up deyployment nor from robot main.