If you already have the STid Architect Blue Reader and this was not already configured for use with Proxyclick QR codes, please follow the setup steps below.
The info below details our configuration of the STid Architect Blue Reader so it may function with Proxyclick-generated QR codes.
Testing was completed using an STid USB / RS485 converter cable (Part Number: CNV_USB_485) and SECard Software.
The reader used in our testing was an ARCS-R31-AQ/BT1-3La/1 (QR/Wiegand output/read only).
It’s possible that your setup may have additional requirements and the configuration will differ, this guide should therefore be taken only as an example and focuses only on QR code reading setup.
<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" /> If you are using the SECard Software to create a DESFire configuration card, you may skip any steps involving the USB / RS485 converter cable.
</aside>
<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" /> If you require any assistance with the reader setup process or functions not mentioned below, you should contact STid support directly - [email protected]
</aside>
<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" /> Following the steps above will mean the reader is set to:
A - Read Proxyclick QR codes B - Output the 8-digit decimal token number as 32 bits of Wiegand data.
A simple rule in the ACS to read all 32 bits should give you the exact token number encoded to the QR.
</aside>
<aside> <img src="/icons/warning_yellow.svg" alt="/icons/warning_yellow.svg" width="40px" /> Other functionality is available using this reader and you may configure it to function with various physical or Bluetooth credentials. You will need to ensure these features do not conflict with the requirements for reading Proxyclick QR codes if so.
</aside>