Glad to here it.  Perhaps technical committee TC108 should consider pulling in
IEC 61010-1 into that new standard too. 

There are other examples were a merge of two or more standards makes sense,
like integrating UL1741, UL1012, UL1776, UL1236, UL1564 and UL458. 
 ______________________________________
______________________________________________ 

Ralph McDiarmid  |   Schneider Electric   |  Renewable Energies Business  |  
CANADA  |   Regulatory Engineer




From:   Richard Nute <[email protected]> 
To:     [email protected] 
Cc:     [email protected] 
List-Post: [email protected]
Date:   09/15/2010 05:00 PM 
Subject:        Re: [PSES] SV: [PSES] IEC 60950-1 vs IEC 60601-1

________________________________







> I'd like to see a generalized approach to product safety with one or two
> generic standards and not the large proliferation of standards which we
> have today.

IEC 62368-1 is a step in this direction.

Yes, safeguards against electric shock are the
same for a computer as for a toaster.  For
medical, the limits are tighter.







________________________________________________________________________
This email has been scanned for SPAM content and Viruses by the MessageLabs
Email Security System.
________________________________________________________________________


-
----------------------------------------------------------------
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
<[email protected]>

All emc-pstc postings are archived and searchable on the web at
http://www.ieeecommunities.org/emc-pstc
Graphics (in well-used formats), large files, etc. can be posted to that URL. 

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 <[email protected]>
Mike Cantwell <[email protected]> 

For policy questions, send mail to:
Jim Bacher <[email protected]>
David Heald <[email protected]> 


Reply via email to