0% found this document useful (0 votes)
222 views71 pages

TM PTE 01 - General

Uploaded by

Faheem Mirza
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
222 views71 pages

TM PTE 01 - General

Uploaded by

Faheem Mirza
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 71

The PORT Technology - Technical Documents

TM PTE 01 - General
Basic Information on PORT Technology Elevator System

Document Number : EJ 41905010

Document Version : 07

Release Date : 06.06.2015

KA Number : 153396

Software Version : V1.2.353.1

Author : Sylvia Helfenstein

Reviewer : Christian Sprenger

Releaser : Paul Friedli

Lead Office : EB9.

Copyright © 2015 INVENTIO AG All rights reserved.


1. Index
1. Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Fundamentals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. PORT Technology Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Coordinate System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3. Task Identification Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.4. User Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.5. Software Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.6. Main Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.7. Setup Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4. Installation and Commissioning Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.1. Software Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.2. Order Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.3. Registration Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.4. Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.5. Adding of Login Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.6. Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.7. Commissioning Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5. Initial Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1. Tasks on PTG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.2. Tasks on PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
6. Building Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.1. Commission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
7. Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.1. Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.2. Windows Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.3. LON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
8. Jobmanager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
8.1. Creating of Jobmanager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
8.2. Basic Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
9. Group Traffic Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
9.1. Creating of Group Traffic Manager on PTG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
9.2. Creating of Group Traffic Manager on PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
9.3. Basic Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
10. Doors and Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
10.1. Internal PC Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
11. SOMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
11.1. Creating of SOM Task on PTG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
11.2. Creating of SOM Task on PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
11.3. Importing of SOMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
12. Install Expert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
13. Overview Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
14. I/O Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
15. Internal Supervisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
15.1. Opening of Supervisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
15.2. Opening of SMS Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
16. Logger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
16.1. Creating of Logger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
17. Updating of of PORT Technology Software and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
17.1. Update Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
17.2. Search Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
17.3. Update Tool Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
17.4. Software Status on Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
17.5. Updating of Software on Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
17.6. Update Tool Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
18. Lobby Vision / e-Vision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
18.1. Creating of Lobby Vision Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
18.2. Lobby Vision Task Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
19. PORT Technology Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
20. Extended Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

EJ_41905010_07 TM PTE 01 - General


Page 2 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
PORT Technology may also be referred to as:
TM PTE 01 for PORT Technology Elevator
TM PTA 01 for PORT Technology Access
TM PTN 01 for PORT Technology Network
TM PTO 01 for PORT Technology Options.

Copyright © 2015 INVENTIO AG All rights reserved. INVENTIO AG, Seestrasse 55, CH-6052 Hergiswil, owns and retains all copyrights
and other intellectual property rights in this manual. It shall only be used by SCHINDLER personnel or authorized SCHINDLER agents for
purposes which are in the interest of SCHINDLER. Any reproduction, translation, copying or storing in data processing units in any form or by
any means without prior permission of INVENTIO AG is regarded as infringement and will be prosecuted.

EJ_41905010_07 TM PTE 01 - General


Page 3 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
2. About this Manual
This manual provides:
The fundamentals of PORT Technology
A main description of tasks and devices
Basic information on the installation and commissioning procedure.

This document is a brief description of everything for beginners of PORT Technology and can be used as a reference document for main
topics. The information given in this document does not go into deep detail.

These tasks are carried out by an Expert.

EJ_41905010_07 TM PTE 01 - General


Page 4 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
3. Fundamentals
3.1. PORT Technology Concept
There is no control function like a group controller. Each transport medium (each elevator) has its own job manager acting as a selling unit of
its own transport capacity. Requirement handlers (for example terminals), as representative of a passengers requirement, send an offer
request to all job managers able to fulfill the demand. All job managers send an offer back. The terminal then ends an order to the job
manager with the best offer.

All PORT Technology modules are "plug and play" devices and, as far as possible, self configuring. They have so called "position property",
which defines their geographical position in the building by x-and y-coordinates (in meters, horizontally, starting at the building zero point), the
floor (vertically) and the zone (a two to three dimensional limited area with the same access restrictions).

All PORT Technology components are connected to the PORT Technology network (main PORT Technology nets are LON and Ethernet).
With the physical connection to the network, the installation is done and no further drivers must be installed. Other, not PORT Technology
compatible components need, at minimum, a software driver to make it compatible to PORT Technology. In most cases, a special hardware
is also needed.

EJ_41905010_07 TM PTE 01 - General


Page 5 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
3.2. Coordinate System
PORT Technology uses the position properties to calculate the walking time from terminals to elevators, or to define the arrow on the display
to show the direction to walk to the assigned elevator door.

Each PORT Technology component is physically positioned within a building by means of five properties:

X-coordinate (0 ... 255 meters)


Y-coordinate (0 ... 255 meters)
Orientation
Floor number (floor -50 ... 205.) Floor number 50 = Ground floor (0)
Zone (0 ... 255).

Unit
The unit of measure for X and Y coordinates is meters [m].

The definition of these five properties is an important part of the (on-site) configuration process and is normally done immediately after
connecting the device to the network.

Terminal Position (orientation)

The terminal position is entered as x-y coordinates within the building coordinate system. The orientation is
entered at the terminal or with the visual configuration. It has the following contents:

X>: In x direction
Y^: In y direction
<X: x opposite direction
vY: y opposite direction.

Elevator Position

The elevators x-y position is measured at the center of the front door. The orientation is the direction entering
the front door.

The position and orientation is entered at the Job managers tabs. It is also configured within the visual
configuration.

EJ_41905010_07 TM PTE 01 - General


Page 6 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
Example

The origin is 0, 0.
Terminal T1: X=4, Y=8, Orientation Y^
Terminal T2: X=13; Y=8, Orientation Y^
Terminal T3: X=15, Y=3, Orientation X>
Elevator A: X=5, Y=10, Orientation Y^
Elevator B: X=8, Y=10, Orientation Y^
Elevator C: X=12, Y=10, Orientation Y^
Main Database: X=12, Y=18

Maximum Values
The maximum value for X and Y is 255 [m] (0 ... 255).
The maximum number of floors is 255 (-50 ... 205).

EJ_41905010_07 TM PTE 01 - General


Page 7 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
3.3. Task Identification Overview
Each PORT Technology module in the system has a task identification (TID) consisting of four bytes.
Byte 1: Module type
Byte 2 ... 4: Depending on the first byte.

PORT Technology Component TID Byte TID Byte 2 TID Byte 3 TID Byte 4
1

Terminal (Local) 1 Floor (+50) X-coordinate Y-coordinate

Job Manager 2 Car number (first car) Car number (last car) [1...] 0 = Master (+64 = backup)
[1...]
(mainly same as byte 2)

Drive 3 Car number [1...] 0 0 = Master (+64 = backup)

Door 4 Car number [1...] Door side [1 ... 4] Deck [1...]+ (+64 = backup)

Dest. Indicator HW in Car 5 Car number [1...] Door side[1 ... 4] (+16 = Deck number [1...]
2nd)

Deck 6 Car number [1...] Deck number [1...] 0

Load Measure Module 7 Car number [1...] Deck number [1...] 0

Lock Handler 8 Building number Floor (+50) Number

Position Display on Floor 9 Car number [1...] Floor (+50) Door side [1 ... 4]

Dumb Terminal 10 Floor (+50) X-coordinate Y-coordinate

TAG Reader 11 Floor (+50) X-coordinate Y-coordinate

Visitor Control 12 Floor (+50) X-coordinate Y-coordinate

Apartment 14 Building number Floor (+50) Number

LON Destination Indicator on 15 Car number [1...] 0 0 = Master (+6 4= backup)


Floor

RS-485 Destination Indicator on 15 0 Group number 0 = Master (+64 = backup)


...

Destination Indicator in Car 16 Car number [1...] Door side [1 ... 4] Deck number [1...]+ (+64 =
Backup)

Annunciator 17 Car number [1...] Lowest floor (+50) Side [1 ... 4]

Designation Plate 18 Car number [1...] 0 0


Controller

I/O-Board HW 40 Building number X-coordinate Y-coordinate

ZigBee Handler 51 Building number Floor (+50) Number

Escalator Interf. 55 Building number Upper floor (+50) Number

Shuttle Manager 75 Number 0 0

I/O Board Shuttle Manager 75 Number 1 0

Evacuation Manager 76 Number 0 Priority

Parking Manager 78 Car 0 Priority

EJ_41905010_07 TM PTE 01 - General


Page 8 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
Lobby Interface 79 Lowest car [1...] Highest car [1...] 0 = Master (+64 = backup)

External SID Supervisor 81 - - -

SOM-Handler 82 1 Building number (PTG Drive-) number

E-Vision Interface 83 Car number [1...] Group number [1...] 0

New Lobby Interface 84 Lowest car [1...] Highest car [1...] 0 = Master (+64 = backup)

Autocall 91 0 0 0 = Master (+64 = backup)

Logger 92 Building number 0 Number

Statistics Recorder 93 Car number [1...] 0 0

Arcnet & TX-4 Server 99 Lowest car [1...] Highest car [1...] 0 = Master (+64 = backup)

Backup Database (local) 102 1 1 Backup number >=2

PT-Config (internal) 111 X-position Y-position 0

Overview Proxy 123 Building number 0 Number

Terminal (Global) 129 Floor (+50) X-coordinate Y-coordinate

User Configuration Window 200 - - -

Overview Window 201 10 Building number Number

Traffic Simulator 201 11 - -

Visual IRON others 202 - - -

XML converter 205 - - -

Supervisor 208 0 0 Priority

External Call Manager 211 X-position Y-position Number

OneID 217 Car number [1...] 0 0

Logger (global) 220 Building number 0 Number

SMS Server 221 0 0 0 = Master (+64 = backup)

Database Importer 222 1 1 Number

PORT Authority 223 0 0 Number

Crowd Prevention 224 Number 0 0

Master Database (global) 230 1 1 0

Backup Database (global) 230 1 1 1

PTG 239 X-coordinate Y-coordinate 0

Module Manager 240 - - -

Time Server 250 0 0 = PC, 1 = PTG Priority

[...] variable value (...) specific value

The Task-ID must be unique within the system. It is not allowed to have two tasks with the same identification!

EJ_41905010_07 TM PTE 01 - General


Page 9 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
3.4. User Levels

Expert Trained Schindler Technician Supermaster


+ can add/edit Supermaster
+ can change the building layout
+ can change the System configuration

Supermaster Building management Master


+ can add/edit Masters
+ can edit the building behavior (Time Patterns, Zone Access…)

Master Tenant/HR representative User


+ can unlock a programming station
+ can add/edit users

User Everyone who works/lives in the building Can use the lift(s)

Description User Master Supermaster Expert

User of PORT Technology

Edit / Add User within Group

Define Zones, Time Patterns, Access Zones, Master Groups, Masters

Edit / Add Supermaster Names

Configure Networks, Elevators, Elevator Groups, Door

3.5. Software Overview


The PORT Technology software contains six main menus and several sub-menus.
This section describes the first two menu levels.

Name of Tab User Master Supermaster Expert

Users / Building

Users

Card Reader

Site Info

User Groups / Building

Locations

Master Groups

Time Patters

EJ_41905010_07 TM PTE 01 - General


Page 10 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
Zones and Zone access

Transfer Rules

Lifts

Languages

Network, Elevators, Tools

Visual Configuration

Overview 1) 1)

Close Program 1)

1) If applicable

3.5.1. Network Elevator Tools


Within Network, Elevators, Tools, you can add and delete any task which should run on this particular PC. It is the so called Module
Manager.

View Description

Display of the PC/PTG you are currently working on to see and create tasks or select a different device/PC to
see/modify the configuration.

The configuration of PTG/PTDB/PTDBS can only be seen but not changed.

Display of task categories

To open a submenu, double-click a category.

Sub-categories Display of task sub categories

TID / Description When double-clicking a main category or sub-category, the corresponding tasks created are displayed.

EJ_41905010_07 TM PTE 01 - General


Page 11 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
This section includes:

Diagnostic tools
Network tools
General explanations.

Quick selection to the tools list

Quick selection to start new task

Erasing of selected task

Additional information on the task

Additional detailed information on the task

Display of duplicated TIDs.

The main categories and sub-categories marked in black (instead of gray) contain a task.

3.5.2. Visual Configuration


The visual configuration gives an overview about the installed PORT Technology modules in a graphical manner and allows to configure
various parameters for the devices.

If no user configuration window has been created yet:

The visual configuration is not available and the Visual Configuration button is disabled.

1. Click Visual Configuration.

The elevator arrangement is displayed, showing the placement of each


component.

Pos. Description

Top The tabs indicate the available floors.


"Any" is selected by default, displaying all devices/task on all the floors.
If a floor is selected, only the devices/tasks configured on this particular floor are displayed.

EJ_41905010_07 TM PTE 01 - General


Page 12 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
Left OK: Closes the Visual Configuration.
Launch Install Expert: Starts the Install Expert.
The list displays all TIDs where there is communication to. If you click a TID, the details of the selected device/task are
displayed.
Buildings tab: Displays all Buildings configured. You can filter to display the devices/tasks for one building only.
Devices tab: Filter to for example display Jobmanagers or Terminals only.

Right SOM: Opens the SOMs configured in the database.


CFG: Opens the stored configuration files (xml) from the database.
OVR: Opens the "Custom Overview" Editor.
Port: Opens the special PORT configuration.
I/O: Opens the configuration of IO Boards/Modules.
OPT: Opens the Product Options tool.

Center On the left hand side and at the bottom, the X (horizontal) and Y (vertical) axis are displayed. The numbers identify the TID,
each dot (number) represents one meter.

The maximum value for X and Y is 255.

Before configuring the installation, check the "0" point of origin is somewhere located on a building corner because negative
numbers are NOT possible.
As soon as you double click a device/task, the configuration window of the corresponding device/task opens.

3.6. Main Tasks

3.6.1. Database
In Visual Configuration, click one of the database icons.

TID Icon Description

230.1.1.0 Master database (global)

230.1.1.1 Backup database (global)

102.1.1.n Backup database (local)


n indicates to the PTG/PC where the task is running

The following window opens:

EJ_41905010_07 TM PTE 01 - General


Page 13 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
Tab Description
Status Check of database status

ID Levels Details on access identification

Parameters Details on database positioning

Forward Credential Enabling or disabling the verification of credentials in the database

3.6.2. Jobmanager
In Visual Configuration, click the Jobmanager icon.

The following window opens.

Tab Description
Position Coordinates Positioning the Jobmanager in Visual Config.

EJ_41905010_07 TM PTE 01 - General


Page 14 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
Planner Specify data about:

Space in Car
Car Load
Preselector
Activity
Checks
Door/Transfer Times
Maximum Waiting Time
Maximum intermidiate Stops
Load
Allocation closing door.

Allocation Status Enable or disable allocations.

Trip Table Shows the Trip Table.

Floor Settings Determine a Call Limit and an additional Transfer Time for each floor.

Transfer Enable or disable transfers between groups.

Special Special configuration for jobmanager.

3.6.3. Terminals
The following terminal types are available:

PORT Z-Line Touch Terminal Visitor Control Simulated Terminal

Information

TID Symbol

1.floor.x.y

For all terminal types, most of the configuration is identical or similar.


The additional settings for Touch Terminal or Visitor Control are described seperatly.

3.6.4. Timeserver

Displays the status of the timeserver Running or Not Running.

EJ_41905010_07 TM PTE 01 - General


Page 15 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
3.7. Setup Rules

3.7.1. Database
Depending on the amount of users/cards, the master database is on a PTG or on a PTDB.

Number of Cards Location of Master Database Location of Backup Database

< 2.000 PTG2 PTG2

< 10.000 PTDB PTG2 or PTDB

< 32.000 PTDBS PTDB or PTDBS

Example 1
Your installation has 1220 users/cards.

Master database: On PTG


Backup database: On PTG.

Example 2
Your installation has 3507 users/cards.

Master database: On PTDB


Backup database: On PTG.

EJ_41905010_07 TM PTE 01 - General


Page 16 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
Example 3
Your installation has 18560 users/cards.

Master database: On PTDBS


Backup database: On PTDB.

You must not have any database on a PTG!

The databases can always be installed on a device with higher capacity.


For example, installation with 1600 cards/users:
- Master database: On PTDB or PTDBS
- Backup database: On PTG.

EJ_41905010_07 TM PTE 01 - General


Page 17 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
4. Installation and Commissioning Overview
4.1. Software Registration
When you start the Core software the very first time, the system asks for a registration number.

4.2. Order Number


To obtain the licence (registration number), an order number is required.

The license (registration number) can be obtained from your TMCC, sending the registration request form (or TMG if no TCCC
applies).

4.3. Registration Number

1. Type the registration number into the corresponding field.


2. Click Register.

A registration confirmation is displayed (OK or not OK).


The EXPERT password for the initial login is displayed.

1. Write down the EXPERT password. Keep the EXPERT password in a safe place!

Do not Lose the EXPERT Password


If you lose the EXPERTpassword and have no other login available:
You will not be able to log in anymore.
You will have to re-register to obtain a new initial password.
Keep the EXPERT password in a safe place. With the EXPERT password,
you have full access to the program!

1. As soon as you have logged in the very first time, create a new Expert user for your login.

With the new Expert user, the first login is not needed any longer.

EJ_41905010_07 TM PTE 01 - General


Page 18 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
4.4. Login

After first installation and registration of the Core software, you have to login with the Expert password provided to be able to make
any configuration.
The same applies if you have lost your login password or the card reader is defective

1. Press and hold "CTRL"-"ALT"-"Shift"-keys (all at the same time).


2. Click Program locked with the left mouse button.
3. When the login window is displayed, release the keys.
4. Username: Type EXPERT.
5. Password: Type the EXPERT password provided during registration.

If you have lost the EXPERT password, re-registration is required. If this is the case,
delete the license file and restart the programm.

4.5. Adding of Login Users

Only Expert users can create new login users.


New logins should only be created for trained Schindler employees.
Each Schindler employee should have his own credentials. After first login, the Schindler employee can change his
password.

Keep in mind
The software is set up for password login.

Whenever possible, do not use the password login. Use cards instead.
Never use the password login on programming stations. Always use cards.

To create a login user:

1. Press and hold Alt+Ctrl+Shift and click the PORT Technology logo.
2. Click New.
3. Add the user credentials with the corresponding level of access.

Do not use an easily guessable password such as "1234", "schindler", etc.

EJ_41905010_07 TM PTE 01 - General


Page 19 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
4.6. Installation Steps

The installation steps described in in this section are for reference only. Some steps may be skipped, some steps may be added.

Step Remark

1 Install the main switch box (MSB) in the machine room. The MSB is the network-heart of the system.

2 Connect every existing controller through its interface to For details, see the document PTE - Underlayer.
the PTGs and connect them to the MSB.

3 Install the terminal riser including the terminals. Connect For redundancy, minimum two risers are recommended.
the terminal riser to the MSB.

4 Install the destination indicator (DI) for each car and door Minimum one destination indicator is required per car.
side.

5 Install the designation plates. Each elevator must be clearly identified (A, B, C, etc.) for the
passengers.

6 Install the annunciators on the floor and in the car. One annunciator print (ANN) has four channels and can handle
Connect the annunciators to the system. maximum four designation plates of the same elevator.

7 Install the programming station. Connect the programming -


station to the MSB.

4.7. Commissioning Steps

We distinguish between commissioning of the PTCore Software and of the system itself (jobsite).
The commissioning steps described in this section refer to the commissioning of the system (jobsite) only.

Step Remark

1 Start the PORT Technology application (PTCore). Log in as Expert. If no programming station is used in the building, use
your service laptop.

2 Start the master and backup database on the PTG or the PTDB. For details, see chapter Initial Settings.

3 Setup the building configuration with all necessary information. For details, see PTE - Supermaster Manual.

4 Setup the network connection driver for communication. For details, see chapter Network.

5 Start the job managers on the PTGs with the corresponding controller For details, see PTE - Underlayer.
interface.

6 Start all other necessary tasks, for example SOM Handler, LobbyVision For details, see the corresponding chapter.
Interface, Statistics Recorder, etc.

7 Perform a final check with the Install Expert. For details, see chapter Install Expert.

EJ_41905010_07 TM PTE 01 - General


Page 20 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
5. Initial Settings

The tasks described in this chapter are essential. Other tasks may be added optionally.

With oneiD, the tasks described in this chapter are not required. For details, see the document PTE - oneID.

5.1. Tasks on PTG

5.1.1. Database
1. In Visual Configuration, click the first PTG, PTDB or PTDBS.

Parameter Description
SID-Number Unique number, consecutively numbered (1 ... 254), reflecting the Jobmanager (elevator) number

Host Name Name of the device

X-Position Position on the X-coordinate

Y-Position Position on the Y-coordinate

1. Click System.
2. Start the Master database.

EJ_41905010_07 TM PTE 01 - General


Page 21 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
Parameter Description
Database Select the Database check box to define the database.

Number 0: Master database


For backup database, use the PTG number +10 (for example: PTG: 1, backup database: 11)

Master Select the Master check box to define the master database.

5.1.2. Jobmanager
1. In Visual Configuration, click the PTG to be configured.
2. Click Lift.
3. Select the Door/Drive check box. Select the corresponding interface.
4. Select the Jobmanager check box.
5. Click OK.
6. Repeat the procedure for each PTG.

1. In Visual Configuration, click the PTG to be configured.


2. Click Lift.

Parameter Description
Door / Drive Defining the door/drive type

Jobmanager Starting the jobmanager task

Group Traffic Manager Starting the Group Traffic Manager task

BIOP PRHs For PORT 2 (BIO terminals)

Statistics Recorder Activating the statistics recorder to obtain the required data for reporting

File Exchange Activating the file exchange to obtain the required data for reporting

LON Floor Display Activating the floor display

EJ_41905010_07 TM PTE 01 - General


Page 22 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
5.2. Tasks on PC

5.2.1. Time Server


1. Log on to the PORT Technology software as an Expert.
2. Click Network, Elevator, Tools.
3. Click System > Time Servers.
4. Click Create Time Server.
5. Repeat the procedure for any additional programming station.

The time server with the lowest TID is the "master" time server and synchronizes the time to its clients.
Check only one master time server is present.

Standard configuration of time server:

250.0.0.0 Programming station 1 (master)


250.0.0.102 Programming station 2
250.0.0.103 Programming station 3
Etc.

Time Server on PTG


On the PTG, the time server is created automatically. No additional action is required.
To synchronize time, a PC with the master time server task must still be running.

A standalone time server task is available for syncronizing time with non-PORT Technology PCs/devices (for
example LobbyVision, e-Vision, etc.).

5.2.2. User Configuration Window


1. Log on to the PORT Technology software as an Expert.
2. Click Network, Elevator, Tools.
3. Click User Administration > User Configuration.
4. Click Create User Configuration Window.
No more configurations are required.
5. Click Finish.

On a programming station, check the box This Schindler ID <PCName> is a programming station.
On a service PC, check the box This Schindler ID <PCName> is a programming station.

EJ_41905010_07 TM PTE 01 - General


Page 23 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
6. Building Configuration

This chapter includes only short information about the content of the most important building configurations.
Supermasters are allowed to do all configurations. Masters can only edit users within their group.
For details, see PTE - Supermaster Manual and PTE - Master User Manual.

Users/Building contains the configuration of the users and the installation which may include multiple buildings.

The Users/Building window has various tabs.


Depending on the access level, the number of available tabs may vary.

Tab Description

Users The user database contains all the information collected on the elevator system users. Users can either be people or objects
such as food trolleys and hospital beds. A user can have access rights, defined with predefined user profiles or individually.

A master can access the user database for the masters group assigned to him on order to enter or change data.

Card A connected Card Reader can be assigned here.


Reader

Site Info The site info can be entered to identify the PORT Technology installation. If there is a SMS message sent to a support
center, the site can be identified with this information.

Users User groups can be groups of people, or objects such as hospital beds or food trolleys. User groups are defined to prevent
Groups / members of certain groups from using the same elevator; for example visitors and a patient in a hospital bed. A user can be
Buildings assigned to several groups, and it is possible to prevent several other groups from traveling with him.

A site can include more than one building. This buildings can be handled with the building groups. It is important that at
least one building is defined.

Locations A location can be shown in the Visual Configuration Window. For Information only.

Master Master groups are used to limit a master’s access to the user data in the PORT Technology database. Masters can only
Groups view, enter and change data for the users in the one or more master groups assigned to them.

PORT Technology contains 64 master groups (group 0 to 63). Group 63 is reserved for Expert use and has to be always
named "Schindler", Group 62 is reserved for Supermaster use and has to be always named "Supermaster". All other groups
can be named individually.

To avoid confusion about different master groups, it is strongly recommended to give them clear recognizable names (for
example, company A, company B, hotel C), before they will be assigned to a master or Supermaster.

Time The time pattern is a set of time segments with a common reference that occur during the week. Examples of time patterns
Pattern are business hours, weekend, the time a certain zone is closed to traffic.

EJ_41905010_07 TM PTE 01 - General


Page 24 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
Zones and A zone is an area within a building with defined access rights. Users can have access rights to one or more zones.
Zone
Access A zone transfer is when a user moves from one zone to another. The level of identification required for a user to make a
transfer between specified zones is clearly defined. These identification levels form the basis of the security concept for a
building complex.

Zones are identified by their name or a number. The color can be chosen manually or automatically.

Standard is: One floor = one zone (with the same numbering as the floor).

Transfer Transfer rules define specific transfer conditions for groups or people. They can be defined for example for VIPs to allow a
Rules zone transfer that is normally prohibited or to allow disabled people to board always on floor 1 of a double deck car.

Lifts The elevators and number of floors can be defined by "Lifts". There are several possibilities, to enter doors, floors and to
define entries for every level.

All Lifts within the whole installation has to be configured here.

Languages A Language can be assigned to a user from the "Assistance" dialog box located under the "User" tab. The language used for
these announcements can also be selected there.

The languages available for audio assistance for any specific PORT Technology system are programmed in the speech
module firmware for that system.

A defined language does not mean necessarily announcement, it can be displaying only.

6.1. Commission

Coommissioning of the following configuration is mandatory:

Site info
Building(s)
Lift layout (lifts)
Zones and zone access.

EJ_41905010_07 TM PTE 01 - General


Page 25 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
7. Network
For details on the networking, see:

PTN - General
PTN - Expert.

1. Click Network, Elevators, Tools.


2. On the Main Categories menu, double-click Driver.

Button / Tab Description


New Connection Adding a new driver

New Gateway Connection Adding a new Gateway connection

UDP General information on UDP

TCP Client / Server General information on TCP

LON Network General information on LON Network

Windows Messages General information on Windows Messages

7.1. Ethernet
Ethernet is based on an Internet protocol suite. The physical layer consists of the basic networking hardware transmission technologies of a
network. The network layer provides addressing and path determination through a network of many networks connected by routers. This is
done frequently using IP addresses. The transport layer provides the transmission of an application from one computer to another computer.
The most known transport protocols are TCP and UDP.

TCP (Transmission Control Protocol) is used for connection-oriented transmissions.


UDP (User Datagram Protocol) is used for connectionless transmissions.

Layer (OSI names) Type

Transport Protocol TCP UDP

Network IP

Physical and Data Link LAN WAN

EJ_41905010_07 TM PTE 01 - General


Page 26 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
7.1.1. UDP
The UDP (User Datagram Protocol) is for the communication between PC devices such as

Programming station
PORT
PTG, PTDB
VCL, touch terminal, VDI, PDI...
Mainstation PCs
etc.

The UDP driver is the standard ethernet network driver.

With its bus topology, UDP is ideal for connecting IRON devices together. We propose to use a distinct UDP Connection for each group and
one common UDP gateway to interconect the groups.

Here, the gateway can rather be seen as semipermeable firewall with following characteristics:

Traffic from and to global devices is allowed.


Traffic among local devicess is blocked.

7.1.1.1. UDP Gateway

A gateway connection is required to connect different groups together.

A Z-line terminal can only handle up to 50 partners. If more than 50 partners (jobmanager, database, SOM handler) are used, the network
must be divided and a second main station is required.
The number of partners on PORTs is not limited.

Usually the elevator groups building are defined as a cluster. The groups are interconnected by a gateway connection.
The UDP port for the gateway connection is 6500. This is considered as a global network connection.
Communication within each cluster takes place via another port such as 6503 or 6504.This is considered as a local network
connection.
The devices in one local network connection/cluster cannot communicate via the global connection with devices in another local
network connection/cluster. This means that a terminal within a particular cluster cannot send requests and assign calls to elevators
in another cluster.

Examples of devices in a local network connection [device ID = 0…127]:

Terminals
Job managers
Doors
Drives
Most of the other operational elevator devices.

Examples of devices in a global (gateway) network connection [device ID = 128…255]:

Main data base


First backup data base
Most visualization devices such as Overviews and Visual configuration.

EJ_41905010_07 TM PTE 01 - General


Page 27 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
7.1.2. New Connection on PTG
1. In Visual Configuration, click the PTG to be configured.
2. Click Drivers.

Parameter Description
LON Interface Selecting the LON interface type

Select Encryption Key Selecting the encription key

UDP Driver Selecting the UDP port

Auxiliary UDP Driver Selecting the UDP gateway

Top Server Driver Selecting the TCP port

Top Client Driver Selecting the TPC client

1. Udp Driver:
Port: Select the UDP port (for example: Start with 6942).
2. Auxiliary Udp Driver:

Select the Enabled check box.


Port: Select the UDP gateway (for example: Start with 6500).
Select the Gateway check box.
The UDP gateway is optional and can be switch off.

EJ_41905010_07 TM PTE 01 - General


Page 28 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
7.1.3. New Connection on PC

1. Log on to the PORT Technology software as an Expert.


2. Click Networks, Elevators, Tools.
3. On the Main Categories menu, double-click Driver.
4. Click the UDP tab and read the instructions.
5. Click New Connection.

1. In the dialog box, select the following parameters:

Choose Netdriver Type: Select UDP from the drop-down list.


UDP Options:
If only one UDP network is available: Keep the default settings.
If a second UDP network (second group) is available: Select a different port
number (for example 6504). Keep the remaining default settings.
2. Click Finish.

The new network connection is displayed in the Installed Connections list.

7.2. Windows Message


The Windows Messages network driver is used for communication between the different programs installed on the same computer, for
example External Supervisor.

To establish a Windows Message connection, check:


The net number is the same.
The executable is running on the same PC.
It is possible to have multiple Windows Message drivers with the same net number.

Use Windows Messages to connect different applications (.exe-files) on the same PC. (preferred connection for PORT
Technology).

7.2.1. New Connection on PC

1. Log on to the PORT Technology software as an Expert.


2. Click Network, Elevator, Tools.
3. On the Main Categories menu, double-click Driver.
4. Click the Windows Messages tab and read the instructions.
5. Click New Connection.

1. In the dialog box, select the following parameters:


Choose Netdriver Type: Windows Message
Net Nr: Keep the default number 1.
Encrypt: Keep the default setting No encryption.
2. Click Finish.

The new network connection is displayed in the Installed Connections list.

EJ_41905010_07 TM PTE 01 - General


Page 29 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
7.3. LON
The LON (Local Operating Network) is a fieldbus that connects various devices such as terminals, annunciators, destinaton
indicators or I/O boards to a PORT Technology PC solution or a PTG.
Only two data wires are required for communication. Shielding is not required.

7.3.1. LON Topology

Description Bus Topology Free Topology


Maximum Cable Length 900 m 500 m

Maximum T-Cable Length 3m > 3 m possible

Maximum Node-to-Node Distance - 300 m

Bus Termination 105 Ohm (on either 2 x 105 Ohm (parallel, at the center point, equals
end) 52.5 Ohm)

Maximum Number of LON Devices (distributed on a 2.5 mm2 32 per segement


power line)

Power versus Bus


This description applies for the LON bus, not for the power of the devices.
The power supply (NG) must be sufficient to supply all devices connected. Multiple power supply might be
required, depending on the power consumption of the devices.

7.3.2. New Connection on PTG

1. Select Gesytech USB (default). If no LON is connected, select None to switch off the LON interface.
2. Install the LON network:

Two wires for the signal from PTG.


Two wires for power supply 24V from any power module.
3. Download the LON node software with the update tool (PORT Technology software on PC).

Maximum 32 LON nodes on each PTG riser.

EJ_41905010_07 TM PTE 01 - General


Page 30 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
7.3.3. New Connection on PC

1. Log on to the PORT Technology software as an Expert.


2. Click Network, Elevator, Tools.
3. Click
4. Click Driver > Driver.

1. In the dialog box, select the following parameters:


- Choose Netdriver Type: LON
- Interface Type: See the information box below.
- Interface No: Keep the default number 1.
2. Click Finish.

The new network connection is displayed in the Installed Connections list.

The Interface Type depends on the interface card type.

On Mainstation PC: Easylon: PCI or Easylon: USB.


On service laptop: Echelon: PCMCIA or Easylon: USB.

EJ_41905010_07 TM PTE 01 - General


Page 31 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
8. Jobmanager
Type Description

Planning This is the preferred and standard way to connect an elevator to the PORT Technology. For each elevator, a separate
jobmanager job manager is created.

Conventional This type of jobmanager is used only when there is a conventional TX or MX elevator (simplex) with landing and
jobmanager car call buttons. The controller remains conventional, but the access rules are handled by the PORT Technology.
For the jobmanager settings, see Conventional Jobmanager Settings.

Use only if advised

Miconic 10 A Miconic 10 Overlay is connected to the PORT Technology.


Overlay Job Ma There is only one job manager for the entire group.
nager
Typically not used anymore.

8.1. Creating of Jobmanager

Creating of conventional jobmanager


The conventional jobmanager is created automatically. No additional steps are required.
For the settings, see Conventional Jobmanager Settings in PTE - Expert.

1. In Visual Configuration, click the PTG to be configured.


2. Click Lift.

Parameter Description
Door / Drive Defining the door/drive type

Jobmanager Starting the jobmanager task

Group Traffic Manager Starting the Group Traffic Manager task

BIOP PRHs For PORT 2 (BIO terminals)

EJ_41905010_07 TM PTE 01 - General


Page 32 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
Statistics Recorder Activating the statistics recorder to obtain the required data for reporting

File Exchange Activating the file exchange to obtain the required data for reporting

LON Floor Display Activating the floor display

1. Select the Jobmanager check box to start the Jobmanager task.


2. Click OK.

The Jobmanager number (TaskID) is taken from the SID Number.

Do not forget to adjust the Lift ID of the corresponding PTG because this is taken for the TID of the Jobmanager.

Set the SID number of the corresponding elevator in the installation (not group).

Number the SID number consecutively (1..254).

EJ_41905010_07 TM PTE 01 - General


Page 33 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
8.2. Basic Settings

Only the main settings are described in this document. For details, see PTE - Expert Manual.

8.2.1. Position Coordinates


The position coordinates indicate the position and orientation of the elevators.

Parameter Description
X-Position Select the x-position of the elevator measured from the center of the front door.
Range: 0 ... 255 m.

Y-Position Select the y-position of the elevator measured from the front door.
Range: 0 ... 255 m.

Orientation Select the orientation of the front door of the elevator.

X> Y^ <X vY

Allocation Text Type the displayed elevator name.


Maximum two characters (letters and numbers) are possible, for example A, B, C, etc., or A1, A2, A3, etc.

EJ_41905010_07 TM PTE 01 - General


Page 34 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
8.2.2. Planner
Space in Car:

Type or select the following car specifications:

Space X: Space in x-direction


Space Y: Space in y-direction.

Car Load:

Type or select the following car load specifications:

Rated Load: Approved rated load of the elevator per deck according to the car
label inside the car.
Max. Car Filling: Percentage of the rated load available for the call allocation. The
value should be in the range of 50 ... 80 %. Recommended value: 60 %.
Max. Load: This value is calculated automatically based on the Rated Load and
the Max. Car Filling values, using an average weight of 75 kg per person.

Door / Transfer Times:

Type or select the door open times and the transfer time.

Use the default values and optimize depending on the local situation.

Checks:

Select the required specifications.

Exclusion of passenger groups: Default setting: Check box selected.


If not selected, all the group exclusion settings for the users are ignored. For details,
see section Excluded Groups Functions in the document PTE - Master User Manual.
Assigned car must stop (unless full): Default setting: Check box selected.
If selected, the assigned car stops in travel direction if space for the passenger(s) is
available ("Panorama Lift" function).

EJ_41905010_07 TM PTE 01 - General


Page 35 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
8.2.3. Allocation Status

Setting Description
Current Status Green: Allocations enabled.
Red: Allocations disabled. The reason for disabling is displayed in the status bar.

Current Plan Length Numbers of allocated stops.

Stop allocations to this car Click to disable and enter allocations to this car.
The elevator completes the planned stops after having been out of order.

Enable allocations to this car Click to enable and enter allocations to this car.

EJ_41905010_07 TM PTE 01 - General


Page 36 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
8.2.4. Floor Settings

Setting Description
Floor Floor number

Call Limit Type the maximum number of calls for each floor. Recommended value: 1 or 2.

To prevent misuse (call repetition by users without identification), the recommended call limit value is 1 or 2. The limit
is set per boarding floor (floor) and is applied for each destination separately.

Additional Type the additional transfer time for each floor. Default value: 0.
Transfer Time
The additional transfer time is added to the calculated Door/Transfer Time. For details on the Door/Transfer Time, see
the Planner tab.

EJ_41905010_07 TM PTE 01 - General


Page 37 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
8.2.5. Special

Setting Description
Description Type an additional text to the allocation text to be displayed in the overview.

Evacuation Floor number where the elevator is travelling to in case of an unrecoverable error.
Floor
Type the floor number where the elevator has to travel to in case of an unrecoverable error (for example main lobby
floor).

EJ_41905010_07 TM PTE 01 - General


Page 38 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
9. Group Traffic Manager
The Group Traffic Manager optimizes traffic, waiting time, intermediate stops and parking.
Formerly, the Group Traffic Manager was called "Group and Parking".

9.1. Creating of Group Traffic Manager on PTG


1. In Visual Configuration, click the PTG to be configured.
2. Click Lift.

Parameter Description
Door / Drive Defining the door/drive type

Jobmanager Starting the jobmanager task

Group Traffic Manager Starting the Group Traffic Manager task

BIOP PRHs For PORT 2 (BIO terminals)

Statistics Recorder Activating the statistics recorder to obtain the required data for reporting

File Exchange Activating the file exchange to obtain the required data for reporting

LON Floor Display Activating the floor display

1. Select the Group Traffic Manager check box to start the Group Traffic Manager task.

For each elevator, a group traffic manager is required.


The Group Traffic Manager number (TaskID) is taken from the SID Number.

After creating all group traffic manager tasks, group them.

EJ_41905010_07 TM PTE 01 - General


Page 39 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
9.2. Creating of Group Traffic Manager on PC

1. Click Network, Elevator, Tools.


2. Click Lift > Planner.
3. Click Create Job Manager.
4. Select the Create Group Traffic Manager check box.
5. Click Finish.

For each elevator, a group traffic manager is required.

After creating all group traffic manager tasks, group them.

EJ_41905010_07 TM PTE 01 - General


Page 40 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
9.3. Basic Settings
In Visual Configuration, click the P icon.

The folowing window opens:

Tab Description

Group Settings apply for all group members.


All group members are updated automatically.

Lift For independent elevator settings.

EJ_41905010_07 TM PTE 01 - General


Page 41 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
9.3.1. Group
Group Members:

1. Select all elevators in the same group, for example in the same zone of the building.
Default setting: No elevator selected, except own.

It is absolutely necessary and mandatory to check all GTM of one group as a group, otherwise the GTM does
not operate correctly.

Group Parking - Activity:

Select the required mode.

Off: No group parking activity. However, an elevator may park according to the
individual settings defined on the Lift tab.
On: Parking according to the settings below, such as parking to predefined floors
and/or statistical parking.
For each elevator that shall participate in group parking, set the individual activity
mode on the Lift tab to Group Parking. For elevators controlled via CCI, do not use
parking at all.
On while Timing active: Mode is set to On while the specified timing is active and set
to Off while the timing is not active.
On except Timing is active: Mode is set to On while the specified timing is not active
and set to Off while the timing is active.

Group Parking - Group Optimization:

Smaller values reduce the destination times and the number of intermediate stops, as
different elevators are likely to be used for different passengers.
Higher values reduce the waiting times and increase the number of intermediate stops,
as the same elevator is likely to be used for different passengers.
Recommended value: 50 ... 100 (Default value: 100).

With high values, the system may not have sufficient handling capacity during peak
hours.

Group Parking - Reduce Long Waits:

Long waiting times are avoided if possible, for example fewer calls will experience long
waiting, but more calls may experience average instead of small waiting times.
Higher values have a stronger effect.
Recommended value: 20 ... 100 (Default value: 20).

Not all long waits may be eliminated, but the probability will decrease.

EJ_41905010_07 TM PTE 01 - General


Page 42 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
9.3.2. Lift

Activity:

1. Select the required mode.

No Parking: The elevator does not park at all.


Park to predefined floor: The elevator is parked at the predefined floor.
Group Parking: The elevator is parked according to the
Group Parking settings.

For elevators with a car call interface, select the No parking mode.
For each elevator that shall participate in group parking, set the individual activity mode on the Lift settings to Group
Parking.

Free to Park Delay:

Delay after which an elevator becomes idle before parking.

Default value: 5.0 s.

EJ_41905010_07 TM PTE 01 - General


Page 43 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
10. Doors and Drives

For details, see PTE - Underlayer.

Several different interface types of doors and drives are available. For each "Planning Job Manager", at least one door and one drive task is
required. The different types can be mixed.

Type Description
VCOM (TX, TX-GC, This type is mainly used with the PORT Technology. PORT Technology operates a TX, TX-GC, TX-GC2 or
TXG-C2, TX5) TX5 group over the VCOM bus.
Each controller uses one PTG as interface.

BMS (MX-GC) This type is very similar to the VCOM type. Each controller uses one PTG as interface.

I/O-Board This type is normally used for modernization where the PORT Technology controls a conventional elevator
(Car Call Interface) (Schindler or third party) by means of the existing car call buttons.
This door drive interface requires an I/O-board connected to the LON bus.

ARCNET (Miconic This type is used for Miconic V, 2nd generation with the ARCNET bus.
V)

Internal PC This type allows the simulation of a door drive within the PC. This type is normally used for demonstration
Simulation purposes.

Check the tabs of the different door /drive types for information on the connection of the various interfaces to the real
controllers.
Read the information carefully.

EJ_41905010_07 TM PTE 01 - General


Page 44 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
10.1. Internal PC Simulation

1. Click Network, Elevators, Tools.


2. Click Lift > Door/Drive > General.

To change the number of simulated floors, select the


corresponding drive and click Show selected.
Complete the visual configuration of the number of floors and
entrance sides.

3. To create an internal PC simulated door/drive interface, click Creat


e Door/Drive.

1. Select the following parameters from the drop-down list:


Interface: Internal PC simulation
Number of Floors:
Create Doors:
2. Click Finish.

The door and drive are added to the installed lift list respectively.

1. Repeat the procedure for all required doors and drives.

EJ_41905010_07 TM PTE 01 - General


Page 45 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
11. SOMs
1. Log on to the PORT Technology software as an Expert.
2. Click Visual Configuration.
3. Click SOM.

Tab Description
Available SOMs Edit Special Requiement Modes

Special Requiement Modes Specification for SRM 300

Active SOMs Display all active SOMs

Parameters Position the SOM icon

EJ_41905010_07 TM PTE 01 - General


Page 46 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
11.1. Creating of SOM Task on PTG
1. In Visual Configuration, click the PTG to be configured.
2. Click Group.

Parameter Description
SOM Handler Activating the SOM handler

Overview Proxy For locks only (PORT Technology Access)

TX4 Server Starting theTX4 server task

Arcnet Server Starting the Arcnet server task

Port Authotity Displaying the fire information sign in case of fire service

Floor Display Not required

1. Select the SOM Handler check box.


2. Select the group number.
3. Select the Master check box to define the master database.
Each group contains one master SOM handler.
4. Click OK.

EJ_41905010_07 TM PTE 01 - General


Page 47 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
11.2. Creating of SOM Task on PC

Applicable for installations with main station only.

The SOM handler handles all SOM's within PORT Technology.


The SOM handler also handles SOM's running in the underlayer but started on SID by code input.
Three different SOM handler types are available:
PORT Technology
M10 Overlay
PORT Technology - DLL.

Only one master and one backup SOM handler can exist within the PORT Technology PC application.
The master SOM handler and the backup SOM handler must be running on separate PCs.

1. Click Network, Elevator, Tools.


2. Click Lift Group > SOM Handler.
3. Click Create SOM Handler.

1. Select PORT Technology.


2. Select the required parameters from the drop-down list for:
Group Number
Priority.
3. Click Finish.

EJ_41905010_07 TM PTE 01 - General


Page 48 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
11.3. Importing of SOMs

Button Description
View / New / Edit / Copy Viewing the SOM settings
Creating new SOMs
Editing the SOM settings
Copying existing SOMs.

Delete Deleting existing SOMs

On / Off Starting or switching off SOMs

Import / Export Importing or exporting SOMs from the file system

1. To import a new SOM:


Click Import.
Select the corresponding .xml file in the file system.
2. To export a SOM:

Select the SOM to be exported.


Click Export.
Select the storage location.
Click Save.
The SOM data is stored as an .xml file.

EJ_41905010_07 TM PTE 01 - General


Page 49 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
12. Install Expert
The install expert makes an automatic check of the PORT Technology software installation and configuration and shows suggestions for fault
correction.

It is recommended to run the install expert:

After initial configurations


After modifications
Once every six months.

It is recommended to run the install expert before the initial starting of the the PORT Technology software and after every essential
modification.

EJ_41905010_07 TM PTE 01 - General


Page 50 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
13. Overview Window
1. Click Network, Elevators, Tools.
2. On the Main Categories menu, double-click Overviews.

Button Description
Create Overview Create an overview module

Create Overview Proxy Create an overview proxy module

EJ_41905010_07 TM PTE 01 - General


Page 51 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
14. I/O Controls
The I/O controls configuration is used to configure PORT Technology modules that require an input our output, such as door drives, floor light
controllers and door bell controllers, SOMs, internal supervisors, etc.
1. Log on to the PORT Technology software as an Expert.
2. Click Visual Configuration.
3. Click I/O.

4. Select the I/O control (number) to be configured.


5. Add the pin table on the right side of the working window. As long as no real I/O board has been assigned, the indicators are
displayed in grey. Depending on the selected module, the parameters will change to reflect the module type.
If the corresponding module is not an I/O-control (for example a simulated drive or a VCOM drive), the message This is not an
I/O-control is displayed.
A list of all available physical I/O boards is displayed.
6. Click the desired TID numbers in the Available I/O Board Controls and Available I/O Boards columns to change the selection.

EJ_41905010_07 TM PTE 01 - General


Page 52 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
When the I/O board is connected, its number is displayed. The PIN indicators take the color of the state of the corresponding input.

Green: Signal is active low


Red: Signal is active high.

EJ_41905010_07 TM PTE 01 - General


Page 53 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
15. Internal Supervisor

The Supervisor tasks are only used together with PC (Programming Station) hardware.

General: The supervisor checks the following:

Correct function of the modules


Temperature
Availability of the job managers
Error messages from the system.

The supervisor can be configured to send messages to a service center, to a Schindler technician, the building manager or to appear a
message on the programming station.

Actions: For each defined event, the supervisor takes one of the following actions:

Show messages on the window


Set or clear an Output PIN on a defined I/O board
Send a SMS to one or more persons
Send an e-mail to one or more person
Shut down the PC in case of over-temperature.
Deployment: Depending of the number of PORT Technology PCs, it is advisable to have more than one supervisor tasks running.
Ideally, the supervisor tasks should be running on different branches of the network to increase the availability and it is recommended on the
backup PC regarding the temperature sensor.

15.1. Opening of Supervisor

1. Click Network, Elevators, Tools.


2. Click Supervision > Supervisor.
3. Click Create Supervisor.

1. In Visual Configuration, double-click the supervisor.


2. Fill in the following information:
Telephone directory
Module group
Actions
Settings and further information.

EJ_41905010_07 TM PTE 01 - General


Page 54 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
15.2. Opening of SMS Task

1. Click Network, Elevators, Tools.


2. Click Supervision > SMS Task.
3. Click Create SMS Task.

1. Double-click the SMS task (221.x.x.x).


2. Fill in the following information:
Communication
Debugging.

To be able to send SMS messages, the Supervisor task and the SMS hardware module must be available.

EJ_41905010_07 TM PTE 01 - General


Page 55 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
16. Logger
A so called "logger task" logs important events into a file on disk. The logger file can later be used to analyze the whole elevator traffic with
the "Traffic Expert" application.

Preferrably, the logger task is stared on the PTDB if available. Alternatively, the logger task can be started on a PC.
On PTGs, no logger task can be started.
If no PTDB or PC are available, a statistics recorder can be started on a PTG.

On mainstation, start the logger on the backup PC, never on the master PC.

When a logger task is created, the logger normally creates one logger file per day.
Each logger file has the following name format: YYYY_MM_DD_VV.logger.sq3 (YY=year, MM=month, DD=day, VV=version).
The logger file version is incremented in case writing of the logger file fails and a new logging attempt is required.

The logger task is a local task. Therefore, one logger task per network cluster is required.
A network cluster is a network of interconnected iron components using "direct" iron drivers (non-gateway drivers).

On mainstation, start the logger on the backup PC, never on the master PC.

16.1. Creating of Logger

1. Click Network, Elevator, Tools.


2. Click Supervision > Logger.
3. Click Create Logger.

1. Number: Select the instance number (related to the


corresponding group) from the drop-down list.
2. Click Finish.

EJ_41905010_07 TM PTE 01 - General


Page 56 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
17. Updating of of PORT Technology Software and Components

The PORT Technology software in the field is not updated every time a new software version is released.

A software update is performed for following reasons:

New software features


Hardware replacement (programming station, service laptop, main station, touch terminal, etc.)
Fault correction.

The update folder on the FTP server includes the following components:

Component Descripton

Database Database conversion software (Paradox to SQLite)

PORT Technology Software Software for programming station, main station PCs

Visitor Control Software for visitor control

Touch Terminal Software for touch terminal

SID Zipper Diagnostics tool

Driver Driver for VCOM, ARCNET, LON, ....

Update first the programming station.


Check the elevators are still running.

The update is performed in following steps:

1. Download of software
2. Update of database (optional)
3. Update of PORT Technology software
4. Update of LON components
5. Update of visitor control and touch terminal (optional)
6. Update of drivers (optional).

17.1. Update Tool


Update Tool is used to update the software on following devices:

PORT 1.X
PORT 4.X
PTG1 (PORT Technology Gateway 1)
PTG2 (PORT Technology Gateway 2)
PDI (PORT Destination Indicator)
LON Devices (ZLine, ANN, IO, DI, PDC).

The PORT Technology software version V1.2.329.1 or newer is required.

1. Log on to the PORT Technology software as an Expert.


2. Click Network, Elevator, Tools.

EJ_41905010_07 TM PTE 01 - General


Page 57 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
1. At Tools, select Update Tool from the drop-down menu.

17.2. Search Devices


Use Search Devices to find all mentioned devices within the network.

Search using IRON Diagnostic will find all devices comminicating on the configured network on the current PCs (UDP, LON, etc.).
Search on local network will find all "smart" devices connected to the network regardless of the driver installed (DUP, TCP, etc.).

To update LON devices such as ZLine, DI, ANN, etc., use Search using IRON Diagnostic.
To update and commission unconfigured devices such as PORT, PTDB, VCL, etc., use Search on local network.

17.2.1. Searching using Iron Diagnostics


Searching devices with Search using Iron Diagnostic will find all devices and tasks connected to the current IRON network on the
PC on which the Update Tool is running.

EJ_41905010_07 TM PTE 01 - General


Page 58 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
17.2.2. Searching on Local Network
Searching devices with Search on local network will find all devices within the same network (IP resp. Netmask) as the PC on which the
Update Tool is running, regardless of UDP, UDP GW, etc.

Tip
If the UDP or IP of a device is not known, the device can be found with this option, as long as the device is connected and
powered.

EJ_41905010_07 TM PTE 01 - General


Page 59 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
17.3. Update Tool Window

Left Pane

Column Description

Type Device type (PORT, PDI, PTG)

Hostname PC Name of this device

UDP UDP used for this device to connect

Version Installed PT software version on device

IRON Installed IRON software version on device

State Software status of the device (see below for more information)

Action Action to be taken (see below for more information)

Right Pane

The details displayed in the right pane are for information only (normally not used in the field).

Tab Description

Device Device details, such as IP address, etc.


Details

Software Details of all software packages within the device system (old version and "to install" version)
Details

Configure Visual configuration preferred to configure device (see corresponding device document for further information). Also see
Device section Incorrect IP Configuration.

Messages Message flow

EJ_41905010_07 TM PTE 01 - General


Page 60 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
17.4. Software Status on Device
Depending on the installed packages, the the software status of a device can either be:
uptodate
upgrade
downgrade
remove.

Each device has several different packages inside the software which makes it easier to update only parts and not the entire software itself.

uptodate (green)

The software version on the device is identical with the current PORT Technology software provided.

upgrade (turquoise)

At least one software package requires an update.


The software version on the device is older than the current PORT Technology software provided.
The preceeding number indicates the number of software packages to be updated.

downgrade (pink)

At least one software package is newer than the current PORT Technology software provided.
Either update the PORT Technology software or downgrade the software on the device.
The preceeding number indicates the number of software packages to be downgraded.

Never downgrade the PORT Technology software!


Downgrading the software on the PTG is also NOT recommended!

remove (grey)

At least one software package is not used anymore.


Recommendation: Remove these software packages.
The preceeding number indicates the number of software packages to be removed.

EJ_41905010_07 TM PTE 01 - General


Page 61 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
17.5. Updating of Software on Device
The software packages on a device can be:
Updated
Downgraded
Removed.

General update procedure


1. Update one device first.
2. Test the device.
3. Update either:

Riser by riser (PORT), so that one PORT on the floor is still available.
Even/odd elevators (PTG), so that half of the elevators are still in service.
Main/secondary PDI, so that one PDI in the car is still available to display the destinations.

1. Select the device(s) to be updated using one of the following methods:

Select one device only.


Select multiple devices in a row.
Click the first device in the row.
Press and hold the Shift key.
Click the last device in the row.
Select multiple interjacent devices.
Click the first device.
Press and hold the Ctrl key.
Click all the required devices.

1. Right-click the selected device(s).


2. Select Update Software. In the Action column, the status of the selected device(s)
changes to Update.
3. Check the status in the Action column only changes to Update on the devices that
require an update.
4. If a device with the action status Update does not require an update:

Right-click the device.


Select "Do nothing".

The device in removed from the update list.

1. Click Execute Action(s).


2. Click Yes.

In the State column, the status of the update process is displayed.

After completion of the update, the result of the update is displayed.

State column: Green (uptodate)


Action column: Update Complete.

1. Repeat the procedure for all devices to be updated.

Update Procedure in Short


Select the device.
Right-click the device and select Update Software.
Click Execute Action(s).

EJ_41905010_07 TM PTE 01 - General


Page 62 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
Updating of Identical Device Types / UDP Ports

Devices / UDP ports of the same type can be updated at once.

During the update, these devices might not be available for operation.

1. Do not select any device.


2. Click Execute Action(s).

1. Select the UDP Port or device type to be updated.


2. Click OK.

17.6. Update Tool Troubleshooting

17.6.1. Incorrect IP Configuration


If the column State is marked in red and the status update wrong ip configuration is displayed, a serious error has occurred.

The device has a wrong IP setting, which can cause serious problems for the installation.
Select the Device Details tab and check the IP setting of the device.
To change the IP setting immediately, select the Configure Device tab and correct the setting.

EJ_41905010_07 TM PTE 01 - General


Page 63 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
17.6.2. Two Update Tools Running within Same System

The error message indicates the PC on which this update tool is running. This update tool can be closed.

Only run one update tool at a time. Otherwise, one update tool might update and the other update tool might downgrade (if it has
older software).

17.6.3. Two Network Cards Used in PC


If the PC used to run the Update Tool has two network cards, select the network card to be used for the update.

1. Select the required network card from the drop-down list.

When changing the IP of the PC; these settings need to be adjusted.

EJ_41905010_07 TM PTE 01 - General


Page 64 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
17.6.4. Checking of Installed Software Packages
1. Select the Software Details tab.
2. Select the Show all Software Packages check box.

All installed packages are displayed.

EJ_41905010_07 TM PTE 01 - General


Page 65 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
18. Lobby Vision / e-Vision

For e-Vision, a Lobby Vision task is also used. If both Lobby Vision and e-Vision are used, the Lobby Vision task will automatically
handle both.

Connect the Lobby or e-Vision PC to the PORT Technology network (Ethernet) and create a Lobby Vision task for each group on
the first PTG of the corresponding group.

For Lobbyvision 3 (LV3) you have to use "Lobbyvision 3" Task instead.

18.1. Creating of Lobby Vision Task

18.1.1. Creating of Lobby Vision Task on PTG


1. In Visual Configuration, click the PTG to be configured.
2. Click Interface.

Parameter Description
Lobby Interface Configuration for Lobby Vision

LV3 Interface Configuration for LV3

DB Importer Transfering common data of persons and assigned badges

Ext Call Manager Activating an external call manager, so that an external control system can be used

XML Converter Activating the XML converter to send elevator information in real time

Escalator Configurating the escalator interface

EJ_41905010_07 TM PTE 01 - General


Page 66 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
For Lobby Vision 2 (LV2), start one Lobby Vision task for each group of elevotors.
Configure the Lobby Vision task on the new icon (for example G1 L1, G1 L2, G2 L2).

Lobby Vision task: Started on first PTG of the group.


Backup task: Started on the second PTG of the group.

18.1.2. Creating of Lobby Vision Task on PC

1. Click Network, Elevators, Tools > Interfaces.


2. Select the Lobby Vision / e-Vision tab.
3. Click Create Lobby Interface.

1. Select the lowest and highest car number of this group.


2. If the Lobby Vision task is created on a backup PC, select the
Backup check box.
3. Click Finish.

EJ_41905010_07 TM PTE 01 - General


Page 67 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
18.2. Lobby Vision Task Setting
In Visual Configuration, click the Lobby Vision icon.

The following window opens:

Tab Description Tab Description


Configuration tba Service Simulation tba

Master Messages tba Call Simulator tba

Lobby Messages tba Transfer tba

E-Vision Messages tba SpecialMessage tba

EJ_41905010_07 TM PTE 01 - General


Page 68 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
19. PORT Technology Support
Use the Support Home page or refer to the trouble-shooting document PTE - Diagnostics.

EJ_41905010_07 TM PTE 01 - General


Page 69 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved
20. Extended Index
1. Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Fundamentals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. PORT Technology Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Coordinate System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3. Task Identification Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.4. User Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.5. Software Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.5.1. Network Elevator Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.5.2. Visual Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.6. Main Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.6.1. Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.6.2. Jobmanager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.6.3. Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.6.4. Timeserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.7. Setup Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.7.1. Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4. Installation and Commissioning Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.1. Software Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.2. Order Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.3. Registration Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.4. Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.5. Adding of Login Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.6. Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.7. Commissioning Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5. Initial Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1. Tasks on PTG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1.1. Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1.2. Jobmanager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.2. Tasks on PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.2.1. Time Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.2.2. User Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
6. Building Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.1. Commission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
7. Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.1. Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.1.1. UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.1.1.1. UDP Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.1.2. New Connection on PTG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.1.3. New Connection on PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.2. Windows Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.2.1. New Connection on PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.3. LON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
7.3.1. LON Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
7.3.2. New Connection on PTG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
7.3.3. New Connection on PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
8. Jobmanager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
8.1. Creating of Jobmanager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
8.2. Basic Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
8.2.1. Position Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
8.2.2. Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
8.2.3. Allocation Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
8.2.4. Floor Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
8.2.5. Special . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
9. Group Traffic Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
9.1. Creating of Group Traffic Manager on PTG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
9.2. Creating of Group Traffic Manager on PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
9.3. Basic Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
9.3.1. Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
9.3.2. Lift . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
10. Doors and Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
10.1. Internal PC Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
11. SOMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
11.1. Creating of SOM Task on PTG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
11.2. Creating of SOM Task on PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
11.3. Importing of SOMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

EJ_41905010_07 TM PTE 01 - General


Page 70 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved.
12. Install Expert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
13. Overview Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
14. I/O Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
15. Internal Supervisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
15.1. Opening of Supervisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
15.2. Opening of SMS Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
16. Logger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
16.1. Creating of Logger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
17. Updating of of PORT Technology Software and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
17.1. Update Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
17.2. Search Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
17.2.1. Searching using Iron Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
17.2.2. Searching on Local Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
17.3. Update Tool Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
17.4. Software Status on Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
17.5. Updating of Software on Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
17.6. Update Tool Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
17.6.1. Incorrect IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
17.6.2. Two Update Tools Running within Same System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
17.6.3. Two Network Cards Used in PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
17.6.4. Checking of Installed Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
18. Lobby Vision / e-Vision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
18.1. Creating of Lobby Vision Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
18.1.1. Creating of Lobby Vision Task on PTG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
18.1.2. Creating of Lobby Vision Task on PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
18.2. Lobby Vision Task Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
19. PORT Technology Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
20. Extended Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

EJ_41905010_07 TM PTE 01 - General


Page 71 of 71 Copyright © 2002 - 2015 Inventio AG. All Rights Reserved

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy