[sane-devel] compile problems with scanbd: undefined reference to symbol 'pthread_sigmask@@GLIBC_2.2.5'

2013-01-03 Thread Dominik Kopp
Louis Lagendijk wrote:

 hello
 On Wed, 2013-01-02 at 20:45 +0100, Dominik Kopp wrote:
 There is something wrong with the autoconf configuration that you need
 to solve before you can run
 autoreconf -if
 if you have installed autoconf and libtool (install them first
 otherwise).
 I will check what we are missing in svn to avoid this in the future.
 After running autoreconf, run configure again. If compilation still
 fails, please report back to me and we will work on it.
 
 Kind regards, Louis
 
 

I installed libtool (autoconf 1.12 was already installed) and did the 
autoreconf -if

the ./configure and make fails again with same error message.

I changed also the line 140 in the makefile from automake-1.11 into automake 
1.12, but this doesn't make any differences, too.

regards
Dominik




[sane-devel] compile problems with scanbd: undefined reference to symbol 'pthread_sigmask@@GLIBC_2.2.5'

2013-01-03 Thread Wilhelm
Hi Dominik,

Am 02.01.2013 20:45, schrieb Dominik Kopp:
 Hi,

 I'm trying to complile scanbd inside VirtualBox (host/client both openSUSE
 12.2 64-bit) but I have no success.

 The error message during make is:
 /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../x86_64-suse-linux/bin/ld:
 dbus.o: undefined reference to symbol 'pthread_sigmask@@GLIBC_2.2.5'


 Here are my executed commands with the (hopefully) important parts of the
 output messages:

 dom at linux-8k4r:~ svn co https://scanbd.svn.sourceforge.net/svnroot/scanbd/
 ...
 Ausgecheckt, Revision 132.

 dom at linux-8k4r:~/scanbd/trunk cd scanbd
 dom at linux-8k4r:~/scanbd/trunk cd trunk
 dom at linux-8k4r:~/scanbd/trunk ./configure
 ...
 checking pkg-config is at least version 0.9.0... yes
 checking for CONFUSE... yes
 checking for DBUS... yes
 checking for UDEV... yes
 checking for SANE... no
 checking for sane-config... sane-config
 configure: creating ./config.status
 config.status: creating Makefile
 config.status: creating src/scanbd/Makefile
 ...


 dom at linux-8k4r:~/scanbd/trunk make
   cd .  /bin/sh /home/dom/scanbd/trunk/missing --run automake-1.11 --
 foreign
 /home/dom/scanbd/trunk/missing: Zeile 52: automake-1.11: Kommando nicht
 gefunden.
 WARNING: `automake-1.11' is missing on your system.  You should only need it
 if
   you modified `Makefile.am', `acinclude.m4' or `configure.ac'.
   You might want to install the `Automake' and `Perl' packages.
   Grab them from any GNU archive site.
 CDPATH=${ZSH_VERSION+.}:  cd .  /bin/sh /home/dom/scanbd/trunk/missing
 --run autoconf
 aclocal.m4:17: warning: this file was generated for autoconf 2.68.
 You have another version of autoconf.  It may work, but is not guaranteed
 to.
 If you have problems, you may need to regenerate the build system entirely.
 To do so, use the procedure documented by the package, typically
 `autoreconf'.
 /bin/sh ./config.status --recheck
 running CONFIG_SHELL=/bin/sh /bin/sh ./configure --no-create --no-recursion
 configure: loading site script /usr/share/site/x86_64-unknown-linux-gnu
 checking for a BSD-compatible install... /usr/bin/install -c
 checking whether build environment is sane... yes
 checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
 ...

 gcc -DPACKAGE_NAME=\scanbd\ -DPACKAGE_TARNAME=\scanbd\ -
 DPACKAGE_VERSION=\1.2.1\ -DPACKAGE_STRING=\scanbd\ 1.2.1\ -
 DPACKAGE_BUGREPORT=\wilhelm.meier at fh-kl.de\ -DPACKAGE_URL=\\ -
 DPACKAGE=\scanbd\ -DVERSION=\1.2.1\ -DSTDC_HEADERS=1 -
 DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -
 DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\.libs/\ -DHAVE_ALARM=1 -
 DHAVE_DUP2=1 -DHAVE_FTRUNCATE=1 -DHAVE_GETCWD=1 -DHAVE_MEMSET=1 -
 DHAVE_PUTENV=1 -DHAVE_REGCOMP=1 -DHAVE_STRDUP=1 -DHAVE_STRERROR=1 -
 DHAVE_ARPA_INET_H=1 -DHAVE_FCNTL_H=1 -DHAVE_LIMITS_H=1 -DHAVE_NETINET_IN_H=1
 -DHAVE_SYS_SOCKET_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYSLOG_H=1 -
 DHAVE_UNISTD_H=1 -DHAVE_CHOWN=1 -DHAVE_FORK=1 -DHAVE_VFORK=1 -
 DHAVE_WORKING_VFORK=1 -DHAVE_WORKING_FORK=1 -DHAVE_STDLIB_H=1 -
 DHAVE_MALLOC=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 -DHAVE_LINUX_LIMITS_H=1 -
 DHAVE_UTMP_H=1 -DHAVE_UTMPX_H=1 -DUSE_UDEV=1 -DUSE_SANE=1 -I.-Wall -
 Wextra -
 std=c99 -g  -Werror   -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include
 -DSCANBUTTOND_LIB_DIR=\/usr/local/lib64/scanbd/scanbuttond/backends/\ -
 DSCANBD_CFG_DIR=\/usr/local/etc/scanbd/\   -g -O2 -MT sane.o -MD -MP -MF
 .deps/sane.Tpo -c -o sane.o sane.c
 mv -f .deps/sane.Tpo .deps/sane.Po
 /bin/sh ../../libtool --tag=CC   --mode=link gcc -Wall -Wextra -std=c99 -g
 -Werror   -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include-
 DSCANBUTTOND_LIB_DIR=\/usr/local/lib64/scanbd/scanbuttond/backends/\ -
 DSCANBD_CFG_DIR=\/usr/local/etc/scanbd/\   -g -O2  -lconfuse   -ludev -lrt
 -ldbus-1 -rdynamic -lsane  -L/usr/lib64 -lnetsnmp -lcrypto -lm -ldl  -lm
 -ljpeg  -lgphoto2 -lgphoto2_port -lm -lexif   -lusb-1.0   -o scanbd
 scanbd.o daemonize.o dbus.o udev.o slog.o sane.o   -ldl
 libtool: link: gcc -Wall -Wextra -std=c99 -g -Werror -I/usr/include/dbus-1.0
 -I/usr/lib64/dbus-1.0/include -
 DSCANBUTTOND_LIB_DIR=\/usr/local/lib64/scanbd/scanbuttond/backends/\ -
 DSCANBD_CFG_DIR=\/usr/local/etc/scanbd/\ -g -O2 -rdynamic -o scanbd
 scanbd.o daemonize.o dbus.o udev.o slog.o sane.o  /usr/lib64/libconfuse.so -
 ludev -lrt -ldbus-1 -lsane -L/usr/lib64 /usr/lib64/libnetsnmp.so -lcrypto -
 ljpeg -lgphoto2 -lgphoto2_port -lm -lexif -lusb-1.0 -ldl
 /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../x86_64-suse-linux/bin/ld:
 dbus.o: undefined reference to symbol 'pthread_sigmask@@GLIBC_2.2.5'
 /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../x86_64-suse-linux/bin/ld:
 note: 'pthread_sigmask@@GLIBC_2.2.5' is defined in DSO
 /lib64/libpthread.so.0 so try adding it to the linker command line
 /lib64/libpthread.so.0: could not read symbols: Invalid operation
 collect2: error: 

[sane-devel] single line scanner

2013-01-03 Thread wally
Hello,

i want to use my sane supported flatbed scanner as a ccd single line scanner
for spectroscopy. Therfore i want to disassemble the scanner and position the 
CCD-sensor behind a prisma.

Therefore its necessary to switch off motortransport of the sensor and let 
the CCD-sensor scan continuously  a single line e.g. every second (1Hz)
 Because the CCD-sensor  gets the light to scan from a prisma, its also 
necessary to switch off the lights.

Do you think, such project is possible using sane ?
Do you know a similar effort and/or an url to such a project ?
Any other hint highly welcome. 
 
thank you 
wally  




[sane-devel] Canon Pixma MX375 problem

2013-01-03 Thread Rolf Bensch
Hi Ivan,

Can you please sniff the usb packages on a windows machine (a vm is ok)
of a complete 1200dpi 5mm x 5mm scan using usbsnoop:
http://benoit.papillault.free.fr/usbsnoop/? Then I can have a look at
the 1200 dpi problem.

I cannot help with the ADF problem, sorry.

Cheers,
Rolf



Am 29.12.2012 18:40, schrieb Ivan G.:
 I tried to scan an image at 600 dpi wit xsane, and i didn't found any error. 
 This is the output of xsane:
 
 [pixma] pixma_read_image():completed
 [pixma] Reader task terminated
 
 But if i try to scan at 1200 dpi i receive the ETIMEDOUT problem. This error 
 happen even if i try to scan with ADF (so adf is not working for me). 
 
 Cheers,
 Ivan
 
 
 - Messaggio originale -
 Da: Rolf Bensch rolf at bensch-online.de
 A: Ivan G. dreamos82 at yahoo.it
 Cc: sane-devel at lists.alioth.debian.org sane-devel at 
 lists.alioth.debian.org
 Inviato: Sabato 29 Dicembre 2012 15:56
 Oggetto: Re: Re: [sane-devel] Canon Pixma MX375 problem
 
 Hi Ivan,
 
 Following the installation description also means to install latest sane
 1.0.24 from git.
 
 Your scanner is experimental code in 1.0.23 and you need to create the
 environment variable PIXMA_EXPERIMENT.
 
 Next week I will have a look to the timeout problem.
 
 Last question: Does your scanner scan images above 600 dpi without any
 error and is adf working?
 
 Cheers,
 Rolf
 
 
 Am 28.12.2012 23:24, schrieb Ivan G.:
 Ok, 
 i just managed to have scanimage working, i succesfully scanned an image 
 following suggestions reported here: 
 https://alioth.debian.org/tracker/?group_id0186atidA0366func?tailaid10912


 i simply exported these variables: 

   export PIXMA_EXPERIMENT=export SANE_DEBUG_PIXMA

 And now it seems to work (also with xsane). 
 The only problem now is that sometimes i receive the following timeout 
 error: 

 [pixma] XML message sent to scanner:
 ?xml version=.0 encoding=utf-8 ?cmd 
 xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/;ivec:contentsivec:operationEndJob/ivec:operationivec:param_set
  
 servicetype=scanivec:jobID0001/ivec:jobID/ivec:param_set/ivec:contents/cmd
 [pixma] XML response back from scanner:
 ?xml version=.0 encoding=utf-8 ?
 cmd xmlns:ivec=ttp://www.canon.com/ns/cmd/2008/07/common/
  ivec:contents
  ivec:operationEndJobResponse/ivec:operation
  ivec:param_set servicetype=can
  ivec:responseOK/ivec:response
  ivec:response_detail/
  ivec:jobID0001/ivec:jobID
  /ivec:param_set
  /ivec:contents
 /cmd
 [pixma] pixma_read_image() failed ETIMEDOUT
 [pixma] Reader task terminated: ETIMEDOUT
 [pixma] read_image():reader task closed the pipe:0 bytes received, 1678578 
 bytes expected
 [pixma] pixma_close(): Canon PIXMA MX370 Series

 it seems to verify when the scanner is in sleep mode, that it took 3 or 4 
 seconds to wake-up.

 There is a way to manipulate that timeout?

 @Rolf: 
 I looked on the git version of the README. But still i cannot find anything 
 related to my problem, but it seems that i solved it. 
 That file doesn't contain any helpful information on how to solve my problem.

 Cheers
 Ivan


 - Messaggio originale -
 Da: Rolf Bensch rolf at bensch-online.de
 A: Ivan G. dreamos82 at yahoo.it
 Cc: sane-devel at lists.alioth.debian.org sane-devel at 
 lists.alioth.debian.org
 Inviato: Venerd? 28 Dicembre 2012 20:49
 Oggetto: Re: Re: [sane-devel] Canon Pixma MX375 problem

 Hi Ivan,

 You can find an old version on the website:
 http://www.sane-project.org/README.linux.

 or the latest one in git; fetch a r/o clone with: '$ git clone
 git://git.debian.org/sane/sane-backends.git'.

 Cheers,
 Rolf


 Am 28.12.2012 19:22, schrieb Ivan G.:
 Hi rolf, 

 i lookedd at README.linux, but i cannot find where it can help me. 
 Since:
 1. i installed it using gentoo package manager
 2. the scanner is recognized by sane, but i get the error:
 scanimage: open of device pixma:04A91759_72024A failed: 
 Operation not supported
 3. The usb flag is set for sane package. 

 Or maybe i missed the point with the solution in README.linux? 

 Any other idea? 

 Cheers, 
 Ivan



 - Messaggio originale -
 Da: Rolf Bensch webmaster at bensch-online.de
 A: Ivan Ivello dreamos82 at yahoo.it
 Cc: sane-devel at lists.alioth.debian.org sane-devel at 
 lists.alioth.debian.org
 Inviato: Venerd? 28 Dicembre 2012 14:40
 Oggetto: Re: [sane-devel] Canon Pixma MX375 problem

 Hi Ivan,

 Please follow the installation description in README.linux.

 Cheers,
 Rolf


 Am 27.12.2012 23:26, schrieb Ivan Ivello:
 Hi all, 

 i'm trying configure the Pixma MX375 scanner on gentoo, i followed steps 
 done by Daniel on a previous post (here: 
 http://lists.alioth.debian.org/pipermail/sane-devel/2012-August/030229.html)
  

 I installed sane-backends 1.0.23 with (compiled with  sane_backends_pixma 
 use flag enabled) and activated debug mode. 

 Then sane-find-scanner 

[sane-devel] compile problems with scanbd: undefined reference to symbol 'pthread_sigmask@@GLIBC_2.2.5'

2013-01-03 Thread Dominik Kopp
Wilhelm wrote:

 Hi Dominik,
 
 Am 02.01.2013 20:45, schrieb Dominik Kopp:
 /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../x86_64-suse-
linux/bin/ld:
 dbus.o: undefined reference to symbol 'pthread_sigmask@@GLIBC_2.2.5'
 /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../x86_64-suse-
linux/bin/ld:
 note: 'pthread_sigmask@@GLIBC_2.2.5' is defined in DSO
 /lib64/libpthread.so.0 so try adding it to the linker command line
 /lib64/libpthread.so.0: could not read symbols: Invalid operation
 collect2: error: ld returned 1 exit status make[1]: *** [scanbd] Fehler 1
 make[1]: Leaving directory `/home/dom/scanbd/trunk/src/scanbd'
 make: *** [all-recursive] Fehler 1
 
 looks like -lpthread is missing on openSUSE. 

file /lib64/libpthread.so.0 exists.  (linked to /lib64/libpthread-2.15.so)

 Do you mind trying to
 compile with the Makefile.simple instead of configure?

dom at linux-8k4r:~/scanbd/trunk make -f Makefile.simple
make -f Makefile.simple -C src/scanbd all
make[1]: Entering directory `/home/dom/scanbd/trunk/src/scanbd'
cc   scanbd.o slog.o sane.o daemonize.o dbus.o udev.o  -lsane -ludev -
lconfuse -lpthread -ldbus-1 -o scanbd
make[1]: Leaving directory `/home/dom/scanbd/trunk/src/scanbd'
make -f Makefile.simple -C doc all
make[1]: Entering directory `/home/dom/scanbd/trunk/doc'
echo Generating manpage scanbd.8...;
Generating manpage scanbd.8...
sed  -e 's|@PACKAGEVERSION@|1.2.1|g' \
 -e 's|@PACKAGENAME@|scanbd|g' \
 -e 's|@SBINDIR@|/usr/local/bin|g' \
 -e 's|@SCANBDCFGDIR@|/usr/local/etc/scanbd|g'  scanbd.man scanbd.8
make[1]: Leaving directory `/home/dom/scanbd/trunk/doc'

ok, and where is the binary?  
(this is my fourth or fifth program I'm trying to compile. Therefore I'm not 
very skilled...)


 As safer aproach would be to use scanbd-1.2.1 instead of trunk.

ok, according to the INSTALL file:

dom at linux-8k4r:~/scanbd/releases/1.2.1 USE_SANE=yes make -e clean all
make -C scanbuttond clean
make[1]: Entering directory `/home/dom/scanbd/releases/1.2.1/scanbuttond'
make -C backends clean
make[2]: Entering directory 
`/home/dom/scanbd/releases/1.2.1/scanbuttond/backends'
rm -f *.o *~ *.so
make[2]: Leaving directory 
`/home/dom/scanbd/releases/1.2.1/scanbuttond/backends'
make -C interface clean
make[2]: Entering directory 
`/home/dom/scanbd/releases/1.2.1/scanbuttond/interface'
rm -f *.o *~
make[2]: Leaving directory 
`/home/dom/scanbd/releases/1.2.1/scanbuttond/interface'
rm -f *~
make[1]: Leaving directory `/home/dom/scanbd/releases/1.2.1/scanbuttond'
rm -f -f scanbd test *.o *~
cc  -DUSE_SANE -UUSE_SCANBUTTOND -DUSE_HAL  -c -o scanbd.o scanbd.c
In file included from scanbd.h:45:0,
 from scanbd.c:23:
slog.h:33:1: error: unknown type name ?bool?
In file included from scanbd_dbus.h:33:0,
 from scanbd.h:46,
 from scanbd.c:23:
/usr/include/dbus-1.0/dbus/dbus.h:29:33: fatal error: dbus/dbus-arch-deps.h: 
Datei oder Verzeichnis nicht gefunden
compilation terminated.
make: *** [scanbd.o] Fehler 1


dbus-1-devel package is installed and contains following files:
/usr/include/dbus-1.0/dbus/dbus.h
/usr/lib64/dbus-1.0/include/dbus/dbus-arch-deps.h
...
(full list at http://pkgs.org/opensuse-12.2/opensuse-update-x86_64/dbus-1-
devel-1.5.12-4.10.1.x86_64.rpm.html )

-
then I tried:
dom at linux-8k4r:~/scanbd/releases/1.2.1 make clean all

ok, this is working.

make install does mostly well.

dom at linux-8k4r:~/scanbd/releases/1.2.1 su
Passwort: 
linux-8k4r:/home/dom/scanbd/releases/1.2.1 # make install
echo Make /usr/local/etc/scanbd
Make /usr/local/etc/scanbd
mkdir -p /usr/local/etc/scanbd
echo Copy files to /usr/local/etc/scanbd
Copy files to /usr/local/etc/scanbd
cp scanbd.conf /usr/local/etc/scanbd
cp example.script /usr/local/etc/scanbd
cp scanadf.script /usr/local/etc/scanbd
cp test.script /usr/local/etc/scanbd
echo Copy scanbd to /usr/local/bin
Copy scanbd to /usr/local/bin
mkdir -p /usr/local/bin
cp scanbd /usr/local/bin
echo Copy scanbuttond backends to 
/usr/local/etc/scanbd/scanbuttond/backends
Copy scanbuttond backends to /usr/local/etc/scanbd/scanbuttond/backends
mkdir -p /usr/local/etc/scanbd/scanbuttond/backends
cp scanbuttond/backends/*.so /usr/local/etc/scanbd/scanbuttond/backends || 
/bin/true
cp: Aufruf von stat f?r ?scanbuttond/backends/*.so? nicht m?glich: Datei 
oder Verzeichnis nicht gefunden
echo Copy scanbd_dbus.conf to /etc/dbus-1/system.d/
Copy scanbd_dbus.conf to /etc/dbus-1/system.d/
cp scanbd_dbus.conf /etc/dbus-1/system.d
cp scanbuttond/backends/meta.conf 
/usr/local/etc/scanbd/scanbuttond/backends || /bin/true
echo Edit /etc/inetd.conf
Edit /etc/inetd.conf


is that OK? Should I try to move forward with the next steps as described in  
INSTALL?

regards
Dominik




[sane-devel] Perfection 610: cannot scan in color

2013-01-03 Thread Evil Mr Henry
Basically, scanimage -v -d epson2:libusb:003:005 --format png  
outfile.png works, but scanimage -v --mode color -d 
epson2:libusb:003:005 --format png  outfile.png throws the classic 
invalid argument

(It is, in fact, an Epson Perfection 610 USB scanner.)

This is a new computer; the scanner worked on my old computer in much 
the same setup.

Running Mint (Ubuntu) 64bit, Sane 1.0.22-7ubuntu1

The following is the output after setting export SANE_DEBUG_EPSON2=255:

scanimage -v --mode color -d epson2:libusb:003:005 --format png  
outfile.png
[sanei_debug] Setting debug level of epson2 to 255.
[epson2] sane_epson2_init: sane-backends 1.0.22
[epson2] epson2 backend, version 1.0.124
[epson2] sane_epson2_open: name = libusb:003:005
[epson2] e2_dev_init
[epson2] open_scanner: libusb:003:005
[epson2] scanner opened
[epson2] found valid Epson scanner: 0x4b8/0x103 (vendorID/productID)
[epson2] e2_set_model: model is 'generic'
[epson2] esci_reset
[epson2] e2_cmd_simple: size = 2
[epson2] e2_send: size = 2, reply = 1
[epson2] e2_send: ESC @
[epson2] buf[0] 1b .
[epson2] buf[1] 40 @
[epson2] e2_send: cmd count, r = 0, w = 1
[epson2] e2_recv: size = 1, buf = 0x7fffd8a8144f
[epson2] e2_recv: cmd count, r = 1, w = 1
[epson2] buf[0] 06 .
[epson2] e2_discover_capabilities
[epson2] esci_request_identity
[epson2] e2_cmd_info_block, params len = 2, reply len = 0, buf = 
0x7fffd8a813d8
[epson2] e2_send: size = 2, reply = 0
[epson2] e2_send: ESC I
[epson2] buf[0] 1b .
[epson2] buf[1] 49 I
[epson2] e2_send: cmd count, r = 1, w = 2
[epson2] e2_recv: size = 4, buf = 0x7fffd8a81300
[epson2] e2_recv: cmd count, r = 2, w = 2
[epson2] buf[0] 02 .
[epson2] buf[1] 00 .
[epson2] buf[2] 13 .
[epson2] buf[3] 00 .
[epson2] e2_recv_info_block: payload length: 19
[epson2] e2_recv: size = 19, buf = 0x1ca1fc0
[epson2] e2_recv: cmd count, r = 3, w = 2
[epson2] buf[0] 44 D
[epson2] buf[1] 31 1
[epson2] buf[2] 52 R
[epson2] buf[3] 4b K
[epson2] buf[4] 00 .
[epson2] buf[5] 52 R
[epson2] buf[6] 96 .
[epson2] buf[7] 00 .
[epson2] buf[8] 52 R
[epson2] buf[9] 2c ,
[epson2] buf[10] 01 .
[epson2] buf[11] 52 R
[epson2] buf[12] 58 X
[epson2] buf[13] 02 .
[epson2] buf[14] 41 A
[epson2] buf[15] ec .
[epson2] buf[16] 13 .
[epson2] buf[17] 7c |
[epson2] buf[18] 1b .
[epson2] e2_set_cmd_level: D1
[epson2] e2_add_resolution: add (dpi): 75
[epson2] e2_add_resolution: add (dpi): 150
[epson2] e2_add_resolution: add (dpi): 300
[epson2] e2_add_resolution: add (dpi): 600
[epson2] maximum scan area: 5100x7036
[epson2] e2_set_fbf_area: 0.00,0.00 215.84,297.857330 600 [mm]
[epson2] esci_request_status
[epson2] e2_send: size = 2, reply = 4
[epson2] e2_send: ESC F
[epson2] buf[0] 1b .
[epson2] buf[1] 46 F
[epson2] e2_send: cmd count, r = 3, w = 3
[epson2] e2_recv: size = 4, buf = 0x7fffd8a81340
[epson2] e2_recv: cmd count, r = 4, w = 3
[epson2] buf[0] 02 .
[epson2] buf[1] 00 .
[epson2] buf[2] 00 .
[epson2] buf[3] 00 .
[epson2] status: 00
[epson2]  ready
[epson2]  no option equipment installed
[epson2]  does NOT support extended commands
[epson2] detection with request_extended_status
[epson2] esci_request_extended_status
[epson2] e2_cmd_info_block, params len = 2, reply len = 42, buf = 
0x7fffd8a81380
[epson2] e2_send: size = 2, reply = 46
[epson2] e2_send: ESC f
[epson2] buf[0] 1b .
[epson2] buf[1] 66 f
[epson2] e2_send: cmd count, r = 4, w = 4
[epson2] e2_recv: size = 4, buf = 0x7fffd8a812e0
[epson2] e2_recv: cmd count, r = 5, w = 4
[epson2] buf[0] 02 .
[epson2] buf[1] 00 .
[epson2] buf[2] 2a *
[epson2] buf[3] 00 .
[epson2] e2_recv_info_block: payload length: 42
[epson2] e2_recv: size = 42, buf = 0x1ca2000
[epson2] e2_recv: cmd count, r = 6, w = 4
[epson2] buf[0] 01 .
[epson2] buf[1] 00 .
[epson2] buf[2] 00 .
[epson2] buf[3] 00 .
[epson2] buf[4] 00 .
[epson2] buf[5] 00 .
[epson2] buf[6] 00 .
[epson2] buf[7] 00 .
[epson2] buf[8] 00 .
[epson2] buf[9] 00 .
[epson2] buf[10] 00 .
[epson2] buf[11] 00 .
[epson2] buf[12] 00 .
[epson2] buf[13] 00 .
[epson2] buf[14] 00 .
[epson2] buf[15] 00 .
[epson2] buf[16] 00 .
[epson2] buf[17] 00 .
[epson2] buf[18] 00 .
[epson2] buf[19] 00 .
[epson2] buf[20] 00 .
[epson2] buf[21] 00 .
[epson2] buf[22] 00 .
[epson2] buf[23] 00 .
[epson2] buf[24] 00 .
[epson2] buf[25] 00 .
[epson2] buf[26] 50 P
[epson2] buf[27] 65 e
[epson2] buf[28] 72 r
[epson2] buf[29] 66 f
[epson2] buf[30] 65 e
[epson2] buf[31] 63 c
[epson2] buf[32] 74 t
[epson2] buf[33] 69 i
[epson2] buf[34] 6f o
[epson2] buf[35] 6e n
[epson2] buf[36] 36 6
[epson2] buf[37] 31 1
[epson2] buf[38] 30 0
[epson2] buf[39] 20
[epson2] buf[40] 20
[epson2] buf[41] 20
[epson2] main = 01, ADF = 00, TPU = 00, main 2 = 00
[epson2] e2_set_model: model is 'Perfection610'
[epson2] push button detected
[epson2] no command available to detect capabilities
[epson2] esci_request_identity2
[epson2] e2_cmd_info_block, params len = 2, reply len = 0, buf = 
0x7fffd8a813d8
[epson2] e2_send: size = 2, reply = 0
[epson2] e2_send: ESC i
[epson2] buf[0] 1b .
[epson2] buf[1] 69 i
[epson2] e2_send: cmd