Lift control – configure 2N systems to control lift access

You can setup 2N RFID/Keypad/Bluetooth/Fingerprint equipped IP units to control which floors authorized user can access.

The whole scenario allows interconnection of 2N IP units with AXIS A9188 I/O Relay Modules, which tells the lift which floor can be accessed after a person authorizes using the 2N IP unit as shown on the following image:

Types of most typical scenarios are:

1. A 3^rd party RFID card reader in the lift cabin is connected over Wiegand to a 2N Access Unit or located at the top of the shaft or in the Machine room. The 2N Access unit communicates over IP with the Axis A9188, which is connected to the Lift Controller. The Lift Controller uses CANbus (or similar) to control the buttons in the Lift Car.
2. A 2N Access Unit or supported intercom is installed in the lift cabin requiring an Ethernet cable connection from the machine room. This is the most convenient scenario. The 2N device communicates again over IP with the AXIS A9188 in the same way as above.
3. A 2N Access Unit or supported intercom is installed in the lift cabin, which does not have an Ethernet connection. 2N^® 2Wire converters are used to bring IP connectivity and PoE through the Lift car’s traveling cable over available 2 wires. This provides IP connectivity for communication between the  2N device and the Axis A9188, which is linked with the Lift Controller.

The following guide will explain, how to set the whole scenario to allow a person access to certain floors in the lift using their credentials (RFID, Code, Bluetooth or Fingerprint).

Configure the 2N unit to communicate with the AXIS 9188 I/O Relay Module

• Make sure the 2N device has Gold license (Lift feature included) installed and firmware 2.27 or newer is used.

• Connect the 2N unit to the AXIS A9188 I/O Relay Module in section Hardware - Lift Control by specifying the IP address of AXIS A9188.

Make sure you fill in the authentication as well (admin credentials for the AXIS relay module - root/root by default).

2N® Access Commander

• Create a Zone for each Floor in the section Zones. It is correct that these Zones will not have any device assigned, since lift enabled devices cannot be added to any Zone.
  
  
  
  
• Assign each zone to the Company which contains users who are allowed access to that particular floor (multiple Companies can be selected if needed).
  
  
  
  
• Users should be placed in groups which will later be granted access to particular floors.
  
  
  
  

Navigate to Access Rules and begin creating rules to define which zones or floors each group may access. For example, the group ‘Company A Sales Team’  can be paired with the zone ‘first floor’ to allow the users of that group access to the first floor.

• • Enable lift control usage in added devices in the device details page in Access Commander.
    
    

    If you add to Access Commander device with lift control license, it will become automatically enabled for Lift Control)

  • To finally setup which users can access which floor, in device details go to Management and create Floor assignment according to the physical connection of relays between AXIS A9188 and the lift itself (for example relay io_1_1 on AXIS A9188 is physically connected to lift that 1st floor will become available for Groups of users which have in Access rules defined rules for Zone 1st floor).

    Since up to 8 AXIS A9188 can be connected, you need to know which relay belongs to which AXIS A9188 I/O Relay Module:

    io_1_1 in Floor list stands for first connected AXIS A9188 to 2N unit and its first relay

    io_1_2 in Floor list stands for first connected AXIS A9188 to 2N unit and its second relay

    io_2_1 in Floor list stands for second connected AXIS A9188 to 2N unit and its first relay

    etc...

    • 
      
      
      
      
      From now all users, which are part of Groups associated in Access rules with Zone 1st floor and have valid credentials, when they authorize on 2N IP unit in lift cabin will be able to use lift button for 1st floor.

    (Optional) Setup floor to allow access to anyone who presses the lift floor button
    

    • In order to allow access to floor without the need to authorize person using an RFID card, in device details go to Management and create Floor assignment according to the physical connection of relay between AXIS A9188 and lift itself (for example relay io_1_2 on AXIS A9188 is physically connected to lift which 2nd floor will become available for anyone who just presses a 2nd-floor button in the lift).
      
      
      
      
      
      From now, anyone who presses the button for 2nd floor will be able to access that floor.

      Optionally, Time profile can be set, which will restrict access to that floor for desired time frames.

      If none of the Time profiles is used it means 24/7 allowed access.

IP Intercom/Answering unit lift setup

The setup is quite easy once you finished all the previous steps in this guide.

You can create a user that will stand in for your 2N OS based answering unit – in this example, we’re using several 2N® Indoor View units. Name these users according to your preferences, we named them Apartment 101 – 2N Indoor View etc.

• Make sure each user residing on the 1st floor is assigned to a group that has access to this floor – in our case, it’s 1st floor group as shown a few steps before in Access Rules.

• Now go to devices and open device detail of an intercom and configure its quick dial buttons or touch display to call all users and devices in e.g. Apartment 101:

• Now that this is ready, go to the intercom’s web interface via Configure Device.

Switch for lift control

Activate the switch by entering DTMF (activation code) and therefore send the following HTTP request. Replace the values in red with your own values:

https://LiftDeviceIP/api/lift/grantaccess?user=$CallUuid$&duration=seconds

https://127.0.0.1/api/lift/grantaccess?user=$CallUuid$&duration=5 (example)

*LiftDevice = either 127.0.0.1 (if the very same device is controlling the lift) or some other device (where the Axis relay is connected)

The HTTP request uses LIFT API that’s part of I/O API of the 2N device in the lift that controls the Axis A9188 relay module.

IP Intercom

• Create a floor by giving it a name (for better orientation)
• Choose wheter or not the floor should be publicly accessible and if any time profile should be applied

• Fill in the API command in the switch-on (127.0.0.1 is used because the AXIS relay is connected to this Verso, if it was a different device, then you would fill in the IP address of that device instead).

Authentication matches HTTP API authentication (see below).

https://LiftDeviceIP/api/lift/grantaccess?user=$CallUuid$&duration=seconds

https://127.0.0.1/api/lift/grantaccess?user=$CallUuid$&duration=5 (example)

*LiftDevice = either 127.0.0.1 (if the very same device is controlling the lift) or some other device (where the Axis relay is connected)

• Set up an HTTP API account for Access Control API and fill in the authentication (matching the authentication in the switch HTTP command).

• Create a user to be called (Indoor View in our case)

• Lastly, give the user a PIN code for the LIFT control switch (switch 2 in our case) and assign it a floor

2N OS answering unit setup

This setting is identical for 2NOS only and Access Commander included.

To configure a 2N OS answering unit, access the web interface of the unit. This unit needs to have devices corresponding with phone numbers of intercoms that are going to call it, in this example we’re using device:Verso, but you can use other syntaxes depending on network setup. Add a new device or edit an existing one.

The last step is to set up Unlock Buttons – as you can see, we set up separate ones for door control and lift control. If LIFT is checked, its icon will change to make it easier to differentiate between the two.

Once this Main entrance – 2N IP Verso device (whose device name is Verso) calls the Apartment 101 – 2N Indoor View user, the 2N® Indoor View recognizes it and shows the appropriate unlock buttons.

Tapping either of these will either open the door or start the lift action and send the HTTP request to the 2N device in the lift which then enables the appropriate buttons on the lift control panel via the Axis A9188.

It’s important to note that 2N® Access Commander serves as a synchronization server to make sure that the $CallUuid$ of the called user/device corresponds with the Uuid of a user in the 2N device that manages the lift. As this is an additional feature, you may still use this 2N device to enable lift buttons directly e.g. via Bluetooth or RFID.

2N^® Mobile Video setup

Configuration of 2N^® Mobile Video is described in this Video – 2N^® Mobile Video: registration and setup or here: Switch codes – How to unlock the door?

2N^® IP Handset setup

Configuration of 2N^® IP Handset's call features and switch codes is described here: Direct call – How to set up a 2N^® IP Handset for a direct SIP call (without PBX) and how to open door

2N^® Indoor Touch 2.0 setup

Configuration of 2N^® Indoor Touch 2.0 is described in this Video – Setting up calls between 2N^® Indoor Touch 2.0 and 2N IP intercoms or here: How to set up calls from/to 2N IP intercoms?

Last update

• 2022-10-24

Devices used

• 2N^® IP Verso
• 2N Access Unit 2.0
• 2N^® Indoor View
• AXIS A9188-VE Network I/O Relay Module

Licenses required

• Gold license (For IP intercoms)
• Lift Module – only for the device that controls the lift

Compatible 2N intercoms for calls and lift control

• 2N^® IP Style
• 2N^® IP Verso
• 2N^® IP Force
• 2N^® IP Safety
• 2N^® IP Vario

Compatible 2N devices for lift control

• 2N^® IP Style
• 2N^® IP Verso
• 2N^® IP Force
• 2N^® IP Safety
• 2N^® IP Vario
• 2N Access Unit 1.0
• 2N Access Unit 2.0
• 2N Access Unit M

Compatible 2N answering units

• 2N^® Indoor View
• 2N^® Indoor Compact
• 2N^® Indoor Talk
• 2N^® Mobile Video
• 2N^® IP Handset
• 2N^® Indoor Touch
• 2N^® Indoor Touch 2.0