1.0 Introduction

The Allegion AD Series locks can be integrated with the Local Linkage feature to provide enhanced functionality and monitoring.

Note: Both the AD-300 and AD-400 locks can be used with Local Linkage.

2.0 Ensure Advanced Local Linkage is Enabled

1. Verify that your NXT-MSC controllers are updated to the latest firmware revision (1.211) at the time of writing.
2. Verify that Local Linkage is enabled on your Doors.NET license (you can check this via Start >> All Programs/All Apps >> Doors.NET >> License Manager).
3. Click on the License tab.
4. Scroll down to Options.
5. Check that 'Enable Advanced Local Linkage' is set to True.
   
   
   
   
6. Log in to the administrative client then go to Setup >> Advanced Local Linkage icon.
   
   

3.0 Configure the Local Linkage Procedure

When Local Linkage screen open it will be on the procedures screen.

1. Select the NXT (MSC) controller from the controller drop-down list (the controller which the AD lock is communicating to).
2. Click the New Procedure button then highlight 'New Procedure 1'.
3. The procedure is what you want the system to do, for example; you may want to activate a specific control point (output), which in turn might activate a buzzer or switch on an LED.
4. The control point would have to be located on the same NXT (MSC) controller and it cannot be programmed for a function such as a door contact, RTE 1 or RTE 2. (It must be listed in the hardware tree as a 'Control Point').
5. This setup example will use a 4x4 module connected to one of the controller's other buses (bus 2) - The outputs on the 4x4 have already been labeled (Buzzer 1 and 2 plus LED 1 and 2).
   
   
   
   
6. This example will also use a PIM 400-485 and AD-400 connected to bus 1 of the controller, as shown in the following image.
7. With New Procedure highlighted, input a new description, such as Buzzer 1 - On, then save  (via the icon at the top left of the user interface).
8. Click the Add Action button.
9. Highlight the new action entry.
10. From the Action Item Type list on the right, select Control Point Control.
11. From the Control Point list, select the output named 'Buzzer 1'
12. Then set the action to On.
    
    
    
    
13. Click the New Procedure again and name it Buzzer 1 - OFF, and save.
14. Click the Add Action button again.
15. You have to setup the second procedure to set the same control point to OFF, as shown below.
    
    
    
    
16. Once you have saved these two procedures you are ready to set up the two required triggers.

4.0 Configure the Local Linkage Triggers

The Local Linkage triggers are the event types that activate the Local Linkage procedures. Most triggers have opposite event types; such as an input going active (and then secure), a tamper going active (and then secure) or a controller going offline (and then back online). In this setup example we have to decide which trigger will activate the control point for buzzer 1 and which opposite trigger will deactivate buzzer 1.

There are various extended event types generated by the AD-400 locks, these events are as follows:

- Interior Push Button: Inactive

- Interior Push Button: Active
- Dead Bolt: Retracted
- Dead Bolt: Extended

- Request To Enter: Inactive
- Request To Enter: Active

- Motor: Normal

- Motor: Stalled

- Lock Clutch: Inactive
- Lock Clutch: Active

- Low Battery: Normal
- Low Battery: Alarm

- Critical Battery: Normal
- Critical Battery: Alarm
- Bezel Tamper: Secure
- Bezel Tamper: Alarm
- Keyswitch: Inactive
- Keyswitch: Active
- Communication: RF Restored
- Communication: RF Loss

1. We will use the two Low Battery event types for our two triggers.
2. To setup the first trigger click the Add Trigger button.
3. Rename the trigger with a description such as; Low Battery - Door 1.
4. From Execute This Procedure select Buzzer 1 - ON.
5. Procedure Command should be left at its default setting.
6. rom Source Type select Access Control Reader (ACR).
7. On the right you will see a list of system events (transactions).
8. Change the Type to Extended Mode using the drop-down list.
   
   
   
   
9. The Extended Mode transaction list will appear so select the Low Battery: Alarm transaction type.
10. From Source select the AD lock wired into bus 1.
11. Active During This Schedule should be set to Always.
12. Trigger Variable Logic should be left at the default setting of None.
13. Your setup for this first trigger should resemble the image shown below:
    
    
    
    
14. Click the Add Trigger button again to begin the setup of the second trigger.
15. Name this trigger 'Normal Battery - Door 1' or something similar.
16. This second trigger setup will be almost identical to the first trigger, the only exceptions are that the 'Buzzer 1 - OFF' procedure will be selected and the transaction type will be Low Battery: Normal, instead of Low Battery: Alarm.
17. Setup of the second trigger should resemble the screen shot below:
    
    
    
    
18. This Local Linkage action setup is now complete; when the AD series lock has a low battery it will generate an event which will activate buzzer 1 via Local Linkage. When the battery level is normal again the buzzer 1 will be deactivated via Local Linkage.
19. This is just a typical example. When using the AD series lock sets, any of the listed event types can be used as triggers to action anything that the NXT (MSC) controller is capable of performing.