EP3904259A1 - Aufzugskommunikationssystem - Google Patents

Aufzugskommunikationssystem Download PDF

Info

Publication number
EP3904259A1
EP3904259A1 EP20172442.4A EP20172442A EP3904259A1 EP 3904259 A1 EP3904259 A1 EP 3904259A1 EP 20172442 A EP20172442 A EP 20172442A EP 3904259 A1 EP3904259 A1 EP 3904259A1
Authority
EP
European Patent Office
Prior art keywords
elevator
bus
ethernet bus
communication system
data channel
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP20172442.4A
Other languages
English (en)
French (fr)
Inventor
Juha-Matti Aitamurto
Ari Kattainen
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Kone Corp
Original Assignee
Kone Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Kone Corp filed Critical Kone Corp
Priority to EP20172442.4A priority Critical patent/EP3904259A1/de
Publication of EP3904259A1 publication Critical patent/EP3904259A1/de
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B66—HOISTING; LIFTING; HAULING
    • B66B—ELEVATORS; ESCALATORS OR MOVING WALKWAYS
    • B66B1/00—Control systems of elevators in general
    • B66B1/34—Details, e.g. call counting devices, data transmission from car to control system, devices giving information to the control system
    • B66B1/3415—Control system configuration and the data transmission or communication within the control system
    • B66B1/3423—Control system configuration, i.e. lay-out
    • B66B1/343—Fault-tolerant or redundant control system configuration
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B66—HOISTING; LIFTING; HAULING
    • B66B—ELEVATORS; ESCALATORS OR MOVING WALKWAYS
    • B66B1/00—Control systems of elevators in general
    • B66B1/34—Details, e.g. call counting devices, data transmission from car to control system, devices giving information to the control system
    • B66B1/3415—Control system configuration and the data transmission or communication within the control system
    • B66B1/3446—Data transmission or communication within the control system
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B66—HOISTING; LIFTING; HAULING
    • B66B—ELEVATORS; ESCALATORS OR MOVING WALKWAYS
    • B66B1/00—Control systems of elevators in general
    • B66B1/34—Details, e.g. call counting devices, data transmission from car to control system, devices giving information to the control system
    • B66B1/3415—Control system configuration and the data transmission or communication within the control system
    • B66B1/3446—Data transmission or communication within the control system
    • B66B1/3453—Procedure or protocol for the data transmission or communication
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B66—HOISTING; LIFTING; HAULING
    • B66B—ELEVATORS; ESCALATORS OR MOVING WALKWAYS
    • B66B5/00—Applications of checking, fault-correcting, or safety devices in elevators
    • B66B5/0087—Devices facilitating maintenance, repair or inspection tasks

Definitions

  • the present application relates to the field of elevator communication systems.
  • an elevator controller may receive information from call buttons and then control an elevator drive to serve calls, or the elevator controller may receive information from a safety circuit and then based on this information control one or more entities of the elevator system. These are only some possible examples of situations where information is received and/or sent within an elevator system.
  • an elevator system may comprise multiple different internal data transmission solutions. This may mean that multiple different communication stacks and multiple different physical layers may be used simultaneously. The use of multiple different internal data transmission solutions may result in a complicated and inefficient solution. Further, if a bus node, for example, a node disposed in a pit is connected to a communication bus enabling communication to an elevator controller, the communication bus may become faulty and thus communication from the bus node in the pit (for example, from the pit inspection station) towards the elevator controller may not be possible.
  • an elevator communication system associated with a building comprising an elevator shaft.
  • the elevator communication system comprises an ethernet bus, an elevator controller communicatively connected to the ethernet bus and configured to communicate via the ethernet bus, a plurality of connecting units disposed along the elevator shaft to implement the ethernet bus, at least one bus node disposed in the elevator shaft separated by a distance from the elevator controller and being communicatively connected to the ethernet bus and configured to communicate via the ethernet bus, and a second data channel separate from the ethernet bus, the second data channel establishing a direct connection between the at least one bus node and the elevator controller.
  • the at least one bus node is disposed in a pit of the elevator shaft and the elevator controller is disposed in an upper part of the elevator shaft, in a landing of the upper part of the building, or in a machine room in the upper part of the building.
  • a maintenance or an inspection device disposed in the pit such as pit inspection station, can be used for a maintenance and/or an inspection operation even in case of a malfunction of the primary bus, i.e. the ethernet bus.
  • the second data channel comprises a separate ethernet bus section from the at least one bus node to the elevator controller.
  • the second data channel comprises a separate wire loop between the at least one bus node and the elevator controller.
  • the second data channel comprises a wireless data channel between the at least one bus node and the elevator controller.
  • the at least one bus node comprises an inspection station.
  • the various embodiments discussed below may be used in an elevator system comprising an elevator that is suitable and may be used for transferring passengers between landing floors of a building in response to service requests.
  • the various embodiments discussed below may be used in an elevator system comprising an elevator that is suitable and may be used for automated transferring of passengers between landings in response to service requests.
  • FIG. 1A illustrates an elevator communication system according to an example embodiment.
  • the elevator communication system comprises an elevator controller 100 and bus nodes 102A, 102B, 102C disposed in an elevator shaft.
  • the elevator communication system further comprises a plurality of connecting units 104A-104D disposed along the elevator shaft to implement an ethernet bus 106.
  • the ethernet bus 106 may be, for example, 100BASE-TX or 10BASET1L point-to-point ethernet bus.
  • the elevator controller 100 is communicatively connected to the ethernet bus 106 and configured to communicate via the ethernet bus 106.
  • the connecting unit 104A-104D may comprise, for example, a switch, a hub or a router.
  • elevator controller 100 and the bus nodes 102A, 102B, 102C are configured to comprise the connecting units 104A-104D. Further, in this example, the bus node 102C is separated by a distance from the elevator controller 100 and is communicatively connected to the ethernet bus 106 and configured to communicate via the ethernet bus 106. In an example embodiment, the bus node 102C is disposed in the elevator shaft far from the elevator controller 100. For example, the bus node 102C may be disposed in a pit of the elevator shaft and the elevator controller 100 be disposed in an upper part of the elevator shaft, in a landing of the upper part of the building, or in a machine room in the upper part of the building.
  • the elevator controller 100 may be disposed in the lower part of the building.
  • the bus node 102C comprises an inspection station.
  • the elevator communication system further comprises a second data channel 108 separate from the ethernet bus 106, the second data channel 108 establishing a direct connection between the bus node 102C and the elevator controller 100.
  • the second data channel 108 may comprise a separate ethernet bus section from the bus node 102C to the elevator controller 100, a separate wire loop between the bus node 102C and the elevator controller 100, or a wireless data channel between the bus node 102C and the elevator controller 100.
  • the second data channel 108 may also be implemented by using some other communication protocol than the ethernet protocol, for example, the CAN or LON protocol.
  • the second data channel is configured for establishing a direct connection between the at least one bus node and the elevator controller during a special operational state of an elevator, such as during maintenance, inspection or emergency operation of the elevator.
  • FIG. 1B illustrates an elevator communication system according to another example embodiment.
  • the elevator communication system comprises an elevator controller 100 and bus nodes 112A, 112B, 114 disposed in an elevator shaft.
  • the elevator communication system further comprises a plurality of connecting units 110A-110D disposed along the elevator shaft to implement an ethernet bus 106.
  • the ethernet bus 106 may be, for example, 100BASE-TX or 10BASET1L point-to-point ethernet bus.
  • the nodes 112A, 112B, 114 are connected to their respective connecting units 110B, 110C, 110D.
  • the elevator controller 100 is communicatively connected to the ethernet bus 106 and configured to communicate via the ethernet bus 106.
  • the connecting unit 110A-110D may comprise, for example, a switch, a hub or a router.
  • the nodes 112A, 112B, 114 are separate nodes from the connecting units 110B, 110C, 110D.
  • the bus node 102C is separated by a distance from the elevator controller 100 and is communicatively connected to the ethernet bus 106 and configured to communicate via the ethernet bus 106.
  • the bus node 102C is disposed in the elevator shaft far from the elevator controller 100.
  • the bus node 102C may be disposed in a pit of the elevator shaft and the elevator controller 100 be disposed in an upper part of the elevator shaft, in a landing of the upper part of the building, or in a machine room in the upper part of the building.
  • a maintenance or an inspection device disposed in the pit such as pit inspection station, can be used for a maintenance and/or an inspection operation even in case of a malfunction of the primary bus, i.e. the ethernet bus 106.
  • the elevator controller 100 may be disposed in the lower part of the building.
  • the bus node 102C comprises an inspection station.
  • the inspection station may comprise means for setting the elevator into a maintenance/inspection mode and/or for cancelling the maintenance/inspection mode.
  • the inspection station may also comprise means (for example, buttons) for driving a low-speed inspection drive with the elevator car.
  • the elevator communication system further comprises a second data channel 108 separate from the ethernet bus 106, the second data channel 108 establishing a direct connection between the bus node 102C and the elevator controller 100.
  • the second data channel 108 may comprise a separate ethernet bus section from the bus node 102C to the elevator controller 100, a separate wire loop between the bus node 102C and the elevator controller 100, or a wireless data channel between the bus node 102C and the elevator controller 100.
  • the second data channel 108 may also be implemented by using some other communication protocol than the ethernet protocol, for example, the CAN or LON protocol.
  • the elevator communication system may further comprise one or more multi-drop ethernet bus segments 120A, 120B (for example, in the form of 10BASE-T1S) reachable by the elevator controller 100, and a plurality of elevator system nodes 116A, 116B, 118A, 118B coupled to the multi-drop ethernet bus segments 120A, 120B and configured to communicate via the multi-drop ethernet bus segments 120A, 120B.
  • the elevator controller 100 is reachable by the elevator system nodes 116A, 116B, 118A, 118B via the multi-drop ethernet bus segments 120A, 120B.
  • Elevator system nodes that are coupled to the same multi-drop ethernet bus segment may be configured so that one elevator system node is to be active at a time while the other elevator system nodes of the same multi-drop ethernet bus segment are in a high-impedance state.
  • At least some of the above discussed example embodiments may ensure transmission of data from a bus node, for example, an inspection station is case a normally used data transmission channel becomes faulty.
  • a pit inspection station can be used for a maintenance and/or an inspection operation even in case of a malfunction of the primary bus, i.e. the ethernet bus.
  • Example embodiments may be implemented in software, hardware, application logic or a combination of software, hardware and application logic.
  • the example embodiments can store information relating to various methods described herein. This information can be stored in one or more memories, such as a hard disk, optical disk, magneto-optical disk, RAM, and the like.
  • One or more databases can store the information used to implement the example embodiments.
  • the databases can be organized using data structures (e.g., records, tables, arrays, fields, graphs, trees, lists, and the like) included in one or more memories or storage devices listed herein.
  • the methods described with respect to the example embodiments can include appropriate data structures for storing data collected and/or generated by the methods of the devices and subsystems of the example embodiments in one or more databases.
  • All or a portion of the example embodiments can be conveniently implemented using one or more general purpose processors, microprocessors, digital signal processors, micro-controllers, and the like, programmed according to the teachings of the example embodiments, as will be appreciated by those skilled in the computer and/or software art(s).
  • Appropriate software can be readily prepared by programmers of ordinary skill based on the teachings of the example embodiments, as will be appreciated by those skilled in the software art.
  • the example embodiments can be implemented by the preparation of application-specific integrated circuits or by interconnecting an appropriate network of conventional component circuits, as will be appreciated by those skilled in the electrical art(s).
  • the examples are not limited to any specific combination of hardware and/or software.
  • the examples can include software for controlling the components of the example embodiments, for driving the components of the example embodiments, for enabling the components of the example embodiments to interact with a human user, and the like.
  • Such computer readable media further can include a computer program for performing all or a portion (if processing is distributed) of the processing performed in implementing the example embodiments.
  • Computer code devices of the examples may include any suitable interpretable or executable code mechanism, including but not limited to scripts, interpretable programs, dynamic link libraries (DLLs), Java classes and applets, complete executable programs, and the like.
  • a "computer-readable medium” may be any media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.
  • a computer-readable medium may include a computer-readable storage medium that may be any media or means that can contain or store the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.
  • a computer readable medium can include any suitable medium that participates in providing instructions to a processor for execution. Such a medium can take many forms, including but not limited to, nonvolatile media, volatile media, transmission media, and the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Indicating And Signalling Devices For Elevators (AREA)
EP20172442.4A 2020-04-30 2020-04-30 Aufzugskommunikationssystem Withdrawn EP3904259A1 (de)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP20172442.4A EP3904259A1 (de) 2020-04-30 2020-04-30 Aufzugskommunikationssystem

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP20172442.4A EP3904259A1 (de) 2020-04-30 2020-04-30 Aufzugskommunikationssystem

Publications (1)

Publication Number Publication Date
EP3904259A1 true EP3904259A1 (de) 2021-11-03

Family

ID=70482409

Family Applications (1)

Application Number Title Priority Date Filing Date
EP20172442.4A Withdrawn EP3904259A1 (de) 2020-04-30 2020-04-30 Aufzugskommunikationssystem

Country Status (1)

Country Link
EP (1) EP3904259A1 (de)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017008849A1 (en) * 2015-07-15 2017-01-19 Otis Elevator Company Elevator control system
US20180186602A1 (en) * 2015-07-01 2018-07-05 Peter Herkel Elevator control system and elevator system comprising same
WO2020079314A1 (en) * 2018-10-16 2020-04-23 Kone Corporation Arrangement for transferring transportation infrastructure control data within a shared data network
EP3651419A1 (de) * 2018-11-09 2020-05-13 Otis Elevator Company Verwaltung eines in einer verkettung verbundenen kommunikationsnetzwerks von aufzugsvorrichtungen mit redundanten datenpfaden

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180186602A1 (en) * 2015-07-01 2018-07-05 Peter Herkel Elevator control system and elevator system comprising same
WO2017008849A1 (en) * 2015-07-15 2017-01-19 Otis Elevator Company Elevator control system
WO2020079314A1 (en) * 2018-10-16 2020-04-23 Kone Corporation Arrangement for transferring transportation infrastructure control data within a shared data network
EP3651419A1 (de) * 2018-11-09 2020-05-13 Otis Elevator Company Verwaltung eines in einer verkettung verbundenen kommunikationsnetzwerks von aufzugsvorrichtungen mit redundanten datenpfaden

Similar Documents

Publication Publication Date Title
US11440773B2 (en) Automatic rescue operation in an elevator system
AU2015367707B2 (en) Method for operating an electronic safety system with temporary subscribers
US20230024201A1 (en) Elevator communication system
EP3904259A1 (de) Aufzugskommunikationssystem
US20210339978A1 (en) Elevator communication system
US20210339976A1 (en) Elevator communication system
US11407613B2 (en) Elevator communication system
EP3904255A1 (de) Aufzugsystem
EP3904257A1 (de) Aufzugskommunikationssystem und verfahren zum einrichten eines solchen aufzugskommunikationssystems
US20230373749A1 (en) Elevator communication system, and a method and an apparatus in an elevator system
EP3904256A1 (de) Aufzugsystem
US20230373750A1 (en) Elevator communication system, a method and an apparatus
US20240182261A1 (en) Elevator system
US11380190B2 (en) Safety communication in an elevator communication system
US20230373754A1 (en) Elevator communication system, a method and an apparatus
EP3995425A1 (de) Zentrales aufzugverwaltungssystem
US20230373748A1 (en) Elevator communication system, a method and an apparatus
WO2022228650A1 (en) A conveyor communication system and a conveyor system

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

B565 Issuance of search results under rule 164(2) epc

Effective date: 20201117

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20220504