Please help, I have a question and I need an answer.
You can use our Knowledge Capture app to leverage your team’s collective expertise. With the app, agents can: Search the Help Center without leaving the ticket Insert links to relevant Help...
This article covers the configuration of U-Prox SL (v.30.xx) and SE series readers operating within a unified ACS under U-Prox IP software, alongside Hikvision biometric terminals integrated via the Hikvision ISAPI interface. These biometric terminals perform both face recognition and Mifare Classic/Mifare Ultralight card reading.
To ensure compatibility with the Hikvision terminals when reading Mifare Classic and Mifare Ultralight cards using U-Prox readers, perform the following in the U-Prox Config mobile app: set the reader’s card‐reading template to “U-Prox reverse all.”
In the U-Prox IP software, in the settings for readers that use Hikvision biometric terminals, the “Reader type” field should be set to “26 bits,” which corresponds to the Wiegand 26 format:
To register Mifare Classic cards with 4-byte codes in the U-Prox IP software, you must use a U-Prox reader connected to a U-Prox IP400 controller. In the U-Prox Config mobile app for that reader, set the output interface to Wiegand 42 and the Mifare card-reading template to U-Prox reverse all.
Registering cards with 7-byte codes is somewhat more complex. This applies to Mifare Classic cards with 7-byte UIDs and to Mifare Ultralight cards. The following options are possible:
Registration via a U-Prox reader connected to a U-Prox IP400 controller
00XXXXXXXX
, where XXXXXXXX
are the eight significant hex digits. That identifier will show up in U-Prox IP as a standard card.00XXXXXXXXXXXXXX
, where the 14 trailing hex digits XXXXXXXXXXXXXX
are the significant bits. That identifier will show up in U-Prox IP as a mobile identifier read from the smartphone.Additionally: