What it can do — TECH FASS APS mini Plus
Feature by feature, as assessed on 2026-06-04. Read the limitation column before you
promise a customer something the hardware cannot do.
Connection, health and audit
| Feature |
Supported |
Limitation |
| Connection & session |
Partially |
Traffic between the system and the controllers is not encrypted, so the network path to them has to be a trusted one. |
| Liveness / keepalive |
Partially |
A lost controller is noticed only when the next regular read of its event memory goes unanswered, so a very short dropout can pass unreported. |
| Time synchronization |
Partially |
The controller clock is set from the system, but the way it stores the day of the week has not been confirmed on real hardware, so day-dependent access hours should be checked on site. |
| Offline audit recovery |
Partially |
Card reads and door events stored while the system was away are collected once it comes back, but the controller keeps only a limited loop of them, so the oldest are overwritten during a long outage. |
| Health & supervision |
Partially |
Loss of communication, an opened enclosure and a flat or failing battery are named clearly, while rarer faults arrive as an unnamed message that has to be looked up in the manufacturer's manual. |
| Configuration & reset audit |
Partially |
Changes to the controller's settings and a remote reprogramming are recorded only as unnamed device messages, so they appear in the log without being clearly labelled as configuration changes. |
| Configuration discovery |
Partially |
A scan finds the controllers present on the bus, but it always adds one door, one output and three inputs to each of them, so whatever a given model does not have must be deleted by hand. |
Access control
| Feature |
Supported |
Limitation |
| Credential management |
Partially |
A person can hold a card and one PIN; giving them a second PIN, or one the hardware cannot store, can stop their card reaching the controller at all. |
| Card formats |
Partially |
Cards are matched by their full serial number, and a number typed in by hand is read as a hexadecimal value, which should be checked against a card the reader has actually seen. |
| Sync mode |
Yes |
— |
| Reset & restore |
Yes |
— |
| Double-sync safety |
Partially |
Sending the same people to the controller a second time is expected to change nothing, but that has not yet been confirmed on real hardware. |
| Schedules / time profiles |
Partially |
Access hours can be set as up to two windows a day for each day of the week, but a window cannot run past midnight and holidays cannot be given hours of their own. |
| Access levels / groups |
No — the hardware cannot do it |
The hardware has no notion of a named group of doors, so each person's rights are carried door by door rather than by assigning them to a group. |
| Holidays |
Partially |
Up to 64 public holidays are sent to the controller for one year at a time, so the list has to be refreshed before the next year begins. |
| Antipassback |
Partially |
The controller can refuse a card that is passed back and used twice and it reports the refusal, but the rule is set up on the hardware and a person stuck outside cannot be released from the system. |
| Door control |
Partially |
A door can be released for a moment, but it cannot be held open for a delivery or locked shut in an emergency from the system. |
| Reader mode / enable |
Partially |
A reader cannot be switched off or moved between card-only and card-plus-PIN from the system; that has to be set on the hardware itself. |
| Access events |
Partially |
Entries, refusals, door openings and input changes are all reported, but some rarer messages from the controller still arrive without a readable name. |
| Enrollment |
Partially |
A new card is registered by holding it up to a reader; fingerprints and other biometrics cannot be enrolled because the hardware does not read them. |
Safety
| Feature |
Supported |
Limitation |
| Panic / duress / emergency |
Partially |
A PIN entered under threat raises an alarm, but the system cannot start an evacuation or lock the building down in response. |
| Feature |
Supported |
Limitation |
| Inputs |
Partially |
Input changes are reported, but which terminal on the controller each one belongs to has to be worked out by trying them on site. |
| Outputs |
Partially |
An output can be switched on from the system, but there is no way to switch it off again from here. |
| Output schedules |
Not included |
Outputs cannot be set to switch themselves on and off at fixed times of day. |