problems transfering development to deployment equipment

[elgir]

hello I have the following problem:

I have a computer with labView 7.0 and teststand 3.0 for development and my application runs perfectly with the User Interface created for it.

but I have another computer with just TestStand 3.0 for deployment.

the idea is run the application in the deployment computer.

if I open the application in the deployment computer using the sequency editor and run it it, works with no problem but if I try to use the operator interface it promps an error : "the vi is not executable".

and I can't really understand why I can run it from the sequency editor but not from the User Interface.

what and how should modify the user interface in order it will run the application?

I hope some one will help me

thanks a lot

elgir

[~jiggawax~]

Hey elgir,

So basically you have 2 computers: the development PC and the deployment PC.  Do you have the sequence editor on both PCs?  If so then are you saying that the sequence runs on the deployment PC sequence editor?  If this is true then you should NOT have a problem.  The Sequence Editor and Operator Interface should both be able to run sequences the same. 

My guess is that your adapter is set to use the LabVIEW development environment instead of the runtime engine.  This may be something to check.  Go to Configure>>Adapters and choose LabVIEW.  Then check to see what environment it is selected to run in. 

Also, When does the error pop up?  Does it happen after you click Run UUT or Single Pass?  OR Does the error occur when you just open up the Operator Interface?

Hope this helps,

[elgir]

jigg thanks a lot for help me

yes I have testStand 3.0 on both computers and in both computers I can execute the sequence from sequence editor.

but I copied the User Interface from development computer to the deployment computer and executed the Operator Interface and It opens in fact I can depress the Run UUT button and application runs and then stops in a step and promps a message like: "vi not excecutable".

I had same problem when I first tryied to run steps in sequence editor and I had to modify some vi to run "dimamically" but finally all sequence runs well.

then I went to the next step with it, used the User Interface and Im obtaining similar error messages.

so it seems like some other vi needs to be modified to run "dimamically" but I don't think is the apropiate way because they are several and there should be a setting or something else that will solve the problem

both computers have the adapters setting to labview-run time 7.0

thanks a lot

elgir

[~jiggawax~]

Looks like we have to try the next option for the good old "VI will not execute" error.  VIs that ship with LabVIEW, I call those native VIs, are sometimes compiled with earlier versions fo LV.  When trying to execute the VI with just the run-time engine it cannot be executed because of this compilation.  The best way around this is to mass compile all the VIs that you are using in your Sequence. Also, make sure that any subVIs you are calling (some could be native) are being mass compiled as well.  Check out this link for mass compiling: http://digital.ni.com/public.nsf/allkb/AA97C01071D7CF678625695100582F40

What this does is makes sure all the VIs being called by TestStand are now compiled to execute with the 7.0 run time engine.  If you search around on NIs website you should find others that have seen this as well. 

Hope this helps,

[elgir]

yes in fact I tried to mass compile the user interface and I get the following error: " complileFolder: error 13 at c:.........TestExec.exe

do you have an idea what could be?

I also have error messages when I mass compile all the application Vis

really appreciate your help

elgir

[elgir]

now I mass complile the VIs and reported not error.

but once I try to buld the deployment I get errors like that:

Warning: You may need to add any sequence files referenced by the following expressions:
"reportgen_" + RunState.Root.Locals.ReportOptions.Format + ".seq" in step 'Process Step Result', sequence 'SequenceFilePostResultListEntry', sequence file 'C:\Software Loading Station\SOFTWARE LOAD\Teststand\SW_Load_SEQ_Model MH.seq'

once I try to build it it promps error like : "some broken VIs ..." 

why if I mass complile the VIs with not error messages?

thanks

elgir

[~jiggawax~]

Hey Elgir,

I do not recommend mass compiling the User Interface.   That should work as is and has no correlation to the run time engine of the sequence file or adapters.  Think of the User Interface as a simple application that is not tied to your sequence or the VIs it calls.

You can ignore those warnings.  All it means is that you are dynamically calling a VI or sequence based on an expression.  When you call something based on an expression TestStand is not sure what it is calling UNTIL it actually reaches that point during execution.  Therefore the deployment utility cannot look at or analyze dependencies because it does not know what they are.

Could you post a screenshot or the actual text of the error you are seeing in the deployment utility?

Thanks,

[elgir]

yes this is the error:

[~jiggawax~]

http://digital.ni.com/public.nsf/allkb/862567530005F09E862568260067F6AE