Good catch, but I'd be very concerned about why a cable shield that is supposedly grounded at one end has enough AC on it to give a nasty shock. You have to wonder about the technical prowess of those who initially designed/installed/tested the system.
Years back I was fighting a problem with the waveshape from a T1 interface. It turned out the whover wired that telephone central office used 72 ohm twisted pair instead of the proper 100 ohm cable.
I am amazed that anybody would use BNC connectors for an audio input on a remoted transmitter. My guess is that the transmitters were not designed to be remoted like that. Transformer coupling, balanced or not, with an electrostatic shield between primary and secondary, was definitely the correct fix.
OF course, it would have been valuable to figure out why there was 90 volts AC between the two grounds. I can immagine several explanations, though.
And of course there is always the burden of believing that the system functioned correctly at some time. Unfortunately, not everything that is built is designed, and not everything that is designed is designed correctly. So sometimes there are problems like this.
Yes, it was definately a band-aid moment. The solution would have been to redesign the audio output and input stages of the communications gear to use isolated and balanced audio at both ends. The equipment rack and consoles were separated by 6 floors. I admit that the AC Safety ground for the building wasn't up to the challenge, or that there was some other piece of equipment that at causing the problem of a high difference in the ground potential.
But all of that aside, the real problem was a crap design using unbalanced audio extended over several floors which would have caused problems no matter what. The equipment manufacturer, C----ns, should have known much better.
The isolation transformers where mounted on a piece of plexiglas and had a cover and warnings on it identifying the problem. This didn't exist prior to the band-aid moment.
I would have thought that over the 15 year period that this problem existed that someone would have corrected the problem on such a critical service much earlier.
I have often thought about how much the government would have spent over the 15 years that they tried to resolve this problem. Of course, I was never told, but I did catch heck for being $5.00 over what I had estimated the repair cost would be! It's been 35 years since I have worked there. I wished I did know...
I'd been playing with electronics since I was a child, and at this point, troubleshooting had become almost instinctive. What had amased me at the time was that no one realised where the problem lay! It was pretty obvious where the problem was coming from.
One thing that I have noticed is that when trouble shooting equipment, people tend to think that the installation was working at some point. If everything that was checked is as it should be, it's usually the thing that no one has checked that's causing the problem!
Yes, Naperlou, the trick for Clint's success may have been that he didn't know what was attempted earlier. Like you, I'd like to know what that was. Clint will be checking in on these comments, so we may get the rest of the story.
Clint, what a great story. You took a disciplined approach without preconceptions. You questioned the selection of the cable and tracked down the issue. I just wonder what was done before to address the issue. Sometimes it pays to take a new approach without knowing what was done before.
For industrial control applications, or even a simple assembly line, that machine can go almost 24/7 without a break. But what happens when the task is a little more complex? That’s where the “smart” machine would come in. The smart machine is one that has some simple (or complex in some cases) processing capability to be able to adapt to changing conditions. Such machines are suited for a host of applications, including automotive, aerospace, defense, medical, computers and electronics, telecommunications, consumer goods, and so on. This discussion will examine what’s possible with smart machines, and what tradeoffs need to be made to implement such a solution.