Importing CVI driver to LabVIEW 5.1

Hi,
I want to import a CVI driver to LabVIEW 5.1. I am familiar with the process of converting CVI driver to LabVIEW 7 library but i do not find that tab in labVIEW 5.1
Can somebody help me out?
Regards,
Siddu

Hi Siddu,
Since there isn't a direct way to "Import CVI Instrument Driver" to LabVIEW 5.1, you will have to build the code that calls the CVI driver yourself. You can either call the CVI code using a CIN Node or you can compile the driver to a DLL and call it from LabVIEW using a Call Library Function Node. I definitely prefer the latter approach. All you then have to do is create small 'wrapper'-VIs that call each function in the DLL. Remember to connect the front panel objects of the VI to the connector pane, so it can be called as a SubVI.
Search our Web site for information on how to create a DLL in CVI and use the following manual for information on how to call the DLL from LabVIEW:
Using External Code in LabVIEW
- Philip Courtois, Thinkbot Solutions

Similar Messages

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

    When I import CVI fp into labview it converts my const char * to int without any warning...
    For example CVI function:
    void my_func(const char *value);
    Labview conversion:
    void my_func(int *value);
    Any help?
    Thanks.
    CVI 2010
    LabVIEW 2011 SP1
    Vision Builder AI 2011 SP1

    Hello Sheetal,
    I wasn't able to reproduce the problem if I use char * instead of const char * in the function panel.  Were you able to do so?   Either way, when you initially convert your FP to LabVIEW code, you are asked to specify a DLL that contains the code associated with the function panel.  I would double check that the function prototype inside the DLL specified in the 'select a shared library or DLL'. is not set to int *.  When I used char * or const char * in my DLL, LabVIEW convert the parameter to be a CStr data type, which is the same as char *.
    Thanks
    Wendy L
    LabWindows/CVI Developer Newsletter - ni.com/cvinews

  • 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

  • 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

  • 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

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

  • Importing Instruments Driver from LabWindows/CVI

    Does anybody have got wintools_32.dll library ?
    I need it to convert LabWindowc/CVI Wintools Instrument Driver to Labview.
    Could you send it to me?
    Romek.
    [email protected]

    Hi!
    Thanks for your answer.
    Exactly, I've tried to import LabWindows/CVI instrument driver to Labview.
    This Instrument driver I've found here:
    http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?p_guid=B45EACE3F04956A4E034080020E74861&p_node=DZ52176&p_submitted=N&p_rank=&p_answer=&p_source=External
    During import procedure i was asked about wintools_32.dll library.
    Personally I am interested in System Tray icons functionality of this driver.
    I'm not sure that wintools_32.dll is Labwindows/CVI library, but i've searched Microsoft Windows pages with no results.
    Regards.
    Romek.

  • I have an in-house instrument driver written in labwindows, is it possible to use this driver in labview?

    If this is not possible, how do you go about converting it for use in labview?

    Just go to Tools>Instrumentation>Import CVI Instrument Driver. In LabVIEW 5, it's under the File menu and is called Convert CVI FP File.

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

  • CVI & Driver Instrument

    Hi guys. My problem is to see the Rigol DSA1030A as instrument in CVI. I have connected it via USB and following the guide I have downloaded the IVI driver where I haven't found any *.fp file.
    Yestarday talking with a NI engineer he suggest me to use the VISA...but I have no idea. Is there any guide where I can read something? or by the way can you help me with this problem?
    Thank you

    As I said, I never used Rigol instruments so I don't know the answer to this question.
    In the document linked by Wolfgang in your other thread there indeed is a log (report.html) that refers to LabVIEW VIs being generated out of the CVI driver, so it should be available somewhere... There is also a .msi installer: did you tried running it? Has it installed some particular software or document?
    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?

  • Aeroflex 2975 driver for LabVIEW 8.0

    Is there a way to convert the Aeroflex IFR 2975 driver for LabVIEW CVI for use in LabVIEW 8.0?  OR, is there a driver already developed for this? 

    Frank,
     I am using the LV 7.1.1 version of this CVI driver in an application I wrote. We should be able to recompile this for 8.0. Basically as I explained with no handshaking the instrument falls out of sync with the controlling computer. Basically the only GPIB command that is supported in that driver is *IDN?. So what I have done is after other  calls I use this command and compare the return string to see if it is what I expected. If not I use a popup telling the operator that a GPIB error occurred and to reboot the IFR to clear the bus. I also have instructed the operator to run NI Spy in the background...this seems to cut down the occurance of these errors. Another way to clear the bus that is faster and usually works is to stop the application, and read the bus using MAX until you see a timeout when there is no more data available( usually twice). Then rerun the application. Depending on the application this might be a work around though not an elegant one.
     Since the driver was converted from a CVI driver it uses the call library function node. This does not allow us to control the timing between the Write functions and Read functions. If you are doing something that is relatively simple you could use the TCL command set and VISA to write a driver. Just put a wait function between the Write and Read function and experiment with the timing until it looks like it won't fail. I've considered doing this myself but have been hoping that they will actually make the instrument 488.2 compliant. I am assuming that the actual error is that the data buffer is being read by the controller before the instrument is finished writing to it. The other scenario is that the data buffer might not actually be getting flushed every time it is read. I'm hoping my first assumption is correct or they have even more problems with the instrument.
     In January of '05' they actually enabled the following commands *SRE xx, *SRE? and *STB?. I recently wrote a simple vi to see what happens to the Status Byte after using IDN? command and reading the data buffer. The MAV bit begins logic low, then goes hi when the data is available. After reading the data (i.e. "IFR Systems, 2975.....) I again query the Status Byte. The MAV bit is still in a logic hi state. I sent screenshots of the front panel and block diagram as well as the .spy files to them. All was heavily notated and they said they were going to look at it. If anyone is interested in this I can post this code as well.
    Using LabVIEW 2010SP1 and TestStand 4.5

  • Import Live Video into LabVIEW

    I am an electrical engineering working on my senior project at Western New England College. I am working with a small team building a quadrotor UAV and part of my task is to add some image processing to the craft. I have the algorithm to do the processing but I am not sure how to import the images into LabVIEW. We are using a FlyCamOne3 camera on the UAV and transmitting the images back through a 5.8 GHz transmitter and want to take the video from the receiver into LabVIEW. We do not have a large budget so I was hoping I could use a standard capture card to read the video in and pass it to LabVIEW. I read that the device needs to be DirectShow compliant but I do not know what that means exactly. The reading I did indicated that DirectShow is a piece of software from Microsoft and not a part of the hardware. Our team plans to run all of the code on a laptop so the capture card would have to be USB, firewire, or ethernet. I would really appreciate any help finding an appropriate capture card for this application or some other solution to the problem.
    Thanks for your help
    Tyler

    I have spent a good part of the day searching for firewire, ethernet, and USB 2.0 capture cards without having much success. It appears that the options on that front are fairly limited and I was having a hard time confirming that the options I found would be DirectShow compliant. I finally found an older thread on this forum which suggested to use a video to firewire converter however. I managed to find Video-to-USB converter which converts from an RCA video to USB and the documentation claims it has a driver for LabView. Is there any way to tell if this would be compatible with newer version of LabView? I am concerned that the hardware is about 5 years old and if things have changed substantially in the way LabView aquires the image then it may not be compatible anymore.
    Thanks,
    Tyler

  • Control CD or DVD Drive through LabVIEW

    Hi All,
    I am interested in controlling my PCs internal CD/DVD drive using LabVIEW. I've had a look around the forums and ni website and it seems that external CD drives can be controlled using a PXI card and the SCSI interface.
    Searching the LabVIEW help I haven't been able to find any reference to SCSI but I guess the protocol must be implemented somewhere as it can be used with the PXI card I found referenced during my search.
    Initially I would like to just open and close the drive - if anyone can offer some pointers in the right direction I would appreciate it.
    Also if anyone is familiar with the level of access provided by SCSI maybe I could get a little extra information. For example eventually it would be useful to be able to control the motor speed of the CD turntable independently - is this type of command exposed in SCSI?
    Many thanks for your help,
    David
    Solved!
    Go to Solution.

    Open / Close, here: https://decibel.ni.com/content/docs/DOC-19732
    Beginner? Try LabVIEW Basics
    Sharing bits of code? Try Snippets or LAVA Code Capture Tool
    Have you tried Quick Drop?, Visit QD Community.

Maybe you are looking for