Dear CD,
There are certainly more and different hoops to jump through to get the base code running in 2015.
I am receiving build errors related to RobotMain.VI using the provided template and our team number 3548. “Cannot complete build because the following VI loaded broken” (C:\Users\Documents\LabVIEW Data\2015 Robot Project \Robot Main.vi)
Further down it says
Broken VIs:
– Details Display Dialog.vi:
Function not supported for current target
–Not Found Dialog.vi
Function not supported for current target
Sub VI not supported in current target
ANy hints?
I followed some of the documentation rabbit trails and have the target setup as roboRIO3548.local but I don’t think the build issue is related.
I am running both Labview and Driver Station as the administrator (Win 7). Is that required this year, again?
I’ve actually found it to be a little less complicated than last year. Removing the requirement for specific static IP addresses takes away several hoops.
I am receiving build errors related to RobotMain.VI using the provided template and our team number 3548. “Cannot complete build because the following VI loaded broken” (C:\Users\Documents\LabVIEW Data\2015 Robot Project \Robot Main.vi)
Further down it says
Broken VIs:
– Details Display Dialog.vi:
Function not supported for current target
–Not Found Dialog.vi
Function not supported for current target
Sub VI not supported in current target
ANy hints?
Seeing the error in context might help. Can you post a picture of it?
You might get more information if you open Robot Main and click on the broken Run arrow at the top of the screen. It’ll give you a list of the errors, and you can click on each of them to be taken to the part of the code where the problem is.
I followed some of the documentation rabbit trails and have the target setup as roboRIO3548.local but I don’t think the build issue is related.
When you provided team number 3548 during the creation of the project, it should have set the target as roboRIO-3548.local (with a dash).
I am running both Labview and Driver Station as the administrator (Win 7). Is that required this year, again?
I don’t think we’re running LabVIEW as administrator, and everything seems to be working fine. The Driver Station computer is definitely not logged in as an administrator.
My hint is that your code seems to have compiled in a VI that wants to display a dialog box. That generally isn’t good on an embedded device, so it breaks the VI asking for said dialog box.
On a hunch, I looked at the General Error Handler VI and sorta assumed this may be the culprit. It calls the Details Display, but shouldn’t do it on a roboRIO.
What is the history of this project? When you say this is a base project, is it built from the template this year? Or is this an old project that has been modified?
Does it run with the run button and fail during a Build? Or is the run arrow broken as well?
Greg McKaskle
Greg,
Yes I am using the 2015 software. I receive the same error on two machines, my laptop and now my desktop. On my desktop I just downloaded the FRC update Suite and installed it and found the same error.
I ran into the issue right after selecting a new 2015 arcade project with arm or mechanum project and my team number. I tried build and Build All like in 2014 and it failed. Then I found the instructions to use Deploy in Robot Main.VI and it failed it a similar manner.
I am a bit suspicious now that this was released this way. Can someone else confirm this. Yikes!
I need to run to our team meeting for tonight and appreciate any help upon returning after 9:00 p.m.
Thanks,
Dear CD,
Tonight I had one of our students build a new 2015 software arcade project using the same procedure I have used at home without any errors. So, I am puzzled. I have attached a screen shot of the error messages from my desktop at home.
Dear CD,
The solution to this problem was a licensing issue with two Labview vision components. Upon licensing and subsequent out and back into Labview with a fresh start, the build was completed. Thanks Alan for your Run tip that helped provide the necessary information. Also thanks always to Greg for helping everyone on CD forums.
You are welcome. And thanks for letting us know the resolution. It is very confusing that the licensing issue results in that dialog.
Greg McKaskle
