The below details our configuration of the Nedap NVITE reader.
It is possible that your setup may have additional requirements and the configuration will differ; this guide should therefore only be taken as an example.
The NVITE reader requires the “NVITE Configuration Tool” software seen below. You may obtain this software from Nedap directly.
Above we see the QR scanning settings. The top two items are always enabled in our testing. Further information is included in the reader documentation from Nedap.
<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" /> String format
Select "Decimal string" when using Proxyclick QR codes. This will convert the number from decimal to hex.
The default string format is "Hex-string". When configured for a Wiegand output this may require the “Convert BCD to Binary” setting in the next step to also be enabled (see Additional Notes below).
</aside>
The above shows the settings in place when the reader was set up with an example Wiegand format and the String Format set to “Decimal string”. A matching Wiegand setting would need to be set in the ACS.
<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" /> The above is an example only. You will need to set a suitable Wiegand rule or card format in the ACS.
</aside>
<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" /> We do not encode any parity bits alongside the token number in our QR codes, so there’s no need to include parity bits nor configure any parity calculation within the ACS unless this is required in the ACS due to the card formats used. Example: When using Brivo with a HID 37bit format, this format requires parity bits to also be sent and they need to be selected in the reader setup.
</aside>