Instrument Driver Template VI's

Hello,
I am doing a study about labview and need to control instruments via labview
in an effort to create an "database" of the instruments at the lab.
In a later stage i shall use these VI's so that i can control a complete
test for emc.
Am i correct in thinking that i should make my own representation of (in
this case a signalgenerator R&S SMY) with the help of an instrument driver
template?
In this case i have downloaded a file that contains these VI's from
http://www.ni.com/devzone/idnet/development.htm#la​bview and i can open them
with labview buth how do i go about in making these VI apear as an icon so
that i can use the "commands" to create the VI of the signal generator.
Do i have to place the files that i downloaded in a specifi
c dir to see them
in labview ?
THX

You would use the templates to help create a driver for any instrument that doesn't already have a driver written for it. Go to Developing a LabVIEW Instrument Driver for a starting point in how to create your own driver. Once you've created a driver, you can add the functions to the Instrument Driver subpalette. The LabVIEW help contains directions on how to create and edit new subpalettes. The driver files that you create can be stored anyplace but typically they go in the instr.lib folder. You should also be aware that the template VIs only cover a small fraction of the functions necessary for a driver (reset, self-test, err
ror query, and a couple others). Depending on the complexity of the instrument, plan on spending up to month for each driver you need to write.

Similar Messages

  • Instrument driver template

    There exists a template for developing own VISA instrument drivers. It
    includes directories with a standard VIs for opening closing, initializing
    etc. Also, there are predefined menus for Configure/Data/Action/Utilities.
    Where can I download this template libraries ? I forgot where I once got it
    from ;-)
    Oliver Friedrich

    go here:
    http://www.ni.com/devzone/idnet/development.htm
    Michael Aivaliotis
    VI Shots LLC

  • 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

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

  • 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 to make an instrument driver appear in toolbox

    Hi,
    i created an instrument driver using the create new instrument driver project option.  I have all the VIs in place in the project and have saved the whole thing, library and all into the instr.lib folder and have restarted labview and the VIs are still not showing up under instrument i/o -> instrument drivers option.  could someone please go over the process or just tell me what i might be missing to have these drivers show up in the toolbox!
    Thanks for help,
    brent schenk
    Solved!
    Go to Solution.

    From the Getting Started Menu >> Browse
    From the Create New window >> project >> project from wizard >> Instrument driver project
    select New driver from template
    select the type of instrument you have
    Click next
    **Make sure the project location is correct. I think this is where you are going wrong.**
    It should say something like, C://Program Files/National Instruments/LabVIEW 8.5/instr.llb/yourproject/yourproject.lvproj
    If you have this directory correct, it should show up under the instrument library
    National Instruments
    Applications Engineer

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

Maybe you are looking for