Highlighted
Contributor - Level 3

S16 catastrophic fault

We recently came in the the building for a training night. On switching the system on, one of the guys realised that the S16 had not been powered up. When he powered it up, instead of the usual click that you get when you power up in the wrong order, the system emitted a very loud continuous shriek: he immediately hit the power switch, but the shriek blew all the FOH top end speakers.
Once we assessed the damage we tried to recreate the fault and the same problem re-occurred, even with the desk fully muted!! Since then we have not had a problem and we can't get the error to repeat itself. It was apparently just a one-off (or rather a two-off)

Does anyone know how this could happen and what we have to do to stop it destroying the repaired speakers. The help desk very helpfully told us the equipment was out of warranty, full stop.

History: About three months ago there was a lightning strike nearby and the S16 AES50 card stopped working. We asked Behringer to repair it and it was put back into service. The repaired S16 worked perfectly for about three months, except that it would not handshake and sync unless it was switched on before the X32. We got into the habit of making sure it was switch on first, and didn't think about it very much. It just seemed to be working again.
--------------- Neil Millward Church Tech, Scotland
NeilMillward Contributor - Level 3 2017-01-08

2017-01-08

S16 catastrophic fault

We recently came in the the building for a training night. On switching the system on, one of the guys realised that the S16 had not been powered up. When he powered it up, instead of the usual click that you get when you power up in the wrong order, the system emitted a very loud continuous shriek: he immediately hit the power switch, but the shriek blew all the FOH top end speakers.
Once we assessed the damage we tried to recreate the fault and the same problem re-occurred, even with the desk fully muted!! Since then we have not had a problem and we can't get the error to repeat itself. It was apparently just a one-off (or rather a two-off)

Does anyone know how this could happen and what we have to do to stop it destroying the repaired speakers. The help desk very helpfully told us the equipment was out of warranty, full stop.

History: About three months ago there was a lightning strike nearby and the S16 AES50 card stopped working. We asked Behringer to repair it and it was put back into service. The repaired S16 worked perfectly for about three months, except that it would not handshake and sync unless it was switched on before the X32. We got into the habit of making sure it was switch on first, and didn't think about it very much. It just seemed to be working again.

Contributor - Level 3

Re: S16 catastrophic fault

Maybe it was some sort of Sample Clock feedback loop with both S16 and X32 trying to take control of the clock signal. Smiley Sad Whatever it sounds like the S16 is still rather sick unfortunately. I would write it off as an insurance loss if you are covered and get a new replacement. Or is lightning counted as an Act of God and not covered?