Add a Reader

Adding an access controller automatically adds placeholders for its non-configured, on-board readers depending on the number of on-board readers supported by the controller. For example, when an LNL-4420 is added, two on-board reader placeholders are added to it. Similarly, adding a reader interface automatically adds downstream reader placeholders. One reader placeholder is added to a single door reader interface, and two are added to a dual door interface.

Changing the number of readers, regardless of their online or offline status, may affect the system operating costs. Contact your VAR for more information.

To configure these readers, perform the following steps:

From the sidebar, select Devices to display the device tree.
Select a reader placeholder to open its configuration screen. Alternatively, select on the placeholder and then Configure.
Enter a Name for the reader. This name is used when assigning card readers to spaces, when monitoring alarms, and elsewhere in the system.
Choose the type of reader Protocol that is output by the reader (such as Wiegand or OSDP).
- LNL-X2210 - Dual Onboard readers only support Reader 1 for OSDP.
- LNL-X2210 - Single Onboard + SIOs readers do not support OSDP.
For OSDP readers, only: Use Secure Channel is enabled by default for new readers. (See Secure communications.)
When a reader is in "Card and PIN" mode, a special duress PIN signals to the system that the person attempting entry is in danger (they may be entering under threat). If Duress PIN allows access is enabled, access will be granted under duress and the event "Access Granted - Entry Occurred - Duress PIN Used" or "Access Granted - No Entry Occurred - Duress PIN Used" will be generated depending on whether or not the door was opened. If Duress PIN allows access is disabled , access will be denied under duress and the event "Access Denied - Duress PIN Used" will be generated. (Duress PIN allows access is enabled by default for new readers.)
The duress PIN is the person's current PIN + 1. For example: If their PIN is 123456, the duress PIN would be 123457. If the last digit of their PIN is “9”, the duress digit needs to be “0”. For example: If their PIN is 123499, the duress PIN would be 123490.
For Wiegand readers, only:
1. Choose the type of LED wiring. This configures the LED on the reader, and is activated only if the reader is connected to an access controller.
  1. 1-wire - The LED control is via a single wire.
  2. 2-wire - Two wires will be used to control the LED on the reader. This option applies to readers that support 2-wire communication and is the default choice.
2. Choose the type of Keypad (if any) this reader has.
  For OSDP keypad readers, 8-bit or 4-bit burst reader configurations are not required. Instead, all PIN entries are transmitted via standardized ASCII messaging.
  For Wiegand keypad readers, select one of the following types:
  - No keypad
  - 8-bit burst - For 8-bit output keypads with an 8-bit burst of data corresponding to the specific key sent each time a key is pressed. This option is commonly used for Credential and PIN verification.
  - 4-bit burst - For 4-bit output keypads with the keypad data sent in 4-bit Wiegand key-bursts.
Enable Pair to a primary reader to pair the reader with a primary reader for controlling a single door as a primary-secondary set. When pairing is enabled, choose a Primary Reader on the same controller that is not already a primary or secondary reader. Note: Paired readers do not need to be on the same reader interface and can be onboard readers.
See Paired LNL-Series readers to learn more.
Select to enable Allow authorized access to locked door. This allows people with special access to open this reader's door when it is locked. Special access must be authorized for people via People Groups. (For more information, refer to Locked Door Override.)
Configure reader modes:
1. (Optional) Choose a Schedule from the drop-down to associate it with reader modes. (See Configure scheduled reader modes.)
2. Choose a Default reader mode from the drop-down. This mode specifies how the reader behaves when it is online and communicating with the access controller. Most of the modes are self-explanatory, except for "Facility code only" which means the access grant decision is based on the facility code setting for the card format. The "Credential and PIN" mode is available when a Keypad reader type is configured.
3. Choose an Offline reader mode from the drop-down. This mode specifies how the reader behaves when communication is lost between the controller and the reader interface.
Configure double card presentation:
1. Select to enable Double Card Presentation. In addition to configuring the reader, double card presentation must be authorized for the person through People Groups.
2. Choose the behavior for the reader when a badge is presented twice.
  - Unlock until reset (default setting) - The reader mode will be changed to Unlocked, returning to its configured mode when the schedule changes.
  - Unlock until manually released - The reader mode will be changed to Unlocked, behaving as a reader mode override that applies until a user releases the reader from the override or an action that is configured by a controller rule triggers the change.
  - Unlock for a limited time - The reader mode will be changed to Unlocked, behaving as a reader mode override that applies for a specified time. Select the Duration from the drop-down or enter a custom duration. The maximum duration is 7 days.
  - Event only - This is intended to be used as an event that will trigger an action (for use in conjunction with controller rules).
    The first time a card is presented, it will generate an access event. If the card is presented a second time within 5 seconds of the first presentation, it will trigger a double card presentation. If the person is authorized for double card presentation, the configured reader behavior will take effect.
Configure door strike:
1. Enter the Strike time. This specifies the number of seconds the door strike is energized when access is granted. Typically, this is set from 5 - 10 seconds, but Strike time can be set from 1 - 255 seconds (4.25 minutes).
2. Enter the Held open time. This specifies the number of seconds the door can be held open before an alarm is generated. Held open time can be set from 1 - 32,767 seconds (approximately 9 hours). The default value is 30 seconds.
3. Enter the Extended strike time. This specifies the number of seconds the door strike is energized for people with Use extended access times enabled. This field is intended for people who need extra time to proceed through a doorway.
4. Enter the Extended held open time. This specifies the number of seconds a door is held open for people with Use extended access times enabled. This field is intended for people who need extra time to proceed through a doorway.
5. Select to enable Do not activate strike on REX. A REX contact is typically a button, motion sensor, or crash bar assembly located near the associated door. When a cardholder pushes the button or activates the sensor, a REX (Request to Exit) is sent to the access controller. If Do not activate strike on REX is enabled, the door strike will not energize when the REX contact closes. If Do not activate strike on REX is disabled, the door strike energizes when the REX closes.
Configure door contact:
1. Choose the supervision setting that specifies how input for door contact will be individually monitored based on how the hardware is wired.
  Supervision and normally open/closed configuration options:
  - Unsupervised, Normally Closed (Default for door contact)
  - Unsupervised, Normally Open (Default for REX)
  - Standard Supervision, Normally Closed
  - Standard Supervision, Normally Open
  Each auxiliary input can be individually wired for either supervised or unsupervised activity. An unsupervised input is an unprotected, low security input. Someone can short-circuit the connection between the auxiliary input and the device controlled by the input, thereby defeating the circuit. Although the device may trigger an alarm condition in such a situation, the auxiliary input will not be aware of it.
  By contrast, a supervised input’s circuit is equipped with resistors. Subtle changes in the voltage on the circuit can be detected to determine whether someone has tampered with the wiring. For this reason, supervised inputs provide a high level of security.
  The standard supervised circuit requires 1k ohm, 1% resistors in a series and in parallel. See wiring diagram examples in Alarm Contact Wiring for the Dual Reader Interface Module LNL-1320 and Input Circuit Wiring for the Intelligent Controller LNL-X4420.
2. Select to enable Assume door used. All valid card swipes are then reported immediately as “Access Granted - Entry Occurred” events, even if the person did not open the door. If Assume door used is not enabled, “Access Granted - Entry Occurred” is not reported until the person opens the door after a valid card swipe. If the door is not used, the event “Access Granted - No Entry Occurred” is reported.
3. Select to enable Ignore door forced. When ignored, no "Door Forced" events or statuses will be reported for this device.
4. Select to enable Ignore door held. When ignored, no "Door Held" events or statuses will be reported for this device.
Configure REX (Request to Exit). A REX contact is typically a button, motion sensor, or crash bar assembly located near the associated door. When the device is activated, a REX is sent to the system:
1. Monitoring: Choose the supervision setting that specifies how the input for REX devices will be individually monitored.
2. Send REX events is disabled by default. This specifies that the "Request to Exit - Door Used" and "Request to Exit - Door Not Used" events will not be sent to reduce clutter in the event feed. Enable this setting to receive the REX events in the event feed.
  When Send REX events is disabled, email notifications will not be sent for the "Request to Exit - Door Used" or "Request to Exit - Door Not Used" events. However, the controller rules still apply for these events even though they are not included in the event feed.
3. Disable REX during schedule is off by default. If this option is on , REX functionality and events will be disabled during the schedule specified in Choose schedule. An example of disabling REX: If the REX input is triggered, it will not activate the door strike to open the door.
Select Save to save the configuration. If you exit this screen after entering the reader information without saving, you will be prompted to save or discard your changes.

When saved, OSDP readers configured to Use Secure Channel will enter link mode until the reader establishes an encrypted connection on the Secure Channel. (See OSDP secure channel link mode.)

The first time a downstream reader is configured for an LNL-X2210 (LNL-2210), synchronize the access controller.

Training videos:

Related Topics