dir.mnu dependency conflict

[jyang72211]

Hi all,

I am using LV2009 SP1, and I am having an dir.mnu dependency conflict.  See attached.  The dir.mnu is in conflict with a lvlib in my instr.lib.  I understand that dir.mnu is a generic name, but isn't it inside a lvlib, which will provide a library specific name scope?  The error said that it is conflicting with a dir.mnu in Signal Processing, which is not used or even appear in my project.  What's going on?  

[Kevin_H.]

I've never quite gotten a great grasp on why these errors happen when they do. Is the dependency problem preventing proper execution of the code? If you search the LV 2009 folder for dir.mnu you'll see there are quite a few of them. If you can find and relink it to what it was supposed to be linked to that'd be good. It kinda looks like from the warning it hasn't effected anything and was automatically resolved. If your program is running fine, don't worry about it! If not, try to figure out what the dependency was original. Maybe even remove it from the project tree if you can. It often happens when you transfer code between machines where directory paths were a little different. LabVIEW typically automatically resolves these problems and just warns you that they happened.

[fdinoff]

I have the same problem.

The dir.mnu file conflicts then appears in the dependencies section when the file is loading but when the file is loaded it disappears from the dependencies section. However the next time I load the file it says the dependecy conflicts again. This warning has not affected the code in any noticable way so I have been ignoring it for a while.

[JLBehr]

Same problem here!

This same problem started only after I added a SECOND inst.lib driver

drivers installed:

Keithley_2000_Series_(3.0.0)_LV8.0+.zip

-and-

agilent_e363x_series.zip     (ver 3.1.1)

LabVIEW Pro 2009f3

-Jason

[Kevin_H.]

I would say the best thing you can do (and what I typically do when I can't find the source of these warnings) would be to create a new project and reload all of your files into it. Does the problem persist?

[JLBehr]

Hi Kevin,

Yes, it does persist.

to recreate:

1) make and save new project (p1.lvproj)

2) Add a new VI (vi1.vi)

2a) Place in this the init code for the Keithley 2000  (vi is un-runnable due to lack of inputs, but we don't care at this point)

2b) Save vi1.vi

2c) Close vi1.vi

3) Add a new VI (vi2.vi)

3a) Place in this the init code for the Agilent E363x (vi is un-runnable due to lack of inputs, but we don't care at this point)

3b) Save vi2.vi

3c) Close vi2.vi

4) Open Vi1.vi and Vi2.vi

Error occurs on opening the second VI

Thanks!

-Jason

[Kevin_H.]

You're using LV 8.0? Are these the 2 drivers you said you downloaded?

http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=014E6EF883B9743DE0440003BA7CCD...

and

http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=0475216F9FCA5335E0440003BA7CCD...

Do you have the appropriate version of NI-VISA? (3.2)

I'll try to recreate using the steps you've listed.

[JLBehr]

Hi Kevin,

The Answers are:

LabVIEW 2009 Pro, Ver 9.0f3

NI-VISA Ver 5.0.3

Yes, Those are the correct links to the drivers,

For the HP I used the LabVIEW 2009 version

For the Keithley, I got the drivers from the Keithley site. (http://www.keithley.com/support/data?asset=52936)

- I just finished verifying that the Keithley sourced driver is the same as the ** version 8.0 ** driver on the NI site, although the "Keithley 2000 Readme.html" file is different

Thanks in advance

-Jason

[Kevin_H.]

You might want to download the latest version of the drivers (the 2009 ones) from our site instead of the 8.0 ones. If you could link a screenshot of the particular error, it might also be helpful. I haven't been able to recreate the problem yet, but I'll keep looking into it once you've tried those 2 things (2009 version and getting a screenshot).

[JLBehr]

Hi Kevin,

I upgraded the inst drivers to the 2009 version.

Started a new project, made 2 new VI's

Placed the Keithley 2000 init into one VI

When I placed the HP E3631A init into the second VI this is what I get

I close and re-open the Project

Here is what I get when I open the "keithley 2000 dmm init.vi"