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

Similar Messages

  • 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

  • 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

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

  • Teststand call cvi instrument driver

    I'm new to working with instrument drivers in TestStand. I'm trying to use TestStand to call a CVI instrument driver dll (for Agilent N5767 power supply), and then perform a specific function (init, set voltage, set current, etc.) All of the instruments in my test bench are connected via LAN, and they are configured in NI MAX too. I thought it was pretty straight forward, but I'm obviously missing something. Attached is the simple TS 3.1 seq file with the steps I'm trying perform.
    Attachments:
    N5700_on_off.seq ‏20 KB

    Hi Bkoch1,
    Please elaborate on the problem you are experiencing. I am able to open the sequence file you have attached and view your steps and on the surface, this seems like it should work just fine. What indications are you experiencing that it does not work fine? Have you tried setting breakpoints and using the Watch Window to monitor variables to ensure that they are being passed into the DLL? Please explain what the problem is and try to narrow down where the problem occurs and we would be happy to help you.
    Regards,
    Jackie
    DAQ Product Marketing Engineer
    National Instruments

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

  • 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

  • No longer able to import movies from Sony HDR-SR10

    I have a Sony HDR-SR10 camera. I have previously been able to import videos from it to iMovie '08, but now I always get an error :
    *An Error Occurred During Import*
    There was a problem importing 1 of 1 clips from your camera. Please review the imported movies carefully.
    I can't think of anything which has changed since when I was able to import movies, except that I have upgraded to Snow Leopard.

    Hi Winston, thanks for your answer. It's a bit worrying to hear about having to format the camera every now and then' I haven't formatted it since I bought it 18 months ago...
    No, I don't have any other software that can convert the videos. Is there any free software which can do it?
    I did try repairing the image database on the camera, but it didn't help.
    I don't know if this is clear from my previous post, but none of the clips on the camera can be imported; it's not just some of them. There are hundreds of clips on the camera...
    Sony have told me I should upgrade to iMovie '09; do you know if this is likely to help? Could the problem be caused by running iMovie '08 on Snow Leopard?
    Thanks for your help.

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

  • No longer able to access external hard drive

    Since upgrading my MacBook Pro to Mountain Lion I can no longer mount either of my NAS (iomega and buffalo) I've tried connecting via finder, connecting via IP address. Nothing works it just times out or shows connection failed.
    I can connect fine on my old MacBook running Lion and was able to connect with my Pro before the upgrade.
    Neither NAS has firmware updates available and the only change is the upgrade to Mountain Lion. Any suggestions how I connect to my back-up drives now?
    OSX 10.8.2
    Buffalo Linkstation Live LS-CHLv2 2TB
    Iomega Home Media Network Hard Drive Cloud Edition

    OK, I tried that with a couple of music folders. So far so good.
    Does this mean I have to select all my music files and add them to the new library file created on the external drive? I'm not sure how or when this problem began. I've had this external drive arrangement working for two years. I suspect it happened with the iTunes 7.5 upgrade but it wasn't noticed until today.
    So do I go ahead and recreate the Library file by adding all the music folders into it? I realize I'm going to lose playlists, but that isn't a big deal.

  • No longer able to import CD's into iTunes

    Hi,
    I have a customer whom with I set up a music server running iTunes.
    This has worked fine for the past two years, no problems at all - he has nearly 25GB of songs on there and about 20 playlists.
    The problem has now arisen where he is unable to import any more CD's
    When he puts a CD in it appears correctly in Windows Explorer and you can see the tracks on it.
    You do not get prompted to import the CD.
    It no longer appears on the left hand menu as a CD from which you can choose tracks to import.
    Interstingly when you click File - IMPORT you can select and import individual tracks but not multiple.
    I have tried a new CD drive and it has the same problem. I have also updated to the latest version of iTunes and he still as the same problem
    Any suggestions would be gratefully received!

    This just started for me too. Isn't there a fix from apple on this? This is in apple's software, not the computer. I can import cd's through the burner but it says disc burner or software not found when trying to burn one.I tried several things but one of the solutions listed is to uncheck the cd text button but my cd text button cannot be changed(faded but not gone)I've tried to repair it,uninstall and reinstall,update drivers,new gear driver software,slowing burning speeds to 8x or less but this seems to be a software issue. Help!!!

  • No longer able to import photos onto my iPod Video 80GB

    Hi all
    I have had my iPod Video 80gb for about 2 months and at first enjoyed viewing my photos on it. The day that V7.3 was released & I upgraded I experienced several problems, some of which are already well documented on this forum. One problem that nobody else seems to have mentioned, is that I can now no longer import any of my photos onto my iPod. I receive the message...
    “Some of your photos including filename.jpg were not copied to the iPod Caraline’s iPod because they cannot be displayed on your iPod.
    As absolutely nothing had changed on either my iPod or my computer (other than iTunes version) I presumed this problem was tied up the new version. As I was having other problems with this version I decided to uninstall and re-install V7.2. However the problem persists. I even tried deleting everything from my iPod and every iTunes file, folder & cache and starting from scratch again with V7.2. I have also re-set my iPod back to the factory settings.
    It does not seem to matter what the source of the original photos was, either from camera, or scanned, nor does it matter the size. I have spent hours experimenting, and absolutely nothing I do seems to solve this problem.
    I am totally stumped as to why photos that I once could copy onto my iPod now are deemed undisplayable. I feel terribly disappointed as my iPod now seems crippled and does not perform a function that was a main consideration in buying one in the first place.
    Any help would be greatly appreciated.

    Sorry everyone. I just realised that photos are discussed in a the iPod forum and this topic is being covered there. So please ignore this post.

Maybe you are looking for