Subdiagram no longer works within a flat sequence

[alexmer]

Hello everyone. I'm new to labview and I ran into a roadblock with my program.

I have a diagram that involves a DAQ assistant controlled by a timed loop within a for loop (its purpose is to output voltage from a max to min value in a number of steps). By itself the code works. I constructed another diagram that is supposed to increase the voltage from 0 -> max voltage as a "warmup" for the device. I need the warmup to happen before the main diagram, so I put them in a flat sequence. However, once I do so the program only executes the warmup then ends. Any ideas on what could be causing this?

The computer I am doing it on is not connected to the internet and I do not have a flash drive so the best I can do is post pictures of the screen.

http://imgur.com/a/Li9md

Could anyone help? Thanks.

[altenbach]

You should never use "equal" comparisons on floating point values.

Why are none of the error out wired. Maybe they try to tell you something?

What are typical controls values (e.g. for "number of loops", etc.)

[Alexander_Sobolev]

>> program ends

Do you mean it gives error in the main loop? Or does it normally end the program without giving errors?

I suppose there is an error happening - because first daqmx write does not close write to AO. Next daqmx assistant write tries to access the same resource and fails.

Connect first loop end condition with Stop terminal of daq assistant. 

Also I would be not surprised if the original program never end the internal timed loop - you are comparing two doubles with "equal" as a loop end condition. No-No-No. Less or equal (like in the first loop) is better.

[billko]

If you really insist on "equals", the best you can do is "equal to a point" where you decide how many places you want to use in your comparison.  Then you just use "number to fractional string" for each number with the precision equal to the number of decimal places and THEN do the comparison (while they are still strings).

I've seen some really esoteric discussions that go way over my head about how to compare them, but this seems to be the easiest way for me.

[altenbach]

Well, the "equal" problem (while real!) would cause the program to never stop so it cannot explain the observation.

Of course it could be that comparison is immediatly equal and the loop stops after one iteration.

There is no error handling, so the code would not stop if there is an error in the DAQ stuff.

I still suspect that N of the FOR loop receives a zero, causing the FOR loop (and the containing timed loop) to be skipped entirely.

We clearly need more information from the OP.

[alexmer]

Thank you guys for the advice. I had a less than or equal sign before but I changed it thinking it might help. I'll revert that and wire the loop condition to the DAQ stop terminal next time I'm in the lab. Hopefully that'll fix it.