Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 4 May 2020 01:47:09 +0700
From:      Victor Sudakov <vas@sibptus.ru>
To:        Polytropon <freebsd@edvax.de>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Brother HL-L2340D printer and lpd?
Message-ID:  <20200503184709.GA52059@admin.sibptus.ru>
In-Reply-To: <20200503192444.2d700440.freebsd@edvax.de>
References:  <20200503171259.GA48627@admin.sibptus.ru> <20200503192444.2d700440.freebsd@edvax.de>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

--Kj7319i9nmIyA2yE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Polytropon wrote:
> On Mon, 4 May 2020 00:12:59 +0700, Victor Sudakov wrote:
> > Dear Colleagues,
> >=20
> > I'm trying to use a Brother HL-L2340D printer as a simple networked
> > line printer with lpd. I've successfully used HP and Canon printers like
> > that with a simple printcap like this:
> >=20
> > # by VAS
> > lp|Brother HL-L2340D series:\
> >         :sh:\
> >         :rp=3DTEXT_P1:\
> >         :rm=3D192.168.1.74:sd=3D/var/spool/output/lpd1:lf=3D/var/log/lp=
d-errs:
> >=20
> > but the story with Brother HL-L2340D is different. When fed some input=
=20
> > with "lptest |lpr", it just spits out 3 empty pages. I've never seen
> > anything like that before.
>=20
> It's possible that your previous printers could understand
> regular (unformatted) ASCII text, but the new one doesn't.

I've never seen a network printserver (and I've seen a few) which would
not understand plain ASCII text. I did not even imagine that such an
abomination is at all possible.

It's true, I've heard about GDI winprinters with LPT interfaces,
but a networked printer?=20

>=20
> > I'm wondering if someone has this printer and made it work as a line
> > printer.
> >=20
> >  From the specification at
> > https://support.brother.com/g/b/spec.aspx?c=3Dus&lang=3Den&prod=3Dhll23=
40dw_us_eu_as
> > it should support LPD.
>=20
> It's not a matter of supporting LPD - it's the question which
> printer language the printer can process. The default output
> format for programs is PS. According to the above specification,
> the printer does not understand PS. However, it supports PCL,
> and tools like gs (GhostScript) should be able to convert PS
> to PCL. This is what you need to send to the printer.

Indeed, it probably does not understand PostScript, though it does have
a PostScript queue for some reason.

But what's the point of running an LPD server on port 515/tcp and not
understanding ASCII text? LPD is an acronym of "Line Printer Daemon"
BTW. The text queue is here: https://imgur.com/upHVJ2g.png

>=20
> I assume you're not using CUPS? In this case, a PPD file for
> this printer would probably be the easiest thing, but you can
> get around using CUPS of course.

No, I don't use CUPS, I think it's a monster.

>=20
> Maybe this example can help:
>=20
> First verify that the printer really understands PCL. You can
> use nc (netcat) to send it some data directly. If it works,
> instantiate a simple printer filter in /etc/printcap, for example:

Could you please generate a small one-page PCL file for me so that I
could test it? I suppose I should netcat it to the 9100 (raw) port, right?


--=20
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
2:5005/49@fidonet http://vas.tomsk.ru/

--Kj7319i9nmIyA2yE
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEcBAEBAgAGBQJerxGtAAoJEA2k8lmbXsY0WLMH/3tfUqdeOAWYi+h0nQEMMwxG
X/DI2rq4BIiVPcgQDw33qLQwXj+0E4/x8prLf54gIzIFDwNRXI60Mu6XD/+T5Aa2
H/mvQ91578KO+bhIAM5KQnuHELhUSQFxCb4vf3cGfnNRTwfKm2d20vt+kRXmR2PD
/2Zzotevr28AHQQ9HQOOeYe4deZk4xFoFTXPmjlHDST3Avdc/p2ykFo+GRnTvole
b/2MVDVuGhLIDPuEVGtULmgyMHkMx+byx9G72sqPedYMC+wZAqTU8XXWVKpby/Vn
Y9eY3N67EUkP4Lw0tGzg2ZJ8RTVn6egtXAZ/h41EtBgKN0fDBn9pGo/pXSdj7Vc=
=Un6/
-----END PGP SIGNATURE-----

--Kj7319i9nmIyA2yE--



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20200503184709.GA52059>