Hi

the problem with UPEK and image capabilities is not in the hardware itself, 
but rather in the way the original linux driver (used for creating the driver 
in libfprint) interfaces with the device.

the devices has co-processor, which can be used to compare the prints (and is 
in linux driver, probably in windoze too), but can return image data when 
asked correctly (windoze drivers does that, for instance).

therefore what you need is to use the imaging interface of the device, which 
is not found in any open-source driver AFAIK.

Pavel


On Saturday 27 of March 2010 20:25:13 Vadim E. Evard wrote:
> Please excuse my English.
> 
> I am now working in the FingerGraph project,
> http://code.google.com/p/fingergraph/
> 
> It is pseudo-cross-platform project since we use .Net/Mono.
> To work in Linux (it is my care in the project) we have chosen
> libfprint, because it works with our
> 0483:2016 SGS Thomson Microelectronics Fingerprint Reader
> and
> Futronic FS80.
> 
> I've experimented with SGS Thomson device. It can perform verify action;
> but we need raw, not processed image to implement graph identification
> method.
> 
> As for SGS Thomson, the example program writes this text:
> 
> libfprint-0.1.0-pre2/examples$ ./img_capture
> 
> Found device claimed by UPEK TouchStrip driver
> this device does not have imaging capabilities.
> 
> The main questions are: what do the words `does not have imaging
> capabilities' mean? Is it difficult to correct this situation? Does
> other our scanner have them? And where can we see the list of devices
> having these capabilities? (I have not found any information about this
> in Russian, and searching in English is very difficult for me).
> 
> Thanks in advance.
> Vadim
> 
> _______________________________________________
> fprint mailing list
> [email protected]
> http://lists.reactivated.net/mailman/listinfo/fprint
_______________________________________________
fprint mailing list
[email protected]
http://lists.reactivated.net/mailman/listinfo/fprint

Reply via email to