Problems with installer/executable files

[Dennis_Knutson]

Help>Find Examples are the shipping examples - they are example VIs that ship with LabVIEW. Look at any of the DAQmx examples.

Message Edited by Dennis Knutson on 04-08-2009 01:38 PM

[cmhand]

Oh okay I misunderstood you I knew the examples were there but I thought you were referring to a certain example...in  your opinion what do you think is my best option of those 3 since you did see my program

[Dennis_Knutson]

I would probably use the Select in each state where a hardware error might occur. Use a shift register to pass the error between states. Make sure every state has the error wired through it! In the error handler state, use a Simple Error Handler function to popup a message and inform the user. Define the next state in the error handler as 'Done'.

This is pretty basic. At some point you could get a lot fancier and attempt to fix the error and resume or restart but the above should get you started.

[cmhand]

The thing is I cant set up a basic way because the way I have it setup right now is that every input is being checked for the main reason that if there is a short it will be detected and displayed on the front panel. I cant just check one input each frame because everytime I apply an output every single input needs to be checked. When it looks for errors it needs to look for like 7 different inputs. Im not going to scrap what I have because It works almost perfect right now...can you take one frame of my program and kind of show what you are talking about.

[Dennis_Knutson]

STOP THINKING OF ERRORS AS ANYTHING TO DO WITH YOUR TEST RESULTS!

The attached picture shows a state where you are applying a logic level. All of the other states would be exactly the same except for the state to run next when no error exists.

Message Edited by Dennis Knutson on 04-08-2009 02:49 PM

[cmhand]

So I need to change all my states where I am applying an output like you showed in that picture...you said also to use a select on the cases where I am looking for errors. The way I have it will not work at all for those cases???

[Dennis_Knutson]

You would do the same thing in every case where there is a function that returns an error. You are not looking for any errors now. I keep repeating myself about that. An error in LabVIEW is not the same thing as a fault in your product. None of those Booleans you have in your existing code are the type of errors you need to be trapping. You are looking for pass/fail conditions right now and only pass/fail conditions. A error returned by a function (i.e. DAQ Assistant) is completely different. A measurement that you take may return a Boolean false that indicates a failure of the product but it is not an error as defined in programming.

There is a lot of information in the on-line help about errors. As a start, search for the topic 'errors>handling' and try to stop thinking of your pass/fail measurements as the same thing.

[Dennis_Knutson]

Your subVIs should also be doing an error check if you have DAQ Assistants inside of them. Every subVI should have an error in/error out connection. You did not post the subVIs so I have no idea what kind of modification you need to do there.

[cmhand]

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

[cmhand]

Also what I want is to display all these errors at the end of the program on the front panel which is what it is doing. I understand the difference you are referring to with error handling and just pass/fail conditions. Right now just using the pass/fail conditions to test the errors on the product is working just fine...a certain pin on the board either has 12V or it doesnt and thats simply all the test needs to do to ensure no shorts or other failures on the board. So am I able to set up my error handling to work exactly the same as what I have right now when it comes to pass/fail conditions??? Am I able to leave all my boolean and just add these error handling along with that to check for possible hardware errors with the daq modules???