Elevator braking force detection data recording and analyzing method

Abstract

According to the elevator braking force detection data recording and analyzing method provided by the invention, data recording can be carried out after each braking force detection, analysis is facilitated, the elevator is prohibited from running when the detection result is poor, and the elevator is allowed to run only after the detection result is normal again; and the safety and the reliability of the brake force of the elevator are improved. According to the technical scheme, the defects that data records are not formed in braking force detection, only one result is output, and data support cannot be provided for data analysis are overcome; 2, when the braking force is insufficient, only an alarm is given for reminding, operation is not forbidden, and the safety is influenced;

Description

Technical Field

[0001] The present invention belongs to the technical field of elevator brake force detection data recording and analysis, and in particular, relates to an elevator brake force detection data recording and analysis method. Background Art

[0002] At present, when testing the brake force of an elevator, the inverter can output a low-frequency downward torque without opening the brake of the motor, and judge whether the brake force is good through the motor speed or position feedback. The existing technical solutions have the following defects: 1. The brake force detection does not form a data record, but only outputs a result, which cannot provide data support for data analysis; 2. When the brake force is insufficient, it only alarms and reminds, but does not prohibit operation, which affects its safety. Summary of the invention

[0003] In order to solve the above problems, the purpose of the present invention is to provide a method for recording and analyzing the brake force detection data of an elevator. The method can record data after each brake force detection, which is convenient for analysis. When the detection result is bad, the elevator is prohibited from running, and the elevator is allowed to run only after re-testing it to be normal. The present invention can solve the problems in the prior art that the brake force detection does not form a data record, data analysis and early warning cannot be performed, and the safety is low. Specifically, the method forms a data record of the brake detection data to analyze the trend of the data, and reminds the user in advance based on this to prevent it before it happens. And it has three forms of brake force detection: manual triggering, power-on triggering, and timed triggering.

[0004] The technical solution adopted by the present invention is:

[0005] A method for recording and analyzing brake force detection data of an elevator, wherein a data record is formed after each brake force detection, and all data records are stored. The data record is analyzed to determine whether the brake force is in a normal state. If it is determined that the brake force is in an abnormal state, the elevator is prohibited from running, and the user is prompted to check and repair in advance. After the repair, the elevator is re-tested and the brake force is determined to be in a normal state, and then the elevator resumes operation.

[0006] Furthermore, the braking force detection can be carried out in three forms: manual triggering, power-on triggering, and timing triggering.

[0007] Furthermore, the data record includes detection time, total detection times, triggering mode, moving distance, output torque, and detection results.

[0008] Furthermore, the abnormal state includes that the data record changes too quickly, the moving distance becomes larger and larger, and the data record is close to the braking failure judgment threshold.

[0009] Furthermore, the method can also query the total number of detections through data records.

[0010] Beneficial effects of the present invention:

[0011] The present invention records data after each brake force test, which is convenient for analysis. Whether the brake force is in a normal state is determined by analyzing changes in the data records. When the test result is poor, the elevator is prohibited from running. The elevator is allowed to run only after re-testing to find out that it is normal, thereby improving the safety and reliability of the elevator's brake force. DETAILED DESCRIPTION

[0012] To make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be described in detail below. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other implementation methods obtained by ordinary technicians in this field without making creative work belong to the scope of protection of the present invention.

[0013] Example:

[0014] The elevator brake force detection data recording and analysis method forms a data record after each brake force detection, and stores all data records. By analyzing the data records, it is determined whether the brake force is in a normal state. If it is determined that the brake force is in an abnormal state, the elevator is prohibited from running, and the user is prompted to check and repair in advance. After the repair, the elevator is re-tested and determined to be in a normal state, and then it resumes operation.

[0015] More specifically, the braking force detection can be in three forms: manual triggering, power-on triggering, and timing triggering.

[0016] More specifically, the manual triggering form includes the following steps: when the construction elevator is at the limit, click the "brake test" button on the screen, the system automatically performs a brake test, and simultaneously records the test time, total number of tests, trigger mode, moving distance, output torque, and test result data of this brake test. After analyzing the data trend of the brake force test, it is found that the test data has not changed much, then it is determined that the brake force is in a normal state.

[0017] More specifically, the power-on trigger form includes the following steps: turn on the power-on brake detection switch, when the construction elevator is at the limit, the system is powered on, the system automatically performs a brake test, and simultaneously records the test time, total number of tests, trigger mode, moving distance, output torque, and test result data of this brake test. After analyzing the data trend of the brake force test, it is found that the moving distance is getting larger and larger, then it is determined that the brake force is in an abnormal state, the user is prompted to check and repair in advance, and the elevator is prohibited from running. After maintenance, the elevator is re-tested and determined to be in a normal state after the brake force is determined to be in a normal state, and then it resumes operation.

[0018] More specifically, the timed trigger form includes the following steps: the system sets a timed brake detection function, and when the construction elevator is at the limit, the timed time is reached, the system automatically performs a brake detection, and simultaneously records the detection time, total number of detections, trigger mode, moving distance, output torque, and detection result data of this brake detection, analyzes the data trend of the brake force detection, and finds that the value is close to the brake failure judgment threshold, then it is determined that the brake force is in an abnormal state, prompts the user to check and repair in advance, and prohibits the elevator from running. After maintenance, the elevator resumes operation after re-testing and determining that the brake force is in a normal state.

[0019] More specifically, the method can also query the total number of detections through data records.

[0020] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A method for recording and analyzing brake force detection data of an elevator, characterized in that: The method forms a data record after each brake force detection and stores all data records. By analyzing the data record, it is determined whether the brake force is in a normal state. If it is determined that the brake force is in an abnormal state, the elevator is prohibited from running and the user is prompted to check and repair in advance. After the repair, the elevator is re-tested and determined to be in a normal state, and then it resumes operation.

2. A method for recording and analyzing brake force detection data of an elevator according to claim 1, characterized in that: The braking force detection can be carried out in three forms: manual triggering, power-on triggering, and timing triggering.

3. A method for recording and analyzing brake force detection data of an elevator according to claim 2, characterized in that: The data records include detection time, total detection times, triggering mode, moving distance, output torque, and detection results.

4. A method for recording and analyzing brake force detection data of an elevator according to claim 3, characterized in that: The abnormal state includes that the data record changes too quickly, the moving distance becomes larger and larger, and the data record approaches the braking failure judgment threshold.

5. The method for recording and analyzing brake force detection data of an elevator according to claim 4, characterized in that: This method can also query the total number of detections through data records.