Menu ▾ ▴

#6 not printing when a color ink tank is empty

v1.0_(example)
wont-fix
nobody
None
1
2019-08-14
2015-07-15
Mehmet Giritli
No

Hi, My printer has the capability to keep working even when some ink tanks (except pigment black) are empty. On windows it throws you a warning that there are empty tanks and you should hit ok on the printer to continue. I was in this situation the other day and the printer did not print with cups-bjnp complaining that an ink tank is empty. Interstingly, when I checked the properties of the printer I also saw that the error messasge contained printer out of paper situation, which was not the case. So, there seems to be some bug in there regarding printing when a color ink tank is empty. I'm using cups 2.0.2 with cups-bjnp 2.0.

Discussion

  • yann bonnamy

    yann bonnamy - 2017-09-12

    Hi, i have the same issue, on a gentoo distribution , if i use net-print/cups-bjnp-2.0 and if my ink level are low, then i have no printing and debug shows :

    ==> /var/log/cups/error_log <==
W [11/Sep/2017:22:18:54 +0200] [Job 341] Network host \'printer.mYlan\' is out of paper, will retry in 30 seconds...

==> /var/log/cups/bjnp_log <==
   DEBUG: 600.698 Connecting to 192.168.11.40 port 8611 (IPv4)
   DEBUG: 600.698 Sending UDP command to 192.168.11.40 port 8611(IPv4)
   DEBUG: 600.728 Sending UDP command to 192.168.11.40 port 8611(IPv4)
    INFO: 600.730 Identity = MFG:Canon;CMD:BJL,BJRaster3,BSCCe,NCCe,IVEC,IVECPLI;SOJ:TXT01,BJNP2,BJNPe;MDL:MG6100 series;CLS:PRINTER;DES:Canon MG6100 series;VER:1.030;STA:19;FSI:03;HRI:5;MSI:DAT,E3,HFSF;PDR:4;PSE:ABXM66945;
   DEBUG: 600.730 Printer model = Canon MG6100 series
   DEBUG: 600.730 Sending UDP command to 192.168.11.40 port 8611(IPv4)
    INFO: 600.731 Printer status: <?xml version="1.0" encoding="utf-8" ?>
<cmd xmlns:ivec="http://www.canon.com/ns/cmd/2008/07/common/"
xmlns:cijn="http://www.canon.com/ns/wdp/2008/01/print/">
        <ivec:contents>
                <ivec:operation>GetStatusResponse</ivec:operation>
                <ivec:param_set servicetype="print">
                        <ivec:response>OK</ivec:response>
                        <ivec:response_detail/>
                        <ivec:status>idle</ivec:status>
                        <ivec:status_detail>MarkerSupplyAttention</ivec:status_detail>
                        <cijn:IJPrinterStatus>
                                <cijn:Name>BSCCe</cijn:Name>
                                <cijn:ReadData>BST:04;PID:00,00,00;CHD:CL;LVR:GAL,AT;MID:30948D;CTK:M,SET,/,PBK,SET,/,GY,IO,/,BK,SET,/,C,LOW,/,Y,SET;CIR:M=040,PBK=040,GY=000,BK=040,C=010,Y=040;DJS:NO;DBS:NO;DWS:1500,1570;DOC:4,00,NO;DSC:NO;FSI:03;HRI:5;PRC:2,0;MSI:DAT,E3,HFSF;PDR:4;HRC:NO;TCA:M,AC,/,PBK,AC,/,GY,AC,/,BK,AC,/,C,AC,/,Y,AC;</cijn:ReadData>
                                <cijn:NumberOfBytes>291</cijn:NumberOfBytes>
                        </cijn:IJPrinterStatus>
                </ivec:param_set>
        </ivec:contents>
</cmd>
   DEBUG: 600.731 Read printer status: 4, Printing = 0, Busy = 0, Error = 0
   DEBUG: 600.731 Sending UDP command to 192.168.11.40 port 8611(IPv4)

==> /var/log/cups/error_log <==
W [11/Sep/2017:22:19:24 +0200] [Job 341] Network host \'printer.mYlan\' is out of paper, will retry in 30 seconds...

    the workaround is to downgrade to =net-print/cups-bjnp-1.2.1 , then everything is back OK

       INFO: 000.000 BJNP debug level = DEBUG
   DEBUG: 000.000 cups-bjnp: argv[0] = bjnp://printer.mYlan:8611/?debuglevel=DEBUG
   DEBUG: 000.000 cups-bjnp: argv[1] = 341
   DEBUG: 000.000 cups-bjnp: argv[2] = linux
   DEBUG: 000.000 cups-bjnp: argv[3] = Untitled
   DEBUG: 000.000 cups-bjnp: argv[4] = 1
   DEBUG: 000.000 cups-bjnp: argv[5] = media=A4 sides=one-sided number-up=1 number-up-layout=lrtb job-billing= job-uuid=urn:uuid:051fd6ab-62a1-3b38-4b8c-50597b9cc241 job-originating-host-name=localhost date-time-at-completed= date-time-at-creation= date-time-at-processing=   DEBUG: 000.001 Connecting to 192.168.11.40 port 8611
   DEBUG: 000.001 Sending UDP command to 192.168.11.40 port 8611
   DEBUG: 000.029 Sending UDP command to 192.168.11.40 port 8611
    INFO: 000.031 Identity = MFG:Canon;CMD:BJL,BJRaster3,BSCCe,NCCe,IVEC,IVECPLI;SOJ:TXT01,BJNP2,BJNPe;MDL:MG6100 series;CLS:PRINTER;DES:Canon MG6100 series;VER:1.030;STA:19;FSI:03;HRI:5;MSI:DAT,E3,HFSF;PDR:4;PSE:ABXM66945;
   DEBUG: 000.031 Printer model = Canon MG6100 series
   DEBUG: 000.032 Established TP connection to printer 192.168.11.40 port 8611
   DEBUG: 000.155 bjnp_write: starting printing of 4096 characters
   DEBUG: 000.155 bjnp_write2: printing 680 bytes
   DEBUG: 000.155 bjnp_write: Printed 680 bytes, last command sent: 3
   DEBUG: 000.156 bjnp_backchannel: receiving response
   DEBUG: 000.156 bjnp_backchannel: response: written = 2a8, seqno = 3
   DEBUG: 000.156 bjnp_write: starting printing of 3416 characters
   DEBUG: 000.156 bjnp_write2: printing 56 bytes
   DEBUG: 000.156 bjnp_write: Printed 56 bytes, last command sent: 4
   DEBUG: 000.157 bjnp_backchannel: receiving response
   DEBUG: 000.157 bjnp_backchannel: response: written = 38, seqno = 4
   DEBUG: 000.157 bjnp_write: starting printing of 3360 characters
   DEBUG: 000.157 bjnp_write2: printing 3360 bytes
   DEBUG: 000.157 bjnp_write: Printed 3360 bytes, last command sent: 5
   DEBUG: 000.159 bjnp_backchannel: receiving response
   DEBUG: 000.159 bjnp_backchannel: response: written = d20, seqno = 5
   DEBUG: 000.183 bjnp_write: starting printing of 4096 characters
   DEBUG: 000.183 bjnp_write2: printing 4096 bytes
   DEBUG: 000.183 bjnp_write: Printed 4096 bytes, last command sent: 6
   DEBUG: 000.197 bjnp_backchannel: receiving response
   DEBUG: 000.197 bjnp_backchannel: response: written = 1000, seqno = 6
   DEBUG: 000.211 bjnp_write: starting printing of 4096 characters
   DEBUG: 000.211 bjnp_write2: printing 4096 bytes
   DEBUG: 000.211 bjnp_write: Printed 4096 bytes, last command sent: 7
   DEBUG: 000.213 bjnp_backchannel: receiving response
   DEBUG: 000.213 bjnp_backchannel: response: written = 1000, seqno = 7
   DEBUG: 000.239 bjnp_write: starting printing of 4096 characters
   DEBUG: 000.239 bjnp_write2: printing 4096 bytes
   DEBUG: 000.239 bjnp_write: Printed 4096 bytes, last command sent: 8
   DEBUG: 000.241 bjnp_backchannel: receiving response
   DEBUG: 000.241 bjnp_backchannel: response: written = 1000, seqno = 8
   DEBUG: 000.267 bjnp_write: starting printing of 4096 characters
   DEBUG: 000.267 bjnp_write2: printing 4096 bytes
   DEBUG: 000.267 bjnp_write: Printed 4096 bytes, last command sent: 9
   DEBUG: 000.277 bjnp_backchannel: receiving response
   DEBUG: 000.277 bjnp_backchannel: response: written = 1000, seqno = 9
   DEBUG: 000.295 bjnp_write: starting printing of 4096 characters
   DEBUG: 000.295 bjnp_write2: printing 4096 bytes
   DEBUG: 000.295 bjnp_write: Printed 4096 bytes, last command sent: 10
   DEBUG: 000.298 bjnp_backchannel: receiving response
   DEBUG: 000.298 bjnp_backchannel: response: written = 1000, seqno = a
   DEBUG: 000.322 bjnp_write: starting printing of 4096 characters
   DEBUG: 000.323 bjnp_write2: printing 4096 bytes
   DEBUG: 000.323 bjnp_write: Printed 4096 bytes, last command sent: 11
   DEBUG: 000.325 bjnp_backchannel: receiving response
   DEBUG: 000.325 bjnp_backchannel: response: written = 1000, seqno = b
   DEBUG: 000.350 bjnp_write: starting printing of 4096 characters
   DEBUG: 000.350 bjnp_write2: printing 4096 bytes
   DEBUG: 000.351 bjnp_write: Printed 4096 bytes, last command sent: 12
   DEBUG: 000.352 bjnp_backchannel: receiving response
   DEBUG: 000.352 bjnp_backchannel: response: written = 1000, seqno = c
   DEBUG: 000.378 bjnp_write: starting printing of 4096 characters
   DEBUG: 000.378 bjnp_write2: printing 4096 bytes
   DEBUG: 000.378 bjnp_write: Printed 4096 bytes, last command sent: 13
   DEBUG: 000.381 bjnp_backchannel: receiving response
   DEBUG: 000.381 bjnp_backchannel: response: written = 1000, seqno = d
   DEBUG: 000.398 bjnp_write: starting printing of 2808 characters
   DEBUG: 000.398 bjnp_write2: printing 2808 bytes
   DEBUG: 000.398 bjnp_write: Printed 2808 bytes, last command sent: 14
   DEBUG: 000.400 bjnp_backchannel: receiving response
   DEBUG: 000.400 bjnp_backchannel: response: written = af8, seqno = e
   DEBUG: 000.416 bjnp_write: starting printing of 265 characters
   DEBUG: 000.416 bjnp_write2: printing 265 bytes
   DEBUG: 000.416 bjnp_write: Printed 265 bytes, last command sent: 15
   DEBUG: 000.417 bjnp_backchannel: receiving response
   DEBUG: 000.417 bjnp_backchannel: response: written = 109, seqno = f
   DEBUG: 000.417 Sending UDP command to 192.168.11.40 port 8611

    thx for taking this old issue in account,

    Yann.

     

  • Louis Lagendijk

    Louis Lagendijk - 2019-08-14

    Sorry people, I completely missed this report. I have been looking into this today.
    The behavior may seem a regression compared to windows, but it will protect the printhead. The Windows driver probably has a machanism to NOT print color when one of the color cartidges runs out., hence there is no risk for burning the print head. Under CUPS the backend receives an already rendered image (without information whether or not it contains color information), so continuing to print would possibly destroy the print head.

    There is an error where bjnp reports out of paper instead of out of ink. This will be fixed in the upcoming cups-bjnp 2.0.3 version.

     

  • Louis Lagendijk

    Louis Lagendijk - 2019-08-14
    • status: open --> wont-fix
     

Log in to post a comment.

MongoDB Logo MongoDB