plustek: Thread: Canon N670U stops during scanning


[<<] [<] Page 1 of 1 [>] [>>]
Subject: Canon N670U stops during scanning
From: Capers ####@####.####
Date: 31 Dec 2002 03:34:24 -0000
Message-Id: <20021231032653.WSHF22267.mta01-svc.ntlworld.com@[10.137.100.61]>

I've just obtained a Canon N670U scanner, and have been trying to use it with xsane. However, I'm having problems with the scanner locking up part way through a scan or preview scan.

I'm using a freshly compiled sane 1.0.9, with plustek 0.45-TEST5 and xsane 0.90 on a Red Hat 8 system.

The lockups mainly occur when calibration is switched on in plustek.conf, but can occur with no calibration. Lockups also occur if I set the gain values manually in the config file. 

Below is debug output from using xsane, where I've set the gain values manually, and calibration is switched off. The output is similar with calibration enabled.

[plustek] sane_start
[plustek] drvopen()
[plustek] usbDev_open(/dev/usb/scanner0,0x04A9-0x220D)
[plustek] Vendor ID=0x04A9, Product ID=0x220D
[plustek] usbio_DetectLM983x
[plustek] usbio_DetectLM983x: found LM9832/3
[plustek] Device description for >0x04A9-0x220D< found.
[plustek] usb_initDev(37,0x04a9,1)
[plustek] Device WAF: 0x0000004a
[plustek] Vendor adjusted to: >Canon<
[plustek] LAMP-STATUS: 0x00000000
[plustek] RESETTING REGISTERS(1)
[plustek] MISC I/O after RESET: 0x66, 0x16, 0x91
[plustek] usb_SetScanParameters()
[plustek] * HDPI: 4.000
[plustek] * XDPI=150, HDPI=4.000
[plustek] * DataPixelStart=75, LineEnd=75
[plustek] * Full Steps to Skip at Start = 0x0000
[plustek] usb_GetMCLKDivider()
[plustek] * Integration Time Adjust = 0 (HDPI=4.000,MCLKD=4.000)
[plustek] * Current MCLK Divider = 4.000000
[plustek] * PC-Rate mclkdiv=1.500000
[plustek] * MOTOR-Settings: PWM=0x08, PWM_DUTY=0x1f
[plustek] * PhyBytes   = 2
[plustek] * PhyLines   = 3221218396
[plustek] * TotalBytes = 2147441192
[plustek] * PL=295, coeffsize=216, scaler=3
[plustek] * PauseLimit = 295, [0x4e] = 0x91, [0x4f] = 0x01
[plustek] usb_SetScanParameters() done.
[plustek] usbDev_getCaps()
[plustek] usbDev_getLensInfo()
[plustek] wMAX=9600, WPHYMAX=1200
[plustek] scanmode = 3
[plustek] usbDev_getCropInfo()
[plustek] usb_GetImageInfo()
[plustek] PPL = 634
[plustek] LPA = 876
[plustek] BPL = 1902
[plustek] bright 0 contrast 0
[plustek] usbDev_setScanEnv()
[plustek] usb_SaveImageInfo()
[plustek] dwFlag = 0x00000800
[plustek] usb_GetImageInfo()
[plustek] Preview Mode set!
[plustek] Setting map[0] at 0x0813fec8
[plustek] Setting map[1] at 0x08143ec8
[plustek] Setting map[2] at 0x08147ec8
[plustek] usbDev_startScan()
[plustek] * HDPI: 8.000
[plustek] * XDPI=75, HDPI=8.000
[plustek] LAMP-STATUS: 0x00000000
[plustek] Switching Lamp on
[plustek] Warmup-Timer started
[plustek] LAMP-STATUS: 0x00000001
[plustek] Lamp-Timer stopped
[plustek] dwflag = 0x40000000 dwBytesPerLine = 1902, dwLinesPerScan = 876
[plustek] TIME START
[plustek] sane_start done
[dll] sane_get_parameters(handle=0x81305b0,params=0x8187b3c)
[plustek] reader process...
[plustek] reader_process started
[plustek] reader_process:starting to READ data (1666152 bytes)
[plustek] buf = 0x413f0008
[plustek] usbDev_readImage()
[plustek] usb_DoCalibration()
[plustek] goto shading position
[plustek] ShadingOriginY=30
[dll] sane_set_io_mode(handle=0x81305b0,nonblocking=1)
[plustek] sane_set_io_mode: non_blocking=1
[plustek] sane_set_io_mode done
[dll] sane_get_select_fd(handle=0x81305b0,fdp=0xbfffe7dc)
[plustek] sane_get_select_fd
[plustek] sane_get_select_fd done
[plustek] shading position reached
[plustek] SETMCLK[9/2], using entry 6: 2.000000, 600
[plustek] --> BYPASS
[plustek] SETMCLK[9/2], using entry 0: 6.000000, 75
[plustek] <-- BYPASS
[plustek] MOTOR: PWM=0x08, PWM_DUTY=0x33 0x45=0x13 0x48=0x00, 0x49=0xf2
[plustek] MCLK_FFW = 6 --> 0x0a
[plustek] Calibration done
-----------------------
[plustek] Static Gain:
[plustek] REG[0x3b] = 33
[plustek] REG[0x3c] = 35
[plustek] REG[0x3d] = 29
[plustek] Static Offset:
[plustek] REG[0x38] = 1
[plustek] REG[0x39] = 1
[plustek] REG[0x3a] = 1
[plustek] -----------------------
[plustek] calibration done.
[plustek] usb_SetScanParameters()
[plustek] * HDPI: 8.000
[plustek] * XDPI=75, HDPI=8.000
[plustek] * DataPixelStart=75, LineEnd=5147
[plustek] * Full Steps to Skip at Start = 0x0190
[plustek] usb_GetMCLKDivider()
[plustek] * Integration Time Adjust = 0 (HDPI=8.000,MCLKD=6.000)
[plustek] * Current MCLK Divider = 6.000000
[plustek] * PC-Rate mclkdiv=1.500000
[plustek] * MOTOR-Settings: PWM=0x08, PWM_DUTY=0x3f
[plustek] * PhyBytes   = 636
[plustek] * PhyLines   = 876
[plustek] * TotalBytes = 1671408
[plustek] * PL=294, coeffsize=216, scaler=3
[plustek] * PauseLimit = 294, [0x4e] = 0x91, [0x4f] = 0x01
[plustek] usb_SetScanParameters() done.
[plustek] Warmup: Waiting 45 seconds
[plustek] ImageProc is: ColorDuplicate8_2
[plustek] usb_ScanBegin()
[plustek] usb_MapDownload()
[plustek] brightness   = 0 -> 0
[plustek] contrast*100 = 0 -> 100
[plustek] usb_MapDownload() done.
[plustek] --> BYPASS
[plustek] Reading the data now!
[plustek] PhyDpi.x         = 75
[plustek] PhyDpi.y         = 75
[plustek] UserDpi.x        = 75
[plustek] UserDpi.y        = 75
[plustek] NumberOfScanBufs = 137
[plustek] LinesPerScanBufs = 4384
[plustek] dwPhyBytes       = 636
[plustek] dwPhyPixels      = 634
[plustek] dwTotalBytes     = 1671408
[plustek] dwPixels         = 634
[plustek] dwBytes          = 1902
[plustek] dwValidPixels    = 634
[plustek] dwBytesScanBuf   = 61056
[plustek] dwLinesDiscard   = 0
[plustek] dwLinesToSkip    = 1
[plustek] dwLinesUser      = 876
[plustek] dwBytesLine      = 1902
[plustek] usb_IsDataAvailableInDRAM()
[plustek] Data is available

After this, the scanner head moves some distance down the bed, and then stops, and I have to kill the process.

Is this a known problem, and are there any workarounds?
Leaving the calibration off gives very pink images, that aren't really usable.

If you need further information, just ask.

Thanks,

- Martyn Capewell

Subject: Re: Canon N670U stops during scanning
From: Capers ####@####.####
Date: 31 Dec 2002 13:13:05 -0000
Message-Id: <20021231130533.DEVJ900.mta05-svc.ntlworld.com@[10.137.100.64]>

> 
> From: "Craig Cooper" ####@####.####
> Date: 2002/12/31 Tue AM 09:42:21 GMT
> To: ####@####.####
> Subject: Re: Canon N670U stops during scanning
> 
> Hi,
> 
> I am using freshly compiled sane109 and test4 with 670U very successfully.
> 
> The trick I used was to do all the steps, and use YaST2 or DrakConf to
> install new scanner (right, drakconf doesn't like plusteks). Once this is
> done, RE-EDIT the plustek.conf file. There should be some more options there
> for platter size etc (defaults are fine - full A4 size). Also, turn warmup
> to 0.
> 
> Hope this helps (?) or try test4

Would it be possible to take a look at your plustek.conf file?

I may go back to TEST4 today, and see if that helps.

One further note: I only have a dual P2 300MHz (A Dell Workstation 400). Is this sufficient to handle the processing requirement?

- Martyn Capewell

Subject: Re: Canon N670U stops during scanning
From: Capers ####@####.####
Date: 1 Jan 2003 21:44:32 -0000
Message-Id: <20030101213645.MWVB14589.mta02-svc.ntlworld.com@[10.137.100.62]>

> From: "Craig Cooper" ####@####.####
> Date: 2002/12/31 Tue PM 08:54:35 GMT
> To: ####@####.####
> Subject: Re: Canon N670U stops during scanning
> 
> Hi Again,
> 
> Will send the .conf file later today (am in WinXP at moment). I have a
> Tri-boot (through NTLDR) system running Win98, XP Pro, and Mandrake 9.0
> Linux all on separate partitions. Running an AMD 2000XP+ with 80G HDD and
> HP930C Printer, Canon N670U scanner, 4 port USB 1.1 Hub, and 6 port USB 2.0
> Hub (internal) and of course, Logitech Wingman Rumblepad USB joystick. All
> working under Linux :-)
> 
> Will send conf file shortly, hopefully will solve your problems.

Thanks for that. After checking for only one sane.d directory (which involved removing the old Red Hat 8.0 installed version in /etc/sane.d) I tried your config file. Sadly, I get the same results.

With a little more investigation, I find that a preview scan does eventually complete, after about an hour. There's 20 minute gaps between periods of head movement.

My feeling is that I may have a problem elsewhere. The scanner seems to work on a different machine under Windows, which rules out the scanner, so it may be either the USB hardware implementation is a little faulty, or the USB hardware driver is faulty.

Of course, I have no real evidence for this, but that's my hunch, given that you have the scanner working well.

I'll return it to the shop, and hope to get a refund.

Thanks anyway.

- Martyn Capewell


[<<] [<] Page 1 of 1 [>] [>>]


Powered by ezmlm-browse 0.20.