[McIvyParticipant]

Just to confirm the firmware resolution, this last week we lent an AB168 to a client, forgetting to ensure that they had updated their QU16 desk.(We thought they had, having sent them a previous instruction which was probably ignored….)

Needless to say, whilst in their care, the AB168 reverted to original firmware following a power failure and they lost control. The panic phone call later confirmed that they had not updated the desk to V1.7+, so we had to talk them calmly through the update. Solved the problem when the AB168 was automatically aligned, but not before client had lost half a show.

Stark warning to all!

[McIvyParticipant]

Nicola,
Thanks for the details now provided.
Having mothballed our AB168 for the last few months since comms board replacement, for fear of accidental firmware reset (rumour factory at it’s best…!!!), and with no GLD backup, only iLive and QU’s in the warehouse, we are relieved to be able to install the permanent fix and start to use what is otherwise a great product, particularly with the advantage of rack-less usage and phantom power tell tails.
We too suffered failure whilst working live, which both upset the clients and knocked my digital confidence so badly that this old luddite retreated to rock solid analogue for the remainder of that clients run.
Brave foot forward again now……..!

[McIvyParticipant]

Colonel Ted,

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?

[McIvyParticipant]

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.

[McIvyParticipant]

Hi Hawk,

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.

Regards,

[McIvyParticipant]

Hawk,

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.

Best of luck.

[McIvyParticipant]

Hi there,

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!

Regards to all,

McIvy

[Author]

Posts