All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: "Kennedy, Smith (Wireless Architect)" <smith.kennedy@hp.com>
Cc: Open Printing <printing-architecture@lists.linux-foundation.org>,
	Daniel Dressler <danieru.dressler@gmail.com>,
	"The CUPS developer list." <cups-devel@cups.org>
Subject: Re: [Printing-architecture] [cups-devel] Communication between IPP printer and "ipp" CUPS backend
Date: Wed, 16 Sep 2015 16:24:47 -0300	[thread overview]
Message-ID: <55F9C1FF.5000307@gmail.com> (raw)
In-Reply-To: <FB1D5086-D828-40DE-AD16-85293A1C66C4@hp.com>

[-- Attachment #1: Type: text/plain, Size: 1902 bytes --]

On 09/15/2015 09:32 PM, Kennedy, Smith (Wireless Architect) wrote:
> Hi Till,
>
> Sorry for not replying earlier. Would you have any USB traces from Wireshark or a Beagle protocol analyzer, or logs, and/or the corresponding document files, so that we could try to repro it internally?
>
> Smith

Attached is a tarball with the following files:

"log" files (with hex dumps of all communication content) of the 
following command line for several print jobs:

./ippusbxd -d -v 03f0 -m c211 -s BR54BFB02C05XK -P 60000 2>&1 | tee log

Each job was printing the file "doacao.odt" out of LibreOffice on a CUPS 
queue with the device URI (using HPLIP driver):

ipp://localhost:60000/ipp/print?waitjob=false

The job succeeded in most cases, after each job I have stopped ippusbxd, 
saved the "log" file and started it again. After each failed job I have 
turned off and turned on the printer again.

log10 Succeeded
log11 Succeeded
log12 Succeeded
log13 Succeeded
log14 Failed
log20 Succeeded
log21 Succeeded
log22 Succeeded
log23 Succeeded
log24 Failed
log30 Succeeded
log31 Succeeded
log32 Succeeded
log33 Succeeded
log34 Succeeded
log35 Failed

error_log file (with LogLevel=debug) for all the above print jobs:

error_log

Example files:

bashrc
doacao.odt

Binary data which goes to the printer when printing the above example files:

printout-bashrc
printout-doacao

Script to run ipptool for printing a job:

ipptool-print

I have tested on a Ubuntu Vivid (15.04) system with the following 
software versions (some Wily (15.10) packages installed):

ippusbxd: Current GIT snapshot from 
https://github.com/tillkamppeter/ippusbxd
The GIT snapshot (compared to the 1.22 release) adds hex-dumping 
communication content in log output.

CUPS 2.1rc1
cups-filters 1.0.67
HPLIP 3.15.2
Ghostscript 9.16

Printer is the HP DeskJet Ink Advantage 2546 all-in-One

I hope that this information helps.

    Till



[-- Attachment #2: ippusbxd-problem.tar.xz --]
[-- Type: application/x-xz, Size: 619932 bytes --]

  parent reply	other threads:[~2015-09-16 19:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11 17:07 [Printing-architecture] Communication between IPP printer and "ipp" CUPS backend Till Kamppeter
2015-09-15 21:02 ` Till Kamppeter
     [not found]   ` <FB1D5086-D828-40DE-AD16-85293A1C66C4@hp.com>
2015-09-16 19:24     ` Till Kamppeter [this message]
2015-09-16 19:34     ` [Printing-architecture] [cups-devel] " Till Kamppeter
2015-09-21 19:53       ` Till Kamppeter
     [not found]         ` <36CB0E79-9A2E-44E4-AA39-A04101623303@hp.com>
2015-11-20 19:59           ` Till Kamppeter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55F9C1FF.5000307@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=cups-devel@cups.org \
    --cc=danieru.dressler@gmail.com \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=smith.kennedy@hp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.