Skip to content
JANOVA Access · Intercom
Access control

Access Control System

An access control system has four layers: credential, reader, controller and lock/power. Start with the door list and the cards people already carry; then choose a two-door controller for 1–2 doors, a four-door controller for 3–4 doors, and TCP/IP with RS485 downstream for larger sites.

  • 1–62 doors per IP
  • Wiegand / RS485 / TCP/IP
  • Offline decisions
  • PRO3000: CE / FCC / C-TICK
Access control keypad and card reader
Quick answer

What does an access control system include?

It includes a credential (card, face or QR), a reader, a controller and a lock with its power supply. The controller stores permissions and events, so doors keep working when the server is offline. For 1–2 doors, a two-reader board is usually enough; for 3–4 doors, use a four-door board; larger sites extend over RS485 or multiple TCP/IP controllers.

  • Start from the door list, not the reader
  • Match the reader to the existing card technology
  • Keep lock power separate and size it for inrush
  • Confirm fire release and lift interfaces before quoting
Selection tables

Which controller, reader and lock fit this door?

The first table maps the door requirement to a controller and reader. The second compares the models used on this page. The third lists the design checks that decide whether the system will pass commissioning.

Selection table — controller, reader and lock

Door requirementRecommended configuration
One or two doors Two-reader controller or a standalone terminal
Four or more doors Four-door controller or multiple TCP/IP controllers
Existing cards Match 125 kHz ID or 13.56 MHz Mifare readers
Offline or unstable network Controller with card/event buffer and battery backup
Lift or fire integration Relay I/O and a documented platform API

Controller and reader models in this range

ModelTypeKey capacityInterfacesBest for
PRO3000 Two-door network controller 55,000 cards; 45,000 events TCP/IP; RS485; 2 readers; 4 relays 1–2 doors with offline decisions
CD8000 Series Single, double or four-door controller CD8001 / CD8002 / CD8004 TCP/IP; -35 to +65 °C 1–4 doors in one enclosure
HA-MCR45-32 13.56 MHz Mifare reader ISO 14443A; 6.4 cm read range Wiegand output Existing Wiegand controllers
AskFaceBS Browser management software Access, visitor, attendance, lift, large screen TCP/IP; local network Central permissions and reports

Design checks before the quotation

Design itemTypical settingWhy it matters
Door count 1–2 / 3–4 / 5–62 per IP address Sizes the controller, enclosure and power supply
Credential 13.56 MHz Mifare, face, QR, or existing ID/CPU cards The reader must match the cards people already carry
Reader output Wiegand 26/34 or RS485 Must match the controller input format
Controller location Secure-side cabinet or IT rack Protects the board and simplifies service
Offline capacity 55,000 cards / 45,000 events for PRO3000 Doors keep working when the server is offline
Network TCP/IP with fixed IP or DHCP reservation Keeps the controller reachable and stable
Lock type Maglock, electric strike or bolt; fail-safe or fail-secure Affects egress, fire behaviour and power
Lock power Dedicated supply with battery backup Handles inrush current and holds the lock during outages
Exit device Button, motion sensor or break-glass Code-compliant egress from the secure side
Door contact Monitored input for held-open and forced-door alarms Turns the door into a monitored opening
Interlock Two-door airlock where required Prevents two doors opening at the same time
Anti-passback Entry and exit readers with direction logic Stops one card being passed back
Fire release Dry contact or relay from the fire panel Unlocks doors for evacuation
Lift control Relay or software option with a compatible lift interface Applies the same permission model to floors
Software AskFaceBS or the existing platform Permissions, records and reports live here
Commissioning Door-by-door test, including fire release and lock failure Catches wiring and configuration faults before handover
Compatibility & boundaries

What can this system do, and what still needs confirmation?

The controller is the integration point. Confirm the third-party interfaces at design stage; do not assume that a relay is enough for every fire, lift or CCTV system.

What it can do

  • Connect 13.56 MHz Mifare readers over Wiegand
  • Control maglocks, strikes and bolts through relay outputs
  • Keep working offline with local card and event storage
  • Extend over RS485 or multiple TCP/IP controllers
  • Integrate fire release, lift control and CCTV where the interfaces exist

What it cannot do / needs confirmation

  • Fabricate door frames, cut concrete or provide civil works
  • Guarantee an existing card system without the card type and reader format
  • Replace fire acceptance or code compliance review
  • Integrate a third-party platform that has no documented API
  • Size the lock power supply without the lock model and current

Send the door list, card type, controller model, lock model and fire/lift interface documents. We will mark what is confirmed and what still needs a site check.

Frequently asked questions

Access control questions buyers ask before ordering.

The answers below follow the controller, reader and lock logic used on this page.

How many doors can one controller handle?

A two-reader board typically controls two doors; four-door boards cover four. Larger sites can extend over RS485 or use multiple TCP/IP controllers. Confirm the door list and reader direction.

What card technology should we use?

13.56 MHz Mifare (ISO 14443A) is common for new projects. If the site already uses ID or CPU cards, confirm the reader compatibility before changing the ecosystem.

Does the controller keep working without a server?

Yes. Access decisions and event storage run on the controller; the platform synchronises when the connection returns. Confirm the offline capacity for your cardholder count.

Can we integrate with fire, lift and CCTV?

Controllers provide relay inputs/outputs and platform APIs for common integrations. Share the third-party system interface documents at design stage; integration is confirmed case by case.

Do we need a controller if the reader has a relay?

A reader with a relay can control one lock, but it does not provide multi-door coordination, central permissions or a full audit trail. Use a controller for multi-door sites, anti-passback, interlock or platform integration.

Can you match our existing cards?

The standard reader in this range is 13.56 MHz Mifare. For 125 kHz ID or CPU cards, the reader and controller format must match the existing card system. Send a card photo, the chip type and the current reader model before ordering.

Still have a question? Contact

Get a quote

Send the door list. We will return a controller and reader configuration.

Include the door count, card type, lock type, existing controller and any fire or lift interface. We will reply with a model mix and the questions that still need answers.

  • Door list / unit list
  • Existing cable, cards and controller
  • Site photos and timeline

Project inquiry

Share the site type, number of doors or apartments, and the functions you need. We will reply with a recommended configuration and a quotation.

By submitting this form you agree that we may contact you about this inquiry. We do not sell your data. Privacy policy