LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Adding dependency conflicts Ver 2009 f3

Solved!
Go to solution

Hello seasoned LV'ers

 

I started having this problem when I added some inst drivers from another machine without installing them through the normal driver install. The drivers are the Agilent ESG Series drivers for my E4421B Signal Gen, and my HP8563E spectrum analyzer. Both versions are from Labview 8.

 

After going through the discussion forums, I have:

-Since deleted each of these driver .vi's from the project.

-Deleted them from the C:\Program Files\National Instruments\LabVIEW 2009\instr.lib directory.

-Re-saved my project, and now do NOT get the error.

-Downloaded the same version from the "Find Instrument Drivers" in my project help.

-Did a mass compile of the ESG driver directory.

-Re-saved as if...

-When I attempt to place my "initialize" .vi on the Block Diagram I get the warning shown in the .jpg below.

These drivers seem to work, but I get the never ending error, and not enough information that I can correct it. Can anyone give me a hand with this please?

0 Kudos
Message 1 of 23
(4,000 Views)

Its just warning you that adding a library member to the project adds the whole library to the project.  Ignore the warning- in this case it is safe 


"Should be" isn't "Is" -Jay
Message 2 of 23
(3,997 Views)

Well That was an "Easy" button. THANKS!

0 Kudos
Message 3 of 23
(3,990 Views)

oops... now I get this every time I open up the main vi.

0 Kudos
Message 4 of 23
(3,970 Views)

Yes, You will need to resolve the conflicts in the project (Yes, it is sort of a pain but, had you installed the Driver correctly in the first place.....)

Well, Pain is a good teacher.


"Should be" isn't "Is" -Jay
Message 5 of 23
(3,966 Views)

Sigh... ok, I'm willing to learn this.

 

Is there somewhere that explains differently, or more expansively what these conflicts are and how to resolve them? 🙂

 

pain is good, pain is good, pain sucks

0 Kudos
Message 6 of 23
(3,959 Views)
Solution
Accepted by Hobbs23

On the ribbon bar of the Project Explorer there is a ! Glyph that does a resolve conflicts operation

Hit it

Then select the "Good" item and press "load with selected": OK any "Resave alls" that pop-up;

Rinse and repeat until you have had enough pain to teach you not to do that again.


"Should be" isn't "Is" -Jay
Message 7 of 23
(3,952 Views)

Sigh.... it shall be done.

0 Kudos
Message 8 of 23
(3,946 Views)

I can not seem to get the conflict Glyph to become unshaded, and recognize my conflict. I select any number of possible targets, right clicking or hammer does not intimidate the Glyph.

 

The main .vi that I run, which prompts the error message alters the files shown in the project. What it is really drawing my attention to is unclear to me. The error does not return until I close out of the project, and try to run the main .vi again.

 

Thoughts?

0 Kudos
Message 9 of 23
(3,940 Views)

Lest see a snip of the Project Explorer

 

Is the conflict in "Dependancies"?  You ma need to select a conflicted item and Right Click "Resolve Conflicts" from there.  You don't have Auto-populating Folders do you?  (Think it though- you can't change the load from location of a conflicted item in an auto-populated folder) so you might need to STOP THAT (autopopulating folders are evil anyway)


"Should be" isn't "Is" -Jay
Message 10 of 23
(3,930 Views)