If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
I have an eStudio 2500 that is driving me crazy. 5 service calls on this machine for the same problem. I have replaced the paper sensors in the bridge unit and the hole punch unit and am still getting this error. Anyone with ideas please help.
does this happen when doing print jobs? copying? both?
does the paper stop as it's exiting the fuser?
we had one that kept E020'ing but only on print jobs & only from the top tray, eventually removed & reloaded print driver, all was well for a while, then back to same again. in the end they had a replacement machine.
when it jams, take a look @ the 2nd transfer roller to see if there's any layers of colour toner on it. i have a theory on these errors that the 2nd tr roller is running in contact with the transfer belt at a point when it shouldn't be, causing paper to drive when it shouldn't ( or at the wrong speed ) . also when printing i believe the machine runs at a different speed than copying.
if a print job is attempted & it's size is judged as non-standard, the machine will jam because it doesn't know what paper size it's feeding ( i proved this with a usb pen, printed a non-standard size job, the machine jammed as the paper was leaving the fuser giving ... yes an E020
Check the 2nd transfer roller there was an issue with these and Toshiba issued an updated one. Most in the production line were shipping with 2 one in the machine and one in the box. The setup tech was suppose to switch during setup but I keep finding the wrong one in the machine. These will slow down the drive assembly causing all sorts of headaches.
Also check the exit switch, I have had a bad spring on the actuator that did not return the switch fast enough causing e020.
I think I may have repaired the problem. Toshiba put out a bulletin on this problem and it seems that the IPC board has been giving them some issues. I flashed the finisher with the latest firmware and the issue seems to have gone away.
Comment