Forum,
Naturally, once the code works, it breaks in a whole new way. Today I tried to build my code to deploy new Autonomous code; however, the build process required vis which I have never seen in the Main code before. These files are:
- Set Low Priority Dashboard Data.vi
- Set High Priority Dashboard Data.vi
The project example is the one in which the live image feed from the camera is preset into the project (if that has anything to do with it). Isn't it awful when perfectly good code just stops working?
Pre-thanks for the help from Team 810
Those VIs are part of the DriverStation.lib. They should be in the palettes in the lower left subPalette of WPILib.
There is a strange issue with RT and unreachable code where the compiler sometimes takes out code inside of a switch or code which has a constant expression wired to it. But later when the files are ready for download, another part of the compiler gets confused because it cannot find some of the files it believes it needs.
If you open Robot main, the default code was calling it with the vision target globals. If you right click and Find all Instances, it will show you where the code uses the High Priority subVI. This may help locate all the locations.
If you do have an issue with the constant wired to the switch, you can instead use the Diagram Disable structure, basically the comment structure.
Greg McKaskle
That is initially what i assumed as well; however, it is not there. Was there some update that I missed besides the first update? My choices are as follows in the DriverStation library under WPIRobotics Library:
- START/STOP communications
- Get Alliance/Digout/DigIn/GetAnologIn
- Set DigOut/UserData
If you are missing updates, the Getting Started window tries to help with that.
From what you describe in the palette, it sounds like the computer you are on has not been updated.
Greg McKaskle