Method for defining load data of an elevator car and elevator supervising unit

Abstract

This invention relates to a method for defining load data for an elevator car (102). The method includes: obtaining (210) speed data representing the speed of an asynchronous elevator hoisting motor (110) arranged to drive the elevator car (102) along an elevator shaft (104) by at least one motion sensor device (550); and defining (220) the load data of the elevator car (102) based on the obtained speed data, the direction of elevator drive, and predefined reference data. The invention also relates to an elevator monitoring unit (120), a computer program product, and a system for defining load data for an elevator car (102).

Description

Technical Field

[0001] This invention generally relates to the technical field of elevator systems. In particular, this invention relates to monitoring elevator systems. Background Technology

[0002] An elevator system typically includes at least one elevator car and an elevator hoisting motor arranged to drive the elevator car between multiple floors along an elevator shaft. The elevator system may also typically include one or more internal sensor devices for providing various operational data of the elevator system. Operational data may include, for example, load data for at least one elevator car. For example, the elevator system may include load weighting devices arranged to each elevator car to provide load data for said elevator cars. Load data can be used, for example, for people flow monitoring, detecting occupancy, etc. However, there may be situations where the elevator control system of the elevator system is inaccessible and therefore the load data for at least one elevator car is unavailable, such as in the case of remote monitoring or maintenance of a third-party elevator system. Alternatively or additionally, there may be situations where it may be necessary to define alternative methods for the load data of at least one elevator car.

[0003] Therefore, an alternative solution is needed to define the load data for elevator cars. Summary of the Invention

[0004] The following is a simplified overview to provide a basic understanding of some aspects of various embodiments of the invention. This overview is not a comprehensive summary of the invention. It is neither intended to identify key or essential elements of the invention nor to depict its scope. The following overview presents only some concepts of the invention in a simplified form as a prelude to a more detailed description of exemplary embodiments of the invention.

[0005] The object of this invention is to provide a method, elevator monitoring unit, computer program product, and system for defining load data of an elevator car. Another object of this invention is that the method, elevator monitoring unit, computer program product, and system for defining load data of an elevator car enable the definition of load data of an elevator car without being connected to an elevator control system that includes an elevator car.

[0006] The object of the present invention is achieved by the method, elevator monitoring unit, computer program product and system as defined by the respective independent claims.

[0007] According to a first aspect, a method for defining load data of an elevator car is provided, wherein the method includes: obtaining speed data representing the speed of an asynchronous elevator hoisting motor by at least one motion sensor device, the asynchronous elevator hoisting motor being arranged to drive the elevator car along an elevator shaft; and defining load data of the elevator car based on the obtained speed data, the direction of elevator drive, and predefined reference data.

[0008] Predefined reference data may include scaling factors and sliding data under the condition that the load is known in the direction the elevator is driven.

[0009] Predefined reference data may also include synchronization speed data.

[0010] When the elevator is driven upwards, the load data of the elevator car can be defined according to the following formula:

[0011] m load =(s up_load -s up_known ) / k up +m known ,

[0012] Where s up_known The upward slip data is given under known load conditions, k up It is the upward scaling factor, s up_load It is the upward slip data given the load data to be defined, and m known The mass of the known load is given, where the upward slip data, in the case of the load data to be defined, can be included in the obtained speed data or defined based on the obtained speed data and the synchronous speed data.

[0013] Alternatively, when the elevator is driven in the downward direction, the load data of the elevator car can be defined according to the following formula:

[0014] m load =(s down_load -s down_known ) / k down +m known ,

[0015] Among them, s down_known The downward slip data, k, is given under a known load. down It is a downward scaling factor, and s down_load It is the downward slip data given the load data to be defined, wherein the downward slip data given the load data to be defined can be included in the obtained speed data or defined based on the obtained speed data and synchronous speed data.

[0016] Reference data can be defined during the learning drive of the elevator car.

[0017] The learning drive may include: obtaining first reference speed data representing the speed of the elevator hoisting motor when the elevator car with a first known load is driven up and down along the elevator shaft; obtaining second reference speed data representing the speed of the elevator hoisting motor when the elevator car with a second known load is driven up and down along the elevator shaft; and defining reference data based on the obtained first reference speed data and the obtained second reference speed data.

[0018] Defining reference data during learning-driven processes may include: defining synchronous speed data based on the obtained first reference speed data or the obtained second reference speed data; defining slip data in both directions under a first known load based on the defined synchronous speed data and the obtained first reference speed data; defining slip data in both directions under a second known load based on the defined synchronous speed data and the obtained second reference speed data; and defining a scaling factor based on the defined slip data upward or downward under a known load and the known first and second loads.

[0019] Alternatively, defining reference data during learning-driven operations may include defining a scaling factor based on upward or downward slip data under known loads and known first and second loads, wherein the upward and downward slip data under the first known load may be included in the obtained first reference velocity data, and the upward and downward slip data under the second known load may be included in the second reference velocity data.

[0020] At least one motion sensor device may be included in the elevator monitoring unit without being communicatively connected to the control system of the elevator system including the elevator car.

[0021] The hoisting motor of an asynchronous elevator can be a direct online (DOL) induction motor or a frequency-controlled induction motor.

[0022] According to a second aspect, an elevator monitoring unit is provided for defining load data of an elevator car, wherein the monitoring unit includes: at least one motion sensor device configured to acquire speed data representing the speed of an asynchronous elevator hoisting motor arranged to drive the elevator car along an elevator shaft; and a processing unit configured to: acquire the speed data from the at least one motion sensor device; and define the load data of the elevator car based on the acquired speed data, the direction of elevator drive, and predefined reference data.

[0023] Predefined reference data may include scaling factors and sliding data under the condition that the load is known in the direction the elevator is driven.

[0024] Predefined reference data may also include synchronization speed data.

[0025] When the elevator is driven upwards, the processing unit can be configured to define the load data of the elevator car according to the following formula:

[0026] m load =(s up_load -s up_known ) / k up +m known ,

[0027] Among them, s up_known The upward slip data is given under known load conditions, k up It is the upward scaling factor, s up_load It is the upward slip data given the load data to be defined, wherein the upward slip data given the load data to be defined can be included in the obtained speed data or defined based on the obtained speed data and synchronous speed data.

[0028] Alternatively, when the elevator is driven in the downward direction, the processing unit can be configured to define the elevator car load data according to the following formula:

[0029] m load =(s down_load -s down_known ) / k down +m known ,

[0030] Among them, s down_known The downward slip data, k, is given under a known load. down It is a downward scaling factor, and s down_load It is the downward slip data given the load data to be defined, wherein the downward slip data given the load data to be defined can be included in the obtained speed data or defined based on the obtained speed data and synchronous speed data.

[0031] The processing unit can be configured to define reference data during the learning drive of the elevator car.

[0032] The learning drive may include: a processing unit configured to: obtain first reference speed data representing the speed of the elevator hoisting motor when an elevator car with a first known load is driven up and down along the elevator shaft; obtain second reference speed data representing the speed of the elevator hoisting motor when the elevator car with a second known load is driven up and down along the elevator shaft; and define reference data based on the obtained first reference speed data and the obtained second reference speed data.

[0033] Defining reference data during learning-driven processes may include a processing unit configured to: define synchronous speed data based on acquired first reference speed data or acquired second reference speed data; define slip data in two directions under a first known load based on the defined synchronous speed data and the acquired first reference speed data; define slip data in two directions under a second known load based on the defined synchronous speed data and the acquired second reference speed data; and define a scaling factor based on the defined slip data up or down under a known load and the known first and second loads.

[0034] Alternatively, defining reference data during learning-driven processes may include: the processing unit being configured to define a scaling factor based on upward or downward slip data under known loads and known first and second loads, wherein the upward and downward slip data under the first known load can be included in the obtained first reference velocity data, and the upward and downward slip data under the second known load can be included in the second reference velocity data.

[0035] The elevator monitoring unit may not have a communication connection with the control system of the elevator system, including the elevator car.

[0036] The hoisting motor of an asynchronous elevator can be a direct online (DOL) induction motor or a frequency-controlled induction motor.

[0037] According to a third aspect, a computer program product for defining load data of an elevator car is provided, which, when executed by a computer, causes the computer to perform the method described above.

[0038] According to the fourth aspect, a system is provided, wherein the system includes an elevator monitoring unit as described above and an external computing unit configured to: receive load data of an elevator car from the elevator monitoring unit, and store and analyze the received load data of the elevator car.

[0039] When read in conjunction with the accompanying drawings, the various exemplary and non-limiting embodiments of the invention, as well as their additional objects and advantages, will be best understood from the following description of specific exemplary and non-limiting embodiments.

[0040] The verbs “comprising” and “including” are used herein as open-ended restrictions, neither excluding nor requiring the presence of any unlisted features. Unless otherwise expressly stated, the features recited in the dependent claims may be freely combined with each other. Furthermore, it should be understood that the use of “a” or “an,” i.e., the singular form, throughout this document does not exclude a plurality. Attached Figure Description

[0041] The embodiments of the invention are illustrated in the accompanying drawings by way of example and not limitation.

[0042] Figure 1 An example of an elevator system is illustrated schematically.

[0043] Figure 2 An example of a method for defining load data for an elevator car is illustrated schematically.

[0044] Figure 3 An example of a learning-driven approach used to define reference data is illustrated.

[0045] Figure 4 Another example of learning-driven learning used to define reference data is illustrated.

[0046] Figure 5 An example of a component of an elevator monitoring unit is shown schematically.

[0047] Figure 6 An example of a system including an elevator monitoring unit and an external computing unit is illustrated schematically. Detailed Implementation

[0048] Figure 1 An example of an elevator environment (i.e., elevator system 100) is schematically shown, in which elevator monitoring unit 120 can be implemented as described below. Elevator system 100 includes an elevator car 102 configured to travel along elevator shaft 104 between multiple floors (i.e., floors 106a-106n). Elevator system 100 also includes elevator hoisting machinery 108, which includes an elevator hoisting motor 110 arranged to drive elevator car 102 along elevator shaft 104. Elevator hoisting machinery 108 may also include one or more known elevator hoisting machinery entities, such as one or more pulleys and / or rollers, brakes, etc., which are not shown for clarity. Figure 1As shown in the diagram. The elevator hoisting mechanism 108 may be located in a machine room 112 situated above the elevator shaft 104, or alternatively, the elevator hoisting mechanism 108 may be located within the elevator shaft 104 (e.g., in a machine room-less elevator system). The elevator hoisting motor 110 is an asynchronous motor. The asynchronous elevator hoisting motor 110 may be an induction motor, such as a direct-on-line (DOL) induction motor (e.g., a single-speed DOL induction motor or a dual-speed DOL induction motor) or a frequency-controlled induction motor (e.g., an open-loop scalar-controlled induction motor). The elevator system 100 also includes an elevator control system 114, which is configured to at least partially control the operation of the elevator system 100. The elevator control system 114 may reside, for example, in a machine room 112. Figure 1 The elevator system 100 may be located in machine room 112 or in one of the floors 106a-106n of elevator system 100. Elevator control system 114 may include, for example, an elevator drive unit configured to control elevator hoist motor 110 to drive (i.e., move) elevator car 102 along elevator shaft 104. In the case of a DOL induction motor, elevator control system 114 may include a controllable switch, such as a contactor, between elevator hoist motor 110 and a three-phase power supply network. Alternatively, for example, if variable speed is required, the induction motor may be controlled by a frequency controller (e.g., an inverter). Elevator system 100 may also include one or more known elevator-related entities, such as elevator suspension devices for carrying (i.e., suspending) elevator car 102, such as ropes or belts, as well as counterweights, safety circuits and devices, elevator door systems, etc., which are not explicitly shown in the text. Figure 1 As shown in the image.

[0049] The elevator monitoring unit 120 can be implemented as an external entity to the elevator system 100. This means that the elevator monitoring unit 120 is not connected (i.e., has no communication connection) to the elevator control system 114. In other words, the elevator monitoring unit 120 cannot access the elevator control system 114, which results in the elevator monitoring unit 120 being unable to access any data obtained or defined by the elevator control system 114. Therefore, if the elevator monitoring unit 120 is implemented as an external entity, it cannot obtain data representing the load of the elevator car 102 from the elevator control system 114. As an example, the elevator monitoring unit 120 can be implemented in a third-party elevator system where access to the elevator control system 114 is unavailable.

[0050] The elevator monitoring unit 120 includes at least one motion sensor device 550 for acquiring speed data representing the speed of the elevator hoisting motor 110. The at least one motion sensor device 550 may include at least one internal sensor device of the elevator monitoring unit 120 and / or at least one external sensor device of the elevator monitoring unit 120 communicatively connected to the elevator monitoring unit 120. Communication between the elevator monitoring unit 120 and the at least one external motion sensor device 550 may be based on one or more known communication technologies, wired or wireless. The elevator monitoring unit 120 and at least one of the at least one motion sensor device 550 may be arranged in the elevator car 102, for example, in the roof of the elevator car 102, such as... Figure 1 As shown in the example. Alternatively, at least one of the motion sensor devices 550 of the monitoring unit 120 may be arranged in the elevator car 102, and the elevator monitoring unit 120 itself may be arranged in any other suitable location within the elevator system, for example, in one of the floors 106a-106b of the elevator system 100 or in the machine room 112.

[0051] Preferably, the obtained speed data may include elevator car speed data representing the speed of the elevator car 102. The elevator car speed data corresponds to the speed (e.g., rotational speed) of the elevator hoisting motor 110, i.e., is related to the speed (e.g., rotational speed) of the elevator hoisting motor 110. The elevator car speed data may include, for example, the speed of the elevator car 102, the acceleration of the elevator car 102, the position / location of the elevator car 102 within the elevator shaft 104, and / or any other data representing the speed of the elevator car 102. Alternatively or additionally, the elevator car speed data may include, for example, any speed data associated with the moving mechanism of the elevator car 102, which is related to the speed of the elevator hoisting motor 110. When the acquired speed data includes elevator car speed data, at least one motion sensor device 550 may include, for example, an accelerometer, a barometric pressure sensor device configured to provide height data of the elevator car 102 within the elevator shaft 104, a magnetometer configured to provide speed data by using positioning based on a magnetogram of the elevator shaft 104, an imaging device (e.g., a camera or any other vision-based device), a magnetic tape reader device, a laser distance measuring device, radar, an (ultrasound)-based distance measuring device, and / or, for example, a low-pulse encoder device arranged to a pulley. Acquiring the elevator car speed data allows for the simple acquisition of speed data representing the speed of the elevator hoist motor 110 without requiring direct measurement of the speed of the elevator hoist motor 110. The rotational speed and / or slippage of the elevator hoist motor 110 can be defined based on the elevator car speed data.

[0052] Alternatively, the obtained speed data may include rotational speed data representing the rotational speed of the elevator hoist motor 110 or slip data representing the slip of the elevator hoist motor 110. The term "slip data" throughout this application refers to the slip of the elevator hoist motor 110 when the elevator hoist motor 110 operates at a synchronous speed, or the corresponding elevator component-related speed difference relative to the speed of the elevator component. An elevator component may be any elevator component of the elevator system 110 that is mechanically linked to and moved by the elevator hoist motor 110, such as the elevator car 102, a pulley, a roller, or any other elevator component moved by the elevator hoist motor 110. In cases where the obtained speed data includes rotational speed data, at least one motion sensor device 550 may be a proximity sensor device arranged to the rotor shaft of the elevator hoist motor 110. The proximity sensor device may be, for example, an inductively based proximity sensor device or a vision-based proximity sensor device, such as a tachometer. The proximity sensor device includes at least one indicator (e.g., a magnet or marker of a specific color, such as white) attached to the circumference of the rotation axis and a fixed sensor configured to detect the proximity of the at least one indicator device. One indicator is sufficient to obtain the rotation of the elevator hoisting motor 110, but two or more indicators are also required to obtain the direction of rotation. Where the obtained speed data includes slip data, at least one motion sensor device 550 includes a sensor device configured to provide slip data.

[0053] By reference Figure 2 An example describing a method for defining load data for elevator car 102. Figure 2The method is illustrated as a flowchart. At step 210, the elevator monitoring unit 120 acquires speed data via at least one motion sensor device 550. The acquired speed data represents the speed of the elevator hoisting motor 110. The acquired speed data may include elevator car speed data, rotational speed data, or slip data as described above. The speed data may be expressed, for example, in revolutions per minute (RPM) or meters per second (m / s). The elevator drive includes different phases, such as an acceleration phase, a steady-state speed phase, and a deceleration phase. Speed ​​data may be acquired during the steady-state speed phase of the elevator drive. Alternatively or additionally, speed data may be acquired at least partially during the final portion of the acceleration phase of the elevator drive and / or at least partially during the beginning portion of the deceleration phase of the elevator drive. Alternatively, at least one motion sensor device 550 can continuously acquire speed data during elevator operation, and the processing unit 510 of the elevator monitoring unit 120 can select from the continuously acquired speed data speed data acquired during the steady-state speed phase, speed data acquired at least partially during the final portion of the acceleration phase of the elevator operation, and / or speed data acquired at least partially during the beginning portion of the deceleration phase of the elevator operation. Before the elevator operation begins, the elevator hoisting motor 110 is in a stationary phase. During the acceleration phase of the elevator operation, the speed of the elevator hoisting motor 110 increases from a stationary speed to a steady-state speed. When the steady-state speed of the elevator hoisting motor 110 is reached, the steady-state speed phase of the elevator operation begins. During the steady-state speed phase of the elevator operation, the elevator hoisting motor 110 drives the elevator car 102 at a steady-state speed. The steady-state speed can be defined by the supply frequency and the load on the elevator car 102. When the speed of the elevator hoisting motor 110 begins to decrease from the steady-state speed, the deceleration phase of the elevator operation begins. During the deceleration phase of the elevator operation, the speed of the elevator hoisting motor 110 decreases from the steady-state speed to a standstill. One or more stages of the elevator drive may also include one or more sub-stages, such as an acceleration phase, a deceleration phase, a constant acceleration phase, an acceleration phase, a deceleration phase, a deceleration phase, a constant deceleration phase, etc. According to one example, if the elevator hoisting motor 110 is a dual-speed DOL induction motor, the elevator drive may include two steady-state speed stages. In this case, speed data can be obtained during the steady-state speed stage, which has a longer duration. As described above, at least one motion sensor device 550 is configured to obtain speed data of the elevator hoisting motor 110. At least one motion sensor device 550 can provide the obtained speed data to the processing unit 510 of the elevator monitoring unit 120. In other words, the processing unit 510 of the elevator monitoring unit 120 can obtain speed data from at least one motion sensor device 550.

[0054] At step 220, the processing unit 510 of the elevator monitoring unit 120 defines the load data (m) of the elevator car 102 based on the obtained speed data, the direction of elevator drive, and predefined reference data. load The defined load data can represent the mass of the load on the elevator car 102. If the nominal load of the elevator car 102 is known, the load data can be expressed as a value in kilograms, or as a percentage. The defined load data for the elevator car 102 includes the mass of the load residing inside the elevator car 102, not the mass of the elevator car 102 itself. The processing unit 510 of the elevator monitoring unit 120 can define the direction of elevator drive based on the acquired speed data. For example, the direction of elevator drive can be defined based on the elevator car speed data included in the acquired speed data. According to another example, the direction of elevator drive can be defined based on the rotational speed data included in the acquired speed data. The rotational speed data, elevator car speed data, and slip data vary depending on the load of the elevator car 102 and the direction of elevator drive, which allows the load data of the elevator car 102 to be defined based on the acquired speed data, the direction of elevator drive, and predefined reference data.

[0055] The predefined reference data may include scaling factors and slip data in the direction of elevator drive given a known load. The predefined reference data may also include synchronization speed data representing the synchronization speed of the elevator motor 110. Synchronization speed data may include the synchronization speed of the elevator hoisting motor 110 or speed data of elevator components representing a related value of the synchronization speed of the hoisting motor 110. An elevator component may be any elevator component of the elevator system 110 that is mechanically linked to and moved by the elevator hoisting motor 110, such as the elevator car 102, pulleys, rollers, or any other elevator component moved by the elevator hoisting motor 110. For example, if the obtained speed data includes elevator car speed data or rotational speed data, the predefined reference data may also include synchronization speed data used to define slip data in the direction of elevator drive given a known load. According to another example, if the obtained speed data includes slip data, it may not be necessary to include synchronization speed data in the predefined reference data. A known load may be, for example, a first known load or a second known load, discussed later in this application in conjunction with the definition of predefined reference data. A known load refers to a mass (m... knownThe known load. Alternatively, the known load can be any other known load. The known load can be expressed as a numerical value, for example, in kilograms. The scaling factor represents the relationship between the slip data of the elevator car 102 and the load data. The value of the scaling factor is the same for both directions of elevator drive (i.e., up and down), but the sign of the scaling factor depends on the direction of elevator drive. In other words, if the scaling factor is higher up (k... up If ) is positive, then the downscaling factor (k) is increased. down If k is negative, then k is negative, and vice versa (i.e., k is negative). up =-k down This is because when the elevator car 102 is driven in one direction, the slip of the elevator hoist motor 110 is positive, and when the elevator car 102 is driven in another direction with the same load, the slip of the elevator hoist motor 110 is negative. However, if the load on the car 102 changes with the direction of elevator drive, the relationship between the direction of elevator drive and the slip of the elevator hoist motor 110 may change. The synchronous speed of the elevator hoist motor 110 represents the rotational speed of the magnetic field in the stator windings of the elevator hoist motor 110 caused by the frequency of the voltage supplied to the elevator motor 110. The synchronous speed of the elevator hoist motor 110 depends on the frequency of the generated voltage and the number of poles in the elevator hoist motor 110. Synchronous speed data can be expressed, for example, in RPM or m / s. If the elevator hoist motor 110 rotates at the same RPM as the magnetic field, there will be no relative motion between the rotor and the magnetic field; therefore, no current is induced in the rotor, and no magnetic field is generated to cause the rotor to rotate. The slippage of the elevator hoisting motor 110 represents the difference between the synchronous speed of the elevator hoisting motor 110 and the actual speed of the elevator hoisting motor 110.

[0056] The following discussion presents an example of defining the load data of the elevator car 102 at step 220 based on the obtained speed data, the direction of elevator drive, and predefined reference data. When the elevator drive direction is upward along the elevator shaft 104, the load data (m) of the elevator car 102 is... load It can be defined according to the following formula:

[0057] m load =(s up_load -s up_known ) / k up +m known (1)

[0058] Where s up_known The upward slip data is given under known load conditions, k up It is the upward scaling factor, s up_loadIt is the upward sliding data given the load data to be defined (i.e., the defined load data), and m known The mass of the known load. In the case of load data to be defined, the upward slip data can be included in the obtained velocity data, or based on the obtained velocity data and synchronous velocity data (n). sync The obtained velocity data can be defined as follows: As mentioned above, the velocity data can include slip data. In this case, the upward slip data (s) is defined in the context of the load data to be defined. up_load The velocity data is obtained from formula (1) above. Alternatively, the obtained velocity data may include elevator car velocity data or upward rotational velocity data. In this case, the upward slip data can be defined according to the following formula, given the load data to be defined:

[0059] s up_load =n sync -n up_load (2)

[0060] Where n up_load It is the speed data obtained when the elevator is driven upwards.

[0061] Alternatively, when the elevator is driven downwards along the elevator shaft 104, the load data (m) of the elevator car 102 is... load It can be defined according to the following formula:

[0062] m load =(S down_load -S down_known ) / k down +m known (3)

[0063] Among them, s down_known1 The downward slip data, k, is given under a known load. down It is a downward scaling factor, and s down_load This refers to the downward slip data under the load data to be defined. The downward slip data under the load data to be defined can be included in the obtained speed data, or defined based on the obtained speed data and synchronous speed data. As mentioned above, the obtained speed data can include slip data. In this case, the downward slip data (s) under the load data to be defined... down_load The velocity data is obtained from formula (3) above. Alternatively, the obtained velocity data may include elevator car velocity data or downward rotational velocity data. In the latter case, the downward slip data can be defined according to the following formula in the case of the load data to be defined:

[0064] s down_load =n sync –n down_load (4)

[0065] Where n down_load It is the speed data obtained when the elevator is driven in the downward direction.

[0066] Reference data can be defined during the learning drive of elevator car 102. The learning drive of elevator car 102 can be performed, for example, during the installation phase of monitoring unit 120. The learning drive can be performed in the elevator system 100 in question, where monitoring unit 120 will be implemented. Alternatively, the learning drive can be performed in another elevator system 100 with a similar configuration to elevator system 100, where monitoring unit 120 will be implemented. For example, reference data can be predefined during type testing at a production facility, and monitoring unit 120 with predefined reference data can be implemented (i.e., installed) in elevator system 110 without performing the learning drive in said elevator system 100. The predefined reference data can be stored, for example, in the memory unit 520 of elevator monitoring unit 120, or elevator monitoring unit 120 can obtain the predefined reference data from a database.

[0067] By reference Figure 3 Describe examples of learning-driven learning. Figure 3 The learning drive is illustrated as a flowchart. At step 310, as the elevator car 102 with a first known load moves upward and downward along the elevator shaft 104, the elevator monitoring unit 120 obtains first reference speed data representing the speed of the elevator hoisting motor 110 via at least one motion sensor device 550. The first reference speed data may be obtained during the steady-state speed phase of the elevator drive, at least partially during the final portion of the acceleration phase of the elevator drive, and / or at least partially during the beginning portion of the deceleration phase of the elevator drive. Alternatively, at least one motion sensor device 550 may continuously obtain the first reference speed data during the elevator drive, and the processing unit 510 of the elevator monitoring unit 120 may select from the continuously obtained first reference speed data the first reference speed data obtained during the steady-state speed phase, at least partially during the final portion of the acceleration phase of the elevator drive, and / or at least partially during the beginning portion of the deceleration phase of the elevator drive. The first known load may be, for example, but not limited to, an empty elevator car 102, i.e., zero load. This is merely an example, and any other known load may be used as the first known load. The first reference velocity data may be included under the first known load (n) up_known1 The upward elevator car speed data or rotational speed data under the condition of ) and the first known load (n down_known1The first reference speed data may include downward elevator car speed data or rotational speed data under a first known load condition. Alternatively, the first reference speed data may include upward slip data (s) under a first known load condition. up_known1 ) and downward slip data under the first known load (s down_known1 The first reference velocity data for upward and downward movement under the first known load can be expressed, for example, in RPM or m / s.

[0068] At step 320, as the elevator car 102 with the second known load moves upward and downward along the elevator shaft 104, the elevator monitoring unit 120 obtains second reference speed data representing the speed of the elevator hoisting motor 110 via at least one motion sensor device 550. The second reference speed data may be obtained during the steady-state speed phase of the elevator drive, at least partially during the final portion of the acceleration phase of the elevator drive, and / or at least partially during the beginning portion of the deceleration phase of the elevator drive. Alternatively, the at least one motion sensor device 550 may continuously obtain the second reference speed data during the elevator drive, and the processing unit 510 of the elevator monitoring unit 120 may select from the continuously obtained second reference speed data the second reference speed data obtained during the steady-state speed phase, at least partially during the final portion of the acceleration phase of the elevator drive, and / or at least partially during the beginning portion of the deceleration phase of the elevator drive. The second known load is different from the first known load. The second known load may be, for example, but not limited to, a technician with a known mass. This is merely an example, and any other known load different from the first known load may be used as the second known load. The second reference velocity data may be included under the second known load (n) up_known2 In the case of upward elevator car speed data or rotational speed data and the second known load (n) down_known2 The second reference speed data may include downward elevator car speed data or rotational speed data under a second known load. Alternatively, the second reference speed data may include upward slip data (s) under a second known load. up_known2 ) and downward slip data under the second known load (s down_known2 The second reference velocity data, both upward and downward, under a second known load can be expressed, for example, in RPM or m / s. Figure 3 In the example, step 320 is executed after step 310, but step 320 may alternatively be executed before step 310.

[0069] At step 330, the processing unit 510 of the elevator monitoring unit 120 defines reference data based on the obtained first reference speed data and the obtained second reference speed data.

[0070] Figure 4 It was disclosed schematically in a more detailed manner. Figure 3 The flowchart. Specifically, step 330 starts from... Figure 4 The process becomes clear. As described, the processing unit 510 of the elevator monitoring unit 120 defines reference data based on the first reference speed data and the second reference speed data obtained at step 330 during the learning drive. In this example, the first reference speed data includes elevator car speed data representing the speed of the elevator car 102 in both directions under a first known load, and the second reference speed data includes elevator car speed data representing the speed of the elevator car 102 in both directions under a second known load. Alternatively, the first reference speed data may include rotational speed data in both directions under a first known load, and the second reference speed data may include rotational speed data in both directions under a second known load, as described above. In this case, the same steps and the same formulas can be used to define the reference data, as will be described for the elevator car speed data. Alternatively, the first reference speed data may include slip data in both directions under a first known load, and the second reference speed data may include slip data in both directions under a second known load. In this case, steps 410 to 430 can be omitted, and step 330 only includes the definition of the scaling factor at step 440.

[0071] At step 410, the processing unit 510 of the elevator monitoring unit 120 defines the synchronization speed data (n) based on the obtained first reference speed data or the obtained second reference speed data. sync For example, synchronization speed data can be defined using the following formula:

[0072] n sync =(n up_known1 +n down_known1 ) / 2, (5)

[0073] Where n up_known1 The data represents the upward speed of the elevator car under the first known load condition, and n down_known1 This refers to the downward speed data of the elevator car under a first known load. Alternatively, the synchronous speed data can be defined using the following formula:

[0074] n sync =(n up_known2 +n down_known2 ) / 2, (6)

[0075] Where n up_known2 The data represents the upward elevator car speed under the second known load condition, and n down_known2This is the downward elevator car speed data under the second known load condition.

[0076] At step 420, the processing unit 510 of the elevator monitoring unit 120 defines slip data (s) in both directions under the first known load based on the defined synchronous speed data and the obtained first reference speed data. up_known1 and s down_known1 ). Upward slip data (s) under the first known load. up_known1 It can be defined, for example, according to the following formula:

[0077] s up_known1 =n sync -n up_known1 (7)

[0078] Downward slip data (s) under the first known load condition down_known1 It can be defined, for example, according to the following formula:

[0079] s down_known1 =n sync -n down_known1 (8)

[0080] At step 430, the processing unit 510 of the elevator monitoring unit 120 defines slip data (s) in both directions under the second known load based on the defined synchronous speed data and the obtained second reference speed data. up_known2 s down_known2 ). Upward slip data (s) under the second known load condition. up_known2 It can be defined, for example, according to the following formula:

[0081] s up_known2 =n sync -n up_known2 (9)

[0082] Where n up_known2 This refers to the upward elevator car speed data under the second known load condition. It also includes the downward slip data (s) under the second known load condition. down_known2 It can be defined, for example, according to the following formula:

[0083] s down_known2 =n sync -n down_known2 (10)

[0084] Where n down_known2 This is the downward elevator car speed data under a second known load condition. Figure 4 In the example, step 430 is executed after step 420, but step 430 may alternatively be executed before step 420.

[0085] At step 440, the processing unit 510 of the elevator monitoring unit 120 defines a scaling factor based on the upward or downward slip data under the first known load and the second known load. As mentioned above, the slip data can be included in the first reference speed data and the second reference speed data, or defined in steps 420 and 430 above. Also as mentioned above, the value of the scaling factor is the same for both directions of elevator drive, but the sign of the scaling factor depends on the direction of elevator drive. Therefore, it is sufficient to define the upward or downward scaling factor based on the slip data under the first known load and the second known load, and then define the other scaling factor by changing the sign of the other scaling factor. The scaling factor can be defined using the upward slip data under the known load, for example, according to the following formula:

[0086] k up =(s up_known2 -s up_known1 ) / (m known2 - m known1 (11)

[0087] Where s up_known2 The upward slip data is under the second known load condition, s up_known1 The upward slip data is given under the first known load, m known1 The mass of the first known load, m known2 This is the mass of the second known load. Alternatively, the scaling factor can be defined using downward sliding data under the known load, for example, according to the following formula:

[0088] k down =(S down_known2 -S down_known1 ) / (m known2 - m known1 (12)

[0089] Among them, s down_known2 The downward slip data is under the second known load condition, s down_known1 It is the downward slip data under the first known load condition.

[0090] Figure 5An example of components of the elevator monitoring unit 120 is schematically shown. The elevator monitoring unit 120 may include a processing unit 510 containing one or more processors, a memory unit 520 containing one or more memories, at least one motion sensor device 550 as described above, a communication interface unit 530 containing one or more communication devices, and a possible user interface (UI) unit 540. The mentioned components may be communicatively coupled to each other, for example, via an internal bus. The memory unit 520 may store and maintain portions of a computer program (code) 525 and any other data. The computer program 525 may include instructions that, when executed by the processing unit 510 of the elevator monitoring unit 120, cause the processing unit 510 and thus the elevator monitoring unit 120 to perform desired tasks, such as one or more of the method steps described above and / or the operations of the elevator monitoring unit 120 described above. Therefore, the processing unit 510 may be arranged to access the memory unit 520 and retrieve and store any information from and to the memory unit 520. For clarity, the processor herein refers to any unit suitable for processing information and controlling the operation of the elevator monitoring unit 120 and other tasks. Operation can also be implemented using a microcontroller solution with embedded software. Similarly, memory unit 520 is not limited to a certain type of memory, but any type of memory suitable for storing the described multiple pieces of information can be applied in the context of this invention. At least one of the one or more memories of memory unit 520 may also be included by processing unit 510 as internal memory of processing unit 510. Communication interface unit 530 provides one or more communication interfaces for communicating with any other unit (e.g., with external computing unit 610, one or more databases, or with any other unit). User interface unit 540 may include one or more input / output (I / O) devices for receiving user input and output information, such as buttons, keyboards, touch screens, microphones, speakers, displays, etc. Elevator monitoring unit 120 may also include one or more other sensor devices for acquiring any other data. Computer program 525 may be a computer program product that may be included in a tangible non-volatile (non-transitory) computer-readable medium carrying computer program code 525 embodied therein for use with a computer (i.e., elevator monitoring unit 120).

[0091] The method described above and the elevator monitoring unit 120 enable the definition of load data for the elevator car 102 using at least one motion sensor device 550 located outside the elevator system 100, without requiring a communication connection with the elevator system 100 including the elevator car 102. This improves the monitoring capabilities of the elevator system, particularly in the case of a third-party elevator system. The defined load data for the elevator car 102 can be used, for example, for material / personnel flow estimation. Therefore, the method and elevator monitoring unit 120 discussed above improve material / personnel flow estimation. Alternatively or additionally, the defined load data for the elevator car 102 can be used, for example, to detect entrapment situations where passengers are trapped inside the elevator car 102, for example, when the elevator car 102 stops between floors. Therefore, the method and elevator monitoring unit 120 discussed above improve the detection of entrapment situations.

[0092] According to one embodiment, the elevator monitoring unit 120 can be configured to send defined load data of the elevator car 102 to an external computing unit 610, such as an external server, like a cloud server or any other server outside the elevator system 110. The external computing unit 610 can analyze the load data received from the monitoring unit 120, for example, to trigger maintenance-related tasks. According to another embodiment, the monitoring unit 120 can be configured to send the acquired speed data and the direction of elevator drive to the external computing unit 610, and the external computing unit can be configured to perform the definition of the load data of the elevator car 102, i.e., method step 220 described above. Similarly, the monitoring unit 120 can be configured to send the acquired first reference speed data and second reference speed data to the external computing unit 610, and the external computing unit 610 can be configured to define reference data, i.e., method step 330 described above. Figure 6 A system 600 including an elevator monitoring unit 120 and an external computing unit 610 is schematically shown. The external computing unit 610 can be communicatively connected to the elevator monitoring unit 120. Communication between the elevator monitoring unit 120 and the external computing unit 610 can be based on one or more known communication technologies, wired or wireless.

[0093] The different examples of methods for defining load data for elevator car 102 described above are defined with reference to an elevator system 100 comprising an elevator car 102 traveling along an elevator shaft 104. However, the elevator system 100 may also include elevator groups, i.e., a group of two or more elevator cars 102, each traveling along a corresponding elevator shaft 104 configured as a unit operating to serve the same floors 106a-106n. All the examples discussed above also apply to an elevator system 100 comprising elevator groups. For example, an elevator system 100 comprising elevator groups may include a corresponding elevator monitoring unit 102 for each elevator car 102 in the elevator group, the elevator monitoring unit 102 being configured to define the load data of said elevator car 102.

[0094] The specific examples provided in the description above should not be construed as limiting the applicability and / or interpretation of the appended claims. Unless otherwise expressly stated, the list and groups of examples provided in the description above are not exhaustive.

Claims

1. A method for defining load data of an elevator car (102), the method comprising: Speed ​​data (210) is obtained by at least one motion sensor device (550), the speed data representing the speed of an asynchronous elevator hoisting motor (110) arranged to drive the elevator car (102) along the elevator shaft (104), and The load data of the elevator car (102) is defined (220) based on the obtained speed data, the direction of elevator drive, and predefined reference data. The predefined reference data includes a scaling factor and slip data in the direction of elevator drive under known load. Wherein, the slip data represents the difference between the synchronous speed of the elevator hoisting motor and the actual speed of the elevator hoisting motor, and the scaling factor represents the relationship between the slip data of the elevator car and the load data.

2. The method according to claim 1, wherein, The predefined reference data also includes synchronization speed data.

3. The method according to any one of the preceding claims, wherein when the elevator is driven upward, the load data of the elevator car (102) is defined according to the following formula: m load =(s up_load -s up_known ) / k up +m known , Where s up_known The upward slip data is given under known load conditions, k up It is the upward scaling factor, s up_load It is the upward slip data given the load data to be defined, and m known The mass of the known load, wherein the upward slip data, given the load data to be defined, is included in the obtained velocity data or defined based on the obtained velocity data and synchronous velocity data, or When the elevator is driven in a downward direction, the load data of the elevator car (102) is defined according to the following formula: m load =(s down_load -s down_known ) / k down +m known , in, s down_known The downward slip data, k, is given under a known load. down It is a downward scaling factor, and s down_load It is the downward slip data under the load data to be defined, wherein the downward slip data under the load data to be defined is included in the obtained speed data or defined based on the obtained speed data and synchronous speed data.

4. The method of claim 3, wherein the reference data is defined during the learning drive of the elevator car (102). The learning drive includes: When the elevator car (102) with a first known load is driven upward and downward along the elevator shaft (104), first reference speed data is obtained (310), the first reference speed data representing the speed of the elevator hoisting motor (110). When the elevator car (102) with a second known load is driven upward and downward along the elevator shaft (104), second reference speed data (320) is obtained, the second reference speed data representing the speed of the elevator hoisting motor (110) of the elevator hoisting motor, and The reference data (330) is defined based on the obtained first reference velocity data and the obtained second reference velocity data. The reference data defined during the learning-driven process (330) includes: Synchronization speed data (410) is defined based on the obtained first reference speed data or the obtained second reference speed data. Based on the defined synchronization speed and the obtained first reference speed data, (420) the slip data in both directions under the first known load are defined. Based on the defined synchronization speed and the obtained second reference speed data, (430) the slip data in both directions under the second known load are defined, and The scaling factor (440) is defined based on the defined slip data upward or downward under the known load and the known first and second loads.

5. The method according to claim 4, wherein, During the learning drive, the reference data is defined (330) as follows: the scaling factor is defined (440) based on the upward or downward slip data under the known load and the known first load and second load, wherein the upward and downward slip data under the first known load is included in the obtained first reference velocity data, and the upward and downward slip data under the second known load is included in the second reference velocity data.

6. The method according to claim 5, wherein the at least one motion sensor device (550) is included in the elevator monitoring unit (120) and has no communication connection with the elevator control system (114) of the elevator system (100) including the elevator car (102).

7. The method according to claim 6, wherein, The asynchronous elevator hoisting motor (110) is a direct online (DOL) induction motor or a frequency-controlled induction motor.

8. An elevator monitoring unit (120) for defining load data of an elevator car (102), the monitoring unit (120) comprising: At least one motion sensor device (550) is configured to acquire speed data representing the speed of an asynchronous elevator hoisting motor (110), which is arranged to drive the elevator car (102) along the elevator shaft (104). The processing unit (510) is configured as follows: The speed data is obtained from the at least one motion sensor device (550), and The load data of the elevator car (102) is defined based on the obtained speed data, the direction of elevator drive, and predefined reference data. The predefined reference data includes a scaling factor and slip data in the direction of elevator drive under known load. Wherein, the slip data represents the difference between the synchronous speed of the elevator hoisting motor and the actual speed of the elevator hoisting motor, and the scaling factor represents the relationship between the slip data of the elevator car and the load data.

9. The elevator monitoring unit (120) according to claim 8, wherein, The predefined reference data also includes synchronization speed data.

10. The elevator monitoring unit (120) according to any one of claims 8 to 9, wherein when the elevator is driven upward, the processing unit (510) is configured to define the load data of the elevator car (102) according to the following formula: m load =(s up_load -s up_known ) / k up +m known , Where s up_known The upward slip data is given under known load conditions, k up It is the upward scaling factor, s up_load It is the upward slip data given the load data to be defined, and m known The mass of the known load, wherein the upward slip data, given the load data to be defined, is included in the obtained velocity data or defined based on the obtained velocity data and synchronous velocity data, or When the elevator is driven in a downward direction, the processing unit (510) is configured to define the load data of the elevator car (102) according to the following formula: m load =(s down_load -s down_known ) / k down +m known , in, s down_known The downward slip data, k, is given under a known load. down It is a downward scaling factor, and s down_load It is the downward slip data under the load data to be defined, wherein the downward slip data under the load data to be defined is included in the obtained speed data or defined based on the obtained speed data and synchronous speed data.

11. The elevator monitoring unit (120) according to claim 10, wherein the processing unit (510) is configured to define the reference data during the learning drive of the elevator car (102), The learning drive, including the processing unit (510), is configured as follows: When the elevator car (102) with a first known load is driven upward and downward along the elevator shaft (104), first reference speed data representing the speed of the elevator hoisting motor (110) is obtained. When the elevator car (102) with a second known load is driven upward and downward along the elevator shaft (104), second reference speed data representing the speed of the elevator hoisting motor (110) is obtained, and The reference data is defined based on the obtained first reference velocity data and the obtained second reference velocity data. During the learning-driven process, the reference data is defined including the processing unit being configured as follows: Synchronization speed data is defined based on the obtained first reference speed data or the obtained second reference speed data. Based on the defined synchronization speed and the obtained first reference speed data, slip data in both directions are defined under the first known load. Based on the defined synchronization speed and the obtained second reference speed data, the slip data in both directions under the second known load are defined, and The scaling factor is defined based on the sliding data of the elevator lifting motor (110) under the known upward or downward load, as well as the known first load and second load.

12. The elevator monitoring unit (120) according to claim 11, wherein, Defining the reference data during the learning drive includes: the processing unit (510) is configured to define the scaling factor based on the sliding data of the elevator hoisting motor (110) moving up or down under the known load and the known first load and second load, wherein the sliding data moving up and down under the first known load is included in the obtained first reference speed data, and the sliding data moving up and down under the second known load is included in the second reference speed data.

13. The elevator monitoring unit (120) according to claim 12, wherein, The elevator monitoring unit (120) is not connected to the elevator control system (114) of the elevator system (100) that includes the elevator car (102).

14. The elevator monitoring unit (120) according to claim 13, wherein, The asynchronous elevator hoisting motor (110) is a direct online (DOL) induction motor or a frequency-controlled induction motor.

15. A computer program product (525) for defining load data of an elevator car (102), the computer program product causing the computer to perform the method according to any one of claims 1 to 7 when executed by a computer.

16. A system (600) for defining load data of an elevator car (102), comprising: The elevator monitoring unit (120) according to any one of claims 8 to 14, and External computing unit (610), which is configured as follows: The load data of the elevator car (102) is received from the elevator monitoring unit (120), and The received load data of the elevator car (102) is stored and analyzed.

Images