Skip to main content

 

Eptura Knowledge Center

Nedap Setup Guide

  1. Last updated
  2. Save as PDF

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.

clipboard_e349a7ac9a2f3d137c0adf676271bb4f9.png

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.

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).

clipboard_e99a61338e2536c92114e08e0e4784fb6.png

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.

The above is an example only. You will need to set a suitable Wiegand rule or card format in the ACS.

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.

Additional Notes

Convert BCD to binary

  • Enable this option to convert the BCD (decimal) number to a binary value if Hex string was selected in the QR Scanning settings.

clipboard_ea470acfac03b3183b6cc90a00cf256bc.png

You will see above that we needed to set 43bits for the ID number in order to attain a 37 bit Wiegand output from the reader - due to the BCD setting.

The basic requirements are for the reader to read either the first or last 8 digits of the Proxyclick QR string, as this is where we place our 8-digit token number, and transmit that data in a way that will be understood by the ACS.

This may be a simple Wiegand rule transmitting only the token number or you can make this more complex, adding parity bits if required by your particular setup.