ProSoundWeb Community

Please login or register.

Login with username, password and session length
Advanced search  

Pages: 1 2 [3]  All   Go Down

Author Topic: GFI's Tripping  (Read 8218 times)

Jean-Pierre Coetzee

  • Classic LAB
  • Hero Member
  • *
  • Offline Offline
  • Posts: 862
  • Gauteng, South Africa
Re: GFI's Tripping
« Reply #20 on: November 02, 2017, 04:34:38 AM »

I'll point out that this may not be an accurate test. If there is leakage, and the equipment is interconnected with other equipment or if the chassis is grounded by other means (such as being in contact with structural steel), then some of the leakage current may find a path to ground other than through the equipment grounding conductor.

For an accurate test, disconnect any audio leads from the equipment and insulate the device from incidental grounding.

(Leakage is a common source of "ground loop hum.")
I believe this is what Mike implied.

Sent from my 2014817 using Tapatalk

Logged
Audio Technician
Word & Life Church

"If you want "loud", then run a piece of sheet metal through a table saw------

If you want "watts"-then plug in a toaster"
- Ivan Beaver

Mike Sokol

  • Moderator
  • Hero Member
  • *****
  • Offline Offline
  • Posts: 3361
  • Lead instructor for the No~Shock~Zone
    • No~Shock~Zone Electrical Safety
Re: GFI's Tripping
« Reply #21 on: November 02, 2017, 08:31:02 AM »

I believe this is what Mike implied.

Yes, do this on the bench disconnected from all other gear. That's the only way to get an accurate reading. Another aspect of this to consider is that some brand GFCI's may be more sensitive to high-frequency ground leakage from switching power supplies. A standard meter won't be able to measure those high-frequency currents, but any good o'scope measuring across a series resistor should be able to discover that sort of leakage.

ProSoundWeb Community

Re: GFI's Tripping
« Reply #21 on: November 02, 2017, 08:31:02 AM »


Pages: 1 2 [3]  All   Go Up
 



Site Hosted By Ashdown Technologies, Inc.

Page created in 0.034 seconds with 25 queries.