test circuit for this blog. The PSU delivers power, the eLoad draws it. The DMM measures the current. All are controlled by LabVIEW

IVI: Interchangeable Virtual Instrument. What's that?

All three devices in this setup use the LabView virtual instrument interface (IVI).

If you have another PSU or DMM (or even the load!) you can substitute the LabVIEW blocks with those of your instrument.

IVI is an initiative to have a similar driver for similar instruments.  Reusable abstract blocks that represent a DMM, scope, PSU, ...

Whether you have PSU (or other lab instrument) from vendor A or B, the IVI drivers try to help you abstract from that.

It actually works if two instruments have the same functionality. I was able to port a Rigol oscilloscope flow to a Tektronix one with little changes.

When I wrote the IVI drivers for my load, I consulted the ones made by BK and other suppliers, to find common ground.

I've investigated IVI drivers from several suppliers, and they tried to stick to this paradigm for common functionality.

Experienced users will tell that this isn't magic, and that's true.

It works when you're using a DMM, PSU or scope as usual and do your best to abstract from the hardware (like programming portable C ).

It doesn't when you've built a flow with a specific instrument in mind.

The IVI drivers for the DMM and PSU I use are available from National Instrument's website.

The IVI driver for the eLoad is developed and available on element14.

The LabVIEW Test Panel

You can control the test behaviour from the control panel I built for this flow.

The red square defines what the power supply does.

It will run a number of cycles, stepping from start voltage, increasing the output of the PSU with the voltage increment.

If you select single run, the flow will stop after these steps are taken. Else the process will run until you push the stop button.

The green square groups the settings for the device under test - the DC load.

I'm using the low level API here: talking directly to the DAC that controls the constant current.

Similar to the PSU, it steps through a number of DAC settings, with a start point, a number of steps and an increment.

This is the inner loop. It's running through all the settings for each step the PSU takes.

The blue rectangle shows the progress of the test.

You can see how many iterations the outer loop (left) and the inner loop have taken.

The orange part are the DMM settings and results. The meter is set to current mode. Measurements are taken in the inner loop, after the eLoad constant current is set.

All values are written to a spreadsheet.

Additionally, some measurements of the PSU and the ADCs of the load are logged.

This allows to see the effective current that the load draws for a given DAC setting.

And how the ADCs measure that current, the temperature and the voltage at the terminals.

We have 3 compare points for the current - that is the same in all three instruments. It's a series circuit.

• I ask the PSU how much current it delivers (reasonably precise).
• I ask the DMM what current it measures (very precise).
• I record the value of the ADC that measures the voltage (I want to make that precise).

Because the data is in a spreadsheet, you can run analysis over the values to find out the behaviour of the load. Both the control part and the measure part of it.

The LabVIEW Flow

You'll always find a part of the process that connects to the instruments and initialises them. And a closing block.

These I'm not going to show here. I attach the project so that you can view those yourself.

Let's focus on the outer and inner loop.

click to enlarge

You'll see three lanes. The DC Load on top, the PSU in the middle and the DMM at the bottom.

The outer loop is marked red and controls the PSU.

You can see an incrementer block that alters the settings at each iteration.

Each loop, the new value for the PSU voltage is calculated and sent to the instrument.

The green square marks the inner loop - executed several times for each PSU voltage setting.

Again it's controlled by an incrementer block. The desired DAC setting is calculated and sent to the eLoad.

Then - in the middle of the inner loop, after all instruments are set, the flow retrieves data from load, PSU and DMM.

At the end of the inner loop, one row of data is written to a spreadsheet.

At a few places I've placed a wait, to allow things to settle and - in case of the eLoad - wait for the firmware to retrieve the last ADC values.

The flow is attached. And a sample spreadsheet.

You can view the full flow with the LabVIEW Community Edition.

Attachments:

eload_dp832a_dmm6500_current_25.xlsx	eload_dp832a_dmm6500_current_25.xlsx
eload_examples20200429.zip
	labviewreport.pdf