LabWindows: Connecting Oscilloscope LeCroy WaveRunner 64Xi via GPIB

[LabWin_User]

Dear Sirs,
we updated our oscilloscope and bought therefore a new LeCroy WaveRunner 64Xi which should communicate with my current LabWindows (V5.5.1) application via GPIB.
The current application works with the older oscilloscope LeCroy LT354 and the LeCroy 9314A.
I used the NI software driver/interfaces named LEC9xxx (ANSI-C sources and on *.fp-file).

Now I have problems with this driver for the new oscilloscope.

Can I use this driver with few changed done by myself or is there a new driver available for this oscilloscope?

[thehobbs]

There is not currently a driver for LabWindows/CVI that officially supports the new WaveRunner Xi series.  LeCroy has an IVI-C driver for CVI that supports the WaveRunner Series:

http://www.lecroy.com/tm/Library/Software/LabView/LabViewDrivers.asp?menuid=8

You should try this driver with your Xi instrument.  You may be required to disable ID Query in the Initialize function.

I hope this helps.

[ugursarac]

While initiating the wavepro 7300 XXL via GPIB and with IVI driver, lecroy is giving "illegal header path for command" log message. what is the problem? Thanks,

[Leonard33]

Hi,

It sounds like the header file path is not setup in Measurement and Automation Explorer (MAX).

Start here: http://zone.ni.com/devzone/cda/tut/p/id/3377 (This is a link to an NI document titled "Getting Started Using National Instruments IVI with LabVIEW or LABWindows/CVI")

It will show you how to setup the IVI driver in MAX.

Let me know if this does not resolve the error.

Leonard Brown

LeCroy Applications Engineer

[ugursarac]

Hi, thanks for your response.

we are trying to solve our problem using the documents you adviced. But we could not accomplish to reset the Lecroy without error.

I could not understand the relation between header problem and MAX.

Thanks,

[Leonard33]

Hi,

I have to appologize, I am confusing LabWINDOWS and LabVIEW.

In LabVIEW, you can use the import wizard to create a vi for each function in the dll file.  Part of this is specifying the path to the header file.

I do not have enough experience yet with LabWINDOWS/CVI to tell what the issue is.

I will get my IVI driver working with LabWINDOWS and get back to you on this.

Cheers,

Leonard Brown

LeCroy Applications Engineer