hp5400backend-devel Mailing List for Scanjet HP5400 family sane backend (Page 2)
Status: Alpha
Brought to you by:
soumarmt
You can subscribe to this list here.
2003 |
Jan
(2) |
Feb
(3) |
Mar
(16) |
Apr
(1) |
May
|
Jun
(16) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(8) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
From: Frank H. <fra...@un...> - 2003-04-04 10:56:17
|
HelloThomas, here is my discription of the installation process. Frank Installation of the hp5400 backend under Suse Linux 8.0: /**/ Download hp5400-sane-backend_20030304.tar.gz /**/ Download sane-backends-1.0.11 // Installation of sane-backends-1.0.11: Unpack sane-backends-1.0.11 (I normaly use ark (kde).): =09tar -xvzf sane-backends-1.0.11.tar.gz Set the directories like in Suse (otherwise read sane-backends-1.0.11/REA= DME): =09./configure --prefix=3D/usr --sysconfdir=3D/etc =09make =09make install (The preinstalled sane package must not be uninstalled. Then you have no=20 problems with rpm- dependencies.) // Installation of hp5400-sane-backend: Unpack hp5400-sane-backend_20030304.tar.gz: in same partition as /usr/lib/sane e.g.: =09tar -xvzC /usr/lib/sane -f hp5400-sane-backend_20030304.tar.gz=20 =09cd /usr/lib/sane/hp5400/ (or make install may not work and you have to copy after make: cp sane-hp5400.so /usr/lib/sane/libsane-hp5400.so.1) modify hp5400/Makefile (you have to insert the right path of course) (ned= it=20 Makefile): SANE_BACKEND_SRC=3D/home/frank/sane-backends-1.0.11 and SANE_LIBS_DIR=3D/usr/lib/sane =09make =09make install Modify hp5400.conf (nedit hp5400.conf): #Linux: /dev/usbscanner cp hp5400.conf /etc/sane.d Add line in dll.conf (nedit /etc/sane.d/dll.conf): hp5400 Check if /dev/usbscanner exists: =09ls /dev/usb* Check if the "scanner" kernel module is loaded: =09lsmod usbcore 55136 1 [scanner usb-ohci] scanner 8480 0=20 If not add in /etc/modules.conf: alias /dev/usbscanner scanner options scanner vendor=3D0x3f0 product=3D0x1105 =09modprobe scanner For more convenience (module loaded at bootup) add in /etc/init.d/boot.lo= cal: modprobe scanner Checks: Scanner attached to the usbport?: =09lsusb Scanner recognised by sane?: =09sane-find-scanner Scanner supported by sane: =09scanimage -L If sane-find-scanner finds the scanner and scanimage not, try =09scanimage -d hp5400:/dev/usbscanner > out.pnm =09(check the image with "gimp out.pnm" e.g.) or =09xsane hp5400:/dev/usbscanner If this works something is wrong with /etc/sane.d/dll.conf or=20 /etc/sane.d/hp5400.conf. Frank Heuser fra...@un... hp5...@li... |
From: Wes M. <mor...@co...> - 2003-03-23 01:13:13
|
My HP5400c is up and running. Thanks for working on this! Just a small question. I wanted to try to do a little OCR work with my scanner. For this purpose, I thought it would be good to scan in Lineart mode. Am I right in thinking that this mode is not yet available? Or is there something I've missed? Thanks in advance for any help you can give me. Wes |
From: <hp5...@un...> - 2003-03-16 20:30:27
|
Thanks, I got it working now too... but two things: 1) You need to adjust the brightness (like said in the thread) to get a=20 not-blue images 2) The RGB seems to be moved from eachother when you zoom in. If you scan= a=20 black line, you see a red, green and blue line in the zoom-in. But... great work on the backend... thanks a lot. Jeroen On Monday 10 March 2003 20:39, Kevin DeKorte wrote: > Jeroen, > > Read this thread and that should answer your questions > > https://sourceforge.net/mailarchive/forum.php?thread_id=3D1796241&forum= _id=3D24 >635 > > Kevin > > On Sunday 09 March 2003 10:09 am, hp5...@un... wrote: > > Hey, > > This is my first time try of connecting a scanner to linux. I have a > > HP5400, connected with the USB cable to my RH8 machine. I think it ha= s > > sane 1.0.8 with XSane. I compiled and installed the backend, but some= how > > Xsane still doesnt recognize my scanner. Is anyone able to help me a > > little, because I dont know if my scanner responds, if sane is config= ured > > right, etc. etc. Simply because I dont have the commands for it. > > > > Jeroen > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Etnus, makers of TotalView, The > > debugger for complex code. Debugging C/C++ programs can leave you fee= ling > > lost and disoriented. TotalView can help you find your way. Available= on > > major UNIX and Linux platforms. Try it free. www.etnus.com > > _______________________________________________ > > Hp5400backend-devel mailing list > > Hp5...@li... > > https://lists.sourceforge.net/lists/listinfo/hp5400backend-devel > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Hp5400backend-devel mailing list > Hp5...@li... > https://lists.sourceforge.net/lists/listinfo/hp5400backend-devel |
From: Kevin D. <kde...@ya...> - 2003-03-10 19:39:07
|
Jeroen, Read this thread and that should answer your questions https://sourceforge.net/mailarchive/forum.php?thread_id=1796241&forum_id=24635 Kevin On Sunday 09 March 2003 10:09 am, hp5...@un... wrote: > Hey, > This is my first time try of connecting a scanner to linux. I have a > HP5400, connected with the USB cable to my RH8 machine. I think it has sane > 1.0.8 with XSane. I compiled and installed the backend, but somehow Xsane > still doesnt recognize my scanner. Is anyone able to help me a little, > because I dont know if my scanner responds, if sane is configured right, > etc. etc. Simply because I dont have the commands for it. > > Jeroen > > > ------------------------------------------------------- > This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger > for complex code. Debugging C/C++ programs can leave you feeling lost and > disoriented. TotalView can help you find your way. Available on major UNIX > and Linux platforms. Try it free. www.etnus.com > _______________________________________________ > Hp5400backend-devel mailing list > Hp5...@li... > https://lists.sourceforge.net/lists/listinfo/hp5400backend-devel |
From: <hp5...@un...> - 2003-03-09 16:55:17
|
Hey, This is my first time try of connecting a scanner to linux. I have a HP54= 00,=20 connected with the USB cable to my RH8 machine. I think it has sane 1.0.8= =20 with XSane. I compiled and installed the backend, but somehow Xsane still= =20 doesnt recognize my scanner. Is anyone able to help me a little, because = I=20 dont know if my scanner responds, if sane is configured right, etc. etc.=20 Simply because I dont have the commands for it. Jeroen |
From: Kevin D. <kde...@ya...> - 2003-03-08 14:58:14
|
Thomas, Success! I have found two places in the code where this commenting out nee= ds=20 to be done. After that things worked really well. I used xsane to preview.=20 I scanned at 75dpi,300dpi,600dpi and 1200dpi Only problem was that the image was a little blue. I had to up the brightne= ss=20 to about 50 to get "white" This makes me VERY happy to see this working and I appreciate all your work= =2E=20 The only thing I have left that needs windows is my camera now.. And the=20 gphoto team is working on that.=20 Kevin Author: mplayerplug-in http://mplayerplug-in.sf.net On Friday 07 March 2003 03:41 pm, Thomas Soumarmon wrote: > Hi, > > your problem is now that the version string sent by the scanner does not > match the ones we've got in development. > > You have to modify the C code in hp5400.c to be able to run the backend. > The scanner is queried about a version string which is typically : > 'SilitekIBlizd C3 ScannerV0.84' or 'SilitekIBlizd C3 ScannerV0.86' on the > scanner we tested. > You may disable this test, changing > > if( memcmp( szVersion+1, MatchVersion, sizeof(MatchVersion)-1 ) ) > { > if( memcmp( szVersion+1, MatchVersion2, sizeof(MatchVersion2)-1 ) ) > { > DBG(DBG_MSG, "Sorry, unknown scanner version. Attempted match on '%= s' > and '%s'\n", MatchVersion, MatchVersion2 ); > DBG(DBG_MSG, "Vesion is '%s'", szVersion ); > ret =3D -1; > goto hp5400_close_exit; > } > } > > into : > > #ifdef 0 > if( memcmp( szVersion+1, MatchVersion, sizeof(MatchVersion)-1 ) ) > { > if( memcmp( szVersion+1, MatchVersion2, sizeof(MatchVersion2)-1 ) ) > { > DBG(DBG_MSG, "Sorry, unknown scanner version. Attempted match on '%= s' > and '%s'\n", MatchVersion, MatchVersion2 ); > DBG(DBG_MSG, "Vesion is '%s'", szVersion ); > ret =3D -1; > goto hp5400_close_exit; > } > } > #endif > > Note that you would be the first one to test it with your version of the > scanner. It should work but as the versions of the internal chipset are > different it may not. > > Anyway I have added just now a similar patch in the CVS. > To disable the version test, look in the Makefile for > NO_STRING_VERSION_MATCH. > > > Thomas. > > Le Vendredi 7 Mars 2003 21:13, Kevin DeKorte a =C3=A9crit : > > Ok, > > > > Made some progress... > > > > just a a note the modprobe line should be > > > > #added for HP5470 scanner > > alias /dev/usb/scanner0 scanner > > options scanner vendor=3D0x3f0 product=3D0x1005 > > > > the product version was off > > > > So now I am getting closer I have this error > > > > SANE_DEBUG_HP5400=3D255 scanimage > > [sanei_debug] Setting debug level of hp5400 to 255. > > [hp5400] sane_init > > [hp5400] Reading config file > > [hp5400] vendor/product 0x03F0-0x1005 > > [hp5400] Read: reqtype =3D 0xC0, req =3D 0x04, value =3D 1200 > > [hp5400] Read: reqtype =3D 0xC0, req =3D 0x04, value =3D C500 > > [hp5400] Command 12 verified > > [hp5400] Sorry, unknown scanner version. Attempted match on > > 'SilitekIBlizd C3 ScannerV0.84' and 'SilitekIBlizd C3 ScannerV0.86' > > [hp5400] Vesion is ''[hp5400] sane_get_devices > > scanimage: no SANE devices found > > [hp5400] sane_exit > > > > > > > > Kevin > > > > On Friday 07 March 2003 12:29 pm, Thomas Soumarmon wrote: > > > Hi, > > > > > > > > > > > > (snip) > > > > > > > [hp5400] Reading config file > > > > [hp5400] Using usb 0x03f0 0x1005 as device file > > > > [hp5400] vendor/product 0x0000-0x0000 > > > > [hp5400] hp5400_open failed > > > > [hp5400] sane_open: > > > > Segmentation fault > > > > > > Here you should have : > > > [hp5400] vendor/product 0x03f0 0x1005 > > > That is because of the hp5400.conf (see below) > > > > > > > in hp5400.conf I have > > > > usb 0x03f0 0x1005 > > > > > > in hp5400.conf don't put anything to use default device selection > > > > > > (snip) > > > > > > > hub.c: USB new device connect on bus1/1, assigned device number 19 > > > > usb.c: USB device 19 (vend/prod 0x3f0/0x1005) is not claimed by any > > > > active driver. > > > > > > Module scanner is not loaded. It should handle the USB device. Add > > > those lines to /etc/modules.conf : > > > #added for HP5470 scanner > > > alias /dev/usb/scanner0 scanner > > > options scanner vendor=3D0x3f0 product=3D0x1105 > > > > > > then run > > > modprobe > > > to launch the scanner module > > > > > > > Any ideas where I should look? Could it be a permission issue? > > > > > > I think it should work now. > > > > > > > > > Thomas. > > > > > > > > > ------------------------------------------------------- > > > This SF.net email is sponsored by: Etnus, makers of TotalView, The > > > debugger for complex code. Debugging C/C++ programs can leave you > > > feeling lost and disoriented. TotalView can help you find your way. > > > Available on major UNIX and Linux platforms. Try it free. www.etnus.c= om > > > _______________________________________________ > > > Hp5400backend-devel mailing list > > > Hp5...@li... > > > https://lists.sourceforge.net/lists/listinfo/hp5400backend-devel > > ------------------------------------------------------- > This SF.net email is sponsored by: Etnus, makers of TotalView, The debugg= er > for complex code. Debugging C/C++ programs can leave you feeling lost and > disoriented. TotalView can help you find your way. Available on major UNIX > and Linux platforms. Try it free. www.etnus.com > _______________________________________________ > Hp5400backend-devel mailing list > Hp5...@li... > https://lists.sourceforge.net/lists/listinfo/hp5400backend-devel |
From: Thomas S. <sou...@ne...> - 2003-03-07 22:42:58
|
Hi, your problem is now that the version string sent by the scanner does not = match=20 the ones we've got in development. You have to modify the C code in hp5400.c to be able to run the backend. The scanner is queried about a version string which is typically : 'SilitekIBlizd C3 ScannerV0.84' or 'SilitekIBlizd C3 ScannerV0.86' on the= =20 scanner we tested. You may disable this test, changing if( memcmp( szVersion+1, MatchVersion, sizeof(MatchVersion)-1 ) ) { if( memcmp( szVersion+1, MatchVersion2, sizeof(MatchVersion2)-1 ) ) { DBG(DBG_MSG, "Sorry, unknown scanner version. Attempted match on '%= s'=20 and '%s'\n", MatchVersion, MatchVersion2 ); DBG(DBG_MSG, "Vesion is '%s'", szVersion ); ret =3D -1; goto hp5400_close_exit; } } into : #ifdef 0 if( memcmp( szVersion+1, MatchVersion, sizeof(MatchVersion)-1 ) ) { if( memcmp( szVersion+1, MatchVersion2, sizeof(MatchVersion2)-1 ) ) { DBG(DBG_MSG, "Sorry, unknown scanner version. Attempted match on '%= s'=20 and '%s'\n", MatchVersion, MatchVersion2 ); DBG(DBG_MSG, "Vesion is '%s'", szVersion ); ret =3D -1; goto hp5400_close_exit; } } #endif Note that you would be the first one to test it with your version of the=20 scanner. It should work but as the versions of the internal chipset are=20 different it may not.=20 Anyway I have added just now a similar patch in the CVS.=20 To disable the version test, look in the Makefile for NO_STRING_VERSION_M= ATCH. Thomas. Le Vendredi 7 Mars 2003 21:13, Kevin DeKorte a =E9crit : > Ok, > > Made some progress... > > just a a note the modprobe line should be > > #added for HP5470 scanner > alias /dev/usb/scanner0 scanner > options scanner vendor=3D0x3f0 product=3D0x1005 > > the product version was off > > So now I am getting closer I have this error > > SANE_DEBUG_HP5400=3D255 scanimage > [sanei_debug] Setting debug level of hp5400 to 255. > [hp5400] sane_init > [hp5400] Reading config file > [hp5400] vendor/product 0x03F0-0x1005 > [hp5400] Read: reqtype =3D 0xC0, req =3D 0x04, value =3D 1200 > [hp5400] Read: reqtype =3D 0xC0, req =3D 0x04, value =3D C500 > [hp5400] Command 12 verified > [hp5400] Sorry, unknown scanner version. Attempted match on 'SilitekIBl= izd > C3 ScannerV0.84' and 'SilitekIBlizd C3 ScannerV0.86' > [hp5400] Vesion is ''[hp5400] sane_get_devices > scanimage: no SANE devices found > [hp5400] sane_exit > > > > Kevin > > On Friday 07 March 2003 12:29 pm, Thomas Soumarmon wrote: > > Hi, > > > > > > > > (snip) > > > > > [hp5400] Reading config file > > > [hp5400] Using usb 0x03f0 0x1005 as device file > > > [hp5400] vendor/product 0x0000-0x0000 > > > [hp5400] hp5400_open failed > > > [hp5400] sane_open: > > > Segmentation fault > > > > Here you should have : > > [hp5400] vendor/product 0x03f0 0x1005 > > That is because of the hp5400.conf (see below) > > > > > in hp5400.conf I have > > > usb 0x03f0 0x1005 > > > > in hp5400.conf don't put anything to use default device selection > > > > (snip) > > > > > hub.c: USB new device connect on bus1/1, assigned device number 19 > > > usb.c: USB device 19 (vend/prod 0x3f0/0x1005) is not claimed by any > > > active driver. > > > > Module scanner is not loaded. It should handle the USB device. Add th= ose > > lines to /etc/modules.conf : > > =09#added for HP5470 scanner > > =09alias /dev/usb/scanner0 scanner > > =09options scanner vendor=3D0x3f0 product=3D0x1105 > > > > then run > > =09modprobe > > to launch the scanner module > > > > > Any ideas where I should look? Could it be a permission issue? > > > > I think it should work now. > > > > > > Thomas. > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Etnus, makers of TotalView, The > > debugger for complex code. Debugging C/C++ programs can leave you fee= ling > > lost and disoriented. TotalView can help you find your way. Available= on > > major UNIX and Linux platforms. Try it free. www.etnus.com > > _______________________________________________ > > Hp5400backend-devel mailing list > > Hp5...@li... > > https://lists.sourceforge.net/lists/listinfo/hp5400backend-devel |
From: Kevin D. <kde...@ya...> - 2003-03-07 20:53:04
|
Ok, Made some progress... just a a note the modprobe line should be #added for HP5470 scanner alias /dev/usb/scanner0 scanner options scanner vendor=0x3f0 product=0x1005 the product version was off So now I am getting closer I have this error SANE_DEBUG_HP5400=255 scanimage [sanei_debug] Setting debug level of hp5400 to 255. [hp5400] sane_init [hp5400] Reading config file [hp5400] vendor/product 0x03F0-0x1005 [hp5400] Read: reqtype = 0xC0, req = 0x04, value = 1200 [hp5400] Read: reqtype = 0xC0, req = 0x04, value = C500 [hp5400] Command 12 verified [hp5400] Sorry, unknown scanner version. Attempted match on 'SilitekIBlizd C3 ScannerV0.84' and 'SilitekIBlizd C3 ScannerV0.86' [hp5400] Vesion is ''[hp5400] sane_get_devices scanimage: no SANE devices found [hp5400] sane_exit Kevin On Friday 07 March 2003 12:29 pm, Thomas Soumarmon wrote: > Hi, > > > > (snip) > > > [hp5400] Reading config file > > [hp5400] Using usb 0x03f0 0x1005 as device file > > [hp5400] vendor/product 0x0000-0x0000 > > [hp5400] hp5400_open failed > > [hp5400] sane_open: > > Segmentation fault > > Here you should have : > [hp5400] vendor/product 0x03f0 0x1005 > That is because of the hp5400.conf (see below) > > > in hp5400.conf I have > > usb 0x03f0 0x1005 > > in hp5400.conf don't put anything to use default device selection > > (snip) > > > hub.c: USB new device connect on bus1/1, assigned device number 19 > > usb.c: USB device 19 (vend/prod 0x3f0/0x1005) is not claimed by any > > active driver. > > Module scanner is not loaded. It should handle the USB device. Add those > lines to /etc/modules.conf : > #added for HP5470 scanner > alias /dev/usb/scanner0 scanner > options scanner vendor=0x3f0 product=0x1105 > > then run > modprobe > to launch the scanner module > > > Any ideas where I should look? Could it be a permission issue? > > I think it should work now. > > > Thomas. > > > ------------------------------------------------------- > This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger > for complex code. Debugging C/C++ programs can leave you feeling lost and > disoriented. TotalView can help you find your way. Available on major UNIX > and Linux platforms. Try it free. www.etnus.com > _______________________________________________ > Hp5400backend-devel mailing list > Hp5...@li... > https://lists.sourceforge.net/lists/listinfo/hp5400backend-devel |
From: Thomas S. <sou...@ne...> - 2003-03-07 19:31:06
|
Hi, (snip) > [hp5400] Reading config file > [hp5400] Using usb 0x03f0 0x1005 as device file > [hp5400] vendor/product 0x0000-0x0000 > [hp5400] hp5400_open failed > [hp5400] sane_open: > Segmentation fault Here you should have : [hp5400] vendor/product 0x03f0 0x1005 That is because of the hp5400.conf (see below) > in hp5400.conf I have > usb 0x03f0 0x1005 in hp5400.conf don't put anything to use default device selection (snip) > hub.c: USB new device connect on bus1/1, assigned device number 19 > usb.c: USB device 19 (vend/prod 0x3f0/0x1005) is not claimed by any act= ive > driver. > Module scanner is not loaded. It should handle the USB device. Add those = lines=20 to /etc/modules.conf : =09#added for HP5470 scanner =09alias /dev/usb/scanner0 scanner =09options scanner vendor=3D0x3f0 product=3D0x1105 then run =09modprobe to launch the scanner module > Any ideas where I should look? Could it be a permission issue? I think it should work now. Thomas. |
From: Kevin D. <kde...@ya...> - 2003-03-07 18:03:44
|
Hello, Hey thanks for working on the driver. I compiled via CVS today for the first time. I am getting this error SANE_DEBUG_HP5400=255 scanimage -d hp5400 [sanei_debug] Setting debug level of hp5400 to 255. [hp5400] sane_init [hp5400] Reading config file [hp5400] Using usb 0x03f0 0x1005 as device file [hp5400] vendor/product 0x0000-0x0000 [hp5400] hp5400_open failed [hp5400] sane_open: Segmentation fault My dll.conf I added hp5400 in hp5400.conf I have usb 0x03f0 0x1005 sane backed is scanimage -V scanimage (sane-backends) 1.0.11; backend version 1.0.11 sane-find-scanner -q found USB scanner (vendor=0x03f0, product=0x1005) at libusb:001:019 dmesg stuff hub.c: USB new device connect on bus1/1, assigned device number 19 usb.c: USB device 19 (vend/prod 0x3f0/0x1005) is not claimed by any active driver. Any ideas where I should look? Could it be a permission issue? Kevin |
From: Martijn v. O. <kl...@sv...> - 2003-03-06 10:45:32
|
On Thu, Mar 06, 2003 at 11:17:51AM +0100, Thomas Soumarmon wrote: > Hi, >=20 > Bertrik was right about the problem of calibration for high resolution sc= ans.=20 > I enlarged the calibration data sent, depending on dpi and it works bette= r. > There are still small vertical black areas =3D> calibration data is not c= orrect. > Anyway, calibration data have to be fully computed because currently it i= s the=20 > same small amount of data replicated as much as needed. Yep, that'd be because the calibration data has areas with zeros which represent the areas outside the glass. By repeating the same data you'll get black areas in the middle of the picture. > It seems that 2400 dpi is broken so I disabled the 2400 dpi option of the= gui=20 > for the moment. You have to define SUPPORT_2400_DPI in sane-hp5400.c to h= ave=20 > it back. Yep, the Xsize value from the scanner overflows. I'm about to commit a fix for that. In theory the Yvalue can also overflow but I havn't seen what happens there. > I commited the changes as it makes the scanner works better with 1200 dpi= .=20 > I'll have a look later to see how to calculate the correct data of the=20 > calibration. Well, 600dpi looks good so far. --=20 Martijn van Oosterhout <kl...@sv...> http://svana.org/kleptog/ > Support bacteria! They're the only culture some people have. |
From: Thomas S. <sou...@ne...> - 2003-03-06 10:19:07
|
Hi, Bertrik was right about the problem of calibration for high resolution sc= ans.=20 I enlarged the calibration data sent, depending on dpi and it works bette= r. There are still small vertical black areas =3D> calibration data is not c= orrect. Anyway, calibration data have to be fully computed because currently it i= s the=20 same small amount of data replicated as much as needed. It seems that 2400 dpi is broken so I disabled the 2400 dpi option of the= gui=20 for the moment. You have to define SUPPORT_2400_DPI in sane-hp5400.c to h= ave=20 it back. I commited the changes as it makes the scanner works better with 1200 dpi= =2E=20 I'll have a look later to see how to calculate the correct data of the=20 calibration. Have a nice day, Thomas. |
From: Thomas S. <sou...@ne...> - 2003-03-05 12:53:59
|
Hello everybody, Colour offset problem seems to be fixed now. It looks that it was corrected twice. Maybe the second time was by the sc= anner=20 itself when the request type is set to "not preview" ? Anyway, I commited the small change and it looks OK until 600 dpi. Next alpha version will be released by friday. You can get C sources directly from the sourceforge CVS : cvs -d:pserver:ano...@cv...:/cvsroot/hp5400backend login= =20 cvs -d:pserver:ano...@cv...:/cvsroot/hp5400backend co=20 hp5400/hp5400 By the way, there is a new mailing list used to monitor the modifications= made=20 in the CVS repository :=20 hp5...@li... Have a nice day, Thomas. |
From: Martijn v. O. <kl...@sv...> - 2003-03-05 00:44:15
|
On Tue, Mar 04, 2003 at 07:23:06PM +0100, Thomas Soumarmon wrote: > > Problems with scrambled images could be caused by an overflow of the > > internal data buffer (at least that's what I found with niash12/14/19 > > chips). In that case, you should be able to correlate this to backtrack= ing > > (quickly moving back and forth of the lamp). > > Do the scrambled images also occur if you scan only a narrow vertical > > strip? >=20 > At first I thought you would be right but even with a narrow vertival str= ip,=20 > most pixels are "absent". I'll send you on a separate mail a tiny part of= the=20 > vertical strip. It shows colored vertical lines (red and green). > It might be related to the query sent to the scanner. We have to check if= all=20 > the flags are correct. I need to do some scans in windows at higher resolutions to see if any other flags get turned on. Unfortunatly I havn't found a way to trap *all* the data going over the USB link. My theory on the colour corruption is one of two things: 1. Some kind of internal buffer length. In other words, when the line length exceeds a certain amount it breaks into multiple blocks per line. 2. Since the intrinsic resolution of the scanner is only 300dpi, for everything higher it needs to move the head from side to side (I don't know if this is true, but it makes an odd sound at higher res). So this means that if it's sending data back in order that instead of the normal: Red (row x) Green (row x+k) Blue (row x+2k) that instead it's sending: Red (row x, pixels 0,8,16,24,...) Green (row x+k, pixels 0,8,16,24,...) Blue (row x+2k, pixels 0,8,16,24,...) Red (row x, pixels 1,9,17,25,...) Green (row x+k, pixels 1,9,17,25,...) Blue (row x+2k, pixels 1,9,17,25,...) etc If this is true then it's going to *very* interesting to sort that out. Does this have any precedent or am I making this up? --=20 Martijn van Oosterhout <kl...@sv...> http://svana.org/kleptog/ > Support bacteria! They're the only culture some people have. |
From: Thomas S. <sou...@ne...> - 2003-03-04 18:24:19
|
> >Martijn have done more great work those days. It is still an alpha ver= sion > > as it is not full featured and there are still two major bugs : > >* the image goes fuzzier as the resolution increases > >* 1200 and 2400 dpi images are scrambled. > >Except of that, 75 and 150 dpi are working pretty well. > > What do you mean by fuzzier? > Is this the problem of vertical shift between separate color components > (R G B)? Yes. That point is "under control" as we know how to correct it during th= e=20 image composition, reading colors on separate lines. > > Problems with scrambled images could be caused by an overflow of the > internal data buffer (at least that's what I found with niash12/14/19 > chips). In that case, you should be able to correlate this to backtrack= ing > (quickly moving back and forth of the lamp). > Do the scrambled images also occur if you scan only a narrow vertical > strip? At first I thought you would be right but even with a narrow vertival str= ip,=20 most pixels are "absent". I'll send you on a separate mail a tiny part of= the=20 vertical strip. It shows colored vertical lines (red and green). It might be related to the query sent to the scanner. We have to check if= all=20 the flags are correct. Thank you again for sharing your experience and for your help. Thomas. |
From: Bertrik S. <be...@zo...> - 2003-03-04 18:07:41
|
Thomas Soumarmon wrote: >Hi everybody, > >Martijn have done more great work those days. It is still an alpha version as >it is not full featured and there are still two major bugs : >* the image goes fuzzier as the resolution increases >* 1200 and 2400 dpi images are scrambled. >Except of that, 75 and 150 dpi are working pretty well. > What do you mean by fuzzier? Is this the problem of vertical shift between separate color components (R G B)? Problems with scrambled images could be caused by an overflow of the internal data buffer (at least that's what I found with niash12/14/19 chips). In that case, you should be able to correlate this to backtracking (quickly moving back and forth of the lamp). Do the scrambled images also occur if you scan only a narrow vertical strip? Kind regards, Bertrik |
From: Thomas S. <sou...@ne...> - 2003-03-04 09:07:24
|
Hi everybody, Martijn have done more great work those days. It is still an alpha versio= n as=20 it is not full featured and there are still two major bugs :=20 * the image goes fuzzier as the resolution increases=20 * 1200 and 2400 dpi images are scrambled. Except of that, 75 and 150 dpi are working pretty well. The release is downloadable at http://sourceforge.net/projects/hp5400back= end/ The most significant modifications are : - improved calibration - implemented gamma correction - Add support for new SCANOFFSET command 0xE700. This means we can remove all the options relating to offsets in xsane itself. This might require adjustment depending on the model of scanner. - Add support for the two kinds of types of scan requests. This is what controls whether to use the scan offsets. - Add a ScanType parameter so we can distinguish between previews and nor= mal scans. In future we'll use this to control the scan speed. - Add code to protect the scanner against silly mistakes. It will restric= t your scan area to the glass and no more.=20 Have a nice day, Thomas. |
From: Thomas S. <sou...@ne...> - 2003-02-28 07:37:17
|
Hi, We did not test the direct loading of the backend. Since now we've done i= t=20 using dll.conf file redirecting to the hp5400 backend : edit dll.conf that should be in /usr/local/etc/sane.d/ or /etc/sane.d/ add the line hp5400 and try rerun the scanimage or xsane However you can do : SANE_DEBUG_HP5400=3D255 scanimage -d hp5400 to have a debug log Thank you for reporting successes and failures of the alpha releases. Le Vendredi 28 F=E9vrier 2003 03:15, vous avez =E9crit : > First I configured Makefile and hp5400.conf...sorry for my poor english= :) > root@debian:~/hp5400# make > gcc -Wall -O2 -g -DV_MAJOR=3D1 -DV_MINOR=3D0 -fPIC > -I/root/sane-backends-1.0.11/include -c -DSTANDALONE -o hp5400_scanner.= o > hp5400_scanner.c > gcc -Wall -O2 -g -DV_MAJOR=3D1 -DV_MINOR=3D0 -fPIC > -I/root/sane-backends-1.0.11/include -c -DSTANDALONE -o hp5400.o hp5400= =2Ec > gcc -lm -o hp5400 hp5400_scanner.o hp5400.o > gcc -Wall -O2 -g -DV_MAJOR=3D1 -DV_MINOR=3D0 -fPIC > -I/root/sane-backends-1.0.11/include -c -o sane-hp5400.o sane-hp5400.= c > gcc -lm -shared -fPIC -Wl,-soname -Wl,libsane.so.1 -o sane-hp5400.so > sane-hp5400.o > root@debian:~/hp5400# make install > rm -f /usr/local/lib/sane/libsane-hp5400.so.1 > ln `pwd`/sane-hp5400.so /usr/local/lib/sane/libsane-hp5400.so.1 > > root@debian:~# dpkg -l libusb-0.1-4 > Desired=3DUnknown/Install/Remove/Purge/Hold > > | Status=3DNot/Installed/Config-files/Unpacked/Failed-config/Half-insta= lled > |/ Err?=3D(none)/Hold/Reinst-required/X=3Dboth-problems (Status,Err: > > uppercase=3Dbad) > > ||/ Name Version Description > > +++-=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D-=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D-=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=3D=3D=3D ii libusb-0.1-4 0.1.6a-2.1 Userspace USB programming li= brary > > root@debian:~# scanimage -V > scanimage (sane-backends) 1.0.11; backend version 1.0.11 > > root@debian:~# ll /usr/local/lib/sane/libsane-hp5400.so.1 > -rwxr-xr-x 2 root root 66k Fev 27 19:54 > /usr/local/lib/sane/libsane-hp5400.so.1 > > root@debian:~# cat /proc/bus/usb/devices > T: Bus=3D04 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D 1 Spd=3D12 = MxCh=3D 2 > B: Alloc=3D 0/900 us ( 0%), #Int=3D 0, #Iso=3D 0 > D: Ver=3D 1.00 Cls=3D09(hub ) Sub=3D00 Prot=3D00 MxPS=3D 8 #Cfgs=3D = 1 > P: Vendor=3D0000 ProdID=3D0000 Rev=3D 0.00 > S: Product=3DUSB UHCI-alt Root Hub > S: SerialNumber=3De000 > C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3D40 MxPwr=3D 0mA > I: If#=3D 0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub ) Sub=3D00 Prot=3D00 Driv= er=3Dhub > E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 8 Ivl=3D255ms > T: Bus=3D04 Lev=3D01 Prnt=3D01 Port=3D00 Cnt=3D01 Dev#=3D 2 Spd=3D12 = MxCh=3D 0 > D: Ver=3D 1.10 Cls=3D00(>ifc ) Sub=3D00 Prot=3D00 MxPS=3D 8 #Cfgs=3D = 1 > P: Vendor=3D03f0 ProdID=3D1105 Rev=3D 0.00 > S: Manufacturer=3DHewlett-Packard > S: Product=3DHP Scanjet 5400C Series > S: SerialNumber=3DCN19R1H00YBD > C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3De0 MxPwr=3D 48mA > I: If#=3D 0 Alt=3D 0 #EPs=3D 3 Cls=3D10(unk. ) Sub=3D01 Prot=3D00 Driv= er=3D(none) > E: Ad=3D81(I) Atr=3D02(Bulk) MxPS=3D 64 Ivl=3D0ms > E: Ad=3D02(O) Atr=3D02(Bulk) MxPS=3D 64 Ivl=3D0ms > E: Ad=3D83(I) Atr=3D03(Int.) MxPS=3D 1 Ivl=3D10ms > T: Bus=3D03 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D 1 Spd=3D12 = MxCh=3D 2 > B: Alloc=3D 0/900 us ( 0%), #Int=3D 0, #Iso=3D 0 > D: Ver=3D 1.00 Cls=3D09(hub ) Sub=3D00 Prot=3D00 MxPS=3D 8 #Cfgs=3D = 1 > P: Vendor=3D0000 ProdID=3D0000 Rev=3D 0.00 > S: Product=3DUSB UHCI-alt Root Hub > S: SerialNumber=3De400 > C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3D40 MxPwr=3D 0mA > I: If#=3D 0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub ) Sub=3D00 Prot=3D00 Driv= er=3Dhub > E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 8 Ivl=3D255ms > T: Bus=3D02 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D 1 Spd=3D12 = MxCh=3D 2 > B: Alloc=3D 0/900 us ( 0%), #Int=3D 0, #Iso=3D 0 > D: Ver=3D 1.00 Cls=3D09(hub ) Sub=3D00 Prot=3D00 MxPS=3D 8 #Cfgs=3D = 1 > P: Vendor=3D0000 ProdID=3D0000 Rev=3D 0.00 > S: Product=3DUSB UHCI-alt Root Hub > S: SerialNumber=3De800 > C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3D40 MxPwr=3D 0mA > I: If#=3D 0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub ) Sub=3D00 Prot=3D00 Driv= er=3Dhub > E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 8 Ivl=3D255ms > T: Bus=3D01 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D 1 Spd=3D480= MxCh=3D 6 > B: Alloc=3D 0/800 us ( 0%), #Int=3D 0, #Iso=3D 0 > D: Ver=3D 2.00 Cls=3D09(hub ) Sub=3D00 Prot=3D01 MxPS=3D 8 #Cfgs=3D = 1 > P: Vendor=3D0000 ProdID=3D0000 Rev=3D 2.04 > S: Manufacturer=3DLinux 2.4.20 ehci-hcd > S: Product=3DVIA Technologies, Inc. USB 2.0 > S: SerialNumber=3D00:10.3 > C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3D40 MxPwr=3D 0mA > I: If#=3D 0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub ) Sub=3D00 Prot=3D00 Driv= er=3Dhub > E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 2 Ivl=3D256ms > > root@debian:~# scanimage -d hp5400 > Segmentation fault |
From: Thomas S. <sou...@ne...> - 2003-02-27 13:11:29
|
Hello everybody, An alpha 2 version of the SANE backend for the HP5400 series scanners is available for download at http://sourceforge.net/projects/hp5400backend As it is alpha code, it is not fully featured. If developpers are interested in helping to fix the bugs and improve the backend, they are welcome !! Have a nice day, Thomas. |
From: Thomas S. <sou...@ne...> - 2003-02-25 22:00:03
|
Hello everybody, An alpha version of the SANE backend for the HP5400 series scanners is=20 available for download at http://sourceforge.net/projects/hp5400backend=20 As it is alpha code, it is not fully featured. If developpers are interested in helping to fix the bugs and improve the=20 backend, they are welcome !! Have a nice day, Thomas. |
From: Bertrik S. <be...@zo...> - 2003-01-25 11:02:18
|
Thomas Soumarmon wrote: >I have been playing around with my HP5470c scanner for some days without any >good results. I tried to handwrite C code corresponding to USBSnoopy logs I >got before as the logs are a bit long and tough, it never worked fully. So I >decided to replay the log with usb-robot. Logs did not fit with the expected >syntax... annoying. >So I decided to write an awk program that would write for me the C sourcecode >that replays the log, and it works. >Now I'll need to add the code to write the image to a file. Could anybody tell >me which format should I expect for the image (RGB pixels from top left ?). > I found that for the HP ScanJet 3300, image data is delivered like this: one line of red data, one line of green data, one line of blue data. To make it more complicated, the red, green and blue lines are out-of-sync vertically, meaning that the scanner delivers it like this: * red data of line 1, green data of line 2, blue data of line 3 * red data of line 2, green data of line 3, blue data of line 4 * red data of line 3, green data of line 4, blue data of line 5 etcetera And also it turned out for the hp3300 that the image was mirrored left-to-right, but this is straightforward to correct. SANE and the pnm format require the data to be delivered in R,G,B per pixel. >Is there a library I should use for image saving and processing (ImageMagick >?). Thank you for your help. > For the hp3300 testtool I used the pnm file format. A pnm file is very easy to create, just a text header followed by raw RGB data. I then used gimp to view the result. Bertrik |
From: Thomas S. <sou...@ne...> - 2003-01-24 12:30:41
|
Hi everybody, I have been playing around with my HP5470c scanner for some days without = any=20 good results. I tried to handwrite C code corresponding to USBSnoopy logs= I=20 got before as the logs are a bit long and tough, it never worked fully. S= o I=20 decided to replay the log with usb-robot. Logs did not fit with the expec= ted=20 syntax... annoying. So I decided to write an awk program that would write for me the C source= code=20 that replays the log, and it works. Now I'll need to add the code to write the image to a file. Could anybody= tell=20 me which format should I expect for the image (RGB pixels from top left ?= ).=20 Is there a library I should use for image saving and processing (ImageMag= ick=20 ?). Thank you for your help. I suppose that tha tool could be of interest for more people so it is=20 available for download at sourceforge : http://prdownloads.sourceforge.net/hp5400backend/USBSnoopy2CsourceCode.ta= r.gz?download Just a few notes : * This tool works with libusb. Feell free to port it to the kernel USB li= b if=20 you know how to do it. * you need awk and a C compiler to use it (if you don't have them, it is=20 probably of no use for you) Regs, Thomas. |