Refer to the article below to understand the OSDP protocol:
Note: Suprema devices use 2.1.6 v of the OSDP protocol
All official firmware for BioStar 2 devices use OSDP protocol for RS485 by default.
* 2.x firmware for entry level devices, 1.x firmware for 2nd generation devices
Refer to the following article if you don't know what entry device or 2nd generation devices are: 1st Generation Device / 2nd Generation Device / Entry Level Device
Suprema device as a slave device
You can use a Suprema device as a slave device with a third party controller using OSDP with the official firmware, but in that case the devices operate only as a dummy reader. This means that the device does not store the user data. If you would like matching to be done on the device with the user information stored on the device you would have to customize the firmware.
Suprema device as a slave device using Access on Cards
Note that you will have to issue access on cards through the BioStar 2 software. If you're not familiar with Access on Cards refer to the FAQ article
1. If the slave device is connected to a master Suprema device, the AoC matching is done on the master device.
2. If the slave device is not connected to a master Suprema device the AoC matching is done on the slave device and the card ID (secure ID) is sent to the master device.
3. If the slave device is in factory default status,and no primary or secondary keys are used for AoC, then the slave device will match AoC without any smart card layout configured.
This is based on BioStar 2.6 Firmware specification. Previous firmware may not behave this way.
Suprema device as a master device
Suprema device cannot be a master device when used with a third party device without customization when using OSDP.
This is because there is no way to know the ID of the attached device because there isn't an established device search command with OSDP
Hence the search method is a manufacturer's command which means that it differs by each manufacturer.
Therefore a customization is always necessary in such cases.
Case A (ACU holds the user information)
In this case, the ACU should enroll the user fingerprint and store the user information in the ACU’s memory.
The ACU should also have a feature to transfer template to RS485 Slave device.
Relevant operation mode:
Device matching (Card+Finger)
Case B (Suprema device holds the user information)
In this case the system administrator handles two different software for Suprema’s reader and the ACU.
The user data will be sent to the slave device and the slave device should do the input (fingerprint) matching and send the matching result to the master device through RS485.
This is not supported by regular firmware and requires a customization of the firmware.
Case C (Access on Card Matching)
* Access on Card is the Template on Card concept in BioStar 2.
The following device types are available to transfer card ID of the Access on card though RS485.
You will have to use BioStar 2 to issue the Access on Cards and configure the device to have the smart card template format.
Relevant device type:
A2, BS2, P2
Relevant operation mode:
Template On Card (Card+Finger)
1. Device search issue.
- Check if Device ID 0 can be searched.
If a master ACU searches a Suprema device via OSDP, the Suprema device's OSDP ID will be 0.
- Check that the Baud rate of the ACU and Suprema device matches:
Suprema device's baud rate default is 115200.
If you're still having issues, please let us know what OSDP command the controller users to search the device.
2. I receive "NAK reply, unsupported command" when using OSDP_Biomatch command
If the template is over 400 bytes, this response will appear. Try changing the template size to 384 bytes.