Hi,
the enroll process seems to work. However, when verifying it detects my finger
in about 1 out of 10 tries. Is this a bug or is it normal?
Regards
Timo
> Igor Filatov hat am 27. Januar 2018 um 18:52
> geschrieben:
>
> Yes, this time it worked. First of all, you should be able to op
Yes, this time it worked. First of all, you should be able to open
finger.pgm in the same directory with an image viewer and see your finger.
Then you can try exmaples/enroll and examples/verify to enroll and verify
your fingerprint. If everything seems ok, install the driver with `sudo
make instal
Hi,
it seems as if it worked when I swiped my finger over the reader in a natural
length (before I just tapped it). This is the output:
fp:debug [fp_init]
fp:debug [register_driver] registered driver upekts
fp:debug [register_driver] registered driver aes3500
fp:debug [register_driver] registe
Hi Timo, thanks for the logs!
Note to self: next time check spam folder when waiting for someone's logs.
Yes, it works, but your log shows that only 2 frames were captured. The
driver wants no less than 7 which is why capture has failed. Try a longer
swipe.
On a side note, The number is semi-arb
Hi,
Just for the case that the output of elanfp.c is still relevant:
Device with vid 4f3 pid c1a found.
Config number is 1
CMD RESET sent
CMD Fuse Load sent
CMD VERSION sent
FP Bridge FW Version 1.66
CMD Get Image Size sent
Width x Height = 64x144
CMD Get Calibrat
Hello Timo,
Le samedi 27 janvier 2018 à 13:40 +0100, Meta Colon a écrit :
> fp:debug [find_supporting_driver] driver elan supports USB device
> > 04f3:0c1a
> > elan:debug [activate_run_state] FW ver 1.66
> > elan:debug [activate_run_state] sensor dimensions, WxH: 144x64
Ok, I record your informat
Hi,
/examples/img_capture/ had the following output (I had to put my finger
on it at some point of time):
fp:debug [fp_init]
fp:debug [register_driver] registered driver upekts
fp:debug [register_driver] registered driver aes3500
fp:debug [register_driver] registered driver aes400
