[sane-devel] [janitorial] New backend: escl (seems to also work via USB)

Till Kamppeter till.kamppeter at gmail.com
Sun Dec 15 19:39:49 GMT 2019

It seems that one can also use the eSCL backend via USB, with the help of the 
IPP-over-USB daemon ippusbxd (the backend is probably not exactly IPP, ippusbxd 
is more to understand as an HTTP-over-USB daemon).

Get ippusbxd from


or install the "ippusbxd" package of your distribution.

Connect your device via USB. Depending on how your distribution is configured it 
can happen that a CUPS queue for the printing part of the device gets created, 
so you will not sacrifice printing to get your scanner to work.

Check with "ps -aux | grep ippusbxd" whether ippusbxd is actually running (an 
auto-created print queue can also be an HPLIP one if the device is from HP).

If ippusbxd is not running, simply fire it up manually, if your device is the 
only IPP-over-USB-capable printer connected to your machine you do not even need 
command line arguments:


The daemon outputs its port and its PID. The port is usually 60000. Now use 
curl, wget, or a browser and access


Correct the port if yours is not 60000.

You get back the capabilities XML list of the eSCL scanning part of your device. 
So it seems that eSCL scanning is possible through ippusbxd.

Note that ippusbxd does not advertise this capability through DNS-SD. The DNS-SD 
record of ippusbxd is completely artifical and is mainly based on the USB 
(printer) device ID. I need to extend the record, but I need a reliable way to 
find out via USB whether the device is only a printer or has also a scanner 

With a deeper look into the source code of HPLIP one can perhaps also find a way 
to use eSCL via USB without ippusbxd but I do not recommend it. With ippusbxd 
one gets both printing and scanning to work in a driverless (driver = 
device-model-specific software and/or data) manner, using the capability of the 
hardware to advertise itself and to provide a full list of capabilities and 
having universal software to do the job (cups-filters for printing and the eSCL 
SANE backend for scanning).

See the output of

wget http://localhost:60000/eSCL/ScannerCapabilities

on my device below.



<?xml version="1.0" encoding="UTF-8"?>

On 15/12/2019 15:54, Till Kamppeter wrote:
>> I didn't see any device managing Tiff, send me the capability file, I could 
>> add the support.
>> curl http://<ip>:<port>/eSCL/ScannerCapabilities
>> or
>> curl -k https://<ip>:<port>/eSCL/ScannerCapabilities
> Below is the output of my HP DeskJet 2540, it seems to only support JPEG and 
> PDF, so the backend should also support PDF (and if SANE does not support PDF, 
> SANE needs either to get appropriately extended (preferred solution) or the 
> backend should convert PDF to TIFF, which would not need a PDF interpreter as 
> this PDF consists only of bitmaps).
> Note that these outputs should not be collected and added to the backend as a 
> database, but rather the backend should poll this from the scanner whenever it 
> is called.
> By the way, the output has PWG in it, so it seems that this eSCL scanning 
> standard was developed by or in cooperation with the Printer Working Group.
>     Till
> ----------
> <!--  -->
> <scan:ScannerCapabilities 
> xmlns:scan="http://schemas.hp.com/imaging/escl/2011/05/03" 

More information about the sane-devel mailing list