Here's some more ideas for improvement of the FRC LabVIEW framework:
- Put functional tasks in places where it says "you could put your code here" (For example, in timed tasks, you can put code that tracks the current location of the robot using the encoders and gyro. I can make code for this if you're interested.)
- Display joystick axis and buttons on front panel of Disabled.vi (great for troubleshooting. The joysticks can be tested without the robot being enabled.)
- Create a VI that can be used anywhere in the user code to tell the current state of the robot. There's several ways of doing this:
- Put "Robot Mode" on the functions pallette
- Change connector pane of the "Watchdog Status" VI to not require the watchdog ref as an input (make it recommended)
- Create a seperate lightweight version of "Robot Mode" without the extra logic (Really this would just be taking the small section of "Robot Mode" that determines enabled/disabled and teleop/autonomous, and making it a subVI on the functions pallette)