Electrostatic Discharge
Jul 15,2007 00:00 by admin

Electrostatic Discharge

10.1 INTRODUCTION

This chapter reviews the problem of electrostatic discharge (ESD) as it affects wireless sensor network nodes, and the importance of proper electrical, mechanical, and product design in its control. Similar to electromagnetic compatibility (EMC) problems, ESD problems often require a multi-disciplinary approach for proper resolution. Unlike most EMC problems, however, ESD problems can be difficult to identify in the field; often, the first indication of an ESD weakness in a design are sporadic reports of "dead" nodes not attributable to other causes, or reports of very specific failure types, such as corruption of certain register contents in a microcontroller. ESD problems are difficult enough to detect in wireless sensor networks designed for consumer and home automation applications, where an ESD event may be instigated by a charged individual, but become even more troublesome in networks for industrial, agricultural, and military applications, many of which operate essentially autonomously, without direct human contact. Lack of human contact may lower the overall failure rate. but can result in a lack of information on the failures that do occur. It is important, therefore, to understand the ESD problem, so that it may be "designed out" of the finished product.

THE PROBLEM

10.2.1 Examples

Most people are familiar with static electric discharges on cold winter days or other especially dry conditions. These discharges, although only unpleasant to humans, may be fatal to modern electronic products; further, weak discharges that are undetectable to humans can still damage electronic products.[1] What follows is a selection of ESD-related events associated with consumer electronic products, illustrating the importance of the problem and the variety of guises in which it may appear.

Now, after a discharge to the serial port contacts, the product's real time clock (RTC) appeared to stop — but the product would continue to work normally in every other way. It was found that the microcontroller had two programming bits that controlled the RTC increment rate. The RTC could be set to increment either once per second, once per minute, once per hour, or to not increment at all. The ESD event was somehow corrupting these bits so that the RTC would not increment, and, therefore, appear to stop. Working with the designers of the microcontroller, the product engineer assigned to this problem determined that the RTC was supplied power through a particular supply pin, the Vrr pin. A 150-Ω resistor in series with the Vrr pin (made possible due to the very low current drain of the RTC) fixed it. To speed testing, special product firmware was written during this part of the investigation that constantly checked the value of the sensitive bits. If a change were noted, a light-emitting diode (LED) on the product would turn on.

10.2.2 Failure Modes

Product failures resulting from ESD events may take many forms. They can, however, be placed into two general categories, long-term and short-term failures, depending on the time scale of the failure. Short-term failures are generally found immediately after the ESD event. Long-term failures take time, perhaps even months or years, to become apparent.

[1]Steven H. Voldman, Lightning rods for nanoelectronics, Scientific American, v. 287, n. 4, October 2002, pp. 90–97.

[2]Owen J. McAteer, Electrostatic Discharge Control. Upper Falls, MD: MAC Services Incorporated. Available from the Electrostatic Discharge Association, Rome, NY. 1990. Chapter 11.

[3]Yogi Anand and Dana Crowe, Latent ESD failures in Schottky barrier diodes, Proc. Electrical Overstress/Electrostatic Discharge Symp., 1999, pp. 160–167.



eXTReMe Tracker