gmane.comp.graphics.scanning.sane.devel

xsane queries

Ganapati Hegde — 2012-05-25T13:55:29

Hi Oliver ,

 

I have few queries regarding xsane , I would be of great help if you can
give some valuable inputs on this.

 

In the investigation phase for a new scanner driver that would like to
leverage the XSane application, 

1.Does the vendor have a mechanism of disabling unsupported
features in existed xsane
2.If the vendor wants to add a feature, is there a config file
that you can modify without actually modifying code. Hence each vendor
will not disturb other installations.

If not, would XSane consider adding/disabling unsupported features?

3.And how do we submit our changes? 
4.What is the mode of deployment for our scanner driver frontend ?
Is it through XSane updates, or can we ship the same externally through
an installer.

 

Regards

Ganapati Hegde

 

 


______________________________________________________________________________
 DISCLAIMER: This electronic message and any attachments to this electronic
 message is intended for the exclusive use of the addressee(s) named herein

scanimage -L has stopped working,sane-find-scanner still detects

Bryan McNeil — 2012-05-24T17:56:22

I'm running mac osx 10.7 and originally was set up using the packages
available here: http://www.ellert.se/twain-sane/ (libusb, sane backends,
twain sane interface). My scanner was being detected fine last week, since
then I installed drivers for a different scanner (No way that caused this
problem I imagine) and configured, and make install'd the libusb source.
After that scanimage -L was no longer working, but sane-find-scanner still
found the device. The result for that is: found USB scanner (vendor=0x04a9
[Canon], product=0x2220 [CanoScan], chip=LM983x?) at
libusb:001:002-04a9-2220-ff-00. I've tried reinstalling those pakcages
again with no success. Searching around on this archive I found someone
with a similar problem who fixed it by configuring and make installing his
sources again but that has not worked for me.

Any help would be appreciated, thanks.

Re: HP ScanJet 5590 big endian

Ilia Sotnikov — 2012-05-24T12:27:28

...
...
...
...
...

Nhan,
thanks, nice catch. Does the backend work as expected (produces normal
images, correctly uses selected source etc) after applying the patch?
I suspect there are other places in the backend we should take a
closer look.

Re: Adding new product

Ganapati Hegde — 2012-05-24T12:09:00

Hi Allan  ,

 

Thanks for response ..

 

Our product specific features are compatible with the SANE API and
compatible with licensing terms. 

I will follow up XSane queries with author of XSane.  If you know could
you  send us XSane authors mail id or  group which I have to send my
XSane queries. 

 

Regards

Ganapati Hegde

 

From: m. allan noah [mailto:kitno455< at >gmail.com] 
Sent: Wednesday, May 23, 2012 6:22 PM
To: Ganapati Hegde
Cc: sane-devel< at >lists.alioth.debian.org; Tripti Rai
Subject: Re: [sane-devel] Adding new product

 

The author of XSane is not a member of the sane project. You would have
to ask him about how he accepts patches. But I doubt he will remove
features from XSane just for you. You could certainly fork XSane, but
you would have to adhere to its license.

Are your product specific features compatible with the SANE API? What is
the license of your backend.

allan

On Wed, May 23, 2012 at 8:27 AM, Ganapati Hegde
<ganapati.hegde< at >celstream.com> wrote:

Hi,

 

 I have some more question

Re: FW: [xsane-devel] Adding new product

Ganapati Hegde — 2012-05-24T11:52:49

Hi Oliver ,

 

I have few queries regarding xsane ,

 

In the investigation phase for a new scanner driver that would like to leverage the XSane application, 

1.Does the vendor have a mechanism of disabling unsupported features in existed xsane
2.If the vendor wants to add a feature, is there a config file that you can modify without actually modifying code. Hence each vendor will not disturb other installations.

If not, would XSane consider adding/disabling unsupported features?

3.And how do we submit our changes? 
4.What is the mode of deployment for our scanner driver frontend ? Is it through XSane updates, or can we ship the same externally through an installer.

 

Regards

Ganapati Hegde

 

 

 

 

 

From: sane-devel-bounces+ganapati.hegde=celstream.com< at >lists.alioth.debian.org [mailto:sane-devel-bounces+ganapati.hegde=celstream.com< at >lists.alioth.debian.org] On Behalf Of Ganapati Hegde
Sent: Thursday, May 24, 2012 4:42 PM
To: Oliver.Rauch< at >xsane.org
Cc: san

FW: [xsane-devel] Adding new product

Ganapati Hegde — 2012-05-24T11:11:56

Hi Oliver ,

I was looking into the xsane source code. I would like to know whether
any changes to xsane will be integrated?

      For the new product that I am looking at, I will have to remove
support to some of the existing xsane features for example 'gamma
widgets' as well as some of the options under 'File, Preferences etc'.
Also I will be adding couple of new product specific feature to the
frontend "xsane". Will these changes be integrated into the Xsane
release? If not kindly let me know how do we write new frontend that can
use the sane-backend?

 

Regards

Ganapati Hegde

 

From: m. allan noah [mailto:kitno455< at >gmail.com] 
Sent: Wednesday, May 23, 2012 6:22 PM
To: Ganapati Hegde
Cc: sane-devel< at >lists.alioth.debian.org; Tripti Rai
Subject: Re: [sane-devel] Adding new product

 

The author of XSane is not a member of the sane project. You would have
to ask him about how he accepts patches. But I doubt he will remove
features from XSane just for you. You could certainly fork XSane, but
you would hav

Re: Adding new product

m. allan noah — 2012-05-23T12:51:45

The author of XSane is not a member of the sane project. You would have to
ask him about how he accepts patches. But I doubt he will remove features
from XSane just for you. You could certainly fork XSane, but you would have
to adhere to its license.

Are your product specific features compatible with the SANE API? What is
the license of your backend.

allan

On Wed, May 23, 2012 at 8:27 AM, Ganapati Hegde <
ganapati.hegde< at >celstream.com> wrote:

Adding new product

Ganapati Hegde — 2012-05-23T12:27:57

Hi,

 

 I have some more questions on the way releases and changes are handled.

 

1.       I was looking into the xsane source code. I would like to know
whether any changes to xsane will be integrated?

a.       For the new product that I am looking at, I will have to remove
support to some of the existing xsane features for example 'gamma
widgets' as well as some of the options under 'File, Preferences etc'.
Also I will be adding couple of new product specific feature to the
frontend "xsane". Will these changes be integrated into the Xsane
release? If not kindly let me know how do we write new frontend that can
use the sane-backend?

 

2.       Once backend code is submitted how many days will it take for
release to happen, and when will the new backend version be available in
SANE repository. 

 

3.       Will the releases for frontend and backend happen at the same
time?

 

 

Regards

Ganapati Hegde

 

From: m. allan noah [mailto:kitno455< at >gmail.com] 
Sent: Wednesday, May 16, 2012 5:50 PM
To: Gana

HP ScanJet 5590 big endian

Nhan Ngo Dinh — 2012-05-22T16:27:57

Hello,

I've been trying to connect an HP ScanJet 5590 to an Atheros AR7241 rev 
1 system (MIPS 24Kc V7.4 CPU), using OpenWrt. The CPU is big endian. I 
got the error:

[hp5590] hp5590_get_ack
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 12, value = 142, 
index = 32, len = 1
USB error: error sending control message: Connection timed out
[sanei_usb] sanei_usb_control_msg: libusb complained: error sending 
control message: Connection timed out
[hp5590] hp5590_get_ack: USB-in-USB: error getting acknowledge

Using SANE_DEBUG_SANEI_USB=255 and SANE_DEBUG_HP5590=255 I got exactly 
the same result (even print_buffer() output was the same) as another 
user who tried to use this backend on a PPC (see this post: 
http://lists.alioth.debian.org/pipermail/sane-devel/2010-June/026900.html).

So I tried to run the same device under a little endian platform and I 
saw a difference:

Little Endian (working)
=======================
[hp5590] hp5590_init_scanner
[hp5590] hp5590_cmd: USB-in-USB: command : 0012
[hp5590

Debugging sane-find-scanner/scanimage

Rogan Dawes — 2012-05-22T14:52:36

Hi folks,

I am using SANE (scanimage (sane-backends) 1.0.22; backend version
1.0.22) on OpenWRT Backfire 10.3.1 on a Buffalo WZR-HP-G300NH,
attempting to interface with a Samsung SCX4300 MFP.

This device is supported by the xerox_mfp backend, and has worked in the
past. Now, for some odd reason, it is failing to detect the scanner.

Here is the debugging output I have managed to obtain:

root< at >gw:/# SANE_DEBUG_XEROX_MFP=128  SANE_DEBUG_SANEI_USB=4
sane-find-scanner

  # 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.
  # Also you need support for SCSI Generic (sg) in your operating system.
  # If using Linux, try "modprobe sg".

[sanei_debug] Setting debug level of sanei_usb to 4.
[sanei_usb] sanei_usb_init: marki

Re: Canon Mx 700 - Scanbuttons

Wilhelm — 2012-05-21T05:13:05

Am 17.05.2012 12:13, schrieb Louis Lagendijk:

As the author of the scanner button daemon (scanbd) I would be 
interested too in this functionality :-)

Re: HP Scanjet 3690 not recognized

stef — 2012-05-18T05:33:05

Le 18/05/2012 03:55, Michael N.Steen a écrit :
     Hello,

     the interesting part is:
[sanei_usb] sanei_usb_open: trying to open device `libusb:004:012'
libusb:error [op_set_configuration] failed, error -1 errno 71
[sanei_usb] sanei_usb_open: libusb complained: Numerical result out of range
[genesys] attach: couldn't open device `libusb:004:012': Invalid argument
     this means SANE's to set up USB for your scanner. I have 
encountered this problem with my GL646 based MD5345. I worked around it 
by recompiling SANE with another libusb version (ie I used libusb 
instead aof libusb-1.0, or the other way round, I don't remember). The 
same software combination worked on another computer. I did some 
debugging but don't have enough time to finish. I wouldn't be surprised 
if it is a kernel or libusb (or a combination of both) bug.

Regards,
     Stef

Re: HP Scanjet 3690 not recognized

Michael N.Steen — 2012-05-18T01:58:19

tor, 17 05 2012 kl. 07:17 +0200, skrev stef:


Hi, 

In addition to your suggestion I tried
# sane-find-scanner -v -v 
and attached the output as another text file. Seemingly uninteresting
part are deleted and replaced with [...]. The original file is available
if need be.

Thank you very much for your time.

Best regards, 
Michael

This is sane-find-scanner from sane-backends 1.0.22

  # 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.

searching for SCSI scanners:
[...]
  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

searching for USB scanners:
checking /dev/usb/scanner... failed to open (Invalid argument)
checking /dev/usb/scanner0... failed to open (Invalid argument)
checking /dev/usb/scanner1... failed to open (Invalid argument)
checking /dev/usb/scanner2...

Re: HP Scanjet 3690 not recognized

Michael N.Steen — 2012-05-18T01:55:55

tor, 17 05 2012 kl. 07:17 +0200, skrev stef:


Hi, 

So I tried 

# export SANE_DEBUG_GENESYS=255
# export SANE_DEBUG_GENESYS_LOW=255
# export SANE_DEBUG_GENESYS_GL646=255
# export SANE_DEBUG_SANEI_USB=255
# scanimage -L

It seems to me, that it finds the scanner but can't figure out what to
do with it. The output is so long and I'm not sure what is important and
what not, so I' attaching it all as a text file, except that seemingly uninteresting
part are deleted and replaced with [...] to comply with the size limits of the list.

The original file is available if need be.

My apologies to the moderators if I have inadvertedly violated the rules of the list.

Thank you very much for your time.

Best regards, 
Michael

[sanei_debug] Setting debug level of genesys to 255.
[genesys] SANE Genesys backend version 1.0 build 63 from sane-backends 1.0.22
[genesys] SANE Genesys backend built with libusb
[genesys] sane_init: authorize != null
[sanei_debug] Setting debug level of sanei_usb to 255.
[sanei_usb] sanei_usb

Re: Scaner digitaliza, mas não aparece imagem

stef — 2012-05-17T11:31:41

Le 16/05/2012 04:43, Михаил a écrit :
     Hello,

     since SANE 1.0.22 doesn't fully support the HP2400/G2410, it is 
better to test against the SANE's development version where it is 
supported.

Regards,
     Stef

Re: Canon Mx 700 - Scanbuttons

Louis Lagendijk — 2012-05-17T10:13:58

Hi,
Right now you can't. I wrote the network layer for the pixma backend,
and at the time could not figure out the button stuff. It is the only
part of the network stuff that does NOT work.

And as nobody ever asked, I never got around to look into that anymore.
I will put it on my TODO list to look into it again when I can find some
time

Kind regards, Louis

Canon Mx 700 - Scanbuttons

Nelson — 2012-05-17T05:46:52

Re: HP Scanjet 3690 not recognized

stef — 2012-05-17T05:17:16

Le 16/05/2012 03:28, Michael N. Steen a écrit :
     Hello,

     could you add :
export SANE_DEBUG_SANEI_USB=255
     before running scanimage -L as root ? I have seen usb failing 
sometimes on setting alternate endpoints. Which was solved by compiling 
SANE with the old libusb (not libusb-1.0). With this debug level we 
should have more information about it.

Regards,
     Stef

Re: HP Scanjet 3690 not recognized

Michael N. Steen — 2012-05-16T16:57:24

ons, 16 05 2012 kl. 12:29 -0400, skrev Steven Santos:

I don't use sudo but I tried su root, hence the #. The result was the
same as I got as an ordinary user, though.

Best regards,
Michael Steen

Adding new product

Ganapati Hegde — 2012-05-16T12:03:35

Hi ,

 

I have a requirement to support new device , How can I integrate  new
product specific backend code with sane and to whom I need to send my
code.

My widgets are different from existing xsane frontend. Can I write my
own product specific frontend code and integrate with sane backend ?

 

Thanks

Ganapati Hegde

 

 

 

 


______________________________________________________________________________
 DISCLAIMER: This electronic message and any attachments to this electronic
 message is intended for the exclusive use of the addressee(s) named herein
 and may contain legally privileged and confidential information. It is the 
 property of Celstream Technologies Pvt Limited. If you are not the intended
 recipient, you are hereby strictly notified not to copy, forward, distribute
 or use this message or any attachments thereto. If you have received this
 message in error, please delete it and all copies thereof, from your system
 and notify the sender at Celstream Technologies or 
 administrator< at >cels

Re: HP Scanjet 3690 not recognized

Michael N. Steen — 2012-05-16T01:28:29

Thank you for the suggestions. Here is the result of my endeavours, as
you'll see to no avail:

# dmesg | tail -6
usb 4-1: new full speed USB device using uhci_hcd and address 11
usb 4-1: New USB device found, idVendor=03f0, idProduct=1405
usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=12
usb 4-1: Product: HP Scanjet Scanner
usb 4-1: Manufacturer: Hewlett-Packard
usb 4-1: SerialNumber: CN38DS24YS

# export SANE_DEBUG_GENESYS=255
# export SANE_DEBUG_GENESYS_LOW=255
# export SANE_DEBUG_GENESYS_GL646=255
# scanimage -L
[sanei_debug] Setting debug level of genesys to 255.
[genesys] SANE Genesys backend version 1.0 build 63 from sane-backends
1.0.22
[genesys] SANE Genesys backend built with libusb
[genesys] sane_init: authorize != null
[genesys] sane_init: little endian machine
[genesys] probe_genesys_devices: start
[genesys] attach: start: devp != NULL, may_wait = 0
[genesys] attach: trying to open device `libusb:004:011'
[genesys] attach: couldn't open device `libusb:004:011': Invalid
argument