Manual data input in a loop

[Aquaphire]

Hey all,

I'm  wondering how to input manual data into a loop (control string).

At the press of a button, my program records various other data (time/strain/ stress/ etc...) but before the loop ends, I want it manually type in a value (pressure) since it doesnt have a digital output. I was wondering how I could write the loop so that it won't continue UNTIL a value has been filled in and, for example the "ok" button has been pressed.

thanks

[Joe_H]

Why not use the prompt user for input function on the time and dialog pallette.

[Aquaphire]

I don't think I have that function... Using labview 6.1 😞

or did u mean the "One button dialog" , link 2 booleans together, and put the manual value in, if empty string constant false, and one button dialog true, move on?

thanks.

Message Edited by Aquaphire on 07-14-2005 04:19 PM

[Joe_H]

You are right you do not have that option in 6.1 but you could do as you said, or you could make your own subvi made to accept user input.This would be the easiest to do I would think.

[Joe_H]

Try these two vi's and see if it is close

[LV_Pro]

If you make your own dialog box, or even in the higher level one, put a while loop "in series" with the rest of the program's flow  (before the outer loop ends). The attached picture shows one method (I don't have the LV version you are using handy)

P.M.

[Aquaphire]

HEY LV_Pro,

How do u make the "error IN" and "Error out"?

I don't understand what its use is precisely....

[Ankita]

Hey,

Error in and error out are error clusters. An error cluster consists of three parts: error status (true value implies an error occurred), error code (numeric code for the error) and  error source (it tells you which function or VI caused the error). The error in and error out clusters can be found in the Controls >> Array and Cluster palette . These clusters are used for transferring any error information to/from a subVI.

Hope it helps.

Ankita

[LV_Pro]

The error clusters may also be used even when the vi won't generate its own errors, to provide a means to force the order in which vi's are executed. If you drop your dialog/operator entry sub-vi on to the calling vi's diagram without some means to determine when it is called it may be called before you actually want it. By putting the error clusters into it, even if they are just passed through the vi, and then wiring them to the error out of the vi prior to when you want it to run, and the dialog vi's own error out to the vi that follows when you want it to run, it forces, by data flow, the vi to execute when you expect it. This obviously is not always necessary and frequently I will put the error clusters. etc., into a new vi and then never actually use them but ...

P.M.

[Aquaphire]

thanks both of u. I managed 🙂