[sane-devel] HP Scanjet 2400c (partial) success, 100 and 300 dpi work both in grayscale and colour (some small changes needed)

[stef]

Le dimanche 30 mai 2010 22:22:02 Piotr Mis, vous avez ?crit :
 Dnia 2010-05-30, nie o godzinie 11:14 +0200, stef pisze:
  Le vendredi 28 mai 2010 16:07:50 Piotr Mis, vous avez ?crit :
   Very sorry, sent to soon.
   
   Hello,
   
   I was delighted that there is some progress with Scanjet 2400c.
   
   I ran it through some tests, and fixed what I could. Results:
   
   git version of genesys backend works partially:
   
   grayscale:
 * 50  dpi: hangs
 * 100 dpi: works partially, motor step too big, need to switch
 off
 
   the scanner to prevent damage
 
 * 300 dpi: works nicely
 * 600 dpi: picture distorted
   
   colour:
   as grayscale, but colour channels seem to be switched and slightly
   offset vertically.
   
   I tried to fix it myself and managed to fix the colour channels and the
   motor step in 100dpi.
   
   
   My changes below, comments/advice very welcome:
   
   1. The scanner  (at least mine) is RBG not BGR, this fixes the vertical
   offset as well:
   
   
   diff --git a/backend/genesys_devices.c b/backend/genesys_devices.c
   index a8da85d..3459090 100644
   --- a/backend/genesys_devices.c
   +++ b/backend/genesys_devices.c
   @@ -1173,7 +1173,7 @@ Genesys_Model hp2400c_model = {
   
  0, 24, 48,   /* RGB CCD Line-distance correction in
   
   pixel */
   
   -  COLOR_ORDER_BGR, /* Order of the CCD/CIS colors */
   +  COLOR_ORDER_RGB, /* Order of the CCD/CIS colors */
   
  SANE_FALSE,  /* Is this a CIS scanner? */
  SANE_FALSE,  /* Is this a sheetfed scanner? */
   
   2. The motor definition for 100 dpi from FULL_STEP to HALF_STEP:
   
   diff --git a/backend/genesys_gl646.h b/backend/genesys_gl646.h
   index 5dc3725..695d55f 100644
   --- a/backend/genesys_gl646.h
   +++ b/backend/genesys_gl646.h
   @@ -555,11 +555,11 @@ static Motor_Master motor_master[] = {
   
  /* HP2400/G2410 motor settings base motor dpi = 600 */
  {MOTOR_HP2400,  50, SANE_TRUE ,  50, HALF_STEP, SANE_FALSE,
   
   SANE_FALSE, 63,
   -  {MOTOR_HP2400, 100, SANE_TRUE , 100, FULL_STEP, SANE_FALSE,
   SANE_TRUE,  63, 1
   +  {MOTOR_HP2400, 100, SANE_TRUE , 100, HALF_STEP, SANE_FALSE,
   SANE_TRUE,  63, 1
   
  {MOTOR_HP2400, 300, SANE_TRUE , 300, HALF_STEP, SANE_FALSE,
   
   SANE_TRUE , 63, 3
   
  {MOTOR_HP2400, 600, SANE_TRUE , 600, FULL_STEP, SANE_FALSE,
   
   SANE_TRUE , 63,
   
  {MOTOR_HP2400,  50, SANE_FALSE,  50, HALF_STEP, SANE_FALSE,
   
   SANE_FALSE, 63,
   -  {MOTOR_HP2400, 100, SANE_FALSE, 100, FULL_STEP, SANE_FALSE,
   SANE_TRUE,  63, 1
   +  {MOTOR_HP2400, 100, SANE_FALSE, 100, HALF_STEP, SANE_FALSE,
   SANE_TRUE,  63, 1
   
  {MOTOR_HP2400, 300, SANE_FALSE, 300, HALF_STEP, SANE_FALSE,
   
   SANE_TRUE , 63, 3
   
  {MOTOR_HP2400, 600, SANE_FALSE, 600, FULL_STEP, SANE_FALSE,
   
   SANE_TRUE , 63,
   
   What I'm still really missing is the preview in xsane, has probably
   something to do with not working 50dpi mode.
   
   Regards,
   
   Piotr
  
  Hello,
  
  so with these changes 100 dpi is working ? If you wish I can send you my
  
  log decoding scripts. By recording scanner activity under windows with
  usbsnoop, then processing it through them, you'll have the values to put
  in HP2400 motor and sensor tables for the modes that  aren't working
  yet.
  
  Regards,
  
  Stef
 
 Yes, 100 and 300 dpi both produce quite good scans with these settings.
 And yes, please do send me the scripts, I'll try to get the rest
 working.
BTW. What would be nice to have is the scanner running smoothly in
 300 dpi colour (and higher resolutions in both grayscale and colour).
 The motor stops, then runs backwards a few steps, then restarts a few
 times during scanning, this seems not to influence scan output. Looks
 like the data are not read fast enough from or written too fast by the
 scanner. This is exactly what I experience  when scanning using Windows
 from within virtual machine, but then, even in 100 dpi grayscale mode.
 Can this problem be fixed when using data from your decoding scripts as
 well?
 
 Regards,
 
 Piotr
Hello,

here are the scripts. Just run decode.sh on the UsbSnoop.log recorded 
under windows. You'll get the right values to put in the tables in the 
resulting file.
Be aware that windows driver doesn't always scanned at the resolution 
you 
asked. Select a full width area of the smallest height to minimize log size. 
The value to use are the ones of the final scan you. Thsi scan is the one 
after shading data is sent to scanner.
For the backtracking issue, the gl646 datasheet hint that dummy can 
overcome this. I haven't had it working, You'll need to test.

Regards,
Stef
-- next part --
A non-text attachment was scrubbed...
Name: scripts.tar.gz
Type: application/x-compressed-tar
Size: 14589 bytes
Desc: not available

[sane-devel] HP Scanjet 2400c (partial) success, 100 and 300 dpi work both in grayscale and colour (some small changes needed)

[Piotr Mis]

Dnia 2010-05-31, pon o godzinie 06:59 +0200, stef pisze:
 Le dimanche 30 mai 2010 22:22:02 Piotr Mis, vous avez ?crit :

--CUT---
   Hello,
 
   here are the scripts. Just run decode.sh on the UsbSnoop.log recorded 
 under windows. You'll get the right values to put in the tables in the 
 resulting file.
   Be aware that windows driver doesn't always scanned at the resolution 
 you 
 asked. Select a full width area of the smallest height to minimize log size. 
 The value to use are the ones of the final scan you. Thsi scan is the one 
 after shading data is sent to scanner.
   For the backtracking issue, the gl646 datasheet hint that dummy can 
 overcome this. I haven't had it working, You'll need to test.
 
 Regards,
   Stef
Thanks for the scripts. However, I seem to be doing something wrong. 
After starting usbsnoop it scans about 1000 packets, then stops. 
During the scan no packets are captured, so your scripts produce no
output when processing the logs. Have you seen this problem before? Test
OS is Windows XP SP2. 

Regards,

Piotr

[sane-devel] HP Scanjet 2400c (partial) success, 100 and 300 dpi work both in grayscale and colour (some small changes needed)

[stef]

Le vendredi 28 mai 2010 16:07:50 Piotr Mis, vous avez ?crit :
 Very sorry, sent to soon.
 
 Hello,
 
 I was delighted that there is some progress with Scanjet 2400c.
 
 I ran it through some tests, and fixed what I could. Results:
 
 git version of genesys backend works partially:
 
 grayscale:
   * 50  dpi: hangs
   * 100 dpi: works partially, motor step too big, need to switch off
 the scanner to prevent damage
   * 300 dpi: works nicely
   * 600 dpi: picture distorted
 colour:
 as grayscale, but colour channels seem to be switched and slightly
 offset vertically.
 
 I tried to fix it myself and managed to fix the colour channels and the
 motor step in 100dpi.
 
 
 My changes below, comments/advice very welcome:
 
 1. The scanner  (at least mine) is RBG not BGR, this fixes the vertical
 offset as well:
 
 
 diff --git a/backend/genesys_devices.c b/backend/genesys_devices.c
 index a8da85d..3459090 100644
 --- a/backend/genesys_devices.c
 +++ b/backend/genesys_devices.c
 @@ -1173,7 +1173,7 @@ Genesys_Model hp2400c_model = {
 
0, 24, 48,   /* RGB CCD Line-distance correction in
 pixel */
 
 -  COLOR_ORDER_BGR, /* Order of the CCD/CIS colors */
 +  COLOR_ORDER_RGB, /* Order of the CCD/CIS colors */
 
SANE_FALSE,  /* Is this a CIS scanner? */
SANE_FALSE,  /* Is this a sheetfed scanner? */
 
 
 2. The motor definition for 100 dpi from FULL_STEP to HALF_STEP:
 
 diff --git a/backend/genesys_gl646.h b/backend/genesys_gl646.h
 index 5dc3725..695d55f 100644
 --- a/backend/genesys_gl646.h
 +++ b/backend/genesys_gl646.h
 @@ -555,11 +555,11 @@ static Motor_Master motor_master[] = {
 
/* HP2400/G2410 motor settings base motor dpi = 600 */
{MOTOR_HP2400,  50, SANE_TRUE ,  50, HALF_STEP, SANE_FALSE,
 SANE_FALSE, 63,
 -  {MOTOR_HP2400, 100, SANE_TRUE , 100, FULL_STEP, SANE_FALSE,
 SANE_TRUE,  63, 1
 +  {MOTOR_HP2400, 100, SANE_TRUE , 100, HALF_STEP, SANE_FALSE,
 SANE_TRUE,  63, 1
{MOTOR_HP2400, 300, SANE_TRUE , 300, HALF_STEP, SANE_FALSE,
 SANE_TRUE , 63, 3
{MOTOR_HP2400, 600, SANE_TRUE , 600, FULL_STEP, SANE_FALSE,
 SANE_TRUE , 63,
{MOTOR_HP2400,  50, SANE_FALSE,  50, HALF_STEP, SANE_FALSE,
 SANE_FALSE, 63,
 -  {MOTOR_HP2400, 100, SANE_FALSE, 100, FULL_STEP, SANE_FALSE,
 SANE_TRUE,  63, 1
 +  {MOTOR_HP2400, 100, SANE_FALSE, 100, HALF_STEP, SANE_FALSE,
 SANE_TRUE,  63, 1
{MOTOR_HP2400, 300, SANE_FALSE, 300, HALF_STEP, SANE_FALSE,
 SANE_TRUE , 63, 3
{MOTOR_HP2400, 600, SANE_FALSE, 600, FULL_STEP, SANE_FALSE,
 SANE_TRUE , 63,
 
 What I'm still really missing is the preview in xsane, has probably
 something to do with not working 50dpi mode.
 
 Regards,
 
 Piotr
 
Hello,

so with these changes 100 dpi is working ? If you wish I can send you 
my 
log decoding scripts. By recording scanner activity under windows with 
usbsnoop, then processing it through them, you'll have the values to put in 
HP2400 motor and sensor tables for the modes that  aren't working yet.

Regards,
Stef 

[sane-devel] HP Scanjet 2400c (partial) success, 100 and 300 dpi work both in grayscale and colour (some small changes needed)

[Piotr Mis]

Dnia 2010-05-30, nie o godzinie 11:14 +0200, stef pisze: 
 Le vendredi 28 mai 2010 16:07:50 Piotr Mis, vous avez ?crit :
  Very sorry, sent to soon.
  
  Hello,
  
  I was delighted that there is some progress with Scanjet 2400c.
  
  I ran it through some tests, and fixed what I could. Results:
  
  git version of genesys backend works partially:
  
  grayscale:
* 50  dpi: hangs
* 100 dpi: works partially, motor step too big, need to switch off
  the scanner to prevent damage
* 300 dpi: works nicely
* 600 dpi: picture distorted
  colour:
  as grayscale, but colour channels seem to be switched and slightly
  offset vertically.
  
  I tried to fix it myself and managed to fix the colour channels and the
  motor step in 100dpi.
  
  
  My changes below, comments/advice very welcome:
  
  1. The scanner  (at least mine) is RBG not BGR, this fixes the vertical
  offset as well:
  
  
  diff --git a/backend/genesys_devices.c b/backend/genesys_devices.c
  index a8da85d..3459090 100644
  --- a/backend/genesys_devices.c
  +++ b/backend/genesys_devices.c
  @@ -1173,7 +1173,7 @@ Genesys_Model hp2400c_model = {
  
 0, 24, 48,   /* RGB CCD Line-distance correction in
  pixel */
  
  -  COLOR_ORDER_BGR, /* Order of the CCD/CIS colors */
  +  COLOR_ORDER_RGB, /* Order of the CCD/CIS colors */
  
 SANE_FALSE,  /* Is this a CIS scanner? */
 SANE_FALSE,  /* Is this a sheetfed scanner? */
  
  
  2. The motor definition for 100 dpi from FULL_STEP to HALF_STEP:
  
  diff --git a/backend/genesys_gl646.h b/backend/genesys_gl646.h
  index 5dc3725..695d55f 100644
  --- a/backend/genesys_gl646.h
  +++ b/backend/genesys_gl646.h
  @@ -555,11 +555,11 @@ static Motor_Master motor_master[] = {
  
 /* HP2400/G2410 motor settings base motor dpi = 600 */
 {MOTOR_HP2400,  50, SANE_TRUE ,  50, HALF_STEP, SANE_FALSE,
  SANE_FALSE, 63,
  -  {MOTOR_HP2400, 100, SANE_TRUE , 100, FULL_STEP, SANE_FALSE,
  SANE_TRUE,  63, 1
  +  {MOTOR_HP2400, 100, SANE_TRUE , 100, HALF_STEP, SANE_FALSE,
  SANE_TRUE,  63, 1
 {MOTOR_HP2400, 300, SANE_TRUE , 300, HALF_STEP, SANE_FALSE,
  SANE_TRUE , 63, 3
 {MOTOR_HP2400, 600, SANE_TRUE , 600, FULL_STEP, SANE_FALSE,
  SANE_TRUE , 63,
 {MOTOR_HP2400,  50, SANE_FALSE,  50, HALF_STEP, SANE_FALSE,
  SANE_FALSE, 63,
  -  {MOTOR_HP2400, 100, SANE_FALSE, 100, FULL_STEP, SANE_FALSE,
  SANE_TRUE,  63, 1
  +  {MOTOR_HP2400, 100, SANE_FALSE, 100, HALF_STEP, SANE_FALSE,
  SANE_TRUE,  63, 1
 {MOTOR_HP2400, 300, SANE_FALSE, 300, HALF_STEP, SANE_FALSE,
  SANE_TRUE , 63, 3
 {MOTOR_HP2400, 600, SANE_FALSE, 600, FULL_STEP, SANE_FALSE,
  SANE_TRUE , 63,
  
  What I'm still really missing is the preview in xsane, has probably
  something to do with not working 50dpi mode.
  
  Regards,
  
  Piotr
  
   Hello,
 
   so with these changes 100 dpi is working ? If you wish I can send you 
 my 
 log decoding scripts. By recording scanner activity under windows with 
 usbsnoop, then processing it through them, you'll have the values to put in 
 HP2400 motor and sensor tables for the modes that  aren't working yet.
 
 Regards,
   Stef 

Yes, 100 and 300 dpi both produce quite good scans with these settings.
And yes, please do send me the scripts, I'll try to get the rest
working.
   BTW. What would be nice to have is the scanner running smoothly in
300 dpi colour (and higher resolutions in both grayscale and colour).
The motor stops, then runs backwards a few steps, then restarts a few
times during scanning, this seems not to influence scan output. Looks
like the data are not read fast enough from or written too fast by the
scanner. This is exactly what I experience  when scanning using Windows
from within virtual machine, but then, even in 100 dpi grayscale mode.
Can this problem be fixed when using data from your decoding scripts as
well? 

Regards,

Piotr

[sane-devel] HP Scanjet 2400c (partial) success, 100 and 300 dpi work both in grayscale anbd colour after some changes

[Piotr Mis]

Hello,

I was delighted that there is some progress with Scanjet 2400c. So I ran it 
through some tests,
and fixed what I could. Results:

git version of genesys backend works partially:

grayscale:
  * 100 dpi: works partially, motor step too big, need to switch off
the scanner to prevent damage
  * 300 dpi: works nicely
  * 600 dpi: picture distorted

[sane-devel] HP Scanjet 2400c (partial) success, 100 and 300 dpi work both in grayscale and colour (some small changes needed)

[Piotr Mis]

Very sorry, sent to soon.

Hello,

I was delighted that there is some progress with Scanjet 2400c.

I ran it through some tests, and fixed what I could. Results:

git version of genesys backend works partially:

grayscale:
  * 50  dpi: hangs
  * 100 dpi: works partially, motor step too big, need to switch off
the scanner to prevent damage
  * 300 dpi: works nicely
  * 600 dpi: picture distorted
colour: 
as grayscale, but colour channels seem to be switched and slightly
offset vertically.

I tried to fix it myself and managed to fix the colour channels and the
motor step in 100dpi. 


My changes below, comments/advice very welcome:

1. The scanner  (at least mine) is RBG not BGR, this fixes the vertical
offset as well:


diff --git a/backend/genesys_devices.c b/backend/genesys_devices.c
index a8da85d..3459090 100644
--- a/backend/genesys_devices.c
+++ b/backend/genesys_devices.c
@@ -1173,7 +1173,7 @@ Genesys_Model hp2400c_model = {
 
   0, 24, 48,   /* RGB CCD Line-distance correction in
pixel */
 
-  COLOR_ORDER_BGR, /* Order of the CCD/CIS colors */
+  COLOR_ORDER_RGB, /* Order of the CCD/CIS colors */
 
   SANE_FALSE,  /* Is this a CIS scanner? */
   SANE_FALSE,  /* Is this a sheetfed scanner? */


2. The motor definition for 100 dpi from FULL_STEP to HALF_STEP:

diff --git a/backend/genesys_gl646.h b/backend/genesys_gl646.h
index 5dc3725..695d55f 100644
--- a/backend/genesys_gl646.h
+++ b/backend/genesys_gl646.h
@@ -555,11 +555,11 @@ static Motor_Master motor_master[] = {
 
   /* HP2400/G2410 motor settings base motor dpi = 600 */
   {MOTOR_HP2400,  50, SANE_TRUE ,  50, HALF_STEP, SANE_FALSE,
SANE_FALSE, 63,  
-  {MOTOR_HP2400, 100, SANE_TRUE , 100, FULL_STEP, SANE_FALSE,
SANE_TRUE,  63, 1
+  {MOTOR_HP2400, 100, SANE_TRUE , 100, HALF_STEP, SANE_FALSE,
SANE_TRUE,  63, 1
   {MOTOR_HP2400, 300, SANE_TRUE , 300, HALF_STEP, SANE_FALSE,
SANE_TRUE , 63, 3
   {MOTOR_HP2400, 600, SANE_TRUE , 600, FULL_STEP, SANE_FALSE,
SANE_TRUE , 63,  
   {MOTOR_HP2400,  50, SANE_FALSE,  50, HALF_STEP, SANE_FALSE,
SANE_FALSE, 63,  
-  {MOTOR_HP2400, 100, SANE_FALSE, 100, FULL_STEP, SANE_FALSE,
SANE_TRUE,  63, 1
+  {MOTOR_HP2400, 100, SANE_FALSE, 100, HALF_STEP, SANE_FALSE,
SANE_TRUE,  63, 1
   {MOTOR_HP2400, 300, SANE_FALSE, 300, HALF_STEP, SANE_FALSE,
SANE_TRUE , 63, 3
   {MOTOR_HP2400, 600, SANE_FALSE, 600, FULL_STEP, SANE_FALSE,
SANE_TRUE , 63,  

What I'm still really missing is the preview in xsane, has probably
something to do with not working 50dpi mode. 

Regards,

Piotr



  

[sane-devel] HP ScanJet 2400c not supported?

[Giovanni Toraldo]

On Wed, Apr 14, 2010 at 6:32 AM, stef stef.dev at free.fr wrote:
 ? ? ? ?the HP2400 (and its G2410 twin) ?has experimental support for 50, 100, 
 300
 and 600 dpi uncalibrated modes in latest source version. You are welcomed to
 test it by getting it at http://www.sane-project.org/source.html . You'll need
 to compile it.

It's great Stef, it works!

I compiled the git version and added the string hp2400 to
/etc/sane.d/dll.conf, and scanimage  output gives me a nice scan.
In the next week I will make much more tests (various DPI, etc).

Let me know if you need some particular test with this hardware.

Regards.

-- 
Giovanni scorp Toraldo

[sane-devel] HP ScanJet 2400c not supported?

[Giovanni Toraldo]

Hi,

I have the HP ScanJet 2400c and it's not working with sane 1.0.20
(from Debian Unstable).
Someone has any news for the current status of the backend support of
this flatbed scanner?

Thanks.


$ scanimage  test
[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.
scanimage: sane_start: Invalid argument

$ sane-find-scanner
found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x0a01 [hp
scanjet scanner], chip=GL646_HP) at libusb:002:002

$ scanimage -L
device `genesys:libusb:002:002' is a Hewlett Packard ScanJet 2400c
flatbed scanner

$ lsusb -vv
Bus 002 Device 002: ID 03f0:0a01 Hewlett-Packard ScanJet 2400c
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass  255 Vendor Specific Class
  bDeviceSubClass   255 Vendor Specific Subclass
  bDeviceProtocol   255 Vendor Specific Protocol
  bMaxPacketSize0 8
  idVendor   0x03f0 Hewlett-Packard
  idProduct  0x0a01 ScanJet 2400c
  bcdDevice1.01
  iManufacturer   1 Hewlett-Packard
  iProduct2 hp scanjet scanner
  iSerial12 CN74CSR03S
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   39
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0
bmAttributes 0xc0
  Self Powered
MaxPower   48mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass255 Vendor Specific Subclass
  bInterfaceProtocol255 Vendor Specific Protocol
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02  EP 2 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83  EP 3 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0001  1x 1 bytes
bInterval   8
Device Status: 0x0001
  Self Powered

-- 
Giovanni scorp Toraldo

[sane-devel] HP Scanjet 2400c, GL646

[Luke]

Hello,

I've been waiting for a backend for my scanner for almost 2 years and
finally realised, that I can do better than just sit and wait.
According to what I've read in archives of this group it looks like
there are some people interested in development of this backend, but
they lack help. So if there is anything I can do to speed up the
development, I would, because I hate to dual boot only because of the
scanner.
Actually I've tried scanning with scanimage, but like someone has
already pointed out, only got the motor to move for about 2 mm and turn
the lamp on.
I'm willing to provide logs, test, or else - just tell me what do you
need.
Thanks in advance

[sane-devel] HP Scanjet 2400c for genesys

[Parag N(पराग़)]

Hi,
On 7/14/06, St?phane VOLTZ stef...@modulonet.fr wrote:
 Le jeudi 13 juillet 2006 12:17, Parag N() a ?crit:
  Hi Stef,
 
  On 7/12/06, St?phane VOLTZ stef...@modulonet.fr wrote:
   Hello,
   I have started a document at
   http://perso.modulonet.fr/~stefdev/sane/gl646.odt which is in early
   stages, I'll improve it this next days.
 
I have added some contents there. Can you check it?
  Attaching gl646.odt here.
  Regards,
  Parag.

 I'll be off for a few days, will have a look at it next week.

 Are you back from holidays?
Regards,
Parag.
From masn...@gftp.org  Fri Jul 21 21:53:01 2006
From: masn...@gftp.org (Brian Masney)
Date: Fri Jul 21 21:53:08 2006
Subject: [sane-devel] Debug output from Lexmark X1270 scanner
Message-ID: b0e1cc100607211453g1308a254xeccb423fe32bb...@mail.gmail.com

Hi,
   I just bought a Lexmark X1270 printer/scanner. Sane is able to
recognize the scanner using the X1100 driver. Whenever I try to scan
something, the scanner makes a loud noise and the scanning head does
not move. It appears that the head may be trying to go the wrong way.
I am using Sane 1.0.17-3 from the Debian testing distribution. Here is
the debug output from the driver.

[sanei_debug] Setting debug level of lexmark to 20.
[lexmark] SANE Lexmark backend version 1.0-0
[lexmark] sane_init: version_code=0xbff75468
[lexmark] attachLexmark: devname=libusb:002:021
[lexmark] sane_get_devices: device_list=0xbff754b8, local_only=0
[lexmark] sane_open: devicename=libusb:002:021, handle=0xbff77338
[lexmark] sane_open: devname from list: libusb:002:021
[lexmark] init_options: lexmark_device = 0x8246830
[lexmark] sanei_lexmark_x1100_open_device: devnum=0
[lexmark] sane_control_option: handle=0x8246830, opt=0, act=0,
val=0x80db354, info=(nil)
[lexmark] Option value = 6
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 1
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 1
[lexmark] sane_control_option: handle=0x8246830, opt=1, act=0,
val=0x826bc98, info=(nil)
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 2
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 2
[lexmark] sane_control_option: handle=0x8246830, opt=2, act=0,
val=0xbff7734c, info=(nil)
[lexmark] Option value = 150
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 3
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 4
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 4
[lexmark] sane_control_option: handle=0x8246830, opt=4, act=0,
val=0x826bc98, info=(nil)
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 5
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 1
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 1
[lexmark] sane_control_option: handle=0x8246830, opt=1, act=0,
val=0x8284ca8, info=(nil)
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 2
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 2
[lexmark] sane_control_option: handle=0x8246830, opt=2, act=0,
val=0xbff76f04, info=(nil)
[lexmark] Option value = 150
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 2
[lexmark] sane_get_parameters: handle=0x8246830, params=0x80db470
[lexmark] sane_get_parameters: Data size determined as f7314
[lexmark] sane_get_parameters:
[lexmark]   format: SANE_FRAME_RGB
[lexmark]   last_frame: TRUE
[lexmark]   lines 2ee
[lexmark]   depth 8
[lexmark]   pixels_per_line 1c2
[lexmark]   bytes_per_line 546
[lexmark] sane_get_parameters: handle=0x8246830, params=0x80db470
[lexmark] sane_get_parameters: Data size determined as f7314
[lexmark] sane_get_parameters:
[lexmark]   format: SANE_FRAME_RGB
[lexmark]   last_frame: TRUE
[lexmark]   lines 2ee
[lexmark]   depth 8
[lexmark]   pixels_per_line 1c2
[lexmark]   bytes_per_line 546
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 1
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 2
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 4
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 1
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 1
[lexmark] sane_control_option: handle=0x8246830, opt=1, act=0,
val=0x827e8b0, info=(nil)
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 2
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 2
[lexmark] sane_control_option: handle=0x8246830, opt=2, act=0,
val=0xbff7600c, info=(nil)
[lexmark] Option value = 150
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 3
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 4
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 4
[lexmark] sane_control_option: handle=0x8246830, opt=4, act=0,
val=0x8283a28, info=(nil)
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 5
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 1
[lexmark] sane_get_option_descriptor: 

[sane-devel] HP Scanjet 2400c for genesys

[Gerald Murray]

 
 IIRC, after power up, I just selected mono and started scanning.
 If you want, I can do this again and carefully record the single
 steps.
 
 Bye,
   Uwe

Hi,
For now, I do not it re-done.  I am going to try to get an understanding
of what was done in that log, and why.   From what I have looked into
so far, that program seems to have been less than a straight-forward
design.  I need to try some tests for undocumented register(s) to see if
that changes results.  This may take some time as well, so I do not 
expect results soon.  I am hoping to just use this one log, and then
see if that can get any kind of result.
Thanks for producing that log.

Gerald

[sane-devel] HP Scanjet 2400c for genesys

[Uwe Stange]

Hi all,

Gerald Murray wrote:
 I have looked into the log posted on July 5 by Uwe Stange.
 The frontend setup alternates between color and mono three times
 before finally using mono for the scan.
 That it did alternate many times was interesting, I thought.

IIRC, after power up, I just selected mono and started scanning.
If you want, I can do this again and carefully record the single
steps.

Bye,
Uwe

[sane-devel] HP Scanjet 2400c for genesys

[Parag N(पराग़)]

Hi Stef,
On 7/12/06, St?phane VOLTZ stef...@modulonet.fr wrote:
 Hello,
 I have started a document at
 http://perso.modulonet.fr/~stefdev/sane/gl646.odt which is in early stages,
 I'll improve it this next days.

  I have added some contents there. Can you check it?
Attaching gl646.odt here.
Regards,
Parag.
-- next part --
A non-text attachment was scrubbed...
Name: gl646.odt
Type: application/octet-stream
Size: 11178 bytes
Desc: not available
Url : 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060713/6e16805a/gl646.obj
From gmur...@cloudnet.com  Thu Jul 13 05:25:32 2006
From: gmur...@cloudnet.com (Gerald Murray)
Date: Thu Jul 13 16:09:57 2006
Subject: [sane-devel] HP Scanjet 2400c for genesys
Message-ID: 1152768332.44b5d94cef...@webmail.cloudnet.com

Hi all,

I have looked into the log posted on July 5 by Uwe Stange.

The frontend setup alternates between color and mono three times
before finally using mono for the scan.

URB 8, 63, and 104 setup color
URB 23, 78 and 119 setup mono

after 119, finally deciding on mono, that log shows
URBs 705 931 2881 3639 3700 4079 re-assert mono.

That it did alternate many times was interesting, I thought.

Best regards,
Gerald

[sane-devel] HP Scanjet 2400c for genesys

[Stéphane VOLTZ]

Hello,

I have started a document at 
http://perso.modulonet.fr/~stefdev/sane/gl646.odt which is in early stages, 
I'll improve it this next days.


Regards,
Stef

[sane-devel] HP Scanjet 2400c for genesys

[Parag N(पराग़)]

Hi all,
On 7/5/06, Gabriel Guerreiro gabriel.guerre...@gmail.com wrote:
 I have such a log.
 Sending in attachment.

 Sent it to stef last week.
 It's too long to send to the list.

 I could help with some tests too.

 I tried the patch you posted on the list, and made some scans.

 The image is unintelligible and dark.

 I reversed some changes in that patch:
   I don't need to hack the warmup.
   The gamma was being set twice.

 I tried to apply some of the configs of the hp2300, but with no results.
Yes i know that patch is not giving any output. My
observations for this scanner are
1)Warmup code is not passing test so scanner is not moving at all. So
i need to modify warmup code so that scanner will start moving.
2)Also i did similar stuff of configuring HP2400 code like HP2300
wherever it applies but no results.
 Anyway will check log from you all.
Regards,
Parag.

[sane-devel] HP Scanjet 2400c for genesys

[Stéphane VOLTZ]

Le mardi 4 juillet 2006 11:51, Thomas Mader a ?crit?:
 Hello,

 I have a HP Scanjet 2400c and would like to know if I can help somehow to
 speed up the development of the driver for this?
 Can I provide some information about it or something else?


Hello,

this topic has come a few time on the list. The way I see 2400 support 
added 
is to record usb activity under windows, decode it. Then modify the genesys 
backend accordingly. Test the changes, and compare debug output until it is 
close enough to windows behaviour.

However, I think there is a 'roadmap': take the functions one after the 
other 
in the sequence they are used by the  backend. For instance, it make no sense 
to directly jump to the final scan and trying to hack it, since it relies on 
values detected by previous functions.

Here's the call graph for a preview:

sane_open
gl646_init
gl646_init_regs
sanei_genesys_create_slope_table
sanei_genesys_create_gamma_table
gl646_set_fe
gl646_slow_back_home
gl646_send_gamma_table
gl646_set_powersaving

sane_start
gl646_save_power
gl646_set_fe

gl646_search_start_position
gl646_setup_sensor
sanei_genesys_exposure_time
gl646_setup_steps
sanei_genesys_create_slope_table
gl646_send_slope_table
gl646_set_fe
gl646_begin_scan
sanei_genesys_read_data_from_scanner
 this function generates a searh_position16.pnm and 
search_position.pnm
which are pictures of the innings of the scanner. These 
should contain
black and white areas that will be basis for postion 
detection.
gl646_end_scan
sanei_genesys_search_reference_point

... more to come ... 

I'm currently compelting this, but I think making 
gl646_search_start_position 
working will take enough time to let me finish.


Some on these functions already test for HP2300. You can add 
tests and 
values for 2400 there. However, there are two points to take into account:
- for the HP2300 I made the analog frontend work like the MD5345 one 
since
I couldn't make it work like it is in usb logs.
-  motor slope creation should favor 
sanei_genesys_create_slope_table3() over
the sanei_genesys_create_slope_table() currently used.

I append the latest version of the scripts that I use for log decoding. 
 The 
cmd.sh takes a decoded log and emits scanner status at each motor start 
(which is used as a 'commit'). It is usefull since you can take it's output 
to compare scanner internal state with the one from the backend log (output 
of gl646_bulk_write_register() ) right before gl646_begin_scan().

Don't hesitate to ask for more or send patches ...

Regards,
Stef



-- next part --
A non-text attachment was scrubbed...
Name: scripts.tar.bz2
Type: application/x-tbz
Size: 15628 bytes
Desc: not available
Url : 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060706/db074ddb/scripts.tar.bin
From ni...@rmk.co.il  Thu Jul  6 06:49:39 2006
From: ni...@rmk.co.il (Nigel Ridley)
Date: Thu Jul  6 06:50:29 2006
Subject: [sane-devel] Only superuser can scan
In-Reply-To: 44a9414c.3050...@wayforth.co.uk
References: 44a9414c.3050...@wayforth.co.uk
Message-ID: 44acb283.8080...@rmk.co.il

Antony Gelberg wrote:
 Hi all,
 
 This is a Debian testing box.  The normal user can't scan, but it's
 different to permissions problems that I've seen before.  He can see a
 scanner, but there is a question mark in the (incomplete) output of
 sane-find-scanner.  It's a Canon lide 60 (genesys backend).  I have
 bodged the permissions on /proc/bus/usb/001/002 to allow all rw, but no
 difference.  It's running 2.6.15, with udev, not hotplug.
 
 aft:/home/dr# sane-find-scanner -q
 found USB scanner (vendor=0x04a9 [Canon], product=0x221c [CanoScan],
 chip=GL841) at libusb:001:002
 aft:/home/dr# su dr
 dr@aft:~$ sane-find-scanner -q
 found USB scanner (vendor=0x04a9, product=0x221c, chip=GL841?) at
 libusb:001:002
 dr@aft:~$ id
 uid=1001(dr) gid=513(Domain Users)
 groups=46(plugdev),110(scanner),111(saned),513(Domain Users)
 dr@aft:~$ ls -l /proc/bus/usb/001/002
 -rw-rw-rw- 1 root root 57 2006-07-02 17:26 /proc/bus/usb/001/002
 dr@aft:~$ scanimage --version
 scanimage (sane-backends) 1.0.17; backend version 1.0.17
 dr@aft:~$ uname -a
 Linux aft 2.6.15-1-k7 #2 Mon Mar 6 15:42:39 UTC 2006 i686 GNU/Linux
 
 Any advice would be appreciated.
 
 Antony
 


-- 
PrayingForIsrael.net
http://www.prayingforisrael.net/

Messianic E-Cards.com
http://www.messianicecards.com/

[sane-devel] HP Scanjet 2400c for genesys

[Parag N(पराग़)]

Hi,
On 7/6/06, St?phane VOLTZ stef...@modulonet.fr wrote:
 Le mardi 4 juillet 2006 11:51, Thomas Mader a ?crit:
  Hello,
 
  I have a HP Scanjet 2400c and would like to know if I can help somehow to
  speed up the development of the driver for this?
  Can I provide some information about it or something else?
 

 Hello,

 this topic has come a few time on the list. The way I see 2400 
 support added
 is to record usb activity under windows, decode it. Then modify the genesys
 backend accordingly. Test the changes, and compare debug output until it is
 close enough to windows behaviour.

 However, I think there is a 'roadmap': take the functions one after 
 the other
 in the sequence they are used by the  backend. For instance, it make no sense
 to directly jump to the final scan and trying to hack it, since it relies on
 values detected by previous functions.

 Here's the call graph for a preview:

 sane_open
 gl646_init
 gl646_init_regs
 sanei_genesys_create_slope_table
 sanei_genesys_create_gamma_table
 gl646_set_fe
 gl646_slow_back_home
 gl646_send_gamma_table
 gl646_set_powersaving

 sane_start
 gl646_save_power
 gl646_set_fe

 gl646_search_start_position
 gl646_setup_sensor
 sanei_genesys_exposure_time
 gl646_setup_steps
 sanei_genesys_create_slope_table
 gl646_send_slope_table
 gl646_set_fe
 gl646_begin_scan
 sanei_genesys_read_data_from_scanner
  this function generates a searh_position16.pnm and 
 search_position.pnm
 which are pictures of the innings of the scanner. 
 These should contain
 black and white areas that will be basis for postion 
 detection.
 gl646_end_scan
 sanei_genesys_search_reference_point

 ... more to come ...

 I'm currently compelting this, but I think making 
 gl646_search_start_position
 working will take enough time to let me finish.


 Some on these functions already test for HP2300. You can add 
 tests and
 values for 2400 there. However, there are two points to take into account:
 - for the HP2300 I made the analog frontend work like the MD5345 one 
 since
 I couldn't make it work like it is in usb logs.
 -  motor slope creation should favor 
 sanei_genesys_create_slope_table3() over
 the sanei_genesys_create_slope_table() currently used.

 I append the latest version of the scripts that I use for log 
 decoding.  The
 cmd.sh takes a decoded log and emits scanner status at each motor start
 (which is used as a 'commit'). It is usefull since you can take it's output
 to compare scanner internal state with the one from the backend log (output
 of gl646_bulk_write_register() ) right before gl646_begin_scan().

 Don't hesitate to ask for more or send patches ...

 Regards,
 Stef
 From my side Function call trace for gl646_init(). Its not recursive trace.
===
 gl646_init
sanei_genesys_get_status
gl646_init_regs
   sanei_genesys_create_slope_table
   sanei_genesys_create_gamma_table
   sanei_usb_control_msg
   sanei_genesys_write_register
  gl646_bulk_write_register
  gl646_asic_test
  gl646_set_fe
  gl646_bulk_read_data
  gl646_slow_back_home
  sanei_genesys_init_shading_data
  gl646_repark_head
  gl646_send_gamma_table
  gl646_set_powersaving
=
 I will submit more call trace by tomorrow.
Regards,
Parag.

[sane-devel] HP Scanjet 2400c for genesys

[Parag N(पराग़)]

Hi,
On 7/4/06, Thomas Mader thez...@gmail.com wrote:
 Hello,

 I have a HP Scanjet 2400c and would like to know if I can help somehow to
 speed up the development of the driver for this?
 Can I provide some information about it or something else?

   I am also working on this scanner. Can you give me Windows Log for
this scanner. You need to send me USB log of scanner just after its
power up using 
http://benoit.papillault.free.fr/stats/get.php?location=../usbsnoop/sniff-bin-1.8.zip.
Install this zip. start SniffUSB.exe and install sniffer on the
location where you can see Scanner is attached and then powerup
scanner and do take some preview scan of any document under windows.
Then close sniffer application and send me usbsnoop.log file under
windows directory.
Regards,
Parag.

[sane-devel] HP Scanjet 2400c for genesys

[Uwe Stange]

Hi,

great, I use this scanner too.

Parag N() wrote:
 Install this zip. start SniffUSB.exe and install sniffer on the
 location where you can see Scanner is attached and then powerup
 scanner and do take some preview scan of any document under windows.
 Then close sniffer application and send me usbsnoop.log file under
 windows directory.

I did as you told. You can find the log file under the following link:

http://www.uwe-stange.de/download/usbsnoop.zip

Tell me if you need more logs.

 Regards,
 Parag.

Bye,
Uwe

[sane-devel] HP Scanjet 2400c for genesys

[Thomas Mader]

Hi Parag,

very nice to hear that development is under way. You can get my log from 
http://members.chello.at/ezechiel/usbsnoop.tar.bz2
I hope it's not too much trash in it. If it's unusable or if you need 
something else, just call.

regards,
Thomas

On Wednesday 05 July 2006 15:23, you wrote:
 Hi,

 On 7/4/06, Thomas Mader thez...@gmail.com wrote:
  Hello,
 
  I have a HP Scanjet 2400c and would like to know if I can help somehow to
  speed up the development of the driver for this?
  Can I provide some information about it or something else?

I am also working on this scanner. Can you give me Windows Log for
 this scanner. You need to send me USB log of scanner just after its
 power up using
 http://benoit.papillault.free.fr/stats/get.php?location=../usbsnoop/sniff-b
in-1.8.zip. Install this zip. start SniffUSB.exe and install sniffer on the
 location where you can see Scanner is attached and then powerup
 scanner and do take some preview scan of any document under windows.
 Then close sniffer application and send me usbsnoop.log file under
 windows directory.
 Regards,
 Parag.
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
Url : 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060705/83671e49/attachment.pgp
From subscripti...@gnumed.net  Thu Jul  6 00:37:29 2006
From: subscripti...@gnumed.net (Horst Herb)
Date: Thu Jul  6 00:47:03 2006
Subject: [sane-devel] Avision scanner timeout
In-Reply-To: 001701c6a043$78b0bf20$5f00a...@rx30.com
References: 001701c6a043$78b0bf20$5f00a...@rx30.com
Message-ID: 200607061037.29570.subscripti...@gnumed.net

On Thursday 06 July 2006 00:58, Kerry Menzel wrote:
 I am trying to get an Avision AV220 scanner to work with Redhat Linux 9
 (2.4.29-abi). When I connect the scanner the hpusbsci module is

I have that scanner (with USB interface).
It works nicely with the avision module, including Duplex
(but I am using a 2.6.17 kernel on Debian Linux)

Horst

[sane-devel] HP ScanJet 2400c

[Stéphane VOLTZ]

Le Lundi 14 Novembre 2005 21:54, carlos a ?crit?:
 Hi Stef,
I know how to program in C, but I know nothing about how a scanner
 works, in any case, I have an hp2400c which has been doing a great job as a
 brick, if you would be so kind so as to send me those scripts I may give it
 a try to write a backend for that scanner.
 thanks,

 carlos.

Hello,

here they are. Don't hesitate to ask further questions on the list.

Regards,
Stef
-- next part --
A non-text attachment was scrubbed...
Name: scripts.tar.bz2
Type: application/x-tbz
Size: 8219 bytes
Desc: not available
Url : 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20051117/804ea5a8/scripts.tar.bin
From lno...@dragon.unideb.hu  Thu Nov 17 08:17:34 2005
From: lno...@dragon.unideb.hu (Levente =?ISO-8859-1?Q?Nov=E1k?=)
Date: Thu Nov 17 08:33:08 2005
Subject: [sane-devel] Re: Re: Re: epson 3490 - transparency unit problem
In-Reply-To: 200511162349.28532.oliver.schwa...@gmx.de
References: 4376277f.3090...@free.fr
200511152113.01824.oliver.schwa...@gmx.de 437b7dfb.20...@free.fr
200511162349.28532.oliver.schwa...@gmx.de
Message-ID: 1132215454.12161.7.ca...@novak.chem.klte.hu

On Wed, 2005-11-16 at 23:49 +0100, Oliver Schwartz wrote:

 
 I can somehow understand that it happens at 2400 dpi. In fact I think 
 that 2400 dpi won't ever work and should be disabled, or replaced by 
 1800 dpi, which should be ok.

Please wait until I test it out. And I suppose you meant 1600 dpi (which
is a multiple of 800) instead of 1800 dpi (and Patrick wanted to say
3200 dpi instead of 3600). AFAIK our scanner's maximum resolution is
3200 dpi. If I'm right, the PF 3490 has a 800 dpi of linear CCD
resolution, higher ones are 'faked' by offsetted sensor elements. In
this case multiples of 800 should work.

 I'm a bit surprised about the effect at 3600 dpi. Can you send me an 
 image which shows the effect?
 

I did not have any problems at 3200 dpi. And before the CVS change, the
only problem was the now solved interlacing phenomenon.

Levente

[sane-devel] HP ScanJet 2400c

[carlos]

Hi Stef,
   I know how to program in C, but I know nothing about how a scanner works,
in any case, I have an hp2400c which has been doing a great job as a brick,
if you would be so kind so as to send me those scripts I may give it a try to 
write a backend for that scanner.
thanks,

carlos.

On 07/11/05 22:05, St?phane VOLTZ wrote:
 Le Lundi 7 Novembre 2005 18:49, Kristoffer a ?crit?:
  On Mon, 07 Nov 2005 17:49:06 +0100, Kristoffer k...@online.no wrote:
   I want to get it working! And I see that the genesys author in
   genesys.conf have it commented out and to be uncommented only for
   development purposes.
  
   Can the author comment on the state of 2400? I would be delighted to
   help, Maybe i could also make the support in genesys backend complete
   for this driver, if he/you can't, but since i've never made a c program
   before(or anything other than very basic bash/dos batch scripts and MMF)
   i could use some help.
  
   what i'm thinking is 1. grab the source 2. change the code to what it
   looks like windows driver is doing(by snooping) 3. then i'd need help on
   howto compile it and test it fast to see if it is functioning correctly.
   4.maybe you could implement it in your driver or tell me howto ;) hey
   it's fun!
  
   If you wish, I can provide you with my awk scripts that turn usb logs 
 into 
 low/mid level genesys functions. Which ease the developpement. 
   I'd recommend to play with sane 1.016 sources, since the experimental 
 version 
 is now not working any more for hp2300/md6471 due to some exposure_time 
 improvement. When this will be resolved, you may bring back you change into 
 it.
   The code path to modifiy is the one taken by th hp2300 (look fo HP2300) 
 in 
 code. You'll have to figure how the  right register related constants to put 
 into genesys_devices.c .
 
 Regards,
   Stef
 
 --
 sane-devel mailing list: sane-devel@lists.alioth.debian.org
 http://lists.alioth.debian.org/mailman/listinfo/sane-devel
 Unsubscribe: Send mail with subject unsubscribe your_password
  to sane-devel-requ...@lists.alioth.debian.org
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20051114/c82ac897/attachment.pgp
From till.kamppe...@gmx.net  Tue Nov 15 01:41:30 2005
From: till.kamppe...@gmx.net (Till Kamppeter)
Date: Tue Nov 15 02:06:15 2005
Subject: [sane-devel] 2 new paperweights: HP ScanJet 3800 and 4890
Message-ID: 43793cca.2040...@gmx.net

Oi,

here at Mandriva we got two new scanners from HP for testing/hardware 
certification: ScanJet 3800 and ScanJet 4890. Both do not work with 
current SANE. I have run the following commands on them:

lsusb
lsusb -vvv
sane-find-scanner -v -v

On the SANE has found a GL841 chipset and so I tried to run it with the 
genesys backend. I added usb 0x03f0 0x1b05 to genesys.con and ran

SANE_DEBUG_GENESYS=255 scanimage -L

but also without success.

The output of all commands you find here:

http://www.linuxprinting.org/till/tmp/hpscanjet3800.txt
http://www.linuxprinting.org/till/tmp/hpscanjet4890.txt

I wanted to add the 4890 (the 3800 is already there) to the list of 
unsupported scanners via

http://www.sane-project.org/contrib.html

but the data was not accepted. I got an error message that in one of the 
fields invalid data was entered. Therefore I post the info here on the list.

Till

[sane-devel] HP ScanJet 2400c

[Stéphane VOLTZ]

Le Lundi 7 Novembre 2005 18:49, Kristoffer a ?crit?:
 On Mon, 07 Nov 2005 17:49:06 +0100, Kristoffer k...@online.no wrote:
  I want to get it working! And I see that the genesys author in
  genesys.conf have it commented out and to be uncommented only for
  development purposes.
 
  Can the author comment on the state of 2400? I would be delighted to
  help, Maybe i could also make the support in genesys backend complete
  for this driver, if he/you can't, but since i've never made a c program
  before(or anything other than very basic bash/dos batch scripts and MMF)
  i could use some help.
 
  what i'm thinking is 1. grab the source 2. change the code to what it
  looks like windows driver is doing(by snooping) 3. then i'd need help on
  howto compile it and test it fast to see if it is functioning correctly.
  4.maybe you could implement it in your driver or tell me howto ;) hey
  it's fun!
 
If you wish, I can provide you with my awk scripts that turn usb logs 
into 
low/mid level genesys functions. Which ease the developpement. 
I'd recommend to play with sane 1.016 sources, since the experimental 
version 
is now not working any more for hp2300/md6471 due to some exposure_time 
improvement. When this will be resolved, you may bring back you change into 
it.
The code path to modifiy is the one taken by th hp2300 (look fo HP2300) 
in 
code. You'll have to figure how the  right register related constants to put 
into genesys_devices.c .

Regards,
Stef