Hi, I've made some progress ...
I changed : /* CANOLIDE35 */ {1200, /*TODO: find a good reason for keeping all three following variables*/ 87, /*(black) */ 87, /* (dummy) */ 0, /* (startxoffset) */ 10400, /*sensor_pixels */ 210, 200, By : /* CANOLIDE35 */ {600, /*TODO: find a good reason for keeping all three following variables*/ 87, /*(black) */ 87, /* (dummy) */ 0, /* (startxoffset) */ 10400, /*sensor_pixels */ 210, 200, And used the gpo values : /* CANONLIDE35 */ { {0x38, 0x80} , {0x7f, 0xe0} It's no so bad ... (but image is always inverted ...) To have the white led, in color mode of scanimage, it's ok. scanimage -d --mode Color > image.pnm PS : I need to be root ... do you know what to do to avoid it ? Concerning scan borders, we must change scan area (not best, but better) : SANE_FIX (9.), /* Start of scan area in mm (x) */ SANE_FIX (7.7), /* Start of scan area in mm (y) */ SANE_FIX (218.0), /* Size of scan area in mm (x) */ SANE_FIX (297.0), /* Size of scan area in mm (y) */ Guillaume Gastebois a ?crit : > Hello, > > I modified registers 10-1d with : > > {0x04, 0xd3, 0x04, 0xd3, 0x02, 0xa3, 0x20, 0x06, 0x00, 0xff, 0x24, 0x00, > 0x00, 0x04}, > Where do I set this ? (which parameter of which struct ?) Thanks again for your help. PS : Reading your comments, I guess you're french ;) Bonne soir?e ;) > and now the led is really white (red green and blue by moving eyes). > > Led calibration seems to be good. > > But calibration is always 60s long..... > I need help. > Thanks > > Regards > Guillaume > > Pierre Willenbrock a ?crit : > >> Hi Guillaume, >> >> Guillaume Gastebois schrieb: >> >>> Hello, >>> >>> Why calibration is so long (~50/60s) ? >>> >> It is probably failing. Should take about 3-5 seconds. Look at the logs, >> the calculated averages and calibration are dumped there. >> >> >>> What are /* Start of white strip in mm (y) */ and /* Start of black mark >>> in mm (x) */ in genesys_devices.c ? >>> >> Those are configuration values for calibration steps. I don't know if >> any of these are currently used or if the values are hardcoded. >> >> I think the start-of-black-mark is used to detect the beginning of the >> document area for some gl646 scanners. The start-of-white-strip was once >> used in shading calibration. Currently, the shading calibration is setup >> for a calibration area looking like this: >> >> home position >> +-------------------------------- >> ! black area >> +-------------------------------- >> ! white area >> +-------------------------------- >> >> The border between black area and white area is autodetected per pixel, >> as the border is usually not straight. >> >> You scanner seems to offer only a white area, so we will need to do >> shading calibration differently. My current idea is this: >> * always gather data on a white area >> * for black data, reduce the led exposure time to the minimum(0x101, >> those registers cannot be set to 0. per byte.). >> * for white data, use the normal exposure times >> I tried something like this for offset calibration, to see if there is >> any difference between white area+0x101 exposure time and black >> area+normal exposure time. There was no difference in the final images, >> and i think the resulting calibration was the same as well. >> >> >>> Regarding the log file you said : >>> W ! 0x23 ! 0x050 ! dac value rgb(offset value) >>> W ! 0x2b ! 0x028 ! pga gain rgb >>> But on debug, I see that these two registers are never written. >>> >> 0x23 and 0x2b are merely convenience registers. Writing to 0x23 and 0x2b >> is equivalent to a write to each of 0x20-0x22 and 0x28-0x2a. For >> cis-sensors, there is only one channel used, so we could get away with >> only two registers writes(for the correct channel or 0x23/0x2b), but >> this won't work for ccd-sensors. >> >> >>> Another thing : when scaning in color the leds are blue ???? >>> >> I'd expect a shade of white, perhaps blueish. my scanner does a >> magentaish white. You may also see the single colors when quickly moving >> your eyes relatively to the scanner. >> >> Regards, >> Pierre >> >> >> > >