Just last night I had an issue with my AB168 linked to my QU16.
Basically the sound comes through but you can not adjust the gain or add phantom power.
The outputs kept working fine, but we had to re-route all inputs through an analogue cable.
We had a power issue just before, not directly involving the mixer or the stage rack, but on the same electric system. This issue caused our main breaker to jump and the only consequent issue seemed to be this loss of control.
I just tested it with both my QU-16 mixers, and the issue remains.
Is there somthing I’m doing wrong, or should I just take it to my distributor for analysis?
We have an identical problem with a brand new AB168 and a QU-24.
Other dSnake boxes work fine and we’ve tried all sorts of cables, but no control of gain, pad or Phantom on AB168 switched inputs, making the stagebox essentially unusable.
Audio passes perfectly well in both directions and both devices seeing each other. Everything normal on QU-24 local inputs but as soon as you yellow light the inputs to dSnake, the desk shows gain and phantom power changes, but nothing happens on the stagebox.
We did a firmware upgrade to latest version on the QU-24.
Before we raise the issue with tech support, anyone with ideas please step forward!
It’s just the second day I start using my new AB168. I have to move everything to the stage so we can connect analog. I don’t think it has anything to do with CAT5e cable or power. The AB168 stays in this problem forever, no way to recover.
If you have identical symptoms to ours above, it sounds like a Comms Board failure on the new AB168 and you should raise a Technical Support Ticket with A&H and refer back to your Supplier immediately.
Simple AB168 internal Comms Card swap-out by A&H Service Distributors solved the problem, following quick and accurate remote diagnosis under Warranty Ticket. All working fine at present.
Should therefore be a quick fix, but has to go back to Service Centre.
Argh, just happened to me on my 3rd time out with my AB168+Qu-24. Swapped out Ethernet cable, rebooted everything. Brought everything home and reset the firmware, as everyone above, but to no avail. Used the
ab168 for outputs, which worked fine, but had to create a 16 line snake with lots of connected XLR cables. Had exactly 1 left in the hamper when all connected. Fortunately got to the gig 4 hours early or this would have been really bad. I have a couple weeks before the next show when the ab168 is essential, but really never want to have this happen again. I use the AB168 plugged into a Furman, so it not have seen any spikes at any time. Odd that it doesn’t have an on/off switch though, as turning things on/off via plugging is often a bit dicey. And, of more concern, is the replacement board also likely to fail at some point in the future or is this now a fixed problem? Never want to have to do that again.
Mine is still in repair, but I also fear it would happen again. Anyway, I really think A&H should compensate some of the loss we suffered due this design/manufacture problem. As a $1400 snake box, it is not suppose to have this kind of problem. I’d rather spend less money and get a more reliable AR2412 now.
I have a theory folks. Ever plug/unplug the ethernet cable while the ab168 is on? Makes noises, acts funny,etc. I have a feeling there is no protection circuit on the ethernet card - which is unusual any time after 1996, but possible. I plan to ONLY connect the unit while the unit is powered off as a precaution. My dealer graciously got me a replacement immediately, so I, at least, am back in business.
I don’t think that is the reason. Being digital, when you plug and unplug the ethernet cable, there is no noise or anything like that. Glad you got a replacement so quickly, let us know if it is working properly over time.
It appears Allen & Heath is aware of this and they are - to their credit - working on a solution for me. Current theory seems to be that some ab168s revert to an older version of the firmware on some connections to some Qu series mixers some of the time. Connecting to a GLD re-updates the firmware and problem solved. I suspect there will eventually be a newer firmware version that prevents the reversal. Not sure how that will get applied at sites that don’t have GLDs, but if the GLD can update the firmware, there have to be other means as well. Hang in there and contact your sales rep or the company if you experience this. They want to get this solved as well. Fortunately, it seems to be rare.
Hmmm. Not sure about that? Our problem was definitely confirmed as a hardware failure requiring a board swap. No mention of a firmware incompatibility issue, which is concerning.
A similar issue happened for us on March 20th 2015.
The AB168 worked perfectly at the home studio. We took it to the show, set it up and the QU16 desk could not “see” any of the active 12 inputs. We tried the back up Ethernet cable, (roughly) 40 feet, and nothing. The “ready” light would not go on.
I was able to play back 16 track recording through the unit from the QDrive through the box though. Just no signal from the stage. Nada.
With 60 minutes prior to show time, we made the decision to relocate the QU16 to the stage and manage sound via the Ipad App, learning this on the fly.
When the unit came home, I tried to recreate the issue, using the same preset scene with all the appropriate inputs, and it worked fine.
I am a little suspicious that the unit was plugged into a power bar, whereas before, it has always been plugged into mains. That is the only change I can think of.
At the price paid, the unit needs to be bulletproof and the band needs to have confidence that the equipment will work. It is NO FUN having to change a stage 60 minutes prior to a gig.
This sounds a little bit different than what we experienced. The problem we had is lost of preamp control permanently, but the outputs are OK since they are line level.
Hawk is right… Your problem is indeed a little different than the one we’ve been experiencing.
If you had no “Ready” light, and had no input signals from the stagebox whatsoever, you had more of a connection failure. Conversely, we had the green light, and had some input signal flowing, we just couldn’t control it!
I wonder, did you have the flashing yellow LED adjacent to the Cat5 socket on the stagebox?
I have 2x SB168 units which were purchased from a famous retailer in Germany. I have a QU32 and ran the unit at an event with no issue. Unfortunately, the second time we used the unit it started sending loud bangs down the PA with a phantom power bang down the first 16 channels on the desk. Then we lost all signal from and to the stage box which came back on after around 10-12 seconds. This happened around 8 times in 2 hours. In the end I had to run an analogue multicore to the stage and remove the unit.
I was advised that it may be my cat5e cable that was causing the fault and that I had not fully unwound my 75m roll so put it down to this. After then checking with shorter cables, the fault was still present. I ordered another SB168 from the same supplier and this unit has been perfect with no faults and using the same cables so I know that it is the unit.
I returned the unit to the supplier who honoured their warranty agreement and collected/returned the unit for no charge. I included a not with the SB168 explaining the full fault and that the unit needs to be powered for around 3 hours before a fault is found. By this time I had noticed that if the unit is on and I gently touch the the cat5e cable going into the SB168 that connection is lost and after 10-12 seconds it will re-connect. When the unit was returned I was informed that it was a “firmware problem” and that it had now been updated and all is fine.
Unfortunately it failed on the next event but this was for around 700 people with a major tribute band performing. I have contacted the supplier again who have agreed to accept the unit back for repair but I really do not trust this unit and I do not believe that they will test the unit over a long amount of time so I wondered if anyone is aware of this fault so that I can tell them whats wrong and to please replace it.
THIS IS A RE-POST SEEMS LIKE IT SHOULD BE INCLUDED IN THIS THREAD
Third song into the show last night our Qu-16 quit seeing the inputs from our dSnake. Outputs were OK.
Could not re-assign them (couldn’t see them), rebooting stage box, rebooting console, 3rd installation of new firmware, another stage box and even a hard power re-set of the console has not corrected it.
Had to re-set analog for rest of the shows. Thankfully we were in a club setting and the band could cover it acoustically. Vocals were all wireless at FOH.