Re: Cable
If it isn't possible to have continuity in the aes50 ground, you should try to have chassis to chassis ground as that will take care of build-up of static potential and ground potential differences.
Hi Per,
Long time no talk. Glad to see we're both still kicking.
While chassis to chassis ground may be a nice thing ( FWIW, I still don't know what happens if the console and stage box power are on separate services with a significant ground potential difference, as in powered by services in different buildings and connected by FTP), the static potential that is the bothersome one is on people as compared to the devices and NOT what's on one device vs. the other. The devices are by definition and practice grounded, while the people float and can develop a significant charge that is discharged by touching the console, stage box, or microphone.
I can disrupt the sync when the stage box and console are two feet apart and their power cords are plugged into the same outlet but they are connected by UTP or FTP with no Ethercon. That is exactly what's shown in Brian Wynn's videos. FTP without Ethercons bonds the two devices together but still allows ESD to disrupt the sync, which disrupts the signal.
What's needed is total cable shield coverage AND continuity; continuity alone doesn't cut it.
Your other comment about fiber solving the problem is intriguing; if the snake is fiber, is it using AES50 anymore? AES50 is defined as using Ethernet cable, so I don't get it.
Another interesting aspect of this problem is that it only occurs when the stage box is used. As I type this I realize that I now have an S32 but haven't checked to see if it suffers the same problem as the S16. I'll try to do that in the next few days. It would be interesting if they solved it with the newer box, and I'll have my hopes up.
I also don't know if there is an ESD problem when the inputs are sourced from AES50 but there is no snake or stage box connected. One wouldn't use it that way, but I guess that would be one more data point.
Lastly, while we're talking, I thought of you the other day when I had a possible problem that a weird patching trick (that I think you mentioned some time ago) might have solved.
Did you post a signal diagram that somehow had a console connected to the B connector of an S-16 chain (two S-16's, first one A to a different console (Console ONE), S16B to A input of second S-16, second S-16B to second console).
Was the second console acting like a third S-16 and so providing more inputs to Console ONE? Or was there some other reason? Or did I imagine that?
As it was, I figured out another solution to solve the immediate problem, and learned today that the problem disappeared completely without the need for a solution.
Thanks,
Dan