Don't be discouraged. Writing a scanner driver is very difficult work, especially if you lack documentation. Writing the epjitsu backend was so frustrating, I doubt I will work on such a stupid scanner again. Perhaps A. Imass will have some interest is continuing your work :)
allan 2010/6/8 St?phane Blondon <stephane.blondon at gmail.com>: > As discussed before on this mailing list, I tried to write an open > driver in order to replace epkowa but I fail and I will live far from > the scanner in few weeks so I can't continue. > > > To sum up what is known today: > - the protocol is more or less like the epjitsu. > - however the command headers are not the same as the epjitsu ones. > - command used to call to set up the resolution is "1e 8d". > Value for 50dpi: "03" > Value for 600dpi: "02" > Value for 12800dpi: "00" > - the preview scans at 50dpi > > - the firmware is included in the Esf66.bin file (in the MS Windows driver). > - the 255 first bytes of Esf66.bin are not sended. > - the end of the Esf66.bin is not sended too (they are only "ff" values). > > > It's probably not useful but my logs and files are there: > http://sblondon.free.fr/scanner_v100/ > > I will unsubscribe to the mailing list in days/weeks. > > -- > St?phane > > -- > 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"
