Content Comparison

...

Technical Manual | TM-20210309-TP-22 iProtect Access / Security | Coupling | 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.

...

The TKH security iProtect integration with elevators control systems adds higher security and destination
control to the elevators in your building. The integration means that you can restrict access to elevators and
floors for cardholders via time schedules and access rights.

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

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

...

Other settings depend on the selected elevator typevtype

2.3 Status

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

...

The implementation support a number of features like
· VIP traveling
· Management traveling
· Handicaped Handicapped function (also called disabled)
· Non-stop calls
· Elevator lobby calls
· Entrance calls
· Room calls

...

• 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>

3.3 Remote server

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

...

For maintenance and installation of the elevator functionality there is a specific status overview available to
check all the connections.
Installation | Overview | Status | Reader-Elevator
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

...