call for testers

[rayl]

hi all

so the latest git version will produce fingerprint scans on my
laptop. if people can test this out and report success/failure, that
would be very helpful.

$ git clone git://github.com/rayl/vfs101driver.git
$ cd vfs101driver
$ make
$ mkdir img img/A img/B img/C img/D img/X
$ ./bin/proto woot
while (want more prints)
wait for repeating " xx xx 00 00 16 00 00 00 FF FF 01" on
screen
swipe finger
hit ctrl-C to exit
$ gwenview img/X

it would also be useful to tee the output of bin/proto into a file and
send it to me.

thanks
ray

[Damir Syabitov]

Wow! Cool news! I broke my head trying to get FF FF 01 response from device.

[Francesco Zuliani]

Hi,

> so the latest git version will produce fingerprint scans on my
> laptop. if people can test this out and report success/failure, that
> would be very helpful.
>
> $ git clone git://github.com/rayl/vfs101driver.git
> $ cd vfs101driver
> $ make

add a
$ mkdir bin

> $ mkdir img img/A img/B img/C img/D img/X
> $ ./bin/proto woot
> while (want more prints)
> wait for repeating " xx xx 00 00 16 00 00 00 FF FF 01" on
> screen
> swipe finger
> hit ctrl-C to exit
> $ gwenview img/X
>

I'm getting lots of file when I swipe my finger ... in all directories.

Using the largest one in img/X I obtain a reasonable picture of my finger.

The picture however is vertically splitted in two ...
About 4/5 contain a good fingerprint, the rest also resembles a fingerprint,
but seems like a "piece" of the main one ...

Hope this is useful

Francesco

[Damir Syabitov]

Test app worker once, after terminating - it's stops work. Returns
something like:
> Peek (-1)
---> 00 00 00 00 12 00 E8 1F 00 00 04
<--- 00 00 00 00 12 00 00 00 00 00 B0 08

> Peek (-1)
---> 01 00 00 00 12 00 EC 1F 00 00 04
<--- 01 00 00 00 12 00 00 00 00 00 FE CB

At success time - the results with pictures was like Francesco
results.

[Damir Syabitov]

Ooops. My mistake - forget about "woot"

[Ray Lehtiniemi]

Francesco Zuliani wrote:
> add a
> $ mkdir bin
>

i think i'm going to just ad a target to the makefile to create the
appropriate directory structure, i'll make sure bin is in there.

> I'm getting lots of file when I swipe my finger ... in all directories.
>

yes, the image seems to come back in 4 vertical stripes, which i've
named A, B, C and D. X is just the raw image containing all four subimages.

> Using the largest one in img/X I obtain a reasonable picture of my finger.
>

excellent, good news!

> The picture however is vertically splitted in two ...
> About 4/5 contain a good fingerprint, the rest also resembles a fingerprint,
> but seems like a "piece" of the main one ...
>

yes, image A is the large fingerprint, the smaller fingerprint is images
B and C, finally image D is the junk along the right side of the
picture. The boundaries of each section are marked with white lines
along the top and bottom 10 pixels of the image.

> Hope this is useful
>
it is, thanks.

ray

> Francesco
>
> To unsubscribe from this group, send email to vfs101driver+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
>

[Ray Lehtiniemi]

rayl wrote:
> it would also be useful to tee the output of bin/proto into a file and
> send it to me.
>

just realized that the current output of ./bin/proto contains the raw
fingerprint image data, so please don;t send this to me! :-)

i will make the output anonymous by default and add an explicit command
line switch to include the raw data tonight. once that's in place, i'll
issue another call for sample output logs.

sorry
ray

[Ray Lehtiniemi]

Damir Syabitov wrote:
> Ooops. My mistake - forget about "woot"
>

i guess i'll make woot the default for now, since it's the only
interesting cycle routine at the moment.

so once you used woot, you got the expected fingerprint images under
img/X? there should be 5 small images for every large fingerprint
image, and the large image should be split into several distinct
sections (at the white marker lines in the top and bottom 10 pixels of
the image)

thanks
ray

[Damir Syabitov]

Bytes 209-272 of one line is something like a checksum of middle part
of the print.
They can be flipped from right to left and putted up over the image.

[Damir Syabitov]

[Damir Syabitov]

[Damir Syabitov]

[Damir Syabitov]

Interesting bug on page refresh...

[nicolas]

Hi,

I tested but I have a problem. No image are created in any "img/"
directory.
When I run "./bin/proto woot", " xx xx 00 00 16 00 00 00 FF FF 01"
appears on screen after maybe 3 seconds.
But when I swipe my finger, the program terminated with "Main cycle
complete success!" and there is no images in the img/X.

Nico

[Damir Syabitov]

> To unsubscribe from this group, send email to vfs101driver+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
>

bin/proto woot personal

[nicolas]

Hi,
Here the output after swiping my finger on my fingerprint device.
http://dl.dropbox.com/u/5780009/out.txt

The image produced seem to be splited in 2 part.
The progam crash maybe 2 second after I swipe my finger with :
"Failed to reset device
Failed to release interface"

Thanks
Nico

[Ray Lehtiniemi]

hi nico

nicolas wrote:
> Hi,
> Here the output after swiping my finger on my fingerprint device.
> http://dl.dropbox.com/u/5780009/out.txt
>

thanks, will have a look

> The image produced seem to be splited in 2 part.
>

yes, it's still unclear what purpose the second, smaller image serves.

> The progam crash maybe 2 second after I swipe my finger with :
> "Failed to reset device
> Failed to release interface"
>

something in the current code seems to be causing the device to lock up
after the scan finishes. i can make it loop and scan as many
fingerprints as i want, but as soon as the program exits, the device
locks up and i have to reset it.

ray

[Eric]

I did exactly that, and got the same symptoms as Nicolas above.

~/vfs101driver-read-only$ bin/proto woot personal
Libusb inititalized!
Searching for device...
Device found!
Checking active kernel driver...
Claiming interface...
claimed interface
Configuring device...
Device configured!
Entering main cycle...
UP : 0x01 0x00 0x00 0x00 0x12 0x00 0xE8 0x1F 0x00 0x00 0x04
DOWN: 0x01 0x00 0x00 0x00 0x12 0x00 0x00 0x00 0x00 0x00 0x7C 0x5F
UP : 0x02 0x00 0x00 0x00 0x12 0x00 0xEC 0x1F 0x00 0x00 0x04
DOWN: 0x02 0x00 0x00 0x00 0x12 0x00 0x00 0x00 0x25 0x19 0x27 0x44
UP : 0x03 0x00 0x00 0x00 0x12 0x00 0xF0 0x1F 0x00 0x00 0x04
DOWN: 0x03 0x00 0x00 0x00 0x12 0x00 0x00 0x00 0x6E 0x18 0xA7 0x52
UP : 0x04 0x00 0x00 0x00 0x12 0x00 0xF4 0x1F 0x00 0x00 0x04
DOWN: 0x04 0x00 0x00 0x00 0x12 0x00 0x00 0x00 0xEF 0x63 0x71 0xA6
UP : 0x05 0x00 0x00 0x00 0x12 0x00 0xF8 0x1F 0x00 0x00 0x04
DOWN: 0x05 0x00 0x00 0x00 0x12 0x00 0x00 0x00 0x00 0x00 0x00 0x00
UP : 0x06 0x00 0x00 0x00 0x12 0x00 0xFC 0x1F 0x00 0x00 0x04
DOWN: 0x06 0x00 0x00 0x00 0x12 0x00 0x00 0x00 0x1D 0x29 0xBB 0x55
UP : 0x07 0x00 0x00 0x00 0x04 0x00 0x2E 0x00
DOWN: 0x07 0x00 0x00 0x00 0x04 0x00 0x00 0x00 0x0A 0x00
UP : 0x08 0x00 0x00 0x00 0x02 0x00 0x00
DOWN: 0x08 0x00 0x00 0x00 0x02 0x00 0x00 0x00 0x56 0x46 0x53 0x20 0x76
0x65 0x72 0x20 0x33 0x2E 0x37 0x32 0x20 0x20 0x76 0x63 0x33 0x2D 0x73
0x79 0x73 0x2E 0x72 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x00 0x00 0x00
UP : 0x09 0x00 0x00 0x00 0x04 0x00 0x28 0x00
DOWN: 0x09 0x00 0x00 0x00 0x04 0x00 0x00 0x00 0x00 0x00
UP : 0x0A 0x00 0x00 0x00 0x04 0x00 0x14 0x00
DOWN: 0x0A 0x00 0x00 0x00 0x04 0x00 0x00 0x00 0x00 0x00
Main cycle complete success!
~/vfs101driver-read-only$

Furthermore, I opened src/proto.c and can't find any reference to argc
or argv anywhere, nor any instance of the words "personal" or "woot".
What's am I missing?

[Eric]

Alright, I realized my mistake. I was using the SVN code on the Google
Code page instead of the GIT code from github.

I executed the correct command and proto generated 5 images in img/X
(and nothing in A-D). Of the five, one resembles my fingerprint. The
other 4 are small, blocky images.

Can I send anything to be of help?

[Ray Lehtiniemi]

Eric wrote:
> Alright, I realized my mistake. I was using the SVN code on the Google
> Code page instead of the GIT code from github.
>
> I executed the correct command and proto generated 5 images in img/X
> (and nothing in A-D). Of the five, one resembles my fingerprint. The
> other 4 are small, blocky images.
>
> Can I send anything to be of help?
>

nope, just your success report is good for now. it's sounding like the
quick hack i put in place to initialize the hardware is working fine on
most people's devices.

thanks for testing
ray

[Eric]

I also get the errors

Failed to reset device
Failed to release interface

at the end of the fingerprinting sequence.