> You might try outputting ascii pgm files; use P2 instead of P5 as the > header line, then a line with the width and height output in %d printf(3) > format, then a line with the maximum value (15 for a 4-bit int) and then > a whitespace-separated list of the 4-bit values in %d format. > > Eg, something like: > > P2 > 6 4 > 15 > 0 0 0 0 0 7 > 0 13 0 4 0 0 > 0 0 12 0 3 0 > 8 0 0 11 1 0 Thanks, I'll try it.
>> If I give a link to a sample of the data, obtained from reader, can >> you help me deal with what to do with this data? > > I wouldn't mind trying it out. Enrolled data can be downloaded from here: http://gentoo.homelan.lg.ua/distrib/enroll.tar.bz2 With my very bad English, I'll try to explain all what I can discover... Description of enrolling process on the egistec reader. During the wait loop, when finger sweep detected (changed first byte of a returned buffer), the following occurs: -> send command (I call it "prepare to get data") <- received 6144+13 bytes of data (saved as pre-enroll.bin) -> send command for get image data -> received 61440+13 bytes of data (image 0, saved ad enroll0.bin) And so on seven times again. Last 13 bytes of data appended to all returned buffers independently of the purpose. These 13 bytes always identical in all cases, except errors. I think this some report about operation succeeded. There is two directories in archive - 'slower-sweep' and 'faster-sweep'. Each directory contains pre-enroll data (6144) and 8 saved buffers. Thanks for agreeing to help :) _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
