Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.postscript > #3072 > unrolled thread

duplex ?

Back to article view | Back to comp.lang.postscript

Contents

  duplex ? Peter Billam <peter@www.pjb.com.au> - 2017-05-19 05:36 +0000
    Re: duplex ? ken <ken@spamcop.net> - 2017-05-19 07:57 +0100
      Re: duplex ? Peter Billam <peter@www.pjb.com.au> - 2017-05-19 11:40 +0000
        Re: duplex ? ken <ken@spamcop.net> - 2017-05-19 19:19 +0100
          Re: duplex ? tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-05-19 21:26 -0400
            Re: duplex ? Peter Billam <peter@www.pjb.com.au> - 2017-05-21 07:18 +0000
              Re: duplex ? John Reiser <jreiserfl@comcast.net> - 2017-05-23 21:40 -0700

#3072 — duplex ?

Hi.  So I have this Brother HL-5440D printer which is supposed to be
able to print duplex.  But I can't seem to invoke that :-(  I tried:

%%BeginProlog
%%Requirements: duplex
%%IncludeFeature: duplex
%%BeginFeature: duplex
...

without success.  Am I fumbling round in the right place ?
I don't find PLRM very clear on these things.

Peter

-- 
Peter Billam    www.pjb.com.au    www.pjb.com.au/comp/contact.html

[toc] | [next] | [standalone]

#3074

In article <slrnoht13h.2hh.peter@box8.pjb.com.au>, peter@www.pjb.com.au 
says...
> 
> Hi.  So I have this Brother HL-5440D printer which is supposed to be
> able to print duplex.  But I can't seem to invoke that :-(  I tried:
> 
> %%BeginProlog
> %%Requirements: duplex
> %%IncludeFeature: duplex
> %%BeginFeature: duplex
> ...
> 
> without success.  Am I fumbling round in the right place ?

Those lines are all comments, comments are (generally) ignored by the 
PostScript interpreter.

Its not at all obvious to me what you are actually sending to the 
device, just these comments or something else ?

If you are looking at a PostScript file produced by the driver for this 
printer, then somewhere after the "%%BeginFeature" line will be the 
PostScript code which actually implements duplexing. If that is present 
you need to look at it and use that code.


Its unfortunate that you find the PLRM difficult to work with, in my 
experience its one of the best specifications I've read.

Duplexing is clearly defined in the PLRM, assuming your printer conforms 
to the specification in this regard (which is by no means certain) you 
would need to send something like :

<</Duplex true>> setpagedevice

Note that you may also have to set /Tumble in order to get the reverse 
pages properly oriented.



			Ken

[toc] | [prev] | [next] | [standalone]

#3075

On 2017-05-19, ken <ken@spamcop.net> wrote:
>
> Its unfortunate that you find the PLRM difficult to work with,
> in my experience its one of the best specifications I've read.

Yes, it's pretty good.  The best I've ever seen is Programming in Lua,
but that is a totally unfair comparison because Lua is so much leaner.

> Duplexing is clearly defined in the PLRM, assuming your printer conforms 
> to the specification in this regard (which is by no means certain) you 
> would need to send something like :
>    <</Duplex true>> setpagedevice

That itself was very helpful :-) I had been stuck in the DSC section.
So this is my current best-effort test-file :

%!PS-Adobe-3.0
% PLRM ed.2  p. 674
%%Requirements: duplex
%%IncludeFeature: duplex
%%BeginFeature: duplex
%%EndComments
%%BeginProlog
%%EndProlog

% printer description files see pp. 227, 229, 251, 613
% p.235 p.669
%%BeginSetup
%%BeginFeature *Duplex True
<< /Duplex true >> setpagedevice
%%EndFeature
%%EndSetup

%%Page: 1 1
%%BeginPageSetup
%%EndPageSetup
298 421 40 0 360 arc fill
showpage

%%Page: 2 2
%%BeginPageSetup
%%EndPageSetup
298 421 40 0 360 arc stroke
showpage

%%EOF

but it still doesn't print duplex :-(
lpd does see the printer correctly as a HL5440D.

Peter

-- 

Peter Billam    www.pjb.com.au    www.pjb.com.au/comp/contact.html

[toc] | [prev] | [next] | [standalone]

#3076

In article <slrnohtmcq.17r.peter@box8.pjb.com.au>, peter@www.pjb.com.au 
says...

> but it still doesn't print duplex :-(

Not a lot I can szay really, that ought to be enough for a standard 
PostScript implementation. Of course, not all implementations are 
standard.


> lpd does see the printer correctly as a HL5440D.

So you are running Linux ? Any chance you could run a Windows VM, or 
borrow a Windows machine to install the printer driver and see if you 
can get it to work there ?

If so you could capture the PostScirpt and look at it to see what it 
does.

Dumb question but you are sure its a duplex equipped variant ? And the 
duplex unit works ? (I know, it says D, but worth checking)



			Ken

[toc] | [prev] | [next] | [standalone]

#3077

On Fri, 19 May 2017 19:19:09 +0100, ken wrote:

> Dumb question but you are sure its a duplex equipped variant ? And the 
> duplex unit works ? (I know, it says D, but worth checking)

Excellent question. 

I have a monochrome Samsung printer that claims to be a duplexing printer,
but it has no true duplexing mechanism: it does what I can only think to
call "virtual" duplexing, viz., running thr print job through for all *odd*
pages, then prompting the user to run it through again, with the stack of
output pages suitably inverted as input, printing all the even pages.

I have also a Brother HL-1440 (mis-)labeled the same misleading way.

HTH. Cheers, -- tlvp
-- 
Avant de repondre, jeter la poubelle, SVP.

[toc] | [prev] | [next] | [standalone]

#3080

On 2017-05-20, tlvp <mPiOsUcB.EtLlLvEp@att.net> wrote:
> On Fri, 19 May 2017 19:19:09 +0100, ken wrote:
>> Dumb question but you are sure its a duplex equipped variant ?
>> And the duplex unit works ? (I know, it says D, but worth checking)
>
> Excellent question. 
>
> I have a monochrome Samsung printer that claims to be a duplexing printer,
> but it has no true duplexing mechanism: it does what I can only think to
> call "virtual" duplexing, viz., running thr print job through for all *odd*
> pages, then prompting the user to run it through again, with the stack of
> output pages suitably inverted as input, printing all the even pages.
>
> I have also a Brother HL-1440 (mis-)labeled the same misleading way.

Oh.  Er...  Ah well, I didn't Really Need it anyway.
At least I have a plausible test-script.  I can see the driver, in
  /opt/brother/Printers/HL5440D/
which contains four files that mention the word Duplex:
  box8 (debian) ~> cd /opt/brother/Printers/HL5440D/
  box8 (debian) HL5440D> grep Duplex */*
  inf/brHL5440Dfunc:Duplex={OFF}
  inf/brHL5440Dfunc:Duplex Type={Long}
  inf/brHL5440Dfunc:Duplex={OFF,ON}
  inf/brHL5440Dfunc:Duplex Type={Long,Short}
  inf/brHL5440Drc:Duplex=OFF
  inf/brHL5440Drc:DuplexType=Long
  Binary file lpd/brprintconflsr3 matches
  Binary file lpd/rawtobr3 matches

unfortunately the interesting-looking ones are both compiled ELF 32-bit
LSB executables ; there are people who can decompile these things,
but I've never done that.  I can't even invoke rawtobr3 successfully:
  box8 (debian) lpd> ./rawtobr3 duplex.ps
  Error:  :cannot open file !!
but I should be able to work out how that's done from
lpd/filter_HL5440D  which invokes it normally.

Thanks,  Peter

-- 

Peter Billam    www.pjb.com.au    www.pjb.com.au/comp/contact.html

[toc] | [prev] | [next] | [standalone]

#3088

On 05/21/2017 12:18 AM, Peter Billam wrote:

> At least I have a plausible test-script.  I can see the driver, in
>    /opt/brother/Printers/HL5440D/


===== hints from /etc/cups/ppd/HL-5470DW.ppd:
*OpenUI *Duplex/Double-Sided Printing: PickOne
*FoomaticRIPOption Duplex: enum CmdLine A
*OrderDependency: 100 AnySetup *Duplex
*DefaultDuplex: None
*Duplex DuplexNoTumble/On (Flip on Long Edge): "%% FoomaticRIPOptionSetting: Duplex=DuplexNoTumble"
*FoomaticRIPOptionSetting Duplex=DuplexNoTumble: " -dDuplex"
*Duplex DuplexTumble/On (Flip on Short Edge): "%% FoomaticRIPOptionSetting: Duplex=DuplexTumble"
*FoomaticRIPOptionSetting Duplex=DuplexTumble: " -dDuplex -dTumble"
*Duplex None/Off: "%% FoomaticRIPOptionSetting: Duplex=None"
*FoomaticRIPOptionSetting Duplex=None: ""
*CloseUI: *Duplex
=====

Incidentally, note that the hardware margins are 12 points (1/6 inch, 4.23mm) on all sides.
So anything which claims that they are 18 points horizontally and 36 points vertically
(portrait orientation) can/should be corrected.  Search for "18 36" then adjust *4* numbers.

-- 

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.postscript

csiph-web