Nested For Loop skipping case structure

[Otman]

The Case Structure inside the inner For Loop is skipped when running the code in normal speed, but when I run it in Highlight Mode it works. Anyone has any idea why this is happening? Appreciate any insight.

[JÞB]

why do you belive it is skipped?  What version of LabVIEW?

Side note: Why is the DBL wired into the case structure?  It is just passed through in both cases...

[RobCole]

Run some probes in the data. Especially on the error lines and the feed to the number of iterations. See what is happening. It could be a timing issue while running at full speed.

The subVIs did not come across with the code snippet, so I can not test the code.

Rob

[altenbach]

In addition to jeff's questions: What is the value going into N (maybe the earlier subvis need to be paced more slowly and you get a zero otherwise due to errors).

[JÞB]

Looking a bit deeper

~~~Oh Magic 8-ball~~~~ did the OP intend to use CASE select = 0 (mod (i, 20))  so that every 20th iteration fired the true case?

[Maybe-- you seem to be on to something]

use Quotient and Remainder.

[Otman]

Jeff,

The code in the CASE does not run when the loop gets to 20 while program runs at "normal" speed.

I wired the DBL for data flow purpose only to keep consistent with LV best practice, I think.

[Otman]

Robert,

I did run the probes in the data, and they give the results I want for data. The subVIs just sets my instrumentation.

I know the snippit didn't come thru and I'm not sure why. I'll try to figure that one out.

[Otman]

altenbach,

the value going into the second loop is 36 which is the size of a test array. whould running earlier subvi's matter even though all VI's are in series meaning that next one will not run until the previous one is done performing its tasks?

[JÞB]

Just zip the project and set normal default data as default in the controls and indicators. attach the zip

What is the hardware?

[Otman]

Jeff,

Sorry for the dumb question but what is OP?

Don't integers compare cleanly in labview? You're right I want the CASE to fire every 20th iteration.

Thank you all so far for shedding light in this problem.