Practical lab · Access control

Access-control door logic

Fill in a truth table of door states and the events a controller reports.

Simulation — not real hardware

Simulation — not real hardware. Results are planning estimates from the formulas shown; real equipment, cabling and firmware differ. Check datasheets and site conditions before you buy or install.

What this lab covers

A single controlled door has a lock, a reader, a door position contact and a request-to-exit (REX) button. The controller watches them and reports events: a valid card releases the lock; the door opening without a valid card or REX is forced; an authorised opening left open past the held-open time is held.

Real controllers add schedules, anti-passback, interlocks and fire-alarm release. This exercise covers the core logic you need to read an event log.

Worked example

Door closed, nobody at the reader: Normal — door closed and locked.

Door contact opens but no card was read and REX was not pressed: the controller cannot tell who opened it, so it reports Door forced open — alarm — usually a missing REX on the inside, a mechanical key, or a door pushed open.

Try it

Door states and the event to choose for each
#Door openCredentialREXHeld timerEvent
1No—No—
2NoValidNo—
3NoInvalidNo—
4Yes—NoRunning
5YesValidNoRunning
6YesValidNoExpired
7Yes—YesRunning
8Yes—YesExpired
contactreaderREXno alarm
Row 2 as the controller sees it. Focus a row's choice to draw it.
Progress is kept only in this browser.All labsNext: Reader wiring: Wiegand and OSDP

Talk to an engineer

Not sure which service fits?

Tell us what you are working on. A Foxnet engineer will point you to the right session, book or request — or tell you honestly if you do not need one.