Instrument driver

Someone here has just purchased a Keithley 2400 source/measure unit for
doing I-V characterisations on some diodes they make. The group wants to
drive it from Labview to acquire, preferably in log space, a series of I-V
measurements. On the face of it this could be almost trivial if the bare
minimum of coding were done, however nobody in that group has Labview
programming experience. I do, but am reluctant to get involved since I have
too much other stuff backlogged to be volunteering myself.
I've had a nosey around ni.com and found something for an old Keithley
instrument that does the same job- with luck the newer instrument will be
essentially an upgrade and will understand the same instructions. However,
in case this doesn't work, d
oes anyone have a VI they're willing to share
that at least can be used to set a voltage and return a current? I'm willing
to do some modification if necessary to get the data out and onto disk.

I just went to www.keithley.com and from there Technical Support>Instruments>2400
and got KEI2400.llb that loads into LabVIEW 5 and 6. It doesn't use VISA
but that's an easy conversion.
"Craig Graham" wrote:
>Someone else also mailed me suggesting checking out Keithley- I initially>didn't
because I assumed anything they had would have been shipped with the>instrument,
and the guys playing with it told me no Labview stuff was>supplied (though
there were Labview examples with my Keithley 2700 unit).>>I've looked at
the Keithley website and discovered, incredibly, that>although they have
a 2400 library, it is for Labview3 and of course can't be>loaded in the current
5.x/6.x installations.>>If they can't get anywhere wi
th the "older" stuff
I pulled from ni.com then>I'll just have to convert this v3 file up to a
current version, which is>doable since I still have the v3 and v4 installation
disks, but it's not>something I'll work on until they've tried the older
drivers and see if they>work.>>Dennis Knutson
wrote in message>news:[email protected]..>>>> I used this instrument
in a project a few years ago. I got a LabVIEW>driver>> from Keithley. Check
their web site and your local sales rep. If you still>> can't find it, I'll
try and see if I still have a copy.>>>

Similar Messages

I am trying to continuously switch images on the VI, but it freezes when I try to access an oscilloscope through its instrument driver.

I am drawing 2 different colored rectangles contiuously on the screen using a while loop. I try to get information from an oscilloscope while this is switching, but the loop stops while the instrument driver aquires the measurement. The oscilliscope value depends on the switching of the rectangles, so I need them to occur simultaneously.

First you should have the two operations in different loops so one doe snot stop and wait for the other.
This should get you closer to what you are asking if you are not doing this already.
Next, look at the code you are using to get at the scope. If it opens/reads/closes, you can sped things up by opening once, repeatedly reading and only close at the end.
If you have covered all of the above, then provide more info (i.e. post code) So we can be of further assistance.
FWI There was a version of VISA that code "Lock-up the CPU" when doing reads. Are using VISA and do you have the latest version?
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

I would like to know which instrument driver works for the Tektronix TDS 544A

I am trying to use TDS544A with CVI and downloaded the driver for TDS 540 and it didnt seam to work... should it? If not, which one will???

Hello,
Well, it appears that you are correct in that it must be somewhat different since you are getting the errors you described. Since that is the case and we don't have an instrument driver for that particular instrument, I would recommend one of two things. Try to modify the existing instrument driver to send the commands that your instrument expects, or make regular Visa calls to communicate with your instrument.
Also, I would encourage you to submit a request for the specific instrument driver you are interested in. I cannot guarantee when or if it will be created, but they will evaluate what can be done and get back to you. You can submit that request here:
http://zone.ni.com/idnet97.nsf/instrumentdriverrequest/
Good luck
with your Application!
Regards,
Steven B.
Applications Engineering
National Instruments

"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

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

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

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.

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 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 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 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

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.

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

Hp 4145B instrument driver problem

I am having a problem with the graphics plot.vi program of the hp 4145B instrument driver library I downloaded from NI network. This Vi calls a sub vi which is data output.vi and this particular subvi is unable to send its data to the computer. Only in case of short integration time (i.e. the instrument takes measurement very fast and it is not worth always), the dataoutput.vi is able to write if the time out (in ms) is large enough. However I would like to get the data out for a larger integration time, so that the data is good enough. And although this subvi works, this is unable to send its data array to the graphics plot.vi and I get an error message from graphics plot.vi saying error with receive message problem. Could anypne help
me with this?

It sounds like you just need to adjust your timeout. Open the initialize VI and increase the timeout in the block diagram, the original values is set to 10000ms.

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

Can I use instrument driver in a software application

Hi,
I'd like to develop a generic driver to control any instrument from a software application . Can I use the LabWindows/CVI wizard to succeed ?
Once I have created my dll, does it mean something to call IVI function from a sofware application ? (for example : in a Visual C++ application, can I call Prefix_init and after Prefix_WriteInstrData if I have connected an Instrument with an input ?).
Thanks

Hi,
Using the IVI class driver in your application you can at least use the same program to communicate with instruments belonging to the same class.
To acomplish this you need the specific driver for the instrument. The class driver provides a standard API you can use in your application. The class driver in turn calls the specific instrument driver that you have configured.
If you call WriteInstrData you still need to determine the command string you need to send to the instrument. The IVI driver wraps the instrument I/O, using the attribute model or high level functions.
DiegoF.
National Instruments.

Instrument driver

Similar Messages

Maybe you are looking for