Conflicts in building LV project...

[mnx]

Hi,

I have developed an application main vi which uses some instrument drivers and some other sub vis for operation.It works absolutely fine and shows no error when I run it directly.But while creating the project for the same it is unable to load those instrument drivers properly and showing several conflicts.How can I resolve all those and why is it happening?

[LV_user1]

Can you tell what error you are facing and for which VIs?

[mnx]

I can see conflicts mainly arising due to the same name of several vis in the instrument drivers. So do I need to change the name of each of those before building my project or is there any other method that I can use?..Attached is the conflict screenshot for reference..

[crossrulz]

It looks like you just copied your drivers into your project folder.  That is where the conflicts are.  So you have a choice.  Do you want the drivers to be in LabVIEW's inst.lib or do you want them in your project folder.  Whichever you don't want get rid of.

[mnx]

Hi Crossrulz,

Thanks for replying

I have a couple of queries..

I want to build an installer for my application and I think putting drivers in the project will be better.What is your opinion on this?.

And, how to remove drivers from LV's inst.lib?

Also, If I remove drivers from LV's inst.lib,will it not give problems in future while creating some other vi or application? 

[mnx]

Can anybody please tell me the steps to use instrument drivers in a project?

[mnx]

Any thoughts on this??..

[PaulG.]

Alway leave instrument drivers in Inst.lib. The only other copies of these drivers should be in the different versions of LV. Copying these drivers for each project is a real pain and creates the conflicts you speak of.

I've experiened a lot of conflicts in projects. Most stem from multple versions of the drivers in multiple versions of LV and pointing to instrument drivers in the project instead of Inst.lib.

I use Auto-populating folders in my project. Every instrument in my project gets its own folder. I create a sub-vi in the folder and *copy the contents* of the vi tree for that instrument and save that as the vi tree in the project folder. I also save all associated sub-vi's for that instrument. I've alleviated most of my bad experiences with project conflicts with this approach.

Another source of conflicts: some drivers are the same for different models of hardware. For example Agilent 34970, 34972, 34901, 34903, etc,all use the same drivers (Agilent 34970) from the inst.lib. In this case I leave one copy of the vi tree in the project and create subdirectories under that project folder for each additional instrument that uses the same drivers.