BioSmart PV-WM-MFR, Operation Manual, Page: 19 / 24

Operation Manual BioSmart PV-WM v.029.1|03.2021|en
Page 19 of 24
BioSmart PV-WM Reader
Operation Manual
№ Fault description Possible reason Elimination method
Access group is not assigned
to BioSmart UniPass
controller
Check access group assignment (see
Biosmart-Studio User Guide)
The palm vein patterns were
incorrectly registered (the
correct palm position wasn ’ t
observed when scanning)
Re-add the palm veins following the
recommendations for the palm veins
scanning (see the Biosmart-Studio
User Guide)
4 The user can’ t be
identified by the card
There is no card code in the
Biosmart-Studio software
database
Check the user cards presence in
memory (see the Biosmart-Studio
User Guide and User Manual
BioSmart UniPass Controller)
Card format doesn ’ t match
the reader type
Make sure that the RFID-card type
used is compatible with the built-in
RFID-reader type
Access group is not assigned
to BioSmart UniPass
controller
Check access group assignment (see
the Biosmart-Studio User Guide)
In the case when the measures taken didn ’ t allow to eliminate the malfunction and in the event of
malfunctions that are not described in Table 7 , it’ s recommended to contact technical support.
PV-WM Reader Settings
After connecting the readers to the BioSmart UniPass controller and connecting the controller to the
local netwo rk, it’ s necessary to specify the readers serial numbers. These actions are performed in the
controller's WEB interface.
Access to the controller's WEB-interface is carried out using a computer with a WEB-browser. To gain
access, it’ s necessary to supply power to the controller and connect it to a PC. Make sure that routing is
configured between the computer and the controller, TCP port 8082 is open.
To enter the web-interface, enter the controller's IP-address in the browser line in the form
IP_address:8082 . By default, the controller has an IP-address 172.25.110.71 , so if the IP-address hasn ’ t
changed, enter 172.25.110.71:8082 into the browser line. The screen will display the form shown in Figure 13.
Figure 13 – Access wondow to the controller web-interface