Hi,
The place I work has an Azure 2000 perminantly installed for use in the nightclub area of the venue. We are having some issues with the desk:
1. The desk software seems unstable, in other words it crashes lots which is a particular problem when the strobes become jammed on for 2-3 minutes while we try to reset the desk because it has crashed. (FYI we use martin atomic 3k's so they are bright!)
2. We though the crashing was a corruption of the current program loaded on there. We performed a Hardware Wipeall and updated the software to 2003. The issue was now when we tried to reporgram the show (we wanted to make sure the corruption was not on the show disk).
We managed to patch in all the fixture (36 in total) and the colours for the MAC250's we have and the desk claimed that the memory was full. A quick check verified it thought 0% of the memory was free. Could someone help me with this?
3. Is more of a software issue between myself and the desk. When you have some fixtures performing a shape generated chase and say you wanted to grab one of the fixtures in the chase to use as a spotlight. You enter the programmer and try to grab the fixture but find you cannot pan and tilt. So my question is, why does the shape generator have priority over the programmer controls? Is there any way to change this?
Sorry about the long post, thanks in advance for any help you can give.
Julian
Azure 2k Issues - Crashing & Memory Problems - Help!
Moderator: Moderators
That was spam. Needs to be deleted.
I can't really help, but I am guessing there may be a hardware/memory problem.
Regarding overriding shapes, AFAIK the Azure code is based on the Pearl code. There is no way in the Pearl to override shapes & so I would imagine it is the same for the Azure.
The ability to take control and use as a spot etc. would be very valuable and has been suggested.
I can't really help, but I am guessing there may be a hardware/memory problem.
Regarding overriding shapes, AFAIK the Azure code is based on the Pearl code. There is no way in the Pearl to override shapes & so I would imagine it is the same for the Azure.
The ability to take control and use as a spot etc. would be very valuable and has been suggested.
Okay, let's try some things:
1. Have you performed the "extended memory test"?
2. Did you look at the bus errors? If they are there, clear them.
3. Do you use a custom SG.DAT file? I have seen that if you have a tiny mistake on it, the show gets corrupted over time.
4. Use the softbutton "Optimize memory pool" after long programming sessions. The programmer seems to clutter the desk over time.
5. Did the desk perform in a moist and/or cold environment. That also can cause problems.
I can give you only 1 other advice: SAVE SAVE SAVE!! Preferably on different floppy disks. Whenever you see the desk running stable, SAVE! After patching: SAVE! 1 hour of programming: SAVE (on disk 2)! After final legending: SAVE (on disk 3)! Because when you save a show that is somewhat corrupted, you will only load a corrupt show again with the same problems.
Normally, when resetting the desk, the DMX-output goes to 0 for all channels. I may be mistaken, but if the desk can't start up, hold the memory buttons 41 and 50 (or 21 and 30, I'm not sure) while starting up the desk. That gives you access to the AVOS screen. Then perform a wipeall via that menu.
For the "Followspot" problem, there is a workaround:
1. Select your light
2. Locate it
3. Perform a circle shape with size and speed set to 0.
1. Have you performed the "extended memory test"?
2. Did you look at the bus errors? If they are there, clear them.
3. Do you use a custom SG.DAT file? I have seen that if you have a tiny mistake on it, the show gets corrupted over time.
4. Use the softbutton "Optimize memory pool" after long programming sessions. The programmer seems to clutter the desk over time.
5. Did the desk perform in a moist and/or cold environment. That also can cause problems.
I can give you only 1 other advice: SAVE SAVE SAVE!! Preferably on different floppy disks. Whenever you see the desk running stable, SAVE! After patching: SAVE! 1 hour of programming: SAVE (on disk 2)! After final legending: SAVE (on disk 3)! Because when you save a show that is somewhat corrupted, you will only load a corrupt show again with the same problems.
Normally, when resetting the desk, the DMX-output goes to 0 for all channels. I may be mistaken, but if the desk can't start up, hold the memory buttons 41 and 50 (or 21 and 30, I'm not sure) while starting up the desk. That gives you access to the AVOS screen. Then perform a wipeall via that menu.
For the "Followspot" problem, there is a workaround:
1. Select your light
2. Locate it
3. Perform a circle shape with size and speed set to 0.
-
light-o-matic
- Posts: 15
- Joined: 20 Dec 2005, 15:33
Julian, sounds like you might have multiple problems. But I suggest taking a look at the hardware aspects of things.
I have an Azure 2000 which was previously in a club installation. It would often have corrupted video or crashes.
Avolites America suggested that I clean and tighten all the connectors in the board (there are quite a few), and it made a huge difference. Each connector was sprayed with deoxit, the excess blotted with a soft rag. Then a small spray of preservit and plugged firmly back into place. I find that doing this around once a year makes all the difference.
I also will gently push down any socketed chips in the console, and I will take out the video card and video card riser and spray them as well.
The video card must then be put firmly back in place.
Since doing this, problems with the board have been extremely rare.
But I suggest that if you have zero electronics experience you get someone else to do it. But if you have for example had a decent amount of experience taking apart and building PCs and haven't broken anything yet, then that's fine.
I have an Azure 2000 which was previously in a club installation. It would often have corrupted video or crashes.
Avolites America suggested that I clean and tighten all the connectors in the board (there are quite a few), and it made a huge difference. Each connector was sprayed with deoxit, the excess blotted with a soft rag. Then a small spray of preservit and plugged firmly back into place. I find that doing this around once a year makes all the difference.
I also will gently push down any socketed chips in the console, and I will take out the video card and video card riser and spray them as well.
The video card must then be put firmly back in place.
Since doing this, problems with the board have been extremely rare.
But I suggest that if you have zero electronics experience you get someone else to do it. But if you have for example had a decent amount of experience taking apart and building PCs and haven't broken anything yet, then that's fine.
Sorry it has been a while since I have been on the forum.
I have opened the desk and re-seated all the chip, the desk is much much more stable and has crashed once since then
(which was november, when I was trying this out as a last resort before we were going to send the desk off to avo).
As for the optimised memory pool, I wasn't sure what it did much what you say makes sense and I will remember to use it in the future.
As for the followspot thing you suggested I will try it, sounds like a cool idea.
As for Bus errors, they come and then they go and every so often the pop up again, so whatever it is, it is intermittent.
As for crashing during strobes, our incomming supply is directly from the rather large substation below the building and supply problems are unlikely. We think it is a co-incidence since it has crashed randomly when strobes are not running. it is more of a problem that when it crashes with strobes it locks the strobes to 100% until we reset the desk.
Thanks for the help,
Julian
I have opened the desk and re-seated all the chip, the desk is much much more stable and has crashed once since then
(which was november, when I was trying this out as a last resort before we were going to send the desk off to avo).
As for the optimised memory pool, I wasn't sure what it did much what you say makes sense and I will remember to use it in the future.
As for the followspot thing you suggested I will try it, sounds like a cool idea.
As for Bus errors, they come and then they go and every so often the pop up again, so whatever it is, it is intermittent.
As for crashing during strobes, our incomming supply is directly from the rather large substation below the building and supply problems are unlikely. We think it is a co-incidence since it has crashed randomly when strobes are not running. it is more of a problem that when it crashes with strobes it locks the strobes to 100% until we reset the desk.
Thanks for the help,
Julian
Who is online
Users browsing this forum: No registered users and 13 guests