LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Problems with installer/executable files


cmhand wrote:

I have two subVIs, one just sets all outputs to false at the beginning of the program and at the end. The other subVI are all the digital inputs that are being checked...ill post them both


 

Wow. Two Rube Golberg VIs in one post.

 

Here are a couple of replacements with proper error in/out connections.

Download All
0 Kudos
Message 21 of 40
(1,247 Views)
Back to my question though. The way you are trying to help me set up this error handling, will I be able to check all these inputs at the same time??? Also I want the errors to be displayed at the end of the program so I dont want the program to stop if it gets an error. I noticed you set the select to go to the error handler if there is an error. Is that just one frame that the program will refer back to if theres an error??? if so im assuming it doesnt really matter where at in the program I place that but it makes me think if there is an error and the program jumps to the error handler frame that the program will just stop there, or is there a way to continue back to where you were at in the program and continue testing while displaying the errors at the end?
0 Kudos
Message 22 of 40
(1,243 Views)
I don't know what you mean by 'all these inputs at the same time' and continuing the test with a hardware error is silly.
0 Kudos
Message 23 of 40
(1,241 Views)

Okay I will clarify better sorry. I currently am using a few Digital Input/Output modules and a cDaq 9172. I work at a company that builds various trucks (aerial, digger derricks, cranes, etc) and am a co-op electrical engineer here. I am very new to labview and have kind of been in charge of setting up a new automated tester to test various boards that go on these trucks. Currently many of the testers are manual involving a person having to flip a switch which applys 12V to a certain point on the board which may control a certain function on the truck, etc. This automated tester will use labview and involves a person just hooking up the board to the tester and running the program. On the current program I am editing now there are several inputs that need to be checked throughout the program such as Ignition Cold, ACC Cold, +12V Machine, etc totalling to 7 for this particular program. What the program does is when it says 'Apply Ignition Hot', 12V is being applied by the Digital Output module to that particular pin/spot on the board and then the next frame checks certain functions that should then come on which in this case would be Ignition Cold and ACC Cold, BUT it also needs to check the 5 other inputs to make sure they dont come on due to somewhere on that board there is a short due to bad soldering etc or some mechanical error that would effect those inputs. The reason I was using the pass fail is that in this case Ignition Cold and ACC Cold should both be getting 12V at their input but the rest should not be. In the other program I finished there are 183 frames of this and over 30 Digital Outputs and Inputs that are being applied and checked so a much bigger complex circuit board. Does this clarify better?

0 Kudos
Message 24 of 40
(1,239 Views)

Interesting but not at all material to error capture/handling and whether to continue a test if an error is detected. If a hardware error happens, then the results from the 9172 are bogus and if you continue the test, you are just wasting time.

 

Nothing I've suggested affects the way you are currently acquiring and processing test results. I would have done it differently but that's immaterial as well.

0 Kudos
Message 25 of 40
(1,235 Views)
So the way I am doing it is a legit way of detecting the possible errors on the board right? I do need to figure out the hardware errors though such as if the DAQ isnt even connected to the computer. If the DAQ isnt even connected to the computer then why does the executable still run and somehow display results?? because the actual program wont run if the DAQ is not connected. Thats what started this whole question for me, which I think falls under hardware error
0 Kudos
Message 26 of 40
(1,233 Views)

Please stop called defects on the boards 'errors'. An error in a program has a pretty well defined meaning. Call board problems 'Faults'.

 

The way you are doing it is pretty sloppy and inefficient but if you (and your boss) is happy with it, fine.

 

The executable runs because you have no error handling. It's just that plain and simple. When you run it from LabVIEW, it won't run because you probably have automatic error handling turned on. And I'll bet you did not know that LabVIEW has an option for automatic error handling.

0 Kudos
Message 27 of 40
(1,230 Views)
Im sorry for the wrong technicallity. The automatic error handling in labView is just simply when it wont let you run a program because of errors that you must fix correct?? So if I want to detect the hardware issues I need to continue to do what you were suggesting but Ill probably leave how I am detecting the faults on the board since that is working perfect unless you have a rune goldberg quick that would be more efficient for me. If perhaps one of the modules burns up or something internally happens I need to detect that which I never thought about doing until you began helping me and yes in that case if a module isnt even working right I would want the program to end right there and say "module # isnt working" or "no power" etc. The faults are what I want to be displayed at the end of the program which its currently doing fine. If you dont want to help me anymore I understand but I thank you so far for what you  have helped me with...I went back and changed all my output frames to look like the one you posted...now I am figuring out the input frames where the faults are checked, and hopefully get figured out the frame that would display the hardward issues.
0 Kudos
Message 28 of 40
(1,227 Views)

The automatic error handling is basically the same as what we have been discussing. When any type of error is detected, you get a popup that describes the error code and error message. There is probably a way to use automatic error handling in an exe but it's not something I've ever tried as it is too simplistic in many cases.

 

I or someone else will continue to help. When you are done with the modifications, post back if you have problems.

0 Kudos
Message 29 of 40
(1,219 Views)

I know this isnt right because the appendix array from my subVI is going to have true and false boolean so that wired to the bottom selector wont work right I dont think...how do you connect to the error out of the subVI so I can set up these frames like the one you posted???

0 Kudos
Message 30 of 40
(1,199 Views)