Hello Guru's, etc.
I have been learning best practice the hard way lately. Correcting as I go, has cleaned up much.
The problem I have now is when I place an Init.vi on a block diagram from the newly downloaded HP8563E driver (ver 8.2.1), I get a warning as shown. This happens with NO OTHER driver in the pallet that I have tried.
-I have just gone through correcting for similar errors, caused by having my project files all over the place including drivers in the wrong place. Once I was shown the errors of my ways, and corrected it, my dependency conflicts all went away.
I have deleted and re-downloaded the drivers to no avail. When I mass compiled the project, it complained the tree.vi was bad. I don't know how that associates to the init vi? Would someone mind giving me a hand up with this one please?
I'm not sure that I have seen the Project Explorer ever show me what I realized was an error. I'm using LV2009, so I'm not sure how far along they were with conflict resolution.
-But anyway, I tried a different driver today, the Agilent E4418 driver, compatible with ver 8. I got the same warning as my first post, but I told it to add it anyway. When I opened the project up fresh it looked ok, until I ran the primary vi. This is what It gave me. All you can do is click close, so I did.
-I opened up what I could fit on the screen to show you what I am seeing. I clicked on the different files and at no time did the conflict icon unshade. Ideas?
I tried a different driver, (Agilent E4418) and It did the same thing. This time I told it to add anyway. When I opened up fresh I got the warning shown on top. I said close and printed a snip of what I see in the LV-2009 version Project Explorer. I guess I am not sure what the conflict should look like. Ideas?
Sorry, the pictures are too small to see, can you attach them? You can click the yellow triangle for "resolve conflicts" on the project explorer toolbar. The individual items are marked with a yellow warning triangle in the project tree as well.
Likely your items are cross-linked, and you have to tell it which file you actually wanted loaded.
Now that does make sense. I will attach the files. That "resolve Conflicts" icon always remains shaded. I tried clicking on the files that it warned about, expecting to get a reaction, or different options but no. I'm almost ready to rename the file or something like( i'll show you file conflict!). but no.
I did that and found no errors, so I created an error. You notice both drivers are naming the menu file the same exact file name. I thought maybe in the earlier versions of LabView They thought nothing of lifting the hood, and renaming the files like the .mnu files. So...
-I renamed all of those files... NNNNOOOOWWWW I got errors that I can see. uh-huh. I do. It gives you a tiny little yellow triangle on the file in question, and the complaint that it was deleted, moved or renamed. Still no option for corrective action. I put it back.
-But that annoys a point, because out of all the files it complains about in these 2 driver collections, It's the menu files, that happen to be the same name, that ONLY are public, and that happen with other drivers that I download of similar directory structure and work for LV version 8, and 9.
Ok, try this on for size. I tried editing the pallet. Synchronizing the directory, renaming the actual mnu from here. The conflict could care less, but I did realize that I may have too many variables because there are actually 3 instrument drivers that whine about this, but only if I use them in the vi. So I removed them.
- Then I started by just loading the Power Meter Agilent E4418 Driver. I added an init, and a close to the vi. I then went into Pallet edit and sync'ed the directory. Saved all, and exited. No complaints when I opened and ran the vi.
-I believe I have a base line for testing the others. Now at this point I would think other people could chime in with Ideas for properly editing the pallet in order to keep the other drivers from conflicting. I may just need to look up the problem in my new understanding of what I think is causing it. I would think this would be a normal thing for those that used to run LV-2009 f3 Base package. Recommendations PLEASE? 🙂