Import CVI instrument driver in 8.0

[test_man]

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

[test_man]

anybody please?

[shahina]

Hello Sheetal,

When you refer to version 8.0, do you mean you are using LabVIEW 8? Or are you having problems converting your instrument driver using the LabVIEW Interface Generator for LabWindows-CVI Instrument Drivers in LabVIEW 7.1 (whereas the built-in tool has worked with LabVIEW 7.1 before)?

Are you using the Basic or Advanced configuration and can you post the report generated from running the conversion utility?

If you would like to convert a CVI instrument driver from LabVIEW 8, then we have a beta version of the utility here:
ftp://130.164.213.28/Upload/FP%20Converter/DriverCtoLV.2005.11.07.exe
However, please note that this is still a beta quality software.

Thanks and best regards,
Shakhina P.
Applications Engineer
National Instruments

[test_man]

Hi,

What I meant was I use LV8.0. and I have problem converting CVI instrument drive to labview VIsin 8.0 which worked fine in 7.1.

So if I use built in conversion program in 7.1 it works fine and generates all vis for every funstion in instrument driver.

As I wrote these are just plain c functions without and instrument interface.

I tried both modes in 8.0 Basic and advanced.

[rolfk]

Since you can create the LabVIEW VI library in LabVIEW 7.1 to call your CVI instrument driver, what hinders you to just load the LabVIEW 7.1 version of that driver in LabVIEW 8 and use it?

Rolf Kalbermatter

[test_man]

Well that is fine. But you would expect to work 8.0 same way. I will post my fp and code here as soon I get chance.

[alexlights]

Hello,

The link times out for me: ftp://130.164.213.28/Upload/FP%20Converter/DriverCtoLV.2005.11.07.exe.

I'm trying to make a VI from the Yokogawa 2533 power meter cvi found at http://sine.ni.com/apps/we/niid_web_display.download_page?p_id_guid=E3B19B3E9381659CE034080020E74861.

I did it in class with 7.1, but now that I'm back in the office with LabView 8.0, I can't seem to get it to convert. I'm going to keep looking in the help files and on line, but any help here would be great.

I have LabView 8.0 with CVI 8.0.

Thanks,
_ALEX

[alexlights]

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?

[Dennis_Knutson]

I looked at the driver and since it doesn't come with a DLL, the conversion tool will not work. All the conversion tool does is put a LabVIEW wrapper around the Call Library Function Node. LabVIEW itself does not come with a C compiler to create the necessary DLL from the source code. You can try posting your problem to the CVI forum and see if someone can create a DLL for you.

[alexlights]

I think I got it.
In the CVI program i made an IVI, under tools/create ivi.  I was then able to use the LabView tool to convert that to a bunch of VIs. Of Course they don't work, I need to configure the communications...but I'm on my way...