Showing posts with label inrush current. Show all posts
Showing posts with label inrush current. Show all posts

Monday, March 23, 2015

Use slew rate control to cleanly power up and reduce peak inrush current of your DUTs

Previously on Watt’s Up? a colleague wrote about how the current limit setting affects a power supply’s voltage response time (click here to review). In this posting he clearly shows how a low current limit setting can greatly slow down the output voltage turn on response time when powering up your DUT.

While this is generally true and good advice, especially for basic performance power supplies, there are additional things to consider when working with high performance power supplies models, as you will see.

Many basic performance power supplies tend to have larger output filter capacitors in order to achieve lower output noise performance. A disadvantage of having a large output capacitor is that it slows down the output voltage response speed of the power supply. Basic performance power supplies can have turn on response times on the order of a 100 milliseconds.

High performance power supplies operate by a somewhat different set of rules. In comparison to basic performance power supplies they typically have much smaller output capacitors and they are designed to have output turn on and turn off response times on the order of a millisecond or less.

However, absolute fastest is not always the best and that is why fast, high performance power supplies also usually incorporate an output voltage slew rate control as well. This allows you to optimize the output turn on and turn off speed for your particular application. This lets you take advantage of the faster output speed you have available, without it being overkill and cause other problems.

The two most common problems that arise when powering up and powering down many DUTs are related to charging and discharging the input filter capacitor incorporated into them. They are:
  • High peak inrush (and discharge) currents due to the high dV/dt slew rate being applied
  • Power supply CC-CV mode cross over issues resulting from the high peak inrush current


To illustrate, the turn on characteristic of our N6762A power supply was captured when powering up a load consisting of a 1,200 microfarad capacitor in parallel with a 10 ohm resistor. The N6762A was set to 10 volts and its voltage slew rate set to maximum.  This was captured using the N6762A’s digitizing voltage and current readback together with the 14585A software, shown in Figure 1.
  


Figure 1: N6762A power supply turn on response set to maximum slew rate into parallel RC load

The vertical markers have been placed at zero and maximum voltage points of the turn on ramp. The peak inrush current reaches 3.7 amps and the peak voltage overshoots to 11.06 volts, 10% over the 10 volt setting. The overshoot is a result of the power supply crossing over into current limit during the ramp up and allowing the voltage to rise to 11.06 volts before the voltage control loop regains control to bring the output back down to 10 volts. It also takes a little while for the voltage to settle after the peak overshoot. Both the overshoot voltage and peak inrush current can be problems when powering up a DUT. These occur as a result of having too fast of a voltage slew rate when powering the DUT.

To address the problem we then set the N6762A’s slew rate to a more acceptable value of 2,000 volts/second. The turn on voltage and current were again captured and are shown in Figure 2. As can be seen the voltage overshoot is eliminated and the inrush current has been reduced to a more moderate 3.3 amps.


Figure 2: N6762A power supply turn on response set to 2,000 V/s slew rate into parallel RC load

So in closing high performance power supplies have a significant advantage in their output response speed, in comparison to basic power supplies. And while faster is usually better, absolute fastest may not be best, and this applies to the output response time of power supplies as well! But by having the ability to set the output slew rate on high performance power supplies gives you the ability to optimize its speed for your given application, providing for the best possible outcome possible!

.

Friday, December 12, 2014

Why Does Over Current Protect (OCP) have a Programmable Delay Value in the First Place?

Since I am on a roll about over current protect (OCP), having just completed a two-part posting “Why does the response time of OCP vary on the power supply I am using and what can I do about it?” (Review part 1) (Review part 2) there is yet another aspect about OCP that is worth bringing up at this time. And that is “why does OCP have a programmable delay value in the first place?” This actually came up in a discussion with a colleague here after having read my part posting.

It may seem a bit ironic that OCP has a programmable delay in that in my posting on OCP I shared ideas on how one can minimize the response time delay encountered. But this is not contradictory. One may very well want to minimize it, eliminating extra delay being encountered, but not necessarily eliminate it altogether. As can be seen in my previous postings, I had programmed the OCP delay time to 5 ms.

The programmable OCP delay does serve a purpose, and that is to prevent false OCP trips. Adding some delay time prevents these false trips.  For someone who knows the root cause of false OCP tripping they might be half right. There are actually been two main causes of false OCP trips which are prevented by adding some delay time.

The original problem with OCP was that it would be falsely tripped when output voltage settings were changed on the power supply, due to capacitive loading at the test fixture or within the DUT. This is especially prominent with inrush current when first bringing up the voltage to power the DUT. An OCP delay prevents false triggering under these conditions. To correct the false tripping the delay would be invoked when output programming changes were made. As one example, the OCP delay description in our manual for our 663x series power supplies states:

This command sets the time between the programming of an output change that produces a constant
current condition (CC) and the recording of that condition by the Operation Status Condition register. The
delay prevents the momentary changes in status that can occur during reprogramming from being
registered as events by the status subsystem. Since the constant current condition is used to trigger
overcurrent protection (OCP), this command also delays OCP.”

Under this situation the momentary overcurrent is induced by the power supply. Although not nearly as much as in issue in practice, momentary overcurrents can also be DUT-induced as well. This is the second situation that can cause a false tripping of the OCP. The DUT may be independently turned on after the bias voltage has already been on and draw a surge of current. Or the DUT may change mode of operation and draw a temporary surge of current.  If the OCP delay is invoked only by an output programming change it does not have any effect in these situations.

On later generation products, such as our N6700, N6900, and N7900 series, the user also has the ability to programmatically select between having the OCP delay activate from either an output change, or from going into CC condition. This gives the user a way to remain consistent with original operation or have OCP delay effective for momentary DUT-induced overload currents as well!


Monday, June 30, 2014

Doing Inrush Current Testing with the New AC6800 AC Sources

Hi everybody,

It is the last day of the month and therefore time for me to get my blog post out.  I want to build on Gary's latest post concerning the new Agilent/Keysight AC6800 AC Sources (Click Here).  One of the key features that Gary mentioned is inrush current testing.

My colleague Russ did a video on inrush current testing for the launch.  This gives you a little bit of perspective on why you want to do the testing and gives some good tips.


When you do inrush current testing, you typically want the highest value that the current has reached when the power is enabled.  The AC6800 has a peak hold current value that will store this value for you.  The unit stores the highest current value it has measured since that value was last cleared (either manually or from power on).  One key thing to remember is to always clear out the peak hold value before doing your measurement so that you know that your measurement is up to date.

The AC6800 can synchronize the enabling of the output to a user defined phase.  When you specify the phase, it will enable the output at that phase in the sine wave (anything from 0 to 360 degrees).  The combination of the peak hold measurement and this phase synchronization are what make this testing possible.  

I  did a video for the launch where I did a tour of the front panel, including a short description of how to do inrush current testing:

  



I also have a programming example on this topic.  Below is a snippet of a program that I wrote in VB.NET using Agilent VISA-COM:


That's about it for me this month.  Please let us know if you have any questions in the comments.  




Friday, January 24, 2014

Using Binary Data Transfers to Improve Your Test Throughput

From time to time I have shared here on “Watt’s Up?” a number of different ways the system DC power supply in your test set up impacts your test time, and recommendations on how to make significant improvements in the test throughput. Many of these previous posts are based on the first five of ten hints I’ve put together in a compendium entitled “10 Hints on Improving Throughput with your Power Supply” (click here for hints 1-5).

Oscilloscopes, data acquisition, and a variety of other test equipment are often used to capture and digitize waveforms and store large arrays of data during test, the data is then downloaded to a PC. These data arrays can be quite large, from thousands to millions of measurements. For long-term data logging the data files can be many gigabytes in size. These data files can take considerable time to transfer over an instrument bus, greatly impacting your test time.

Advanced system power supplies incorporating digitizing measurement systems to capture waveform measurements like inrush current are no different. This includes a number of system DC and AC power products we provide. Even though you usually have the choice of transferring data in ASCII format, one thing we recommend is instead transfer data in binary format. Binary data transmission requires fewer bytes reducing transfer time by a factor of two or more.


Further details about using binary mode data transfers can be found in hint 7 of another, earlier compendium we did, entitled “10 hints for using your power supply to decrease test time” (click here to access). Between these two compendiums of hints for improving your test throughput I expect you should be able find a few different ideas that will benefit your particular test situation!

Tuesday, April 30, 2013

How do I measure inrush current with an Agilent DC Power Supply?

Hello everybody! I want to build on my blog post from last month.  This month, we are going to discuss how to measure inrush current using the DC Power Analyzer’s scope function as well as the digitizer feature that is available on some of our system power supplies.

Measuring inrush current is a task that many customers that use DC Power Supplies want to accomplish.  When you are doing this test on the bench, the N6705B DC Power Analyzer (DCPA) is your best bet.  The DCPA has the scope feature which makes this a breeze.  One of the great things about Agilent power supplies is that they can measure current directly, without the need for a current probe. Some of our supplies have very high current measurement accuracy as well so you can get an accurate representation of your current.

In the below screenshot, I just had a capacitor connected to the output of the supply.  I set a voltage arbitrary waveform that went from 0 V to 20 V with the voltage slew set for the maximum.  I set the scope to trigger on the Arb run/stop key so that when I hit the key, both the arbitrary waveform and the scope triggered.  After I acquired the waveform, I used the markers to get the maximum current.  That number is our inrush current.   


As I said earlier, DCPA is geared towards bench use.   The graphical scope makes this task pretty easy.  Many of our system supplies (as well as the DCPA) have a digitizer feature that you can access using the SCPI programming interface.  The digitizer will sample the output using settings that you provide it.  These settings are: the number of points, the time interval between points, and the number of pretrigger points that you acquire.  In the N678xA SMU modules, the time interval is as low as 5.12 us and the number of points is as high as 512kpoints.  Here is a list of commands to set up the digitizer (written for the N67xx supplies) as well as some comments.

Set the digitizer to measure current:
 SENS:FUNC:CURR ON,(@1)

Set the number of pretrigger points, a negative value represents points taken before the trigger:
SENS:SWE:OFFS:POIN -100,(@1)

Set the total number of points to acquire:
SENS:SWE:POIN 5000,(@1)

Set the time interval between points:
SENS:SWE:TINT 0.000020,(@1)

Set the measurement trigger source to bus:
TRIG:ACQ:SOUR BUS,(@1)

 Initiate the measurement trigger system
INIT:ACQ (@1)

Send a trigger:
*TRG

Using this code, once the trigger is sent, the measurement system will acquire 5000 points at a time interval of 20 us while taking 100 pretrigger points. 

After the measurement occurs, you read the current back using:
FETC:ARR:CURR? (@1)

Once you have the array of current measurements, you can do any normal calculation that you can do on any array.  To measure inrush, you want to find the maximum current in the array.  This peak will be your inrush current.  I wrote a program that followed the exact same steps that I used on the scope above (setting up a step that went from 0 to 20 V and synchronizing triggers) and measured a maximum of 1.07748 A.  As you can see, I got a similar result from the two different approaches.

That is all that I have this month.  I hope that it is useful information.  If you have any questions at all please feel free to ask them in our comments.