Avid Digidesign 003 Factory Dead Faders

[deadfaders_003_factory]

A google search for DEAD FADERS 003 XX.X shows multiple users with the same problem that just turned up for me today. All faders have stopped working altogether. Firmware updates do not fix the problem, fader firmware version x.xx still shows up in the Utility screen afterwards. I have used the 003 for maybe 40 hours total, always dust-covered when not in use, always babied.

The resolution given below is that the faders will come on line "when the unit is reset". My question is:

How does one reset the 003 Factory?

Interestingly the issue below seems to refer to 1 fader, but why all of them? Why so many people with the same problem?

This is on the Digidesign website, at http://www.digidesign.com/index.cfm?...34&nStartAt=41

"Dead faders on the 003.
As of this writing, the 003 does not have a fader recalibration utility. It is possible to move the fader with a non-conductive material until the motor disengages. The fader will not come back online until the unit is reset.
Digidesign is looking into a possible fix to the 003 firmware to resolve this issue."

There is no date given to say what date is "this writing".

This is a very frustrating and surprising problem to happen with such an expensive piece of gear.

[GloryIsSilent]

Since I'm having this issue, would I be correct in reading that this is caused by moving a fader with a non-conductive material?

[DigiTechSupt]

Here's info on testing and recalibrating faders:

http://avid.custkb.com/avid/app/self...lite=reset+003

You may also want to try a firmware reset:

http://avid.custkb.com/avid/app/self...lite=reset+003

If you're still experiencing problems, you should contact a service center or tech support by phone for further troubleshooting.

[converted]

did it work?

[GloryIsSilent]

Originally Posted by converted

did it work?

Nope.

[BANJAR TERATAI CAPUNG]

also here nope - i think problem must bigger than firm ware or reset- but 003 still working manually by mouse- so any idea solve that problem -for specific clue - happened if in session we add something like track - or plug in but if just mix system ok