I have a MPC3003 that was showing SC899 on arrival so I updated the firmware and switched it back on SC899 came on again even with network unplugged tried format the HDD and then it shows SC819 whilst trying to do the Format HDD ALL procedure Any Ideas other than a Dead Controller?
MPC 3003 SC899 / 819
Collapse
X
-
Re: MPC 3003 SC899 / 819
Can you try to turn on the power with the front door open, maybe it won't code like that. Then get in to user tools and turn on user authentication, that may drop the offending job. -
Re: MPC 3003 SC899 / 819
Not all SC 899 are related to printing. When you update firmware be sure to update everything. Also be sure not to install SOP firmware unless you have a Smart Operation Panel. If you have a Smart Operation Panel do not install normal operation panel firmware. I do not find SC 819 listed for the MP C3003, but for most machines it is a fatal kernel error.Comment
-
Re: MPC 3003 SC899 / 819
Java EXJS firmware can also cause stupid SC's like this, even if it's not being used.It's 106 miles to Chicago. We've got a full tank of gas, half a pack of cigarettes, it's dark and we're wearing sunglasses.
Hit it.Comment
-
Re: MPC 3003 SC899 / 819
Hi.
Does that machine have a fax unit onboard? I have had faulty fax units cause SC819 before. Remove all optional peripherals, like bridge units and fax units and start the machine in its most basic state, then start refitting and testing these one by one until it codes.
Faulty printer memory on the controller can also cause SC819. Try removing, cleaning and reseating the memory. Also try known working memory (same type and capacity).Press the GREEN button!!Comment
-
Re: MPC 3003 SC899 / 819
Hi.
Does that machine have a fax unit onboard? I have had faulty fax units cause SC819 before. Remove all optional peripherals, like bridge units and fax units and start the machine in its most basic state, then start refitting and testing these one by one until it codes.
Faulty printer memory on the controller can also cause SC819. Try removing, cleaning and reseating the memory. Also try known working memory (same type and capacity).Comment
-
Comment
Comment