Elevator communication system

Abstract

According to an aspect, there is provided an elevator communication system. The system comprises an elevator controller, a multi-drop Ethernet bus segment reachable by the elevator controller, and a plurality of elevator system nodes connected to at least one multi-drop Ethernet bus segment configured to communicate over the multi-drop Ethernet bus, wherein the elevator system nodes are reachable by the elevator controller over the multi-drop Ethernet bus segment.

Description

Technical Field

[0001] This application relates to the field of elevator communication systems. Background Technology

[0002] In modern elevator systems, an increasing amount of data is sent and received by different entities within the system. For example, an elevator controller may receive information from call buttons and then control the elevator drive to respond to calls, or it may receive information from safety circuits and then control one or more entities within the elevator system based on that information. These are just some possible examples of how information is received and / or sent within an elevator system.

[0003] A key characteristic of modern elevator systems is that they can incorporate multiple different internal data transmission schemes. This means that multiple different communication stacks and physical layers can be used simultaneously. Using multiple different internal data transmission schemes can lead to complex and inefficient solutions.

[0004] Therefore, a scheme that mitigates at least one of these disadvantages would be beneficial. Summary of the Invention

[0005] According to a first aspect, an elevator communication system is provided, comprising an elevator controller, at least one multipoint Ethernet bus segment accessible by the elevator controller, and a plurality of elevator system nodes connected to and configured to communicate via the at least one multipoint Ethernet bus segment, wherein the elevator system nodes can reach the elevator controller via the at least one multipoint Ethernet bus segment. Preferably, the plurality of elevator system nodes are connected to the same bus segment of the multipoint Ethernet bus, such that only one bus node is active at a time, while other bus nodes on the same segment are in a high-impedance state.

[0006] In an embodiment of the first aspect, it further includes at least one point-to-point Ethernet bus and at least one connection unit, wherein the at least one connection unit includes a first port connected to a multipoint Ethernet bus in at least one multipoint Ethernet bus segment and a second port connected to a point-to-point Ethernet bus in at least one point-to-point Ethernet bus segment.

[0007] In an embodiment of the first aspect, at least one point-to-point Ethernet bus includes a first point-to-point Ethernet bus facing the elevator car, and at least one multipoint Ethernet bus segment includes an elevator car segment, wherein a connection unit disposed in the elevator car includes a first port connected to the elevator car segment and a second port connected to the point-to-point Ethernet bus. According to an example embodiment, the point-to-point Ethernet bus is located in the travel cable of the elevator car.

[0008] In an embodiment of the first aspect, at least one point-to-point Ethernet bus includes a second point-to-point Ethernet bus, at least one multipoint Ethernet bus segment includes at least one hoistway segment, each hoistway segment includes at least one hoistway node, wherein the connection unit associated with the hoistway segment includes a first port connected to the hoistway segment and a second port connected to the second point-to-point Ethernet bus.

[0009] In an embodiment of the first aspect, at least one multipoint Ethernet bus segment comprises multiple chained multipoint Ethernet bus segments forming a hoistway segment including at least one hoistway node, such that a communication unit interconnects two consecutive hoistway segments to extend the range of the hoistway segment.

[0010] In an embodiment of the first aspect, at least one multipoint Ethernet bus segment includes a multipoint Ethernet bus segment that forms a layer station segment connected to a hoistway node, wherein the hoistway node interconnects the multipoint Ethernet bus segments to which the hoistway node is connected to the layer station segment.

[0011] In an embodiment of the first aspect, at least one multipoint Ethernet bus segment includes a multipoint Ethernet bus segment forming a hoistway segment, the hoistway segment including at least one hoistway node configured to communicate through the hoistway segment, wherein the at least one multipoint Ethernet bus segment includes corresponding layer segments respectively connected to each of the at least one hoistway node, wherein the hoistway node interconnects the layer segments to which the hoistway node is connected to the hoistway segment.

[0012] In an embodiment of the first aspect, the elevator communication system includes a point-to-point Ethernet bus accessible via a first port associated with the elevator controller, and a multipoint Ethernet bus segment in at least one multipoint Ethernet bus segment accessible via a second port associated with the elevator controller.

[0013] In an implementation of the first aspect, at least one of the at least one multipoint Ethernet bus segments is configured to cover a separate functional segment of the elevator system.

[0014] In the first implementation, the individual functional section includes one of the mechanical area section, machine room section, hoistway section, landing section, pit section, and car section.

[0015] In the first embodiment, the elevator communication system also includes an elevator safety controller connected to a point-to-point Ethernet bus, which can be reached via at least one multipoint Ethernet bus segment.

[0016] In the first embodiment, the elevator communication system also includes an elevator group controller connected to the elevator controller.

[0017] In an embodiment of the first aspect, the elevator communication system also includes a network analyzer configured to analyze bus traffic, the network analyzer being communicatively connected to the elevator controller.

[0018] In an embodiment of the first aspect, the elevator communication system further includes a network interface unit communicatively connected to the elevator controller, which is capable of connecting to an external communication network.

[0019] In the implementation of the first aspect, each of the elevator system nodes is configured to interface with at least one of the following: elevator fixing device, elevator sensor, elevator safety device, and elevator control device.

[0020] In the implementation of the first aspect, at least one wellhead node is repeated.

[0021] In an implementation of the first aspect, at least one repeating shaft node is connected to another location in a layer section outside the shaft node.

[0022] In the implementation of the first aspect, the shaft segments are repeated, and the repeated shaft nodes are connected to the repeated shaft segments.

[0023] In an implementation of the first aspect, in some multipoint bus segments, data frames may contain security-related information. In some multipoint bus segments, data frames may contain non-security-related information. In some multipoint bus segments, data frames may contain both security-related and non-security-related information.

[0024] According to a second aspect, a method is provided for introducing a new elevator system component into an elevator control system including an Ethernet bus. The method includes: connecting an elevator system bus node to a multi-point Ethernet bus segment associated with the Ethernet bus; connecting the new elevator system component to the bus node; having the bus node transmit the operating characteristics and network address of the new elevator system component to a configuration controller via the Ethernet bus; and having the configuration controller generate configuration data based on the operating characteristics and physical address of the new elevator system component.

[0025] In a second embodiment, the method further includes configuring at least one of the elevator controller software and new elevator system components based on configuration data.

[0026] In the second implementation, the configuration controller is a remote server or cloud computing entity.

[0027] In the second implementation, the controller is configured as an elevator controller.

[0028] In the second implementation, the new bus node is configured to communicate with the configuration controller using the Ethernet protocol.

[0029] In the second implementation, the new elevator system components include one of the following: a display, a destination call panel, a car call button, a safety contact, a voice intercom system, and a camera. Attached Figure Description

[0030] The accompanying drawings, included to provide a further understanding of the invention and forming part of this specification, illustrate embodiments of the invention and, together with the description, help to explain the principles of the invention. In the drawings:

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

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

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

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

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

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

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

[0038] Figure 1H A portion of an elevator communication system according to another example embodiment is shown.

[0039] Figure 1I A portion of an elevator communication system according to another example embodiment is shown.

[0040] Figure 2 A method for introducing new elevator system components into an elevator control system including an Ethernet bus, according to an example embodiment, is shown.

[0041] Figure 3A and 3B An example of adding a new elevator system component to an elevator control system according to an example embodiment is shown. Detailed Implementation

[0042] The following description illustrates an elevator communication system including an elevator controller, at least one multipoint Ethernet bus segment reachable from the elevator controller, and multiple elevator system nodes connected to and configured to communicate via the at least one multipoint Ethernet bus segment, wherein the elevator system nodes can reach the elevator controller via the at least one multipoint Ethernet bus segment. The illustrated scheme allows, for example, different functional parts of the elevator communication system to be classified into separate multipoint Ethernet bus segments. The illustrated scheme also provides, for example, a simple and efficient method for adding new elevator system nodes to the elevator communication system.

[0043] In the example embodiments, the various embodiments discussed below can be used in an elevator system that includes elevators adapted to and capable of transferring passengers between floors in a building in response to a service request. In another example embodiment, the various embodiments discussed below can be used in an elevator system that includes elevators adapted to and capable of automatically transferring passengers between floors in response to a service request.

[0044] Figure 1A An elevator communication system according to an example embodiment is illustrated. The elevator communication system includes an elevator controller 100. The elevator communication system may also include one or more multipoint Ethernet bus segments 108A, 108B (e.g., in 10BASE-T1S form) reachable from the elevator controller 100, and a plurality of elevator system nodes 104A, 104B, 104C, 106A, 106B, 106C, which are connected to the multipoint Ethernet bus segments 108A, 108B and configured to communicate via the multipoint Ethernet buses 108A, 108B. The elevator system nodes 104A, 104B, 104C, 106A, 106B, 106C can reach the elevator controller 100 via the multipoint Ethernet bus segments 108A, 108B. Elevator system nodes connected to the same multipoint Ethernet bus segment can be configured such that one elevator system node is active at a time, while other elevator system nodes on the same multipoint Ethernet bus segment are in a high-impedance state.

[0045] In an example embodiment, the elevator communication system may include a point-to-point Ethernet bus 110 and at least one connection unit 102A, 102B, 102C. Each connection unit includes a first port connected to a corresponding multipoint Ethernet bus segment 108A, 108B and a second port connected to the point-to-point Ethernet bus 110. Therefore, by using the connection units 102A, 102B, 102C, one or more multipoint Ethernet bus segments 108A, 108B can be connected to the point-to-point Ethernet bus 110. The connection units 102A, 102B, 102C may, for example, be switches. Furthermore, the point-to-point Ethernet bus 110 may be connected to the elevator controller 100. The point-to-point Ethernet bus 110 may be, for example, a 100BASE-TX or 10BASE-T1L point-to-point Ethernet bus. The multipoint Ethernet bus segments 108A, 108B may include, for example, a 10BASE-T1S multipoint Ethernet bus.

[0046] In an example embodiment, elevator system nodes 104A, 104B, 104C, 106A, 106B, and 106C can be configured to interface with at least one of the elevator fixing device, elevator sensor, elevator safety device, and elevator control device. Furthermore, in this example embodiment, the same cables can be used to power the nodes. In another example embodiment, elevator system nodes 104A, 104B, 104C, 106A, 106B, and 106C may include shaft nodes, and multiple shaft nodes can form a shaft segment, such as multi-point Ethernet bus segments 108A and 108B.

[0047] Figure 1B An elevator communication system according to another example embodiment is illustrated. The elevator communication system includes an elevator controller 100. The elevator communication system may also include one or more multipoint Ethernet bus segments 108A, 108B reachable from the elevator controller 100, and a plurality of elevator system nodes 104A, 104B, 104C, 106A, 106B, 106C configured to communicate via multipoint Ethernet bus segments 108A, 108B, wherein the elevator system nodes 104A, 104B, 104C reach the elevator controller 100 via multipoint Ethernet bus segments 108A, 108B. The elevator communication system may also include an elevator group controller 112 connected to the elevator controller 100. The elevator controller 100 may include a switch or router 102D that connects the elevator controller 100 to the internal Ethernet network of the elevator communication system.

[0048] In an example embodiment, the elevator communication system may include a point-to-point Ethernet bus 110 and at least one connection unit 102A, 102B, 102C, each including a first port connected to a corresponding multipoint Ethernet bus segment 108A, 108B and a second port connected to the point-to-point Ethernet bus 110. Therefore, by using the connection units 102A, 102B, 102C, one or more multipoint Ethernet bus segments 108A, 108B can be connected to the point-to-point Ethernet bus 110. The connection units 102A, 102B, 102C may refer to, for example, a switch, hub, or router. Furthermore, the point-to-point Ethernet bus 110 may be connected to the elevator controller 100. The point-to-point Ethernet bus 110 may be, for example, a 100BASE-TX or 10BASE-T1L point-to-point Ethernet bus. The multipoint Ethernet bus segments 108A, 108B may include, for example, a 10BASE-T1S multipoint Ethernet bus.

[0049] In an example embodiment, elevator system nodes 104A, 104B, 104C, 106A, 106B, and 106C can be configured to interface with at least one of the elevator fixing device, elevator sensor, elevator safety device, and elevator control device. Furthermore, in this example embodiment, the same cables can be used to power the nodes. In another example embodiment, elevator system nodes 104A, 104B, 104C, 106A, 106B, and 106C may include shaft nodes, and multiple shaft nodes can form a shaft segment, such as multi-point Ethernet bus segments 108A and 108B.

[0050] The elevator communication system may include an elevator safety controller 114. The elevator safety controller 114 can be connected to a point-to-point Ethernet bus 110 via a connection unit 102E. This means that elevator system nodes 104A, 104B, 104C, 106A, 106B, and 106C can send information to the elevator safety controller 114 via the common point-to-point Ethernet bus 110, and vice versa. For example, elevator system nodes 104A, 104B, 104C, 106A, 106B, and 106C can send information from sensors or fixtures to the elevator controller 100 or the elevator safety controller 114, and receive information from it to control, for example, actuator configuration of fixtures. At least some of the elevator system nodes 104A, 104B, 104C, 106A, 106B, and 106C can be safety nodes according to IEC 61508 SIL Level 3, having a safety processing unit and a separate communication controller. Data from the safety processing unit may be sent only to the elevator safety controller 114. Safety nodes can be configured to interface with elevator safety devices, such as safety sensors or safety contacts that indicate elevator safety, such as landing door contacts, door lock contacts, overspeed regulator contacts, and buffer contacts. Safety nodes can also be configured to communicate with the elevator safety controller 114. To establish secure communication, different types of data checks can be used in the communication, such as checksums, error detection and / or correction algorithms.

[0051] Figure 1C An elevator communication system according to another example embodiment is illustrated. The elevator communication system includes an elevator controller 100. The elevator communication system may also include one or more multipoint Ethernet bus segments 108A, 108B, 108C, 124A, 124B, 124C reachable from the elevator controller 100, and a plurality of elevator system nodes 104A, 104B, 104C, 106A, 106B, 106C, 120A-120F, 124A, 124B, 124C, 126A, 126B, 126C, configured to communicate via multipoint Ethernet bus segment 108A, 108B, 108C, 124 .... 08A, 108B, 108C, 124A, 124B, and 124C communicate with each other. Among them, elevator system nodes 104A, 104B, 104C, 106A, 106B, 106C, 120A, 120F, 124A, 124B, 124C, 126A, 126B, and 126C can reach elevator controller 100 through multi-point Ethernet bus segments 108A, 108B, 108C, 124A, 124B, and 124C.

[0052] In an example embodiment, the elevator communication system may include a point-to-point Ethernet bus 110 and at least one connection unit 102A, 102B, which includes a first port connected to multipoint Ethernet bus segments 108A, 108B and a second port connected to the point-to-point Ethernet bus 110. Therefore, by using the connection units 102A, 102B, one or more multipoint Ethernet bus segments 108A, 108B can be connected to the point-to-point Ethernet bus 110. The connection units 102A, 102B may refer to, for example, a switch, hub, or router. Furthermore, the point-to-point Ethernet bus 110 may be connected to the elevator controller 100. The point-to-point Ethernet bus 110 may be, for example, a 100BASE-TX or 10BASE-T1L point-to-point Ethernet bus. The multipoint Ethernet bus segments 108A, 108B may include, for example, a 10BASE-T1S multipoint Ethernet bus.

[0053] In the example embodiment, elevator system nodes 120A-120F, 126A, 126B, and 126C are configured to interface with at least one of the elevator fixing device, elevator sensor, elevator safety device, and elevator control device. Furthermore, in the example embodiment, the same cables can be used to power the nodes.

[0054] The elevator communication system may include an elevator safety controller 114. The elevator safety controller 114 can be connected to a point-to-point Ethernet bus 110 via a connection unit 102E. This means that elevator system nodes 104A, 104B, 104C, 106A, 106B, 106C, 120A-120F, 126A, 126B, and 126C can send information to the elevator safety controller 114 via the common point-to-point Ethernet bus 110, and vice versa. For example, elevator system nodes 104A, 104B, 104C, 106A, 106B, 106C, 120A-120F, 126A, 126B, and 126C can send, for example, information from sensors or fixtures to the elevator controller 100 or the elevator safety controller 114, and receive information from it to control, for example, actuator configuration of fixtures, etc. At least some of the elevator system nodes 104A, 104B, 104C, 106A, 106B, 106C, 120A-120F, 126A, 126B, and 126C can be safety nodes according to IEC 61508 SIL 3 level, with a safety processing unit and a separate communication controller. Data from the safety processing unit can be sent only to the elevator safety controller 114. The safety nodes can be configured to interface with elevator safety devices, such as safety sensors or safety contacts indicating elevator safety, such as landing door contacts, door lock contacts, overspeed regulator contacts, buffer contacts, etc. The safety nodes can be configured to communicate with the elevator safety controller 114. To establish safe communication, different types of data checks can be used in the communication, such as checksums, error detection and / or correction algorithms, etc.

[0055] The elevator communication system may also include an elevator drive connected to the elevator controller 100. Furthermore, the elevator communication system may include a network interface unit 118 communicatively connected to the elevator controller 100, which enables connection to an external communication network. The network interface unit 118 may include, for example, a router or gateway.

[0056] The elevator communication system may also include a point-to-point Ethernet bus 122, which provides connectivity to the elevator car 116 and various components associated with the elevator car 116. The elevator car 116 may include one or more elevator car nodes 126A, 126B, 126C that can be connected to a connection unit 102F, such as a switch. In an example embodiment, elevator car nodes 126A, 126B, 126C may be connected to the connection unit 102F via a multipoint Ethernet bus segment 108C, thereby forming an elevator car segment. In an example embodiment, the point-to-point Ethernet bus 122 is located in the travel cable of the elevator car 116.

[0057] Communication within an elevator communication system is achieved using at least one point-to-point Ethernet bus and at least one multipoint Ethernet bus segment, allowing the formation of various segments. For example, elevator system nodes 120A and 120B can form the first floor segment, elevator system nodes 120C and 120D can form the second floor segment, elevator system nodes 120D and 120F can form the third floor segment, hoistway nodes 104A, 104B, and 104C can form the first hoistway segment, hoistway nodes 106A, 106B, and 106C can form the second hoistway segment, elevator car nodes 126A, 126B, and 126C can form elevator car segment 108C, and the elevator drive can form a mechanical segment. Each segment 108A, 108B, and 108C is implemented using a separate multipoint Ethernet bus.

[0058] As shown in Figure 1, hoistway nodes 106A, 106B, and 106C interconnect hoistway segment 108B, to which hoistway nodes 106A, 106B, and 106C are connected, to landing segments 124A, 124B, and 124C. In other words, hoistway nodes 106A, 106B, and 106C can include or be used as switches for landing segments 124A, 124B, and 124C. This provides a simple solution for adding new elevator system nodes to the elevator communication system. It also provides a solution where a single elevator system node can act as a switch or repeater for nearby elevator system components (e.g., one or more call buttons, one or more displays, one or more destination control panels, one or more cameras, intercom devices, etc.) to another multipoint Ethernet bus segment.

[0059] The elevator communication system may also include a network analyzer configured to analyze bus traffic, which is communicatively connected to the elevator controller.

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

[0061] The elevator communication system includes an elevator controller 100. The elevator communication system may also include a first multipoint Ethernet bus segment 134A (e.g., in 10BASE-T1S format) reachable from the elevator controller 100, and a second multipoint Ethernet bus segment 134B (e.g., in 10BASE-T1S format) reachable from the elevator controller 100. A first group of elevator system nodes 130A, 130B, and 130C can be configured to communicate via the first multipoint Ethernet bus segment 134A, and a second group of elevator system nodes 132A, 132B, and 132C can be configured to communicate via the second multipoint Ethernet bus segment 134B. The first multipoint Ethernet bus segment 134A can be reached through a first port associated with the elevator controller 100, and the second multipoint Ethernet bus segment 134B can be reached through a second port associated with the elevator controller 100. Elevator system nodes connected to the same multipoint Ethernet bus segment can be configured such that one elevator system node is active at a time, while other elevator system nodes on the same multipoint Ethernet bus segment are in a high-impedance state.

[0062] In the example embodiment, elevator system nodes 130A, 130B, 130C, 132A, 132B, and 132C can be configured to interface with at least one of the elevator fixing device, elevator sensor, elevator safety device, and elevator control device. Furthermore, in the example embodiment, the same cables can be used to power the nodes.

[0063] In an example embodiment, the first multipoint Ethernet bus segment 134A may be a car segment, and the second multipoint Ethernet bus segment 134B may be a hoistway segment. In other example embodiments, each multipoint Ethernet bus segment may be configured to cover a separate functional segment of the elevator system, and the separate functional segment may include, for example, one of a mechanical segment, hoistway segment, landing segment, and car segment. Furthermore, even... Figure 1D Only two multipoint Ethernet segments 134A and 134B reachable by the elevator controller 100 are shown. In other embodiments, the elevator communication system may have more than two multipoint Ethernet bus segments.

[0064] Figure 1EAn elevator communication system according to another example embodiment is illustrated. The elevator communication system includes an elevator controller 100. The elevator communication system may also include one or more multipoint Ethernet bus segments 142A, 142B reachable from the elevator controller 100, and a plurality of elevator system nodes 138A, 138B, 138C, 140A, 140B, 140C, 140B, 140C, configured to communicate via multipoint Ethernet bus segments 142A, 142B, wherein the elevator system nodes 138A, 138B, 138C, 140A, 140B, 140C, 140B, 140C can reach the elevator controller 100 via multipoint Ethernet bus segments 142A, 142B. The elevator communication system may also include an elevator group controller 112 connected to the elevator controller 100. The elevator controller 100 may include a switch or router 102D that connects the elevator controller 100 to the internal Ethernet network of the elevator communication system.

[0065] In an example embodiment, the elevator communication system may include a point-to-point Ethernet bus 136 and at least one connection unit 144A, 144B, which includes a first port connected to a multipoint Ethernet bus segment 142B and a second port connected to a point-to-point Ethernet bus 110. Therefore, by using the connection units 144A, 144B, one or more multipoint Ethernet bus segments 142B can be connected to the point-to-point Ethernet bus 110. The connection units 144A, 144B may refer to, for example, a switch, hub, or router. Furthermore, the point-to-point Ethernet bus 136 may be connected to the elevator controller 100. The point-to-point Ethernet bus 136 may be, for example, a 100BASE-TX or 10BASE-T1L point-to-point Ethernet bus. The multipoint Ethernet bus segments 142A, 142B may include, for example, a 10BASE-T1S multipoint Ethernet bus.

[0066] One or more multipoint Ethernet bus segments can be directly connected to the elevator controller 100. Figure 1E An example is shown in which only one multipoint Ethernet bus segment 142B is connected to the elevator controller 100 via switch 144A.

[0067] In an example embodiment, elevator system nodes 138A, 138B, 138C, 140A, 140B, and 140C can be configured to interface with at least one of the elevator fixing device, elevator sensor, elevator safety device, and elevator control device. Furthermore, in the example embodiment, the same cables can be used to power the nodes. In another example embodiment, elevator system nodes 140A, 140B, and 140C can be hoistway nodes, and they can form hoistway segment 142B.

[0068] The elevator communication system may include an elevator safety controller 114. The elevator safety controller 114 can be connected to a point-to-point Ethernet bus 136 and a multipoint Ethernet bus segment 142A via a connection unit 102E. This means that elevator system nodes 138A, 138B, 138C, 140A, 140B, and 140C can send information to the elevator safety controller 114 via the common point-to-point Ethernet bus 136 and multipoint Ethernet bus segment 142A, and vice versa. For example, elevator system nodes 138A, 138B, 138C, 140A, 140B, and 140C can send information from sensors or fixtures to the elevator controller 100 or the elevator safety controller 114, and receive information from them to control, for example, actuator configuration of fixtures. At least some of the elevator system nodes 138A, 138B, 138C, 140A, 140B, and 140C can be safety nodes according to IEC 61508 SIL 3 level, having a safety processing unit and a separate communication controller. Data from the safety processing unit can be sent only to the elevator safety controller 114. Safety nodes can be configured to interface with elevator safety devices, such as safety sensors or safety contacts indicating elevator safety, such as landing door contacts, door lock contacts, overspeed regulator contacts, and buffer contacts. Safety nodes can be configured to communicate with the elevator safety controller 114. To establish secure communication, different types of data checks can be used in the communication, such as checksums, error detection and / or correction algorithms.

[0069] Figure 1F An elevator communication system according to another example embodiment is illustrated. The elevator communication system includes an elevator controller 100. The elevator communication system may also include a multipoint Ethernet bus segment 146A (e.g., in the form of 10BASE-T1S) forming a hoistway segment reachable by the elevator controller 100. The hoistway segment 146 includes hoistway nodes 148A, 148B, and 148C configured to communicate via the multipoint Ethernet bus segment 146A.

[0070] Elevator system nodes 150A, 150B, and 150C, i.e., landing nodes, are connected to multi-point Ethernet bus segment 152A, i.e., the landing segment. Similarly, elevator system nodes 150D, 150E, and 150F are connected to multi-point Ethernet bus segment 152B, and elevator system nodes 150G, 150H, and 150I are connected to multi-point Ethernet bus segment 152C. Hoistway nodes 148A, 148B, and 148C can be configured as switches or hubs, enabling communication between hoistway segment 146 and the corresponding landing segments 152A, 152B, and 152C. Landing nodes connected to the same multi-point Ethernet bus segment can be configured such that one landing node is active at a time, while other landing nodes on the same multi-point Ethernet bus segment are in a high-impedance state.

[0071] In the example embodiment, floor nodes 150A, 150B, 150C, 150D, 150E, 150F, 150G, 150H, and 150I can be configured to interface with at least one of the elevator fixing device, elevator sensor, elevator safety device, and elevator control device. Furthermore, in the example embodiment, the same cables can be used to power the nodes.

[0072] Figure 1G An elevator communication system according to another example embodiment is shown. Figure 1G The embodiments shown include those concerning Figure 1E All components discussed. Additionally... Figure 1G A repeater 152 is shown that connects another shaft segment 156 to shaft segment 146. (See diagram.) Figure 1G As shown, multiple station sections 158A, 158B, and 158C are connected to shaft nodes 160A, 160B, and 160C. This is consistent with the above information regarding... Figure 1F The discussion is similar. By using more than one repeater, the physical range of multipoint Ethernet bus segments 146 and 156 can be extended.

[0073] Figure 1H A portion of an elevator communication system according to another example embodiment is shown. The elevator communication system includes a hoistway node 160, which can be connected to a point-to-point Ethernet bus or a multipoint Ethernet bus, as described above. A landing segment 168, i.e., a multipoint Ethernet bus segment, is connected to the hoistway node 160. The landing segment 168 also includes a node 164D, which can also be connected to a duplicate hoistway node 162. Thus, for example, even in the event of such a connection error, connection errors in landing nodes 164A, 164B, and 164C can be identified, and communication can continue.

[0074] Figure 1I A portion of an elevator communication system according to another example embodiment is shown. Figure 1H Compared to the previous embodiment, in Figure 1I The middle shaft section has also been repeated.

[0075] The elevator communication system includes shaft nodes 160A, 106B, and 106C, which can be connected to a point-to-point Ethernet bus or a multipoint Ethernet bus, as described above. Landing segments 168A, 168B, and 168C, i.e., multipoint Ethernet bus segments, are connected to the corresponding shaft nodes 160A, 160B, and 160C. Landing segments 168A, 168B, and 168C also include nodes 164D, 170D, and 172D, which can also be connected to repeating shaft nodes 162A, 162B, and 162C. Furthermore, the connections from shaft nodes 162A, 162B, and 162C to the elevator controller 100 can be separate from the connections from shaft nodes 160A, 106B, and 160C to the elevator controller 100. Thus, even in the case of such connection errors, the connection errors of station nodes 164A-164D, 170A-170D, and 172A-172D can be identified, and communication can continue. This means that even if a shaft segment fails, communication can still be maintained through the shaft bus (i.e., a multi-point Ethernet bus segment).

[0076] Figure 2 A method for introducing new elevator system components into an elevator control system including an Ethernet bus, according to an example embodiment, is shown.

[0077] In step 200, the elevator system bus node is connected to a multipoint Ethernet bus segment associated with the Ethernet bus. The multipoint Ethernet bus segment can be any... Figure 1A –1I is one of the discussions.

[0078] In step 202, new elevator system components are connected to the elevator system bus node. In other words, elevator system components are connected to a multi-point Ethernet bus segment via the elevator system bus node.

[0079] In section 204, the elevator system bus node sends the operating characteristics and physical address of a new elevator system component to the configuration controller via a multipoint Ethernet bus. The new elevator system component contains information about its features, characteristics, and capabilities. This information is transmitted to the configuration controller via the multipoint Ethernet bus node. Control tasks for the elevator controller can be assigned based on the capabilities of the transmitted devices. Furthermore, the physical location of the elevator system component connected to the multipoint Ethernet bus node can be determined. Additionally, when a message is sent from the multipoint Ethernet bus node to the configuration controller, switches and routers automatically provide address information so that the receiver knows the network address of the sender (i.e., the elevator system component) when it receives the message.

[0080] In step 206, the configuration controller generates configuration data based on the operating characteristics and physical addresses of the new elevator system components. The configuration controller can also use this configuration data to configure the elevator controller software and at least one of the new elevator system components. After configuration, the new elevator system node can be configured to communicate with the configuration controller using the Ethernet protocol.

[0081] In one example embodiment, the configuration controller is a remote server or cloud computing entity. In another example embodiment, the configuration controller is an elevator controller.

[0082] In an example embodiment, the new elevator system components may include one of the following: a display, a destination call panel, a car call button, a safety contact, a voice intercom system, and a camera.

[0083] The illustrated scheme achieves a solution in which new elevator system components can be easily and scalably configured when added to the control system.

[0084] Figure 3A and 3B An example of adding a new elevator system component to an elevator control system according to an example embodiment is shown.

[0085] Figure 3A An example is shown where new elevator system components (such as displays, destination call panels, car call buttons, safety contacts, voice intercom systems, and cameras) are connected to a multipoint Ethernet bus segment 304A via a new node 300B. In a simplified example, two nodes 300A and 300C are already connected to the multipoint Ethernet bus segment 304A. In this example, the physical connection between the nodes is a dual-connector scheme, where the first connector of a node connects to a previous node, and the second connector of a node connects to a subsequent node. Adding the new node 300B is straightforward and can be done by placing the new node 300B between two existing nodes 300A and 300C and adjusting the wiring.

[0086] Figure 3B An example is shown where new elevator system components (such as displays, destination call panels, car call buttons, safety contacts, voice intercom systems, and cameras) are connected to a multipoint Ethernet bus segment 304B via a new node 302B. The multipoint Ethernet bus segment 304B is implemented to allow the addition of new nodes 302B without altering the wiring of existing nodes 302A and 302C.

[0087] At least some of the example embodiments discussed above enable seamless data transfer between elevator system equipment and any other equipment or system. Furthermore, a common protocol stack can be used for all communications. At least some of the example embodiments discussed above can also provide solutions offering high security and / or easy scalability. At least some of the example embodiments described above can also provide solutions offering high performance. Furthermore, at least some of the example embodiments described above can implement a solution where elevator system nodes can communicate with elevator controllers and remote servers / clouds using Ethernet protocols without any protocol stack conversion. Moreover, at least some of the exemplary embodiments described above enable, for example, the classification of different functional parts of the elevator communication system into separate multi-point Ethernet bus segments.

[0088] 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 relating to the various methods described herein. This information may be stored in one or more memories, 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 memories 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.

[0089] All or part of the example embodiments can be conveniently implemented using one or more general-purpose processors, microprocessors, digital signal processors, microcontrollers, etc., programmed according to the teachings of the example embodiments. As those skilled in the art will understand, a programmer of ordinary skill can easily prepare suitable software based on the teachings of the example embodiments. Additionally, the example embodiments can be implemented by preparing application-specific integrated circuits or by a suitable network interconnecting conventional component circuits, as understood by those skilled in the art of electronics. Therefore, the examples are not limited to any particular combination of hardware and / or software. Examples stored on any or a combination of computer-readable media may include software for controlling components of the example embodiments, driving components of the example embodiments, enabling components of the example embodiments to interact with a human user, etc. Such computer-readable media may also include computer programs 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. In the context of this document, "computer-readable medium" can be any medium or apparatus that can contain, store, communicate, propagate, or transmit instructions used by or in connection with an instruction execution system, apparatus, or device (such as a computer). Computer-readable media can include computer-readable storage media, which can be any medium or apparatus that can contain or store instructions used by or in connection with an instruction execution system, apparatus, or device (such as a computer). Computer-readable media can include any suitable medium that participates in providing instructions to a processor for execution. Such media can take many forms, including but not limited to non-volatile media, volatile media, transmission media, etc.

[0090] Although the essential novel features applicable to its preferred embodiments have been shown and described, it should be understood that those skilled in the art can make various omissions and substitutions, as well as changes in form and detail, to the described apparatus and methods without departing from the spirit of this disclosure. For example, all combinations of those elements and / or method steps explicitly intended to perform substantially the same function in substantially the same manner to achieve the same result are within the scope of this disclosure. Furthermore, it should be recognized that structures and / or elements and / or method steps shown and / or described in conjunction with any of the disclosed forms or embodiments can be incorporated as a general matter of design choice into any other disclosed or described or implied form or embodiment.

[0091] The applicant hereby independently discloses each individual feature described herein, as well as any combination of two or more such features, such that, based on common general knowledge of those skilled in the art, these features or combinations of features can be implemented on the basis of this specification as a whole, regardless of whether such features or combinations of features solve any problem disclosed herein, and are not limited to the scope of the claims. The applicant notes that the disclosed aspects / embodiments may consist of any such individual features or combinations of features. In view of the foregoing description, it will be apparent to those skilled in the art that various modifications can be made within the scope of this disclosure.

Claims

1. An elevator communication system, comprising: an elevator controller (100); at least one multi-drop Ethernet bus segment (108A, 108B, 108C, 134A, 134B, 142A, 142B, 146, 156, 168, 168A-168C) to which the elevator controller (100) has access; and a plurality of elevator system nodes (104A-104C, 106A-106C, 126A-126C, 120A-120F, 130A-130C, 132A-132C, 138A-138C, 140A-140C, 148A-148C, 150A-150I, 164A-164D, 170A-170D, 172A-172D) connected to the at least one multi-drop Ethernet bus segment (108A, 108B, 108C, 134A, 134B, 142A, 142B, 146, 156, 168, 168A-168C) and configured to communicate over the at least one multi-drop Ethernet bus segment (108A, 108B, 108C, 134A, 134B, 142A, 142B, 146, 156, 168, 168A-168C), wherein the elevator system nodes (104A-104C, 106A-106C, 120A-120F, 126A-126C, 130A-130C, 132A-132C, 138A-138C, 140A-140C, 148A-148C, 150A-150I, 164A-164D, 170A-170D, 172A-172D) have access to the elevator controller (100) over the at least one multi-drop Ethernet bus segment (108A, 108B, 108C, 134A, 134B, 142A, 142B, 146, 156, 168, 168A-168C), at least one point-to-point Ethernet bus (110, 122, 136) and at least one connection unit (102A, 102B, 102C, 102F, 144A, 144B), wherein the at least one connection unit (102A, 102B, 102C, 102F, 144A, 144B) comprises a first port of a multi-drop Ethernet bus segment (108A, 108B, 108C, 142B) connected to the at least one multi-drop Ethernet bus segment (108A, 108B, 108C, 134A, 134B, 142A, 142B, 146, 156, 168, 168A-168C) and a second port of a point-to-point Ethernet bus connected to the at least one point-to-point Ethernet bus (110, 122, 136), wherein the at least one point-to-point Ethernet bus (110, 122, 136) comprises a first point-to-point Ethernet bus (122) towards the elevator car (116) and the at least one multi-drop Ethernet bus segment (108A, 108B, 108C, 134A, 134B, 142A, 142B, 146, 156, 168, 168A-168C) comprises an elevator car segment (108C), wherein a connection unit (102F) provided in the elevator car (116) comprises a first port connected to the elevator car segment (108C) and a second port connected to the first point-to-point Ethernet bus (122), wherein the first point-to-point Ethernet bus is located in a travel cable of the elevator car.

2. The elevator communication system of claim 1, wherein, The at least one point-to-point Ethernet bus (110, 122, 136) comprises a second point-to-point Ethernet bus (110, 136), the at least one multi-drop Ethernet bus segment (108A, 108B, 108C, 134A, 134B, 142A, 142B, 146, 156, 168, 168A-168C) comprises at least one hoistway segment (108A, 108B, 142B), each hoistway segment comprising at least one hoistway node (104A-104C, 106A-106B, 140A-140C), wherein a connection unit (102A, 102B, 144A) associated with the hoistway segment (108A, 108B, 142B) comprises a first port connected to the hoistway segment (108A, 108B, 142B) and a second port connected to the second point-to-point Ethernet bus (110, 136).

3. The elevator communication system of any of claims 1-2, wherein, The at least one multi-drop Ethernet bus segment (108A, 108B, 108C, 134A, 134B, 142A, 142B, 146, 156, 168, 168A-168C) comprises a plurality of chained multi-drop Ethernet bus segments (146, 156) forming a hoistway segment comprising at least one hoistway node (148A-148C, 160A-160C), such that a communication unit (154) interconnects two consecutive hoistway segments (146, 156) to extend the range of the hoistway segment (146, 156).

4. The elevator communication system of claim 2, wherein, The at least one multi-drop Ethernet bus segment (108A, 108B, 108C, 134A, 134B, 142A, 142B, 146, 156, 168, 168A-168C) includes a multi-drop Ethernet bus segment (124A-124C, 152A-152C, 158A-158C) forming a landing segment connected to a hoistway node (106A-106B, 148A-148C, 160A-160C), wherein the hoistway node (106A-106B, 148A-148C, 160A-160C) interconnects the multi-drop Ethernet bus segment (108B, 146, 156) to which the hoistway node (106A-106B, 148A-148C, 160A-160C) is connected to the landing segment (124A-124C, 152A-152C, 158A-158C).

5. The elevator communication system of any of claims 1-2, wherein, The at least one multi-drop Ethernet bus segment (108A, 108B, 108C, 134A, 134B, 142A, 142B, 146, 156, 168, 168A-168C) includes a multi-drop Ethernet bus segment (146, 156) forming a hoistway segment including at least one hoistway node (148A-148C, 160A-160C) configured to communicate over the hoistway segment (146, 156); wherein the at least one multi-drop Ethernet bus segment (146, 156) includes a respective landing segment (152A-152C, 158A-158C) connected to each of the at least one hoistway node (148A-148C, 160A-160C), wherein the hoistway node (148A-148C, 160A-160C) interconnects the landing segment (152A-152C, 158A-158C) to which the hoistway node (148A-148C, 160A-160C) is connected to the hoistway segment (146, 156).

6. The elevator communication system of claim 2, wherein, The at least one hoistway node is duplicated.

7. The elevator communication system of claim 6, wherein, The at least one duplicated hoistway node (162) is connected to another location of the landing segment outside of the hoistway node (162).

8. The elevator communication system of claim 7, wherein, The hoistway segment (172A) is duplicated, and the duplicated hoistway node (162A-162C) is connected to the duplicated hoistway segment (172B).

9. The elevator communication system of any of claims 1-2, comprising a point-to-point Ethernet bus (136) accessible through a first port associated with the elevator controller (100), and a multi-drop Ethernet bus segment (142A) of at least one multi-drop Ethernet bus segment (108A, 108B, 108C, 134A, 134B, 142A, 142B, 146, 156, 168, 168A-168C) accessible through a second port associated with the elevator controller (100).

10. The elevator communication system of any of claims 1-2, wherein, At least one of the at least one multi-drop Ethernet bus segment (108A, 108B, 108C, 134A, 134B, 142A, 142B, 146, 156, 168, 168A-168C) is configured to cover a separate functional section of the elevator system.

11. The elevator communication system of claim 10, wherein, The separate functional section comprises one of a machinery area section, a machine room section, a hoistway section, a landing section, a pit section, and a car section.

12. The elevator communication system of any of claims 1-2, further comprising an elevator safety controller (114) connected to the elevator controller over a point-to-point Ethernet bus and reached over at least one multi-drop Ethernet bus segment (108A, 108B, 108C, 134A, 134B, 142A, 142B, 146, 156, 168, 168A-168C).

13. The elevator communication system of any of claims 1-2, further comprising: an elevator group controller (112) connected to the elevator controller (100).

14. The elevator communication system of any of claims 1-2, further comprising: a network analyzer configured to analyze bus traffic, the network analyzer communicatively connected to the elevator controller (100).

15. The elevator communication system of any of claims 1-2, further comprising: a network interface unit (118) communicatively connected to the elevator controller (100), the network interface unit (118) connectable to an external communication network.

16. The elevator communication system of any of claims 1-2, wherein, Each of the elevator system nodes (104A-104C, 106A-106C, 120A-120F, 126A-126C, 130A-130C, 132A-132C, 138A-138C, 140A-140C, 148A-148C, 150A-150I, 164A-164D, 170A-170D, 172A-172D) is configured to interface with at least one of an elevator fixture, an elevator sensor, an elevator safety device, and an elevator control device.

Images