Skip to content

What it can do — BioStation 3 Access Control System

Feature by feature, as assessed on 2026-09-01. Read the limitation column before you promise a customer something the hardware cannot do.

Connection, health and audit

Feature Supported Limitation
Connection & session Partially The link to the terminal is not encrypted, and the local helper service is trusted without its certificate being checked.
Liveness / keepalive Yes —
Time synchronization Yes —
Offline audit recovery Partially Everything that happened before the terminal was first linked to the system stays in its own log and is never read in.
Health & supervision Partially Tampering and loss of contact are reported, but a cut or shorted cable on a monitored input arrives without meaning, and nothing warns about the power supply.
Configuration & reset audit Partially A wipe of all people from the terminal is recorded, but resetting its settings, clearing its database or returning it to factory state leaves no trace in the log.
Configuration discovery Yes —

Access control

Feature Supported Limitation
Credential management Partially People can be sent to the terminal with cards, PIN codes and face data, but not with fingerprints, QR codes or phone credentials.
Card formats Partially Cards are matched on their full number only, so the site code and card number printed on a card cannot be entered separately.
Sync mode Yes —
Reset & restore Yes —
Double-sync safety Partially Sending the same people a second time should leave the terminal exactly as it was, but that has not been confirmed on real hardware.
Schedules / time profiles Yes —
Access levels / groups Yes —
Holidays Partially Public holidays are sent to the terminal, but the daily time plans still treat those days as ordinary weekdays.
Antipassback Yes —
Door control Partially A door can be released for a moment or switched between locked and unlocked, but it cannot be held open permanently and there is no one-touch emergency lockdown.
Reader mode / enable Partially It is visible when someone blocks the terminal at the keypad, but it cannot be blocked or released from the system, and the way it asks for a card, a PIN or a face stays as configured on the hardware.
Access events Partially Card and door activity is reported in detail, but an antipassback alarm arrives without meaning and leaving by the exit button cannot be told apart from a door simply opening.
Enrollment Partially A card or a face can be registered by presenting it at the terminal, but a fingerprint has to be enrolled on the hardware itself and a PIN typed in by hand.

Manufacturer gateway

Feature Supported Limitation
External lifecycle Yes —
Shared transport Yes —
Platform limits / SDK errors Partially When the terminal itself refuses an instruction, the reason it gave is thrown away and the operation still looks as if it went through.