Access Control
1

What is the connection between the mobile credential solution and an access control standalone terminal?

(1) Readers which support BLE, NFC or QR code function can been connected with standalone terminals via Wiegand or OSDP as a secondary device, thus the standalone terminal which does not support mobile credential can be enabled with mobile credential function. (2) In the future, we will also release Armatura’s standalone terminals which support BLE, NFC and QR code functions, and can be used with ACMS and apps. like Armatura ID and Connect and the tools. Clients may choose readers or terminals which support BLE, NFC or QR code functions according to their needs of project (Please refer to the coming up notice for the release of the standalone terminals).
2

Is it required to use any specific reader or controller for the mobile credential solution?

The mobile credential solution includes reader(s), two app. (Armatura ID and Armatura Connect (Mobile)), a desktop tool (Armatura Connect Desktop), and an ACMS system. The solution itself does not include any controller or additional operation software. The reader(s) as the means of mobile credential mainly uses Wiegand or OSDP (RS485) to communicate with other controllers, standalone terminals or other devices. Thus, it is required to bundle specific Armatura reader(s) (standalone terminals will also be released) for sale of the mobile credential solutions under Armatura.
3

Which brand(s) and their device(s) can be connected to EP10/EP20 series readers?

As non-biometric products, EP10 and EP20 series readers can be connected to various third-party devices via Wiegand or RS485 (OSDP). The devices include but are not limited to access controllers, access control standalone terminals and printers. As Wiegand and OSDP are both standard protocols, there are no limits for EP10 and EP20 series readers to connect with only certain hardware of certain brands, all output data are card-type by default.