Surface –> MixRack gigaAce connection problem after 2.0 upgrade

[tcb.churchParticipant]

System setup:

• DM64 MixRack in a rack backstage, FoH run from a dLive S7000 surface
• The DM64 is connected to the network and the surface connects to the MixRack using a single gigaAce connection

The rack containing the MixRack, amps and radio mic receivers is powered up first, then the S7000 surface is powered up after the MixRack has started

I’ve just upgraded the dLive firmware from 1.98 to 2.00 and everything related to the upgrade seemed to go OK. However, when the surface is now switched on, it initially fails to connect to the MixRack and displays the dreaded “Surface’s connection to MixRack failed” screen.

This seems only to be a gigaAce problem because I can successfully connect to the MixRack over the network from the dLive Director software.

If I press “Choose MixRack” on the “Connection filed” screen, the MixRack is visible and I can reboot the surface, and everything seems to be stable.

The system logs simply show lots of entries saying “MixRack Internal Error”

Has anyone else experienced this, and if so, did you find a solution?

Thanks

Chris W

Attachments:

You must be logged in to view attached files.

[tcb.churchParticipant]

After downgrading the firmware to 1.98, the surface connects correctly to the MixRack at boot up, but the “MixRack – Internal Error” and “Touch Screen – Internal Error” kept appearing in the logs.

So after 90 minutes on the phone to tech support, it appears that the 2.0 upgrade ***may*** have brought an underlying hardware problem to light.

A&H are analysing the log files to track down the cause of the problem and I’ll know more in a few days

[tcb.churchParticipant]

Well this is really unexpected…

I cleared the logs on the dLive, loaded the “FoH” default show file and the logs stayed clean.
So I then loaded our show file, and again the logs remained clean.

Then, with the log screen still displayed I inserted the USB stick into the dLive and immediately loads of “Internal Error” entries appeared!

The weird thing is that the USB stick worked well enough for the dLive to read/write files from/to it, but also generated dozens of log errors. Unless you happen to be looking at the log screen at the time the USB stick is inserted, you cannot easily determine what caused these errors. Even the developers at A&H who analysed the logs could not be sure what had caused them.

After reformatting the USB stick, it worked fine in the dLive without causing any further errors.

Long story short, A&H devices seem to be very sensitive to what USB stick is used. I know this also from doing firmware upgrades on ME1 personal mixers. Certain USB sticks can be read, but then cause the ME1 to become unstable…

[Author]

Posts