Hi!
Happy I found this forum... This is my first post, so please be gentle :-)
I just got a Canon ImageRunner c250if printer.
It seems to be working fine, but whenever it exits sleep mode, I get this error e0009-0002.
The service menu titles this error as "Fixing disengagement timeout error", and the description states:
"Signal of the Fixing Pressure Release Sensor could not be detected at pressure release operation of the Fixing Pressure Release Cam,
and the operation was not completed within 4 sec from the start of counterclockwise rotation of the Fixing Motor".
The suggested resolutions span from checking harnesses to replacing the Fixing Assembly / Fixing Drive Assembly / Fixing Drive / Interlock Assembly and more.
Since this only occurs when exiting sleep mode, I thought this might be a firmware issue.
I upgraded to the latest FW, but the problem persists.
A new fixing assembly is quite expensive, so I was wondering if anyone has encountered this problem
and managed to fix it without getting a new assembly.
Sorry for being so lengthy, and thanks in advance for any hint!
- Barak
Happy I found this forum... This is my first post, so please be gentle :-)
I just got a Canon ImageRunner c250if printer.
It seems to be working fine, but whenever it exits sleep mode, I get this error e0009-0002.
The service menu titles this error as "Fixing disengagement timeout error", and the description states:
"Signal of the Fixing Pressure Release Sensor could not be detected at pressure release operation of the Fixing Pressure Release Cam,
and the operation was not completed within 4 sec from the start of counterclockwise rotation of the Fixing Motor".
The suggested resolutions span from checking harnesses to replacing the Fixing Assembly / Fixing Drive Assembly / Fixing Drive / Interlock Assembly and more.
Since this only occurs when exiting sleep mode, I thought this might be a firmware issue.
I upgraded to the latest FW, but the problem persists.
A new fixing assembly is quite expensive, so I was wondering if anyone has encountered this problem
and managed to fix it without getting a new assembly.
Sorry for being so lengthy, and thanks in advance for any hint!
- Barak
Comment