[sane-devel] CS9000F code
Am Sa, 04 Jun 2011 08:12:06 CEST schrieb Gernot Hassenpflug: Hi Gernot, > > > The blog should be available, but since I use dynamic DNS, with a > > > variable IP address, the site might be down sometimes. Just let me > > > know if you cannot access it and I will have a look. > > > > Please check: > > > > ping -c3 aikishugyo.dnsdojo.org > > PING aikishugyo.dnsdojo.org (219.160.114.155) 56(84) bytes of data. > > --- aikishugyo.dnsdojo.org ping statistics --- > > 3 packets transmitted, 0 received, 100% packet loss, time 1999ms > I looks like I needed to add port 80 to my router, maybe, after I > upgraded firmware. Strange, but please check if it works now... I tried hours ago and now: date Sa 4. Jun 22:52:13 CEST 2011 ping -c3 aikishugyo.dnsdojo.org PING aikishugyo.dnsdojo.org (219.160.114.155) 56(84) bytes of data. --- aikishugyo.dnsdojo.org ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2001ms Unfortunately it doesn't work. Could you copy the text of the howto in an email and send it to me? Thanks Al
[sane-devel] Problem using SX410 scanner - Invalid argument error
I'm getting invalid argument errors when trying to run scanimage > out.pnm using an Epson SX410 printer/scanner unit running sane-backends 1.0.21 on Debian. Here's the debug output: steffan at debian:~$ scanimage -L device `v4l:/dev/video0' is a Noname Built-in iSight virtual device device `epson2:libusb:001:014' is a Epson PID 0851 flatbed scanner steffan at debian:~$ scanimage --version scanimage (sane-backends) 1.0.21; backend version 1.0.21 steffan at debian:~$ SANE_DEBUG_EPSON2=255 scanimage > out.pnm [sanei_debug] Setting debug level of epson2 to 255. [epson2] sane_epson2_init: sane-backends 1.0.21 [epson2] epson2 backend, version 1.0.124 [epson2] sane_epson2_get_devices [epson2] probe_devices [epson2] free_devices [epson2] attach_one_config: len = 3, line = usb [epson2] attach_one_config: len = 16, line = usb 0x4b8 0x0851 [epson2] attach_one_usb: dev = libusb:001:014 [epson2] attach: devname = libusb:001:014, type = 3 [epson2] e2_dev_init [epson2] open_scanner: libusb:001:014 [epson2] scanner opened [epson2] found valid Epson scanner: 0x4b8/0x851 (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 = 0x7fff933ced5f [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 = 0x7fff933ced48 [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 = 0x7fff933cec10 [epson2] e2_recv: cmd count, r = 2, w = 2 [epson2] buf[0] 02 . [epson2] buf[1] 02 . [epson2] buf[2] 13 . [epson2] buf[3] 00 . [epson2] e2_recv_info_block: payload length: 19 [epson2] e2_recv: size = 19, buf = 0x9d42b0 [epson2] e2_recv: cmd count, r = 3, w = 2 [epson2] buf[0] 44 D [epson2] buf[1] 37 7 [epson2] buf[2] 52 R [epson2] buf[3] 4b K [epson2] buf[4] 00 . [epson2] buf[5] 52 R [epson2] buf[6] 2c , [epson2] buf[7] 01 . [epson2] buf[8] 52 R [epson2] buf[9] 58 X [epson2] buf[10] 02 . [epson2] buf[11] 52 R [epson2] buf[12] b0 . [epson2] buf[13] 04 . [epson2] buf[14] 41 A [epson2] buf[15] d8 . [epson2] buf[16] 27 ' [epson2] buf[17] d8 . [epson2] buf[18] 36 6 [epson2] e2_set_cmd_level: D7 [epson2] e2_add_resolution: add (dpi): 75 [epson2] e2_add_resolution: add (dpi): 300 [epson2] e2_add_resolution: add (dpi): 600 [epson2] e2_add_resolution: add (dpi): 1200 [epson2] maximum scan area: 10200x14040 [epson2] e2_set_fbf_area: 0.00,0.00 215.84,297.179993 1200 [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 = 0x7fff933cec60 [epson2] e2_recv: cmd count, r = 4, w = 3 [epson2] buf[0] 02 . [epson2] buf[1] 02 . [epson2] buf[2] 00 . [epson2] buf[3] 00 . [epson2] status: 02 [epson2] ready [epson2] no option equipment installed [epson2] 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 = 0x7fff933ceca8 [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 = 0x7fff933cebf0 [epson2] e2_recv: cmd count, r = 5, w = 4 [epson2] buf[0] 02 . [epson2] buf[1] 02 . [epson2] buf[2] 2a * [epson2] buf[3] 00 . [epson2] e2_recv_info_block: payload length: 42 [epson2] e2_recv: size = 42, buf = 0x9d4ba0 [epson2] e2_recv: cmd count, r = 6, w = 4 [epson2] buf[0] 00 . [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] c0 . [epson2] buf[12] d8 . [epson2] buf[13] 27 ' [epson2] buf[14] d8 . [epson2] buf[15] 36 6 [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] 49 I [epson2] buf[28] 44 D [epson2] buf[29] 20 [epson2] buf[30] 30 0 [epson2] buf[31] 38 8 [epson2] buf[32] 35 5 [epson2] buf[33] 31 1 [epson2] buf[34] 20 [epson2] buf[35] 20 [epson2] buf[36] 20 [epson2] buf[37] 20 [epson2] buf[38] 20 [epson2] buf[39] 20 [epson2] buf[40] 20 [epson2] buf[41] 20 [epson2] main = 00, ADF = 00, TPU = 00, main 2 = c0 [epson2] e2_set_model: model is 'PID 0851' [epson2] e2_set_fbf_area: 0.00,0.00 215.84,297.179993 1200 [mm] [epson2] no command available to detect capabilities [epson2] esci_reque
[sane-devel] Fwd: Scanner DocketPORT 468
Le vendredi 3 juin 2011 14:02:48 Enma Ai, vous avez ?crit :
> Hi,
> I tried to callibrate with xsane but I got the same error message:
> 'Fallo al definir valor de opci?n callibrate: Operaci?n no soportada' -->
> Error when trying to define the callibrate option: operation not supported.
>
> I modified syscan_docketport_467_model and changed the motor to
> roadwarrior, but I got the same results. The image proportions are not
> correct, it is streched (longer and narrower).
>
> I have uploaded some sample images:
> http://wtrns.fr/stfoMEspqqmIlU
>
> See sample images generated with:
> scanimage --mode Gray --format=jpeg >image_streched.jpeg
> scanimage --mode Gray --format=tiff >image_streched.tiff
>
> I've been doing some modifications in the model parameters and finally
> modifying the CCD_DSMOBILE600 the image looks correct.
>
> //Modified CCD_DSMOBILE600
> * Pentax DS Mobile 600 */
> {CCD_DSMOBILE600, 300,
>
>
>
> What I haven't been able to get to work is the document end of file
> detection, so I modified the predefined x and y size.
>
> //Modificacion
> static Genesys_Model syscan_docketport_467_model = {
> ...
> SANE_FIX (210.0), /* Size of scan area in mm (x) */
> SANE_FIX (297.0), /* Size of scan area in mm (y) */
> ...
> MOTOR_ROADWARRIOR
> ...
> }
>
> static Genesys_USB_Device_Entry genesys_usb_device_list[] = {
> ...
> {0x1dcc, 0x4817, &syscan_docketport_467_model},
> }
>
> I have uploaded several sample images generated with this commands:
>
> See sample images generated with:
> scanimage --mode Lineart --format=jpeg >image_CCD_ROADWARRIOR300.jpeg
> scanimage --mode Lineart --format=tiff >image_CCD_ROADWARRIOR300.tiff
> scanimage --mode Lineart --format=tiff >image_CCD_665.tiff
>
>
> thanks
>
Hello,
you are doing the right thing. From the stretched pictures we can see
it
is a sensor issue, not a motor one. You might try to evaluate these other
sensors: CCD_ROADWARRIOR, CCD_XP300, CCD_DP685.
For calibration and size issues, a scanimage logfile would be great,
something like:
export SANE_DEBUG_GENESYS=255
export SANE_DEBUG_GENESYS_LOW=255
export SANE_DEBUG_GENESYS_GL841=255
scanimage -d genesys --calibrate 2>calibrate.log >out.pnm
and for length issue:
export SANE_DEBUG_GENESYS=255
export SANE_DEBUG_GENESYS_LOW=255
export SANE_DEBUG_GENESYS_GL841=255
scanimage -d genesys --mode Color 2>rl.log >rl.pnm
For debugging purpose I have this script which runs from compiled
binaries without needing to install. i.e I run 'make' then this script in the
backend subdirectory, which saves me time (I change backend option depending
on what I'm testing):
#!/bin/bash
export SANE_DEBUG_GENESYS=255
export SANE_DEBUG_GENESYS_LOW=255
export SANE_DEBUG_GENESYS_GL646=255
export SANE_DEBUG_GENESYS_GL841=255
export SANE_DEBUG_GENESYS_GL843=255
export SANE_DEBUG_GENESYS_GL847=255
export SANE_DEBUG_GENESYS_GL124=255
export LD_PRELOAD=.libs/libsane-genesys.so
../frontend/scanimage -d genesys --resolution 150 --height 30 --mode Color
2>rl.log >rl.pnm
Regards,
Stef
[sane-devel] Recent NM-1000
Le jeudi 2 juin 2011 20:05:25 Paul Ericson, vous avez ?crit : > Removed all old sane and compiled and installed 1.0.22. > Tried a couple of different things. > The mods in /var/lib/misc/usb.ids are adding two lines: > 1ebb NuCORE Technology, Inc.Added-> 1f44 The > Neat CompanyAdded->0001 NM-1000 Mobile Scanner > 2001 D-Link Corp. [hex] 0001 DWL-120 > WIRELESS ADAPTER #1 Left mods in /var/lib/misc/usb.ids. Here is what > "sane-find-scanner -v -v" shows: Couldn't set configuration: could not set > config 1: Operation not permitted (result from sane-backends 1.0.22)> found USB scanner (vendor=0x1f44, > product=0x0001, chip=GL846?) at libusb:002:004 #2 Left mods in > /var/lib/misc/usb.ids. Here is what "sudo sane-find-scanner -v -v" shows: > 1.0.22)> found USB scanner (vendor=0x1f44 [The Neat Company ], > product=0x0001 [Neat Mobile Scanner]) at libusb:002:004 > > #3 Commented out the two added lines above, ran "sane-find-scanner -v -v", > it says: Couldn't set configuration: could not set config 1: Operation not > permitted 1.0.22)> found USB scanner (vendor=0x1f44, product=0x0001, chip=GL846?) at > libusb:002:004 > > #4 Commented out the two added lines above, ran "sudo sane-find-scanner -v > -v", it says: > 1.0.22)> found USB scanner (vendor=0x1f44 [The Neat Company ], > product=0x0001 [Neat Mobile Scanner]) at libusb:002:004 Interestingly, > when I run sudo sane-find-scanner, it appears to check for more chipsets. > Where as when I run it normally, it stops on GL84x. > > Is "Couldn't set configuration: could not set config 1: Operation not > permitted" as permissions issue or a configuration issue? (Or should I > ignore it?) Thanks, > Paul > I do not authorize any party to give away, publish or sell this e-mail > address. Its use is only for correspondence with me. I also do not consent > to receiving any unsolicited e-mail from any parties. > > > > > > Help Can the SPAM! > > --- On Thu, 6/2/11, stef wrote: > > From: stef > Subject: Re: [sane-devel] Recent NM-1000 > To: sane-devel at lists.alioth.debian.org > Cc: "Paul Ericson" > Received: Thursday, June 2, 2011, 4:13 AM > > Le mercredi 1 juin 2011 22:52:26 Paul Ericson, vous avez ?crit : > > I recently got a NM-1000 mobile scanner. I have not been able to get it > > working under sane. I've attached the output from sane-find-scanner -v -v > > and usb-devices (I'm running Ubuntu 10.04 which has no /proc/bus/usb). > > The scanner wouldn't even show up in lsusb until I modified > > /var/lib/misc/usb.ids. Any thoughts on which sane driver and firmware > > file I should try? (I've tried a couple > > with no > luck) Thanks, > > > Paul > > > > I do not authorize any party to give away, publish or sell this e-mail > > address. Its use is only for correspondence with me. I also do not > > consent to receiving any unsolicited e-mail from any parties. > > > > > > > > > > > > Help Can the SPAM! > > Hello, > > to help find the exact chip it is, can you run sane-find-scanner from > SANE 1.0.22 (just need to compile it and run the freshly compiled > sane-find- scanner from local directory without installing it). The > version you used is older. There is a possibility it is gl124 based. > > Another source of information is using usbsnoop under windows and send > me the log generated when scanner is plugged in. I'd be able to check if > it is a genesys chip. > > Such scanners are often clones of gt68xx supported scanner. In > that case, > an USB log will also tell it. > > Regards, > Stef Hello, I checked -with proper permissions- that my optic slim M12 is detected by sane-find-scanner. Since this hasn't been the case for you, I think we may rule out a gt68xx clone. With a gl124 based scanner, the chip is correctly detected. So I relally think that the last option is to use usbsnoop under windows to have a chance of identifying the asic in your scanner. Regards, Stef
[sane-devel] CS9000F code
On Fri, Jun 3, 2011 at 10:33 PM, Al Bogner wrote: > Am Sa, 12 Feb 2011 09:41:19 CET schrieb Gernot Hassenpflug: > > > Here is the hopefully definitive CS9000F code, with I believe the TPU > > offset in preview fixed. Please check. > > > > Instructions for downloading SANE CVS, and compiling can be found on > > my blog at > > > > aikishugyo.dnsdojo.org/blog > > > > and the attached files should replace files in sane-backends/backend. > > > > Now I can complete the work of creating a sub-driver from the > > combined code. > > I didn't hear anything about a newer code, so I want to try to compile > the one from February myself. > > Unfortunately aikishugyo.dnsdojo.org/blog is not available anymore? > > Can someone please explain me what I need to do or point me to a link? > Hello Al, The blog should be available, but since I use dynamic DNS, with a variable IP address, the site might be down sometimes. Just let me know if you cannot access it and I will have a look. Best regards, Gernot Hassenpflug -- next part -- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110604/61f348ab/attachment-0001.html>
