Elevator communication system

Abstract

According to an aspect, an elevator communication system is provided. The system comprises a first elevator controller, a second elevator controller communicatively connected to the first elevator controller, a first Ethernet bus section connected to the first elevator controller, a second Ethernet bus section connected to the second elevator controller, and at least one elevator system node communicatively connected to the first elevator controller via the first Ethernet bus section and communicatively connected to the second elevator controller via the second Ethernet bus section.

Description

TECHNICAL FIELD

[0001] The present invention relates to the field of elevator communication systems. BACKGROUND

[0002] In modern elevator systems, more and more data is transmitted and received by different entities of the elevator system. For example, an elevator controller can receive information from a call button and then control an elevator drive to serve the call, or an elevator controller can receive information from a safety circuit and then control one or more entities of the elevator system based on the information. These are just some possible examples of receiving and / or transmitting information within an elevator system.

[0003] It is characteristic of modern elevator systems that the elevator system can comprise a plurality of different internal data transmission solutions. This can mean that a plurality of different protocol stacks and a plurality of different physical layers can be used at the same time. The use of a plurality of different internal data transmission solutions can lead to a complex and inefficient solution.

[0004] Furthermore, a redundant safety bus system can be implemented using, for example, a CAN protocol or a RS485 time triggered protocol (TTS). It has duplicate communication channels with the same structure and the same data communication. In this solution, two parallel communication channels are required for safety reasons. However, when an elevator communication system uses, for example, Ethernet bus-based communication, these techniques cannot be used.

[0005] It would therefore be advantageous if there were a solution that could at least alleviate one of these drawbacks. SUMMARY

[0006] According to a first aspect, there is provided an elevator communication system comprising a first elevator controller, a second elevator controller communicatively connected to the first elevator controller, a first Ethernet bus section connected to the first elevator controller, a second Ethernet bus section connected to the second elevator controller, and at least one elevator system node communicatively connected to the first elevator controller via the first Ethernet bus section and communicatively connected to the second elevator controller via the second Ethernet bus section. This makes it possible for the communication capabilities between the elements in the elevator communication system to be maintained even if one of the first or second Ethernet bus sections fails.

[0007] In an implementation form of the first aspect, the first Ethernet bus section comprises sequential bus segments interconnected by at least one switch, the first Ethernet bus section extending in a first elevator shaft, the second Ethernet bus section comprises sequential bus segments interconnected by at least one switch, the second Ethernet bus section extending in a second elevator shaft.

[0008] In an implementation form of the first aspect, the at least one elevator system node comprises a first pit station associated with the first Ethernet bus section and a second pit station associated with the second Ethernet bus section, and the first pit station associated with the first Ethernet bus section is communicatively connected to the second pit station associated with the second Ethernet bus section with a multi-drop Ethernet bus segment.

[0009] In an implementation form of the first aspect, the communication system comprises a shared Ethernet bus segment communicatively connected to the first Ethernet bus section and the second Ethernet bus section, wherein the at least one elevator system node is connected to the shared Ethernet bus segment.

[0010] In an implementation form of the first aspect, the shared Ethernet bus segment is connected to a switch of the first Ethernet bus section and a switch of the second Ethernet bus section.

[0011] In an implementation form of the first aspect, the sequential bus segments of the first Ethernet bus section comprise a point-to-point Ethernet bus segment between a first switch and a second switch and a first multi-drop Ethernet bus segment between the first switch and the second switch, wherein the sequential bus segments of the second Ethernet bus section comprise a point-to-point Ethernet bus segment between a third switch and a fourth switch and a second multi-drop Ethernet bus segment between the third switch and the fourth switch. The at least one elevator system node comprises a first node arranged in the first multi-drop Ethernet bus segment and a second node arranged in the second multi-drop Ethernet bus segment, and the elevator communication system further comprises a shared Ethernet bus segment configured between the first node and the second node.

[0012] In an implementation form of the first aspect, the elevator communication system further comprises a first multi-drop segment connected to a switch of the first Ethernet bus section (the first multi-drop segment containing the first node), a second multi-drop segment connected to a switch of the second Ethernet bus section (the second multi-drop segment containing the second node), and a shared Ethernet bus segment configured between the first node and the second node.

[0013] In an implementation form of the first aspect, the first node is configured to act as a coordinator and the second node is configured to act as a backup coordinator. The first node is configured to periodically monitor the second node to detect a loss of monitoring contact of the second node and instruct a farthest visible node in the shared Ethernet bus segment to terminate the shared Ethernet bus segment. The second node is configured to detect a loss of monitoring contact of the first node to set itself as a coordinator, instruct a farthest visible node in the shared Ethernet bus segment to terminate the shared Ethernet bus segment, and start switching traffic.

[0014] In the implementation of the first aspect, the first node is configured to regain monitoring contact with the second node, instruct the removal termination of the most distant visible node in the shared Ethernet bus segment, and the second node is configured to regain monitoring contact with the first node, instruct the removal termination of the most distant visible node in the shared Ethernet bus segment, and stop switching traffic.

[0015] In the implementation of the first aspect, the shared Ethernet bus segment includes a shared multipoint Ethernet bus segment.

[0016] According to the second aspect, an elevator system including the elevator communication system of the first aspect is provided.

[0017] In the second implementation, the elevator system includes multiple elevator cars configured to move independently within the same elevator shaft. Attached Figure Description

[0018] The accompanying drawings, which are provided to further illustrate the invention and form part of this specification, depict embodiments of the invention and, together with the description, help to explain the principles of the invention. In the drawings:

[0019] Figure 1A An elevator communication system according to an example embodiment is shown.

[0020] Figure 1B An elevator communication system according to another example embodiment is shown.

[0021] Figure 1C An elevator communication system according to another example embodiment is shown.

[0022] Figure 1D An elevator communication system according to another example embodiment is shown.

[0023] Figure 1E An elevator communication system according to another example embodiment is shown.

[0024] Figure 2 A device according to an example embodiment is shown. Detailed Implementation

[0025] An elevator communication system is described below, comprising a first elevator controller, a second elevator controller communicatively connected to the first elevator controller, a first Ethernet bus portion connected to the first elevator controller, a second Ethernet bus portion connected to the second elevator controller, and at least one elevator system node communicatively connected to the first elevator controller via the first Ethernet bus portion and communicatively connected to the second elevator controller via the second Ethernet bus portion. For example, the solution described can improve the reliability and availability of a full Ethernet elevator communication system. Furthermore, in the event of a single failure in the elevator communication system, elevator service and data communication within the elevator communication system do not need to be interrupted.

[0026] Furthermore, the term "communication connection" as used herein may mean that one element can be directly connected to another element, node, or bus, or that it can be indirectly connected to another element, node, or bus via a connecting element, node, or bus.

[0027] In example embodiments, the various embodiments discussed below can be used in elevator systems comprising at least one elevator, which is adapted and usable to transport passengers between floors of a building in response to service requests. In another example embodiment, the various embodiments discussed below can be used in elevator systems comprising at least one elevator, which is adapted and usable to automatically transport passengers between floors in response to service requests.

[0028] Figure 1A An elevator communication system according to an example embodiment is illustrated. The elevator communication system includes a first elevator controller 100 communicatively connected to a second elevator controller. The elevator communication system may further include an elevator group controller 104 communicatively connected to both elevator controllers 100, 102. In some embodiments, the elevator group controller 104 may be integrated into one of the elevator controllers 100, 102 so that the elevator controller runs group controller software to implement group controller functions.

[0029] The elevator communication system may include a first Ethernet bus portion 106A connected to a first elevator controller 100 and a second Ethernet bus portion 106B connected to a second elevator controller 102. The first Ethernet bus portion 106A may include sequential bus segments interconnected by at least one switch 108A-108C or other interconnection unit. The first Ethernet bus portion 106A may extend in a first elevator shaft. Similarly, the second Ethernet bus portion 106B may include sequential bus segments interconnected by at least one switch 110A-110C or other interconnection unit. The second Ethernet bus portion 106B may extend in a second elevator shaft.

[0030] The first Ethernet bus portion 106A may include a point-to-point Ethernet bus and at least one interconnecting connection unit 108A, 108B, 108C. The second Ethernet bus portion 106B may include a point-to-point Ethernet bus and at least one interconnecting connection unit 110A, 110B, 110C. For example, connection units 108A-108C and 110A-110C may refer to a switch. Furthermore, the point-to-point Ethernet bus may be a 100BASE-TX or 10BASE-SET1L point-to-point Ethernet bus.

[0031] The elevator communication system may include at least one elevator system node 112A, 112B, which is communicatively connected to a first elevator controller 100 via a first Ethernet bus portion 106A and communicatively connected to a second elevator controller 102 via a second Ethernet bus portion 106B. In an example embodiment, elevator system nodes 112A, 112B may refer to pit inspection nodes.

[0032] For example, the solution can improve the reliability and availability of a full Ethernet elevator communication system. Furthermore, in the event of a single failure in the elevator communication system, elevator service and data communication within the system do not need to be interrupted.

[0033] Figure 1B An elevator communication system according to an example embodiment is illustrated. The elevator communication system includes a first elevator controller 100 communicatively connected to a second elevator controller. The elevator communication system may further include an elevator group controller 104 communicatively connected to both elevator controllers 100, 102. In some embodiments, the elevator group controller 104 may be integrated into one of the elevator controllers 100, 102 so that the elevator controller also runs group controller software to implement group controller functions.

[0034] The elevator communication system may include a first Ethernet bus portion 106A connected to a first elevator controller 100 and a second Ethernet bus portion 106B connected to a second elevator controller 102. The first Ethernet bus portion 106A may include sequential bus segments interconnected by at least one switch 108A-108C or other interconnection unit. The first Ethernet bus portion 106A may extend in a first elevator shaft. Similarly, the second Ethernet bus portion 106B may include sequential bus segments interconnected by at least one switch 110A-110C or other interconnection unit. The second Ethernet bus portion 106B may extend in a second elevator shaft.

[0035] The first Ethernet bus portion 106A may include a point-to-point Ethernet bus and at least one interconnecting connection unit 108A, 108B, 108C. The second Ethernet bus portion 106B may include a point-to-point Ethernet bus and at least one interconnecting connection unit 110A, 110B, 110C. For example, connection units 108A-108C and 110A-110C may refer to a switch. Furthermore, the point-to-point Ethernet bus may be a 100BASE-TX or 10BASE-SET1L point-to-point Ethernet bus.

[0036] The elevator communication system further includes shared Ethernet bus segments 158A-158D, which are communicatively connected to a first Ethernet bus section 106A and a second Ethernet bus section 106B. One or more elevator system nodes 160A-160L can be connected to the shared Ethernet bus segments 158A-158D. The shared Ethernet bus segments 158A-158D can be connected to switches 108A-108C of the first Ethernet bus section 106A and to switches 110A-110C of the second Ethernet bus section 106B.

[0037] from Figure 1B As can be seen, each node in the elevator communication system is reachable via at least two different routes. For example, if the shared Ethernet bus segment 158A between node 160D and switch 110A of the second Ethernet bus section 106B fails, node 160D still communicates via switch 108A of the first Ethernet bus section 106A.

[0038] For example, the solution can improve the reliability and availability of a full Ethernet elevator communication system. Furthermore, in the event of a single failure in the elevator communication system, elevator services and data communication within the system do not need to be interrupted.

[0039] Figure 1C An elevator communication system according to an example embodiment is illustrated. The elevator communication system includes a first elevator controller 100 communicatively connected to a second elevator controller. The elevator communication system may further include an elevator group controller 104 communicatively connected to both elevator controllers 100, 102. In some embodiments, the elevator group controller 104 may be integrated into one of the elevator controllers 100, 102 so that the elevator controller also runs group controller software to implement group controller functions.

[0040] The elevator communication system may include a first Ethernet bus portion 162A connected to a first elevator controller 100 and a second Ethernet bus portion 162B connected to a second elevator controller 102. The first Ethernet bus portion 162A may include sequential bus segments interconnected by at least one switch 108A-108C or other interconnection unit. The first Ethernet bus portion 162A may extend in a first elevator shaft. Similarly, the second Ethernet bus portion 162B may include sequential bus segments interconnected by at least one switch 110A-110C or other interconnection unit. The second Ethernet bus portion 162B may extend in a second elevator shaft.

[0041] The first Ethernet bus portion 106A may include a point-to-point Ethernet bus and at least one interconnecting connection unit 108A, 108B, 108C. The second Ethernet bus portion 106B may include a point-to-point Ethernet bus and at least one interconnecting connection unit 110A, 110B, 110C. For example, connection units 108A-108C and 110A-110C may refer to a switch.

[0042] The sequential bus segments of the first Ethernet bus segment 162A may include a point-to-point Ethernet bus segment between the first switch 108A and the second switch 108B, and a first multipoint Ethernet bus segment 164A between the first switch 108A and the second switch 108B. Similarly, the sequential bus segments of the second Ethernet bus segment 162B may include a point-to-point Ethernet bus segment between the third switch 110A and the fourth switch 110B, and a second multipoint Ethernet bus segment 164B between the third switch 110A and the fourth switch 110B. The point-to-point Ethernet bus may be, for example, a 100BASE-TX or 10BASE-T1L point-to-point Ethernet bus. The multipoint Ethernet bus segments 164A and 164B may include, for example, a 10BASE-T1S multipoint Ethernet bus.

[0043] Node 116A may be located in a first multipoint Ethernet bus segment 164A, and node 118A may be located in a second multipoint Ethernet bus segment 164B. For example, nodes 116A and 118A may refer to floor control panels configured on each floor. The elevator communication system may further include a shared Ethernet bus segment 140A configured between nodes 116A and 118A.

[0044] One or more nodes 120A, 122A, 120B, and 122B can be directly connected to nodes 116A and 118A, such as displays, one or more call buttons, one or more push-button switches, one or more on / off indicators, etc. Furthermore, one or more of the nodes shown can be configured to connect to at least one of elevator clamps, elevator sensors, elevator safety devices, and elevator control devices.

[0045] The elements between nodes 116A and 118A can be similarly arranged between nodes 116B, 118B and nodes 116C, 118C.

[0046] In addition, such as Figure 1C One or more nodes shown can send information from sensors or fixtures to elevator controllers 100, 102 and receive information from them for control purposes, such as actuator configuration of fixtures, etc. Figure 1C One or more nodes shown can be safety nodes conforming to IEC 61508 SIL Level 3, with a safety processing unit and a separate communication controller. Safety nodes can be configured to connect to elevator safety devices, such as safety sensors or safety contacts indicating elevator safety, such as elevator door contacts, door lock contacts, overspeed regulator contacts, buffer contacts, etc.

[0047] like Figure 1C As shown, nodes 116A-116C and 118A-118C can contain or act as switches for multipoint segments 140A-140C, i.e., landing segments. This provides a simple solution for adding new elevator system nodes to an elevator communication system. It also makes possible a solution where a single elevator system node can act as a switch or repeater for another multipoint Ethernet bus segment, while nearby elevator system components, such as call buttons, displays, destination control panels, cameras, and intercom devices, can be connected to that other multipoint Ethernet bus segment.

[0048] In addition, from Figure 1C As can be seen, each critical node in the elevator communication system is reachable via at least two different routes. For example, the solution described can improve the reliability and availability of a full Ethernet elevator communication system. Furthermore, in the event of a single failure in the elevator communication system, elevator services and data communication within the system do not need to be interrupted.

[0049] Figure 1D An elevator communication system according to an example embodiment is illustrated. The elevator communication system includes a first elevator controller 100 communicatively connected to a second elevator controller. The elevator communication system may further include an elevator group controller 104 communicatively connected to both elevator controllers 100, 102. In some embodiments, the elevator group controller 104 may be integrated into one of the elevator controllers 100, 102 so that the elevator controller also runs group controller software to implement group controller functions.

[0050] The elevator communication system may include a first Ethernet bus portion 142A connected to a first elevator controller 100 and a second Ethernet bus portion 146A connected to a second elevator controller 102. The first Ethernet bus portion 142A may include a first multipoint Ethernet bus segment connected to the elevator controller 100, and the second Ethernet bus portion 146A may include a second multipoint Ethernet bus segment connected to the elevator controller 102. The multipoint Ethernet bus segments 142A and 146A may include, for example, a 10BASE-T1S multipoint Ethernet bus.

[0051] The first Ethernet bus portion 106A may include one or more nodes, such as hoistway nodes 144A-144C. Similarly, the second Ethernet bus portion 146A may include one or more nodes, such as hoistway nodes 144A-144C. Similarly, the second Ethernet bus portion 146A may include one or more nodes, such as hoistway nodes 148A-148C. The first Ethernet bus portion 142A may extend in the first elevator shaft, and the second Ethernet bus portion 146A may extend in the second elevator shaft. In the example embodiment, a single hoistway node may be arranged in each floor.

[0052] The elevator communication system may further include shared Ethernet bus segments 152A-152C that are communicatively connected to the first Ethernet bus portion 142A and the second Ethernet bus portion 146A. One or more elevator system nodes 150A-150L may be connected to the shared Ethernet bus segments 150A-150C. Figure 1D As shown, shared Ethernet bus segments 150A-150C can be connected to hoistway nodes 144A-144C and 148A-148C. Shared Ethernet bus segments 152A-152C may include multipoint Ethernet bus segments, which may contain, for example, 10BASE-T1S multipoint Ethernet buses.

[0053] like Figure 1D As shown, hoistway nodes 144A-144C and 148A-148C can include or serve as switches for hoistway multi-point segments 152A-152C, i.e., landing segments. This provides a simple solution for adding new elevator system nodes to an elevator communication system. It also makes possible a solution where a single elevator system node can act as a switch or repeater for another multi-point Ethernet bus segment, while nearby elevator system components, such as call buttons, displays, destination control panels, cameras, and intercom devices, can be connected to that other multi-point Ethernet bus segment.

[0054] For example, the solution can improve the reliability and availability of a full Ethernet elevator communication system. Furthermore, in the event of a single failure in the elevator communication system, elevator services and data communication within the system do not need to be interrupted.

[0055] Figure 1E An elevator communication system according to another example embodiment is shown. Figure 1E The illustrated embodiments include those with Figure 1D All elements related to the discussion. Furthermore, Figure 1E Repeater 154A is shown, which connects another hoistway multipoint Ethernet segment 142B to multipoint Ethernet segment 142A. (See diagram) Figure 1E As shown, the shared layer station section 152D-152F connects to shaft nodes 144D-144F and 148D-148F, as discussed above. Figure 1D Similarly, by using one or more repeaters, the physical coverage of multipoint Ethernet bus segments 142A and 146A can be extended.

[0056] Although not in Figures 1A-1E The description further indicates that the elevator communication system may include a point-to-point Ethernet bus, which provides connectivity from elevator controllers 100, 102 to the elevator car and various components associated with the elevator car. The elevator car may include a connection unit, such as a switch, to which one or more elevator car nodes may be connected. In an example embodiment, elevator car nodes may be connected to the connection unit via a multipoint Ethernet bus segment, thereby forming an elevator car segment. In an example embodiment, the point-to-point Ethernet bus resides in the moving cable of the elevator car.

[0057] In the example embodiment, the nodes connected to the shared Ethernet bus segment, such as the first nodes 116A, 116B, 116C, 144A, 144B, 144C, 144D, 144E, and 144F, can be configured as coordinating nodes, and the second nodes 118A, 118B, 118C, 148A, 148B, 148C, 148D, 148E, and 148F can be configured as backup coordinators. Monitoring functionality can be configured so that the first nodes 116A, 116B, 116C, 144A, 144B, 144C, 144D, 144E, and 144F can be configured to periodically monitor the second nodes 118A, 118B, 118C, 148A, 148B, 148C, 148D, 148E, and 148F to detect any activity on the second nodes 118A, 118B, 118C, and 148A. The loss of monitoring contact in segments 148B, 148C, 148D, 148E, and 148F instructs the furthest visible node in shared Ethernet bus segments 140A, 140B, 140C, 152A, 152B, 152C, 152D, and 152E to terminate the shared Ethernet bus segments 140A, 140B, 140C, 152A, 152B, 152C, 152D, 152E, and 152F. This could occur, for example, when a node in a shared Ethernet bus segment fails. The second nodes 118A, 118B, 118C, 148A, 148B, 148C, 148D, 148E, and 148F can be configured to detect the loss of monitoring contact with the first nodes 116A, 116B, 116C, 144A, 144B, 144C, 144D, 144E, and 144F, set themselves as coordinators, instruct the furthest visible node among the shared Ethernet bus segments 140A, 140B, 140C, 152A, 152B, 152C, 152D, 152E, and 152F to terminate the shared Ethernet bus segments 140A, 140B, 140C, 152A, 152B, 152C, 152D, 152E, and 152F, and then begin switching traffic.

[0058] To some extent, when another fault in a faulty node or shared Ethernet bus segment 140A, 140B, 140C, 152A, 152B, 152C, 152D, 152E, 152F is repaired, the first nodes 116A, 116B, 116C, 144A, 144B, 144C, 144D, 144E, 144F are configured to regain monitoring access to the second nodes 118A, 118B, 118C, 148A, 148B, 148C, 148D, 148E, 148F, and guide the removal of the furthest visible node in the shared Ethernet bus segment 140A, 140B, 140C, 152A, 152B, 152C, 152D, 152E, 152F from the termination. Similarly, the second nodes 118A, 118B, 118C, 148A, 148B, 148C, 148D, 148E, and 148F can be configured to regain monitoring contact with the first nodes 116A, 116B, 116C, 144A, 144B, 144C, 144D, 144E, and 144F to indicate the removal termination of the most distant visible node among the shared Ethernet bus segments 140A, 140B, 140C, 152A, 152B, 152C, 152D, 152E, and 152F, and to stop the switching traffic.

[0059] This allows the first and second nodes to quickly and effectively detect failures in the shared Ethernet bus segment, and the elevator communication system can remain functional even in the event of a failure, as data can be transmitted using an alternative route.

[0060] The elevator communication system discussed above can be implemented in an elevator system that includes one or more elevator shafts. Furthermore, in an example embodiment, the elevator system may include multiple elevator cars configured to move independently within the same elevator shaft.

[0061] Figure 2 This illustrates that, according to an example embodiment, it can be used as Figures 1A-1E The illustrated node operates on device 200. Device 200 may include at least one processor 202. Device 200 may also include at least one memory 204. Memory 204 may include program code 206, which, when executed by processor 202, causes device 200 to execute at least one example embodiment. Examples of the example embodiments and various aspects of the subject matter may be included in any suitable device, such as a server, elevator controller, or workstation capable of executing the processes of the example embodiments. The example embodiments may also store information related to the various processes described herein. Although controller 300 is described as a single device, it is worth noting that, where applicable, the functionality of controller 300 may be distributed across multiple devices.

[0062] The example embodiments may be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. The example embodiments may store information related to the various methods described herein. This information may be stored in one or more memories 204, such as a hard disk, optical disk, magneto-optical disk, RAM, etc. One or more databases may store information used to implement the example embodiments. The databases may be organized using data structures (e.g., records, tables, arrays, fields, graphs, trees, lists, etc.) included in one or more memory or storage devices listed herein. The methods described with respect to the example embodiments may 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.

[0063] Processor 202 may include one or more general-purpose processors, microprocessors, digital signal processors, microcontrollers, etc., programmed according to the teachings of the example embodiments, which will be appreciated by those skilled in the art of software. Based on the teachings of the example embodiments, programmers with ordinary skills can easily write suitable software that will be appreciated by those skilled in the art of software. Furthermore, the example embodiments may be implemented by the fabrication of application-specific integrated circuits or by connecting suitable conventional component circuit networks, which will be appreciated by those skilled in the art of electrical engineering. Therefore, these examples are not limited to any particular combination of hardware and / or software. Stored on any combination of computer-readable media, the examples may include components for controlling the example embodiments, components for driving the example embodiments, software for enabling the components of the example embodiments to interact with a human user, etc. The computer-readable medium may also include a computer program for performing all or part of the processes performed in implementing the example embodiments (if the processes are distributed). The computer code device of the examples may include any suitable interpretable or executable code mechanism, including but not limited to scripts, interpreters, dynamic link libraries (DLLs), Java classes and applets, complete executable programs, etc.

[0064] As described above, components of the example embodiment may include a computer-readable medium or memory 204 for storing instructions written according to the teachings and for storing data structures, tables, records, and / or other data described herein. In one example embodiment, application logic, software, or instruction set is maintained on any of a variety of conventional computer-readable media. Within the scope of this document, "computer-readable medium" can be any medium or means that can contain, store, communicate, propagate, or transmit 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 can contain or store 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 any suitable medium that participates in providing instructions for execution to a processor. Such media can take many forms, including but not limited to non-volatile media, volatile media, transmission media, etc.

[0065] Device 200 may include a communication interface 208 configured to enable device 200 to send and / or receive information from other devices.

[0066] The device 200 includes means for performing at least one method described herein. In one example, the method may include at least one processor 202 and at least one memory 204 including program code 206, configured to cause the controller 200 to execute the method when executed by at least one processor 202.

[0067] While the essential new features applied to its preferred embodiments have been shown, described, and pointed out, it is understood that various omissions, substitutions, and variations in the form and details of the described apparatus and methods can be made by those skilled in the art without departing from the spirit of the disclosure. For example, it is explicitly intended that all combinations of these elements and / or method steps, performing substantially the same function in substantially the same manner to achieve the same result, are within the scope of the disclosure. Furthermore, it should be recognized that structures and / or elements and / or method steps associated with any disclosed form or embodiment can be incorporated as general matters of design choice into any other disclosed or described or suggested form or embodiment.

[0068] One or more embodiments discussed above can be implemented in a multi-car elevator system. In a multi-car elevator system, multiple elevator cars are adapted to move sequentially along a common circular path in the same cyclic direction. The elevator cars will move upwards along a first shaft and downwards along a second parallel shaft. Transfers from one shaft to another will be carried out horizontally via transfer stations, which are located at least at the top and bottom end terminals of the shafts. In some embodiments, the propulsion force of the elevator cars may be provided by linear motors. Each elevator car may have a mover that works in conjunction with a common stator beam, allowing the elevator cars to be controlled individually. A first elevator controller may be located in or associated with the first shaft. A second elevator controller may be located in or associated with the second shaft. The second elevator controller may be communicatively connected to the first elevator controller. A first Ethernet bus portion may be connected to the first elevator controller and may extend in the first shaft. A second Ethernet bus portion may be connected to the second elevator controller and may extend in the second shaft. At least one elevator system node may be communicatively connected to the first elevator controller via the first Ethernet bus portion and to the second elevator controller via the second Ethernet bus portion. The first and second elevator controllers can be configured to control a multi-car elevator system. Therefore, they can all or separately contain the required elevator control functions.

[0069] The applicant hereby discloses in isolation each individual feature described herein, as well as any combination of two or more such features, provided that such features or combinations can be performed as a whole on the basis of this specification and in accordance with the common common sense of those skilled in the art, regardless of whether such features or combinations of features solve any problem disclosed herein, and without being limited by the scope of the claims. The applicant notes that the disclosed aspects / embodiments may include any such individual features or combinations of features. Based on the foregoing description, various modifications can be made within the scope of the disclosure by those skilled in the art.

Claims

1. An elevator communication system, comprising: First elevator controller (100); The second elevator controller (102) is communicatively connected to the first elevator controller (100); A first Ethernet bus portion (106A, 162A) is connected to a first elevator controller (100). The first Ethernet bus portion (106A) includes sequential bus segments interconnected by at least one switch (108A-108C). The first Ethernet bus portion (106A) extends in the first elevator shaft. A second Ethernet bus section (106B, 162B) is connected to a second elevator controller (102). The second Ethernet bus section (106B) includes sequential bus segments interconnected by at least one switch (110A-110C). The second Ethernet bus section (106B) extends in the second elevator shaft. At least one elevator system node (112A, 112B, 120A, 120B, 122A, 122B, 150A-150I, 156A-156I, 160A-160L) is communicatively connected to a first elevator controller (100) via a first Ethernet bus section (106A, 162A) and communicatively connected to a second elevator controller (102) via a second Ethernet bus section (106B, 162B). The communication system includes shared Ethernet bus segments (114, 140A-140C, 152-152F, 158A-158D, 164A, 164B), which are communicatively connected to a first Ethernet bus portion (106A, 162A) and a second Ethernet bus portion (106B, 162B). At least one elevator system node (112A, 112B, 120A, 120B, 122A, 122B, 150A-150I, 156A-156I, 160A-160L) is connected to shared Ethernet bus segments (114, 140A-140C, 152f, 158A-158D, 164A, 164B), 152-152f, 158a-158d, 164a, 164b).

2. The elevator communication system according to claim 1, wherein: in, The at least one elevator system node (112A, 112B, 120A, 120B, 122A, 122B, 150A-150I, 156A-156I, 160A-160L) includes a first pit inspection station (112A) associated with a first Ethernet bus portion (106A) and a second pit inspection station (112B) associated with a second Ethernet bus portion (106B); The first pit inspection station (112A) associated with the first Ethernet bus section (106A) is communicatively connected to the second pit inspection station (112B) associated with the second Ethernet bus section (106B) via a multi-point Ethernet bus segment (114).

3. The elevator communication system according to claim 1, wherein the shared Ethernet bus segment (158A-158D) is connected to the switch (108A-108C) of the first Ethernet bus section (106A) and the switch (110A-110C) of the second Ethernet bus section (106B).

4. The elevator communication system according to claim 1 or 2, wherein the sequential bus segment of the first Ethernet bus portion (162A) includes a point-to-point Ethernet bus segment between the first switch (108A) and the second switch (108B) and a first multipoint Ethernet bus segment between the first switch (108A) and the second switch (108B), wherein, The sequential bus segments of the second Ethernet bus segment (162B) include a point-to-point Ethernet bus segment between the third switch (110A) and the fourth switch (110B) and a second multipoint Ethernet bus segment between the third switch (110A) and the fourth switch (110B); Among them, at least one elevator system node (112A, 112B, 120A, 120B, 122A, 122B, 150A-150I, 156A-156I, 160A-160L) includes a first node (116A) disposed in a first multi-point Ethernet bus segment (164A) and a second node (118A) disposed in a second multi-point Ethernet bus segment (164B); The elevator communication system further includes a shared Ethernet bus segment (140A) configured between the first node (116A) and the second node (118A).

5. The elevator communication system according to claim 1 or 2, further comprising: The first multi-point segment (164A) is connected to a switch (10A) of the first Ethernet bus section (106A), and the first multi-point segment (164A) includes a first node (116A); The second multipoint segment (164B) is connected to the switch (110A) of the second Ethernet bus section (106B), and the second multipoint segment (164B) includes the second node (118A); A shared Ethernet bus segment (140A) is configured between the first node (116A) and the second node (118A).

6. The elevator communication system according to claim 5, wherein the first node (116A) is configured to act as a coordinator, and the second node (118A) is configured to act as a backup coordinator. in, The first node (116A) is configured to periodically monitor the second node (118A) to detect a loss of monitoring contact with the second node (118B) and instruct the furthest visible node in the shared Ethernet bus segment (140A) to terminate the shared Ethernet bus segment (140A). The second node (118A) is configured to detect the loss of monitoring contact with the first node (116A), set itself as the coordinator, instruct the farthest visible node in the shared Ethernet bus segment (140A) to terminate the shared Ethernet bus segment (140A), and begin switching traffic.

7. The elevator communication system according to claim 6, wherein... The first node (116A) is configured to regain monitoring contact with the second node (118A) to instruct the furthest visible node in the shared Ethernet bus segment (140A) to remove the termination. The second node (118A) is configured to regain monitoring contact with the first node (116A) to instruct the furthest visible node in the shared Ethernet bus segment (140A) to remove the termination and stop the switching traffic.

8. The elevator communication system according to claim 1 or 2, wherein the shared Ethernet bus segments (114, 140A-140C, 152-152F, 158A-158D, 164A, 164B) include shared multipoint Ethernet bus segments.

9. An elevator system comprising the elevator communication system according to any one of claims 1-8.

10. The elevator system of claim 9, comprising a plurality of elevator cars configured to move independently within the same elevator shaft.

Images