In message <d250d01e39356a4e9cc3b4b459d6655094d97...@ms-cda-01.advanced-input.com>, dated Fri, 7 Dec 2012, "McInturff, Gary" <gary.mcintu...@esterline.com> writes:

The counter example, maybe. Is a monitor we built some years ago was at the start of a fire. Evaluation quickly showed that the monitor was not the source but rather a bank teller full of Christmas spirit had lit a candle next to the monitor and didn't blow it out before going home. Somewhere along the line the candle flame was in contact with the monitor - 94V0 - eventually caught fire and the ignition source remained in contact so that the fire spread far enough to ignite some paper on the monitor etc. Ultimately the legal beagles didn't care it was cheaper to settle than to litigate so the claim was paid. But maybe in retrospect it also keep us out of the media rightly or wrongly.

That decision might have contributed to the jillion dollars spent on whether to include 'candle flame ignition' in IEC 60065 and IEC 60950-1.
--
OOO - Own Opinions Only. See www.jmwa.demon.co.uk
The longer it takes to make a point, the more obtuse it proves to be.
John Woodgate, J M Woodgate and Associates, Rayleigh, Essex UK

-
----------------------------------------------------------------
This message is from the IEEE Product Safety Engineering Society emc-pstc discussion 
list. To post a message to the list, send your e-mail to <emc-p...@ieee.org>

All emc-pstc postings are archived and searchable on the web at:
http://www.ieee-pses.org/emc-pstc.html

Attachments are not permitted but the IEEE PSES Online Communities site at 
http://product-compliance.oc.ieee.org/ can be used for graphics (in well-used 
formats), large files, etc.

Website:  http://www.ieee-pses.org/
Instructions:  http://listserv.ieee.org/request/user-guide.html
List rules: http://www.ieee-pses.org/listrules.html

For help, send mail to the list administrators:
Scott Douglas <emcp...@radiusnorth.net>
Mike Cantwell <mcantw...@ieee.org>

For policy questions, send mail to:
Jim Bacher:  <j.bac...@ieee.org>
David Heald: <dhe...@gmail.com>

Reply via email to