[sane-devel] Canonscan N 650U LIDE Scanner does not scan but makes terrible noise

[Winni]

Hi,

with the help of Andrea Vai I was able to modify the file
plustek-usbdevs.c @ line 2064 entering 0.76 for dMaxMotorSpeed.

After that Andrea Vai showed me via Email recompiling 
sane-backends-git20130901

Only recompiling did not work, so we had to rename and modify the 
symbolic links in /usr/lib/x86_64-linux-gnu/sane from

libsane-plustek.so -> /usr/lib/sane/libsane-plustek.so.1.0.22
libsane-plustek.so.1 -> /usr/lib/sane/libsane-plustek.so.1.0.22

to

libsane-plustek.so -> /usr/lib/sane/libsane-plustek.so.1.0.24
libsane-plustek.so.1 -> /usr/lib/sane/libsane-plustek.so.1.0.24

output scanimage -L

[sanei_debug] Setting debug level of plustek to 5.
[plustek] Plustek backend V0.52-11, part of sane-backends 1.0.24git
[plustek] Retrieving all supported and conntected devices
[plustek] Available and supported devices:
[plustek] Device: >libusb:006:002< - 0x04a9x0x2206
[plustek] usbDev_open(auto,) - 0xbcae70
[plustek] Vendor ID=0x04A9, Product ID=0x2206
[plustek] usbio_DetectLM983x
[plustek] usbio_DetectLM983x: found LM9832/3
[plustek] Detected vendor & product ID: 0x04A9-0x2206
[plustek] Device description for >0x04A9-0x2206< found.
[plustek] usb_initDev(38,0x04a9,-1)
[plustek] Device WAF  : 0x00004002
[plustek] Transferrate: 1000000 Bytes/s
[plustek] Device Flags: 0x00000000
[plustek] Vendor adjusted to: >Canon<
[plustek] LAMP-STATUS: 0x00000000 (off)
[plustek] RESETTING REGISTERS(-1) - 0x80
[plustek] MISC I/O after RESET: 0x66, 0x16, 0x91
[plustek] Calibration file-names set to:
[plustek] >/root/.sane/Canon_CanoScan_N650U_N656U-coarse.cal<
[plustek] >/root/.sane/Canon_CanoScan_N650U_N656U-fine.cal<
[plustek] usb_SetScanParameters()
[plustek] usb_GetMCLKDivider()
[plustek] usb_GetMCLKDiv()
[plustek] * PhyBytes   = 6
[plustek] * PhyLines   = 4
[plustek] * TotalBytes = 24
[plustek] * Scansteps=72 (9*1200/150)
[plustek] usb_SetScanParameters() done.
[plustek] usbDev_getCaps()
[plustek] Scanner information:
[plustek] Vendor : Canon
[plustek] Model  : CanoScan N650U/N656U
[plustek] Flags  : 0x00000000
[plustek] drvclose()
[plustek] usbDev_stopScan()
[plustek] usbDev_ScanEnd(), start=0, park=0
[plustek] usbDev_close()
device `v4l:/dev/video0' is a Noname WebCam SCB-0320N virtual device
device `plustek:libusb:006:002' is a Canon CanoScan N650U/N656U flatbed 
scanner
[plustek] Shutdown called (dev->fd=-1, libusb:006:002)
[plustek] Waiting for scanner-ready...
[plustek] Switching lamp off...
[plustek] LAMP-STATUS: 0x00000000 (off)
[plustek] LAMP-STATUS: 0x00000000 (off)
[plustek] Lamp-Timer stopped


BUT (!) with KanotixDFx86_64 Distro I can only start the GUI Frontend as 
root with [ALT f2] kdesu XSane

then I get a dialogue-box which tells me in German ( I translate)

#Warning
#You try to execute XSane as ROOT. This is really DANGEROUS!
#Don't send any error messages if you get problems when executing XSane 
#as root. You are alone !

Then I can choose between 'continue on your own risk' or 'cancel'

Thus, I am alone I go on on my own risk and there you see.

My Canonscan 650U scans as it should. I tried different resolutions.
NO TERRIBLE SOUND !!! YES !!!

I guess it has something to do with rights that I have to use Xsane and 
scanimage -L as root, because using the normal user the device will not 
be recognized. So if someone here has an idea it is highly appreciated.

Until now thank you very much to Andrea Vai showing me how to recompile 
and tweak.

Regards,
Winni



Am 29.08.2013 08:27, schrieb Gerhard Jäger:> On Thursday 29 August 2013 
08:14:53 Andrea Vai wrote:
 >> Hi, thank you for the reply. With the essential help from Gerhard we
 >> seem to have found the issue. See below.
 >>
 >> Il giorno mer, 28/08/2013 alle 20.29 +0000, coxster dillon ha scritto:
 >>> The only thing I can think of, that maybe different between Sane on
 >>> Linux and Twain on Windoze is simply perhaps the speed or more
 >>> specifically the timing between commands issued.  I do not know the
 >>> scanner API in detail enough to be more specific.  If you send the
 >>> steps to the motor rather than say go to position Y, then the timing
 >>> of those steps is probably important.
 >>
 >> That makes sense, as Gerhard suggested me:
 >> -----------------------------------------------------------------------
 >> Are you able to compile the Plustek backend? If yes, you might play
 >> with the following values in the file plustek-usbdevs.c @ line 2064 and
 >> 2065
 >>
 >> There you see the following:
 >> ** Canon N650U/N656U */
 >
 > STOP!
 >
 > Coxter is talking about a LiDE30! That's why I pointed to another
 > code section.
 >
 > While writing the support for LiDE20 and 30 I already did the USBsnoop
 > stuff - you're welcome to repeat...
 >
 > - Gerhard
 >