Please solve this mysterious broken run arrow

[GregFreeman]

Everything works great for a while. Then suddenly, this will happen. This is on a PXI chassis using a lot of LVOOP. It happened on my PC so I moved the code all to a VM. It worked fine for a while, then it just came back. These are NI's VIs. The weird thing is, if I diagram disable them, I still can't deploy. I get a broken run arrow right at the end of the deployment (when it says deploying Main), but when the broken run arrow is clicked I have the error list with no errors in it. Tried closing everything, still problem not solved.

1. 

[GregFreeman]

Control shift click run arrow the first time crashed LabVIEW. The second, it resolved the broken run arrow problem but the deploy still failed. A reboot of the VM at this point though fixed it. Pretty painful work around.

[mikeporter]

Diagram disable structures can indeed cause wierd problems. Ditto conditional structures. They can be useful for troubleshooting or debugging, but I have given up on using them as permanent parts of code.

Mike... 

[GregFreeman]

Thanks Mike. In fact, I traced it back to the general error handler VI which I was using to clear a timeout error with "no dialog" set. It was enabled at the time, but I am stilling getting the issue after disabling it. The strange thing is the inconsistent nature of the error. I am going to try scrapping the VI and just doing my own custom error handling and see what happens. Maybe the issue lies in the fact that within the VI there are some conditional and diagram disable structures and those are acting finicky as you mention.

[dan_u]

I had similar problems, but not as persistent as yours seem to be. The general error handler uses a conditional disable structure inside, sometimes I think this code seems to be compiled for the wrong target. The Details Display Dialog VI is disabled for RT targets, but sometimes this does not seem to work.

[GregFreeman]

So I removed the general error handler but the error came back. The only place it remains is within the simple error handler within the Internencine Avoider.vi that is in the Create TCP Listerner VI. It's inside a conditional disable structure's default case, while the Target_Type==Embedded is empty. I am just going to delete it for now just to try and get past this point and deal with it later.

[GregFreeman]

Sorry, Dan, you must have posted while I was typing. My findings seem to be similar. Just curious, can you tell if this seemed to go hand-in-hand with LVOOP or is it irrespective of that?

[Danubio]

Hello GregFreeman,

I found these links which hopefuly could help, please check them out:

"Why Do I Get a Broken Arrow Although the Block Diagram Has No Broken Wires and the Error List is Empty?"
http://digital.ni.com/public.nsf/allkb/56F3F1DA24A5270286256C020070F67B?OpenDocument

No Errors Listed When Clicking the Broken Run Arrow in LabVIEW
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/8d2a6d74062a9eaa86256993006f0471?O...

Best regards,

Daniel C.

[dan_u]

I wasn't using LVOOP when I encountered that issue.

I'm not sure if this is related, but I also see bad deploys to the RT target from time to time. Modify a SubVI used in the RT code, run (and thus deploy) the RT main VI and I still see the old RT code running (before doing the modification). This is with LV2012 SP1, don't know if it changed in 2013/14. The changed SubVI did not have any conditional disable structure, but the issues could be related in the sense that LV does not recognize the change and thus does not recompile the VI. I use the separate compiled code feature.

Unfortunately I don't have solutions for these issues.

[davekorpi]

Try this video showing how I fixed this problem!

https://www.youtube.com/watch?v=qYAzEpTVsaw

How to Fix Your LabVIEW Failed to Compile or LabView Broken Arrow on Compile.

If you have a happy vi running in LabVIEW and it has a happy arrow then it SHOULD compile to an executable. RIGHT??!! NOT... Frequently, especially if the project is LARGE, it will not properly compile!

I show you how you can compile EVEN when you have a broken arrow!

When LabVIEW fails on building an executable it sometimes does not show you WHERE the error is. It also tells you that you need files that you are not using! Go figure! This is because some of the files are ignored that should not be ignored.

If you know how to get rid of the nag screen please let me know by sending an email to me at dave.korpi@gmail.com

This is on a Virtual Machine Windows 7 on VMWARE Fusion 6.02 and the bloody Virtual Windows 7 works better on my iMac than it does on the Toshiba Laptop that I cloned it from!

I use the LabVIEW Service Request System and it is COMPLETELY worth the cost. They are EXTRAORDINARY I would say about 98.7% of the time!

If you liked the video please subscribe to my channel.

Please LIKE this video if you found it useful!

My website if you need Patent Help of engineering help!

http://www.take5inc.com/

Video made with SnagIt