04-09-2009 09:47 AM
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.
04-09-2009 10:08 AM
04-09-2009 10:14 AM
04-09-2009 10:28 AM
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?
04-09-2009 10:39 AM
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.
04-09-2009 10:47 AM
04-09-2009 10:59 AM
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.
04-09-2009 11:10 AM
04-09-2009 11:43 AM
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.
04-09-2009 01:57 PM
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???