This machine has a 3800 error code. We have replaced the ISU and ribbon cables along with the main pwb and current firmware. Has anyone seen this issue and remedied the issue?
6004 with a 3800 error
Collapse
X
-
Re: 6004 with a 3800 error
Please remember scanner-/ engine partial operation function!
You has to run U906 after C3800 until the problem would solved in total, otherwise system will always coming up with same error code!
I have seen this error during nearby every training after opening from the cont-/ shield box.
Technicians forgot to connect FFC from image sensor pwb on main pwb because it would hidden during closing from the box.
Look for YC33 again.Comment
-
Comment
-
Re: 6004 with a 3800 error
[906QUOTE=KYO_OEM;2371527]Please remember scanner-/ engine partial operation function!
You has to run U906 after C3800 until the problem would solved in total, otherwise system will always coming up with same error code!
I have seen this error during nearby every training after opening from the cont-/ shield box.
Technicians forgot to connect FFC from image sensor pwb on main pwb because it would hidden during closing from the box.
Look for YC33 again.[/QUOTE]
that's a great heads up.
This machine though was a new one that went through set up and coded during delivery. It was brought back and the main ribbon cables and isu were replaced, as was the main pwb. there also was a 2950 that popped up at this time as well which was why the image drive pwb was replaced. I did at least one 906 reset and during this and it never cleared the code.Comment
-
Re: 6004 with a 3800 error
maybe we has to use our brain to look what`s going on inside from the system during startup...
1. C3800/ AFE Error:
no match from written data and scanned data
2. C2950/ Motor CPU Communication Error
no communication/ commands on Motor CPU side
Maybe there is a blocked motor drive or else which is breaking down the communication circuits
I remember old case from Iris1 with C2103/ reason was the laser motor. (killed the motor cpu communication line)
(KDC published bulletin after they received/ checked the lk unit)
What happens by startup with open front cover after U906?Do you get entrance to 1087 mode for checking U904?Do you see other hidden c-calls?
But what happens at first at every start up?
After power on the scanner is moving for AFE controlling, independed to the print engine motors/ does it happen or not?
Do we have a broken scanner motor/ blocked scanner which kills the motor cpu?
This i would check at first.
By the way:
i hate Iris2020 development engineers because of this fu***scanner/ engine partial operation mode.
You can not enter a lot of service modes, because they are blocked...you can`t take out U000 list by USB and so on.
This makes it very difficult to analyse.
e.g. in case of C7901/ missing Eeprom data from black dk
You can`t enter U110, U117 and so on..
So you can`t see if other dks are present.
If all other dks are present, you know that your problem is coming from dk itself, if no dk visible by U117, you know that your problem is coming from pwb.
But which pwb?
Image drive pwb, front pwb, dlp pwb??
No possibilty to check because all needed maintenance point are gone.
You can`t enter U984 for checking serialnumbers from dv units
And so on...Comment
-
Re: 6004 with a 3800 error
maybe we has to use our brain to look what`s going on inside from the system during startup...
1. C3800/ AFE Error:
no match from written data and scanned data
2. C2950/ Motor CPU Communication Error
no communication/ commands on Motor CPU side
Maybe there is a blocked motor drive or else which is breaking down the communication circuits
I remember old case from Iris1 with C2103/ reason was the laser motor. (killed the motor cpu communication line)
(KDC published bulletin after they received/ checked the lk unit)
What happens by startup with open front cover after U906?Do you get entrance to 1087 mode for checking U904?Do you see other hidden c-calls?
But what happens at first at every start up?
After power on the scanner is moving for AFE controlling, independed to the print engine motors/ does it happen or not?
Do we have a broken scanner motor/ blocked scanner which kills the motor cpu?
This i would check at first.
By the way:
i hate Iris2020 development engineers because of this fu***scanner/ engine partial operation mode.
You can not enter a lot of service modes, because they are blocked...you can`t take out U000 list by USB and so on.
This makes it very difficult to analyse.
e.g. in case of C7901/ missing Eeprom data from black dk
You can`t enter U110, U117 and so on..
So you can`t see if other dks are present.
If all other dks are present, you know that your problem is coming from dk itself, if no dk visible by U117, you know that your problem is coming from pwb.
But which pwb?
Image drive pwb, front pwb, dlp pwb??
No possibilty to check because all needed maintenance point are gone.
You can`t enter U984 for checking serialnumbers from dv units
And so on...
here was the sequence.
at startup it would 2950 then immediately reboot
after that reboot it would 3800 and then immediately reboot
other times it would come up with a 3800 first and not reboot.
but in the end the image drive pwb corrected the 2950 and the engine board corrected the 3800 code, but in either case there was never a light from the scanner and I never saw it move.Comment
-
Re: 6004 with a 3800 error
Good Day All
I just came across this thread as i am having the same issues however on the colour versions. I just received my 3rd call for the same amount of machines. I have replaced the ISU's on the 1st two machines which solved the issue immediately, and planning on ordering another one for the 3rd machine.
Anyone else having insight on the matter?
RegardsComment
Comment