[sane-devel] problems with plustek 9630P on fedora 8
On Thursday 24 January 2008 16:24:29 Thierry Leconte wrote: I try to use a plustek 9630P on a fedora 8 but : 1) it is detected as 600/600P 2) scaning an image just doesn't work PJ : the debug output of scanimage -d plustek_pp:/dev/partport0 What could I try ? Hard to say. For some reasons, the memory detection does not work correctly. You might try and play with the options, slowIO could be one. You might also try and play with BIOS parport settings. Set it to EPP only or SPP, never ever ECP!!! HTH Gerhard
[sane-devel] Canon LiDE 90
OK, but via which register is it programmed. I find nothing in GL842 datasheet for frontend. regards Guillaume Selon Pierre Willenbrock pierre at pirsoft.dnsalias.org: Guillaume Gastebois schrieb: Hello, OK, I open my LiDE 90 (very hard not all to destroy...). I find these IC's : GL842 (Genesys well known scanner chip) GLT44016P (SO40 RAM) BU6574 (TSSOP20 ) VHC175 (TSSOP16 quad flip flop) VHC08 (TSSOP16 quad and) LB1940 (TSSOP20 constant current driver) LM324 (SO14 quad op amp) 1733 (TO-263 regularor) Appart the BU6574 (I dont find what it is) I dont find any analog frontend. Is it possible that this chip is located with leds (seems very hard to open.) I don't know where the analog frontend may be found. There are arguments for both positions. The BU6574 has enough pins for the job. Did you look at the back of the pcb? In the documentation i found for one cis sensor, the glassy sensor itself contains just the ccd row and the leds. There may be a small pcb on the sensor bar, carrying the analog frontend. But you really don't need to look for the chip and possibly destroy your scanner on the way.. Let's first try to figure out how it is configured from an usb log. Regards, Pierre
[sane-devel] Canon LiDE 90
On Friday 01 February 2008 09:18:20 Guillaume Gastebois wrote: OK, but via which register is it programmed. I find nothing in GL842 datasheet for frontend. check for register 0x04 Layout: Bit 7 |Bit 6 |Bit 5 Bit 4 |Bit 3 Bit 2 |Bit 1 Bit 0 LINEART |BITSET |AFEMOD[1:0] |FILTER[1:0] |FESET[1:0] HTH Gerhard
[sane-devel] Rename norwegian bokmål translation
Hello, On Jan 31 16:13 Kjartan Maraas wrote (shortened): The norwegian bokm?l locale was renamed from no_NO to nb_NO some time ago and I'd like to see this change reflected in the sane-backends translation as well. Please rename no.po to nb.po and change any corresponding entries in configure.in (ALL_LINGUAS) or po/LINGUAS etc. We do in in our RPM since October 2004 with this patch: - --- po/Makefile.in.orig 2005-07-15 22:50:41.0 +0200 +++ po/Makefile.in 2005-08-08 15:25:50.0 +0200 @@ -2,7 +2,7 @@ # # See po/README for documentation. -ALL_LINGUAS = bg cs da de es fi fr it nl no pl pt ru sv +ALL_LINGUAS = bg cs da de es fi fr it nl nb pl pt ru sv SRC_FILES = ../include/sane/saneopts.h ../backend/artec_eplus48u.c \ ../backend/avision.h \ - And in the sane-backends.spec file with: - %prep ... # locale rename: no - nb: %patch1 -b .nb mv po/sane-backends.no.po po/sane-backends.nb.po - I would appreciate it if it is also done upstream. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex
[sane-devel] Rename norwegian bokmål translation
On Friday 01 February 2008 10:37:58 Johannes Meixner wrote: Hello, On Jan 31 16:13 Kjartan Maraas wrote (shortened): The norwegian bokm?l locale was renamed from no_NO to nb_NO some time ago and I'd like to see this change reflected in the sane-backends translation as well. Please rename no.po to nb.po and change any corresponding entries in configure.in (ALL_LINGUAS) or po/LINGUAS etc. We do in in our RPM since October 2004 with this patch: [SNIPSNAP] I would appreciate it if it is also done upstream. Guess this should be done before releasing 1.0.19! Any objections? Gerhard
[sane-devel] Canon LiDE 90
Guillaume Gastebois schrieb: OK, but via which register is it programmed. I find nothing in GL842 datasheet for frontend. regards Guillaume the analog frontend is programmed through the serial interface accessed by address registers 0x50(FERDA)/0x51(FEWRA) and data registers 0x46/0x47(FERDDATA)/0x3a/0x3b(FEWRDATA). I find this sequence in your log: R/W ! addr ! data ! WM8199 register +--+---+- W ! 0x04 ! 0x000 ! reset R ! 0x07 ! 0x041 ! revision number, ==0x41 W ! 0x04 ! 0x000 ! reset W ! 0x01 ! 0x02f ! Setup reg 1: mode4==0, pgafs=2, selpd=1, mono=1, cds=1, en=1 W ! 0x02 ! 0x007 ! Setup reg 2: del=0, rlcdacrng=0, 0=0, vrlcext=0, invop=1, muxop=3 W ! 0x03 ! 0x026 ! Setup reg 3: chan=0, cdsref=2, rlcv=6 W ! 0x06 ! 0x00d ! Setup reg 4: fm=0, intm=0, rlcint=1, fme=1, acycnrlc=0, linebyline=1 W ! 0x08 ! 0x000 ! Setup reg 5: 0=0, posnneg=0, vdel=0, vsmpdet=0 W ! 0x20 ! 0x050 ! dac value red(offset value) W ! 0x21 ! 0x050 ! dac value green(offset value) W ! 0x22 ! 0x050 ! dac value blue(offset value) W ! 0x23 ! 0x050 ! dac value rgb(offset value) W ! 0x28 ! 0x028 ! pga gain red(0x28 is a factor of 0.85) W ! 0x29 ! 0x028 ! pga gain green W ! 0x2a ! 0x028 ! pga gain blue W ! 0x2b ! 0x028 ! pga gain rgb all WM81xx(at least where datasheets are available) share a similar register layout, with revision 0x41 at address 7. writing to the rgb variant of pga gain/dac value results in writes to all the color specific registers, so it is not needed. So, you have in Genesys_Frontend: reg[1]=0x2f, reg[2]=0x07, reg[3]=0x26, reg2[0]=0x0d, reg2[1]=0x00, the rest of reg/reg2 =0, all sign[x]=0, offset[x]=0x50, gain[x]=0x28. this does not match anything currently in genesys_devices.c. Just add one entry to the Wolfson array, #define a DAC_ to 7 in genesys_low.h and put that in your Genesys_Model. The gain/offset setting should be good for led calibration and will be replaced by gain/offset calibration. After that, get a scan of the calibration area(the area under the housing at the parking position). For this, put 0 into the x_offset and y_offset in your Genesys_Model. If this turns out to be similar to the calibration area of the lide 50, led/offset/gain-calibration should work with only minor changes. Regards, Pierre
[sane-devel] Rename norwegian bokmål translation
go ahead. I think i am going to end up delaying the release for personal reasons, so this wont hurt anything... allan On 2/1/08, Gerhard Jaeger gerhard at gjaeger.de wrote: On Friday 01 February 2008 10:37:58 Johannes Meixner wrote: Hello, On Jan 31 16:13 Kjartan Maraas wrote (shortened): The norwegian bokm?l locale was renamed from no_NO to nb_NO some time ago and I'd like to see this change reflected in the sane-backends translation as well. Please rename no.po to nb.po and change any corresponding entries in configure.in (ALL_LINGUAS) or po/LINGUAS etc. We do in in our RPM since October 2004 with this patch: [SNIPSNAP] I would appreciate it if it is also done upstream. Guess this should be done before releasing 1.0.19! Any objections? Gerhard -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin
[sane-devel] Uninterrupted HP LaserJet M1005 Backend
Hello I try fix-cancel.patch - now backend work more correctly. Regards, tropos -- View this message in context: http://www.nabble.com/Error-in-HP-LaserJet-M1005-Backend-tp15127315p15230285.html Sent from the SANE - Dev mailing list archive at Nabble.com.
[sane-devel] Plustek 7200 log (another GL842 device)
Seeing that people now 'have their eye in' for the GL842, I've taken a quick log using Benoit's sniffer on a win2k system from my Plustek 7200. According to the sane-devl page this uses a GL842 ASIC and a AD9826 CCD. The zipped log is on my demon homepages http://www.n-cantrell.demon.co.uk/7200logs/usbsnoop.log.gz Hope someone can see something useful in it Bob 'Those who like this sort of thing, will find this the sort of thing they like' (Abe Lincoln's rumoured review of a mediocre book) -- robert w hall
[sane-devel] Iriscan 2 (vendor=0x07b3 product=0x045f)
To whoever would like this information:
I have added basic support for an Iriscan 2. By me saying I added support I
mean that I copied and pasted all the information from the Plustek OpticSlim
M12 section. It workd well with everything that I tried which includes scan
preview and scan 600dpi. I was not exactly sure how to name it because the
package was listed as an Iriscan Express 2. The website calls it
an Iriscan 2, and the bottom of the scanner says:
Product Name: Iriscan
Model: HCRSPA4PK301
Package Express2
Sorry if this is not the format for posting this information. The chipset is
a GT-6816-HQ011 MVL 1385.1 0736. Below is the rest of the outputs that I
think you guys would need.
sane-find-scanner output:
found USB scanner (vendor=0x07b3, product=0x045f [600dpi USB Scanner],
chip=GT-6816) at libusb:002:004
scanimage -L (after Override)
device `gt68xx:libusb:002:004' is a Plustek OpticSlim M12 flatbed scanner
firmware:
cism216.fw
Just copied and pasted Plustek info in devices.c
scanimage -L (after Override, and recompile)
device `gt68xx:libusb:002:004' is a Iris scan express 2 flatbed scanner
cvs diff output:
? patch
Index: backend/gt68xx.conf.in
===
RCS file: /cvsroot/sane/sane-backends/backend/gt68xx.conf.in,v
retrieving revision 1.2
diff -r1.2 gt68xx.conf.in
241a242,243
# Iriscan Express2
usb 0x07b3 0x045f
Index: backend/gt68xx_devices.c
===
RCS file: /cvsroot/sane/sane-backends/backend/gt68xx_devices.c,v
retrieving revision 1.48
diff -r1.48 gt68xx_devices.c
401c401
/* Based on data from Jakub Dvo??k xdvorak at chello.cz. */
---
/* Based on data from Jakub Dvo??k xdvorak at chello.cz. */
1848a1849,1873
static GT68xx_Model iriscan_express_2_model = {
iriscan_express_2,/* Name */
Iris, /* Device vendor string */
scan express 2, /* Device model name */
cism216.fw, /* Name of the firmware file */
SANE_FALSE, /* Dynamic allocation flag */
mustek_gt6816_sheetfed_command_set,/* Command set used by this
scanner
*/
600,/* maximum optical sensor
resolution */
1200, /* maximum motor resolution */
600,/* base x-res used to calculate
geometry */
600,/* base y-res used to calculate
geometry */
1200, /* if ydpi is equal or higher, disable
backtracking */
SANE_FALSE, /* Use base_ydpi for all resolutions */
{600, 300, 200, 150, 100, 0}, /* possible x-resolutions */
{600, 300, 200, 150, 100, 0}, /* possible y-resolutions */
{16, 8, 0}, /* possible depths in gray mode */
{16, 8, 0}, /* possible depths in color mode */
SANE_FIX (1.0), /* Start of scan area in mm (x) */
SANE_FIX (9.5), /* Start of scan area in mm (y) */
SANE_FIX (218.0), /* Size of scan area in mm (x) */
SANE_FIX (299.0), /* Size of scan area in mm (y) */
1849a1875,1895
SANE_FIX (10.0),/* Start of white strip in mm (y) */
SANE_FIX (140.0), /* Start of black mark in mm (x) */
SANE_FIX (0.0), /* Start of scan area in TA mode in mm (x) */
SANE_FIX (0.0), /* Start of scan area in TA mode in mm (y) */
SANE_FIX (100.0), /* Size of scan area in TA mode in mm (x) */
SANE_FIX (100.0), /* Size of scan area in TA mode in mm (y) */
SANE_FIX (0.0), /* Start of white strip in TA mode in mm (y) */
0, 0, 0,/* RGB CCD Line-distance correction in
pixel */
0, /* CCD distcance for CCD with 6 lines)
*/
COLOR_ORDER_BGR,/* Order of the CCD/CIS colors */
{0x24, 0x0a, 0x23, 0x0f, 0x23, 0x0b}, /* Default offset/gain */
{0x157, 0x157, 0x157}, /* Default exposure parameters */
SANE_FIX (2.0), /* Default gamma value */
SANE_TRUE, /* Is this a CIS scanner? */
GT68XX_FLAG_NO_POWER_STATUS | GT68XX_FLAG_SHEET_FED
};
1886a1933
{0x07b3, 0x045f, iriscan_express_2_model},
If there is anything else needed just let me know.
-Conrad
