LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Import CVI instrument driver in 8.0

Sheetal,

Did you ever figure this out?  I am also strugling with this new "feature."  I hear from NI sources that they are trying to discourage people from using CVI drivers - forcing people to make native LV drivers. 

Moving VI's from imported in 7 to 8 did not work because LV was not able to find the DLL - I don't want to go through each call lib function and re-point it to the DLL.  And the LV 8 tool messes up anything C function that returns an array.  Oh well, just another reason to not use LV.

0 Kudos
Message 11 of 16
(1,130 Views)
And what's "VXIPnp Error Converter.vi"
0 Kudos
Message 12 of 16
(1,123 Views)
No. LV 8 did not work same way as LV7.1. I ended up using LV7.1 and converted all of my FP to vi and then used in LV8.0
Thanks.
CVI 2010
LabVIEW 2011 SP1
Vision Builder AI 2011 SP1
0 Kudos
Message 13 of 16
(1,119 Views)
Sheetal,
 
Yes, that is exactly what I did. 
 
When moving to LV 8, I had to do some things so the VIs so they could find the DLL.  First, I renamed the DLL and LIB usnig the format that LV expects - abc_32.dll and abc_32.lib (my DLLs did not have the "_32" part). I then put the DLLs in the VXIPNP directory:
 
Copy zabc_32.dll to
C:\VXIPNP\WinNT\Bin
Copy abc_32.lib in
C:\VXIPNP\WinNT\lib
 
I then imported the VIs into LV 7.1 - createing a directory called "abc" into the instr.lib.  I could then move the entire directory to the LV 8.0 instr.lib.  Everything worked in LV 8 without any modifications!  Thanks NI for the new and "improved" import tool!
 
0 Kudos
Message 14 of 16
(1,110 Views)
Also, I did find a way to import my .fp into LV 8 directly.  First, I had to make sure I had a function called "abc_error_message."  This function is then called by VXIPnp Error Converter.vi.  Originally, my DLL had a function "abc_error_description" that did not work.  Second, in my initialize function, I had to change the "resource in" datatype from ViRsrc to ViSession.  In addition, I had to make the default "resource in" a variable and not a constant (if it is a constant, the LV 8 import does not give you an import terminal).
0 Kudos
Message 15 of 16
(1,107 Views)
Hey,
         I thought I would share my experience regarding this topic. I was using LabVIEW 6.1 earlier and had installed the CVI to LabVIEW without any problem but when I got in to LabVIEW 8.0 I couldnt find import CVI to LabVIEW in the TOOLS Menu. But then, some thing provoked my mind. So, I've decided to copy the instrument drivers from LabVIEW 6.1 instr.lib folder to LabVIEW 8.0 instr.lib folder. Finally it worked and now, I am able to see all the functions in LabVIEW 8.0
 
I guess you can find the instr.lib folder in this path
 
C -> Program Files -> National Instruments -> LabVIEW 6.1 -> instr.lib
 
I hope this will help you. And you are always welcome to ask doubts (regarding) installing the CVI drivers. We can try someother methods.
 
Also, this is one of the similar article...if you like to go through
 
 
PS: If your problem is already resolved, ignore this post
 
 
0 Kudos
Message 16 of 16
(1,099 Views)