FingerVein Online
Installation and Programming Manual
Page
67 of 69
3. FingerVein Online electronics does not recognise the proximity card
Ensure the following:
- The reader is correctly connected to the FingerVein Online electronics, either via
the Clock&Data or the RS-232. See
chapter 5.1.: “Connector signals”
- In the case of the UART2-UI, check that their configuration parameters are cor-
). In particular, ensure that the UART and reader
transmission speeds coincide.
- In any event (RS-232 or Clock&Data), check that the reader configuration param-
eters have the ports required enabled (see
)
4. FingerVein Online electronics does not generate events
To generate an event, FingerVein Online electronics must know several things:
- Via which protocol to generate the event (Bio-OCX UART0, Bio-OCX IP, KSP-
IP): it is always generated depending on the last communication received from
the Host. After a reset, and until no communication is received from the Host,
this decision is based on the
CFG_EventCH
parameter (see
.
- In the case of IP communications, the Host IP address to which the frame is to be
sent must be determined. This is the
IP-RemoteHost
parameter indicated in
- In the case of Bio-OCX UDP, the Host IP port must also be known. This will be
port 5501 by default.
- Nevertheless, if several FingerVein Online electronics are being routed, these
should be connected to different IP ports in the Host. If they are assigned auto-
matically by the Host, simply specify a value of
0000
in the
Port-RemoteHost
parameter (
). In this case, FingerVein Online electronics cannot
determine the destination port until it receives a frame from the Host and, there-
fore, no events will be received. This could be a limitation when faced with an
unexpected power cut, as when the power supply is restored, FingerVein Online
electronics will stop generating events until it receives an instruction from the
Host. This limitation can be solved by using the KSP-UDP protocol, as the
event is then transmitted via the Host's 6001 port from any KSP node.
- In the case of Bio-OCX TCP, events cannot be generated until the Host has
opened the TCP/IP Socket. It is not possible to configure the
CFG_EventCH
parameter (see
) so that events are spontaneously generated
via TCP/IP after a reset.
6. FingerVein Online electronics communicates very slowly
There are three possible causes:
- The display is not connected or does not respond correctly. In this case,
FingerVein Online electronics is waiting until the end of Display Time-out