Quote:
Originally Posted by Greg McKaskle
This error means that the VI in your project named Autonomous Iterative is broken. Open the VI from the Project/Team Code, click on the run arrow and see if you can correct the issues with the VI.
Greg McKaskle
|
With all due respect, Greg, no it doesn't mean the vi is broken. I'm getting the same error, except for us it's our Teleop.vi. I can save it fine manually. I can run it on the cRIO just fine. There are no errors anywhere. But when we try to build we get the 1502 error.
Martin:
ni.com/ask has several threads about this. What worked for us is enabling debug info. Right-click on your build spec, then select properties. On the property panel left side select Advanced, then click the box to Enable Debugging. According to stuff on ni.com, debugging forces the diagram to load which overcomes the problem.
What's disturbing about this is loading debug info on a competition robot. I'm trying to figure out a way around it.
Anybody have any ideas? Plus, why the heck does LabVIEW need to save a vi during the build that I've already saved manually?
BTW, ni.com had a couple of other ideas, neither of which worked for me. Perhaps one will work for you. One is to open the offending vi before you build so the diagram is available. Another is to shorten the build path -- apparently path names can get over the 255 char limit on some (all?) Windows platforms (the build path is also on the build spec properties panel.