阅读说明：本技术 电梯中的制动器操作管理 (Brake operation management in an elevator ) 是由 A.罗菲 R.K.罗伯茨 R.E.泰博 M.贾芬克尔 E.皮拉 D.汉维 D.拉什 于 2014-02-06 设计创作，主要内容包括：各实施方案涉及：确定电梯系统的电梯轿厢正在接近停靠位置；基于所述电梯轿厢正在接近所述停靠位置的所述确定,通过控制器获得与所述电梯系统相关联的至少一个参数的值；确定所述电梯轿厢在阈值距离内到达所述停靠位置处；基于所述至少一个参数的所述值并且基于确定所述电梯轿厢在所述阈值距离内到达所述停靠位置处,通过所述控制器确定何时参与制动器循环操作和功率循环操作中的至少一个；以及在对应于何时参与制动器循环操作和功率循环操作中的所述至少一个的所述确定的时间处,启动制动器循环操作和功率循环操作中的所述至少一个。(Embodiments relate to: determining that an elevator car of an elevator system is approaching a stopping position; obtaining, by a controller, a value of at least one parameter associated with the elevator system based on the determination that the elevator car is approaching the landing; determining that the elevator car arrives at the stopping location within a threshold distance; determining, by the controller, when to engage in at least one of a brake cycling operation and a power cycling operation based on the value of the at least one parameter and based on determining that the elevator car arrives at the landing within the threshold distance; and initiating the at least one of brake cycling and power cycling at the determined time corresponding to when to engage the at least one of brake cycling and power cycling.)

1. A method for brake operation management in an elevator system, comprising:

determining a load or number of passengers in an elevator car of an elevator system before the elevator car arrives at a stopping location and a load or number of passengers waiting to enter the car at the stopping location based on at least one of:

load weighing data;

motor torque;

vision and image processing;

an output of a landing load unit within or proximate to the elevator system in a hoistway door;

hall calls and car calls; and

the data for the security system of the building,

wherein the method further comprises:

determining an operation to be performed with respect to a brake, a door of the elevator car, and a power cycle based on the determination of the load or number of passengers in the elevator car before the elevator car arrives at the stopping location and the load or number of passengers waiting to enter the car at the stopping location.

2. The method of claim 1, wherein if the car is loaded prior to reaching the stopping location, the power cycle is delayed until the load weighing data indicates that an amount of load change associated with the elevator car over a given period of time is less than a threshold.

3. The method of claim 1, wherein if the car is loaded before reaching the stopping location, the power cycle is delayed until the load weighing data is below a given threshold for a given period of time, and wherein the brake is lifted after the power cycle and the car is enabled to re-level and leave the stopping location without interruption.

4. The method of claim 1, wherein if there is no load in the car before reaching the stopping location, performing a brake operation and power cycling before opening the door of the elevator car.

5. The method of claim 1, further comprising:

determining that the brake has fallen when the at least one elevator car is at a particular stopping location; and is

Based on determining that the brake has fallen, causing the elevator system to engage in a motion profile away from the particular landing location.

6. The method of claim 5, wherein the motion profile is selected to minimize start-up delay.

7. The method of claim 5, further comprising:

determining that the brake has not fallen and a pre-flight inspection has not been conducted when the at least one elevator car is at a second particular landing; and is

Based on a determination that the brakes have not fallen and a pre-flight check has not been made, causing a brake cycle to occur prior to door closure and motion demand to avoid excessive start delays.

It is noted that various connections between the elements are set forth in the following description and drawings (the contents of which are incorporated in the present disclosure by reference). It should be noted that these connections in general may be direct or indirect unless specified otherwise, and the specification is not intended to be limited in this respect. In this regard, a coupling between entities may refer to a direct connection or an indirect connection.

Exemplary embodiments of an apparatus, system, and method for safely and efficiently controlling an elevator are described. In some embodiments, the timing of the brakes and power cycles at the stopping position may be determined using a constant delay or based on one or more parameters, such as motor torque, load weighing, or car acceleration. The load in the elevator car can be monitored when e.g. a passenger or an object leaves the elevator car. When the elevator car is nearly empty, the brake may be dropped and/or the machine (e.g., motor) may be de-energized, providing sufficient cycle time when the last passenger leaves and the next group of passengers enters the elevator.

Referring to fig. 1, a block diagram of an exemplary elevator system 100 is shown. The organization and arrangement of the various components and devices shown and described below in connection with the elevator system 100 is illustrated. In some embodiments, the arrangement or order of components or devices may be different from that shown in fig. 1. In some embodiments, one or more of the devices or components may be optional. In some embodiments, one or more additional components or devices not shown may be included.

The system 100 may include an elevator car 102 that may be used to transport, for example, people or items, such as loads, up and down an elevator shaft or hoistway 104. The elevator car 102 can include an input/output (I/O) interface that can be used by passengers of the system 100 to select a destination or target landing floor that can be specified according to a floor number. The elevator car 102 may include one or more panels, interfaces, or devices that may be used to facilitate emergency operations.

The elevator car 102 can be coupled to the motor 106 by a drive sheave 114 and a tension member 112. The motor 106 may provide power to the system 100. In some embodiments, the motor 106 can be used to propel or move the elevator car 102.

The motor 106 may be coupled to an encoder 108. The encoder 108 may be configured to provide a position for the machine or motor 106 as they rotate. The encoder 108 may be configured to provide the speed of the motor 106. For example, the speed of the motor 106 may be obtained using a delta positioning technique, potentially as a function of time. The state of the elevator car 102 can be inferred using measurements or data obtained by the encoder 108 from the motor 106.

The system 100 can include a second sheave 110 connected to the elevator car 102 by a tension member 134. The second sheave 110 may be a governor or a dedicated car positioning device. The tension member 134 is designed to have a low tension level to provide good positive engagement with the sheave 110 so that the position and/or speed of the elevator car 102 can be inferred from the encoder 130. In some embodiments, tension members 112 may include one or more cords, cables, chains, or the like. In some embodiments, the tension members 134 may comprise belt or grooved metal belts.

The system 100 may include a brake 116. The brake 116 can be engaged or dropped to secure the elevator car 102 at a particular height or elevation within the hoistway 104.

The system 100 may include a controller 118 or be associated with the controller 118. The controller 118 may include one or more processors 120, and a memory 122 having instructions stored thereon that, when executed by the processors 120, cause the controller 118 to perform one or more actions, such as those described herein. In some embodiments, processor 120 may be implemented at least in part as a microprocessor (uP). In some embodiments, the memory 122 may be configured to store data. Such data may include position, speed or acceleration data associated with the elevator car 102, motor torque data, load weighing data 132, and the like.

In some embodiments, the controller 118 may receive or obtain information or data associated with one or more parameters. For example, the controller 118 may obtain information about motor torque, load weighing, or car acceleration, speed, or position. In some embodiments, the controller 118 may receive such information from one or more sensors, such as the encoder 108, the encoder 130, the desired landing floor location 126, and a load weighing cell 132 that may be positioned at an attachment point on the elevator car 102, such as below a platform or at an attachment point of the tension member 112.

When the elevator car 102 reaches the desired stopping floor 126, the elevator car doors will open and passengers can move in and out of the car. This weight transfer will cause the tension member 112 to extend or contract, thus causing the elevator car sill 124 to move vertically relative to the landing floor sill 126. The difference between the landing position sill 126 and the car sill 124 is referred to as sag 128. It is desirable for the elevator system 100 to minimize the amount of car sag 128 during passenger and payload ingress and egress to the elevator car 102. The controller 118 may use the difference between the encoder 130 and the encoder 108 to estimate the car sag 128 and use this signal to initiate or terminate a re-leveling operation.

In some embodiments, the brake or power cycle (e.g., the timing associated with the brake or power cycle) may be based on the load weighing signal 132. A load weighing signal 132, which may correspond to load weighing data, may be used to indicate the load present in the elevator car 102. The load weighing signal 132 can be monitored when the elevator car 102 has reached the destination floor or landing 126. If the amount of change in the load weighing signal 132 over a given period of time is less than a threshold value, a determination may be made that the brake 116 may be dropped and/or that the machine (e.g., the motor 106) may be powered down. In this way, sag due to load transfer can be minimized.

In some embodiments, the brake or power cycle (e.g., timing associated with the brake or power cycle) can be based on a determination or prediction of a load (e.g., a passenger) that can exit or enter the elevator car 102 as the elevator car 102 approaches the first destination floor or landing as part of a run. For example, if the system 100 or the controller 118 knows that there are fifteen passengers in the elevator car 102 when the elevator car 102 is approaching the first destination stop location, and if the system 100 or the controller 118 knows that at least twelve of the fifteen passengers will be leaving the elevator car 102 when the elevator car 102 reaches the first destination stop location, then the elevator car 102 can make a re-leveling operation (shortly) after reaching the first destination stop location. Further refinements can be made in the following embodiments: where the personal device (e.g., smartphone) of the passenger is used to determine or estimate their identity, such as in an embodiment where the passenger requests elevator service. In some embodiments, the brake or power cycle may be based on an estimate of the incoming passenger flow. The estimation of the incoming passenger flow may be based on historical data.

In some embodiments, the system 100 (or a component or device thereof) may predict that heavy loads will enter the elevator car 102, such as when the elevator car (e.g., car 102) is idle at a stop position and the brake is dropped. Such predictions may be based on knowledge about: passengers assigned due to entering the elevator car 102, load sensors located in the hallway, vision and image processing systems that view the hallway, elevator dispatch inputs, or building safety inputs. The system 100 may initiate or initiate re-leveling to minimize the sag 128 before a passenger has entered the car 102.

Turning now to FIG. 2, a flow diagram of an exemplary method 200 for managing re-leveling and brake or power cycling in the controller 118 is shown. Method 200 may be performed by or in connection with one or more systems, components, or devices, such as those described herein. The method 200 may be used to determine an appropriate time for an elevator system to engage in re-leveling, brake, or power cycling, potentially as part of an elevator operation with the elevator 200. This system is operable to collect measurement signals to optimize a re-leveling control function when the elevator car 102 is near a desired floor landing 126.

In block 202, the load weight signal 132 is continuously measured throughout the landing and re-leveling phases of elevator operation.

In block 204, an estimate of the amount of elevator car sag 128 is made continuously throughout the landing and re-leveling phases of elevator operation. The determination of such an estimate may be based on measurement signals from, for example, the motor encoder 108 and the secondary sheave encoder 130. Other positioning systems or sag estimation techniques that measure sag, directly or indirectly, working in conjunction with or independent of these encoder signals may be used.

In block 206 the value of the stopping floor is retrieved from the elevator controller memory 122 in order to define the stopping position of the elevator car in the building.

In block 208, input from the elevator car is monitored and recorded to indicate whether a request for service has been made from the current landing position to a new landing position.

In block 210, a timer is monitored to record how much time has elapsed during the time since the initial stop at the floor.

In block 212, door status information from the car is monitored and recorded to indicate whether the door is opening, opened, closing, or closed.

In block 214, the need for a boarding passenger at the landing floor 126 is estimated based on the sensor input or the controller signal.

In block 216, the signals from the previous blocks are used to determine the best request to meet the system's landing or re-leveling operational needs while the system is being loaded or unloaded at the landing floor. The output of this block will be the following request: opening or closing the brake 116, energizing or de-energizing the motor 106, and initiating a corrective movement request by the controller 118 to lower the sensed car sag 128 value for the motor 106.

When the elevator car 102 approaches the desired landing location 126, the control block 216 may decide to drop the brake based on the sensed load weight 202 and the landing floor 206. If the car weight indicates that the car is full and the stopping floor is near the bottom of the elevator that is rising very high, the best solution may be to not drop the brake but to make a re-level directly from the normal motion profile command into the floor in order to predict the need for re-level when the full car is unloaded.

Since the elevator car 102 is in the re-leveling mode of operation when at a lower landing position in the building, as determined from the landing floor signal 206, the control block 216 can optimize the time to lift or drop the brake based on, for example, one or more of the sag estimator 204, the load weight signal 202, and the timer 210. The sag estimate 204 will define when the sag value returns within a desired threshold. When this is done, the load weight and timer signal can be used to assess whether a load transfer may or may not have been completed by looking at how much the load weight signal varies within the time window. If the signal change exceeds a set threshold, then the re-leveling operation should continue. If the signal has shown a very small change (e.g., a change less than a threshold), then it is likely that the re-leveling operation can be stopped and the brake dropped.

The control block 216 may use the door signal 212 and the new floor demand signal 208 to determine whether a re-leveling operation should be stopped and converted into a brake drop/safety check state. The control block 216 may record how many brake drop cycles occurred in the operating window at the stop floor 126. If this does not happen at one time, the system needs to stop re-leveling and let the brake fall when the door is closed and a new demand is entered.

The method 200 is illustrative. In some embodiments, one or more of the blocks or operations (or portions thereof) may be optional. In some embodiments, the operations may be performed in an order or sequence different than that shown. In some embodiments, one or more additional operations not shown may be included. In some embodiments, one or more of the blocks or operations may be performed iteratively, potentially as part of a background task.

Embodiments of the present disclosure can be used to select an appropriate or optimal time to cycle an elevator system or change a power or braking state as applied to an elevator system. The timing may be selected to minimize errors or to minimize the number or degree of re-leveling that may be required. In this manner, the elevator system can operate more efficiently, component/device wear and usage can be minimized, and delays incurred as part of elevator system operation can be minimized.

In some embodiments, various functions or actions may occur at a given location and/or in conjunction with the operation of one or more devices, systems, or apparatuses. For example, in some embodiments, a portion of a given function or action may be performed at a first device or location, and the remainder of the function or action may be performed at one or more additional devices or locations.

Embodiments may be implemented using one or more technologies. In some embodiments, an apparatus or system may comprise one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus or system to perform one or more method acts as described herein. In some embodiments, one or more input/output (I/O) interfaces can be coupled to one or more processors and can be used to provide a user with an interface of the elevator system. In some embodiments, various mechanical components known to those skilled in the art may be used.

Embodiments may be implemented as one or more devices, systems, and/or methods. In some embodiments, the instructions may be stored on one or more computer-readable media, such as transitory and/or non-transitory computer-readable media. The instructions, when executed, may cause an entity (e.g., a device or system) to perform one or more method acts as described herein.

Aspects of the present disclosure have been described with respect to illustrative embodiments thereof. Numerous other embodiments, modifications and variations within the scope and spirit of the appended claims will occur to persons of ordinary skill in the art from a review of this disclosure. For example, one of ordinary skill in the art will appreciate that the steps described in connection with the illustrative figures may be performed in an order other than the recited order, and that one or more steps shown may be optional.