Instrument Driver Tool has blank Source driver list.

I am trying to create an Instrument Driver form a template using the Instrument Driver Project Tool. When I launch the tool there are no drivers listed in the Source Driver pull down list. Does anyone know why this list would be blank and how to correct the problem?

If the Templates that are installed with LabVIEW are deleted they drop down menu will be blank. You can try restoring the templates (if they were recently deleted) or try to do repair for LabVIEW so the templates are re-installed.

Similar Messages

Is there a USB Instrument driver developer tool for CVI

Is there a USB instrument driver developer tool/guide for CVI?
Thanks
Chip B.
Solved!
Go to Solution.

Hi! ASIC LabRat,
I agree with your comment. IVI drivers take too much overhead and the executing speed can be very slow compared to the drivers developed using VISA platform. The previous link sent by the NI engineer was very old (2001) and doesn't really help you at all.
Please take a look at this one instead: http://zone.ni.com/devzone/cda/tut/p/id/4713.

Anybody has thermonics T-2500's instrument driver?

Has anybody developed the instrument driver (GPIB)
for Thermonics T-2500?

Hi,
Unfortunately, I was unable to locate a driver for your instrument at either thermonics website or at www.ni.com/idnet. I would like you to submit a request for this driver at: http://zone.ni.com/idnet97.nsf/instrumentdriverrequest/ and with the instrument manufacturer. We develop drivers based on demand and popularity so the more requests we have for it, the greater the possibility that we will develop one.
If you would like to try developing your own instrument driver (or modify the existing one), we have documentation, model instrument drivers, and driver templates to help at :
http://www.ni.com/devzone/idnet/development.htm
We also have a syndicate of third party vendors that specialize in National Instruments' products and services. Some of the
vendors specialize in driver development. I would suggest contacting one of the Alliance members at:
http://www.ni.com/alliance
An instrument driver is a collection of functions that implement the commands necessary to perform the instrument�s operations. In short, someone read the instrument user manual and implemented some of the functionality in a program for the end user. Instrument drivers are not necessary to use your instrument. They are merely time savers to help you develop your project so you do not need to study the manual before writing a program.
There are example VI's in LV on Instrument Connectivity. If you go to the Help menu >> Examples.. >> I/O, you will see a couple and Examples.. >> Fundamentals for File and String manipulation. I would suggest tweaking them to suit your application. Also the specific command that your instrument responds to can be found from it's manual.
Some useful resources for your application are
ni.com > NI Developer Zone >
Development Library > Instrument Connectivity
http://search.ni.com/?col=alldocs&layout=TechResources&ql=a , to search examples and knowledge bases
Hope this helps!
Aaron K.
Application Engineer
National Instruments

Is any one has the instrument driver for APD-Vp series servo motor(manufacture is Metronix in korea) for labView7.1?

Please help me.
Thanks

Hong Zhang,
The Instrument Driver Group gathers requests and may or may not come out with particular drivers based on demand.
We have some excellent online tutorials that should help you out:
http://www.ni.com/devzone/idnet/ is a must starting point for tips/information on developing your own driver. The following site specifically talks about LabVIEW instrument drivers:
http://zone.ni.com/devzone/devzoneweb.nsf/Opendoc?openagent&64325190560C97CE86256E4A006F27F1
If you have any specific questions feel free to post back and we'll see what we can do!
(also have you contacted the instrument manufacturer to see if they have one or would be willing to develop one?)
Craig H.
NI Applications Engineering

Anyone has an instrument driver for Agilent E8364 50GHz PNA

Does anyone have a working instrument driver for the E8364 50GHz PNA? I am currently tryin to use the agpna instrument driver downloaded from NI but i am having errors. The PNA balks that the "query is unterminated" and then the VI times out. Please let me know if you have a working instrument driver.

Is this the driver you are downloading?
If so,
- Are you running the Getting Started VI to test communication?
- Did the ID query pass?
- Make sure you have VISA 2.6 or later installed.
- Try running NI-spy with with the Log to File option enabled and post the spy capture.
NI Spy Tutorial

Looking for Keyence Instrument driver for LV.

Looking for instrument driver for LV developed for the Keyence LS-7500 series micrometer. Has anything seen any or done this already? Any help would be greatly appreciated. BTW I have already checked NI's listing of instrument drivers to no success.

Hello-
There are no drivers listed for this instrument at http://ni.com/idnet. You may want to contact Programmed Test Sources to see if they have a LabVIEW driver for their instrument. If they don't, you can easily create a low-level driver by configuring an I/O assistant VI for each function in the manual. Once you have this low level driver you can just combine functions to make higher level VIs. Alternatively, you can hire an Alliance Member to write an driver for you.
Alliance Member Directory
http://www.ni.com/alliance/alliance_member.htm

"undefined symbol" error while using a custom instrument driver

Hello all, I'm facing a problem related to instrument driver creation.
I want to pack a part of my code to a .FP to be able to reuse it in other applications of mine. This part of code includes calls to Windows API and a third party dll. I have included both windows.h and the include for the dll in the header file for the instrument. I developed the source code and next a little application that simply calls one function to test the result of my work, but I get some 'undefined symbol' errores while linking the test application with the instrument. The instrument header file is included in program source file.
Situation is as follows:
I can run the test application if I include the source file for the instrument directly in the project (without loading the instrument)
I created a static library and can have the test program up and running if directly including the library in the project (again without the .fp file)
I get linker errors when trying to use the instrument I created based on the same code, both when including the instrument at source code level and when including at library level. Adding the .fp to the project makes no difference
Linker errors are all related to WinSDK and third-party dll functions.
Question is: where and how I have to declare the symbols apart including the appropriate .h files in the instrument header file?
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

Being waited on to log on... how flattering
I wish I had a simple and obvious solution, but I don't.
The problem in this case is that, whereas DLLs (via their import libraries) carry no additional build-time dependencies to their clients, that is not the case with object files and static libraries: any project that uses those .obj and .lib files must satisfy all of their dependencies when that project builds.
There is a mechanism, with .fp files, to advertise such dependencies to the clients of the .fp, and that is the auto-load list (Edit>>FP Auto-Load List, in the function tree editor). The caveat, however, is that these indirect dependencies must have a companion .fp that you can add to this list. And in your case, you don't have one. So the only solution I can think of is for you to create a very thin wrapper module where you would wrap all of the SDK functions that you need, then create a basic .fp for this wrapper -- you can do this semi-automatically, from the header file (Options>>Generate Function Tree) -- and then add this .fp to the auto-load list of your primary .fp. And then you'll probably have to create a second .fp wrapper for your other dependency (a non-SDK third-party DLL?).
Once you have declared the dependency chain for this .fp, you should then be able to use it on any test application and CVI should know to link in these additional static libraries whenever it builds the test application.
If you choose to go this route, you'll probably have to deal with a bunch of non-standard data types in the parameters of the SDK functions. I don't remember if these are automatically added to the .fp when you create it from the header file. If not, all you need to do is add them to the .fp later (Options>>Data Types, from the function panel editor). Don't worry about providing the definitions for these data types. They're not necessary. You just need to make sure that their names are in the list.
Luis
Message Edited by LuisG on 05-19-2010 10:43 AM

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?

How to read instrument driver dll files

Hello,
How to read .dll files of an instrument driver? What is the programming methodology followed in dll files? I will be grtaeful to you if someone can point me a way to do this.
Thanks,
Ananda H S

If you can get your hands on the driver dll sdk or source code, you can use Tools --> Import --> Shared Library (.dll)... and use the wizard to easily generate the code you need to implement it.
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

"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

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

Upconvert Third Party Instrument Driver

Attached is a 3rd party instrument driver contained within a .llb that has multiple VIs used to control a GPIB device. I have attached the .llb below.
Source Version: 5.0.1
Target Version: 2011 SP1 (or 8.2 and above would be fine)
Thanks for your time.
Solved!
Go to Solution.
Attachments:
wcl488v1.llb ‏863 KB

attached as 8.2
Attachments:
wcl488v1.llb ‏432 KB

Instrument driver's API

Hi guys!
I need help with one question. I have a number of devices with the same control meaning but with slightly different functionality (list of settings) and different APIs (it's a number of detectors of radiation). I need them all in my programm, and I need the ability to extend the number of devices and it's functionalities in future. The question is, do I have to create instrument driver for each one and then use it in case mode or can I try to create one extendable instrument driver with the common high-level API based on the other APIs?
Thanks!

Hello Err,
I agree with Paul that if would be good for you to look at the concepts that are implemented in IVI drivers. (ni.com/ivi) Your instruments most likely don't fall under one of the current IVI classes, but there is a tool in CVI that helps you create a custom class driver. If your instruments have an overlapping command set, you could just create one driver, with consessions made for the different models. If your instruments have different command sets, you should probably create separate drivers. My recommendation is that you start with the Generic LabVIEW Plug and Play Driver Template in LabVIEW and add your well thought-out radiation detection API to it. You can then use that driver as a template and run the Driver Wizard for each instrument and then customize the generated driver.
I highly recommend investing some time in your API design, so that you won't have to change it later in the development cycle. It also really helps to have someone else to talk to about the API to see what makes sense to someone less familiar with the instruments.
If you would like, please let us know the following:
Instrument models and quantity of each
Average number of commands for each instrument
Communication buses (GPIB, Serial, Ethernet, etc)
Will you be using VISA?
Do the instruments already have dlls that are used to programmatically control them?
Timeframe of project
Cheers,
NathanT

How do I add a Printer Driver to the Driver List??

Im trying to add my printer to a WGPS606 Netgear Print server. So Im adding a Printer to print via LPD IP printing, but My Canon iP4200 is not listed as one of the canon printers in the "Print Using" driver list.
I have been to the Canon site and can only seem to download a Pkg driver file (which I have run).
If I use the "other" setting in the "print using" driver list surely I can add the iP4200 if I had the right driver file.....? How do I get hold of the right file to add it to the list or am I missing the point of adding a print driver to the pre-installed list????

I have read my list through and through but no sign
of Designjet 900. (now slightly cross-eyed). If you
get a chance to look through the list on your mac
when you're reunited, I would be grateful!
The latest version of the Gutenprint/Gimp-Print drivers does not have a generic DeskJet Series 900 PPD. It lists individual printers in the 900 range. The Gimp-Print v4.2.7 driver package did have a generic DeskJet Series 900 PPD. Somewhere in between, there was a change over to model specific PPDs.
Crispian, your original request for a driver for an HP printer was for the HP Deskjet 9800. Gutenprint/Gimp-Print does not support that printer. The hpijs drivers do support that printer. If that is not the printer you have, please specify again which printer you have. There has been mention of the DeskJet 9800, DeskJet 900, and DesignJet 900 in this thread.
Matt
Mac Mini G4; B&W G3/300

I get an error when I use the instrument driver KE230x.

Good day. I am using the ke230x instrument driver connected to a Keithley 2306-PJ. I am using the USB to GPIB to communicate with the instrument
I load the Getting Started VI and when I hit run I get the following error message
====================================================================
Error - 1074003951 occured at ke230x Initialize With Options.vi
Possible reason(s):
Driver Status: (Hex 0xBFFC0011) Primary Error: (Hex 0xBFFC0011) Identification query failed.
Elaboration: Failed to Recognize Model
=====================================================================
When I place the "id query" switch into the false position, everything appears to be working. I have left the "reset device" in the true position and I see the instrument resetting.
I do not understand what is happening?
Thank you for your time and help.

Good day. Dennis - thank you for your response. My next question is if I leave the ID Query off (false) position, I still cannot get the program to work.
My guess is that I am doing something wrong (I am relatively new to LabView). I use the Getting Started vi and everything looks to be working okay. I then start the Application Example (I run the Getting Started vi before I run the Application Example to make sure that the Application Example has the correct instrument handle). When I run the Application Example I get the following error message
Error -1074130544 occurred at ke230x Configure Current Limit.vi
Possible reason(s):
Driver Status: (Hex 0xBFFA1190) The session handle is not valid.
Any help or advice would be greatly appreciated.
Michael

Instrument Driver Tool has blank Source driver list.

Similar Messages

Maybe you are looking for