Two copies of the same VI are deployed causing -18002 conflict

[DowNow_]

We're calling some LabVIEW instrument driver VIs as subvis in some steps, and calling the VIs directly in other steps. The deployment tool deploys two copies of the VIs, the subvis in VISupport directory, and the top level VIs with all the other code modules. Can anyone suggest an overall strategy to overcome this runtime error -18002?

All the solutions we can think of involve manual coding. Dynamically load and unload each offending step, hand enter relative paths, always call each VI as a subvi (wrapper VIs), fix the deployment by unchecking the code module VIs. Anything we missed, any recommendations? Thanks,

cc

[.aCe.]

Have you tried consolidate files shared by projects option http://zone.ni.com/reference/en-XX/help/370052K-01/tsdeploysystem/infotopics/customizecomponents/ in Labview VI options?

[snowpunter]

You could try using a Packed Project Library in the LabVIEW Options dialog in the Deployment Utility, though I'm not sure if that will fix your problem.

Your best bet is to not mix calling low level VIs and wrapper VIs that also contain the same low level VIs in the same automation. We create wrappers and only call those, or make VISA Write/Read wrappers and call those instead of calling the low level VIs to issue instrument commands.

[DowNow_]

Hi,

Thanks for both good replies. Still working through it so far. Do you use packed project libraries in your deployments?

cc