LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Loops being ignored?

I have 5 sequence's, the last sequence contains 5 While loops, one of which has the DAQ displaying three continuous voltage signals and doing most of the work using several shift registers.

Whilst running the vi with the diagram open, it seems to ignore some of other loops that are just waiting for a trigger to take in value from the DAQ While loop.

I've put a breakpoint within the loop that seems to be ignored and it never triggers the breakpoint.

Running the vi panel only seems to see the the other loops What Gives??

Is there a limit to how many While Loops you can have running at the same time?

Could it be because the DAQ Loop is far to busy?

Are there any rules to follow which I should be aware of?
0 Kudos
Message 1 of 7
(3,036 Views)
Funny that !
Seems that a very similar situation was discussed yesterday...
http://forums.ni.com/ni/board/message?board.id=170&message.id=103846&jump=true

CC
Chilly Charly    (aka CC)
0 Kudos
Message 2 of 7
(3,034 Views)
when I only open the panel it works fine, but when I open the diagram and run the vi it only seems to run the while loop with the DAQ's and shift reg's in it.

I've have been able to decrease to two while loops still in paralell now to see if it would make any difference and I ahve also increase and decreased both loops now to no effect.


Help?

Is it a memory problem?

I'm using a lot of property node's?
0 Kudos
Message 3 of 7
(3,009 Views)
Please post your simplified example.
0 Kudos
Message 4 of 7
(3,004 Views)
Thankyou for the offer but I have been able to solve the problem.
0 Kudos
Message 5 of 7
(2,979 Views)
Perhaps you wanna share with all people out there your solution(s)?

Regards
ian
Ian F
Since LabVIEW 5.1... 7.1.1... 2009, 2010, 2014
依恩与LabVIEW
LVVILIB.blogspot.com
Message 6 of 7
(2,962 Views)
I had two While Loops altogether, Trigger Event Loop and DAQ/Shift Reg Loop. Thinking that there was something wrong with the DAQ part, I made that into a separate Loop. The problem stayed in the Shift Reg Loop.

The new DAQ Loop and Trigger Event Loop were not even iterating, Therefore I assumed the problem resided in the Shift Reg Loop.

After reading of similar problems in the NI Discussion Forums, indications were pointing to memory problems that were describing my actual problem.

Solutions were to either use occurrences or only open the front panel when running the program without viewing the diagram, this solution reduces the amount of memory required which worked. However I could not see the effect of applying any changes to the diagram easily.

After reading "architectures_for_designing_labview_applications.PDF", it was suggested to make Local Variables in each Loop.

Utilizing the information found I looked at the way my loops were being stopped. They were being stopped by Property Nodes via a Boolean Indicator, which the other Loops were using to stop.

No Local Variables were in the other Loops.

So I rebuilt the stop sequence, removed the Boolean Indicator and made the new Stop Button with Local Variables in every Loop.

Everything worked?
0 Kudos
Message 7 of 7
(2,940 Views)