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

[FireSprint.com]

We have two persistent errors with all 3 of our Colorado M series printers. We have not gotten a solution out of Canon for these whatsoever. They send techs out weekly with no resolution.

Curious if any of you have found a workaround that run these?

1.) Error 11526.
As you can see, my production team emails alot about these errors causing ~30 minute slowdowns to production. It ruins the current print, and causes us to do a hard restart.




2.) Drop shadows converting to Magenta on certain gloss prints:

We see this from time to time. The typical solution is to fully rasterize the image. The challenge is, like many of us, we get artwork from all over. The magenta drop shadow doesn't appear in any digital file, just when printed. We typically can resolve the issue by fully rasterizing the image first. This is a resource intensive step. We have spoke to Canon, Adobe, and Onyx about this and they all blame each other of course.

 

[Christian @ Visual Graphx]

Magenta shadow is probably due to RGB Transpancies. Rasterizing is the only correction. Do you have an automation systems for preflight?

11526 - Has Canon ever changed the drop detectors? It's typically caused by detectors that are taking too long or proving erroneous reads

 

[FireSprint.com]

Magenta shadow is probably due to RGB Transpancies. Rasterizing is the only correction. Do you have an automation systems for preflight?

11526 - Has Canon ever changed the drop detectors? It's typically caused by detectors that are taking too long or proving erroneous reads

I'll ask about the drop detectors.

We do have alot of automation in preflight. The issue is, we can print the same file on our Durst printers with Durst RIP, our Konica Minolta, or Brother Copier, or look at it on any screen, and there is no magenta drop shadow. Only on the Colorados. We're trying to avoid rasterizing everything. That will end up being terabytes and terabytes of additional data moving through our system.

 

[compu6199]

I have found a "partial solution" for the so called "Magenta Drop Shadows" - In Onyx in Job Editor, at Color Management, choose the profile setting: European Colorimetric (Precise)
I printed the file and the color of the shadows are pretty much acceptable.

Thanks all

Israel Gluck
Compugraph Signs
Israel@compugraphsigns.com

 

[Grizzly]

I've also seen the magenta drop shadow issue. And only on the M. My 1650 prints them great so it gets anything with drop shadows.

 

[GenV]

Hello!
Did the 11526 error ever resolve? We are getting an error with the same code 11526and have been scratching our heads for two weeks now. The printer will not even start or begin to warm up in our instance. Since we had a power outage here the usual suspects were the main relay board and one of the power supplies, but to no avail. Any ideas would be very welcome. Thanks!

 

[soggywinter]

Are the 11526 errors repeatable with the same job being re-sent? If so, have you tried a sending the files with a different version of Onyx RIP or different RIP entirely (ie, Print Factory or Caldera)?

 

[GenV]

Are the 11526 errors repeatable with the same job being re-sent? If so, have you tried a sending the files with a different version of Onyx RIP or different RIP entirely (ie, Print Factory or Caldera)?

We got the error on printer startup, it doesn't even start initializing. We reseated some of the cables between the connector PC and the windows PC and the error has resolved. We had a potential power surge so im sure the computers went a little silly because of it. We suspected PSU failure on the connector computer but that isnt the case. Turns out the technician misdiagnosed the faulty printer PSU (there are 4 of them, of those 3 are different from each other). We have diagnosed the faulty PSU and ordered a new one for replacing and that will hopefully resolve our issue

 

[FireSprint.com]

I’ll check with my team and get an update.

I’m not sure if we just have workaround or they were actually solved. With our 3 Colorados, we basically have a tech in weekly for one reason or another. I just wave and say hi.

 

[FireSprint.com]

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.

 

[Pauly]

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.

I got this error on the 1650 a few weeks ago
I was told its when the software looses connection with the hardware because the software is doing too much. his examples where nozzle comp after a head strike where there is a bad strike and a lot of comp is happening. or a lot of deflecting nozzles.

have you considered caldera with the Colorado's? It honestly runs far far better than onyx. our caldera runs headless just about with it's automation. We've just set up a poolin enfocus switch UI for all files for the colorados and choose which jobs go to which.
we have not come across he grey/magenta issue. Unsure if it's an onyx or adobe problem.

 

[GenV]

Our 11526 was a direct result of the machine being out of order for a long time, has never happened in the middle of printing. After not being plugged in, the first initialization took so long that i believe it essentially "timed out" eventually. I did unscrew and demount both of the computers and checked for any bad cables or loose connections, gave it a good clean and reseated everything back properly and we haven't had an issue since. Since our issue was most likely power supply related we are waiting for the new PSU to arrive to get the machine back up and running again


And i agree with the previous poster, Caldera works miles better with Colorado

 

[David SC]

Anyone fond any type of solution for the 11526 or 11520 errors? We purchased a new M5 that had the errors from the day 1. Spent 4 weeks with techs on site everyday, replaced just about everything on the machine. The controller, the windows computer, a few boards in the machine, HDD in the controllers, etc etc.
Gets the error pretty much every single night during the nighr, but also happens during the day.
Sometimes during printing (somtimes it will have the error with unresonsive screen, but will continue to print the rest of the job, sometimes it will kill the print)
Had it error half way through media calibration. Pretty much errors when ever it feels like it.
Had it recently replaced with a full new printer at the start of the week, and low a behold, same errors.
They are looking into possible issue with the power/grounding in the building now.

 

[Pauly]

Anyone fond any type of solution for the 11526 or 11520 errors? We purchased a new M5 that had the errors from the day 1. Spent 4 weeks with techs on site everyday, replaced just about everything on the machine. The controller, the windows computer, a few boards in the machine, HDD in the controllers, etc etc.
Gets the error pretty much every single night during the nighr, but also happens during the day.
Sometimes during printing (somtimes it will have the error with unresonsive screen, but will continue to print the rest of the job, sometimes it will kill the print)
Had it error half way through media calibration. Pretty much errors when ever it feels like it.
Had it recently replaced with a full new printer at the start of the week, and low a behold, same errors.
They are looking into possible issue with the power/grounding in the building now.

do you have sufficient power to it?

 

[David SC]

do you have sufficient power to it?

2 separate 15 amp circuits (as specified)
Just had them rewired to be on the same phase comming in. In case that is the issue being on different phases.

 

[Pauly]

2 separate 15 amp circuits (as specified)
Just had them rewired to be on the same phase comming in. In case that is the issue being on different phases.

Ah fellow Aussie.
Our M5 and 1650 both run on separate phases on 20a circuits. I've had this error once only on the 1650.
As mentioned above, i was told that it's lost communication between the Software & onboard hardware. The reasons i was told was the PC could have been locking up from the pc doing too much e.g high nozzle comp.
Or sometimes something like that could happen if there is a power issue like spikes or drops. (generally speaking) The fact that it was consistent on 2 machines starts pointing to the power.

 

[David SC]

Ah fellow Aussie.
Our M5 and 1650 both run on separate phases on 20a circuits. I've had this error once only on the 1650.
As mentioned above, i was told that it's lost communication between the Software & onboard hardware. The reasons i was told was the PC could have been locking up from the pc doing too much e.g high nozzle comp.
Or sometimes something like that could happen if there is a power issue like spikes or drops. (generally speaking) The fact that it was consistent on 2 machines starts pointing to the power.

17hrs now with no error. hoping this continues and that was the issue.
Possible that the machine just doesn't like having the two power supply lines comming into the machine "out of phase" of each other and has random connection errors from that. ‍♂️
Odd that Canon couldn't determine that, as it was just a last ditch idea.

 

[David SC]

Scratch that. Error came up again.

 

[GenV]

An update here, we managed to finally replace the faulty power supply but the printer doesn't boot up anymore, with brand new error "no communication with controller - 95". I have reason to believe from a post in the canon forum that these past three weeks diagnosing and booting the machine up and down might have messed up either of the two controllers' software or the OS. Tech support is so slow over here and communication is very sparse. If anyone has any tips on what i could do by myself it would be appreciated!

 

[Pauly]

17hrs now with no error. hoping this continues and that was the issue.
Possible that the machine just doesn't like having the two power supply lines comming into the machine "out of phase" of each other and has random connection errors from that. ‍♂️
Odd that Canon couldn't determine that, as it was just a last ditch idea.

Both mine use a different phase per plug. no issues there.