Griaule Biometrics

Home » Forums » GENERAL » Fingerprint Readers » Lumidigm Mercury M300 series / Win7 issues.
14 replies [Last post]
Djatwork
Offline
Joined: 2010-12-02
Rate this post:
0
No votes yet
Lumidigm Mercury M300 series / Win7 issues.

The Lumidigm mercury M300 series seems not to work under win7

We have tested it with the .net and the VB tool but both will not connect to the reader. The reader seems to be installed correctly and show up in the devicemanager.

Also tested it on a windows XP machine and that does not seem to give a problem both the .net and the VB tool work.  Are there any issues known with win7 that you are aware of?

JB
Offline
Joined: 2010-09-15
Rate this post:
0
No votes yet

Dear customer,

Download the new version of the Fingerprint SDK 2009, there we have upgrade the DLL (CapPluginLumidigm.dll version:1.5.0.0) for that reader.

Tell us your results.

 

 

Jan Beeck

Griaule Support Team

 

Djatwork
Offline
Joined: 2010-12-02
Rate this post:
0
No votes yet

Hi Jan,

I checked the version of the DLL file and it is version 1.5.0.0 .

Do you have any other test tool we might be able to use to test the reader ?

so to be certain it is not a flaw with the drivers.?

 

Werner van Uden

JB
Offline
Joined: 2010-09-15
Rate this post:
0
No votes yet

Dear customer,

Install the driver from the manufacturer (http://www.lumidigm.com/technical-support/), then make sure that the O.S is recognizing the reader (maybe you will have to force the installing of that specific reader, because the manufacturer provide a container with many drivers).

 

Jan Beeck

Griaule Support Team

 

 

Djatwork
Offline
Joined: 2010-12-02
Rate this post:
0
No votes yet

Jan,

I tested the reader under win7 XP 64Bit and it seems to work there so im going to try to find out what is wrong with the 32bit machine.
It is a newly installed machine but it might be flawed. Also trying to install a new pc also with win7 32Bit and see how that goes.

Thanks for the info so far i will let you know what the outcome is for future references.

Werner

Djatwork
Offline
Joined: 2010-12-02
Rate this post:
0
No votes yet

Jan,

It seems to be the machine itself that gave the problem. I think it is due to the fact i first installed the suprema reader to test a few things and started with the Lumidigm after this.
On a new machine it works fine.

Thankx for the quick response

JB
Offline
Joined: 2010-09-15
Rate this post:
0
No votes yet

Dear customer,

Thank you for your feedback, we are glad that you have resolved your issue.

 

Jan Beeck

Griaule Support Team

Becky.L
Offline
Joined: 2010-02-24
Rate this post:
0
No votes yet

I have the Desktop identity product,  I am trying to use Lumidigm reader   venus or mercury.  but no luck. Any idea?   

davi.st1
Offline
Joined: 2010-08-26
Rate this post:
0
No votes yet

Dear customer,

 

Desktop Identity does not support those readers.

http://www.griaulebiometrics.com/page/pt-br/desktop_identity/supported_readers

 

If you have another doubts, don't hesitate to contact us.

 

--

Davi Stuart Zilli

Griaule Support Team

yanky
Offline
Joined: 2006-10-26
Rate this post:
0
No votes yet

I have a lumidigm mercury reader and purchased the SDK based on the fact that it is supposed to be able to identify within 1.5-2 seconds, from my testing, it is taking a lot longer than that to identify or even verify a template. when I do the same test with an older hamster, the speed is much better. so speed is issue number 1, is there is there anything that you guys may be doing with the lumidigm products that may be causing it to go so slow? when I do the same test with the lumigigm demo program it identifies very quickly. 2nd issue I am having, when I scan my finger and it is somewhat dirty, with the lumidigm demo program, I seem to get a clear scan, however with the graiule product, it sometimes does not seem to get a good scan. I am using these products because they are supposed to be superior to other readers and have a higher read rate, and with my testing, I found this to be the case, however when using it with your sdk, I am finding that it is not so. Please let me know if you have any ideas to why this may be happening. I also know that they are coming out with a newer version of their readers that do the image processing on the pc side, do you already support this new version? it should cut the scan time down to 400ms or so.

One more thing I noticed, when trying with your demo, it takes a few seconds for the application to recognize that the finger was removed (with the hamster it recognized immediately), is this something with the demo program or with the mercury unit, it would be unacceptable to have to wait 4 seconds between 2 people in a high traffic area.

Please let me know ASAP, because the deadline for this project is quickly approaching, and I need to make a decision if to work with these products.

Thanks in advance and take care,

Yanky

JB
Offline
Joined: 2010-09-15
Rate this post:
0
No votes yet

Dear customer,

Are you testing with the DLL CapPluginLumidigm.dll version:1.5.0.0?

 

Jan Beeck

Griaule Support Team

yanky
Offline
Joined: 2006-10-26
Rate this post:
0
No votes yet

I am testing with your latest demo application which I based on the file version of CapPluginLumidigm.dll - would be 1.5.0.0

JB
Offline
Joined: 2010-09-15
Rate this post:
0
No votes yet

Dear customer,

Just to make clear your issue, you are having a slow rate of recognition from the reader or from our library? is the latter is your issue make sure that you are calling the right functions with the right templates (i.e. function verify has the reference template and the target one). Once the reader scan correctly the image there shouldn't be any slowness from our layer (library).

 

 

Jan Beeck

Griaule Support Team

 

yanky
Offline
Joined: 2006-10-26
Rate this post:
0
No votes yet

I did not even try the API in itself, I actually started with Graiule's demo program, so I'm assuming that they would have done the optimum programming in the demo. If you ask me, based on my simple analysis, the scanner takes about 500ms till it scanns my finger, then about 4 seconds until the image shows up on the screen, exactly how much of that time is attributed to the transfer of the image over usb is really neligable even if I only get a slow rate of 14MB/sec and the size of the transfer is 288k, it should take about 200ms, I may say that perhaps there is some processing time being spent between the scan and sending the data, but this still doesn't explain why it takes over 2 seconds to recognize that the finger was removed. I would say that the reader is at fault, but when I test the reader with the demo that came with it, I get much better response times.

JB
Offline
Joined: 2010-09-15
Rate this post:
0
No votes yet

Dear customer,

An email has been sent to you.

 

Jan Beeck

Griaule Support Team