The Vi not executable.

[zy6]

(1) I can run this vi individual without any problem.

(2) after I build test sequence, it can not run.

(3) I checked all the vi at 2013 version.

Thanks for help.

see attached files.

[PalanivelThiruvenkadam]

Can you explain clearly which is your main vi and which vi has the problem and what your application does?

[zy6]

Hi:

 (1) IRobot test engine is main vi

(2) Initailize DAQ_CMD_PERBR is try init the DAQ.

this vi is running fine when I run it individual.

but after build , it can not run .

Thanks for help.

[JÞB]

Did you build and run an installer to install the needed runtime drivers?

[zy6]

Hi:

 do you mean 2013 labview runtime engine ?

 I have development 2013 labview version.

it should not need run time engine, is it right?

Thanks

[A-Guz-Man]

So you can run the VIs, what do you mean then by "after I build test sequence, it can not run." or "but after build , it can not run"

You are making them into an executable and then they can't run in your development machine, is that right?

[A-Guz-Man]

If this is the case you may be missing adding the dynamic VIs dependencies when building the executable:

https://forums.ni.com/t5/LabVIEW/Executable-with-Dynamic-VIs/td-p/937434
https://forums.ni.com/t5/LabVIEW/Error-1003-when-dynamically-calling-VI-within-an-executable/td-p/29...

Do you call any VI dynamically? Are you using any toolkit/module?

[GerdW · Accepted solution]

Hi zy6,

the error message says: "DAQ_CMD_PERBR.vi is not executable when you try to open its VI reference in SeqUUTCmd.vi"…

This DAQ_CMD_PERBR contains a lot DAQAssistent calls: I "heard" that they have a tendency to get broken in executables.

Replace those DAQAssistent calls by plain DAQmx function calls and see, how far you get!

Edit: Please don't put "Help" and "Thanks" in the title of all your threads! It is clear you need help when you create a thread and you can thank by giving Kudos…