No Errors, but VI will not execute

[lxjx]

I have a simple labview program that communicates with  a USB-6211 DAQ.  The arrow to start execution is white, indicating no errors.  When I click on it the error window opens and says "No VIs with errors" and the vi does not execute.  Is there a way to diagnose or clear a No Error, error condition?

[MoReese]

Post your code for viewing.

[JÞB]

does not execute" is a bit vague---

Does the vi "run"- "refuse to run" (or run so fast you did not notice),  Or do you need to "abort" to stop it?  Attach the vi and we may be able to help.

[RavensFan]

This KB article talks about a broken run arrow with no errors.  And doing a search came up with a few posts with similar situations.  Though I have yet to see one with a non-broken run arrow that leads to an error window with no errors.

Try doing a Ctrl-click on the run arrow.

Try coping the block diagram code to a new VI.

[lxjx]

Here is the code.  The vi was working a couple of days ago and I've not changed anything.  I could read AI from a signal generator and send AO to a scope.  I tried the suggestions of copying the code to a new vi and using a ctrl click with no luck.

[NIquist]

A RUN arrow simply means there are no obvious errors detected by the compiler.  It does not mean your code has no bugs, will run properly, or give you valid results.  That is still up to you.

I assume you have automatic error handling option turned ON in your system, right?  If not you could have all kinds or errors and never see them since you have no error out indicator.  First, turn on the highlight execution button (light bulb) and watch your code run.  I suspect the DAQ channel you have selected is invalid for some reason.  Otherwise, since your code is so simple, I cant't see anything else that might be a problem.

[RavensFan]

I don't know what to say.  Your VI runs okay for me.  I don't have any DAQ devices connected to my PC, so I had to use a simulated device.  But it runs without errors.

The only thing I noticed was that after opening, it had unsaved changes and the only thing listed was "VI recompiled".

[altenbach]

I would recommend to change the mechanical action of the stop button to "latch when released" instead of "switch when pressed". This way it will be ready for the next run.

(When you use switch action, the button does not automatically revert to FALSE after stopping the program, so if you don't pay attention, the code will stop after one iteration on the next run.) 

[lxjx]

I had to change the mechanical action so that I could use the stop button as a local variable.  There was an error stating that the latching action was incompatible with local variables.

[altenbach]

Then reset it after the loop using another local varable.