Printing 'feature'

Robert von Knobloch wrote:

I have found a 'feature' while trying to print a layout.

 

In this layout, I use the "trestrict" layer.

Printing allows the option 'solid' to be selected or not.

If 'solid' is selected (the default), then all is OK.

If 'solid' is deselected (to not obscure some detail) then my HP

laserjet appears to swallow the print job without trace.

 

I have Eagle version 6.5 installed on OpenSuse Linux 12.1, using CUPS,

printing directly (over a TCP socket) to an HP Laserjet CP3525 colour

laser.

 

CUPS insists that the files have printed (data was sent), but no paper

or error or warning appears on either the printer or in CUPS, just no

printout.

 

I imagine that this is a printer problem (it doesn't like the 'hashed'

pattern of trestrict), rather than Eagle, but it might be helpful for

anyone suffering similar problems.

 

I imagine that other HP Laserjets are also affected.

 

Cheers,

 

Bob von Knobloch.

In the CUPS config file (usually /etc/cups/cupsd.conf) you can change the

LogLevel parameter to 'debug', restart CUPS, and it will then dump the

entire print job history of any future print jobs to its log file

(/var/log/cups/error_log or wherever SUSE puts it). If CUPS is failing

silently, examining these detailed logs will typically show where things

went wrong. Don't forget to revert the LogLevel back to the default

(typically 'warn') when done to avoid massive print logs.

Another option is to print to PDF and then, if it actually generated a PDF,

just output the PDF file directly to the printer using lpr.

If you've already tried both of those steps, CUPS doesn't report any

problems, and the printer still doesn't print, then yes, you've run across a

printer bug. I've occasionally run across them on my Brother laser printer's

built-in postscript interpreter as well.

Bob Johnson

On 13/09/13 08:45, Robert Johnson wrote:

Robert von Knobloch wrote:

 

I have found a 'feature' while trying to print a layout.

 

In this layout, I use the "trestrict" layer.

Printing allows the option 'solid' to be selected or not.

If 'solid' is selected (the default), then all is OK.

If 'solid' is deselected (to not obscure some detail) then my HP

laserjet appears to swallow the print job without trace.

 

I have Eagle version 6.5 installed on OpenSuse Linux 12.1, using CUPS,

printing directly (over a TCP socket) to an HP Laserjet CP3525 colour

laser.

 

CUPS insists that the files have printed (data was sent), but no paper

or error or warning appears on either the printer or in CUPS, just no

printout.

 

I imagine that this is a printer problem (it doesn't like the 'hashed'

pattern of trestrict), rather than Eagle, but it might be helpful for

anyone suffering similar problems.

 

I imagine that other HP Laserjets are also affected.

 

Cheers,

 

Bob von Knobloch.

 

In the CUPS config file (usually /etc/cups/cupsd.conf) you can change the

LogLevel parameter to 'debug', restart CUPS, and it will then dump the

entire print job history of any future print jobs to its log file

(/var/log/cups/error_log or wherever SUSE puts it). If CUPS is failing

silently, examining these detailed logs will typically show where things

went wrong. Don't forget to revert the LogLevel back to the default

(typically 'warn') when done to avoid massive print logs.

 

Another option is to print to PDF and then, if it actually generated a PDF,

just output the PDF file directly to the printer using lpr.

 

If you've already tried both of those steps, CUPS doesn't report any

problems, and the printer still doesn't print, then yes, you've run across a

printer bug. I've occasionally run across them on my Brother laser printer's

built-in postscript interpreter as well.

 

Bob Johnson

 

No Bob, it's the printer.

I can capture the Postscript file on the ethernet cable, as it is sent

to the printer. Just no output.

Chees,

Bob

This could be the 'banknote printing prevention' mechanism that many

laser color printers now have, mandatory scanning for the fine hashed

patterns as banknotes typically have. Another government intrusion in IT.

R.

On 13/09/2013 10:03, Robert von Knobloch wrote:

On 13/09/13 08:45, Robert Johnson wrote:

Robert von Knobloch wrote:

 

I have found a 'feature' while trying to print a layout.

 

In this layout, I use the "trestrict" layer.

Printing allows the option 'solid' to be selected or not.

If 'solid' is selected (the default), then all is OK.

If 'solid' is deselected (to not obscure some detail) then my HP

laserjet appears to swallow the print job without trace.

 

I have Eagle version 6.5 installed on OpenSuse Linux 12.1, using CUPS,

printing directly (over a TCP socket) to an HP Laserjet CP3525 colour

laser.

 

CUPS insists that the files have printed (data was sent), but no paper

or error or warning appears on either the printer or in CUPS, just no

printout.

 

I imagine that this is a printer problem (it doesn't like the 'hashed'

pattern of trestrict), rather than Eagle, but it might be helpful for

anyone suffering similar problems.

 

I imagine that other HP Laserjets are also affected.

 

Cheers,

 

Bob von Knobloch.

 

In the CUPS config file (usually /etc/cups/cupsd.conf) you can change the

LogLevel parameter to 'debug', restart CUPS, and it will then dump the

entire print job history of any future print jobs to its log file

(/var/log/cups/error_log or wherever SUSE puts it). If CUPS is failing

silently, examining these detailed logs will typically show where things

went wrong. Don't forget to revert the LogLevel back to the default

(typically 'warn') when done to avoid massive print logs.

 

Another option is to print to PDF and then, if it actually generated a

PDF,

just output the PDF file directly to the printer using lpr.

 

If you've already tried both of those steps, CUPS doesn't report any

problems, and the printer still doesn't print, then yes, you've run

across a

printer bug. I've occasionally run across them on my Brother laser

printer's

built-in postscript interpreter as well.

 

Bob Johnson

 

 

No Bob, it's the printer.

I can capture the Postscript file on the ethernet cable, as it is sent

to the printer. Just no output.

 

Chees,

 

Bob