@marwah1 wrote:
@RavensFan: A while loop will always start by 0. a For loop no.
you can take a VI, create a for loop and see. In the beginning it start with 0. but if you stop and run again it will start from the last number where it stopped and add..
NO. The i value of both loops always start at zero. Why do you think that is not true?
I find a solution to initialize via the invoke node...
I'd have to see that code. Maybe it works for you. But initializing an invoke node means changing the value of a control back to its default. You were just talking about the i iteration terminal. Two different things. If it works, then it is because you are actually talking about something different than what you are describing.
Last question please, if I stop a while loop via some condition.. and then I want to restard again without restarting the whole VI. I mean I just need to restard the queue.. is it possible ?
You are talking about while loops vs. queues vs. whole VI. I can't picture what you are talking about without seeing the latest code. You should never need to restart the queue. Perhaps you send a "restart" command through the queue which can do several things like restart the motor, or clear the array of boolean flags back to all Falses.
Because my program will at first measure the cold resistance (the loop will stop after measuring), then run the motor till thermal stability, stop the motor, measure the hot resistance (the loop need to restart)
Ideas how to restart a loop?
Put another while loop outside of it.
The activities you are describing, and especially now that you are talking about more activities than where this thread started which was just looking for 3 conditions, means you really need to architect your code into a state machine. Search the forums, search the example finder, and look for the state machine template under the New VI.... menu choice. Once you read up on it. Then sit down away from the PC and with a pencil and paper and draw a flowchart. Figure out all the states or conditions in you program. What activity leads to what. Under what condition does it move on to the next. When does it need to go back to a previous state. Once you have that document, you'll be in a much better position to build your state machine.
