Power Supply Programming Part 2: What Type of Programming Language to Use

Happy Halloween Watt’s up fans!  Today I want to look at what programming language you are going to use to write your program.  Instead of recommending a particular language, I am going to break it down by graphical versus text based programming.

Let me start by saying that there really is no correct answer to this question.   This is a matter of personal taste.   

I am going to start with a bit about my background.  Unlike most of my colleagues, I did not specialize in analog electronics in college.  I focused more on computer engineering.  Due to this specialization, I have taken quite a few programming based courses.  I prefer sitting down and programming using a text based programming language because of my background. 

 Graphical programming languages are a very popular option (Agilent VEE is the one that I am most familiar with).     I find these programs are great for doing short programs.  If something can take up less than one page on your computer screen, then it works pretty well here.  These languages also make building user interfaces really easy since there are a lot of easy to access functions for controlling and displaying instrument data.  I personally find that they get very unwieldy if you want to send and read a lot of data with an instrument.  I also find the looping constructs to be strange.   People have told me that these graphical languages look very similar to circuit diagrams and I can see how people would prefer that kind of view to just plain text programming.

I am going to make a confession.  If I have to write a program quickly and I do not have to show it to anybody, I still will write it in HPBASIC.  I find it to be very easy to do simple instrument programming.  There is no need for drivers, once it is set up properly; sending and receiving information with an instrument is a breeze.    Large programs do not fare very well in HPBASIC though.

My preferred way to program these days is Visual Basic (using VISA-COM IO).  If you look at the power supply example programs that we provide, there is a lot of VB in there.  I feel that a text based program allows you to write much more compact code. It takes up a lot less screen space than an equivalent graphically based language.  Something like Visual Basic is also more versatile since it is not only for test and measurement but for more general applications.  The looping constructs work very nicely here and to me the flow makes more sense.  I also find typing quicker than connecting boxes.  Text based programming does have some cons though.  For one, the graphical languages are written from the bottom up to do instrument control.  They have built in functions and data manipulation that make thing easier.  The graphical languages also have some really good libraries for building User Interfaces. 

 The real correct answer to the questions is the best language to use is the one that you are most comfortable programming in.  If you think that I missed any pros or cons please feel free to share in the comments.

Protect your DUT from over-current in more ways than one

Last month, I posted about one of our new families of products: the N6900/N7900 Series 1- and 2-kW Advanced Power System (APS) DC Power Supplies (click here). I typically like to post about more general power topics rather than focus on specific Agilent products, but this product has some really interesting features from which you can benefit. After 33 years of working on power here, there aren’t too many new products that get me excited, but this is one of them! So here is a story about an application for it.

Earlier this month, I visited one of our customers that had a device under test (DUT) whose input was sensitive to too much current. That is typically not a difficult issue to protect against using Agilent power supplies with over-current protection (OCP). Set the current limit to a value that you don’t want to exceed, turn on OCP, and the power supply output will go into protect (turn off) when the current limit value is reached. Simple enough! But this customer had an additional requirement. In addition to an OCP value as just described, he also wanted to shut down the output if the current exceeded a lower current for more than a specified amount of time. So he wanted the power supply output to go into protect (turn off) if either of the following conditions occurred on his DUT (I changed this example to protect his information):

       1.  DUT input current exceeds 6 A for any amount of time, or
       2.  DUT input current exceeds 4.5 A for 80 ms

To be honest, at the time of the visit, I wasn’t sure if our new product could do this. The product is so new and so feature-rich that I am not yet familiar with all of its capabilities. But when I returned to my office, I set it up and found it was very easy to do! Here is the solution:

I used the advanced signal routing and logical trigger expressions built into our N7952A APS to setup both requirements. I could have sent SCPI commands to setup the same trigger configuration, but our free Power Assistant Software (N7906A) made this even easier. Figure 1 shows the software with the configuration.

If, after creating the configuration, I want all of the SCPI commands that correspond to it for a program, I could use the software feature “SCPI to clipboard” that creates them from the configuration. See Figure 2.

Take a look at this feature in action. Figure 3 shows a scope trace of the current waveform. As you can see, currents that are less than 4.5 A do not trip the protection. And currents above 4.5 A for less than 80 ms (and below 6 A) also do not trip the protection. But as soon as the current exceeds 4.5 A for 80 ms (and remains below 6 A), the protection tripped – the output shut off causing the current to go to zero amps.

This is just one example of how versatile the N6900/N7900 APS power supplies are. For more information about how these advanced power systems can help you in your power application, please use this link: www.agilent.com/find/aps. To explore this advanced signal routing and logical trigger expressions feature even more, take a look at a post from one of my collegues: https://gpete-neil.blogspot.com/2013/10/protecting-your-dut-during-test-with.html

Quickly Measure a High Brightness LED’s (HBLED) Forward Electrical Characteristics

It’s not hard to notice (or extremely hard not to notice!) how high brightness LEDs, or HBLEDs, are quickly becoming commonplace all around us in our daily lives. LEDs are no longer relegated to being an indicator light on a display panel. HBLEDs have drastically ratcheted up their output to become sources for illumination.  More and more autos use them for their tail and brake lights. It’s easy to see the “instant on” they have when the auto in front of you hits its brakes, not to mention the deep purity of color they have in comparison to the incandescent predecessors.  They are also turning up in the headlights, the traffic lights, even high power street and parking lot illumination lights, and in countless other places. A lot of testing, characterization, and development work has, and continues to take place, to achieve this level of performance from HBLEDs. This includes making careful measurements of electrical power being provided and the corresponding luminous efficacy outputted, in order to assess its performance.

In my title above I am using the term “quickly” for two reasons in my posting today. First, it is important when trying to capture the forward characteristics of an HBLED that it is performed in a minimum amount of time in order to minimize temperature change due to self-heating.  The temperature an HBLED is running at has in impact on its performance. Minimizing the amount of temperature change improves accuracy of test results in determining the performance of the HBLED, for a given operating temperature. My second reason for using quickly is providing a means to make these HBLED measurements with just a little time and effort.

It turned out using the N6784A four-quadrant SMU module in an N6705B DC power analyzer mainframe worked out really well on both counts of quickly. This set up is depicted in Figure 1.

Figure 1: HBLED test characterization set up

While the N6784A is an extremely fast voltage source it is even a faster current source. With current rise and fall times of just a few microseconds was a simple matter to generate sub-millisecond-long high amplitude pulses of current with fast settling edges to provide the necessary stimulus for performing the forward electrical characterization of the HBLED. This allowed testing to take place in minimum time and avoid significant heating of the HBLED die.

One of the outcomes of the testing is shown in Figure 2, displayed graphically by the 14585A software.  Here a ramped current pulse was used instead of a flat top pulse. The HBLED’s voltage and current were simultaneously digitized as the current was ramped up. This gave a way of characterizing the HBLED’s forward voltage drop for all levels of drive current, from zero to maximum.

Figure 2: HBLED forward characterization results

The N6705B DC Power Analyzer mainframe and 14585A companion software made quick work of the setup, testing, and display of results.  A ramp waveform from the library of pre-defined ARBs was selected and used to generate the current ramp. In this instance it was set to ramp up to 1.2 amps in 1 millisecond. The oscilloscope mode was used to set up the simultaneous capture of voltage and current, synchronized to the current ramp stimulus. As voltage and current were captured it is also a simple matter to display the power, being the point-by-point product of the voltage and current. The electrical power in can then be correlated with a light output measurement on the HBLED for evaluating its performance.

Not only is this setup able to measure the HBLED’s forward characteristics, as the N6784A can source negative voltage and measure down to nanoamp levels it can quickly test the HBLED’s reverse leakage characteristics as well.

Using the power supply status subsystem to improve your test throughput

Continuing on my throughput theme here, one recommendation is to take advantage of the power supply’s status subsystem. Some power supply operations take notably longer than most to complete than others. Two notable examples:

• Initializing a triggered measurement
• Initializing a triggered output transient or output list event

When developing programs you can include long, fixed wait statements to make certain these operations have completed before proceeding. However, this can easily add many tens of milliseconds or more of unnecessary waiting, increasing overall test time.  A better way is to take advantage of the DC power supply’s status subsystem features that eliminate unnecessary waiting for these operations.

Triggered measurement and output sourcing events can substantially speed up testing by providing actions tightly synchronized with other test activities. But they do have some up-front set up overhead time needed for initializing them. Instead of using a fixed programming delay following an initialization operation it is better to take advantage of the Operation Status Group register in the status subsystem, which is illustrated in Figure 1.

Figure 1: Agilent N6700 series DC power system operation status group

The “WTG meas” bit (#3) or “WTG trans bit (#4) in the condition register can be monitored with a loop in the test program to see when they turn true. At the moment the measurement or output sourcing event is initiated and ready for a trigger the test program will then proceed with its execution without incurring any unnecessary additional waiting. This saves a considerable amount of time as illustrated in Figure 2.

Figure 2: Operation-complete wait time distribution

Instead of waiting for the full worst-case each and every time, the wait is now just the actual time. When repeated over and over for all DUTs being tested, the net result is the average of the actual wait time, which in most cases is just a small fraction of the worst case time! The net result can be many tens of milliseconds test time savings, making an improvement in test throughput.

The first five hints of my compendium “10 Hints for Improving Throughput with your Power Supply” can be viewed here: (click here to access).  For those reading our “Watt’s Up?” blog here are getting the opportunity to preview one of the remaining 5 hints yet to be released!

New Agilent Advanced Power System: More on High-Power!

Last week, I announced two new families of high-power system DC power supplies from Agilent Technologies:

• N6900/N7900 Series 1- and 2-kW Advanced Power System (APS) DC Power Supplies
• N8900 Series 5-, 10-, and 15-kW Autoranging DC Power Supplies

Here is the press release on these two new families:

https://www.agilent.com/about/newsroom/presrel/2013/04sep-em13103.html

In my post last week, I concentrated on the N8900 Series of autoranging power supplies. Those are basic DC power supplies with outputs up to 15 kW (can be paralleled to 100 kW and more). Today, I am focusing on the N6900/N7900 Series of Advanced Power System DC Power Supplies. These power supplies really do live up to their “Advanced Power System” label. I’ve been working here on power products since 1980 and have supported several feature-rich product families in that time: most notable were our AC source products (6811B, 6812B, and 6813B) and more recently, our battery drain analysis source/measure units (N6705B with N6781A). The new N6900/N7900 Advanced Power System rivals those products for rich features and quite honestly, just like our marketing slogan says, they really should help you “overcome your toughest power test challenges”. Why? Read on…

First the basics:

• There are ten 1 kW models each in a 1U package
• There are fourteen 2 kW models each in a 2U package
• Rated output voltages range from 9 V to 160 V
• Rated output currents range from 12.5 A to 200 A
• Outputs can be paralleled up to 10 kW

Here is what these products look like:

Now for a few details. There are two performance levels:

• N6900 Series is designed for ATE applications where high performance is critical
• N7900 Series is designed for ATE applications where high-speed dynamic sourcing and measurement is needed

Both performance levels have advanced power features including:

   Sourcing

• Precision voltage and current programming (N6900 is 14-bit; N7900 is 16-bit)
• Programmable output resistance
• Current sinking up to 10% of rated current (up to 100% with added N7909A power dissipator)

   Measurement

• 18-bit voltage and current measurements
• Power measurements
• Amp-Hour and Watt-Hour measurements

The higher performance N7900 products add more features to the above:

    Sourcing

• Precision 16-bit voltage and current programming (N6900 is 14-bit)
• Output lists to quickly step through voltage or current levels
• Arbitrary waveform generation

    Measurement

• Low current measurement range
• Seamless ranging for dynamic current measurements
• Adjustable sample rate
• Measurement array readback
• External data logging

And even more capabilities:

• Extended current measurement range that measures 2.25 x higher than the rated current
• Sampling up to 200 kS/s
• Extensive triggering capability
• Extensive protection features such as open sense lead detect, over- and under-voltage and current, and over-temperature
• And my personal favorite: you can track power events by adding a black box recorder (N7908A). The N7908A Black Box Recorder is a user-installable option that performs continuous background logging of output voltage, current, power, and system status to its own dedicated mass storage device. Features of this option include:
• Automatic logging starts when the power supply is turned on
• Logs in a circular buffer of about 380 MB
• Select one record every 10 ms (24 hours of logging) or one record every 100 ms (10 days of logging).
• Each record saves the average, maximum, and minimum  values for voltage, current, and power in addition to power supply status bits and events
• Logged data is preserved after a power cycle. A time-stamped event is logged each time power is turned on.

The black box recorder is pretty cool, no? If you have a mission critical power application, this option is a must to keep track of any power related events that might affect your device under test.

One of my colleagues, Neil Forcier, posted about these products on his GPETE blog earlier this month. Here is a link to that post: https://gpete-neil.blogspot.com/2013/09/the-new-advanced-power-system-designed.html

For more detailed information, take a look at the datasheet: https://cp.literature.agilent.com/litweb/pdf/5991-2698EN.pdf

The datasheet contains some fantastic details about the products including 9 tests challenges that are directly addressed by these powerful products. In fact, you can read about each of the 9 test challenges here: www.agilent.com/find/TestChallenges

With all of these advanced features built into this family of products, I think you can now appreciate why we called it the Advanced Power System!

New Agilent Autoranging Power Supplies provide Higher Power

I have stated before that I avoid posting product-only-focused material in this blog since our intention here is to educate about all-things-power rather than to (directly) promote our products. But when we (Agilent….for now…) come out with new power products, I think it is appropriate for me to announce them here. The last time I did this was back on January 23, 2012 in this post:

https://powersupplyblog.tm.agilent.com/2012/01/six-of-seven-new-agilent-power-supplies.html

Coincidentally, those products were autoranging power supplies just like some of the power products we just introduced! Earlier this month, Agilent announced two new families of high-power system power supplies with this press release:

https://www.agilent.com/about/newsroom/presrel/2013/04sep-em13103.html

The two new families are the:

·         N6900/N7900 Series 1- and 2-kW Advanced Power System (APS) DC Power Supplies

·         N8900 Series 5-, 10-, and 15-kW Autoranging DC Power Supplies

Today I will focus on the higher power series, the N8900. Next week, I’ll post about the N6900/N7900 series.

What is particularly exciting for us about the N8900 series of products is that it is the highest power level we have ever provided. I’ve been working here at Agilent with power products since 1980 (we were Hewlett-Packard back then and will soon get yet another new name), and until now, the highest-power power supply we offered was the HP SCR-10 Series at 10 kW. This product was discontinued many years ago. Now the new N8900 series has 5, 10, and 15 kW in a single model and outputs can be paralleled for 100 kW or more! Now that’s a lot of power!!

Back when I started, 10 kW came in a much larger package and weighed over 500 lb (227 kg)! Today, we can get 50% more power (15 kW total) in an 80% smaller package (3 U vs 16 U) that is 85% lighter (73 lb vs 500 lb). See the figure below.

The new N8900 series offers 14 different voltage, current, and power combinations with output voltages up to 1500 V and output currents up to 510 A. Outputs can be put in parallel for 100 kW or more. These are basic power supplies, but have autoranging output characteristics so you get more voltage and current combinations from a single output than if you used a power supply with a rectangular output characteristic. See the figure below.

For more information about autorangers and output characteristics, see the post I mentioned earlier (or click here.)

We also created a video introducing the N8900 series (I do a cameo toward the end…can you pick me out?).

These basic power supplies will be used in many different high-power applications, such as hybrid-electric vehicle test and photo-voltaic inverter test. So if you need a basic high-power power supply, check out the Agilent N8900 Series. And don’t hesitate to ask me a question about the product or its suitability for your application.

How fundamental features of power supplies impact your test throughput – Part 2

In part 1 of” How fundamental features of DC power supplies impact your test throughput” (click here to access) I shared definitions of some of the fundamental power supply features that impact test throughput, including:

• Command processing time
• Up-programming response time
• Down-programming response time

Another fundamental DC power supply feature impacting test throughput is its measurement time. There are actually two aspects to a DC power supply’s measurement time as depicted in Figure 1:

• Measurement settling time
• Measurement integration time

Figure 1: DC power supply measurement time

A good indicator of a DC power supply having a high performance measurement system is having programmable measurement integration time, or aperture time, often programmed in power line cycles (PLCs).  One reason for having a programmable integration time is for minimizing any 50 or 60 Hz AC line ripple getting into the DC measurement, by setting the time one or more multiples of a PLC.  Setting the time to 1 PLC provides good ripple rejection with relatively good throughput. When AC line ripple is not an issue the integration time can be set even smaller than 1 PLC, further reducing measurement time. When the DC power supply has a programmable measurement integration time it will no doubt also have a fast-responding measurement system as well, typically just milliseconds, to complement the higher achievable throughput with programmable measurement integration time.

In comparison basic DC power supplies commonly use a 100 millisecond fixed integration time to support AC ripple rejection for both 50 and 60 Hz line frequencies. They also have low bandwidth, slow-responding measurement systems, which can long time to settle after any step change in loading, before a valid measurement can be taken.

We have just introduced our Advanced Power System (APS) DC power supplies. This is a family of high-performance, high power (1 and 2 kW) DC power supplies designed to address the most demanding test challenges. These fundamental throughput-related features for APS are typically more than two orders of magnitude faster compared to more basic-performance DC power supplies, providing much better throughput in manufacturing test. A colleague of mine recently posted details of their introduction on his “General Purpose Electronic Test Equipment (GEPETE)” blog (click here to access) which I believe you will find of interest. Included in this introduction is a link on throughput that takes you to a series of application briefs I have written that go into more detail on improving test throughput with the DC power supply, which you may find very useful.

So how much test throughput improvement might you expect to see by switching from a basic-performance DC source to a high-performance DC source? Well, it really depends on how much the testing makes use of the DC power supply. If it only uses the power supply to provide a fixed DC bias to the device under test (DUT) that never changes for the duration of the test then it will not make a significant difference. More often than not however, a DUT is tested at several bias voltages with several current drain measurements taken for the various bias voltage settings and DUT operating modes. This can add up to a considerable amount of test time. In this case a high-performance DC power supply can more than pay for itself many times over due to improved test throughput.  To get an idea of the kind of difference a high-performance DC power supply can make I set up a representative benchmark test It compares the throughput performance one of our new APS DC power supplies to that of a more basic-performance power supply.  If you are interested in finding out how much difference it made, I made a video of this benchmark testing, entitled “Increasing Test Throughput with Advanced Power System” (click here to access). All I am going to say here is it is an impressive difference but you will need to watch the video to see how much difference!

How fundamental features of power supplies impact your test throughput – Part 1

When it comes to manufacturing of electronic products, reducing test time to improve throughput is virtually always a top priority, because “time is money” as the old saying goes! Usually most all of the attention may be placed on reducing the test time of the banner aspects of the product, such as the RF performance of a wireless device, for example. However, the choice of the DC system power supply can also have a huge impact on your test time and throughput during manufacturing. You may find the lowest cost, more basic-performance DC power supply that meets your immediate needs end up costing you the difference in price many, many times over of that of a higher-performance DC power supply having better throughput performance in the long run!

The DC power supply can incorporate a number of advanced features, such as elaborate triggering and sequencing systems, which will allow you restructure your testing to optimize throughput. However, even fundamental throughput-related features of the power supply can also have a large impact on your test time, including:

• Command processing time
• Output up-programming time
• Output down-programming time
• Measurement time

Figure 1 illustrates what the command processing and up-programming times are for a DC power supply. The command processing time is the time from when the command is first received to the point where the power supply starts acting on it. In this case it is when power supply’s output starts to change. The up-programming response time is the time the power supply takes for the output to rise and settle within a small band around the final output level, after processing the command instructing it to change its output level.

Figure 1: Power supply command processing and up-programming response times

The down-programming response time is like the up-programming response time except that the power supply is instead being programmed to a lower level. However, you need to look at down-programming independently as short up-programming time does not necessarily guarantee comparably short down-programming time. More basic performance DC power supplies usually lack an active down-programmer circuit that quickly brings down the output. In this case the down-programming response time can be very dependent on how much load the DUT presents to the power supply’s output.

How much difference is there in performance between more basic performance and higher performance DC power supplies on these throughput-related features? It can be considerable; over several orders of magnitude difference. As one example, command processing time can range from up to 100’s of milliseconds for entry-level power supplies to under 1 millisecond for high performance power supplies.

Another fundamental throughput-related feature of a DC power supply is its measurement time. There are a couple of aspects to consider here as well, which I will elaborate on in part 2 of this series on how fundamental features of power supplies impact your test throughput, in an upcoming posting here on “Watt’s Up?” along with tying it all together to show how they affect actual test throughput!

Power Supply Programming: How Should I Send Commands to my Instrument

Hi everyone!  Happy Labor Day to all you readers in the US!  Every month I struggle with what I am going to write and wind up waiting till the end of the month to do my posting (and I am keeping that streak alive).  In order to combat that, I came up with a series of topics on programming instruments, focusing on our power supplies.  Let’s say that this is the first in a series of three (or maybe four I am not sure).  Please note that anything that I state here is my opinion and not Agilent policy.  Today I am going to focus on the how to send commands to your instrument.  In other words, what sort of IO library do you use to send the commands?

All of my suggestions will be based on the Agilent IO Libraries as that is the environment that I am most familiar with.  There are two major options: direct IO where you use the SCPI from the instrument and drivers where there are functions that you call.

First let’s talk about direct IO.  I learned how to program instrument using HPBASIC as my programming language so this is where it all began with me.  Agilent has two modern standards for doing this.  The first and the older standard is the VISA library.  VISA works very well when you are programming an instrument in the C programming language.  Here is a snippet of C code from a N6700 example with VISA (I have intentionally not provided comments to show the program in its purest form): 

VISAstatus=viOpenDefaultRM(&defrm);

VISAstatus=viOpen(defrm,”GPIB0::5”,VI_NULL,VI_NULL,&session);

viPrintf(session,"VOLT 5,(@1) \n");

viPrintf(session, "OUTP ON, (@1) \n");

viPrintf(session, "MEAS:VOLT? (@1) \n");

viScanf(session,"%s",&voltmeasurement);

viClose(session);

viClose(defrm);

It works pretty well and makes sense once you know it.  The viPrintf and viScanf functions are very similar to some basic C functions so if you are a C programmer, this is really the way to go.

There is also a newer option that works pretty nicely in languages that support COM.  This option is called Agilent VISA COM.  VISA COM works well in Visual Basic and C#.  Here is the same program to the above written in VB:

Set ioMgr = New AgilentRMLib.SRMCls

Set Instrument = New VisaComLib.FormattedIO488

Set Instrument.IO = ioMgr.Open("GPIB0::5")

Instrument.WriteString " VOLT 5,(@1)"

Instrument.WriteString " OUTP ON, (@1)”

Instrument.WriteString "MEAS:VOLT? (@1)”

Result = Instrument.Readstring

Instrument.IO.Close

In my opinion, this is easier to read than VISA.  When I have to write a program now, I tend to stick with using VISA COM and Visual Basic. 

The other option is to use a driver.  We presently offer two different driver types for our instruments: VXI Plug and Play and IVI COM.  VXI Plug and Play drivers are obsolete now though so I will not reference them further today.  Here is an example of our program using the IVI driver (in C#):

driver = new Agilent.AgilentN67xx.Interop.AgilentN67xx();

IAgilentN67xxProtection2 protectionPtr;

IAgilentN67xxMeasurement measurementPtr;

IAgilentN67xxOutput3 outputPtr;

int channel

driver.Initialize(“GPIB0::5”, idquery, reset, initOptions);

outputPtr = driver.Outputs.get_Item(driver.Outputs.get_Name(channel));

protectionPtr = driver.Protections.get_Item(driver.Protections.get_Name(channel));

measurementPtr = driver.Measurements.get_Item(driver.Measurements.get_Name(channel));

outputPtr.VoltageLevel(3.0, 3.0);

outputPtr.Enabled = true;

mVolt = measurementPtr.Measure(AgilentN67xxMeasurementTypeEnum.AgilentN67xxMeasurementVoltage);

driver.Close();

As you can see, the driver is much more complex than the direct IO examples. There are a few reasons to use a driver though.  The first and most common reason is that your system itself it designed to use drivers.  Another good reason is portability.  There are instrument classes in the IVI driver that should work for any DC power supply that is compatible.  One of the main downfall of our IVI drivers is that the functions almost always map 1 to 1 with SCPI so there are not many functions that work at a higher level and you don’t save any time programming there.

My main approach is to use VISA COM in Visual Basic.  I find it to be the easiest for me to program and it is what works for me.  Of course no opinion is wrong though and we are happy that our readers are out there buying and programming our instruments.  Thanks!

How to choose a Power Supply Part 1: Student Edition

Note from GaryR: We were fortunate to have an intern, Patrick, in our department for the summer. He has since returned to college, but during his time here at Agilent Technologies, he successfully completed several projects for us. During his last week, he wrote a power supply blog post! Here it is, unedited!!

Hello, I am Patrick, an intern here at Agilent Technologies. This is my first blog post but you might recognize me as “new intern… named Patrick” from the Matthew Carolan insta-classic, “What is Command Processing Time?” And as “Uncredited Waveform Capture Author” from GaryR’s visually-stunning, “Current Limit Setting Affects Voltage Response Time” I might not be able to provide the same engineering life lessons Mr. Brorein, Mr. GaryR, and Mr. Carolan provide you monthly but hopefully you will enjoy this post nonetheless.

As you can probably tell from the title, this blog post is the first in a series written to help readers find the right DC power supply for them. For starters, there are a lot of other power supply companies out there; their products are not mentioned here. Actually, I better give you a disclaimer: this is an Agilent blog post about Agilent products written by an Agilent employee. However, my intentions in this post are to inform our readers on how to find a reliable and dependable power supply to the best of my abilities. I simply do not know enough about non-Agilent DC power supplies to be able to confidently recommend you any. With that out of the way, today’s post is written for college students, like myself, but can help give some insight to anyone looking for a power supply.

Agilent Technologies offers over 200 models of DC power supplies. Finding the perfect power supply for your needs is possible but can take some time. Fortunately, you have found your way to this blog post where I have already done all the work.

The first step in finding your power supply to buy is to determine your budget. If you are financially disabled like me, you are really lucky if you can save up $300 - $500 dollars between buying textbooks for a personal power supply. If you need convincing on why you make the expense, Matt’s “The Joys of Owning a DC Power Supply” brings up some good points. Personally, I like being able to work where I want and when I want, including at my home during the summer where I would be lucky to find working batteries let alone a power supply. Also with the lifespan these power supplies have, this is a piece of equipment you will be using for decades. So first, figure out your budget!

The next thing to determine is what are you using this power supply for? Are you a hobbyist who only has low power needs? Do you need to power multiple DUTs at once for a senior project? Maybe you need a very precisely regulated and accurate output for a research project? If I wanted to work on labs outside of school I would need a supply with multiple outputs. If I wanted to work on side projects in my spare time my requirements are a lot simpler. Figure out what your performance requirements are, and try to anticipate future projects if you can.

Now, how much space do you have to work with? Power supplies come in many different sizes. In a test rack, a smaller power supply means more room for other test equipment. As a student you probably are not going to have a test rack, but you might have a test bench. If your test bench is anything like mine, it is also your laptop table, study space, dining area, and entertainment center. As you do before you buy a new couch, make sure you measure before you buy your new power supply.

For a student, here would be my priorities when shopping for a power supply: inexpensive, compact, and capable. All Agilent power supplies already provide low noise and well regulated outputs, so you do not have to worry about that. But keep in mind what functions and features you would like. For example, it would be nice to find one with an autoranging output characteristic, which would essentially allow one to perform the job of multiple, and/or a computer interface.

For those with similar priorities as above, shown in Table 1 are the power supplies that you might like. The table was populated with power supplies listed in our “Agilent Power Products Selection Guide”. The row on the top represents the base (no options) price range of the power supply if ordered from Agilent. The column on the left side represents your best choice in that price range. Keep in mind that the only difference in some budget ranges is the voltage/current ratings, which is important for your application but does not necessarily make one power supply better than the other. Within the table, each square states the model number of the power supply, voltage/current/power ratings, number of outputs, and number of ranges, available computer interfaces, and dimensions. The output ratings are sometimes separated by commas or there is another set listed below the first. If the power supply has multiple outputs, then each output is separated by a comma. If the power supply has multiple ranges, then each additional range is listed below the first.

To use Table 1, simply find your budget range and then match your application needs to the available models. Models in the same budget range but have increased functionality are placed higher.

The two families of power supplies that fall into the sub $1,000 price range are the E3600 and U8000 series basic power supplies. The E3600 gives you a lot of voltage/current choices, a number of outputs, as well as the ability to program with it in four of the options listed above. The U8000 is more limited in all these aspects but is more affordable and has features typically found only in programmable supplies such as OVP and OCP protection, recall states, and more. See for yourself how the E3600 and U8000 stack up against other power supplies.

All the power supplies listed above come in a ½ RU w x 2 RU h, with 1 RU being equivalent to 19” width and 1.75” height. This size is compact and will have no trouble fitting on a desk, and when not being used can easily be moved and stored.

It is unfortunate that there is no relatively inexpensive Agilent power supply with autoranging output characteristics. At least there are choices (within the E3600 series) with multiple ranges, giving you more output flexibility for more applications (learn more about rectangular vs. autoranging output characteristics).

Also there is a three output power supply on the list (the E3630A) which is in the middle of the pack in terms of budget. The E3630A is actually the same power supply available at my school laboratories, able to handle every exercise I have done so far.

As a student, these power supplies might be outside your budget, but the least expensive choice, the U8001A, is about the same price as a Play Station 3. Would you rather choose: “fun” (the PS3) or “FUN!” (a power supply)? Please note that the distinguishing lowercase and uppercase variations of the word fun is not a reference to the level of fun but rather how loud I would yell it at you if we were face-to-face.

So, I have listed out your choices. All you have to do is figure out which one fits your applications. If you do not know what your applications are then you already missed a step in this blog post, so start over from the beginning. If you do not have an application then you probably do not need a power supply, but thank you for taking the time to read this. If you cannot find the right power supply for your application in this post then keep saving your money and look out for the next part on, “How to choose a DC power supply”, that is where the real fun starts. If you read this post and succeeded in choosing a power supply then awesome. Thanks for reading!

Techniques for using the Agilent N6781A and N6782A and their seamless measurement ranging when currents exceed 3 amps

In an earlier posting “Zero-burden ammeter improves battery run-down and charge management testing of battery-powered devices” (click here to access) I had talked about how the Agilent N6781A 2-quadrant SMU can alternately be used as a zero-burden ammeter. When placed in the current path as a zero-burden ammeter, due to its extended seamless measurement ranging, it can measure currents from nanoamps, up to +/-3 amps, which is the maximum limit of the N6781A. The N6782A 2-quadrant SMU can also be used as a zero burden ammeter. It is basically the same as the N6781A but with a few less features.

One customer liked everything about the N6782A’s capabilities, but he had a battery-powered device that drew well over 3 amps when it was active. When in standby operation its current drain ranged back and forth between just microamps of sleep current to 6 or greater amps of current during periodic wake ups. The N6782A’s +/- 3 amps of current was not sufficient to meet their needs.

An alternate approach was taken that worked out well for this customer, which was made possible only because of the N6782A’s zero-burden ammeter capability. The set up is shown in Figure 1.

Figure 1: Setup for measuring micro-amps in combination with large active-state currents

The N6752A 50V, 10A, 100W autoranging DC power module provides all the power. The N6782A is set up as a zero-burden ammeter and is connected in series with the N6752A’s output. When current ranges from microamps up to +/- 3 amps the N6782A maintains its zero-burden ammeter operation, holding its output voltage at zero. Once +/- 3 amps is exceeded, the N6782A goes into current limit and the voltage increases across its output, at which point one of the back-to-back clamp diodes turns on, conducting current in excess of 3 amps through it. This all can be observed in the screen image of the 14585A software in Figure 2. The blue trace is the N752A’s output current. The middle yellow trace is the N6781A’s current and the top yellow trace is the N6781A’s voltage.

Figure 2: Current and voltage signals for Figure 1 setup captured with 14585A software

In Figure 2 measurement markers have been placed across a portion of the sleep current and we find from the N6782A’s measurement readback it is just 1.458 microamps average. The reason why this works is because of zero burden operation. Because the N6782A is maintaining zero volts across its output, there is no current flowing through either diode. If this same thing was attempted using a conventional ammeter or current shunt, the voltage would increase and current would flow through a diode, corrupting the measurement.

Now the customer was able to get the microamp sleep current readings from the N6782A and at the same time get the high level wake up current readings from the N6752A!

In a similar fashion another customer wanted to perform battery run down testing. Everything was excellent about using the N6781A in its zero-burden ammeter mode, along with using its independent DVM input for simultaneously logging the battery’s run down voltage in conjunction with the current. The only problem was they wanted to test a higher power device. At device turn-on, it would draw in excess of 3 amps, which is the current limit of the N6781A. Current limit would cause the N6781A to drop out of its zero-burden ammeter operation and in turn the device would shut back down due to low voltage. The solution was simple; add the back-to-back diodes across the N6781A acting as a zero-burden ammeter, as shown in Figure 3.  Any currents in excess of 3 amps would then pass through a diode. Schottky diodes were used so the device would momentarily see just a few tenths of a volt drop in the battery voltage, during the short peak current in excess of 3 amps. Now the customer was able to perform battery run-down testing using the N6781A along with the 14585A software to log all the results!

Figure 3: Agilent N6781A battery run-down test set up, with diode clamps for peak currents above 3A

Zero-burden ammeter improves battery run-down and charge management testing of battery-powered devices

One way of assessing run-time of battery-powered devices is to power them up with a regulated DC source, place the device into its appropriate operating modes, and get the corresponding current drawn by the device for each of the various operating modes. Estimations of battery run-time can then be made for different user types, based on the percentage of time spent in each of these operating modes, and the capacity of the battery in mA-hours. The DC source must be able to maintain a stable, transient free voltage at the DUT. A lot of general purpose power supplies have difficulty with mobile wireless devices that draw fast rising, high peak currents. Providing the regulated DC source meets maintains a stable voltage, it offers some advantages, including:

• Maintains a fixed voltage level over time, removing variability due to changing voltage.
• Using built-in current read-back eliminates voltage drop issues encountered with using a resistive shunt. This is problematic with mobile wireless devices that draw high peak, but low average current.

An alternative to using a regulated DC source to power the battery powered device is instead use the actual battery. Just like with using a DC source, one can make representative current drain measurements over shorter periods for all the various operating modes and then make predictions on run-time. Alternately one can also perform actual battery run-down tests which, when performed correctly, yields quite a few more insights beyond representative current drain measurements, such as:

• Low battery discharge termination details.
• Battery capacity and energy actually delivered.
• Actual run time achieved.
• How well the battery and device work together as a system

An actual battery-run down test is an indispensable part of validation as a final proof of performance.

Just as with evaluating battery run-down, it is also just as important to evaluate battery charging and management. Again, a lot of testing can be done on a device independent of its battery, but there is also a lot of additional value in validating a device’s charge management performance with its actual battery.

When validating a device’s discharging and charging performance with an actual battery, the first test challenge is the current drawn from or sourced to the battery needs to be accurately measured and logged over time, together with the battery’s voltage, for making good capacity and energy measurements. The second test challenge here is you cannot afford to introduce any significant drop in voltage between the device and its battery, as this alters charging and discharging performance of the battery powered device. This can be a real problem when trying to use shunt resistors.

An alternative is to use a zero-burden ammeter. You may ask how an ammeter can be zero-burden. It has to have some resistance in order to produce a measurable value, right? Well, not always. Agilent provides an innovative alternative use of the N6781A 2-quadrant source measure module that enables it to operate as a zero-burden ammeter (in addition to being a DC source). Using the N6781A as a zero-burden ammeter to evaluate battery run-down and battery charging of a battery-powered device is depicted in Figure 1.

Figure 1: N6781A zero-burden ammeter / wattmeter operation

The N6781A is able to operate as a zero-burden ammeter because it is able to actively regulate its output at zero volts independent of the current flowing through it. Because its output is zero volts, when placed in series between the device and its battery, there is no voltage drop. At the same time its precision current measurement system is able to now measure the discharge or charge currents. In addition a separate voltage measurement port allows it to measure the battery voltage, so now you are able to capture the battery’s discharge or charge voltage profile, as well as determine charge in amp-hours and energy in watt-hours, as shown in Figure 2.

Figure 2: Capturing, displaying, and evaluating battery run-down results with 14585A software

A useful reference providing further details on evaluating a device’s battery run-down and charging, and how to configure and use the N6781A as a zero-burden ammeter are available in our application note; “Evaluating Battery Run-Down with the N6781A 2-Quadrant Source Measure Unit and the 14585A Control and Analysis Software” (click here to access).

What is Dynamic Current Correction?

Gary and I were talking to one of the design engineers here yesterday about what he worked on recently that might make a good blog post.  We wound up talking about dynamic current correction.  This is an option for the current measurement systems of some of our power supplies.  In order to explain its purpose, let us start with a simplified picture of one of our power supplies:

If you look at the above figure, the current monitor resister is inboard of the output capacitor.   This means that our current measurement system is going to measure both Iout and Ic when we take a current measurement.  Ic is not in any way being sent to the output of the power supply and the DUT will never see this current, the DUT will only see Iout.    We wanted to provide a way that you can see the actual current that is going through the DUT so we offered the Dynamic Current Correction option in our current ranges.  

Since we are talking about a capacitor here, remember that the current through a capacitor equals the capacitance multiplied by the change in voltage over time (I = C * dv/dt).  If you are making a measurement at a DC voltage level, then there is no current through your capacitor since your dv/dt is near zero.  When you have a rapidly changing voltage waveform you can have a large dv/dt and your Ic will be a non-zero number.    A good rule of thumb would be that you want to use the dynamic current correction when you have a changing voltage and you want to turn dynamic current correction off when you have a DC voltage due to reasons that we will get into later.

In the below screenshot from my DC Power Analyzer I am operating an N6762A module set to go from 0 to 50 V with nothing connected to the output.  I do not have the Dynamic Current Correction range selected.

You can see here that the measured current goes up to 1 A even though the output is completely open therefore limiting any current flow.  That current is all flowing through the output capacitor due to the dv/dt of going from 0 to 50 V.  In this screenshot, you are seeing all Ic from the diagram above since Iout is 0.  This is not representative of the DUT current.  In this case we are going to want to use Dynamic Current Correction. 

Keeping everything set the same on the supply I turned the Dynamic Current Correction on and I measured the following waveforms:

As you can see, with Dynamic Current Correction turned on, the effect that the capacitor current has is much less noticeable. With a changing voltage, you definitely want to have this enabled.  

When Dynamic Current Correction is on, the power supply is using the capacitor equation (I= C* dv/dt) to calculate what the capacitor current is and then subtracting the calculated value out of the measured current.  This is a more accurate representation of the output current flowing through the DUT (Iout in the first picture).  There are tradeoffs though.  In some models dynamic current correction will increase the peak to peak current measurement noise and it can also limit the output measurement bandwidth.  These factors are the reason why you should turn it off when you are operating at DC voltages. 

The moral of this blog post is that you want to use the Dynamic Current Correction when you have a rapidly changing voltage and not use it when you have a static voltage.  Please let us know if you have any questions.

Power analysis of automobile self-charging emergency tool

I was recently given a “Swiss+Tech BodyGard Survivor 8-in-1 Automobile Self-Charging Emergency Tool”. How’s that for a compact name? This device does have many features, so I imagine the company had some difficulty devising a name for it. It is meant to be carried in your car and kept close enough to the driver to be used in an emergency. It contains a glass breaker, a seatbelt cutter, a flashlight, an emergency flasher and siren, an AM/FM radio, and rechargeable NiCad batteries that charge by using the self-charging hand crank. See Figure 1.

Since this device contains rechargeable batteries and Agilent makes instrumentation that can do battery drain analysis, I figured I would test the device using our equipment. I used an Agilent N6705B DC Power Analyzer loaded with an N6781A 2-Quadrant Source/Measure Unit (SMU) for Battery Drain Analysis. See Figure 2.

The product’s instruction sheet includes information about the batteries (700 mAH) and the expected battery run time when using the various features. With fully charged batteries, the expected battery run time for each of the features listed below is:

• Flashlight: 12 to 16 hours
• Flasher: 10 to 12 hours
• Radio (low volume): 35 to 40 hours
• Flasher/siren: 6 to 9 hours

Given the battery amp-hour rating (700 mAH) and the expected run time in hours, we can calculate the approximate expected average current draw for each of the various features:

• Flashlight: 700 mAH / 14 hours = 50 mA
• Flasher: 700 mAH / 11 hours = 63.6 mA
• Radio: 700 mAH / 37.5 hours = 18.7 mA
• Flasher/siren: 700 mAH / 7.5 hours = 93 mA

Using the N6781A SMU and the built-in front panel features of the N6705B DC Power Analyzer, I was able to analyzer the current drawn from the batteries when using each of the features. Each feature was used by itself with the other features turned off.

The flashlight draws a steady-state current that I read right from the front panel meter as shown in Figure 3: 50 mA. This agrees perfectly with the expected current draw I calculated. For this measurement and all subsequent current measurements, I connected the N6781A in series with the batteries and set it to Current Measure mode where it acts likes a zero-burden shunt. The measured current is negative in my setup because positive current is current flowing into the battery and with the flashlight on, current is flowing out of the battery.

For the flasher, since the current is not constant, I used the N6705B/N6781A built-in data logger feature and captured 30 seconds of data while the device was flashing. I then used the markers to measure the average current. Since the flasher flashes for a very short period of time (low duty cycle), I expected the average current to be low. When using the flasher, the expected battery run time seemed unusually short to me. At 10 to 12 hours, it is shorter than the flashlight or radio run time, which seems odd. In reality, as shown in Figure 4, the flasher drew very little current (5.6 mA), so it appears that the instruction sheet run time for the flasher is too low. With the device flashing, the battery will last much longer than indicated. In fact, the expected battery run time, when flashing, is about 700 mAH / 5.6 mA = 125 hours, 10 times longer than the time shown on the instruction sheet!

With the radio on, tuned to a station, and set to a low but audible volume, I once again used the data logger to capture the current. The markers show an average current of about 10 mA, which is less than the calculated value of 18.7 mA, but within reason. See Figure 5.

Using the flasher and siren, the data logger shows a current draw of 93 mA, in exact agreement with the expected current draw calculated from the numbers on the instruction sheet. See Figure 6.

The last current analysis I did was to capture 30 seconds of data logging when turning the self-charging crank to recharge the batteries. I purposely varied my cranking rate to see what would happen. Figure 7 shows an average of about 350 mA when turning the crank at what I considered to be a typical rate (highest average numbers on the captured data log). To fully charge 700 mAH batteries, it would take about 2 hours at that rate, which is in agreement with the instruction sheet (it says 2 to 3 hours). I don’t know about you, but I don’t want to turn that crank for 2 hours straight! Let’s hope I never have to use the tool for real, but I’m glad I have it just in case!