LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

VXI libraries update

I'd want to upgrade some VIs from LabView version 4 to version 5.0.1, 6 and 7.
When I open them, VXI VIs (VXIin.vi, VXIout.vi, ect) are recalled as VXIin_old.vi... and they don't work because LabView cannot find the code interface node (.lsb files) to load in these subVIs.
Where could I find these codes? In the old Mac where I worked whit Labview 4 i can't find .lsb files.
Can you help me?

Thanks
0 Kudos
Message 1 of 5
(2,971 Views)
Those VIs distributed with LabVIEW 7 do not use a CIN. They have a Call Library Function. What I suspect has happened is that you had a distribution llb with the old functions in them and that is from where you're having the problem. Check the hierarchy and see if the paths are LabVIEW\vi.lib\instr\vxi\old. If you have an llb with the old functions in them, you can delete them from there and LabVIEW should automatically find the v7 replacements or you can manually replace each instance.
Message 2 of 5
(2,971 Views)
Following with Dennis's solution here is a link to an example taht can automatically remove the VI.lib files from an LLB.

Run this example on your LLB and you shoul dthen be able to open the top level VI up and it will find the new vi.lib files rather than the old ones. You may have to run the VI in the older version of LabVIEW.

Removing vi.lib Files from a Hierarchy, Directory, or LLB

Evan
National Instruments
0 Kudos
Message 3 of 5
(2,971 Views)
Nice. I'll have to save this for future reference.
0 Kudos
Message 4 of 5
(2,971 Views)
Thank you very much for the vi. I have another question.
I imported a lot of files from a mac to a PC. The namefiles with a * symbol are automatically changed in an _ but the VIs don't recognize the subVIs with the new name. What can I do? Is there a VI that can help me?

Thanks a lot
Giacomo
0 Kudos
Message 5 of 5
(2,971 Views)