Net printing seems to cancel

[lesve]

Environment:
TurboPrint Pro 2.14-1
Ubuntu 9.10
PIXMA 4000R

When I print postscript or pictures. (Where the source is big).
Turboprint seems to send a cancel to the printer just before the
printer is finished.
The picture will crash on the end of the page, or
some lines are missing for postscript files.
It works if I use Canon original drivers in Windows environment so
there would be any problem with PIXMA 4000R.

Can it be somewhere where I can confugure turboprint

/LeSve

[zedonet]

Hello,

there is no "timeout" in TurboPrint, however if the printer is connected by network, there may be a timeout in the network transmission.

For network connection, please use the "bjnp" backend - it should be either listed as a port in TurboPrint Control when you add / edit the printer or you can choose "port"="other" and "uri"="bjnp://<ip-address>".

If the problem also occurs with USB connection, please email the log files "/var/log/turboprint/print.log" and "/var/log/cups/error_log" after such an error - send the files to: mail at zedonet dot de (replace "at" by @ and "dot" by .).

[lesve]

My tpsetup looks like this:
=============================================
Turboprint Setup - Printer Setup <tp0>
=============================================
# Print Jobs : 0
S - Short Name : tp0
L - Long Name : Canon_PIXMA_iP4000R
C - Connection : Local Printer
N - Device Name : bjnp://lpr4000.lesve.org:8611
X - Spool Status : Accepting Jobs = 1
Y - Print Status : Started = 1
Z - Delete all print jobs
R - Remove Printer
Q - Return to main menu

maybe the C-option is wrong ?.

Other choices is:
0 - Local Printer device
1 - File file
2 - Network printer LPD remote
3 - Windows network printer smb
4 - Network printer Socket / Jetdirect socket
5 - Linux network printer (IPP) ipp
6 - other (CUPS URI) uri

Is 2 a good choice ?

[zedonet]

The settings look correct, the "bjnp" backend is already selected.

We noticed a possible timeout problem with bjnp prior to version 0.4.

Please check which version of BJNP you are using e.g. by entering from command line

/usr/lib/cups/backend/bjnp --version

(64bit: /usr/lib64/cups/backend/bjnp --version)

it should be at least "0.4".

You may also try the latest version from

http://cups-bjnp.sourceforge.net/

(the Canon Bubble Jet Network Protocol backend is an open source component that is not maintained by us).

[lesve]

When I try to understand the problem I first saw in the cups log the
following errors:

C [07/Apr/2010:22:36:24 +0200] [Job 21] udpcommand: No data received (select)...
C [07/Apr/2010:22:36:25 +0200] [Job 21] udpcommand: No data received (select)...
C [07/Apr/2010:22:36:26 +0200] [Job 21] udpcommand: No data received (select)...
C [07/Apr/2010:22:36:26 +0200] [Job 21] Received -1 characters on close command, expected 16

I started Wireshark to se whats happening.
During the errors it was an UDP Package with Command "Request Closure"
which did not get a reply from the printer.



Notice that it says Payload Length = 16 but there is no Payload ?????

If I look at the cups-bjnp source (0.5.4) it really do this.
(Payload Length without Payload)

From the source:
set_cmd (&cmd, CMD_UDP_CLOSE, session_id, sizeof (cmd));

Do my printer (PIXMA 4000) dislike this CMD_UDP_CLOSE as it is
Malformed

Note:
Maybe the code line easy can be modified as:
set_cmd (&cmd, CMD_UDP_CLOSE, session_id, 0);

[zedonet]

This sounds plausible - I'll send you a version with the suggested patch by email.

[lesve]

The patch
set_cmd (&cmd, CMD_UDP_CLOSE, session_id, 0);

worked out OK for me. Maybe this patch will solve other problems

/Regards