FingerVein Integration Module (VIM)
Installation and Programming Manual
Page
47 of 48
Appendix B. Troubleshooting
1. No warning is received when placing a finger on the biometric sensor
It the optical barrier has stopped working, an
event will have
been generated at some moment to indicate the error status. The most frequent causes
of this fault are:
- The finger is left on the biometric sensor for too long.
events are
generated until a Watchdog appears and equipment switches to error status. It
returns to normal when the finger has been removed.
- There is too much ambient light on the biometric sensor. This light stops the opti-
cal barrier from working correctly and probably also stops the FingerVein sen-
sor from making a correct identification. We advise you to protect the
FingerVein VIM against excessive light, especially sunlight.
2. FingerVein VIM electronics does not recognise the proximity card
Ensure the following:
- The reader is correctly connected to the VIM control electronics, via
Clock&Data. See
chapter 5.1.: “Connector signals”
- Check that the reader configuration parameters have the ports required enabled
(see
)
3. FingerVein VIM electronics does not generate events
To generate an event, FingerVein VIM must know several things:
- After a reset, and until no communication is received from the Host, event gener-
ation is based on the
CFG_EventCH
parameter (see
)
.
- Write a $00 to
CFG_EventCH
to enable event generation from start-up.
6. FingerVein VIM communicates very slowly
Check whether:
- Many configuration parameters are being written from the application. Each write
requires an EEPROM recording time, which slows down the response times. It
is not advisable to write frequently on the EEPROM.
