LabVIEW
front panel
Hi Harutyun,
when you put the terminal of your graph in the 'clear'-event it will receive it's data only when that event occurs. As the event only occurs when clearing the data your graph will never show any plots... When you use an event structure you don't need extra case structures inside (with proper mechanical action setting of your switches)!
Have a look at my changes. I also change the behaviour of the output tunnels of the event structure to not "using default values when unwired" and wired all tunnels in all events - this way your vi will not "forget" any data!
when you put the terminal of your graph in the 'clear'-event it will receive it's data only when that event occurs. As the event only occurs when clearing the data your graph will never show any plots... When you use an event structure you don't need extra case structures inside (with proper mechanical action setting of your switches)!
Have a look at my changes. I also change the behaviour of the output tunnels of the event structure to not "using default values when unwired" and wired all tunnels in all events - this way your vi will not "forget" any data!
Message Edited by GerdW on 07-19-2007 02:01 PM
Hi Melikyan,
you have to clear the chart before plotting the values of 2nd run... Or you use a graph instead.
Now it's up to you to wire up the needed diagram, you should have enough examples so far
you have to clear the chart before plotting the values of 2nd run... Or you use a graph instead.
Now it's up to you to wire up the needed diagram, you should have enough examples so far
Hi Melikyan,
you have to append the data to an existing file.
In LV8+ you have to use the function 'Set file position' before writing your text, up to LV7.1 you have to wire the 'append text' boolean correctly (using 'Write to text file')!
you have to append the data to an existing file.
In LV8+ you have to use the function 'Set file position' before writing your text, up to LV7.1 you have to wire the 'append text' boolean correctly (using 'Write to text file')!
Hi Melikyan,
for your question #1:
You make the decision on 2nd 'progress' based on iteration conter i (even/odd). This will not work as CLEAR is also affecting that counter! So it may happen that i is even when you press RUN, but it may also happen that i is odd...
I changed that with by using a shift register and removing the timeout event.
for question #2:
You can put a progress bar on top of a numeric display. In the first run you show the bar, after the 2nd run you hide the bar - thus the numeric will be visible...
And you still use that huge amount of indicators/controls instead of arrays
for your question #1:
You make the decision on 2nd 'progress' based on iteration conter i (even/odd). This will not work as CLEAR is also affecting that counter! So it may happen that i is even when you press RUN, but it may also happen that i is odd...
I changed that with by using a shift register and removing the timeout event.
for question #2:
You can put a progress bar on top of a numeric display. In the first run you show the bar, after the 2nd run you hide the bar - thus the numeric will be visible...
And you still use that huge amount of indicators/controls instead of arrays
Message Edited by GerdW on 07-31-2007 09:21 AM
