The current GFCI standards now require automatic built in self-test since it’s likely the majority of the older ones were not being manually tested. I don’t know about GFEP. From: Mike Sherman ----- Original Message ----- [mailto:[email protected]] Sent: Thursday, February 16, 2017 11:09 AM To: [email protected] Subject: Re: [PSES] Questions on GFCI & GFEP
Another thing: these are typically "shunt trip" products, which leads to periodic testing to verify that they are still functional. Sent from Xfinity Connect Mobile App ------ Original Message ------ From: Vincent Lee To: [email protected]<mailto:[email protected]> Sent: February 15, 2017 at 8:49 PM Subject: [PSES] Questions on GFCI & GFEP Hi all, Good evening, May I know what are the difference between Ground Fault Current Interrupter (GFCI) and Ground Fault Equipment Protector (GFEP) in terms of safety features (e.g. response time, trip current), usage and operation principle? What are the common industry standards for GFCI and GFEP ? Is there any requirement to maintain, calibrate and check for operation for GFCI and GFEP? Hope to hear from you soon. Thank you very much. Vincent - ---------------------------------------------------------------- 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]<mailto:[email protected]>> 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://www.ieee-pses.org/list.html (including how to unsubscribe)<http://www.ieee-pses.org/list.html> List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the list administrators: Scott Douglas <[email protected]<mailto:[email protected]>> Mike Cantwell <[email protected]<mailto:[email protected]>> For policy questions, send mail to: Jim Bacher <[email protected]<mailto:[email protected]>> David Heald <[email protected]<mailto:[email protected]>> - ---------------------------------------------------------------- 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]<mailto:[email protected]>> 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://www.ieee-pses.org/list.html (including how to unsubscribe)<http://www.ieee-pses.org/list.html> List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the list administrators: Scott Douglas <[email protected]<mailto:[email protected]>> Mike Cantwell <[email protected]<mailto:[email protected]>> For policy questions, send mail to: Jim Bacher <[email protected]<mailto:[email protected]>> David Heald <[email protected]<mailto:[email protected]>> - ---------------------------------------------------------------- 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.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://www.ieee-pses.org/list.html (including how to unsubscribe) 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]>
