...

Technical Manual | TM-20210309-TP-22 iProtect Access / Security | Coupling | iProtect™ Elevator integration Image Modified

View file name TM-20210309-TP-22.pdf

This manual represents the knowledge at the above-mentioned time. TKH security works non-stop to improve her products. For the most recent technical information please contact your consultant or dealer.

...

Introduction 1

...

This document describes outlines the Elevator service in iProtect. It explains within iProtect, detailing its purpose and how it should be
configuredconfiguration. Currently, this integration is available for compatible with the DOAS Mitsubishi Lift system.

1.1 Short

...

Explanation

The TKH security iProtect integration with elevators control systems adds higher enhances the security and destination
control to the of elevators in your building. The integration means that you can restrict This system allows for restricted access to elevators and
specific floors for cardholders via , governed by time schedules and access rights.

For example: instance, a user can may be assigned granted access only to only the ground floor and the 12th floor from 07:30 till to 19:00
hour.

The operation is such that straightforward: cardholders swipe their card cards on the elevator reader that is present located in the so called
elevator call unit. The elevator call unit in turn then displays only shows the available floors accessible to the user, or the user can only enter the
floor numbers , to which the user is also entitled. (they are entitled, depending on the type of call unit). In this integration, the iProtect software sends a command commands directly from the server to the elevator controller
over via the IP network. This replaces the conventional , replacing the traditional relay method of using relays for the connection.

The purpose of the elevator link is to send transmit a command to the elevator controller when the following conditions are met:
a: access is granted (based on the normal standard access rights)
b: the person individual has rights the right to travel with use the elevator
c: the reader has a call location and a known recognized ID for the elevator controller

If all these conditions are truesatisfied, a message is send sent to the elevator controller.

...

1.4 Communication

Communication when presenting When Presenting a cardCard:
When a card is presented to a reader that is related to associated with a call location (and provided access is granted), a message
is send sent to the Elevator Service containing to indicating which node manager (Pluto) and reader a the card is has been presented to.
The Elevator Service will gather extra then gathers additional information based on the call location (related linked to the reader) and the
floor group (related to associated with the card).
With this information, a Call Request is created generated and is sent dispatched to the Elevator Device.

If the request is handled by the Elevator Device processes the request, it sends a message is send back to the Elevator Service
(containing , which includes details about the elevator car that is used) in use, or an error message if something goes wrong.
This message is sent an issue arises. This response is relayed back to the node manager. There , where an event is created that an to indicate whether the elevator call was
successful or not, and this information is send sent to the iProtect Server.

Communication for communication stateState Monitoring:
Each node manager that has with a reader that is related linked to a call location will send heart beat transmits heartbeat messages every
60 seconds. It contains , detailing which readers are functioning properlyoperating correctly.
The Elevator Device is informed if notified about the operational status of the access control system (iProtect). If the system is not functioning properly or not.
If not, the Elevator Device may be set in enter calamity mode. The

Additionally, the Elevator Device may also send heart beats heartbeat messages to the Elevator Service to inform iProtect it’s connection
state. This connection state will be sent communicate its connection status, which is subsequently relayed to the iProtect Server.

...

2 Elevator Service setup

2.1 License

To activate the iProtect Elevator service a special license is required:
· License number 1800: Smart Elevator control

2.2 Configuration

A To create a new Elevator synchronization service can be created in , navigate to the Database Link form which is available via the
through the following menu selection:
Installation | Settings | Database Link.

You can To add a new Database Link by pressing the right mouse button , right-click in the tree view panel and selecting
select Add database link.

In the Database link Link details form you select <Elevator call service> as database type and the details of this
service appear.With the mandatory Name and Elevator type parameter you give this service a unique name and select the
, choose Elevator call service as the database type, which will display the relevant details for this service.

You must provide a unique name for the service in the mandatory Name field and select the appropriate Elevator type parameter, specifying the manufacturer/type interface.

Other Additional settings depend will vary based on the selected elevator typevtype.

2.3 Status

With the Active checkbox the elevator service can be started and stopped.

...

3.1 General Mitsubishi

iProtect has an integration seamlessly integrates with the DOAS Mitsubishi Lift system . through the ELSGW (Elevator Secure Gateway)
. Mitsubishi Electric’s DOAS system optimizes enhances the efficiency of multi-car elevator systems by intelligently allocating cars efficiently
according to based on the floors that passengers input select while waiting in the hall /lobby, helping to reduce both wait and
travel times. The integration means that you can restrict access for a the person via time schedules and
floors increasing security and efficiency of movement around the building.The implementation support a number of features like
· VIP traveling
· Management traveling
· Handicaped function (also called disabled)
· or lobby. This optimization significantly reduces both wait and travel times.

This integration allows for enhanced security and movement efficiency within the building by enabling access restrictions based on time schedules and specific floors.

The implementation supports a variety of features, including:

• VIP traveling

• Management traveling

• Handicapped function (also referred to as disabled)

• Non-stop calls

...

• Elevator lobby calls

...

• Entrance calls

...

• Room calls

3.1.1 Security gate calls ELSGW version

...

3.2 Service

The elevator service has the following operates under specific parameters for the communication with the Nodemangers Node Managers (e.g., Pluto):
The service makes use off . This service utilizes the same certificate that is used employed for the user interface.

• IP address or hostname iProtect: The IP address of the iProtect server who communicate with the
  Pluto(’s)

• Port :
  o Default: <443>

• Use SSL: Checkbox determines whether SSL is used to encrypt the communication between the Pluto
  and iProtect.
  o default: <yes>

• Allow self-signed: client allow self-signed certificate
  o default: <yes>

• Allow insecure: client allow insecure server
  o default <yes>

• Allow expired: do not check the expire date of the certificate.
  o Default: <yes>

• Skip Server Cert: client skip server certificate hostname check
  o Default: <yes>client skip server certificate hostname check
  o Default: <yes>

3.3 Remote server

The parameters in this panel determine what and how the connection is made with the ELSG controller.

...

4.2.1 Elevator floor group

Here we define outline the elevator floor groups.
Floor groups consists consist of 1 one or more floors and those can be on associated with multiple elevators elevator groups.
A Additionally, a floor group can may be linked to a person, see ; refer to chapter 5 for more details.

Access | Settings | Floor group

...

By language: use a logical name for the Elevator floor group for example:
EG1 all > Elevator group 1 all floors
EG1,2 all > Elevator group 1&2 all floors
EG1 -2,-1,0,1,2,3,4,5,6 > Elevator group 1_floor -2 till 6
TKH > all floors for the company TKH

4.2.1.1 Adding a

...

Floor to the

...

Floor Group

When a floor group is created, you are able have the option to add or change modify floors to this within that group.
Double To do this, double-click on the name in the tree view , and select <Elevator group floor list>.
In the detail screen select , choose the floors you want wish to add and save your settings.

4.2.1.2 Adding a

...

Timezone to the

...

Floor

You can assign a separate timezone for each floor in the group a separate timezone , this . This timezone setting is applies only valid for to the specific group in which the setting it is madeconfigured.

Double-click on the < Elevator <Elevator group floor list > list> item in the tree view.
All linked floors are will now be visible in the tree view.
Select the floor for which you want to add a timezone
Select you .
Then, choose your desired timezone in the detail screen.

4.2.2 Call type

A call type is a feature that is dependent on the elevator manufacturer.
These features can be linked to a person, see chapter 5.

...

By language: use a logical name for the call location for example
CL_EG1_0F_lobby
CL_EG1_CAR 1

4.2.4 Reader

For the card reader, an extra An additional field has been added to incorporated into the Other tab , of the card reader specifically for elevator calls.

When a utilizing the card reader is in use for elevator calls access, the LED response of the led on the reader is different.
The response of the reader after badging device varies. Here’s what to expect after presenting a valid card:· slow

• Slow blinking: The reader is waiting for a response

...

• from the elevator controller (ELSGW).

...

• Continuous green light during relay time: The elevator request

...

• has been successfully processed.

• Fast blinking: Access denied; the elevator request has failed (typically after a waiting period of 30 seconds).

Installation | Hardware | Reader

...

For maintenance and installation of the elevator functionality there is a specific status overview available to
check all the connections.

...

This overview shows the status for all card readers that are involved with elevator calls
The following items are shown for each reader

6.2 Specific events

• Webserver disconnected => connection: <nr>, Process: Elevator call service, Database link:
  <name>
  o Connection is lost with the elevator controller

• Webserver connected => connection: <nr>, Process: Elevator call service, Database link: <name>
  o Connection is established, elevator commands can be given

• Elevator call => Reader:<name>, Card: <number> ..
  o No error message
  § Correct elevator call
  o Error: No floor group for elevator request
  § Person has elevator rights but not for this elevator group
  o Error: Elevator service internal error for elevator request
  § If this message appear after approx. 30 seconds there is no feedback from the
  ELSGW. The message is send but the ELSGW cannot proceed with it. Probably due
  a wrong configuration like:
  · an unknown floor number is used by the call location
  · No or wrong <code> used by the card reader (see chapter reader)
  · Elevator group is not active in elevator controller (wrong or in inactive bank)
  · Elevator line status => Line: <name>,
  o Error: OK
  § This line is now OK

...

6.3 ELSGW terminal option

Important noteNote:
Use Please use this tool only in consultation with and in the presence of Mitsubishi.

The ELSGW controller has an option to login by allows you to log in using PuTTY as the terminal software.
With this terminal software it is possible to configurate This software not only enables configuration of the ELSGW but also there are some provides several helpful commands to check the status and communication.

Default Settings:

• IP

...

• Address: 192.168.0.1 (the same IP

...

• used for communication with iProtect)

• Port

...

• Number: 52173

• Protocol: TCP/IP

PuTTY settings: Settings (different as from default):

• Connection

...

• Type: Raw

• Terminal

...

• :

  • Local Echo: Force off

...

• • Local

...

• • Line Editing: Force off

...

• Keyboard:

...

• • Backspace

...

• • Key: Control-H

Some useful commandsUseful Commands:·

• IPCONFIG

...

• INFO?

...

• ELCON?

...

• PKT?

...

• AC?

...

• TRACE?

...

• SNET?

...

• ADRIP?

...

• ADRIP=X.X.X.X (

...

• the returned IP address must

...

• match the iProtect IP address)