- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Has the developer been replaced along with the drum They are normally replaced as one. If not that is why it is coding out. If not with power off then on have tech come out and replace the developer and drum mite require the sensor in the developer cartridge mite be bad.
ATDC sensor malfunction.Try to change the ATDC sensor gain adjustment value,increase or decrease.If the error persist you must be change the developer and the perform the F8(developer and ATDC semsor initialization).To reset please tell me the copier model.
Cof 024 - AIDC sensor contamination correction failure.The photosensore LED located under OPC drum of the AIDC sensor dirty.Clean the sensor,reset the malfunction code if the necessary perform F5 AIDC auto adjustment.
COF 32 ATDC sensor failure.Enter in the service mode select Then.rep.mode select printer mode select ATDC gain adjustment note the current value then clear the current value and change the value up or down.Ex: the current value = 150 clear and change to 154 ,make a few copy and if the error code not displayed is OK.If the error code is appaire clear the value and enter 132,make a feww copy,if OK you are resolved a problem. Service mode entering: press utility key-press metercount-press details(if apaire the details windows)-press Stop 0 0 Stop 0 1 (if appaure admin code press 00000000 ) select techn.rep.mode-printer etc.
how the code appeared? I suppose you worked with the cyan low toner attention untill the machine stopped. in this case you should make an ATDC sensor adjustement! but firstly you should reset the error!