libusb-1.0 port to OS/2 - help needed

[ivan]

Paul, here are the outputs from my usb scanner.

[Paul Smedley]

Paul, do you mean that bluetooth may be ported to os/2 ecomstation?

It may be possible. Of course, whether this means bluetooth keyboards/mice can be supported, remains to be seen.

[Paul Smedley]

This is the output
scanimage >output.pnm 2>debugoutput.txt

Interesting - despite the previous log showing the scanner was detected:
[sanei_usb] sanei_usb_init: Looking for libusb-1.0 devices
[sanei_usb] sanei_usb_init: found 0 devices


Does lsusb see the scanner?

[Paul Smedley]

Paul, here are the outputs from my usb scanner.

out.pnm shows:
device `epson2:libusb:001:001' is a Epson Perfection640 flatbed scanner

so this is the result of scanimage -L?

try scanimage > output.pnm and see if the scanner fires up.

[Wim Brul]

Hi Paul,

I used the following to obtain debugoutput.txt from my CanoScan LiDE 210 scanner. 

@echo off
setlocal
set beginlibpath=d:\sane23\lib;
set SANE_CONFIG_DIR=d:\sane23\etc\sane.d
set SANE_DEBUG_GENESYS=255
set SANE_DEBUG_SANEI_USB=255
d:\sane23\scanimage -L >output.pnm 2>debugoutput.txt
endlocal
exit

And it reports that the scanner is not configured:

[sanei_debug] Setting debug level of sanei_usb to 255.
[sanei_usb] sanei_usb_init: marking existing devices
[sanei_usb] sanei_usb_init: Looking for kernel scanner devices
[sanei_usb] sanei_usb_init: initializing libusb-1.0
[sanei_usb] sanei_usb_init: Looking for libusb-1.0 devices
[sanei_usb] sanei_usb_init: device 0x04a9/0x190a at 001:001 is not configured
[sanei_usb] sanei_usb_init: found 0 devices

Regards, Wim.

[Paul Smedley]

I used the following to obtain debugoutput.txt from my CanoScan LiDE 210 scanner. 
And it reports that the scanner is not configured:

Can you confirm this is with:
12/05/13  10:01       5,769,032           0  scanimage.exe

[ivan]

Paul, just doing scanimage >output.pnm on my Epson 640U produces a black and white scan - just readable, would create problems with OCR.

[Wim Brul]

I used the following to obtain debugoutput.txt from my CanoScan LiDE 210 scanner. 
And it reports that the scanner is not configured:

Can you confirm this is with:
12/05/13  10:01       5,769,032           0  scanimage.exe

Yes, that is the one I used. However, I shot myself in the foot since I had the scanner attached to my own usbecd.sys device driver at the same time. That driver never issues a set configuration request by itself although it always sets a flag that it has done so upon device attachment. Without that driver the scanner is configured. 

[muffetta]

Last update:
lsusbout positive and only available without NeoWPS USB widget (using it attach and detach infinitly and lsusbout is null (0 size).
However scanimage/tame still don't work.
Regards.

[Paul Smedley]

Hi Ivan,

Paul, just doing scanimage >output.pnm on my Epson 640U produces a black and white scan - just readable, would create problems with OCR.

Yup - that's OK - so the scanner works?

try something like:
scanimage -mode color -resolution 300 -x 210 -y 297 > output.pnm

I think the default with the epson2 backend is for lineart mode.
scanimage --help -d epson2 will show you all the options for controlling the scanner backend.

[Paul Smedley]

I used the following to obtain debugoutput.txt from my CanoScan LiDE 210 scanner. 
And it reports that the scanner is not configured:

Can you confirm this is with:
12/05/13  10:01       5,769,032           0  scanimage.exe

Yes, that is the one I used. However, I shot myself in the foot since I had the scanner attached to my own usbecd.sys device driver at the same time. That driver never issues a set configuration request by itself although it always sets a flag that it has done so upon device attachment. Without that driver the scanner is configured.

The log shows:
[genesys] attach: found Canon flatbed scanner LiDE 210 at libusb:001:001

I don't seen any scan attempt. What command line was used?

To try a scan, just try:
scanimage > output.pnm

If it fails:
@echo off
setlocal
set beginlibpath=d:\sane23\lib;
set SANE_CONFIG_DIR=d:\sane23\etc\sane.d
set SANE_DEBUG_GENESYS=255
set SANE_DEBUG_SANEI_USB=255
d:\sane23\scanimage  >output.pnm 2>debugoutput.txt
endlocal
exit

[ivan]

Hi Paul, yes, it scans.

using scanimage --mode color --resolution 300 I got the attached output - converted to jpg to take up less space.

Using --format tif produces the expected tif file output and all the resolutions work

I used the page I did because it represents the type of pages I have to copy and sometimes OCR.  In fact I'm quite pleased with the results, thank you.

I notice there are a lot of options in the epson2 backend listed as [inactive], will any of these be made active in the future?

[Paul Smedley]

Hi Ivan,

using scanimage --mode color --resolution 300 I got the attached output - converted to jpg to take up less space.

Using --format tif produces the expected tif file output and all the resolutions work

I used the page I did because it represents the type of pages I have to copy and sometimes OCR.  In fact I'm quite pleased with the results, thank you.

I notice there are a lot of options in the epson2 backend listed as [inactive], will any of these be made active in the future?

Thanks for the feedback. IN terms of the [inactive] options in the epson2 backend, that's a question for the Sane guys - I jsut pored it to OS/2

Cheers,

Paul.

[Wim Brul]

The log shows: [genesys] attach: found Canon flatbed scanner LiDE 210 at libusb:001:001
I don't seen any scan attempt. What command line was used?

I used d:\sane23\scanimage -L >output.pnm 2>debugoutput.txt

To try a scan, just try: scanimage > output.pnm

[D:\sane23]scanimage > output.pnm
scanimage: open of device genesys:libusb:001:001 failed: Invalid argument

That failed so I used:

@echo off
setlocal
set beginlibpath=d:\sane23\lib;
set SANE_CONFIG_DIR=d:\sane23\etc\sane.d
set SANE_DEBUG_GENESYS=255
set SANE_DEBUG_SANEI_USB=255
rem - d:\sane23\scanimage -L >output.pnm 2>debugoutput.txt
d:\sane23\scanimage >output.pnm 2>debugoutput.txt
endlocal
exit

This gives "sanei_usb_control_msg: libusb complained: Input/output error" always at the same spot when I try again after unplug/replug of the scanner. This is different from your earlier sane-1.0.22-os2-20120131.zip product which allows me to actual obtain a scan.

[Paul Smedley]

The log shows: [genesys] attach: found Canon flatbed scanner LiDE 210 at libusb:001:001
I don't seen any scan attempt. What command line was used?

I used d:\sane23\scanimage -L >output.pnm 2>debugoutput.txt

To try a scan, just try: scanimage > output.pnm

[D:\sane23]scanimage > output.pnm
scanimage: open of device genesys:libusb:001:001 failed: Invalid argument

That failed so I used:

@echo off
setlocal
set beginlibpath=d:\sane23\lib;
set SANE_CONFIG_DIR=d:\sane23\etc\sane.d
set SANE_DEBUG_GENESYS=255
set SANE_DEBUG_SANEI_USB=255
rem - d:\sane23\scanimage -L >output.pnm 2>debugoutput.txt
d:\sane23\scanimage >output.pnm 2>debugoutput.txt
endlocal
exit

This gives "sanei_usb_control_msg: libusb complained: Input/output error" always at the same spot when I try again after unplug/replug of the scanner. This is different from your earlier sane-1.0.22-os2-20120131.zip product which allows me to actual obtain a scan.

Interesting. Any change of a debug log from 1.0.22? Might also be worth sending you a scanimage.exe with libusb logging enabled....