Well, hmmm, yes, no, perhaps - definitely maybe... I have been 'bitten' by some PTCs. Components with 60730 certification are a good place to start, but test the heck out of each individual mfr's 'equivalent' model for use in your particular box.
> -----Original Message----- > From: [email protected] [mailto:[email protected]]On Behalf > Of Greg McClure > Sent: Wednesday, November 18, 2009 9:41 AM > To: Kunde, Brian > Cc: [email protected] > Subject: Re: PTC Test Requirements > > Brian, > > You can easily avoid being concerned with the details of the > test. When you > choose the PTC for your design, make sure you pick one that > already has > component recognition/approval to IEC 60730-1. You will find > that many of > them have UL and TUV component approval already. The PTC > vendors typically > show the test mark approvals on their data sheets. You then > can request a > copy of the certificate from the PTC manufacturer to verify > that it is to > the proper version and clause(s) of the standard. > > By using the recognized component, you avoid the component > testing and > conditioning required in 60730-1. You may still have to > perform testing on > the I/O pin to prove your design meets requirements at the > connector but > that is much easier than the component level test. > > Regards, > > Gregory H. McClure > Lexmark Product Safety > 859 232 3240 office > 859 232 6882 fax - 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]>
