LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Suspicious build in Labview 8.6f1

Solved!
Go to solution

Hi,

 

 I am trying to make a build of my project containing a couple of instrument drivers. But Labview is reacting in a weird way when it's making the preview of the build, I have got this message:

"LabVIEW prevented a file name collision during the build. Duplicate file names cannot be copied to the same destination. You can rename files as part of the build process to avoid name conflicts.

The following files were moved to a unique location:

C:\Program Files\National Instruments\LabVIEW 8.6\instr.lib\Array 3711ALV80\Public\Initialize.vi
C:\Program Files\National Instruments\LabVIEW 8.6\instr.lib\Tektronix TDS 200 1000 2000 Series\Public\Initialize.vi
C:\Program Files\National Instruments\LabVIEW 8.6\instr.lib\Agilent 34970A\Public\Initialize.vi
C:\Program Files\National Instruments\LabVIEW 8.6\instr.lib\TTI TSX3510P QL355\Public\Initialize.vi
C:\Program Files\National Instruments\LabVIEW 8.6\instr.lib\TENMA 72-685X\Public\Initialize.vi
C:\Program Files\National Instruments\LabVIEW 8.6\instr.lib\Tektronix TDS 200 1000 2000 Series\Public\Utility\Error Query.vi
C:\Program Files\National Instruments\LabVIEW 8.6\instr.lib\TENMA 72-685X\Public\Utility\Error Query.vi
C:\Program Files\National Instruments\LabVIEW 8.6\instr.lib\Tektronix TDS 200 1000 2000 Series\Public\Utility\Reset.vi
C:\Program Files\National Instruments\LabVIEW 8.6\instr.lib\TENMA 72-685X\Public\Utility\Reset.vi
C:\Program Files\National Instruments\LabVIEW 8.6\instr.lib\Tektronix TDS 200 1000 2000 Series\Public\Close.vi
C:\Program Files\National Instruments\LabVIEW 8.6\instr.lib\TENMA 72-685X\Public\Close.vi
C:\Program Files\National Instruments\LabVIEW 8.6\instr.lib\TTI TSX3510P QL355\Public\Close.vi
C:\Program Files\National Instruments\LabVIEW 8.6\instr.lib\Agilent 34970A\Public\Close.vi
"

 

I thought Labview was able to make the difference between all the functions of the different instrument drivers, but apparently it's not working.

Labview is creating in the final build a couple of instrument directories with all the VI inside.

 

 

Inside my soft, I am loading some VIs in memory (with reference) before launching the main front panel, that's why I have to put this VI as always included inside the source files of the build.

If I am removing the VI with all the instrument drivers used inside, Labview is not making anymore directories, but I cannot launch my soft anymore too...

 

We didn't have this problem previously with Labview (8.2; 8.2.1; 8.5). Does anybody have some clues??

 

Thanks

0 Kudos
Message 1 of 3
(2,978 Views)
Solution
Accepted by topic author BugVW

Hi BugVW !

 

Check this link and tell me if the problem persists :

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P9nSSAS&l=en-US

 

Regards,

 

 

Message 2 of 3
(2,936 Views)

Hi Emmelyne,

 

Yeah.... it's working! But this is a weird way to fix it no?

For each instrument driver you will have an init, a close, a reset function, and you can't call them the same way?

For example in my company, we're a couple of people working on the same project, but we're just exchanging the source code, without the instr.lib. We would have to rename all our instr.lib in the same way to make it work on each computer?

I thought Labview was able to make a difference between each instrument driver, so between each init or close or reset function. When we're making a library with Labview, there's always some init, close, reset VI created by default.

 

Is it a Labview bug or is it a wrong to work with instrument drivers?

 

Anyway, thanks for your help!!

0 Kudos
Message 3 of 3
(2,919 Views)