Local Linkage - Reader Alarm for Mercury Controllers

Local Linkage - Reader Alarm for Mercury Controllers

1.0 Introduction

When using Mercury EP, LP or MP controller types, when a reader generates a door forced or door held event you will see the event in live events but the reader does not go into 'alarm state' - the reader LED does not change state and the reader does not beep. To create this reader behaviour you must use Local Linkage. Local Linkage procedures are used to define how the reader behaves and to cancel this custom behaviour.

A trigger is then setup to use the door-forced or door-held event which will trigger the first procedure. A second trigger is used to define when the door is secured - this will trigger the procedure that cancels the reader alarm state.


2.0 Create a Procedure to Define the Reader Alarm Mode

  1. In Doors.NET go to Setup >> Advanced Local Linkage.



  2. Local Linkage will open up on the Procedures tab.
  3. Select the controller.
  4. Click the NEW PROCEDURE button.



  5. Select the new procedure then enter a new name for the procedure (for example: Reader Alarm - door name).
  6. With the procedure still selected, click on the ADD ACTION button.
  7. Select the new action.
  8. From the Action Item Type on the right select Reader Temporary LED Mode Control.



  9. From the Reader drop-down list, select the specific reader that you wish to apply the procedure to.
  10. Set an ON color and the amount of time in milliseconds for the ON color to display.
  11. Set an OFF color and the amount of time in milliseconds for the OFF color to display.
  12. Set the Repeat value to 1 and the Beep value to 3.



  13. Save the first procedure action (using the save/save all icon in the upper-left of the client).



  14. Select the reader alarm procedure again and click the ADD ACTION button again. This will add a second action to the procedure.
  15. From the action item type list select Time Delay then set the delay to 1 second.



  16. Save the second action.
  17. Select the main procedure again and click the ADD ACTION button again.
  18. From the action item list select Procedure Control then select the main procedure that has been setup.
  19. Select to execute this procedure. This will mean that the first procedure will execute, there will a 1 second delay, then the procedure will trigger again. This will continue to happen while the door is forced or held open.



  20. Save the third action item.

3.0 Create a Second Procedure to Cancel the Reader Alarm Procedure

A second procedure should now be created that will cancel/abort the first procedure. This second procedure will be triggered when the door closes (and is no longer forced or held).
  1. Click the NEW PROCEDURE button.
  2. A second procedure will be added to the top of the list.
  3. Select the new procedure and name it something like 'Cancel Reader Alarm'.
  4. Click the ADD ACTION button and select the new action.
  5. From the action type list on the right select Procedure Control.
  6. Select the procedure that was setup in section 2.0.
  7. Select Abort Delayed Procedure.



  8. Save the second procedure.

4.0 Create the Trigger to Activate the Reader Alarm

The next step is to create the trigger to activate the reader alarm procedure. This will happen when a specific reader activates door held or door forced events.

  1. Click on the Triggers tab.



  2. Verify that the expected controller is selected.
  3. Click the ADD TRIGGER button.
  4. Select the new trigger condition.
  5. Name the new trigger - i.e [Door Name] - Forced or Held.
  6. From Execute this Procedure list select the reader alarm procedure.
  7. Procedure Command should be left at the default selection.
  8. From the Source Type list, select ACR: Door Position Sensor.
  9. From Source select the specific reader.
  10. For Active During this Schedule select Always or a schedule to determine when the Local Linkage action should be active.



  11. From the transactions list on the right click on More Transactions and then select Either (Forced or Held).



  12. Save the first trigger via the save icon(s) in the upper left.


5.0 Create the Trigger to Cancel the Reader Alarm 

A second trigger must now be created to execute the procedure that will cancel the reader alarm (the second procedure that was created) this trigger will be activated when the door is closed/secured and the reader generates a door secure event.
  1. On the Triggers tab click on the ADD TRIGGER button.
  2. Select the new trigger condition.
  3. Name the new trigger - i.e [Door Name] - Secured.
  4. From Execute this Procedure list select the cancel reader alarm procedure.
  5. Procedure Command should be left at the default selection.
  6. From the Source Type list, select ACR: Door Position Sensor.
  7. From Source select the same reader that was selected for the first trigger.
  8. For Active During this Schedule select Always or a schedule to determine when the Local Linkage action should be active.



  9. From the transactions list on the right select: Door Secured Previously Forced or Held Open.



  10. Save the second trigger.


6.0 Test the Reader Alarm Functionality

You should now activate the reader forced or held event at the configured reader.
​
As soon as the forced or held event appears in live events it will be followed by events that indicate the first procedure has been activated. The physical reader should then start beeping and displaying the LED behaviour as defined in section 2.0.



When the door is closed/secured the reader will generate a door secured event it will be followed by events that indicate the second procedure has been activated. The physical reader will stop beeping and the LED will go back to displaying its normal state.




    • Related Articles

    • Local Linkage Overview

      The Local Linkage section is by far the most powerful feature of the Doors.NET system. It is an advanced input/output management application that allows you to easily customize the operational mode of the controller to suit individual requirements. ...

    • Mercury EP Controllers Overview

      Introduction In addition to our own Mercury Powered NXT controllers (NXT-MSC), Keri also offers non-proprietary authentic Mercury Security hardware, which is supported by Doors.NET Professional Edition software. The hardware platform consists of the ...

    • Mercury LP Controllers Overview

      Introduction In addition to our own Mercury Powered NXT controllers (NXT-MSC), Keri also offers non-proprietary authentic Mercury Security hardware, which is supported by Doors.NET Professional Edition software. The LP hardware platform consists of ...

    • Local Linkage - Program an Output to Follow an Input

      1.0 Introduction A basic Local Linkage example is to program an output on the system to follow an input, so that when the input goes active the output automatically goes active. When the input goes inactive then the output also goes inactive. Prior ...

    • Local Linkage Triggers

      The table below lists all of the available trigger conditions. Changing the Source Type drop down selection will change the available Transaction Type selection. Source Type Transaction Type Available Selection Criteria Access Area Access Area Area ...