Import CVI Instrument Driver in LabView 8.6

Hi,
I am working on Instrument Driver and have code developed in LabWindow/CVI. I have got the information of importing those code in LabVIew through Import CVI Instrument Drive option in Tools»Instrumentation but can't able to see such option on the stated menu. We are using LabView 8.6 Evaluation Version and about to get the License of the same. Does such option unavailable in 8.6 version or am i missing somewhere??
Please help me !!
Thanks in Advance,
Vivek
Solved!
Go to Solution.

Hey Thanks Alot Dennis. I didn't know we need to perform such things. But Why we reaaly need to install those Wizard. If possbile would definitely like to know the reason.
Thanks,
Vivek

Similar Messages

No longer able to import CVI Instrument Driver in LabView 2010

Hello,
I used to be able to download the Import CVI Instrument Driver Wizard in LabView 2009, but there is no wizard for 2010?
I also tried importing the driver with the shared library import, but then Binary, Slides and Rings do not come up with their values i.e. if my slide in CVI has 3 positions :
Description      Value
Item 1                 1
Item 2                 2
Item 3                 3
or if my Binary has
Description      Value
On                        1
Off                        0
they do not import the description into LabView 2010?
I tried copying the directories created by the 2009-wizard to the directories of 2010 i.e.:
from     C:\Program Files\National Instruments\LabVIEW 2009\resource\CVIFpConv
to          C:\Program Files\National Instruments\LabVIEW 2010\resource\CVIFpConv
and
from     C:\Program Files\National Instruments\LabVIEW 2009\project\_DriverCtoLV
to         C:\Program Files\National Instruments\LabVIEW 2010\project\_DriverCtoLV
and the wizard loads and runs until I specify a .fp file and then I get the error in the jpeg attached. When I try to open the block diagram (FC_RFL_Initialize.vi), it says you need a password to view it, so that stops my debugging.
Attachments:
Error using Instrument Driver Import Wizard in LabView 2010.JPG ‏88 KB

HI,
I downloaded the wizard and when I tried to import a driver I got this message shown below...(labview 2010)
Thanks...Ness
Attachments:
Error message.JPG ‏140 KB

Import CVI Instrument Driver failure

Using the "LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers" utility, I successfully converted (wrapped) an IVI-COM instrument driver for use with LabVIEW 8.2.1. However, I have a customer who insists on using LabVIEW 6.0. When I attempt to use the "Import CVI Instrument Driver" tool of version LabVIEW 6.0, I get a crash: Failure: "funcmenu.cpp", line 1873. (Specifically, the error occurs after pressing "OK" to the "CVI Function Panel Converter" dialog and selecting the DLL.) The pop-up suggests to navigate to www.ni.com/failure for assistance in resolving the problem, but when the proper data is entered in that web page, it errors also.
1. Is it possible to do what I'm attempting to do?
2. Any ideas on what is causing my problem?
Thanks

The import tool for CVI drivers only supported IVI-C with LabVIEW 6. If there is no IVI-C driver available, you might be able to write C wrappers around the IVI-COM functions or manually write all of the ActiveX calls to the IVI-COM driver.

"Import CVI Instrument Driver" doesnt work when parameter is viSession pointer

Why does "Import CVI Instrument Driver" menu selection generate a LLB that has VIs which have not been generated correctly when a VI function parameter returns a ViSession pointer. The only one generated correctly was "initialize", however, "autoConnectToFirst" was not. They both have similar prototypes in the .FP file. When I look at the block diagram of the init VI, there is a "IVI New Session" control, but in "autoConnectToFirst", there isn't. Therefore the session returned in Labview is 0, but the session returned in C (through debugging) is a valid session.

The strict answer to "Why?" is because we only implemented the special initialization code for the Initialize function. "autoConnectToFirst" is optional in VPP 3.2, and we chose not to implement it as a special case.
You'll just need to fix the Call Library Node in your VI wrapper to use the proper prototype. I'm not sure how best to handle the "IVI New Session" call; it really expects both a name and viSession, and "autoConnectToFirst" doesn't seem to return the name of the resource it chose. The "IVI New Session" function is what tells LabVIEW how to connect the VISA (or IVI) resource names with your viSession. You could call "VISA Find Resource" to get the first name and see if it's a supported device; this is supposed to match what "autoConnectToFirst" does.
Along those lines, you might be better off implementing "autoConnectToFirst" yourself in LabVIEW. I.e., call "VISA Find Resource", and loop through the results calling your "Initialize" function until you don't get an error.
Let me pull up a soapbox for a moment...
There's a common misconception that "Import CVI Instrument Driver" creates a perfect LabVIEW wrapper around a VXIpnp WIN or IVI-C driver with no manual intervention. The reality is that you will almost always have to do some manual fixups of the converted driver.
In LabVIEW 7, we improved the converter somewhat, and converting an IVI-C driver is now a three-step process: pre-processing the IVI-C driver, importing into LabVIEW, and then doing some programmatic fixups of the results. The resulting wrapper is better than earlier versions of LabVIEW, but it's not uncommon that you will still have to manually fix something up to make it a good, usable wrapper.
That's why we consider "Import CVI Instrument Driver" to be a tool for instrument driver developers. If a vendor creates an instrument driver for an instrument in C, it doesn't make sense for each end user to have to create the LabVIEW wrapper, including all the manual fixups.
Of course, if a vendor wants the best LabVIEW connectivity, they should write a LabVIEW-based driver. But if they're going to only write C- or COM-based drivers, they should create and distribute high-quality LabVIEW wrappers and not force end users to figure out how to do it on their own.
My two cents.
Brian

Import CVI Instrument driver with void pointer

Hi,
I would like to use a CVI instrument driver that contains void pointers as parameters in LabVIEW. There are additional parameters which declare the kind of data where the void pointer points to.
If I try to import this driver to LabVIEW I get warnings that the void pointer paarameters are converted to I32 since LabVIEW do not have the void pointer.
Does anybody know if it is possible to import a CVI function with void pointers that will work properly in LabVIEW? How do I have to handle this converted void pointer?
Thnaks,
erik.

Erik,
you may have a look at this discussion forum thread.
Best regards,
Jochen Klier
National Instruments Germany

Import CVI instrument driver in 8.0

I have CVI instrument driver which just has some c funstions and it does not communicate to any instrument.
It always worked for me in 7.1.
After getting 8.0 and I had to download and install LabVIEW Interface Generator for LabWindows-CVI. It did not work.
I get following error.
The following instrument driver VI(s) cannot be created. This may indicate that the function in the CVI function panel (.fp) file is not consistent with VXIpnp and IVI standards. For example, the function has user-defined data types or has a duplicate function name in the .fp file.
But this works in 7.1.
What do I have to select in Class group?
Which step am I doing wrong?
LabVIEW Interface Generator for LabWindows-CVI is different from 7.1's built in generator.
Sheetal
Thanks.
CVI 2010
LabVIEW 2011 SP1
Vision Builder AI 2011 SP1

I've been playing some more and here is where I'm at.
I
downloaded DriverCtoL.exe from ftp.ni.com. I
forget where exactly I got it and I can’t find it again. I run the program and
it installs the tool/convert cvi to vi command. When I run the command and find
the 2533.fp file it asks for, I get and error message.
“Error
-43990 occurred at Not a valid function panel file.
Verify that
the function panel file is valid and attempt the conversion again.”
Is there
another way to convert the cvi to vi? Or, what step am I doing wrong?

Import CVI instrument driver issue

When I import CVI fp into labview it converts my const char * to int without any warning...
For example CVI function:
void my_func(const char *value);
Labview conversion:
void my_func(int *value);
Any help?
Thanks.
CVI 2010
LabVIEW 2011 SP1
Vision Builder AI 2011 SP1

Hello Sheetal,
I wasn't able to reproduce the problem if I use char * instead of const char * in the function panel. Were you able to do so? Either way, when you initially convert your FP to LabVIEW code, you are asked to specify a DLL that contains the code associated with the function panel. I would double check that the function prototype inside the DLL specified in the 'select a shared library or DLL'. is not set to int *. When I used char * or const char * in my DLL, LabVIEW convert the parameter to be a CStr data type, which is the same as char *.
Thanks
Wendy L
LabWindows/CVI Developer Newsletter - ni.com/cvinews

HP 54501A - Instrument Driver for LabView v.7 or v.8

Hi all,
I'm looking for HP 54501A - Instrument Driver for LabView v.7 or v.8. I have NI gpib/usb controller installed, but cannot control the scope via Labveiw.
The link I found at NI web site within drivers section seems to be broken so I couldn't download it!
Please, anyone, suggest/help!

The link you were given works for me. You can try it again. The given link brings you to a page where the CVI and LabVIEW drivers are listed. the direct link to the LabVIW driver is http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=E3B19B3E9455659CE034080020E748... .

Teststand call cvi instrument driver

I'm new to working with instrument drivers in TestStand. I'm trying to use TestStand to call a CVI instrument driver dll (for Agilent N5767 power supply), and then perform a specific function (init, set voltage, set current, etc.) All of the instruments in my test bench are connected via LAN, and they are configured in NI MAX too. I thought it was pretty straight forward, but I'm obviously missing something. Attached is the simple TS 3.1 seq file with the steps I'm trying perform.
Attachments:
N5700_on_off.seq ‏20 KB

Hi Bkoch1,
Please elaborate on the problem you are experiencing. I am able to open the sequence file you have attached and view your steps and on the surface, this seems like it should work just fine. What indications are you experiencing that it does not work fine? Have you tried setting breakpoints and using the Watch Window to monitor variables to ensure that they are being passed into the DLL? Please explain what the problem is and try to narrow down where the problem occurs and we would be happy to help you.
Regards,
Jackie
DAQ Product Marketing Engineer
National Instruments

How can I use a labview VI as a CVI instrument driver

I have a VI for the Keithley 485 that would like to convert into a form usable by CVI. I don't have labview so I cannot generate a DLL based on the VI.

daquiry:
I've downloaded the 485 driver from both the NI Instrument Driver Network and the Keithley site, any they are both written natively in G (LabVIEW). The driver is rather simple, and is just making 488.2 / VISA calls. Keithley's site also doesn't offer drivers for the 485 in any language other than LabVIEW. This surprises me. I would suggest contacting Keithley and verifying that no C driver exists for the 485. If that's the case, then you may have to write a driver yourself. The 485 Quick Reference guide should have a description of all the available GPIB commands, along with sample code. Since you probably won't need the full range of functionality of the GPIB interface, writing a driver for what you do need shouldn't be t
oo bad.
I've written a short instrument driver which contains only a simple read() function. In implementing this, I've endeavored to translate the G code into C, but unfortunately, I don't have an instrument, so I haven't been able to test it.
Hope this helps..
-- Chris
Attachments:
cviKe485.zip ‏5 KB

How to add instrument driver on labview in Mac

Hi,
I used to use Labview on windows and there was a menu in Tools >> Instrumentation >> Find Instrument Drivers and then I was able to find the driver for the instrument I was working on and install.
However, since I've been using labview on mac, there is no such menu. It only takes you to the website where I can search and download the instrument driver in a zip file, but then I'm not sure how to install the downloaded instrument driver on the Labview in Mac.
Can someone give me a hint?
Thanks,

Unzip and move the folder to instr.lib.

Importing CVI driver to LabVIEW 5.1

Hi,
I want to import a CVI driver to LabVIEW 5.1. I am familiar with the process of converting CVI driver to LabVIEW 7 library but i do not find that tab in labVIEW 5.1
Can somebody help me out?
Regards,
Siddu

Hi Siddu,
Since there isn't a direct way to "Import CVI Instrument Driver" to LabVIEW 5.1, you will have to build the code that calls the CVI driver yourself. You can either call the CVI code using a CIN Node or you can compile the driver to a DLL and call it from LabVIEW using a Call Library Function Node. I definitely prefer the latter approach. All you then have to do is create small 'wrapper'-VIs that call each function in the DLL. Remember to connect the front panel objects of the VI to the connector pane, so it can be called as a SubVI.
Search our Web site for information on how to create a DLL in CVI and use the following manual for information on how to call the DLL from LabVIEW:
Using External Code in LabVIEW
- Philip Courtois, Thinkbot Solutions

Conversion of an Instrument Driver from LabWindows/CVI to LabVIEW

Hello All,
Conversion of an Instrument Driver from LabWindows/CVI to LabVIEW
http://zone.ni.com/devzone/conceptd.nsf/webmain/9A93316BEBEDB17786256FA300675A0A
But I can not find any hyperlinkt to download
"LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers"
Is there any evaluation version for downloading?
Thanks,
nonomiya

So strange,
I go through three pages but does not find any entry for download,
hmm...,
1. After press the hyperlink,
See Also:
LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers
2. and for a resuest info. form.
3. press download..
====
LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers
System Requirements
NI LabVIEW 7.1 or later
Windows 2000/NT/XP
Use the LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers to create LabVIEW VIs for VXIplug&play and IVI-C instrument drivers from function panel (.fp) files.
Instrument Driver Network
Before using the conversion utility to create a new instrument driver wrapper, please visit ni.com/idnet to see if a LabVIEW Plug and Play instrument driver is available for your device. The Instrument Driver Network (IDNET) provides support for more than 3,000 different instrument models from over 170 different instrument vendors.
Recommendations
This utility was created for developers of C-based instrument drivers who wish to provide a LabVIEW interface, but do not develop a LabVIEW Plug and Play driver. By developing the C and LabVIEW interfaces together, it keeps the components synchronized, and eliminates the need for customers to create their own LabVIEW interfaces. Vendors should distribute the LabVIEW wrapper files with the associated VXIplug&play or IVI instrument driver, so that end users do not have to visit multiple web sites to download the complete driver.
If you are not an instrument vendor, we recommend that you use this utility only if you have instrument driver expertise. Access to the instrument driver source code is preferred, in case you need to edit the C instrument driver in LabWindows/CVI.
After generation, the wrapper VIs should be tested with the instrument.
Instructions
Once you install the software, simply access the utility from the Tools>>Instrumentation>>Import CVI Instrument Driver...menu in LabVIEW. This software replaces the built-in tool and provides feature enhancements.
For additional information on this utility, view the resources below.
Readme for the LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers
Submit your Driver
Visit the Instrument Driver Network
nonomiya

Importing Instruments Driver from LabWindows/CVI

Does anybody have got wintools_32.dll library ?
I need it to convert LabWindowc/CVI Wintools Instrument Driver to Labview.
Could you send it to me?
Romek.
[email protected]

Hi!
Thanks for your answer.
Exactly, I've tried to import LabWindows/CVI instrument driver to Labview.
This Instrument driver I've found here:
http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?p_guid=B45EACE3F04956A4E034080020E74861&p_node=DZ52176&p_submitted=N&p_rank=&p_answer=&p_source=External
During import procedure i was asked about wintools_32.dll library.
Personally I am interested in System Tray icons functionality of this driver.
I'm not sure that wintools_32.dll is Labwindows/CVI library, but i've searched Microsoft Windows pages with no results.
Regards.
Romek.

I have an in-house instrument driver written in labwindows, is it possible to use this driver in labview?

If this is not possible, how do you go about converting it for use in labview?

Just go to Tools>Instrumentation>Import CVI Instrument Driver. In LabVIEW 5, it's under the File menu and is called Convert CVI FP File.

Import CVI Instrument Driver in LabView 8.6

Similar Messages

Maybe you are looking for