Question Canon Colorado M Series Persistent Errors (#11526 and Magenta Drop Shadows)

[David SC]

Yeah, there is still no fix. The 11526 error requires a restart. We experience on average of 1-3 times a week on all our machines. The engineers are aware at Canon (according to our local tech), but no one knows what to do. The restart shuts us down for about 20 minutes when it happens I am told.

The magenta drop shadow is one of those things that Canon blames Onyx and Onyx blames Adobe. Our workaround is to flatten images (100% Raster) when we notice it. We don't automatically flatten everything, because it degrades print quality. So basically, we waste the print, then realize it needs to be flattened, then reprint it.

Sorry, I wish I had better news, but these issues are still issues.

Fixed. Network related at some point.
Plug your printer direct to the rip computer via ethernet on a seporate subnet so it is seporate to the rest of your network and only the rip computer can see it and can print to it.
If that runs fine and prints without error, then it's somthing on your network that the printer is freaking out about.
We had to spend a few thousand replacing our entire network hardware (routers, whitches, modems) and it all works now, no errors so far.

 

[David SC]

Yeah, there is still no fix. The 11526 error requires a restart. We experience on average of 1-3 times a week on all our machines. The engineers are aware at Canon (according to our local tech), but no one knows what to do. The restart shuts us down for about 20 minutes when it happens I am told.

The magenta drop shadow is one of those things that Canon blames Onyx and Onyx blames Adobe. Our workaround is to flatten images (100% Raster) when we notice it. We don't automatically flatten everything, because it degrades print quality. So basically, we waste the print, then realize it needs to be flattened, then reprint it.

Sorry, I wish I had better news, but these issues are still issues.

Fixed. Network related at some point.
Plug your printer direct to the rip computer via ethernet on a seporate subnet so it is seporate to the rest of your network and only the rip computer can see it and can print to it.
If that runs fine and prints without error, then it's somthing on your network that the printer is freaking out about.
We had to spend a few thousand replacing our entire network hardware (routers, whitches, modems) and it all works now, no errors so far.