[sane-devel] Getting Clever CAM 360 working
I don't have this folder on my system, libgphoto2/camlibs/ Does something have to be installed to have it? Thanks, -Martin
[sane-devel] Epson Perfection 3490 - first blood
Dear Friends,
Ok, running Linux 2.6.12-rc2, libusb-0.1.10a.
I just bought an Epson Perfection 3490.
Obtained esfw52.bin from installing it on an M$ PC (where the
scanner works like a charm, I must admit).
Then hooked it up to my Linux box, installed said firmware file
and installed sane-backends-2005-09-12.
Apparently some people got it working, but here are my experiences,
as output from the following short bug reporting script.
Anyone have any ideas where to start fiddling with the code?
Thanks.
bjd
---
#!/bin/sh
# bug reporting script
xx()
{
echo \$ $@
eval $@
echo
} 21
# unplug and power-cycle the scanner here, then:
xx strings -n 2 /usr/local/etc/sane.d/esfw52.bin \| tail -n 2
xx cat /proc/bus/usb/devices \| head -n 22
# first use -- this should cause a firmware upload:
export USB_DEBUG=255
export SANE_DEBUG_SNAPSCAN=255
xx scanimage -d snapscan:libusb:004:011 21
xx udevinfo -a -p /sys/bus/usb/devices/4-11/
xx scanimage -L
xx sane-find-scanner
# during this the green 'ready' light blinks green,
# afterwards it is steady green again
export USB_DEBUG=255
export SANE_DEBUG_SNAPSCAN=255
xx scanimage -d snapscan:libusb:004:011 21
# end bug reporting script
---
Output from bug reporting script:
$ strings -n 2 /usr/local/etc/sane.d/esfw52.bin | tail -n 2
EPSON GT-F520 1.08
qThu Apr 14 2005 14:32
$ cat /proc/bus/usb/devices | head -n 22
T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS= 8 #Cfgs= 1
P: Vendor= ProdID= Rev= 2.06
S: Manufacturer=Linux 2.6.12-rc2 ehci_hcd
S: Product=Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller
S: SerialNumber=:00:1d.7
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms
T: Bus=04 Lev=01 Prnt=01 Port=05 Cnt=01 Dev#= 11 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1
P: Vendor=04b8 ProdID=0122 Rev= 1.10
S: Manufacturer=EPSON
S: Product=EPSON Scanner
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=83(I) Atr=03(Int.) MxPS= 8 Ivl=4096ms
$ scanimage -d snapscan:libusb:004:011
[sanei_debug] Setting debug level of snapscan to 255.
[snapscan] sane_snapscan_init
[snapscan] sane_snapscan_init: Snapscan backend version 1.4.43
usb_set_debug: Setting debugging level to 255 (on)
usb_os_init: Found USB VFS at /proc/bus/usb
usb_os_find_busses: Found 004
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 011 on 004
usb_os_find_devices: Found 001 on 004
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 003
usb_os_find_devices: Found 004 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 001
[snapscan] add_usb_device(libusb:004:011)
[snapscan] add_usb_device: Detected (kind of) an USB device
[snapscan] snapscani_usb_open(libusb:004:011)
[snapscan] add_usb_device: Checking if 0x04b8 is a supported USB vendor ID
[snapscan] snapscani_check_device()
[snapscan] mini_inquiry
[snapscan] snapscan_cmd
[snapscan] snapscani_usb_cmd(0,0xbff0cc20,6,0xbff0cbf0,0xbff0cbec (36))
[snapscan] atomic_usb_cmd(0,0xbff0cc20,6,0xbff0cbf0,0xbff0cbec (36))
[snapscan] usb_cmd(0,0xbff0cc20,6,0xbff0cbf0,0xbff0cbec (36))
[snapscan] usb_cmd: cmdlen=6, datalen=0
[snapscan] usb_write: writing: 0x12 0x00 0x00 0x00 0x24 0x00
[snapscan] Written 6 bytes
[snapscan] usb_read: reading: 0xf9 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[snapscan] Read 8 bytes
[snapscan] usb_read: reading: 0x06 0x00 0x02 0x02 0x49 0x00 0x00 0x00 0x45
0x50 ...
[snapscan] Read 36 bytes
[snapscan] usb_read: reading: 0xfb 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[snapscan] Read 8 bytes
[snapscan] snapscani_check_device: Is vendor EPSON model EPSON Scanner a
supported scanner?
[snapscan] snapscani_get_model_id(EPSON Scanner, 0, 2)
[snapscan] snapscani_get_model_id: looking up scanner for ID 0x04b8,0x0122.
[snapscan] snapscani_get_model_id: scanner identified
[snapscan] snapscani_check_device: Autodetected driver: Perfection 3490
[snapscan] snapscani_usb_close(0)
[snapscan] 1st read 3 write 1
[snapscan] snapscani_usb_cmd(0,0xbff0cc20,6,0x0,0x0 (0))
[snapscan] atomic_usb_cmd(0,0xbff0cc20,6,0x0,0x0 (0))
[snapscan] usb_cmd(0,0xbff0cc20,6,0x0,0x0 (0))
[snapscan] usb_cmd: cmdlen=6, datalen=0
[snapscan] usb_write: writing: 0x00 0x00 0x00 0x00 0x00 0x00
[snapscan] Written 6 bytes
[snapscan] usb_read: reading: 0xfb 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[snapscan] Read 8 bytes
[sane-devel] (no subject)
Hi, i am using an Mustek 1248UB, which is fully supported by gt48xx. Operating System is OSX. I installed all necessary packages for OSX and scanimage -L and scanning with scanimage works. But when i use an application, which uses the Twain-Sane-Bridge, the scanner does something short and dies after it. And i get the error message : End of file reached. It happens with all applications, which are using this bridge. Any help? Version of OSX is 10.4.2 Greetings
[sane-devel] End of file reached OSX
Hi, i am using an Mustek 1248UB, which is fully supported by gt48xx. Operating System is OSX. I installed all necessary packages for OSX and scanimage -L and scanning with scanimage works. But when i use an application, which uses the Twain-Sane-Bridge, the scanner does something short and dies after it. And i get the error message : End of file reached. It happens with all applications, which are using this bridge. Any help? Version of OSX is 10.4.2 Greetings
[sane-devel] Re: HP 4570c - any progress?
On Sunday 11 September 2005 18:29, I wrote: Is currently anyone working on this specific driver? If not, is there any code to pick up? Any docs from HP someone already acquired? I would also appriciate some hints/documentation about GL841/GL646 (which seems to be related) [3]. Re-hi all, in reply to my own mail: no answer within 48 hours presumely means that nobody works on this specific driver, that there are no docs available and that there's no code to pick up - correct?! If so, I should try to get some docs first. Does someone know something about HP's doc-sharing policy? Are there any established connections to HP? Please let me know any positive and/or negative experiences you had with HP-(developer)-support before, off-list if preferred. Thanks in advance Daniel
[sane-devel] scanimage via network
I tried accessing the scanner on my oldpc from my newpc and also set the permissions on the oldpc scanner device to chmod a+rwx [root_oldpc] ll /dev/usb/scanner0 crwxrwxrwx1 root root 180, 48 Jan 30 2003 /dev/usb/scanner0 But I am getting the following open error message. [root_newpc] scanimage -d net:192.168.1.50:gt68xx:/dev/usb/scanner0 scanimage: open of device net:192.168.1.50:gt68xx:/dev/usb/scanner0 failed: Error during device I/O What else am I missing? -Martin Giuseppe Sacco wrote: I just found the answer :-) scanimage -d net:IPADDRESS:BACKENDNAME:LOCALDEVICESPEC
[sane-devel] Re: HP 4570c - any progress?
Hi Daniel Franke schrieb: On Sunday 11 September 2005 18:29, I wrote: Is currently anyone working on this specific driver? If not, is there any code to pick up? Any docs from HP someone already acquired? I would also appriciate some hints/documentation about GL841/GL646 (which seems to be related) [3]. Links to documentation on the gl841 and gl646 chips can be found here: http://www.meier-geinitz.de/sane/genesys-backend/ But the log looks different to the ones i get from my gl841-based scanner. This does not mean it is completely incompatible. We don't have any documentation about the usb protocol, just about the register and memory layout of the gl841 and gl646. To view the log you can try to run SnoopyPro in wine. Wine constantly complains about not knowing usbsnpys.vxd, but otherwise it works for viewing the log. Re-hi all, in reply to my own mail: no answer within 48 hours presumely means that nobody works on this specific driver, that there are no docs available and that there's no code to pick up - correct?! If you want to experiment with your scanner without using sane you could extract code from my canon lide35 test program: http://www.pirsoft-dsl-dropzone.de/ Regards, Pierre
[sane-devel] Re: HP 4570c - any progress?
Daniel Franke wrote: On Sunday 11 September 2005 18:29, I wrote: Is currently anyone working on this specific driver? If not, is there any code to pick up? Any docs from HP someone already acquired? I would also appriciate some hints/documentation about GL841/GL646 (which seems to be related) [3]. Re-hi all, in reply to my own mail: no answer within 48 hours presumely means that nobody works on this specific driver, that there are no docs available and that there's no code to pick up - correct?! The stuff in the snoopy log looks similar to the protocol used by the hp5400 scanner, but in a weird way. For example, the scanner sends the SILITEK string in response to a USB transfer that contains the bytes 0x1200. For the HP5400 this is the command to read the version string. On the hp5400, command 0xc500 is used to read back the previously issued command. These bytes can also be seen in the snoopy log in USB transfers with apparently the same meaning as for the hp5400. The protocol is weird because it seems to implement some kind of 'USB-over-USB', i.e. the data payload of the USB control packets looks like another USB control packet. The payload size never appears to exceed 8 bytes. For example, URB #6 has a data payload of c0 04 00 12 00 00 32 00. This looks exactly like the setup packet from a hp5400 log: 0.84643495 URB 5 going down... 0.84644613 -- URB_FUNCTION_VENDOR_DEVICE: 0.84645954TransferFlags = 0001 (USBD_TRANSFER_DIRECTION_IN, ~USBD_SHORT_TRANSFER_OK) 0.84647127TransferBufferLength = 0032 0.84648244TransferBuffer = 811e5a88 0.84649250TransferBufferMDL= 0.84650312UrbLink = 0.84651345RequestTypeReservedBits = c0 0.84652351Request = 04 0.84653385Value = 1200 0.84654390Index = 0.85850408 0.85850967 URB 5 coming back... 0.85852085 -- URB_FUNCTION_CONTROL_TRANSFER: 0.85853202PipeHandle = 81411314 0.85854459TransferFlags= 0003 (USBD_TRANSFER_DIRECTION_IN, USBD_SHORT_TRANSFER_OK) 0.85855605TransferBufferLength = 0032 0.8585TransferBuffer = 811e5a88 0.85857700TransferBufferMDL= 813f88a8 0.85858594 0.85871417 : 00 53 69 6c 69 74 65 6b 49 42 6c 69 7a 64 20 43 0.85884184 0010: 33 20 53 63 61 6e 6e 65 72 56 30 2e 38 34 09 60 0.85897565 0020: 09 60 4f b0 6d b0 00 00 00 00 00 00 00 00 00 0a 0.85900135 0030: 00 64 0.85901085UrbLink = 0.85908377SetupPacket : c0 04 00 12 00 00 32 00 I am pretty sure that Silitek makes the niash types of chips. The HP5400 also uses a niash scanner control chip. I think you can try to understand this weird protocol a little better and see where the differences and similarities are with the HP5400 protocol, then try modify the lower layers of the hp5400 backend. If so, I should try to get some docs first. Does someone know something about HP's doc-sharing policy? Are there any established connections to HP? Please let me know any positive and/or negative experiences you had with HP-(developer)-support before, off-list if preferred. I tried and at least I got an answer although not a very useful one. HP may not even be able to give you docs if they didn't make the scanner control chip. Kind regards, Bertrik Sikken
[sane-devel] canoscan fb630p
Hi!... i've installed all packages (sane-backends, sane-frontends, libieee1284, scan 6.0) and when i scan -C throw me this error.. Finding IEEE1284 ports... parport0 (0x378): rawcptnblbytsweirq... OK (ecp-swe). Detecting scanner: Timeout: Scanner wakeup reply 1 (0x03 in 0x1f) - Status = 0x1f Timeout: Scanner wakeup reply 2 (0x03 in 0x1f) - Status = 0x1f Timeout: Scanner wakeup reply 1 (0x03 in 0x1f) - Status = 0x1f Timeout: Scanner wakeup reply 2 (0x03 in 0x1f) - Status = 0x1f Timeout: Scanner wakeup reply 1 (0x03 in 0x1f) - Status = 0x1f Timeout: Reply 2 (0x0c in 0x1f) - Status = 0x1f and scanner it's turn on, any idea please!... i need scan some photos please!!! Best regards, Arturo
[sane-devel] plustek_pp not working properly for 12000P
I am running a debian system with a manually compiled/installed 2.6.13 kernel. I've built the plustek pp kernel module and use that. Scanimage can't find the scanner, unless it is specified on a -d option, or via an environment default scanner setting. Scanning in only works in lineart or dithered modes. The gray and color modes produce only solid black output. Perhaps this is not the right forum for this, but this scanner worked in Mandrake, and obviously still works based on the dithered images. output of my /proc fs : brian:~$ cat /proc/pt_drv/device0/info Model : 12000P/96000P Portaddress : 0x378 Portmode: EPP (fast I/O, autodetect) Buttons : 0 Warmuptime : 0s Lamp timeout: 0s mov-switch : 0 I/O-delay : 0 CCD-Type: SONY Type TPA : no brian:~$ cat /proc/pt_drv/info Plustek Flatbed Scanner Driver version 0.43-7 Devices : 1 IOCTL-Version: 0x0104 Output of scanimage with a default device: brian:~$ export SANE_DEFAULT_DEVICE=plustek_pp:/dev/pt_drv0 brian:~$ scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). default device is `plustek_pp:/dev/pt_drv0' -- Output of scanimage with debugging turned on: root:/home/brian# scanimage [sanei_debug] Setting debug level of plustek_pp to 256. [plustek_pp] PlustekPP backend V0.43-7, part of sane-backends 1.0.16 [plustek_pp] # Plustek-PP SANE Backend configuration file [plustek_pp] # For use with Plustek parallel-port scanners [plustek_pp] # [plustek_pp] [plustek_pp] # [plustek_pp] # user either [direct] or [kernel] to access the scanner [plustek_pp] # when using [kernel], device specifies the device-node, which is created [plustek_pp] # by the kernel-module loader (applies only to Linux) [plustek_pp] # when using [direct], device is used to set the parallel-port base address [plustek_pp] # or a device-name suitable for libieee1284, i.e. parport0 [plustek_pp] # [plustek_pp] [direct] [plustek_pp] device 0x378 [plustek_pp] Decoding device name 0x378 [plustek_pp] [plustek_pp] # [plustek_pp] # leave the default values as specified in /etc/modules.conf [plustek_pp] # [plustek_pp] option warmup-1 [plustek_pp] Decoding option warmup [plustek_pp] option lOffOnEnd -1 [plustek_pp] Decoding option lOffOnEnd [plustek_pp] option lampOff -1 [plustek_pp] Decoding option lampOff [plustek_pp] [plustek_pp] # model override switch, mostly for cosmetic changes, if the autodetection [plustek_pp] # does not work or could not work correctly [plustek_pp] #option mov 7 [plustek_pp] [plustek_pp] # [plustek_pp] # example for accessing the scanner via libieee1284 [plustek_pp] # [plustek_pp] [direct] [plustek_pp] attach (0x378, 0xbfffc8c8, (nil)) [plustek_pp] Device configuration: [plustek_pp] device name : 0x378 [plustek_pp] direct I/O: yes [plustek_pp] warmup: -1s [plustek_pp] lampOff : -1 [plustek_pp] lampOffOnEnd : yes [plustek_pp] model override: 0 [plustek_pp] - [plustek_pp] drvopen() [plustek_pp] open: PtDrvInit failed: 4 [plustek_pp] open failed: -1 [plustek_pp] device 0x378 [plustek_pp] Decoding device name 0x378 [plustek_pp] #device parport0 [plustek_pp] [plustek_pp] # [plustek_pp] # example for accessing the scanner via the kernel module [plustek_pp] # [plustek_pp] #[kernel] [plustek_pp] device /dev/pt_drv0 [plustek_pp] Decoding device name /dev/pt_drv0 [plustek_pp] # [plustek_pp] #option warmup-1 [plustek_pp] #option lOffOnEnd -1 [plustek_pp] #option lampOff -1 [plustek_pp] attach (/dev/pt_drv0, 0xbfffc8c8, (nil)) [plustek_pp] Device configuration: [plustek_pp] device name : /dev/pt_drv0 [plustek_pp] direct I/O: yes [plustek_pp] warmup: -1s [plustek_pp] lampOff : -1 [plustek_pp] lampOffOnEnd : yes [plustek_pp] model override: 0 [plustek_pp] - [plustek_pp] drvopen() [plustek_pp] open: PtDrvInit failed: 4 [plustek_pp] open failed: -1 [plustek_pp] sane_open - /dev/pt_drv0 [plustek_pp] attach (/dev/pt_drv0, 0xbfffd8fc, 0xbfffe948) [plustek_pp] Device configuration: [plustek_pp] device name : [plustek_pp] direct I/O: no [plustek_pp] warmup: 0s [plustek_pp] lampOff : 0 [plustek_pp] lampOffOnEnd : no [plustek_pp] model override: 0 [plustek_pp] - [plustek_pp] drvopen() [plustek_pp] Scanner information: [plustek_pp] Vendor : Plustek [plustek_pp] Model : 12000P/96000P [plustek_pp] Asic : 0x10 [plustek_pp] Flags : 0x0200 [plustek_pp] drvclose() [plustek_pp] attach: model = 12000P/96000P [plustek_pp] Presetting Gamma tables (len=256) [plustek_pp] -- [plustek_pp] sane_start [plustek_pp] drvopen() [plustek_pp] scanmode = 3 [plustek_pp] bright 0 contrast
