Steve,

Thanks a lot for the very nice hierarchy description below. 

If there's a 10 mil or less spacing between pwr and gnd planes, the plane cap 
is available. The plane cap and the decaps are complementary in whole frequency 
range. Plane cap takes care of high end, and decaps cover low portion. Then the 
location of decaps are not critical. And then decaps can be shared by other 
chips, according to the excellent research conducted by EMC lab at UMR. 

Please allow me to modify a bit your description as follows.   

The capacitance inside the device supports the chip first, but usually not 
enough.
Charge from the planes also supports the chip and replenishes the device 
capacitance,
Decaps replenish the plane on low frequency portion, while plane cap responds 
itself on HF end,
Bulk capacitors replenish decaps and plane cap,
The voltage regulator replenishes the bulk capacitors.

Please correct me. Thanks.

Regards,
Barry
[email protected]
-----------------
From: "sweir" <[email protected]>, on 5/11/00 9:28 PM:
....

The capacitance inside the device supports the chip,
Charge from the planes replenishes the device capacitance,
HF capacitors on the board replenish the planes,
Bulk capacitors replenish the HF capacitors,
The voltage regulator replenishes the bulk capacitors.

....[edited by bm]


_______________________________________________________________________

Why pay when you don't have to? Get AltaVista Free Internet Access now! 
http://jump.altavista.com/freeaccess4.go

_______________________________________________________________________


-------------------------------------------
This message is from the IEEE EMC Society Product Safety
Technical Committee emc-pstc discussion list.

To cancel your subscription, send mail to:
     [email protected]
with the single line:
     unsubscribe emc-pstc

For help, send mail to the list administrators:
     Jim Bacher:              [email protected]
     Michael Garretson:        [email protected]

For policy questions, send mail to:
     Richard Nute:           [email protected]

Reply via email to