Strand 520i - non-responsive front panel

[gareth]

Got a 520i which boots reasonably normally (although it hangs for an unusually long time on the v2.8.6 'splash screen'), but which doesn't respond to any front panel input (buttons, faders, wheels). All displays (including LCDs) are behaving normally, and the console can still be controlled from the alpha keyboard.

 

All connections look sound, BIOS battery has just been replaced, but Ni-MH battery on CS card looks like it's on its last legs (signs of green 'fur' developing on metal battery casing).

 

The one thing I haven't yet checked (because I was more interested in swapping it out for our spare desk so that we could have a show tonight!) is whether it's still outputting DMX. Will check that before I go home tonight.

 

Anyone got any suggestions as to what's up with it, and how to cure it?

[Joe Bleasdale]

A common issue with console front panels not responding is that the panel has lost connection with the motherboard/CPU. I have seen it on a few different consoles. It usually gives a telltale sign such as all the LEDs flashing together, or the screens on the panel displaying something like #### or ****. As you say, the BIOS battery has been replaced, so its unlikely to be that. Maybe worth swapping out the Ni-MH battery as it doesn't sound particularly healthy.

 

Best Regards,

[gareth]

It usually gives a telltale sign such as all the LEDs flashing together, or the screens on the panel displaying something like #### or ****.

 

All displays (including LCDs) {and the LEDs} are behaving normally

 

:blink:

[lurch]

It usually gives a telltale sign such as all the LEDs flashing together, or the screens on the panel displaying something like #### or ****.

 

All displays (including LCDs) {and the LEDs} are behaving normally

 

:blink:

 

Does it have Networker installed on it? If yes, do you get the NET.DRV loaded message just before the splash screen goes.? If not, might be the network card gone AWOL.

Othe things- has anyone been using a riggers remote (wired ones) through a network node (and configured the desk to look for said riggers on a net node)- 520s don't like that and will be completely unresponsive after about 5 seconds.

Other things 2- has someone configured it as a backup rather than main desk, or done something else weird. Have you tried 220clean or just reinstalling?

[gareth]

Does it have Networker installed on it?

Yes.

If yes, do you get the NET.DRV loaded message just before the splash screen goes.? If not, might be the network card gone AWOL.

I haven't actually noticed any of the usual messages at the top of the splash screen - but maybe that's just because I was too distracted by the splash screen being displayed for longer than usual ... on Monday I'll have to take note of what, if anything, is displayed over the splash screen.

Othe things- has anyone been using a riggers remote (wired ones) through a network node (and configured the desk to look for said riggers on a net node)

No - the only remotes we use are wireless Ipaqs.

Other things 2- has someone configured it as a backup rather than main desk or done something else weird

No - the desk in question is never used as a remote, we have another 520i which is used as a 'floating' remote between our venues. The desk config hasn't altered in any way - the only thing that's different since Thursday evening, when the desk last ran a show, is the new BIOS battery.

Have you tried 220clean or just reinstalling?

Wondered how long it would be before someone suggested a 220clean :blink:! No, I haven't tried one yet, partly because I haven't had time (had to swap the desks over and then run the show :** laughs out loud **:), and partly because it wasn't high on the list of things to try because I very much doubt it'll help. I'll do it as a matter of course on Monday when I have the time to attack this problem in a more leisurely manner ...

 

As a matter of interest - who's the 500-series "guru" at Strand these days? Bill Richards was always the oracle to whom I used to direct my console problems, but I don't even know if he's still with Strand - their p*ss-poor post-Phillips website doesn't seem to list one single UK-based staff member now, even the people listed as being European support staff have USA-based phone numbers.

 

A concurrent post has been automatically merged from this point on.

 

Oh, and one more point (before anyone asks!) - I haven't yet determined whether or not the CS card is still spitting out DMX! That's another thing I'll check on Monday. I did go back up to the workshop before going home after the show with the intention of checking it out, but some genius had put the Microscope back into its pouch with the power switch on so its battery was flatter than a flat thing, and there wasn't anything else conveniently close with which to check such things - so I gave up and went home ;).

[Kazeja]

Some of the tracks on the CS processor card which are vital to the front panel comms run in the vicinity of the nicad.

If the corrosion from the nicad has spread to these then provided it's at an early stage, it is still possible to clean up the CS card and bypass these open circuit tracks.

 

You will probably find that all console operation and facilities (DMX etc.) will still work via a keyboard

 

K

[gareth]

Right, sussed it! (Or rather, had it sussed for us! ;))

 

Having spoken to various very knowledgeable people regarding what might be the problem, it turned out to be something very minor and not something we'd ever have worked out for ourselves.

 

We have two 520i desks, both the same age, both with Intel motherboards, but with a slight variation in the BIOS/chipset. My mistake was comparing the BIOS settings of one against the other after replacing the battery on the motherboard - I foolishly assumed that they should be set up the same way. Wrong. One of the motherboards has an issue regarding how 'robust' it is in terms of communicating with things plugged into the ISA slot (which is how the CS card links to the motherboard) and requires IRQ 11 to be reserved in the BIOS. The other one doesn't. And that one tiny discrepancy renders the entire front panel unresponsive to input :) .

 

So, that's that sorted - all we need now is the password to remedy the fact that the desk seems to have forgotten that it should have 400 channels, and that should be appearing in my in-box tomorrow (thanks, John!).