GPIB Instrument Driver Installation

Hi,
I'm currently making software that communicates with several different type of GPIB instruments such as power meters, spectrum analyzers, etc.  With these instruments, I make different types of measurements.  Obviously, to run these intruments I download the drivers or make my own.  Now here is my question:  Is there a way to implement a driver installation interface in my software so it could allow any user to easily install drivers for any types of instruments?  What is also tricky is, these drivers have to be used in my code afterwards to get measurement data.  Hope my intentions are clear enough!
Thanks!!

I don't understand the relationship between VI Analyzer and IVI. The VI Analyzer is used for checking your code for a variety of style recomendations. IVI is a standard for instrument driver interchangability.
For the instruments that fall into one of the 8 defined IVI classes, you should use them and IVI class drivers in your LabVIEW program. Right now, those are the only classes and your network analyzer isn't included. You can go to http://www.ivifoundation.org/ and check the status of other classes but I think the only additions on the horizon are AC power supplies and counter/timers. Since IVI has been around for 8 years and that's an average of 1 instrument a year, we'll probably have to wait another 2 years before these classes are released and if you want a network analyser class, you'll probably have to wait several more years for that to get approved.
Until this happens, you will probably need to provide your own drivers (or wrappers around existing drivers) for instruments that don't fall into existing classes. They may lack some of the true IVI functions such as state caching and simulation but the interchangable part would not be that hard to do if you can define a set of common functions that such an instrument has to provide.

Similar Messages

  • GPIB instrument driver identification

    What is the right labview GPIB instrument driver for ESP300 motion controller produced by Newport Inc.?
    The drivers for motion controllers of Newport posted in ni.com website looks all different with the models provided by newport.

    Hamfery,
    The drivers provided on our website don't apply to your Newport motion controler.Newport is providing motion utilities for this model. It's been written in LabVIEW but you cannot edit it since it is an executable.
    Cyril Bouton
    Applications Engineering
    National Instruments
    Cyril Bouton
    Active LabVIEW Developper

  • GPIB Instrument driver for Keithley 2015 multimeter.

    Hi,
    Does anyone have instrument driver for Keithley 2015 multimeter or does
    anyone know where can I find it? I didn't find it from NI web pages.
    Thanks,
    -Harri

    Did you check Keithley's site Harri? I think I got one from there. They were anxious to know, Keithley that is, which drivers would be worth creating for CVI. Maybe you already have this worked out but otherwise talk to your friendly neighborhood Keithley rep. Hope it helps.
    Grant
    Grant M. Johnson
    Project Engineer
    LECO Corporation

  • I need an GPIB Instrument driver for an HP5386A Freq. Counter.

    LabVIEW will be used to automate some Frequency measurements.

    I would suggest trying to use the HP5384A driver. These two devices are very similar and its possible that the instrument driver is interchangable. Let us know if this works out for you.
    http://zone.ni.com/idnet97.nsf/9b2b33e1993d877786256436006ec498/3e3a4ce78bf42f05862568f50000ce56?OpenDocument
    I hope this helps out.
    -Josh

  • How to install an older instrument driver (GPIB) LV2009 eval, 23 days remaining!

    Hi..
    Still having fun (I think) here trying to "evaluate" LV2009.
    I'm sort of happy with the higher level stuff, front pannels, block diagrams, flow control with error signaling etc, so now time to move on and try to talk with the real world.   The Front Panel development UI is a bit of a dog, but I'll live with that.
    Anyway...
    I have a Marconi 6960 RF power meter (and similar kit) I can use for this "evaluation" and have found a so called driver in the NI developer zone some(i forget)where.   It's a zipfile (no problem) with 4 files in.  .c .h .fp and .doc    Sadly, the .doc though documents the functions of the driver, gives me no clue as to how to install it in LV2009.  It also talks about LabWINDOWS V2.0, and dates from 1997.
    (As an asside, most of what I will have to do, will relate to "older" or "Legacy" GPIB or RS232 connected instrumentation, and maybe one or two USB toys.   There is no choice, LV is expensive enough if we go this route.  But it's not even peanuts compared to the value of some of the instrumentation it will need to work with.)
    Looking arround this board, I'm not realy any the wiser as to what to do with it.  (This downloaded "driver" code.)  It obviously needs compiling, but with what, and then integrating in LV2009, but how?
    I found a link in one sort of related message, something about a driver import wizard, but the link is blocked by some spotty IT type this end, so that is of no help.
    The inbuilt help from within LV2009 is sufficiently vague, or over complicated as to be of little use too.
    What I need, is a simple, put that there, do this, do that type of procedure.
    Again, stumped by simple details, and this is the area I will probably be spending most of my LV life in, from what's being muttered about "upstairs" in the big boss's office earlier.
    Any help appreciated.
    Regards.
    DJB.
    Just been "diverted" onto a hardware repair job, so no hurry, for now.
    OK... Who let the smoke out?

    Hi Dennis.
    Yes, I found that page (and many others) but the info there is sufficiently vague, or so OTT for someone who does not know their way arround the darker recesses of LV (yet) to figure out.   It tells me a lot, but it does not tell me in sufficient detail *exactly* how to install a driver that someone else has created, or for that matter, how to find out what "Drivers" are installed already.
    As you or someone pointed out, that code was also written way back for another system "LabWINDOWS/CVI" (whatever that was) but it shows up when you search for "Drivers for LabVIEW".  It is also listed as supported by LV7.0 and LV8.0.   Those IDN pages also do not yet (that I can see) make any mention of LV2009.  Is it just me that sees this as somewhat inconsitant and confusing for a new user, when NI are pushing LV2009 at this time?
    Someone is now going to tell me that reusing existing older drivers *is* straightforward, but will be vague as to exactly how.
    The only "exposure" to LV we've had here in the past/present, is as users of pre-compiled tools and utilities from some of our principles.  And it has to be said, all of them are without exception, extreemly buggy, so much so, I personally wouldnt say they were fit for even internal Beta testing, as they don't handle "unexpected events" at all well.  And some of these utilities could if they screw up, seriously damage hardware in some instances.
    We've also found many many times, that anything using "VISA" IO drivers (that word again) is almost garanteed to be troublesome to get or keep working, especialy as one lab/workshop PC might have tools and programs from several vendors on it, and they must all work indipendantly when needed (not at the same time!) without interference from other vendors code or preferences.  For some reason, VISA seems to make that all but imposible.
    We have a situation at the moment, where we suspect a "Clash of the VISA's" as we can't reproduce what a customer has reported in the way of bad behaviour of a semi automated test system, but we see other errors relating to the serial IO used, throwing up internal LV runtime error messages, and blank spaces where the *Real meaningfull* comments should be.   It's all pre-compiled code, so we have no way of supporting or debugging it, but try tell the end user that, who's test facility is now at a standstill, untill I can call the East coast USA later today (from the UK) not that I expect a constructive reply till sometime tomorrow, at best.  By then, there'll be Director to Director phone call's going on!
    I've also just been informed, that the workshop PC in question, will not now run something else we need, since we earlier installed the program the user is using (made by the instrument vendor) and all it's baggage, so yet another "Fixit" re-install of VISA (this time from Agilent) is needed to complete another job, and that in turn will break something else.  It's a nightmare!
    Sorry, but in my book, VISA is a no go for "Serious" multi vendor use.  It's too fragile.   In our industry (EMC and product safety testing) "Legacy" GPIB rules, almost without oposition.  USB and LAN connections may be alternatives where the instrument supports them. With some true RS232 point to point low speed dedicated links where needed (often via passively powered fibre optic convertors too) for some measuring instruments.
    But, at this time, all I want to do, is talk/control a simple existing GPIB instrument (a MI 6960, that I know all too well) and I thought (wrongly as it turns out) that I had found a needed "Driver".   If I have to create one from new, I will, one way or another.   But it makes a mockery of the so often quoted aspect of LabVIEW, being quick to construct and deploy a test/trial/control system etc, with an existing vast library of tried and tested instrument/device drivers.  From what I see so far, it's anything but, as it's in the same ball park as all the other RAD IDE's etc (Even Delphi!) in that respect.  The devil is in the detail, and if that detail as often does not exist, it's a task and a half to create it, and get it right.
    Sorry if I ruffle any feathers, but I've been arround RF test & instrumentation systems at the hardware and software level for more years (decades) than I care to admit.  Each and every time someone comes up with a "better" way to do something (usualy involving even more computing power!)  It's anything but quick and easy, and the end result is in all honesty, not realy different to how it was done, before "enforced newness" was applied.
    Regards to All, I've still got the day job to do, so sadly I can't sit in front of this and mess with software all day.  Much as I need to, and often would preffer to!
    DJB.
    OK... Who let the smoke out?

  • How should i modify the hp54600a instrument driver for GPIB so i can use it for RS232 interface ?

    I try to modify the hp54600a instrument driver for GPIB, so i can use it with RS232. But somehow it didnt work. When i try to run the initilize it, the prgoram show VISA read error (time is up before the process is finish). How should I modify the VI so I can use it with RS232 interface ?

    First, check the instrument's user manual to see if the GPIB and serial command sets are the same. Also check to see what EOS(End of String) characters the instrument requires. Then, do a loopback test to test communication in LabVIEW.
    Search Results: Serial Loopback Test
    Ray K
    NI Applications EngineerMessage Edited by Molly K on 02-18-2005 10:57 PM

  • Agilent 6632A GPIB dc power supply, 0-20 Vdc Instrument Driver

    Hi, does anyone here has a Agilent 6632A GPIB dc power supply, 0-20 Vdc Instrument Driver???
    Thank you.

    It's available on NI Home > NI Developer Zone > Instrument Driver Network and search for 6632A.
    Or, see attached.Message Edited by TotalAJ on 06-22-2005 07:33 AM
    Attachments:
    hp6xxxa.zip ‏47 KB

  • AP2222 (System Two) or AP2722. Instrument Driver(GPIB) vs. ActiveX(APIB) which will be more effective?

    Hello Forum,
         This is my first time posting here.  I am on a project where i will be trying to control a AP device.  I have the option of using the AP2722 or an AP2222.  From talking to tech support. 
    AP2222 needs to use ActiveX control LabView to APWIN (APIB)
    while
    AP2722 has an instrument driver and uses GPIB.
    So what kind of things would you guys suggest?  Any opinion? 
    Which will have a gentler or less-steep learning curve?
    Which option is more robust and offers more control?
    Pros and Cons?
    thank you.
    .Danny

    If it was me I would opt for the GPIB option. It is widely used standard available on many different types of instruments.
    I would buy the GPIB controller from NI because of the great support and troubleshooting software that is included. On the plus side you can use this controller to connect to other instruments as well.
    The APIB looks like it is proprietary and you would have to buy the controller from them.
    I assume you want to write your own application in LabVIEW and not use their APWIN? software.
    When they say they have a GPIB driver what was it written in? LabVIEW or something else?
    Using LabVIEW 2010SP1 and TestStand 4.5

  • Measurement Studio Evaluation Software - Instrument Driver Factory

    Greetings,
    I have a copy of the Measurement Studio Evaluaiton Software CD. I've
    installed the Labwindows/CVI Demo and Component Works Demo. Wanted to
    check out the Instrument Driver Factory (located in VB\Instrument
    Driver Factory). When I launch IDF.exe I get an error which states
    that I have to install Labwindows/CVI. I tried the installation a
    couple of times with the same results.
    Has anyone else had this problem?
    Thanks,
    Rick

    Mika,
    I have tried the installation on two machines.
    The first system has Windows XP Pro along with Labview 6.0.2 / MAX /
    PCMCIA-GPIB / Visual Basic 6.0 / Visual Basic.Net
    The second system has Windows 2000 and Visual Basic 6.0
    The Instrument Driver Factory error reads:
    The ComponentWorks Instrument Driver Factory cannot locate
    Labwindows/CVI. In order to use the factory, please install
    Labwindows/CVI version 5.0 or greater.
    The Measurement Studio Evaluation Sofware CD installed Labwindows/CVI
    5.5 The CD picks a path of "C:\MeasurementStudioDemo\CVI\"
    The Instrument Driver Factory is installed in
    "C:\MeasurementStudioDemo\VB\Instrument Driver Factory\"
    The Instrument Driver Factory is installed when the Component Works
    for Visual basic is
    installed.
    The part number on the installation CD is 350654B-00
    Thanks for your help.
    Rick
    On Mon, 25 Nov 2002 14:00:06 -0600 (CST), mfukuchi wrote:
    >Hi!
    >I would like to reproduce the problem on a test machine. Could you
    >please tell me what OS you are using, and if you have any other NI
    >softwares installed on your machine. Also, am I correct that you have
    >Measurement Studio Evaluaiton Software for version 6?
    >
    >Mika Fukuchi
    >Application Engineer
    >National Instruments

  • MAX communicates fine with GPIB Instrument, LV Standalone Exe Front Panel Control Does Not See It.

    I have succesfully created a LV standalone EXE which communicated with external GPIB instruments.  I used LV 7.1 for this.  I upgraded DAQMx to 8.0 on the development machine and also the target which runs the Exe.  The EXe runs fine on the development machine but when run on the target laptop, the front panel control fails to see the GPIB instrument.  On the target, in MAX I  successfully setup communication with the GPIB instrument.  Is there some incompatibilty with DAQMx 8.0 and LV7.1?   An additional piece of info here: when upgrading to DAQMx 8.0, I selected the installation support for LV 7, 7.1 and also 8.  Could this be where the problem lies? 
    Thanks
    Peter

    The GPIB code is actually an IVI driver made for a Rhode and Schwarz TRMS meter.  Its the standard VISA Read/Write, nothing out of the ordinary.  I'm using a USB-GPIB-HS adapter to communicate with it.  Like I mentioned, the VISA instrument control drop down list on the front panel of the Exe does not list any GPIB instruments,  all that is listed is ASRL...1, ASRL...4, and ASRL...10.  In the EXE that used to work, there were no ASRL... references listed.  What was listed was the GPIB0...INSTR...20, COM1, and the parallel port.  So something weird is going on now, somehow effected with the load of DAQMx 8.0.
    Pete.

  • How do I create Labview VISA ports for *individual* GPIB instruments using Prologix USB GPIB controller?

    Hello,
    I'm trying to use a Prologix USB GPIB controller to control GPIB
    instruments, and I would like to have a virtual serial (VISA) port for
    *each instrument*, as is the case with a normal GPIB controller with a
    standard NI driver. However this is not what the Prologix driver
    provides -- it provides a single VISA virtual serial port for the
    entire controller. To address the instrument with GPIB address 11,
    you first send "++addr 11" to the serial port, and then you're talking
    to instrument 11. However, this means I have to change all old
    Labview programs.
    Is it possible to create a "wrapper" function of some kind that will
    define a virtual serial (VISA) port for each *instrument* on the
    controller? For example, to talk to GPIB instrument 11, call it
    ASRL3::11::INSTR, each time it is written to it would have to write to
    the virtual serial port of the controller, say ASRL3::INSTR, first "+
    +addr 11" and then the command that is sent to it.
    A clearer explanation of the difference (i.e. incompatibility), and of
    my objective:
    1) A normal GPIB controller with NI driver: I go to the NI
    Measurement & Instrumentation Panel, under GPIB, and Scan for
    Instruments; all the live instruments show up; subsequently when I
    want to use Labview programs that use VISA ports, the VISA drop boxes
    allow me to choose a different port for each instrument, e.g.
    "GPIB0::11::INSTR", "GPIB0::12::INSTR" would be instruments at
    addresses GPIB 11 and GPIB 12.
    2) The Prologix GPIB controller that plugs into a USB port: In
    Labview you get a *single* VISA virtual serial port, ASRL3::INSTR, for
    the entire GPIB0 controller. Therefore to address GPIB instrument 11,
    you write "++addr 11" to the virtual serial port ASRL3::INSTR, and
    then you are communicating with device 11, so you can write and read
    ASRL3::INSTR to talk to that device. Then to talk to device GPIB 12,
    you write "++addr 12" to the same VISA port, and then you are talking
    to that device. The problem is that this requires recoding all
    Labview code, whereas I would like to be able to use the same program
    either with a normal or with a Prologix GPIB controller. Therefore, I
    would like to create code that scans the controller for all GPIB
    attached devices and creates VISA ports for all. Such ports, when
    written to, would have to first write "++addr DEVICENUM" to
    ASRL3::INSTR (i.e. the port of the GPIB-USB controller) where
    DEVICENUM is the GPIB address of the instrument corresponding to that
    port, and then would have to do a write or read or whatever function
    is being done on that instrument VISA port.
    I haven't figured out if it is possible to do this easily. Help and
    pointers on where to look for hints would be much appreciated. Many
    thanks!
    Milos

    My first impression is that if you don't want to make any changes at all to existing programs is that the wrapper you need is one around VISA. You would need to intercept all of the calls into the NI VISA driver. If you create your own visa32.dll and in there, change the addressing and then call the real VISA driver, you might (repeat, might) get something to work. If this would even work, you still might find that you have to make significant changes anyway. The serial connection is going to be considerably slower, and interface specific functions such as service request handling, bus triggering of multiple instruments, etc., would be difficult to impossible. This would be a lot of work, imho, to just save a couple of hundred dollars over a real GPIB controller. I've seen this Prologix device before and have even used NI's RS-232->GPIB controller. The Prologix intended use to me seems to me more for a hobbyist or very casual user. Of course, I'm used to having multiple GPIB instruments worth 10s/100s of thousands of dollars and the cost of an fully compliant GPIB controller is just lost in the noise.

  • 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

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

Maybe you are looking for