Problems with installer/executable files

[cmhand]

I created an installer with an executable file so I can run my program on another computer that does not have labview. I went ahead and installed all the drivers on the target computer and I installed 8.2.1 Runtime Engine as well as NI-VISA Runtime engine. My program tests circuit boards which are connected to the the various modules and the target computer will be used on the manufacturing floor allowing employees to test circuit boards but not being able to mess up my program which is why I figured the stand alone is the way to go. The main problem I am coming across right now is that when the DAQ modules arent even connected to the usb port of the computer the executable is still running and saying the test passed which is very bad in the case on the manufacturing floor because boards could be sent out that have failures. I dont understand why when the DAQ isnt hooked to the computer the exe still runs when I feel like it shouldnt. Is there some function I can put in my program to make sure there is a signal being sent to the computer whether it is connected or not?? The actual program wont run if its not connected because it does not detect the modules which is good. What also confuses me is that when the DAQ modules are connected to the developer computer and the executable runs the circuit board test fails, BUT if the DAQ modules are connected to the target computer and the executable runs the circuit board test passes like before when the modules arent even connected...it makes me think there is something else I need to install on the target computer...

[Dennis_Knutson]

Instead of something not installed, my guess is that in your program you are not correctly handling any errors. You will definitely get an error if there is no hardware (unless you are simulating it).

[cmhand]

I am using a search 1-D array with a false constant boolean wired to it.  Its hard for me to explain all of it so Ill just post my program and you can take a quick look

[Dennis_Knutson]

And as I suspected, you don't any place where you are doing anything about possible errors. All that you have done is wire up the error cluster to a few time delay functions.

[cmhand]

Did you look at my program? The program is working great it is detecting all the errors I want it to just not detecting whether the Daq is hooked up to the computer when the executable runs. 

[Dennis_Knutson]

Of course I looked at your program. Did you? Where in the program do you have an ERROR INDICATOR? You only have some test result indicators and that is NOT at all the same thing. You haven't even bothered to connect a Simple Error Handler function any place. Program and hardware errors need to be differentiated between faults in the units you are testing.

[cmhand]

Im searching my sub vi for any false or true values which is compared to the array appendix and if it matches up then a true is sent from the equal to the search 1-D and to the resulting indicator. If any time the boolean from the subVI and the array apendix dont match up then the appropriate error from the string appendix is sent to the select and displayed on the front panel. The way I have it works perfect for detecting the errors on the circuit board and displaying what is failing due to shorts and mechanical errors. Im assuming the way I have it set up just detects the programmable errors and what you mentioned is that I dont have anything to detect the hardware errors (such as the daq not even being hooked up to the computer???) but that was kind of what I was asking. I dont understand though how if the Daq modules arent even connected to the computer how is that subVI even working and sending out any type of boolean signal to be compared with the appendix array. The subVI is just simply 32 inputs from a 9425 digital input module that checks the voltage at 32 different inputs and compares it with the array apppendix. Except I am only using the amount of inputs listed in the array appendix.  So basically what am I missing to pick up these possible hardware errors??

[Dennis_Knutson]

What you have set up only detects unit under test errors. There could be logic/programming errors or external hardware errors. The subVIs are not working if there is no hardware. They are returning an error and the Boolean state of the read should be ignored. The subVIs will always return something, even if it's a default value.

Shown below is some of simple optiopns you have for error handling. Look through the shipping examples. You will see a lot in them as well.

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

[cmhand]

It looks like the middle option may be my best option because I already have a select set up in each frame that would display my error message. If I were to set up every frame with that error function would I just wire that after the equal function??

[cmhand]

Also where are these shipping examples you speak of? I searched the examples and not quite sure where they are located