09-07-2007 07:56 AM - edited 09-07-2007 07:56 AM
Message Edited by HmanH on 09-07-2007 07:57 AM
Message Edited by HmanH on 09-07-2007 07:58 AM
09-07-2007 08:08 AM
09-07-2007 09:19 AM
09-10-2007 04:35 AM
09-10-2007 04:53 AM
if you made this vi you already have some Lv programation knowledge - you should therefore know that a while loop will execute as long as not terminated.
in other words: what your program look like now is:
1- tab chosen
2- run while loop, where in each iteration some data will be created and saved.
3- the while loop will not stop until you press the stop (3 or 4) button. remark: stop 3 is hidden!, stop 4 is well below the rest of the front panel.
4- only then, the program will stop.
if you didnt do this vi, i strongly suggest you make one from scratch, and on a step by step approach design what you want to do. As Lynn proposed you better off doing some LV tutorial before.
so, to change what you have right now:
1- easiest is to let run all the data process in one big loop. since the tab is only an indicator, there is no need to connect it to any case structure, unless you have some operation that critically depend on which page is displayed.
2- put all saving option after the loop. as you press the stop button you will be asked to save.
keep posting, we'll try to help from here.
09-10-2007 05:08 AM
09-10-2007 05:28 AM - edited 09-10-2007 05:28 AM
keep posting, we'll try to help (dont forget to rate 🙂 (5 stars only pls))
when you post, make sure all subvis are uploaded. the easiest way to do so is to save your application as : save with options -> development distribution.
your application will then be saved in a library (.llb), with all relevent subvis. you can use your application like that and send the whole llb for use to look at.
about tab control: to my opinion it it best used in combination with an event structure, if operations on each pages is different when displayed than when not displayed.
this seems not to be the case in your application, however i am not really understanding the difference of the 2 cycles. maybe you can explain?
what version of LV do you have?
Message Edited by Gabi1 on 09-10-2007 12:28 PM
09-10-2007 07:11 AM - edited 09-10-2007 07:11 AM
Message Edited by HmanH on 09-10-2007 07:14 AM
Message Edited by HmanH on 09-10-2007 07:17 AM
09-10-2007 10:24 AM
09-11-2007 03:10 AM
Hey HmanH
your vi looks like you have 2 unrelated applications.
here is a very first approximation of what you are trying to do.
Yet, it seems to me like quite an effort and clutter to duplicate virtually all (!!) controls and indicators for the 2 cycles. why not use only one such panel, and just have a button for observing either the cycle 1 or cycle 2? from the programing point of vue it would just mean you can implement everything into subvis, that would get called one or 2 times depending on which cycle is on.
right now, you have inner loop for the cycle to perform, the cycle on-off button also serves to stop the inner loop. then an outher loop for each cycle, to allow multiple cycling.
the current configuration forces you to recommand the relays everytime one of the outer loop reiterate.
do you have event structures possibilities in your version of LV?