Access control · Free guide

HID card detected but door not opening: what to check

The reader beeps but the door stays locked. Use the controller’s event to decide whether the fault is the card and access rules, the reader link, or the lock, relay and power — then check each in order.

Someone shows a card, the reader beeps or flashes, and the door stays locked. The beep only tells you the reader saw something. Whether the fault is the card, the access rules, the reader link, or the lock and its power, the controller’s event log will tell you which half of the system to look at. This guide uses HID cards and readers as the example because they are common on Indian sites; the same logic applies to other makes.

Start with the event log

Present the card once, note the time, and find that moment in the access control software or the controller’s own event list. You will see one of three things:

What the event tells you
Event shownWhere the fault isGo to
Nothing at allThe card data is not reaching the controller: reader wiring, reader settings, or the controller portNo event at all
Access denied (or invalid / unknown card)The controller received a card but refused it: enrolment, card format, access level, schedule, statusAccess denied
Access grantedThe decision was right but the door did not release: relay, lock power, lock or door hardwareGranted, still locked

If the software shows nothing, check that the controller is online (an offline controller still makes decisions but cannot report them live). Look at the reader LED too: on most systems the controller drives the LED, so a green flash means the controller granted access even if the software has not caught up.

No event at all

  1. Try a second, known-good card. If a card that works on another door also gives no event here, the problem is the reader or its link, not the card.
  2. Check reader power. Measure the supply at the reader terminals with the reader working. Readers on long, thin cable can see too little voltage, especially when the lock and reader share a supply.
  3. Check the data wiring for Wiegand readers. Data 0 and Data 1 must go to the matching controller terminals; swapped lines give wrong or no reads. The reader and controller must share a common 0 V. Keep Wiegand runs within the reader maker’s limit (commonly about 150 m with suitable cable) and away from mains cables.
  4. Check the settings for OSDP readers. OSDP runs over RS-485: the reader address and baud rate must match what the controller port expects, and if secure channel is enabled the keys must match. A reader set to Wiegand output on an OSDP port (or the reverse) will beep at cards and send nothing usable.
  5. Confirm the reader is on the port you think it is. On multi-door controllers, readers on the wrong port report against another door. Check that door’s events too.

The reader wiring lab lets you practise matching Wiegand and OSDP conductors to controller terminals.

Access denied

  1. Read the card number the controller received. Most systems show it in the event. Compare it with the number enrolled for that cardholder. If they differ, go to the next section on formats before anything else.
  2. Check the cardholder and card status. Is the card active, not expired, not reported lost? Has the cardholder’s validity date passed?
  3. Check the access level. Does the cardholder’s access level include this door — this exact reader, if entry and exit readers are separate?
  4. Check the schedule and the controller’s clock. Access levels usually apply only during a time schedule. If the controller’s date or time is wrong, a valid card can be refused at the right time of day. Holidays defined in the system change schedules too.
  5. Check door modes and rules. The door may need card plus PIN, may be in a locked-down mode, or may be refusing because of anti-passback (the card has not been used to exit), an interlock with another door, or a two-person rule.
  6. Check the change reached the controller. If the card or access level was changed while the controller was offline, the controller may still be working from old data. Confirm the download or sync completed.

Card numbers and formats

A proximity or smart card carries access data in a particular format: a pattern of bits that the controller must decode the same way the card was programmed. The most common is the 26-bit Wiegand format (H10301): one parity bit, an 8-bit facility code (0–255), a 16-bit card number (0–65,535), and a final parity bit. Many sites also use longer formats, such as 35-bit or 37-bit formats, that carry larger numbers.

  • Format mismatch: if the controller decodes a card in a different format from the one it was programmed with, it produces a different facility code and number, and the card is refused or shows as unknown.
  • Facility code: two cards can have the same card number with different facility codes. If the system checks facility codes, the enrolled facility code must match.
  • Serial number instead of access data: some smart-card readers can be set to send the card’s serial number (CSN) rather than the programmed access data. Cards enrolled one way will not match a reader set the other way, even on the same site.
  • Printed numbers: the number printed on a card is not always the number the controller sees. Where the software allows, enrol cards by presenting them at an enrolment reader rather than typing the printed number.

If several cards from one new batch are all refused while older cards work, suspect a different format or facility code in the new batch, and check the order details with the card supplier.

Access granted, door still locked

The controller made the right decision. Now follow the output to the lock.

  1. Listen and look at the relay. Most controllers have a relay LED or an audible click. No change on a grant means the door’s output is not configured, is mapped to another relay, or the relay has failed.
  2. Know the lock type. A magnetic lock is usually fail-safe: powered to lock, so the relay must remove power on a grant (normally-closed contact). An electric strike is usually fail-secure: powered to unlock, so the relay applies power on a grant (normally-open contact). Wiring a lock through the wrong contact reverses its behaviour.
  3. Measure at the lock during a grant. Measure the voltage at the lock terminals before and during a grant. For a strike it should rise to the rated voltage; for a magnetic lock it should fall to zero. A low voltage points to the supply, a blown fuse, or voltage drop on a long, thin cable.
  4. Check the unlock time. If the door output is set to release for a fraction of a second, the user may not get the door open in time. Most sites use a few seconds.
  5. Check the door hardware. A strike under pressure from a door that does not close squarely (preload) may not release. A magnetic lock with a damaged armature, or a door closer and seals fighting each other, can feel “locked” even with power removed.
  6. Protect the relay. DC lock coils produce a voltage spike when switched off. A suppression diode (or the device recommended by the lock maker) across the lock protects the relay contacts.

The door logic lab walks through door states and events, and the power budgeting lab helps check lock supplies and battery backup.

Safety and escape routes

If the controller, lock or wiring needs replacing, or the fault is intermittent, the access control hub lists the help available. HID, Prox, iCLASS and Seos are trademarks of their owner; this guide is independent and not produced or endorsed by the manufacturer.


This guide is general technical information written for installers, engineers and facility teams. Check the manuals for your exact equipment and follow site safety rules. Brand names identify products only; Foxnet University is independent of the manufacturers mentioned.

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.