LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Help, rather stuck: Should it take 22 ms to (via Visa) write "ISET 2" then "ISET 0" to an instrument? (to a Kikusui electronic load if you're curious)

Hey everyone, I'm trying to create an application that can generate 10 ms wide pulses of current in an electronic load. My program was incapable of doing this, as it seemed to be generating pulses ~66 ms too long. After much optimization I halved this, but that is still far far too much error.

So, as an experiment, I tried telling the load to go to 2 amps, then back to 0 immediately so I could measure the minimum possible time by doing the following:

I wrote a .VI that initializes a Visa session with this hardware I have (a Kikusui PLZ1003WH electronic load to be exact) and then using the Visa write f
unction that is a part of Labview, I wire the string constant "ISET 2" to the "write buffer" input, and the visa output from my initialization function to the "Visa resource name" input. Then from there I wire the dup Visa name to the next Visa write, as well as the string constant "ISET 0" to that "write buffer" input.

The delay, measured on an oscilloscope, is a huge 22 ms. I've got a 233 Mhz processor, and even if this program is 200 cycles long, thats a mere 85.8 nanoseconds. GPIB should be able to handle these 96 bits of information (plus whatever parity/error checking stuff may be used, of course) in 64 microseconds. The cable is only five feet long, so the signal should get there in about 15.2 nanoseconds. So, we're talking a mere 64 microseconds, thats all it should take. Even adding a factor of 10 for the internals of the load, it's not responding near as fast as I would expect.

Anybody have any idea why this is so terribly slow?
0 Kudos
Message 1 of 6
(3,157 Views)
One thing that you're forgetting is how long it might take for the instrument to respond and acknowledge. Maybe the Kikusui takes that long to resond to a new current setting. Getting hold of GPIB bus analyzer and looking at the handshaking lines or talking to Kikusuui might be necessary.
0 Kudos
Message 2 of 6
(3,157 Views)
"GPIB bus analyzer"? Is that a program?

Where can I find such a tool?
Thanks,
Dobbs
0 Kudos
Message 3 of 6
(3,157 Views)
A bus analyzer is a harware tool. It is part of the + series of GPIB controllers from NI. There are also stand alone analyzers available from other manufacturers. For a purely software tool, you can use NI Spy (one of tools with MAX) but I don't think you'll get all of the information you're looking for with this.
0 Kudos
Message 4 of 6
(3,158 Views)

Dennis hi:

I hope you are able to gime a hand with KIKUSUI PLZ-30F electronic load.

1. I'm talking to the instrument via GPIB and it communicates.

2. It doesn't respond on a settings commands - change from CC to CR mode, etc.

3. There are 3 modules in a frame - one master and two slaves.

4. I'm suspicious I'm missing something, and... this company does not have techsupport...???

5. Their drivers have entirely different format from SCPI and I have no use to them.

6. There is an IVI driver - but I didn't try it yet.

 

Best,

Oleg Finodeyev

0 Kudos
Message 5 of 6
(2,951 Views)
I no longer have the load and I don't think the manual is around either. I don't know what IVI driver you are talking about since there isn't any Kikisui IVI drivers on NI's site. There is a LabVIEW driver for the PLZ 3W and 3WH. Have you looked at taht to see if the commands are the same as the instrument you are using?
0 Kudos
Message 6 of 6
(2,943 Views)