Connecting vi's to build a dynamic system

[KOutland]

This should have all 6 necessary files in it. There is the main.vi, two calibration vi's, the interface vi, and a few subvi's.
I have heard that passing data through globals isn't the best method, but I'm not sure how to pass the data by wires.
I'm pretty much at the tail end of this project. I need to present this to two doctors and the rest of my team on Monday evening - therefore I'm mostly aiming for function over form.
I would check out the exectution highlighting but my computer at home is not equiped with a daq card, and I won't be in my lab until tomorrow. I know that the program will go from main > 10lb calibration, but no further than that. Before I had it set up in case stuctures whic
h would all moving from vi to vi, but I could not set it up with a button (it just jumped automatically when the last program finished).
(and by the way, I'm in the eastern time zone, I have a very large monitor, and good eyes to go along with it - thanks for the help)

[paul_s]

see if this works for you - I've added some dataflow control, nixed a couple of local variables, and set subvi node setup - right click on subvi>>subvi node setup>> open when loaded, show when called. Try to write your vi's so data flow is from left to right - makes it easier to follow

Paul

[paul_s]

I just stuck your acquisation in a case wired to false and generated dummy data to test (for loop with random number generator)

[paul_s]

last one didnt wait for file path... this one does and generates dummy data. You need to tell the user when the program is waiting for input - say a simple "pop-up" subvi

[paul_s]

here i took out globals, added dialog, and fixed flow a bit. Hope it helps

[mikeporter]

Basically anything non trivial. You see the problem is that the VI handles errors right there and doesn't pass the information on. The only choices it gives you is continuing--in which case the rest of you code won't know an error occurred, or just stopping your program. No deinitialization. No returning setups to a default or safe condition. No nothing. It just pulls the plug.

This is a very bad thing. NI's justification for it is that these file IO VIs were intended to be examples--not to be used in applications. Unfortunately, the word isn't getting around.

Mike...

[KOutland]

Thanks so much for all the help, but it still won't advance to the next vi after the first step. Main.vi will go to 10lbcalibration.vi correctly, but after completing 10lbcalibration, it won't advance to the 5lbcalibration. Would this have anything to do with the subvi node setup?

[paul_s]

huh? it's working perfect for me... here are the same files again... try execution hilite in 10lb if it doesnt work for you - i cant see a problem

[paul_s]

make sure you havent got 1 of your old vi's in memory instead... if necessary you may have to change your old folder name so labview cant find it. Tools>>browse vi hierarchy of main.vi to check the paths

[KOutland]

I think it has something to do with the subvi node setup. I changed all of them to "suspend when called" and that's where the problem came in. When I don't have that selected it works. I will try again later in my lab to make sure this was the problem.