Problem when I try to run the VI

[EKrille]

Hello!

Sometimes I get a problem when I try to run my VI. When I try to hit the run button, the program jumps in to the block diagram and stops, blinking around, for example, a while loop. To get the program running I have to hit the Run without Pausing button, that have appeared where the run button use to be.

What is the problem?? I just want the VI to run when I hit the Run button, without showing the Block diagram.


??

/ Krille

[Odd_Modem]

The block diagram has a breakpoint set. On the tool palette the breakpoint tool looks like a red circle with an arrow sticking out. There is the menu selection browse breakpoints. Use the breakpoint tool to set them on and off.

[BigBoyTwo]

You appear to hve set a 'breakpoint' in your code. Part of your code will have a red outline. Your program will then stop at this point and the code will be highlighted (until you hit the run/pause button) . To delete this 'beakpoint'go to the tools palette and select the 'breakpoint' tool and click on the red outline.

The 'breakpoint' and 'highlight execution' functions are good tools to use in debugging a program, learning how to use them is recommended execise.

[EKrille]

Yes, I know about the breakpoints. But it is not the problem now. I don´t use breakpoints, and when I search for breakpoints, I don´t have any. I don´t have any redline stuff in the block diagram. So I don't think it is the breakpoint problem.

It is when I hit the run button it stops just like I would have a breakpoint, but I don't. Right in the begining.

Any ideas?

[tst]

Actually, it does sound exaactly like a breakpoint. The "Run without Pausing" option only appears if the VI was paused, which means it has. The most likely explanation is that you placed the breakpoint not on a wire, but on a structure (that while loop). If there are no breakpoints in your program, when you search for one, you should get an empty window saying no results were found. If there is one, it will take you straight to it, which might be interpreted as finding no results. Place a breakpoint in the code and search for breakpoints. See if you get two results. If you do, the other one is around the loop. It should appear as a red frame around the loop. To remove it, you need to click the breakpoint tool on the OUTER side of the loop border (watch where you click, because different places create different breakpoints).
If all this didn't help, post your code.

[EKrille]

I have already tried, by inserting a breakpoint and find it. It is no problem. But when I try to find the one that gives me the problem, I get a empty box. So I am sure that I don't got any brake point.
Ok, I send u the code! I have removed all stuff, but the loop.
And I still have the same problem!!

/ Krille

[PauloM]

I ran your vi and it works normally.
Do you have probes in your code?
In some probes you may have conditional stops witch work exactely like a breakpoint but under some conditions you can define.
But anyway that is probably not the case since you say it's still happening even only with this loop.
Is this happening only in this program?
Can you run other vi's without any problems?

Regards,
Paulo

[shoneill]

I've had cases in the past where setting and then removing breakpoints has left "ghosts" behind which still act as breakpoints, but which don't show up and therefore can't be removed. Normally shutting LabVIEW and re-opening does the trick.

If this doesn't help, try copying everything from the block diagram into a new VI and save it under a NEW name. See if that helps.

Shane.

[EKrille]

Strange! Now it is working like it should. I just have restarted Labview. I have had this problem before. The only common thing I can see, is that I used flat sequence structure. I don't know if that has anything to do with it.

Well, thank u anyway!