FLXs48 lock up

[Martin Oakley]

Hi,

Have a show running at present but occasionally get the desk lock up.

There has been one or two issues during the programming where I received a 'Oops, something has gone wrong message...' but was too slow to capture the error on a USB stick.

Anyway, during the run last night we had a lock up where we had to restart the desk and then everything carried on as normal.

It is a cue where a pair of moving lights are first commanded - this maybe just coincidence but we did have a few issues during programming with them when they just started randomly moving but not lit.

Is there a error log or something that can be retrieved after the even where I can obtain any info to share with you guys?

TIA

[Edward Z88]

Hi Martin, 

Sorry to hear this, we haven't come across this issue before.

Can you confirm you are running ZerOS 7.9.5 on your console? You can find out by tapping Z -> System Information.

Please could you send us a copy of this show file to us at support@zero88.com with a description of the issue, and we'll take a look and see if anything may be causing the issue.

If you have any instances of this happening again, please do let us know.

Hope this helps, let us know if you have any questions.

Edward

[Martin Oakley]

Hi Edward.

Didn't want to update during show run but did not have any further issues. I have since updated to 7.9.5.
I attach an early error log that we received early in the set up/plot where we got the 'Oops something appears to have gone wrong'

One thing we did notice the day after the 'problem' is that one of the playbacks seems to have got corrupted. A power off and power on didn't clear the issue. I really wish we had saved the show at that point with the 'corruption' and tried to call it back in but wise after the event!
The playback (19) continually flashed with the MFF set to zero which indicated to me it was running. It was running a mover very slowly lit with a colour we were not using! Other playbacks had their LED's lit but not flashing. Master playback ran other cues happily but not Playback 19 which was triggered through the stack.

Again for info debug file attached although, as I say, very early on.

debug_31-12-1969_19-00-55.zdb