Use a shared instr.lib directory

[matthias.richwin]

Hi all,

have you ever tried to use a shared instr.lib directory, which is residing on a network drive? What is the best way to accomplish this in your opinion?

Regards
Matthias

[JeanPierre]

Edit the function palette (Tools>Advanced>Edit Palette View) and include a submenu in instr.lib that points to the shared directory.

[matthias.richwin]

Hmm, I can't add a submenu in instr.lib. Don't know why...

What I can do is add a submenu in user.lib, BUT: I have a problem that the vi's in several subdirs in this directory (I have it synchronized with its directory) appear just as question marks and I cannot pick them to place them in the schematic.

Anybody out there who can give me more advice on palette building?

Thanks & Regards
Matthias

[Luther138]

I searched before I posted and I believe this is the same problem we are having.  We have a shared user library on the network.  On both computers we have the network drive mapped to L:\Labview.  But when I open a vi on one computer it says:  VI expected to be at L:\Labview was found at srv2\\Labview.  With srv2 being the actual network resource that L:\ is mapped to.  But then when the vi is opened on the other machine it says VI expected to be at srv2\\Labview was found at L:\Labview. So we always have this fight between the two, could it be that one of the computers subpallete was accidentally mapped to srv2// insteasd of L:\.  I have tried to alliviate this problem by changing the subpallet on the culprit PC to look on the L:\, but now I am having trouble reproducing the problem but it is hard to know for sure if it is fixed.  So my question is... is there antother solution or do I just have to sit and hope this one flys.
Thank you,
-Luther

[Ching_F.]

Hi Luther,

Since the problem has seemed to disappear after mapping the subpalette to L:\, I believe that you are correct in thinking that the PC may have accidentally been mapped to srv2//.  If the issue arises again though, please repost the question, and we’ll take a look at it.

Best of luck on your application, and have a great day!!

[Luther138]

    - The VI expected to be at "\\Srv2\labview\user.lib PXI\Instrument IO\Digital IO\DigIO_Port_Configure.vi" was loaded from "L:\user.lib PXI\Instrument IO\Digital IO\DigIO_Port_Configure.vi".


So here it is again, I believe what is happening is that another computer on the network is loading these resources from \\srv2\labview\ instead of L:\  but all of the computers are, in my opinion, set up the same way.  Is there a way to make sure labview doesnt look in a \\Srv2\labview\ directory or maybe you can force it to only look in the L:\ directory?  I am trying to figure out the cause of this problem then have it just up and go away sometimes only to show up later.  Anyone have any ideas?

[Ching_F.]

Hi Luther138,

Have you noticed any patterns as to when this happens?  Are there specific VI's that throw this error?  Is this specific to certain computers?

You can try to force LabVIEW to look in a specific path by going to Tool  » Options » Paths (In the Category List) » VI Search Path, and then entering the desired search path.

If this doesn't work, please let me know, and also let me know if you can discover any patterns for when this issue arises. 

Best of luck on your application, and have a great day!!

[Luther138]

It is multiple VI's and it doesnt seem to be any one in particular.
I set up all the vi search paths the same on every sinlge computer things almost seemed to be working better but alas we are still having the same problems.  Note that Srv2\labview has been mapped to the L: drive on all computers.
On one computer
DigIO_Relay_Set.vi
    - The VI expected to be at "\\Srv2\labview\user.lib PXI\Instrument IO\Digital IO\Utilities\DigIO_Create_Port_List.vi" was loaded from "L:\user.lib PXI\Instrument IO\Digital IO\Utilities\DigIO_Create_Port_List.vi".
On the other computer
DigIO_Relay_Set.vi
    - The VI expected to be at "L:\user.lib PXI\Instrument IO\Digital IO\Utilities\DigIO_Create_Port_List.vi" was loaded from "\\Srv2\labview\user.lib PXI\Instrument IO\Digital IO\Utilities\DigIO_Create_Port_List.vi".
And back and forth.

Is there a step by step procedure I can take on each computer to make sure it doesnt continue to do this?  It is very anoying for the techs when every vi they use asks them to save because:
"Name or location of the VIs changed in the file system"

Thanks again.

Message Edited by Luther138 on 01-30-2007 08:54 AM

[Ching_F.]

Hi Luther,

One thing to note is that the VI search path is as follows:

1.) First look in the project for the sub-VI.
2.) If the sub-VI is not found in the project, look in the same directory the main VI is located.
3.) If the sub-VI is not found in that directory, then go to the search path options specified in LabVIEW.

What I believe is happening is that some people are opening the Main VI's by typing \\Srv2\ in either Windows Explorer or the Run window the finding the VI while others are opening the L:\ drive and finding the VI this way.  Having people open the VI's in these two different methods can cause these messages.

Please let me know if this does not fix the issue.  Best of luck on this project, and have a wonderful day!!