The reader: reading and nothing more
The reader reads the number from the card and passes it to the controller. In a typical installation it does not make the decision to open the door, because it does not know the permission list, the schedules or the state of the door. Its task is reading, signalling (LED, sound) and passing the data over the link.
That is why removing a reader from the wall by itself does not open the door: the decision is made further on, in the controller. This matters for assessing the sabotage risk, which we describe in the guide on securing an access control reader.
The controller: where the decision is made
The controller compares the received card number with the permission list, checks the schedule and the state of the door, then sends a signal to the lock and records the event. It is also the source of the events that the higher-level system sees: a swipe, a refusal, a door held open too long, reader sabotage.
In case of a fault, it is worth asking: did the controller receive the data at all? If the reader lights up and signals a read, but there is no event in the controller, the problem lies in the link.
Stages of the path from card to door (order)
The link: Wiegand vs OSDP
Wiegand sends data as plain text and does not let the controller check whether the reader is connected and working. OSDP runs on an RS-485 link and is a two-way protocol: the command and the response confirm delivery of the message, and the controller supervises the reader status continuously.
For maintenance the difference is practical. With OSDP a missing reader event points to a specific address, while with Wiegand we learn about a fault from the user. On one RS-485 bus several readers can operate in a chain, so a single cable break can switch off several doors.
Step-by-step diagnosis
Start with the reader: is it powered and does it signal a read? Then check in the controller whether the swipe event appeared. If it did, and the door still does not open, look at the permissions, the schedule or the lock. If there is no event, check the link, the reader address and, in OSDP, the status of the encrypted channel.
Record the result of every diagnosis in a fault register with the reader address and the date. After a few months, doors that fail more often than others become visible, and a replacement can be planned.
Where InnerWeb sits in this chain
InnerWeb does not produce readers or controllers. It receives swipe events from the access control system and links them with qualifications, permits and attendance. It therefore works further down the chain than the controller and takes no part in the decision to open the door. A change of the reader-to-controller protocol requires no changes on the InnerWeb side, as long as the access control system keeps sending events.
Video
Frequently asked questions
Does the reader open the door by itself?
In a typical installation, no. The reader passes the card number on, and the decision is made by the controller based on permissions and the schedule.
What does the reader address mean in OSDP?
The address identifies the reader on the RS-485 bus, so the controller and the events point to a specific device.
Can one cable break switch off several doors?
On a chain of readers on one bus it can happen, depending on the topology and the place of the break.
Does InnerWeb affect opening the doors?
No. The controller decides; InnerWeb receives the events and links them with permits and attendance.
Sources
Let's talk about integrating with your access control system
We will describe which events from the InnerWeb access control system can be received and how to connect them with permits, attendance and working time recording. We will propose a demonstration on your data.
Let's talk