LabVIEW
labview run example
Sorry, I don't have LV 8 at hand just now. I'm attaching a picture to show you what I mean.
This is pretty LabVIEW basics; if I can speak frankly, it's not very good you don't understand it. I suggest you to spend some (more) time to learn LV basics (or your boss to let you do it!).
This is pretty LabVIEW basics; if I can speak frankly, it's not very good you don't understand it. I suggest you to spend some (more) time to learn LV basics (or your boss to let you do it!).
Message Edited by pincpanter on 07-13-2007 11:36 AM
@Melikyan wrote:
Dear Altenbach I have a question. If program run, after 1st cycle I cannot input the time delay, and then continue 2nd cycle, please recomend what way have to input time delay...I need only 1 time delay between the first cycle and second cycle.
FIrst of all, there is no "time delay" between any cycles in your code. Your FOR loop with the progress bar runs in parallel with the measurement code at each iteration of the loop. If you want the wait loop to execute either before of after the DAQ part in each iteration of the FOR loop, you need to enforce some execution order using dataflow.
As Pincpanter mentioned, just place the delay statements (e.g. your FOR loop) it inside a case structure and wire it directly to [i]. Make one case 0, and the other "default".
OK, there are still serious flaws all around. I assume that your initial wait should happen after "Run!" is pressed, but before the DAQ and progress bar will start running. Right now this all happens in parallel, so the initial wait has no functional significance. Right? Right! 😄 You need to create an artificial data dependency to enforce execution order via dataflow.
Since we already have a while loop on the outside, we can recruit it to repeat the DAQ. No extra FOR loop necessary.
In addition to the "Run!" button, also assign a timeout to the event structure. Initially, set it to infinite (-1) so only the "Run!" button can trigger, but then set the timout to either infinite or zero, depending on if you want to repeat the event case once more without user intervention. If the case does not repeat, you simply need to press "Run!" once more for the second run. No need for secondary buttons and complicated instructions. 😉
It is much better to utilize timeouts for long waits, because they can be interrupted at any time. A long wait on the diagram will block everything else.
Right now it is setup to wait indefinitely after each second iteration ([i]=odd), but you can easily modify that too.
Also note that I removed unneeded duplicates such as your "1000000000" diagram constant that occurred 3x where once is plenty.
Just take this as a draft. I cannot test without your hardware, so there are probably bugs. 😉
