GPIB control....

[Srm27]

As always I am not sure if I am asking this correctly, but let try.

I have a number of GPIB instruments to control.

We have the following to be controlled:

Stanford Research DS360 Ultra-low Distortion Function Generator Signal Generator

TTi TSX3510P, power supply

Keithley 2000 6½-Digit Multimeter

I have downloaded IVI drivers for the Keithley 2000 and I appear to have two .fp files  

C:\VXIpnp\WinNT\ke2000

C:\Program Files\IVI Foundation\IVI\Drivers\ke2000

From CVI when loading an instrument which .fp file should I go for?

If, for example, I set the Keithley to DCV, 1V range, go do a test and come back and try to repeat the setting will it be done or will it know it is already set?

I ask as there would be a need to account for setup time, within the instrument, when the request is sent.

There are no drivers for the Stanford Research DS360, any suggestions the best course of action, let make it simple as I am a simple man with little time to implement it.

 

Thanks for you patience and time

Simon

[Shawn_S.]

Hello Simon!

For the Keithley 2000 IVI driver, you will want to use the *.fp file in the C:\Program Files\IVI Foundation\IVI\Drivers... folder.

In regards to the Stanford Research DS360 driver, unfortunately it's not supported.  

However, it is possible to convert LabVIEW project-style instrument drivers into a C programming language driver with the LabVIEW Instrument Driver Export Wizard.  The problem is that the Standford Research srds360 driver is a LabVIEW plug and play driver, not a LabVIEW project style driver.  So, if you had a copy of an older version of LabVIEW (Version 8.0 or 8.2), you could manually transfer the files from the plug and play driver into a LabVIEW project and then export the project style driver into code that LabWindow/CVI would recognize.  We tried to do this on our end, but could not get this driver  to successfully export.  This is likely because the driver is not supported.

It would be easier to create a LabWindows/CVI driver and then submit it so that we may add it to our Instrument Driver Network.  You will want to use the LabWindows/CVI templates and the manual for the DS360 to build the driver.  To guide you, the rest of our tools are available here; you will want to find the LabWindows/CVI Plug and Play section, and I would not worry about certification since you are looking to get up and running quickly.

[Srm27]

Shawn,

Thanks for the pointers and help.

Can I ask, the links you provided, submit it and here are the same as far as I can see is that correct?

The other point that I am still unclear is if you send the same setup to an instrument via GPIB is there a setup time the same if you change between settings?

I ask as at the moment we use python and RS232 to control the instruments. Part of the control is that it will only write to the instrument is the setup is different as, I am told, there is a setup delay even when the instrument receives the same command.

Thanks for the help

Simon

[Wolfgang]

While I don't know the instrument I would agree that there is always a delay - every task takes roughly PI times as initially scheduled and every instrument needs some processing time

Of course this depends on the instrument and on the interface. From my experience, GPIB is quite slow, but it also depends on the manufacturer of the instrument. For example, reading a scope waveform (same number of data points...) from scope A and scope B may show differences of a factor of 5 simply due to the processing time of your commands.

So I always empirically determine the delays for a given instrument/interface combination and add this specific delay time to the software. 

[Shawn_S.]

I appologize.

The link to our Instrument Driver Development Tools is here, and I've included the actual address below.

Instrument Driver Dev Tools

http://www.ni.com/devzone/idnet/development.htm

Wolfgang is right, delays can occur due to processing of commands.

[Srm27]

Hi,

Thanks for the direction/pointes, and so the adventure continues.

Been a bit (a lot) on the lazy side any good examples I could use/get inspiration from!!!

I know I will need to come back to this topic, but hopefully not too often.

Thanks

Simon