Tuesday, September 30, 2014

How Do I Properly Wire My Output?

Hi everyone,


September has been a hectic month here at Keysight’s Power Supply Headquarters (to give you an idea of the kind of month it has been, my dog literally ate my passport a week before I left on an international trip) but I am back with another blog post for your reading pleasure.  Today we are going to talk about how to properly wire your power supply.  This is a common question.  Wiring is something that on the surface seems like it should be really easy but when you dig a little deeper there are many layers to consider.  The repercussions can be pretty severe as well.  With improper wiring, you can make a high performance power supply seem like a low performance benchtop supply.

First, let's talk about the things repercussions of improper wiring.  The first and probably most undesired result is that your voltage will be unstable.  I have seen this in my own former career as a test engineer.  The inductance from our wiring coupled with some capacitance in our test equipment resulted in an oscillation that caused a test to fail.  We spent a Saturday chasing this down and fixed it by properly wiring our system.   

The second undesired result is that your voltage rise time and fall times could be much longer than specified.  This will negatively affect your test throughput which in high volume manufacturing test could cost money due to increased test time.   Properly wiring your power supply will enable you to get the maximum throughput from your power supply.  

The last repercussion that I'll discuss is voltage overshoots and undershoots.  You want these to be as small as possible.  A large overshoot can possibly damage your DUT especially if you do not have your over voltage properly set. A voltage undershoot could cause your DUT to shut down due to a low voltage condition. 

All of these are real pains when you are trying to get your test set up and running.  There are ways to properly wire your system so you can get the maximum specs out of your power supply.  

The first and most basic wiring tip is to keep the wiring as short as possible.  The longer the wiring the higher the impedance from the wiring will be.  The table below shows some specifications on some standard wire sizes:


The second tip is to use remote sensing.  This will sense around all of the wiring drops from the wiring.  This is good practice at all times.  Remote sensing is cool.

The third tip is to twist your wires together.  The key thing to remember her is that you twist the + and - output together and the + sense and - sense together.  This will reduce the mutual inductance in the wires.  Never, ever twist the sense and output leads together.  

This is a picture of the spool of wire that we use for our sense wires here.  You can see the the wires are very tightly twisted together here:

The other option is to use special low inductance wiring.  If you look at the below picture, you can see that there are two flat conductors separated by an insulator.  This reduces the mutual inductance even more than twisting the wires.:


Our N678xA SMU DC Power Modules are very sensitive to how they are wired.  Here is a diagram showing the proper wiring for the N678xA:


The top three items I mentioned should be standard practice when you set up your system.  These are just great wiring practices.  Sometimes you need to go the extra mile.  Back when I was in the test group we followed all of these tips as best I could but due to the test system, we could not minimize the wire length enough.  Our solution was to parallel more wires between the power supply and the load that we were using.  Instead of one twisted pair, we used three twisted pairs in parallel.  This also reduces the impedance of the wiring because you are paralleling the conductors (paralleled inductance and resistance reduces).

One of our design engineers wrote a very good article that touched on this subject a bit.  You can check that out here: Article Link.  

I hope that this is useful to everyone.  Please let us know if you have any questions or comments.


Monday, September 29, 2014

Properly sequence multiple power inputs to protect your DUT

As I mentioned in a previous post, we have devoted a lot of time writing about protecting your device under test (DUT) from the two main DUT-destroying forces available from a power supply: excessive voltage and excessive current. Click here for one of the latest posts including a list to the other posts.

Today I’d like to cover another topic that can cause DUT failure due to a power supply. Some DUTs have multiple DC inputs and some of these multiple-input DUTs are sensitive to the order in which the inputs turn on or turn off. Subjecting the device to an uncontrolled sequence could cause latch-up or excessive current to flow resulting in compromised reliability or even immediate catastrophic failure of the DUT. So properly sequencing the multiple voltages at turn on and off is essential. My colleague, Ed Brorein, wrote a very similar post last year (click here) but I thought this topic was worth repeating especially since we added another series of power products with higher power that has this capability.

Various methods have been used in an effort to address the potential problem associated with improperly sequenced power inputs. Diodes can be placed from one input to another to clamp the voltage thereby preventing one input voltage from going too far above or below another input voltage but this method has limited effectiveness and variable results. Relays can be put in series with each input and controlled with timing circuitry but the relays introduce variable series impedance and timing is imprecise. FETs with associated control circuitry can be placed in series with each input however this method requires significant design time and adds complexity to the setup. Multiple DC power supplies can be controlled through software, but once again, timing is imprecise and response times can be slow.

Several years ago, I wrote an application note on a closely related topic (click here). The method that is most precise and introduces the fewest complications is to use a power supply system that has output sequencing integrated into the system itself. Keysight has several power supply systems that can accommodate precise output sequencing: the N6700 Modular Power System, N6705 DC Power Analyzer, and the more recently released N6900/N7900 Advance Power System. Each system offers the ability to precisely control the turn-on and turn-off sequence of multiple outputs. Timing is set with sub-millisecond resolution. Synchronization across systems is also possible to facilitate timed shut downs of larger numbers of power supply outputs for your DUT inputs. The above mentioned application note specifically addressed the topic of how to configure the system to properly shut down your DC inputs in sequence upon a fault generated by any of the system power supplies.

Below is a simple example of a sequenced turn on of four outputs in an N6705B mainframe. The sequencing is facilitated by setting a different turn-on delay time for each of the outputs (turn-off delays can be set independently). When all outputs are told to turn on simultaneously, the delays are activated resulting in a precisely controlled sequenced turn on. Figure 1 shows how easy it is to implement the delays for a turn-on event. In this case, I used four power supply outputs in an N6705B mainframe with delays set to 5 ms, 10 ms, 15 ms, and 20 ms. I set the output voltages to 10 V, 7.5 V, 5 V, and 3.3 V. You can also set the output voltage rise time (slew rate) independently for each output. Figure 2 shows the results using the scope that is built into the N6705B mainframe.





So you can see that with the proper power supply system, sequencing your multiple DC power supply inputs on your device to protect it from damage is easy. Keysight provides you with the solution to do just that adding to our arsenal of features that protect your valuable DUT.

Wednesday, September 17, 2014

Simulating battery contact bounce, part 1

One test commonly done during design validation of handheld battery powered devices is to evaluate their ability to withstand a short loss of battery power due to being bumped and the contacts momentarily bouncing open, and either remain operating or have sufficient time to handle a shutdown gracefully. The duration of a contact bounce can typically range anywhere from under a millisecond to up to 100 milliseconds long.

To simulate battery contact bouncing one may consider programming a voltage drop out on a reasonably fast power supply with arbitrary waveform capabilities, like several of the N675xA, N676xA, or N678xA series modules used in the N6700 series Modular DC Power System or N6705B DC Power Analyzer mainframe, shown in Figure 1. It is a simple matter to program a voltage dropout of specified duration. As an example a voltage dropout was programmed in Figure 2 on an N6781A SMU module using the companion 14585A software.



 Figure 1: N6700 series and N6705B mainframes and modules



Figure 2: Programming a voltage drop out using the N6705B and N6781A SMU module

While a voltage dropout is fine for many applications, like automotive, in many situations it does not work well for simulating battery contact bounce. The reason for this is there is one key difference to note about a voltage dropout versus a battery contact bounce. During a voltage dropout the source impedance remains low. During a battery contact bounce the source impedance is an open circuit. However, a DC source having the ability to generate a fast voltage dropout is a result of it being able to pull its output voltage down quickly. This is due to its ability to sink current as well as source current. The problem with this is, for many battery powered devices, this effectively short-circuits the battery input terminals, more than likely causing the device to instantly shut down by discharging any carry-over storage and/or disrupting the battery power management system. As one example consider a mobile device having 50 microfarads of input capacitance and draws 4 milliamps of standby current. This capacitance would provide more than adequate carryover for a 20 millisecond battery contact bounce. However, if a voltage dropout is used to simulate battery contact bounce, it immediately discharges the mobile device’s input capacitance and pulls the battery input voltage down to zero, as shown by the red voltage trace in Figure 3. The yellow trace is the corresponding current drain. Note the large peaks of current drawn that discharge and recharge the DUT’s input capacitor.



 Figure 3: Voltage dropout applied to DUT immediately pulls voltage down to zero

One effective solution for preventing the DC source from shorting out the battery input is to add a DC blocking diode in series with the battery input, so that current cannot flow back out, creating high impedance during the dropout. This is illustrated in Figure 4.


Figure 4: Blocking diode added between SMU and DUT

One thing to note here is the diode’s forward voltage drop needs to be compensated for. Usually the best way to do this just program the DC source with the additional voltage needed to offset the diode’s voltage drop. The result of this is shown in Figure 5. As shown by the red trace the voltage holds up relatively well during the contact bounce period. Because the N6781A SMU has an auxiliary voltage measurement input it is able to directly measure the voltage at the DUT, on the other side of the blocking diode, instead of the output voltage of the N6781A. As seen by the yellow current trace there is no longer a large peak of current discharging the capacitor due to the action of the blocking diode.



 Figure 5: Blocking diode prevents voltage dropout from discharging DUT 

Now you should have a much better appreciation of the differences between creating a voltage dropout and simulating battery contact bounce! And as can be seen a blocking diode is a rather effective means of simulating battery contact bounce using a voltage dropout. Stay tuned for my second part on additional ways of simulating battery contact bounce on an upcoming posting.
.


Wednesday, September 10, 2014

How do I protect my DUT against my power supply sense lines becoming disconnected, misconnected, or shorted?

The remote sense lines are a vital part of any good system power supply. As shown in Figure 1, by using a second, separate pair of leads for sensing, the output voltage is now regulated right at the DUT rather than at the output terminals on the power supply. Any voltage drops in the force leads are compensated for; assuring the highest possible voltage accuracy is achieved right at the DUT.




Figure 1: Remotely sensing and regulating output voltage at the DUT

Of course for this to work correctly the sense leads need to have a good connection at the DUT. However, what if the sense leads become disconnected, misconnected, or shorted?

One might think if one or both of the sense leads became disconnected, the sensed voltage would then become zero, causing the output voltage on the force leads to climb up out of control until the over voltage protect (OVP) trips. This turns out not to be the case, as a co-contributor here, Gary had pointed out in a previous posting “What happens if remote sense leads open?” (Click here to review). Basically a passive protection mechanism called sense protect maintains a backup connection between the sense line and corresponding output terminal inside the power supply in the event of a sense line becoming disconnected.

While sense protect is an indispensable feature to help protect your DUT by preventing runaway over-voltage, if a sense lead is open the voltage at your DUT is still not as accurate as it should be due to uncompensated voltage drops in the force leads. This can lead to miscalibrated DUTs and you would not even know that it is happening. To address this some system power supplies include an active open sense lead fault detection system. As one example our 663xx Mobile Communications DC Sources check the sense lead connections during each output enable and will issue a fault protect and shut down the output if one or both sense leads become disconnected. It will also let you know which of the sense leads are disconnected. It can be enabled and disabled as needed. I had written about this in a previous posting “Open sense lead detection, additional protection for remote voltage sensing” (Click here to review).

Taking sense protection further, we have incorporated a system we refer to as sense fault detect (SFD) in our N6900A and N7900A Advanced Power System (APS). It can be enabled or disabled. When enabled it continually monitors the sense lead connections at all times. If it detects a sense fault it sets a corresponding bit in the questionable status group register as well as turn on status annunciator on the front panel to alert the user, but does not disable the output. Through the expression signal routing system a “smart trigger” can be configured as shown in Figure 2 to provide a protect shutdown on the event of a sense fault detection.  In all, sense fault detect on APS provides a higher level of protection and flexibility.




Figure 2: Configuring a custom opens sense fault protect on the N6900/N7900 APS

What happens if the sense leads become shorted? Unlike open sense leads, in this case the output voltage can rise uncontrolled. The safeguard for this relies on the over voltage protect system. The same thing happens if the sense leads are reversed. The power supply will think the output voltage is too low and keep increasing the output voltage in an attempt to correct it. Again the safeguard for this relies on the over voltage protect system. The N6900/N7900 APS does actually distinguish the difference when the sense leads are reversed by generating a negative OVP (OV-) fault, giving the user more insight on what the fault is to better help in rectifying the problem.

Remote voltage sensing provides a great benefit by being able to accurately control the voltage right at the DUT. Along with the appropriate safeguards against sense lead misconnections you get all the benefit without any of the corresponding risks!

Remote sense protect and sense fault detect were just two of many topics about in my seminar “Protect your device against power related damage during test” I gave last month. As it was recorded it is available on demand if you have interest in learning more about this topic. You can access the sign up from the following link: (Click here for description and to register)