Instrument driver development wizard strange behavior

Hi,
I was using the driver development wizard and I started getting strange results.  It started creating VI's where the text builder portion ws seperate from the VISA communication portion of the code.  I had to delete indicators and controls and wire the seperate sections.  Also, the VI's dropped the VISA commands and replaced them with nonsense commands.  Very strange.  I closed and re-opened LabVIEW, but no change.
Has anyone had this happen to them?
Mark Ramsdale

Hi Mark, 
That does seem like some strange behavior. Could you fill me in on some more information? 
I'd like to see if I can recreate the issue on my end. 
What OS are you running?
Version of LabVIEW?
Version of Measurement & Automation Explorer? 
DAQmx Driver?
VISA Driver?
What were you trying to build a driver for? At what point did it start having issues? 
Any other useful information you can think of? 
Applications Engineer
National Instruments
CLD Certified

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. 

  • Does LabWindows/CVI: IVI Instrument Driver Development Course contain subject like Communicating with Instruments(SCPI commands)

    HI,  I am having query regarding; Does LabWindows/CVI: IVI Instrument Driver Development Course contain subject like Communicating with Instruments(SCPI commands)
    LabVIEW: LabVIEW Instrument Control Course Day 1 coves subject like Communicating with Instruments This lesson describes how you can use LabVIEW tocommunicate with instruments. You will learn how touse NI-VISA, NI Spy, SCPI commands, and theInstrument I/O Assistant to perform instrument I/O. My question is to you,Does LabWindows/CVI: IVI Instrument Driver Development Course covers similar kind of training like Communication with Instruments? I am more interested in learning How to use SCPI commands to perform instrument I/O. Will you please guide me? So I can choose correct training course. Thanks & Regards,Jay +91 90110 62790EXFO Electro Optical Engineering India Pvt. Ltd.701, 7th floor The Ceribrum IT Park,Kalyani nagar. Wadgaown Sheri India, Maharashtra, Pune 411014  

    stick to the original thread.

  • Advanced LabVIEW Instrument Driver Development Techniques

    Hi, reading AN006-Developing a LabVIEW™
    Instrument Driver and in page 2 I find:
    "refer to the Advanced LabVIEW Instrument Driver Development Techniques application note."
    I can not find this AN. Is the name correct ?
    Bye
    Luca

    Hi Luca,
    the link you're looking for should be this:
    http://zone.ni.com/devzone/conceptd.nsf/2d17d611efb58b22862567a9006ffe76/e7a1635c2166e0728625680a005b0b9a?OpenDocument
    Happy new year,
    Alberto

  • Labview Instrument driver development-career path

    Hi,
     How is the career path for a labview Instrument Driver Developer ( Third party instruments like Scope,DMM).

    First off LINK, just click on your name the link is duplicated in your recient posts on your profile page.  (Lots of interesting features in the forums)
    As far as career potential for a LabVIEW developer:
     All the skill in the world with LabVIEW won't do much unless you can apply it effectively.  It is a good skill set to have but, LabVIEW itself is a means to accomplish something else.  In my case it facillitates developing automated tests. From your post it would facillitate development of instrument drivers likely, secondary to the goal of facillitating the sales of those instruments.  So, you need more than LabVIEW, you should develop skill and knowledge about Instrument driver standards, instumentation, and communications protocols. While you are doing that you also need to be able to demonstrate your LabVIEW proficeincy.  Certification can help with that.
    Couple some serious understanding of test and measurement techniques with NI Certification and.... well lets just say you can pay the bills with it.  I Know. 
    Jeff

  • VISA Driver Development Wizard

    I found a reference to this great document called
    Using the VISA Driver Development Wizard and NI-VISA to
    Register-Level Program a PXI/PCI Device under Windows.
    As I described in another post, I am having performance problems
    using AccessHW to talk to a legacy ISA board under XP compared to
    Win2k where performance was decent.
    To rule out AccessHW as the problem and confirm that it is an
    XP/hardware issue, I'd like to try another method of
    reading memory at address 0xE0000-0xEFFFF.
    Since the legacy ISA bus on my motherboard is actually
    bridged from the PCI bus, is there anyway to hack with the
    VISA Driver Development Wizard to do memory reads
    on the ISA bus?
    Perhaps making a fictious PCI card with a VISA driver?
    any thoughts?
    mlewis

    Hi Graham,
    Which version of the NI VISA drivers are currently installed on your system?
    Thanks,
    Applications Engineer

  • Instrumentation Driver Developer Guide Documentation Error p9-44 Ivi_UnlockSession

    The source code as listed causes subsequent calls to attribute methods to lock up the development session. Which solution is preferable? Remove the Ivi_UnlockSession statement or add a Ivi_LockSession statement at the top of the method?

    Hello Larry,
    This looks like a mistake in the DDG Manual. The recommendation would be to add Ivi_LockSession at the top as in the following code (from the latest fl45 source):
    ViStatus _VI_FUNC fl45_ConfigureHold (ViSession vi, ViBoolean holdEnable,
    ViInt32 holdThreshold)
    ViStatus error = VI_SUCCESS;
    checkErr( Ivi_LockSession (vi, VI_NULL));
    viCheckParm( Ivi_SetAttributeViBoolean (vi, VI_NULL, FL45_ATTR_HOLD_ENABLE,
    0, holdEnable), 2, "Hold Enable");
    if (holdEnable)
    viCheckParm( Ivi_SetAttributeViInt32 (vi, VI_NULL, FL45_ATTR_HOLD_THRESHOLD,
    0, holdThreshold), 3, "Hold Threshold");
    checkErr( fl45_CheckStatus (vi));
    Error:
    Ivi_Un
    lockSession (vi, VI_NULL);
    return error;
    If you are interested in driver development, I would recommend downloading some drivers from our website (http://www.ni.com/idnet) and walking through them -- we provide the source to many complete drivers.
    Sincerely,
    Jeremiah Cox
    Applications Engineer
    National Instruments
    http://www.ni.com/ask

  • 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

  • Driver development for custom PCI card

    Hi friends,
    I've a PCI card developed in-house. How to prepare a driver for the same in LabVIEW? Can I develop drivers in VISA? I don't have a manufacture id. Is there any other method to develop a driver for PCI card? Once developed, can I use them for other platforms like VC++? My OS is Windows 9X/NT & 2000. I need a driver to use for all these. Lot of querries! hope I made it clear.

    THE ANSWER IS THAT YES YOU CAN DO THIS IN NI-VISA!
    Some have said that you need a kernel driver. This is partially true in that a PXI or PCI card (they are the same as viewed by the OS) must have a kernel driver. NI-VISA provides one for you.
    You said that you do not have a manufacturer ID. This is a requirement of all PCI cards and no kind of driver will work until the card has one. Once you have this ID, run the VISA PXI Driver Development Wizard and it will generate an INF for you for all supported NI-VISA environments that support PXI/PCI. Read the instructions in the appropriate INF file for how to install it into the system so that the OS will attach NI-VISA to your device. It's really simple. NI-VISA supports PXI/PCI on Windows 95, 98, ME, NT
    4, 2000, XP, and LabVIEW RT.
    Some have said that MAX will just show you all PXI/PCI devices in your system. Your device will not show up until NI-VISA can see it, and that won't happen until you generate an INF as described above.
    Since the INF file associates NI-VISA itself to your card, the ADE you use does not matter. NI-VISA supports PXI/PCI in LabVIEW, CVI, MSVC, Visual Basic, or any other ADE that normally works with VISA.
    NI-VISA works well even with more advanced devices because we support all types of register accesses (config, I/O, memory) as well as interrupt handling. Just look at the visa.h that NI ships in the VXIpnp directory. If you are using C/C++, make sure you define NIVISA_PXI before including visa.h. If you use LabVIEW, you need to use the address space numbers as defined in visa.h.
    Good luck.
    Dan Mondrik
    Senior Software Engineer, NI-VISA
    National Instruments

  • Instrument Driver (66319B)

    Hi all,
    i need assistance on locating an instrument driver for model no:   66319B , Power supply unit from Agilent Technologies.
    Currently using labview 8.0.
    Thank you.

    Exactly why do you think that the driver is not supported with
    LabVIEW 8? Installing the 7.1 version should allow it to be opened and
    saved. Do you get an error message or something else when you try to
    open it?
     Since it's an IVI driver, you can also create a 8.0 version directly. Look at the link here
    about the instrument driver import wizard. All of the available LabVIEW
    drivers for this instrument have used this wizard to create them.
    Download just the CVI driver to do this.

  • IVI driver development

    Is there any place where there are open projects for delveloping
    drivers using IVI? I know one is ivifoundation.org but that does not
    list if any comapny wants the driver to be developed for his/her
    instrument.
    u'r help will be appreciated as I am interested in developing IVI
    drivers.
    Thanks,
    RK

    I'm not aware of any listing of companies needing drivers written. I'm assuming that you would like to get paid for driver development so you could try contacting instrument manufacturers and see if they have any need. The biggest (i.e. Tektronix, Agilent) include driver developement in the planning of any new product and usually have an in-house staff doing this type of work but occasionally do go outside. You might also approach instrument manuafacturers that aren't part of the IVI Foundation and try to convince them that a driver will improve sales and that you're just the person that can help. You can also browse the other NI forums such as LabWindows/CVI and Instrument Connectivity to search for driver requests. NI also has a Certified Instrument Driver
    Developer program that you might want to investigate as it would probably help you get jobs. Also, you might not want to limit yourself to IVI developement (which requires LabWindows/CVI) but also include the creation of LabVIEW drivers.

  • LabView 2010 - CVI Driver Import Wizard

    I have previously downloaded and used the driver import wizard to create LabView VIs from a CVI driver. Specifically with Labview 8.x and 2009.
    However the latest version of the wizard (v1.3) will not install with LabView 2010 and there isn't a newer one to download w- So the question is, does anyone know if there is an intention to update this wizard so I can use it with LV 2010 ?
    Thanks

    Hi,
    I am having the same problem. Please let me know if this has been resolved yet.
    I tried copying the following directories to labview 2010:
    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

  • Driver development for 6221 card in RTX & VC++

    Hello All,
    For my application, I need to use NI-6221 card in RTX (Adrence/Venturcom) and VC++ environment. Since NI provides RTX support only in LabVIEW environment, It was informed that we need to write a register level program.
    I have got some examples (for register level program) from NI website (MHDDK) which when I try to compile, it throws an error looking for some RTX functions.
    1. I am using RTX v6.0 for development. Is there something else i need to install to get those RTX functions. What is the procedure that i should follow to compile the examples?
    2. In my application, I have the register level program for NI-6013 (E-Series) card in RTX environment. Is the acquiring procedure same for both E-series and M-series cards?
    3. I also need the base address for accessing the cards memory. Is there any document that gives the details of the base address and other offset addresses?
    Any information on this regard will be of great help to me.
    Thanks,
    Ashok kumar A.

    THE ANSWER IS THAT YES YOU CAN DO THIS IN NI-VISA!
    Some have said that you need a kernel driver. This is partially true in that a PXI or PCI card (they are the same as viewed by the OS) must have a kernel driver. NI-VISA provides one for you.
    You said that you do not have a manufacturer ID. This is a requirement of all PCI cards and no kind of driver will work until the card has one. Once you have this ID, run the VISA PXI Driver Development Wizard and it will generate an INF for you for all supported NI-VISA environments that support PXI/PCI. Read the instructions in the appropriate INF file for how to install it into the system so that the OS will attach NI-VISA to your device. It's really simple. NI-VISA supports PXI/PCI on Windows 95, 98, ME, NT
    4, 2000, XP, and LabVIEW RT.
    Some have said that MAX will just show you all PXI/PCI devices in your system. Your device will not show up until NI-VISA can see it, and that won't happen until you generate an INF as described above.
    Since the INF file associates NI-VISA itself to your card, the ADE you use does not matter. NI-VISA supports PXI/PCI in LabVIEW, CVI, MSVC, Visual Basic, or any other ADE that normally works with VISA.
    NI-VISA works well even with more advanced devices because we support all types of register accesses (config, I/O, memory) as well as interrupt handling. Just look at the visa.h that NI ships in the VXIpnp directory. If you are using C/C++, make sure you define NIVISA_PXI before including visa.h. If you use LabVIEW, you need to use the address space numbers as defined in visa.h.
    Good luck.
    Dan Mondrik
    Senior Software Engineer, NI-VISA
    National Instruments

  • 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

  • Can I use instrument driver in a software applicatio​n

    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.

Maybe you are looking for