[sane-devel] Any news about CanoScan 9000F driver?
Am Mi, 25 Mai 2011 20:59:23 CEST schrieb Sam (Uli) Freed: Thanks for your work on open-source. I am considering buting the 9000F scanner, and I run the latest Ubuntu. Which driver do you mean? AFAIK, the driver is under construction and not in git, but a patch exists. I hope the driver gets into git in the next time. - Can you recommend/for against? - Does your driver support all resolutions/features? - I will be scanning my whole family slide Neg collection from the 1960s on. Do I need all the features? do we have what I need? I think there is no alternative for the price. IMO the highest resolution of the 9000F is useless for your sources, it is more a marketing value. If you speak German, I will search a test for you. If you want to scan slides and neg only, I would recommend you a film scanner, the quality is a lot better. I use a Nikon with vuescan for this. Al
[sane-devel] CanoScan 700F
Le mercredi 25 mai 2011 22:28:46 Sebastian Reinhardt, vous avez ?crit : Am 28.03.2011 21:27, schrieb stef: Le Monday 28 March 2011 00:32:11 Sebastian Reinhardt, vous avez ?crit : Am 01.03.2011 06:59, schrieb stef: Le Wednesday 23 February 2011 22:17:09 Sebastian Reinhardt, vous avez ?crit : . Hello, thanks for these tests. Now I think that the 700F isn't just a clone of LiDE 100/200 and specific structures must be tuned. The first thing to do is to define specific GPIO description for this model and see how it fares. Regards, Stef Ok, how can I help You to make it work? Hello, the steps involved in adapting the backend would be to record the USB activity for a scan done under windows. Then process this log to extract GPIO settings. A new GPIO define and a corresponding entry must be defined in genesys_device.c . Then in genesys_gl847.c the gl847_init_gpio function may be have to be adapted. To my opinion, there isn't much code to write but many tests to run in order to check that the cnages are working like expected. So this task would be better done by someone owning a 700F like you. Regards, Stef Sorry, it took a while, but I have done it: I made log during scanning with winstone (some programms had some problems with xp). I have uploaded the log file of an 75dpi scan to this location: http://snr-solutions.de/UsbSnoop.log This file was generated by SniffUSB-x86-2.0.0006. I hope this can help.. So Stef, if there is a new version of sane-backend, then I will test it again. Hello, one way to try to make support progress would be to run the decoding scripts I posted earlier on these logs, then compare how registers related to GPIO are set and compare to a test run of the current backend implementation. Then change code to handle the differences. Personnaly I haven't yet enough time to help for this model. Maybe at the end of April. Regards, Stef Hi Stef, any news about this driver? Hello, I'm currently completing 2400/4800 dpi support for LiDE 200. I bug fixing a few things, so I haven't currently any time for the 700F. Maybe in about a month. Regards, Stef
[sane-devel] Scanner DocketPORT 468
Hi, I'm trying to get to work scanner DocketPORT 468. I already know it is not supported and I have found no discussions related, however I'm giving it a try as the genesys backend provides support for scanners based on the Genesys Logic GL646 and GL841 chips and I have read in a discussion that GL842 is essentially the same as the GL841. My OS is: Linux version 2.6.35-28-generic (buildd at rothera) (gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) ) I have (sane-backends) 1.0.21; backend version 1.0.21. When connecting the scanner I get: :dmesg [ 3960.456090] usb 2-5: new high speed USB device using ehci_hcd and address 9 :sane-find-scanner -v found USB scanner (vendor=0x1dcc [Document Capture Technologies Inc.], product=0x4817 [SimpleScan], chip=GL842) at libusb:002:008 :scanimage -V scanimage (sane-backends) 1.0.21; backend version 1.0.21 But: scanimage -L No scanners were identified. Any suggestions? Should I just forget about it and look for another scanner? :) Thanks and regards Enma :) -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110526/07caff3e/attachment.html
[sane-devel] Scanner DocketPORT 468
The scanner should probably work since the backend says it works with the Visioneer XP100r3/RoadWarrior/Xerox Travel Scanner, which I believe are rebadged versions of the same model. From: sane-devel-bounces+delm=bulletscan@lists.alioth.debian.org [mailto:sane-devel-bounces+delm=bulletscan.com at lists.alioth.debian.org] On Behalf Of Enma Ai Sent: Thursday, May 26, 2011 4:44 AM To: sane-devel at lists.alioth.debian.org Subject: [sane-devel] Scanner DocketPORT 468 Hi, I'm trying to get to work scanner DocketPORT 468. I already know it is not supported and I have found no discussions related, however I'm giving it a try as the genesys backend provides support for scanners based on the Genesys Logic GL646 and GL841 chips and I have read in a discussion that GL842 is essentially the same as the GL841. My OS is: Linux version 2.6.35-28-generic (buildd at rothera) (gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) ) I have (sane-backends) 1.0.21; backend version 1.0.21. When connecting the scanner I get: :dmesg [ 3960.456090] usb 2-5: new high speed USB device using ehci_hcd and address 9 :sane-find-scanner -v found USB scanner (vendor=0x1dcc [Document Capture Technologies Inc.], product=0x4817 [SimpleScan], chip=GL842) at libusb:002:008 :scanimage -V scanimage (sane-backends) 1.0.21; backend version 1.0.21 But: scanimage -L No scanners were identified. Any suggestions? Should I just forget about it and look for another scanner? :) Thanks and regards Enma :) -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110526/cf22049c/attachment.html
[sane-devel] Scanner DocketPORT 468
Hi,
I have followed the indications from this site to recompile the backends:
https://help.ubuntu.com/community/CheckIfScannerIsClone
sane-find-scanner -v -v (To identify Id of the vendor, product and chipset)
device descriptor of 0x1dcc/0x4817 at 002:004 (Document Capture
Technologies Inc. SimpleScan)
bLength 18
bDescriptorType 1
bcdUSB2.00
bDeviceClass 255
bDeviceSubClass 255
bDeviceProtocol 255
bMaxPacketSize0 64
*idVendor 0x1DCC
idProduct 0x4817*
bcdDevice 3.02
*iManufacturer 10 (Document Capture Technologies Inc.)
iProduct 11 (SimpleScan)*
...
trying to find out which USB chip is used
checking for GL84x ...
This USB chip looks like a *GL842* (result from sane-backends 1.0.21)
found USB scanner (vendor=0x1dcc [Document Capture Technologies Inc.],
product=0x4817 [SimpleScan], chip=GL842) at libusb:002:004
With the above information I found several possible compatible scanners with
chip GL841, even though this scanner has GL842 and it is not supported.
/* GL841 devices */
{0x04a7, 0x0474, visioneer_xp300_model},
{0x04a7, 0x0494, visioneer_roadwarrior_model},
{0x04a7, 0x049b, visioneer_xp100_r3_model},
{0x04a7, 0x04ac, xerox_travelscanner_model},
{0x04a9, 0x2213, canon_lide_50_model},
{0x04a9, 0x221c, canon_lide_60_model},
{0x07b3, 0x0900, plustek_3600_model},
{0x0a17, 0x3210, pentax_dsmobile_600_model},
{0x04f9, 0x2038, pentax_dsmobile_600_model}, /* clone, only usb id is
different */
{0x0a82, 0x4800, syscan_docketport_485_model},
{0x0a82, 0x4802, syscan_docketport_465_model},
{0x0a82, 0x4803, syscan_docketport_665_model},
{0x0a82, 0x480c, syscan_docketport_685_model},
{0x1dcc, 0x4810, dct_docketport_487_model},
{0x1dcc, 0x4812, syscan_docketport_467_model},
I have tried with all the docketport and the scanner is recognized only by
those with the same vendor id 0x1dcc:
//Different vendor id (for example 0x0a82, 0x4802,
syscan_docketport_465_model)
scanimage -L
No scanners were identified.
//Same vendor id: 0x1dcc
scanimage -L
device `genesys:libusb:002:007' is a DCT DocketPORT 487 flatbed scanner
But I get a warning and the scanner finally crashes:
scanimage image.pnm
[genesys] WARNING: Your scanner is not fully supported or at least
[genesys] had only limited testing. Please be careful and
[genesys] report any failure/success to
[genesys] sane-devel at lists.alioth.debian.org. Please provide
as many
[genesys] details as possible, e.g. the exact name of your
[genesys] scanner and what does (not) work.
...
Only Docketport 467 worked and it got to scan, however the image was
completely black and when I tried to scan again the scanner wasn't
recognized any longer.
I will do some more tests with this model and I have also contact the
manufacturer just in case they have a linux driver available. If I finally
get it to scan I will post it.
Thanks for your help! :)
On 26 May 2011 17:07, Daniel Elm delm at bulletscan.com wrote:
The scanner should probably work since the backend says it works with the
Visioneer XP100r3/RoadWarrior/Xerox Travel Scanner, which I believe are
rebadged versions of the same model.
*From:* sane-devel-bounces+delm=bulletscan.com at
lists.alioth.debian.org[mailto:
sane-devel-bounces+delm=bulletscan.com at lists.alioth.debian.org] *On Behalf
Of *Enma Ai
*Sent:* Thursday, May 26, 2011 4:44 AM
*To:* sane-devel at lists.alioth.debian.org
*Subject:* [sane-devel] Scanner DocketPORT 468
Hi,
I'm trying to get to work scanner DocketPORT 468.
I already know it is not supported and I have found no discussions related,
however I'm giving it a try as the genesys backend provides support for
scanners based on the Genesys Logic GL646 and GL841 chips and I have read in
a discussion that GL842 is essentially the same as the GL841.
My OS is: Linux version 2.6.35-28-generic (buildd at rothera) (gcc version
4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) )
I have (sane-backends) 1.0.21; backend version 1.0.21.
When connecting the scanner I get:
:dmesg
[ 3960.456090] usb 2-5: new high speed USB device using ehci_hcd and
address 9
:sane-find-scanner -v
found USB scanner (vendor=0x1dcc [Document Capture Technologies Inc.],
product=0x4817 [SimpleScan], chip=GL842) at libusb:002:008
:scanimage -V
scanimage (sane-backends) 1.0.21; backend version 1.0.21
But:
scanimage -L
No scanners were identified.
Any suggestions? Should I just forget about it and look for another
scanner? :)
Thanks and regards
Enma :)
--
* La Ni?a Ninja *
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110526/c1ecd7c5/attachment.html
[sane-devel] Attempting to write driver for HP ScanJet 4890
Hello, I'm going to attempt to write a back end for my ScanJet 4890 scanner. I'm hoping that it won't be too bad to add to the genesys back end. Thanks, -Scott
[sane-devel] Scanner DocketPORT 468
Le jeudi 26 mai 2011 18:06:32 Enma Ai, vous avez ?crit :
Hi,
I have followed the indications from this site to recompile the backends:
https://help.ubuntu.com/community/CheckIfScannerIsClone
sane-find-scanner -v -v (To identify Id of the vendor, product and chipset)
device descriptor of 0x1dcc/0x4817 at 002:004 (Document Capture
Technologies Inc. SimpleScan)
bLength 18
bDescriptorType 1
bcdUSB2.00
bDeviceClass 255
bDeviceSubClass 255
bDeviceProtocol 255
bMaxPacketSize0 64
*idVendor 0x1DCC
idProduct 0x4817*
bcdDevice 3.02
*iManufacturer 10 (Document Capture Technologies Inc.)
iProduct 11 (SimpleScan)*
...
trying to find out which USB chip is used
checking for GL84x ...
This USB chip looks like a *GL842* (result from sane-backends 1.0.21)
found USB scanner (vendor=0x1dcc [Document Capture Technologies Inc.],
product=0x4817 [SimpleScan], chip=GL842) at libusb:002:004
With the above information I found several possible compatible scanners
with chip GL841, even though this scanner has GL842 and it is not
supported.
/* GL841 devices */
{0x04a7, 0x0474, visioneer_xp300_model},
{0x04a7, 0x0494, visioneer_roadwarrior_model},
{0x04a7, 0x049b, visioneer_xp100_r3_model},
{0x04a7, 0x04ac, xerox_travelscanner_model},
{0x04a9, 0x2213, canon_lide_50_model},
{0x04a9, 0x221c, canon_lide_60_model},
{0x07b3, 0x0900, plustek_3600_model},
{0x0a17, 0x3210, pentax_dsmobile_600_model},
{0x04f9, 0x2038, pentax_dsmobile_600_model}, /* clone, only usb id is
different */
{0x0a82, 0x4800, syscan_docketport_485_model},
{0x0a82, 0x4802, syscan_docketport_465_model},
{0x0a82, 0x4803, syscan_docketport_665_model},
{0x0a82, 0x480c, syscan_docketport_685_model},
{0x1dcc, 0x4810, dct_docketport_487_model},
{0x1dcc, 0x4812, syscan_docketport_467_model},
I have tried with all the docketport and the scanner is recognized only by
those with the same vendor id 0x1dcc:
//Different vendor id (for example 0x0a82, 0x4802,
syscan_docketport_465_model)
scanimage -L
No scanners were identified.
//Same vendor id: 0x1dcc
scanimage -L
device `genesys:libusb:002:007' is a DCT DocketPORT 487 flatbed scanner
But I get a warning and the scanner finally crashes:
scanimage image.pnm
[genesys] WARNING: Your scanner is not fully supported or at least
[genesys] had only limited testing. Please be careful and
[genesys] report any failure/success to
[genesys] sane-devel at lists.alioth.debian.org. Please provide
as many
[genesys] details as possible, e.g. the exact name of your
[genesys] scanner and what does (not) work.
...
Only Docketport 467 worked and it got to scan, however the image was
completely black and when I tried to scan again the scanner wasn't
recognized any longer.
I will do some more tests with this model and I have also contact the
manufacturer just in case they have a linux driver available. If I finally
get it to scan I will post it.
Thanks for your help! :)
On 26 May 2011 17:07, Daniel Elm delm at bulletscan.com wrote:
The scanner should probably work since the backend says it works with the
Visioneer XP100r3/RoadWarrior/Xerox Travel Scanner, which I believe are
rebadged versions of the same model.
*From:*
sane-devel-bounces+delm=bulletscan.com at lists.alioth.debian.org[mailto:
sane-devel-bounces+delm=bulletscan.com at lists.alioth.debian.org] *On
Behalf Of *Enma Ai
*Sent:* Thursday, May 26, 2011 4:44 AM
*To:* sane-devel at lists.alioth.debian.org
*Subject:* [sane-devel] Scanner DocketPORT 468
Hi,
I'm trying to get to work scanner DocketPORT 468.
I already know it is not supported and I have found no discussions
related, however I'm giving it a try as the genesys backend provides
support for scanners based on the Genesys Logic GL646 and GL841 chips
and I have read in a discussion that GL842 is essentially the same as
the GL841.
My OS is: Linux version 2.6.35-28-generic (buildd at rothera) (gcc version
4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) )
I have (sane-backends) 1.0.21; backend version 1.0.21.
When connecting the scanner I get:
:dmesg
[ 3960.456090] usb 2-5: new high speed USB device using ehci_hcd and
address 9
:sane-find-scanner -v
found USB scanner (vendor=0x1dcc [Document Capture Technologies Inc.],
product=0x4817 [SimpleScan], chip=GL842) at libusb:002:008
:scanimage -V
scanimage (sane-backends) 1.0.21; backend version 1.0.21
But:
scanimage -L
No scanners were identified.
Any suggestions? Should I just forget about it and look for another
scanner? :)
Thanks and regards
Enma :)
Hello,
in fact most of the scanners supported by the
[sane-devel] Attempting to write driver for HP ScanJet 4890
Le jeudi 26 mai 2011 19:19:54 sedwards at xmission.com, vous avez ?crit : Hello, I'm going to attempt to write a back end for my ScanJet 4890 scanner. I'm hoping that it won't be too bad to add to the genesys back end. Thanks, -Scott Hello, what does 'sane-find-scanner' report ? Regards, Stef
[sane-devel] Reflecta ProScan 7200
Hi Michael, That took me quite a while to think through, I'm stll not ready with everything yet. I think we need some kind of a document that accumulates all we have come to know. Maybe we should also try to agree on the names we use. I'm trying to compose it, but: not ready yet... What surprises me is the difference you discovered. I attach my INQUIRY response so you can check if there are more differences except for byte 74 (which equals 0x30 for the Crystalscan scanner). I would not expect large differences. Perhaps it is only a small change in the use of bit 3 in MODE SELECT byte 9 (required speed). If I send 0x02 (instead of 0x0a) to the scanner for quality mode, COPY gives an error, and REQUEST SENS gives 70 0005 06 2000 = ILLEGAL REQUEST, INVALID command OPERATION CODE. Would it be worthwhile to check for differences in more detail, for example in the startup sequence? I think it's probably best to continue focussing on the SCSI-DC command. It seems logical to have exposure time, gain and offset for the R, G and B channels, and for quality mode your experiments show where they are in the 23-byte sent by the DC-command. But the normal-mode results are strange. You are right about the very dark scans I get (the raw data, Cyberview corrects for this). But it is strange that normal mode seems to do away with all pixel values in the lower half of the dynamic range, and expands the upper half (by a factor 2). That is what seems to be happening in normal mode, isn't it? We should check if we are missing context. Could it be that some of the unidentified 0xDC-information sets a shadow-highlight range of 50% to 100%? Might normal mode work by simply setting this range? Maybe the DC-information is interpreted by the scanner depending on the modes (startup mode (0x00) with very simple settings, a normal mode (0x08) with more parameters, and a quality mode (0x02/0x0a) with the most extensive parameter set.) Did you experiment with byte 15 (after the RGB-gains)? I notice 0x00 switches off the light during a scan, and non-0x00-values turn it on. I do not know if it is more than just switch on/off, but if we can specify the light intensity, we have an extra parameter to consider. Did you find a relationship of the exposure time specified in the INQUIRY reponse (min 100 max 2500) to the range you find? I do not see a factor 25 between min and max? The (almost) exponential gain curves look like ones I found in datasheets (e.g.http://focus.ti.com/general/docs/lit/getliterature.tsp? genericPartNumber=vsp3100fileType=pdf). Having an analytical description is nice, but not absolutely required; a look-up table for the relationship between the gain parameter value and the actual gain will also work. This table can be derived from your experiments, I'll describe how in the reference document. I have made a small program to communicate with the scanner outside of SANE, because I found I sometimes needed some more flexibility. I intend to use it for documenting my experiments as well, so I'm thinking of adding a facility to run the experiments based on a text script. If I see what is still asking for an explanantion, this effort may be worthwhile. Yours, Jan From: Michael Rickmann [mric...@gwdg.de] Sent: Wednesday, May 18, 2011 6:47 PM To: Vleeshouwers, J.M. Cc: sane-devel at lists.alioth.debian.org Subject: Re: [sane-devel] Reflecta ProScan 7200 Hi Jan, now what I found. huge snip Regards Michael -- next part -- A non-text attachment was scrubbed... Name: INQUIRY.dat Type: application/x-ns-proxy-autoconfig Size: 184 bytes Desc: INQUIRY.dat URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110526/5a6aa4d3/attachment.dat
[sane-devel] xsane
Good Afternoon, I have some questions waiting that you can help me. I'm new in list. The company where I work, development softwares to GED/ECM. We're development to Linux and would like to take project XSANE. Is it possible? How should I proceed? Never developtment to free software but i would like to contribute. Thank you Tiago Zaniquelli -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110526/95f0dacf/attachment.html
[sane-devel] xsane
Le jeudi 26 mai 2011 21:42:35 Tiago Zaniquelli, vous avez ?crit : Good Afternoon, I have some questions waiting that you can help me. I'm new in list. The company where I work, development softwares to GED/ECM. We're development to Linux and would like to take project XSANE. Is it possible? How should I proceed? Never developtment to free software but i would like to contribute. Thank you Tiago Zaniquelli Hello, I think such a question should be directed to XSane's maintainer Oliver Rauch .You'll find contact information at http://www.xsane.org/xsane- contact.html, and XSane's license is explained at http://www.xsane.org/xsane- license.html . Nothing prevents from starting a GPL'ed project from another GPL'ed project, provided proper copyrights and credits are given. However -depending on the amount and nature of changes you plan- may be just proposing patches to Oliver would do it. Regards, Stef
