Taken on a small group of Islands in the Oslo fjord, called Hvasser. A 15 meter peice of fabric playing in the wind, scanned right to left in 21 seconds. Got really lucky with the clouds this time, allowing a single beam of sunlight in as a highlight.
So, when I say “change the image”, I mean the torch does affect the calibration, in the sense that I get different patterns of stripes based on the position of the torch, but it’s still just outputting stripes.
Here are two scans I made by waving the torch around randomly during the calibration, then resting the torch on the glass.
For some reason each pixel is just outputing the same brightness for the whole duration of the scan, except for that black spot where the torch is, which is weird.
So, I re-installed the prism, luckily it just slots back in. I’m not sure if it helped at all, I still get the much the same result most of the time.
I did manage to get this result. It’s black at the top because the lid was closed. I opened the scanner half way thru, and the scan turned white. Then I waved the torch over the sensor and got a definite zigzag. And there’s a hint of grey in the middle, which is encouraging.
So, the sensor is still working, it’s responding to light, just not in a usable way.
@Leavingoldhabits Hi again, I’ve started playing with an Arduino and a light sensor. At the moment all it can do is read the LED light source from the flatbed scanner during the calibration sequence, and record the results.
The N650U has three stages of calibration:
The next step will be to introduce some kind of timestamp for each moment of the recording. Then the hard bit will be to shine a light source onto the sensor so simulate a proper calibration.
I haven’t recorded the calibration on the LiDe 110 yet, but I will. I didn’t realize it when I modified it, but the book says it will scan at 2400x4800dpi which works out to over 550mp for an A4 scan, which dwarfs the 20mp of my mirrorless, lol.