QTR-Quadtone RIP

Hi All,

I have been using QTR along with the Piezography Pro inkset in my 9900 for a little over 18 months now with very few hiccups. A couple of weeks ago, I replaced both the ink selector unit and pump cap assembly in the printer. After installation and running through the calibrations detailed in the service manual the printer produced a single perfect print (which I am grateful for as I was on a deadline), but then started having issues immediately afterwards - specifically, when a print was spooled to the printer the head would scan back and forth as though it was doing a size/skew check, and then would throw Error D17E and ask for the printer to be restarted. I have been told that this error code is a debug code, and doesn't really point to anything specific, but usually relates to a problem with the main board. I sourced a new (to me) board, but before going through the trouble of installing it, thought I would spend some time tinkering - thinking it odd that the printer would turn on and produce that first print with a bad board.

In my troubleshooting today I decided to try and send a print over USB from my laptop (I normally have the printer connected to a desktop computer via ethernet). I also decided to send a print from Photoshop to see if removing QTR from the equation would make any difference - to my surprise, the printer worked perfectly! Next, I downloaded QTR onto my laptop and sent a print over USB using one of the canned Piezography Pro curves and to even greater surprise, it worked! Feels like we are getting somewhere!

I started to think that this was pointing me to either a communication problem related to ethernet, or that there was a conflict with the desktop computer in my studio. I uninstalled and reinstalled the printer and driver, wheeled the printer over so that I could connect it via USB, and sent a print using QTR with my normal working profile that does not apply Inkjetmall's Gloss Chroma Optimizer to the un-inked areas of the print - the printhead scanned back and forth just like earlier, and immediately threw the error D17E and asked to be restarted. I re-connected my laptop and sent a print from QTR using my normal "NoGCO" curve, and the printer scanned back and forth for about 30 seconds and then threw error D17E. Back to square one.

I power-cycled the printer, ran a nozzle check to see if it could even make it past the size/skew check and the nozzle check went off without a hitch. Next, I sent a print from my laptop through USB via Photoshop and it worked perfectly. I sent a print from QTR using the same standard curve that worked the last time and the print was made without any trouble. I ran a print using the NoGCO curve and the printer crashed immediately. I repeated this sequence on my laptop three times and the NoGCO curve always produced an error, where other curves worked flawlessly.

After having lunch, I hooked the printer back up to my desktop computer via USB and ran a print from Photoshop - it worked just fine. I ran a print using a standard Piezography Pro curve via QTR and it worked just fine. As soon as I selected a NoGCO curve the printer produced Error D17E.

I have posted this saga to the InkJetMall community forum, as well as the Epson Wide Format Group asking for help (I imagine there is a lot of crossover among these three, and I apologize for being such a pest but promise to go away eventually haha). Can anyone think of a reason why one specific curve would produce this kind of an oddball error? Specifically when I've been using it without any issues for nearly two years? Obviously, replacing the Ink Selector Unit and the Pump Cap Assembly was the catalyst for this error, but I am so baffled as to why I can trace it back to a specific curve in QTR. With other curves loaded, the printer works just as you would expect and this behavior is consistent between BOTH my laptop and desktop computers (both running Windows 10).

Any ideas or theories would be hugely appreciated. Thanks for taking the time to read through this saga.

Best,

CJ Heyliger

Please email me the curve off list so I can investigate. Sorry, I did not see this detailed of a post on the IJM forum. But then again, I’ve been in 3 weeks of intense print production deadline myself so my time for support has been a bit limited.

Best,
Walker

> On Sep 27, 2019, at 5:53 PM, cj@... [QuadtoneRIP] <QuadtoneRIP@yahoogroups.com> wrote:
> 
> 
> Hi All,
> 
> 
> 
> I have been using QTR along with the Piezography Pro inkset in my 9900 for a little over 18 months now with very few hiccups.  A couple of weeks ago, I replaced both the ink selector unit and pump cap assembly in the printer.  After installation and running through the calibrations detailed in the service manual the printer produced a single perfect print (which I am grateful for as I was on a deadline), but then started having issues immediately afterwards - specifically, when a print was spooled to the printer the head would scan back and forth as though it was doing a size/skew check, and then would throw Error D17E and ask for the printer to be restarted.  I have been told that this error code is a debug code, and doesn't really point to anything specific, but usually relates to a problem with the main board.  I sourced a new (to me) board, but before going through the trouble of installing it, thought I would spend some time tinkering - thinking it odd that the printer would turn on and produce that first print with a bad board.
> 
> 
> 
> In my troubleshooting today I decided to try and send a print over USB from my laptop (I normally have the printer connected to a desktop computer via ethernet).  I also decided to send a print from Photoshop to see if removing QTR from the equation would make any difference - to my surprise, the printer worked perfectly!  Next, I downloaded QTR onto my laptop and sent a print over USB using one of the canned Piezography Pro curves and to even greater surprise, it worked!  Feels like we are getting somewhere!
> 
> 
> 
> I started to think that this was pointing me to either a communication problem related to ethernet, or that there was a conflict with the desktop computer in my studio.  I uninstalled and reinstalled the printer and driver, wheeled the printer over so that I could connect it via USB, and sent a print using QTR with my normal working profile that does not apply Inkjetmall's Gloss Chroma Optimizer to the un-inked areas of the print - the printhead scanned back and forth just like earlier, and immediately threw the error D17E and asked to be restarted.  I re-connected my laptop and sent a print from QTR using my normal "NoGCO" curve, and the printer scanned back and forth for about 30 seconds and then threw error D17E.  Back to square one.
> 
> 
> 
> I power-cycled the printer, ran a nozzle check to see if it could even make it past the size/skew check and the nozzle check went off without a hitch.  Next, I sent a print from my laptop through USB via Photoshop and it worked perfectly.  I sent a print from QTR using the same standard curve that worked the last time and the print was made without any trouble.  I ran a print using the NoGCO curve and the printer crashed immediately.  I repeated this sequence on my laptop three times and the NoGCO curve always produced an error, where other curves worked flawlessly.
> 
> 
> 
> After having lunch, I hooked the printer back up to my desktop computer via USB and ran a print from Photoshop - it worked just fine.  I ran a print using a standard Piezography Pro curve via QTR and it worked just fine.  As soon as I selected a NoGCO curve the printer produced Error D17E.
> 
> 
> 
> I have posted this saga to the InkJetMall community forum, as well as the Epson Wide Format Group asking for help (I imagine there is a lot of crossover among these three, and I apologize for being such a pest but promise to go away eventually haha).  Can anyone think of a reason why one specific curve would produce this kind of an oddball error?  Specifically when I've been using it without any issues for nearly two years?  Obviously, replacing the Ink Selector Unit and the Pump Cap Assembly was the catalyst for this error, but I am so baffled as to why I can trace it back to a specific curve in QTR.  With other curves loaded, the printer works just as you would expect and this behavior is consistent between BOTH my laptop and desktop computers (both running Windows 10).
> 
> 
> 
> Any ideas or theories would be hugely appreciated.  Thanks for taking the time to read through this saga.
> 
> 
> 
> Best,
> 
> CJ Heyliger
> 
> 
>