All Collections
Access Control
For Administrators
How to update LED and Buzzer settings of a reader?
How to update LED and Buzzer settings of a reader?

Learn how to customize the LED and buzzer settings of a reader attached to a Mercury controller

G
Written by Genea Developer
Updated over a week ago

The LED and buzzer settings of readers connected to Mercury controllers can be customized from Genea's web application. Administrators can effectively change a reader's LED and buzzer behavior during different states and access control events.

Overview

Every Mercury controller has 3 LED mode tables (1, 2 and 3). Shown below is the LED mode table 1 (the default LED mode table):

Each LED Mode table has information on a reader's LED behavior for different states which are categorized into Idle and Transient as follows:

  1. Idle states: Rows 1-8 above are idle states.

  2. Transient states: The remaining rows (9-14) are transient.

Each state in an LED mode table has customizable information pertaining to the color, duration and frequency of flashing of the reader's LED, along with the onboard buzzer's beep count. The interpretation of the different columns in the above table is as follows:

The reader's LED will display the <On Color> color for <On Time> seconds followed by the <Off Color> color for <Off Time> seconds. This transition will repeat <Repeat Count> times and the reader's onboard buzzer will sound <Beep Count> times.

As an example based on the above table, during an Access Grant event, the reader will display the Green color for 0.2 secs (200 ms), followed by the Off color (no color) for 0.2 secs (200 ms). This transition will be repeated 7 times, and the buzzer will sound once.

The fundamental idea behind LED / buzzer control is that the states in a LED mode table of a Mercury controller can be customized. Following this, readers attached to that controller which point to that LED mode table will start operating as per the modified LED / buzzer configuration.

Use cases

Here, we will explore a couple of use cases for this feature.

I. Change the LED behavior of readers attached to a Mercury controller

Let's say you have a Mercury controller with 10 readers attached to it. All 10 readers are on an Unlock schedule. You want to change their unlock state LED behavior to a flashing blue. This can be achieved as follows:

  1. Visit the Mercury controller's details page.

  2. Scroll down till you see the 3 LED mode tables.

  3. Click the Edit button next to the Unlocked row as shown below.

  4. A modal with a form will popup. To achieve a blue blinking, fill the form as shown below and hit Save.

This will ensure that all the 10 readers have a blinking blue LED in their idle (Unlocked) state.

II. Assign a different LED Mode table to a reader

In continuation with the previous use case, let's say you attach another reader to the Mercury controller. This reader too is on an Unlock schedule. However, you want its unlock state LED behavior to a steady green. This can be achieved as follows:

  1. Follow steps 1 and 2 from the previous use case.

  2. Click the Mercury LED Mode table 2 tab.

  3. Follow steps 3 and 4 from the previous use case. Make sure to supply the color Green as both On Color and Off Color.

  4. Navigate to the newly attached reader.

  5. Scroll to the Door Access section and click the Edit button.

  6. Select Mercury LED Mode Table 2 from the LED Mode dropdown and hit Save.

The newly attached reader will now have a steady Green LED in its idle (Unlocked) state.

Notes

1. Parameters <Repeat Count> and <Beep Count> are disregarded for idle states as the reader alternates between <On Color> and <On Color> indefinitely.

2. For transient states, <Repeat Count> can range from 1 to 255, while <Beep Count> can be from 0 to 15.

3. Access Granted is a unique Transient state that also disregards the <Repeat Count> parameter. The reader will occupy the entire Access Grant Time, regardless of the <Repeat Count> value. Access Grant Time can be customized in the Door Access section of the Door details page.

4. Unlocked is a unique Idle state that requires a full cycle for changes in LED/buzzer configuration to take effect. For example, if we modify the LED behavior from Green-Red-Green to Green-Blue-Green while a reader is in the Unlocked state, the changes won't immediately apply. Instead, the new behavior will take effect on the next cycle when the reader returns to the Unlocked state.

5. Genea supports reader LED / buzzer customizations for the following readers:

HID

WaveLynx

STiD

HID RP10

Mullion Model ET10

ARCS-AQ

HID RP15

Single Gang Model ET20

ARCS-A

HID RP40

Keypad Model ET25

HID RPK40

Signo™ Reader 20

Signo™ Reader 40

Signo™ Reader 20K

Signo™ Reader 40K

6. LED and buzzer customizations is supported by both Wiegand and OSDP readers. With OSDP readers, administrators have a broader range of colors to choose from. The following colors are supported by the above reader models:

Colors

Off (no color / reader LED off)

Red

Green

Amber

Blue (Available only on select OSDP readers)

Magenta (Available only on select OSDP readers)

Cyan (Available only on select OSDP readers)

White (Available only on select OSDP readers)

7. The availability of the colors on each reader depends on the reader model and its wiring. In the event of a color being unavailable, the reader usually falls back to another color in the list.

8. In case of HID readers, the color Off behaves differently for OSDP and Wiegand protocols. When configured as per Wiegand protocol, an HID reader's Off color is the same as the Idle color configured from the HID Reader Manager app. If the Idle color is set to be Amber, then the Off will be the same as Amber. However, in case of OSDP, the Off color is the same as no color (reader LED off).

Did this answer your question?