[sane-devel] Canon DR-3010C scanner

Mon Nov 26 16:35:54 UTC 2012

Oh, I don't really have any instructions. Just try things like:

scanimage --mode=color --resolution=600 --source="ADF Duplex" -b

and check the resulting images. scanimage --help will give you a list
of other options for the scanner. Try making some scans with various
settings changed, and see if you uncover any problems. A prior user
reported some difficulty making a second scan after using an incorrect
parameter, but I don't have further details.

allan

On Mon, Nov 26, 2012 at 11:31 AM, Milko Simeonov
<msimeonov at intepro-bg.com> wrote:
> Hello Allan,
>
> Yes, we can do that. I'll be waiting for instructions.
>
> Cheers,
> Milko
>
>>>> "m. allan noah" <kitno455 at gmail.com> 11/26/12 5:19 PM >>>
>
> Well, if you can put the DR-3010C thru its paces, and make sure
> everything works (modes, resolutions, batch scanning, duplex, etc),
> then I will commit the required changes. Stef would have to comment on
> the Genesys stuff, as I have little experience there.
>
> allan
>
> On Mon, Nov 26, 2012 at 10:16 AM, Milko Simeonov
> <msimeonov at intepro-bg.com> wrote:
>> I'm happy to do all the necessary configuration and testing. I have the
>> scanner and the flatbed unit available, we can do whatever is necessary
>> and
>> use all resources needed to make it work. If you're interested of course.
>>
>> Cheers,
>> Milko
>>
>>
>>>>> "m. allan noah" <kitno455 at gmail.com> 11/26/12 5:07 PM >>>
>>
>> This device does not use the same protocol as other DR machines. It is
>> actually a Gensys chipset. Stef has some more info, but I think it
>> will take a much more effort to make the flatbed work.
>>
>> allan
>>
>> On Mon, Nov 26, 2012 at 9:59 AM, Milko Simeonov
>> <msimeonov at intepro-bg.com> wrote:
>>> Hi Allan,
>>>
>>> Yes, we are able to scan now through the main scanner (DR-3010C). What's
>>> left to be done is to be able to scan using an add-on device (canon
>>> flatbed
>>> scanner unit 101) that we have. It works like this - the main scanner is
>>> connected to the flatbed unit via USB cable, and the flatbed unit is
>>> connected to the PC via another USB cable (apparently the flatbed has a
>>> built-in usb hub).
>>>
>>> I've connected the devices now as they should be connected, I continue to
>>> be
>>> able to scan via the main scanner.
>>>
>>> The flatbed unit has an USB ID of its own, lsusb returns:
>>> Bus 002 Device 023: ID 1083:162e Canon Electronics, Inc.
>>>
>>> I can also see it in /var/log/messages:
>>> Nov 26 16:53:30 itp01 kernel: usb 2-1.3.1: new high speed USB device
>>> number
>>> 26 using ehci_hcd
>>> Nov 26 16:53:30 itp01 kernel: usb 2-1.3.1: New USB device found,
>>> idVendor=1083, idProduct=162e
>>> Nov 26 16:53:30 itp01 kernel: usb 2-1.3.1: New USB device strings:
>>> Mfr=10,
>>> Product=11, SerialNumber=0
>>> Nov 26 16:53:30 itp01 kernel: usb 2-1.3.1: Product: CANON Flatbed Scanner
>>> Unit 101
>>> Nov 26 16:53:30 itp01 kernel: usb 2-1.3.1: Manufacturer: CANON
>>>
>>> What can we do to make it work? Maybe I need to add the usb id in the
>>> canon_dr.conf file?
>>>
>>> Cheers,
>>> Milko
>>>
>>>
>>>>>> "m. allan noah" <kitno455 at gmail.com> 11/26/12 4:20 PM >>>
>>>
>>> Ok- now, in the sane-backends source, edit backend/canon_dr.c
>>>
>>> Find the function init_model. In that function, there is a section for
>>> the DR-2510C. Copy that section, and change it to match the DR-3010C.
>>> In your new section, also add this:
>>>
>>> s->invert_tly = 1;
>>>
>>> Then recompile and reinstall. Hopefully you will be able to scan.
>>>
>>> allan
>>>
>>> On Mon, Nov 26, 2012 at 9:15 AM, Milko Simeonov
>>> <msimeonov at intepro-bg.com> wrote:
>>>> OK, I've installed them back, they were sane-backends ,
>>>> sane-backends-autoconfig, hplip, hplip-sane and simple-scan .
>>>>
>>>> "scanimage -L" returns:
>>>> device `canon_dr:libusb:002:020' is a CANON DR-3010C scanner
>>>>
>>>> Milko
>>>>
>>>>
>>>>>>> "m. allan noah" <kitno455 at gmail.com> 11/26/12 4:08 PM >>>
>>>>
>>>> You probably should not un-install all the factory sane packages, as
>>>> that will remove frontend programs, and udev rules too. Generally, I
>>>> build sane-backends to overwrite the factory install.
>>>>
>>>> What is the output of scanimage -L when run as root?
>>>>
>>>> allan
>>>>
>>>> On Mon, Nov 26, 2012 at 8:58 AM, Milko Simeonov
>>>> <msimeonov at intepro-bg.com> wrote:
>>>>> Hi Allan,
>>>>>
>>>>> OK, I've uninstalled all sane-related packages that came with the
>>>>> distro
>>>>> and
>>>>> then I did (as root):
>>>>>
>>>>> git clone git://git.debian.org/sane/sane-backends.git
>>>>>
>>>>> ./configure --enable-libusb_1_0
>>>>>
>>>>> make
>>>>>
>>>>> make install
>>>>>
>>>>> All went fine.
>>>>>
>>>>> "scanimage -V" now returns:
>>>>>
>>>>> scanimage (sane-backends) 1.0.24git; backend version 1.0.24
>>>>>
>>>>> "scanimage -T" returned:
>>>>> Created directory: /var/lib/net-snmp/mib_indexes
>>>>> scanimage: sane_start: Invalid argument
>>>>>
>>>>> "sane-find-scanner" returned:
>>>>> # sane-find-scanner will now attempt to detect your scanner. If the
>>>>> # result is different from what you expected, first make sure your
>>>>> # scanner is powered up and properly connected to your computer.
>>>>>
>>>>> # No SCSI scanners found. If you expected something different, make
>>>>> sure
>>>>> that
>>>>> # you have loaded a kernel SCSI driver for your SCSI adapter.
>>>>>
>>>>> could not fetch string descriptor: Pipe error
>>>>> could not fetch string descriptor: Pipe error
>>>>> # No USB scanners found. If you expected something different, make sure
>>>>> that
>>>>> # you have loaded a kernel driver for your USB host controller and have
>>>>> setup
>>>>> # the USB system correctly. See man sane-usb for details.
>>>>>
>>>>> # Not checking for parallel port scanners.
>>>>>
>>>>> # Most Scanners connected to the parallel port or other proprietary
>>>>> ports
>>>>> # can't be detected by this program.
>>>>>
>>>>> What should I do next?
>>>>>
>>>>> Cheers,
>>>>> Milko
>>>>>
>>>>>
>>>>>>>> "m. allan noah" <kitno455 at gmail.com> 11/26/12 3:13 PM >>>
>>>>>
>>>>> Yes, this scanner requires code changes, and has had only minimal
>>>>> testing. Are you able to download and compile a sane-backends
>>>>> development snapshot from here:
>>>>>
>>>>> http://www.sane-project.org/source.html
>>>>>
>>>>> If so, we can make some minor changes to the code, and at least get
>>>>> some scans. It is possible that more changes will be required.
>>>>>
>>>>> allan
>>>>>
>>>>> On Mon, Nov 26, 2012 at 7:44 AM, Milko Simeonov
>>>>> <msimeonov at intepro-bg.com> wrote:
>>>>>> We have few USB scanners Canon DR-3010C which for some reason do not
>>>>>> work
>>>>>> under linux (openSUSE12.1, sled11sp2).
>>>>>>
>>>>>> lsusb returns:
>>>>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>>>>> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>>>>> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>>>>> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>>>>> Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>>>>> Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>>>>> Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>>>>> Bus 002 Device 002: ID 1083:161d Canon Electronics, Inc.
>>>>>>
>>>>>> sane-find-scanner returns:
>>>>>> found USB scanner (vendor=0x1083, product=0x161d) at libusb:002:002
>>>>>>
>>>>>> In /var/log/messages you can see:
>>>>>> Nov 26 14:49:20 sc02 kernel: [ 203.108275] usb 2-2: new high-speed USB
>>>>>> device number 2 using ehci_hcd
>>>>>> Nov 26 14:49:20 sc02 kernel: [ 203.243106] usb 2-2: New USB device
>>>>>> found,
>>>>>> idVendor=1083, idProduct=161d
>>>>>> Nov 26 14:49:20 sc02 kernel: [ 203.243117] usb 2-2: New USB device
>>>>>> strings:
>>>>>> Mfr=1, Product=2, SerialNumber=0
>>>>>> Nov 26 14:49:20 sc02 kernel: [ 203.243124] usb 2-2: Product: CANON
>>>>>> DR-3010C
>>>>>> Nov 26 14:49:20 sc02 kernel: [ 203.243130] usb 2-2: Manufacturer:
>>>>>> CANON
>>>>>>
>>>>>> So all looks fine, however if I open Yast->Scanner, select the scanner
>>>>>> driver and do "Test", I get:
>>>>>> Test with 'scanimage -d canon_dr:libusb:002:002 -v' failed.
>>>>>> The results are:
>>>>>> scanimage: sane_start: Invalid argument
>>>>>>
>>>>>> In /etc/sane.d/canon_dr.conf you can see the following lines:
>>>>>> # DR-3010C
>>>>>> usb 0x1083 0x161d
>>>>>>
>>>>>> scanimage -V returns:
>>>>>> scanimage (sane-backends) 1.0.22; backend version 1.0.22
>>>>>>
>>>>>> rpm -qa | grep sane returns:
>>>>>> sane-backends-1.0.22-15.4.1.x86_64
>>>>>> xsane-0.998-8.1.2.x86_64
>>>>>> hplip-sane-3.11.10-3.1.2.x86_64
>>>>>> sane-backends-autoconfig-1.0.22-15.4.1.x86_64
>>>>>> sane-backends-devel-1.0.22-15.4.1.x86_64
>>>>>>
>>>>>> Any ideas anyone?
>>>>>>
>>>>>> Milko
>>>>>>
>>>>>>
>>>>>> --
>>>>>> sane-devel mailing list: sane-devel at lists.alioth.debian.org
>>>>>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
>>>>>> Unsubscribe: Send mail with subject "unsubscribe your_password"
>>>>>> to sane-devel-request at lists.alioth.debian.org
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> "The truth is an offense, but not a sin"
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> "The truth is an offense, but not a sin"
>>>>
>>>
>>>
>>>
>>> --
>>> "The truth is an offense, but not a sin"
>>>
>>
>>
>>
>> --
>> "The truth is an offense, but not a sin"
>>
>
>
>
> --
> "The truth is an offense, but not a sin"
>

-- 
"The truth is an offense, but not a sin"