file path corrupted

[RHutchings]

I have one instrument that I can't get to work because LabView is looking in the wrong place for it. The files are on the c drive in the inst folder with all of the rest of the instrument vis, the other instruments work fine. when I look at the path on this PC by hovering over an existing and fully functional program, the path shows C:\Program Files (x86)\National Instruments\LabVIEW 2017\instr.lib\Keithley_2600_Series(2.5.0)_LV_2009\Keithley_2600_Series(2.5.0)_LV_2009. I've had trouble with this vi on other PCs but always got them to work. 

[zou]

1. make sure instr.lib is in the search path

        Toolbar => Tools => Options => Paths

        Click the pulldown menu, choose VI Search Path.

2. check the instr.lib path, make sure the Keithley folder is in there.

[RHutchings]

That is all correct. The vis appear in the instrument drop down. I tried running an example program and LV still can't find the vis.

[Michael_Munroe]

Are you using LabVIEW 2017 32-bit?  You may be running 64-bit and saved the instrument in the wrong version.

Suggestions:

1. Mass Compile the instrument folder (Tools -> Advanced -> Mass Compile...)

2. Open the VI Tree in the instr.lib folder and Save All

3. Open the sub-vi and it should show the browse dialog prompting for missing VIs.  Browse to find the VI and save the VI afterwards.

4. The path shown is 139 characters.  The driver may exceed the 255 character limit.  Rename the top folder.

[RHutchings]

Thanks, I think I'm heading in the right direction anyway. Now I'm getting a GlobalVariable cmplaint.

 

[GerdW]

Hi R,

---

@RHutchings wrote:

Thanks, I think I'm heading in the right direction anyway. Now I'm getting a GlobalVariable cmplaint.

---

There should be no global variable within the device driver library!

Did it come with the original driver installation or did you add it to the library?

[RHutchings]

It came with it. It lives in the Private folder

[billko]

---

@RHutchings wrote:

Thanks, I think I'm heading in the right direction anyway. Now I'm getting a GlobalVariable cmplaint.

 

---

It's not a "global variable" complaint; it's a scope complaint.  Your global is private in scope, and something outside the library is trying to use it.  Somebody coded something wrong.

[RHutchings]

Funny thing is, it's just this PC out of 5 or 6 that's complaining. I just got this PC from IT and had LabVIEW installed on it fresh. They didn't install the VISA so I had them do that today. It didn't help.

[RHutchings]

I think I figured it out. After looking closely at the paths, I see they point towards the 64 bit version which didn't get installed on this PC for some reason. I'm having our IT guy install the 64bit version ASAP. I think this what mentioned in this chat somewhere but it didn't sink in.