Our company makes a 230VAC product (laboratory/light industrial) that has a water connection. We received word from a customer in Tennessee, USA, who says the NEC and/or the Tennessee Electric Code requires a GFCI be used with this product. We are not experts in the NEC so can anyone confirm this to be true? We did not know GFCI were required for non-consumer products.
Our product uses a Frequency Drive to speed control a 2hp motor. EMI from the drive causes false trips in the GFCI. On a similar 115VAC product we found GFCI based on the 2006 requirements worked just fine as was immune to the EMI caused by a Frequency Drive, but we cannot find such a reference on 230VAC GFCI. Can anyone suggest a 230VAC 2 pole GFCI that is immune to EMI from Frequency Drives? Does the NEC allow for an alternative for a GFCI such as adding a secondary earthed ground bonding conductor or wiring the power cord direct? Thank you all for your help. The Other Brian ________________________________ LECO Corporation Notice: This communication may contain confidential information intended for the named recipient(s) only. If you received this by mistake, please destroy it and notify us of the error. Thank you. - ---------------------------------------------------------------- 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://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]>
