A platform door system fault diagnosis and processing system and method

Abstract

The present invention provides a fault diagnosis and processing method and system for a platform door system. When a fault occurs in the platform door system, the fault validity is first judged through the fault record data and operation record data of the platform door system. Then, the fault is locked to a certain intermediate event by measuring the key point status of the platform door system, the fault record data and the operation record data of the platform door system, and the fault range is screened to limit the fault to two or three suspected faulty components. After the screening is completed, a fault troubleshooting process is generated according to the measurement difficulty, replacement difficulty and component damage probability of the components. The maintenance personnel find the cause of the fault and complete the fault processing according to the troubleshooting process. Direct dialogue between the equipment and the maintenance personnel can be achieved on the basis of adding a small amount of hardware, which effectively reduces the skill requirements of the maintenance personnel, improves the fault processing efficiency, and has strong popularization.

Description

Technical Field

[0001] The present invention relates to the technical field of intelligent fault processing, and in particular to a fault diagnosis and processing system and method for a platform door system. Background Art

[0002] With the rapid development of the subway platform door industry, platform door systems have been widely used. Once a platform door system fails, in order to ensure on-site safety before the fault is resolved, the station can only isolate the faulty sliding door. At this time, passengers at the corresponding position of the faulty sliding door can only get on and off the train through the adjacent boarding and alighting passage, which will directly increase the train's stop time at the station. In severe cases, it may even cause some passengers to be unable to get on and off the train. Therefore, the subway industry has high requirements for platform door fault handling.

[0003] The platform door system's records consist of fault records and operation records. These records are uploaded to the train control room, dispatch center, and workstations via an integrated monitoring system. These workstations often display information for all equipment on the entire line and are unable to effectively filter out fault records for a single system. Consequently, fault handling relies primarily on manual dialogue, and the information received by maintenance personnel is often very simple, making it difficult to effectively determine the status of on-site equipment. Furthermore, the integrated monitoring system can only display partial data from the platform door system, and much of the data is not uploaded through the integrated monitoring system. This data also prevents effective analysis of specific on-site conditions. Maintenance personnel can only analyze the on-site situation using the platform door system's fault and operation record data after arriving at the site, and conduct troubleshooting according to the corresponding fault handling process. This results in low response time and handling efficiency.

[0004] At the same time, during the daily inspection and maintenance of the platform door system, we found that the platform door system fault record data could not be directly used for fault analysis. Therefore, it was not possible to directly read the platform door system fault record data and compare it with the fault analysis model to guide on-site fault handling. There are several reasons for this situation:

[0005] 1. The platform door system fault records contain some faults caused by people or objects being trapped, or occasional equipment timeouts. However, the on-site equipment is actually functioning normally. If remote diagnosis is performed directly based on the platform door system fault records without conducting a validity analysis on the data, a large number of false alarms will be generated in the system.

[0006] 2. Due to the strong correlation between the control, power supply, and communication wiring of the platform door system, when some components fail, multiple valid fault records will appear simultaneously. The existing system can only list all faults and cannot effectively analyze the impact and scope of the fault;

[0007] 3. The existing platform door system's data collection points are not comprehensive enough to accurately analyze faults. Adding large numbers of sensors to the existing line would be costly and difficult, and these sensors could negatively impact the stability of the existing system.

[0008] 4. When a major fault occurs on site, the emergency repair process will not be initiated directly. The emergency repair process will be initiated only when the fault cannot be alleviated after the station staff's emergency response. If the fault is alleviated, the emergency repair process will not be initiated.

[0009] Therefore, how to establish a system and method that can directly connect accurate equipment with maintenance personnel, have high data accuracy and fault diagnosis capabilities has become an important issue before us.

[0010] In order to solve the above problems, people have been seeking an ideal technical solution. Summary of the Invention

[0011] The purpose of the present invention is to address the deficiencies of the prior art and thus provide a method and system for diagnosing and processing faults of a platform door system.

[0012] In order to achieve the above object, the technical solution adopted by the present invention is: a fault diagnosis and treatment method for a platform door system, comprising the following steps:

[0013] A fault analysis model for various faults is established based on the key measurement point monitoring data, fault record data, and operation record data of the platform door system. The fault analysis model includes top events, intermediate events, and bottom events.

[0014] Periodically obtain the platform door system's operation record data and key measurement point monitoring data;

[0015] When a fault occurs in the platform door system, the fault record data of the platform door system is received, and a fault validity analysis is performed based on the fault record data and / or the operation record data. When it is determined to be a valid fault, the fault level of the current fault phenomenon is determined according to a preset fault level classification table, and the fault level is sent to maintenance personnel;

[0016] Comparing the fault record data with top events of multiple fault analysis models to determine a fault analysis model, searching in the corresponding fault analysis model based on the fault record data and the operation record data to determine an intermediate event that causes the current fault phenomenon;

[0017] Determine whether the current fault analysis model contains key measurement point monitoring data. If so, search all bottom events corresponding to the intermediate event based on the key measurement point monitoring data to determine the suspected bottom event causing the current fault phenomenon. Otherwise, use all bottom events corresponding to the intermediate event as the suspected bottom event causing the current fault phenomenon.

[0018] A troubleshooting process is generated based on the measurement difficulty, replacement difficulty and damage probability of the suspected faulty components corresponding to all suspected bottom events, and the fault record data, the suspected faulty components and the troubleshooting process are sent to maintenance personnel for maintenance personnel to handle the fault based on the fault level, the fault record data, the suspected faulty components and the troubleshooting process.

[0019] Based on the above, after determining that a fault is valid and before determining the fault level, the fault record data may be compared with a preset emergency repair fault type and a preset conventional fault type to determine the fault type of the current fault phenomenon; if it is an emergency repair fault, an emergency repair effectiveness analysis is performed based on the operation record data and / or the fault record data and a preset judgment standard. When the operation record data meets the preset judgment standard, the emergency repair is determined to be valid and the emergency repair process is entered; otherwise, the emergency repair is determined to be invalid and the emergency repair process is not entered;

[0020] If it is a routine fault, there is no need to conduct emergency repair effectiveness analysis;

[0021] If the current fault is neither an emergency repair fault nor a conventional fault, the fault record data and the operation record data are sent to a technician for manual emergency repair effectiveness analysis to determine whether to enter the emergency repair process.

[0022] The present invention also provides a platform door system fault diagnosis and processing system, comprising a platform door system, a status monitoring module, a server, and a maintenance terminal. The server is equipped with a fault analysis model for multiple faults based on key measurement point monitoring data, fault record data, and operation record data of the platform door system. The fault analysis model includes top events, intermediate events, and bottom events.

[0023] The status monitoring module is connected to the platform door system and the server respectively, and is used to periodically read the operation record data and key measurement point monitoring data in the platform door system and upload them to the server;

[0024] The platform door system is further configured to upload fault record data to the server via the status monitoring module when a fault occurs;

[0025] The server includes a fault validity analysis module, a fault level classification module, an intermediate event screening module, a bottom event screening module and a fault troubleshooting process generation module.

[0026] The fault effectiveness analysis module is used to perform fault effectiveness analysis based on the fault record data and / or the operation record data;

[0027] The fault level classification module is connected to the fault validity analysis module and the maintenance terminal respectively, and is used to determine the fault level of the current fault phenomenon according to a preset fault level classification table when the fault validity analysis result is a valid fault, and send the fault level to the maintenance terminal;

[0028] The intermediate event screening module is connected to the fault validity analysis module and is used to compare the fault record data with the top events of multiple fault analysis models to determine the fault analysis model, and search in the corresponding fault analysis model based on the fault record data and the operation record data to determine the intermediate event that caused the current fault phenomenon;

[0029] The bottom event screening module is connected to the intermediate event screening module and is used to, when the current fault analysis model includes key measurement point monitoring data, search all bottom events corresponding to the intermediate events based on the key measurement point monitoring data to determine the suspected bottom event causing the current fault phenomenon; or, when the current fault analysis model does not include key measurement point monitoring data, use all bottom events corresponding to the intermediate events as the suspected bottom events causing the current fault phenomenon;

[0030] The troubleshooting process generation module is connected to the bottom event screening module and the maintenance terminal respectively, and is used to generate a troubleshooting process based on the measurement difficulty, replacement difficulty and damage probability of the suspected faulty components corresponding to all suspected bottom events, and send the fault record data, the suspected faulty components and the troubleshooting process to the maintenance terminal;

[0031] Maintenance personnel handle the fault according to the fault level, the fault record data, the suspected faulty component and the fault troubleshooting process on the maintenance terminal.

[0032] Based on the above, the status monitoring module includes a communication module, a remote communication module, a mode switch and a voltage detection module. The voltage detection module is used to perform voltage detection on key measurement points and obtain key measurement point monitoring data; the communication module is connected to the platform door system to receive the operation record data and fault record data uploaded by the platform door system; the remote communication module is connected to the server to upload the key measurement point monitoring data, operation record data and fault record data to the server; the mode switch is used to switch the working mode of the status monitoring module.

[0033] Based on the above, the fault diagnosis and processing system also includes a fault confirmation terminal, which is connected to the platform door system and the server respectively, and is used to display faults that cannot be identified by the platform door system, and upload manually confirmed fault record data to the server, so that after receiving the fault record data, the server directly compares the fault record data with the top events of multiple fault analysis models to determine the fault analysis model, so as to generate a fault troubleshooting process.

[0034] Compared with the prior art, the present invention has outstanding substantive features and significant progress. Specifically, when a platform door system fails, the fault validity is first judged through the platform door system fault record data and operation record data, and then the fault is locked to a certain intermediate event through the platform door system measurement of key point status, platform door system fault record data and operation record data, and the fault range is screened to limit the fault to two or three suspected faulty components. After the screening is completed, a fault troubleshooting process is generated according to the difficulty of component measurement, replacement difficulty and component damage probability. Maintenance personnel find the cause of the fault and complete the fault handling according to the troubleshooting process; direct dialogue between equipment and maintenance personnel can be achieved on the basis of adding a small amount of hardware, effectively reducing the skill requirements of maintenance personnel and improving fault handling efficiency. It can be applied to the upgrade and transformation of existing line equipment in various professions in the rail transit industry and has strong promotion potential.

[0035] The present invention also performs emergency repair effectiveness analysis based on the operation fault record after fault effectiveness judgment, so that emergency repairs can be carried out as soon as a serious fault occurs, which can effectively reduce the skill requirements of maintenance personnel and improve fault handling efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 It is a schematic flow diagram of the present invention.

[0037] Figure 2 This is a schematic diagram of the platform door system.

[0038] Figure 3 It is a schematic diagram of the safety circuit failure analysis model.

[0039] Figure 4 It is the unlock fault schematic.

[0040] Figure 5 It is a schematic diagram of the fault analysis model for unlocking faults.

[0041] Figure 6 This is a schematic diagram of multiple sliding door failures.

[0042] Figure 7 It is a system principle block diagram of the present invention. DETAILED DESCRIPTION

[0043] The technical solution of the present invention is further described in detail below through specific implementation methods.

[0044] At present, when a fault occurs in the existing platform door system, station personnel are required to perform emergency response first. If the fault cannot be alleviated after emergency response, the emergency repair process will be initiated. If the fault is alleviated, the emergency repair process will not be initiated.

[0045] As shown in the following table, different fault levels have different processing procedures:

[0046]

[0047] Since the platform door equipment is working, many data have extremely high similarities, as shown in the following table:

[0048]

[0049] As can be seen from the table above, different fault levels have different fault handling priorities. If the fault validity analysis and priority analysis are not performed after receiving the fault record data, and the fault record data is directly used, it will directly lead to alarm information errors in the system, which will directly affect on-site fault handling.

[0050] For this reason, Figure 1 As shown, the present invention provides a method for diagnosing and handling faults of a platform door system, comprising the following steps:

[0051] A fault analysis model for various faults is established based on the key measurement point monitoring data, fault record data, and operation record data of the platform door system. The fault analysis model includes top events, intermediate events, and bottom events.

[0052] Periodically obtain the platform door system's operation record data and key measurement point monitoring data;

[0053] When a fault occurs in the platform door system, the fault record data of the platform door system is received, and a fault validity analysis is performed based on the fault record data and / or the operation record data. When it is determined to be a valid fault, the fault level of the current fault phenomenon is determined according to a preset fault level classification table, and the fault level is sent to maintenance personnel;

[0054] Comparing the fault record data with top events of multiple fault analysis models to determine a fault analysis model, searching in the corresponding fault analysis model based on the fault record data and the operation record data to determine an intermediate event that causes the current fault phenomenon;

[0055] Determine whether the current fault analysis model contains key measurement point monitoring data. If so, search all bottom events corresponding to the intermediate event based on the key measurement point monitoring data to determine the suspected bottom event causing the current fault phenomenon. Otherwise, use all bottom events corresponding to the intermediate event as the suspected bottom event causing the current fault phenomenon.

[0056] A troubleshooting process is generated based on the measurement difficulty, replacement difficulty and damage probability of the suspected faulty components corresponding to all suspected bottom events, and the fault record data, the suspected faulty components and the troubleshooting process are sent to maintenance personnel for maintenance personnel to handle the fault based on the fault level, the fault record data, the suspected faulty components and the troubleshooting process.

[0057] When a platform door system fails, the effectiveness of the fault is first determined through the platform door system fault record data and operation record data. Then, the platform door system measures the key point status, the platform door system fault record data and the operation record data to lock the fault to a certain intermediate event, screen the fault range, and limit the fault to two or three suspected faulty components. After the screening is completed, a fault troubleshooting process is generated according to the measurement difficulty, replacement difficulty and component damage probability of the components. Maintenance personnel find the cause of the fault and complete the fault handling according to the troubleshooting process. Direct dialogue between equipment and maintenance personnel can be achieved based on the addition of a small amount of hardware, effectively reducing the skill requirements of maintenance personnel and improving fault handling efficiency. It can be applied to the upgrade and renovation of existing line equipment in various professions in the rail transit industry and has strong promotion potential.

[0058] When a major fault occurs on-site, the emergency repair process is not initiated immediately. It is only initiated when the fault cannot be alleviated after the station staff's emergency response. If the fault is alleviated, the emergency repair process will not be initiated. This places high technical requirements on station staff and can easily lead to the failure to be handled in a timely manner.

[0059] Therefore, in a specific implementation, after determining that a fault is valid and before determining the fault level, the fault record data may be compared with a preset emergency repair fault type and a preset conventional fault type to determine the fault type of the current fault phenomenon; if it is an emergency repair fault, an emergency repair effectiveness analysis is performed based on the operation record data and / or the fault record data and the preset judgment criteria; when the operation record data meets the preset judgment criteria, the emergency repair is determined to be valid and the emergency repair process is entered; otherwise, the emergency repair is determined to be invalid and the emergency repair process is not entered;

[0060] If it is a routine fault, there is no need to conduct emergency repair effectiveness analysis;

[0061] If the current fault is neither an emergency repair fault nor a conventional fault, the fault record data and the operation record data are sent to a technician for manual emergency repair effectiveness analysis to determine whether to enter the emergency repair process.

[0062] It can be understood that the effectiveness analysis of emergency repairs based on operational fault records allows emergency repairs to be carried out as soon as possible when serious faults occur, which can effectively reduce the skill requirements of maintenance personnel and improve fault handling efficiency.

[0063] It can be understood that after generating the troubleshooting process, the suspected faulty parts are matched with special test tools by searching the material library, and when there are special test tools, the name of the special test tool is sent to the maintenance terminal along with the fault record data, the suspected faulty parts and the troubleshooting process.

[0064] It can be understood that the specific steps of the troubleshooting process are generated based on the measurement difficulty, replacement difficulty, and damage probability of the suspected faulty components corresponding to all suspected bottom events as follows:

[0065] If all suspected faulty components can only be diagnosed by measurement, the suspected faulty components are ranked comprehensively based on the difficulty of component measurement * the probability of component damage;

[0066] If all suspected faulty parts can only be diagnosed by replacement, the suspected faulty parts will be ranked comprehensively based on the difficulty of replacing the parts * the probability of damage of the faulty parts. After the faulty parts are replaced, the system will automatically update the damage probability of the corresponding faulty parts.

[0067] If all suspected faulty components can be diagnosed using either the measurement method or the replacement method, the suspected faulty components are ranked comprehensively based on the measurement difficulty * probability of faulty component damage * difficulty of component replacement;

[0068] If there are suspected faulty components that can only be diagnosed by the measurement method, only by the replacement method, or by both the measurement method and the replacement method, they will be ranked within the group according to their respective ranking calculation methods, and then comprehensively ranked according to the weights of the different ranking calculation methods.

[0069] For ease of understanding, this embodiment takes the platform door system safety failure as an example to introduce in detail the steps of performing fault effectiveness analysis based on fault record data, screening bottom events using key monitoring point data, and performing emergency repair effectiveness analysis.

[0070] like Figure 2 The figure shows the schematic diagram of the current platform door system. Test points 1-4 are added key measurement points. Specifically, Test point 1 detects the source voltage of the safety circuit, Test point 2 detects the feedback voltage of the safety circuit, Test point 3 detects the source voltage of the safety circuit at the interface between the platform door system and the signaling system, and Test point 4 detects the feedback voltage of the safety circuit at the interface between the platform door system and the signaling system. Relay K1 is an internal safety circuit relay for the PEDC, responsible for feeding back the safety circuit status to the industrial computer and controlling the full door closure and the on / off of the lock indicator. Relay K2 is an external safety circuit relay, responsible for feeding back the platform door safety circuit status to the signaling system.

[0071] When the platform door system detects a safety circuit fault, the fault record data and the voltage monitoring data of detection points 1-4 are sent to the server. Specifically, the fault record data includes the fault phenomenon, the time when the fault occurs, and the time when the fault ends. According to the characteristics of the safety circuit fault, when the fault record data appears, it can be directly determined that a safety circuit fault occurs on site by analyzing the fault record data, and the relevant information is sent to the maintenance terminal.

[0072] When it is determined that a safety circuit fault occurs on site, since the safety circuit fault belongs to a preset emergency repair fault type, an emergency repair effectiveness analysis can also be performed based on the operation record data and / or the fault record data and the preset judgment standard. Specifically, the preset judgment standard is: after the door is opened and closed again on site, the safety circuit fault still exists or an interlock release instruction appears in the PSL; when the situation after the combination of the operation record data and the fault record data meets the above standard, it is determined that a persistent safety circuit fault occurs on site, and it is necessary to start the emergency repair process, send emergency repair information to relevant equipment management personnel, and carry out emergency repair; when the situation after the combination of the operation record data and the fault record data is: after the door is closed again on site, the safety circuit returns to normal, it is determined that an occasional safety circuit fault occurs on site;

[0073] Since the relevant information has been sent to the maintenance terminal when the fault first occurs, the relevant information will not be sent a second time.

[0074] After determining the validity of the fault, the fault record data is compared with the top events of multiple fault analysis models, and the fault analysis model of the safety circuit fault is selected, such as Figure 3 As shown, based on the fault record data and the operation record data, a search is performed in the corresponding fault analysis model to determine the intermediate event that caused the current fault phenomenon;

[0075] Since the current fault analysis model includes key measurement point monitoring data, a search is also performed in all bottom events corresponding to the intermediate events based on the key measurement point monitoring data to determine the suspected bottom event causing the current fault phenomenon.

[0076] Through the above operations, the number of safety circuit failure points can be reduced from the original 12 to 2-3. After receiving the relevant information, the maintenance personnel will rush to the scene with suspected faulty parts and maintenance tools according to the information prompts, and quickly handle the safety circuit failure according to the troubleshooting process prompted by the maintenance terminal.

[0077] Specifically, according to the safety circuit principle diagram, when the safety circuit fails, there are five states:

[0078] 1. No voltage is detected at test points 1, 2, and 4, but normal voltage is detected at test point 3. Since all other platform door functions are normal, the 24V power module is considered to be functioning properly. The cause of the fault is damage to circuit breaker S1, abnormal wiring, or a tripped circuit breaker. The system sends this information to the maintenance terminal, and maintenance personnel rush to the site with the circuit breaker and common maintenance tools.

[0079] If circuit breaker S1 is found not to have tripped on site, replace S1 after checking the wiring and finding no abnormalities.

[0080] If S1 is found to be tripped on site and the load is measured and no abnormality is found, try to restore the circuit breaker to the closed state. After the equipment returns to normal, observe for a period of time. If no abnormality is found, it is determined that the site has returned to normal. If the circuit breaker trips again, replace the circuit breaker and close it again;

[0081] If the load is short-circuited or the circuit breaker trips again after closing again, just check the short-circuit point of the load. After eliminating the short-circuit point, restore the circuit breaker to the closed state, the safety circuit returns to normal, and the fault is resolved.

[0082] 2. There is no voltage at detection points 2 and 4, but the voltage is normal at detection points 1 and 3. The fault is determined to be a faulty detection switch on a sliding door on that side. The system sends the relevant information to the maintenance terminal, and maintenance personnel rush to the site with the gate lock, detection switch, and special testing tools.

[0083] After arriving at the scene, the sliding door safety circuits are bypassed one by one by isolating the sliding doors one by one. When a certain sliding door is isolated and the safety circuit returns to normal, it is determined that the status of the sliding door detection switch is abnormal. A special test tool is used to test the status of the gate lock detection switch to determine the specific location of the fault detection switch. After checking that there is no abnormality in the wiring, the gate lock or detection switch is replaced according to the difficulty of replacing the detection switch, and the fault is resolved.

[0084] 3. There is no voltage at test point 4, but the voltage at test points 1, 2, and 3 is normal. The fault is determined to be a wiring or relay failure in the external safety circuit relay K2. The system sends the relevant information to the maintenance terminal, and maintenance personnel rush to the site with the relay and general maintenance tools.

[0085] After arriving at the site, check the wiring and find no abnormalities. Replace the safety circuit relay K2. After replacing the relay, the safety circuit returns to normal and the fault is resolved.

[0086] 4. There is no voltage at detection points 3 and 4, but the voltage at detection points 1 and 2 is normal. At this time, it is determined that the fault point is the abnormal voltage of the safety circuit detection source at the interface between the platform door system and the signal system. The system sends the relevant information to the maintenance terminal, and the maintenance personnel notify the signal department for a joint investigation. After the signal department restores power to the platform door, the safety circuit returns to normal and the fault is resolved.

[0087] 5. The voltages at test points 1-4 are all normal. The fault is determined to be in the wiring or the PEDC. The system sends the relevant information to the maintenance terminal, and maintenance personnel rush to the site with the PEDC and common maintenance tools.

[0088] After arriving at the site and checking the wiring and finding no abnormalities, the shield door controller PEDC was replaced. After replacing the shield door controller PEDC, the safety circuit returned to normal and the fault was resolved.

[0089] This embodiment takes the platform door system's gate lock detection switch failure causing the platform door system to report a sliding door unlocking failure as an example, and introduces in detail the steps of generating a fault effectiveness analysis and a troubleshooting process based on operation record data.

[0090] like Figure 4 The figure shows the workflow from the door machine controller DCU sending an unlock command to executing the sliding door opening part. During normal operation, after the door machine controller DCU sends an electromagnet attraction command, it determines whether the gate lock is normally unlocked by the lock-in-place switch status. After receiving the lock-in-place switch action status, the door machine controller DCU determines that the gate lock is normally unlocked and the sliding door opens. If the lock-in-place switch action status is not received, an unlock fault is reported.

[0091] When the platform door system detects an unlocking failure, it sends the fault record data to the server. The server first performs a validity analysis on the data. Because the unlocking failure may be caused by an occasional jam of the gate lock, resulting in an unlocking timeout, the presence of this fault record data cannot directly determine that the on-site equipment has failed. The server needs to perform a fault validity analysis based on the LCB isolation status or sliding door fully opened status corresponding to the operation record data after the fault record is generated. The analysis can be performed in the following two situations:

[0092] 1. After detecting an unlocking failure, when the LCB isolation status corresponding to the operation record data is read, it is judged that the equipment has been deactivated. A sliding door unlocking failure occurs on site, and the server sends relevant information to the maintenance terminal.

[0093] 2. After detecting an unlocking failure, the sliding door opening status corresponding to the operation record data is read, and it can be determined that the on-site equipment is working normally and the on-site failure is sporadic. The fault counting mode is turned on. If the fault record data appears repeatedly within a short period of time, it is determined that there is a hidden danger of sliding door unlocking failure on site, and the server will send the relevant information to the maintenance terminal.

[0094] Figure 5 To unlock the fault, we developed a fault analysis model. We learned that the suspected faulty components for this fault are the gate lock and DCU. The gate lock can be damaged or stuck.

[0095] First, the measurement difficulty, replacement difficulty, and damage probability of the two components corresponding to three situations are analyzed;

[0096] Part Name Measurement difficulty Difficulty of replacement Probability of damage Brake lock stuck 3 7 5.2 Damaged brake lock 7 3 3.2 DCU damaged 1 5 1.6

[0097] In the table, the higher the measurement difficulty and replacement difficulty, the lower the score. The score is scored by experts based on the characteristics of the equipment and is a fixed item. The higher the damage probability, the higher the score. The damage probability is updated in real time based on the results of each fault handling.

[0098] The damage and jamming of the gate lock in this fault can be determined through measurement and manual confirmation. Therefore, the components are scored using the method of measurement difficulty * damage probability. The scores are 22.4 points for gate lock damage, 15.6 points for gate lock jamming, and 1.6 points for DCU damage. Based on the score system, the troubleshooting sequence is to measure whether the gate lock is damaged, whether the gate lock is stuck, and replace the DCU.

[0099] Since the gate lock detection switch has a special test tool, the server will send the name of the suspected faulty component, the troubleshooting process and the name of the special test tool to the maintenance terminal. After receiving the relevant information, the maintenance personnel will rush to the scene with the DCU, gate lock, detection switch and maintenance tools according to the information prompts. According to the fault handling process prompted by the maintenance terminal, the special test tool is used to test the status of the gate lock detection switch. If a problem is detected in the gate lock detection switch, the gate lock or detection switch will be replaced, and the equipment will return to normal and the fault will be handled.

[0100] This embodiment takes the example of a wiring fault of the No. 4 sliding door opening command causing the platform door system to report multiple sliding door opening faults to explain the working principle of the system when multiple faults are detected.

[0101] Figure 6 This is the schematic diagram of the door opening control for the entire side of the platform door system. When a circuit breaker fault occurs in the outlet of a certain sliding door on the door opening command line, all the sliding doors behind the sliding door will fail to open in conjunction.

[0102] When the platform door system detects that sliding doors 4-N have sliding door opening failures at the same time, the fault record data is sent to the server. The server first performs a fault validity analysis. Since multiple sliding doors report failures at the same time on site and the fault record data are consistent, the possibility of false alarms can be ruled out, and it can be determined that the on-site equipment has multiple sliding doors that cannot open in conjunction.

[0103] After the server determines that multiple sliding door failures have occurred on site, it conducts an emergency repair effectiveness analysis. The judgment standard is whether three or more sliding doors are unable to open in a coordinated manner in a row. The on-site fault record data is that 4-N sliding doors cannot be opened in a coordinated manner, which meets the above fault description. Further, based on the operation record data, it is determined that a level one failure has occurred on site and an emergency repair process needs to be initiated. The server sends the relevant information to the maintenance terminal and directly initiates the emergency repair process.

[0104] The server can also directly determine whether the fault is caused by a problem with the outgoing line of sliding door 4 or the incoming line of sliding door 5 (the two ends of the same line) based on the on-site fault record data and the actual wiring conditions of the equipment; after receiving the relevant information, the maintenance personnel rush to the scene after connecting the wires, multimeter and maintenance tools according to the prompts in the information, and check the wiring of the two sliding doors according to the fault handling process prompted by the maintenance terminal. After detecting that the fault is caused by abnormal wiring of the outgoing line of sliding door 4, the outgoing line of sliding door 4 is reconnected, and the equipment returns to normal and the fault is handled.

[0105] If the on-site wiring is that odd-numbered doors are controlled one way and even-numbered doors are controlled another way, then when the above fault occurs, the even-numbered sliding doors after No. 4 will not be able to open in conjunction. At this time, although multiple sliding doors cannot open in conjunction at the same time, the judgment condition of three consecutive doors is not met. It can be determined that the on-site secondary fault does not require the initiation of the emergency repair process. The server can send the fault level and cause analysis to the maintenance terminal.

[0106] If multiple sliding doors report different fault record data at the same time on site, engineers will need to analyze the fault record data to determine whether a complex fault has occurred or a false alarm has been caused by communication data disorder. Based on the analysis results, they will decide whether emergency repairs are needed and provide maintenance personnel with troubleshooting ideas.

[0107] It can be understood that the fault level classification table includes multiple fault levels and the fault phenomena corresponding to each fault level; wherein different fault levels have different fault impacts and fault potentials, and the greater the fault impact and fault potential, the higher the fault level;

[0108] After receiving the fault level, the maintenance personnel will look up the fault level and processing flow comparison table, obtain the response priority and response strategy corresponding to the current fault level, and execute them. Different fault levels correspond to different response priorities and response strategies.

[0109] Example 2

[0110] This embodiment provides a fault diagnosis and processing system for a platform door system, such as Figure 7 As shown, it includes a platform door system, a status monitoring module, a server, and a maintenance terminal. The server has a built-in fault analysis model for multiple faults based on the key measurement point monitoring data, fault record data, and operation record data of the platform door system. The fault analysis model includes top events, intermediate events, and bottom events.

[0111] The status monitoring module is connected to the platform door system and the server respectively, and is used to periodically read the operation record data and key measurement point monitoring data in the platform door system and upload them to the server;

[0112] The platform door system is further configured to upload fault record data to the server via the status monitoring module when a fault occurs;

[0113] The server includes a fault validity analysis module, a fault level classification module, an intermediate event screening module, a bottom event screening module and a fault troubleshooting process generation module.

[0114] The fault effectiveness analysis module is used to perform fault effectiveness analysis based on the fault record data and the operation record data;

[0115] The fault level classification module is connected to the fault validity analysis module and the maintenance terminal respectively, and is used to determine the fault level of the current fault phenomenon according to a preset fault level classification table when the fault validity analysis result is a valid fault, and send the fault level to the maintenance terminal;

[0116] The intermediate event screening module is connected to the fault validity analysis module and is used to compare the fault record data with the top events of multiple fault analysis models to determine the fault analysis model, and search in the corresponding fault analysis model based on the fault record data and the operation record data to determine the intermediate event that caused the current fault phenomenon;

[0117] The bottom event screening module is connected to the intermediate event screening module and is used to, when the current fault analysis model includes key measurement point monitoring data, search all bottom events corresponding to the intermediate events based on the key measurement point monitoring data to determine the suspected bottom event causing the current fault phenomenon; or, when the current fault analysis model does not include key measurement point monitoring data, use all bottom events corresponding to the intermediate events as the suspected bottom events causing the current fault phenomenon;

[0118] The troubleshooting process generation module is connected to the bottom event screening module and the maintenance terminal respectively, and is used to generate a troubleshooting process based on the measurement difficulty, replacement difficulty and damage probability of the suspected faulty components corresponding to all suspected bottom events, and send the fault record data, the suspected faulty components and the troubleshooting process to the maintenance terminal;

[0119] Maintenance personnel handle the fault according to the fault level, the fault record data, the suspected faulty component and the fault troubleshooting process on the maintenance terminal.

[0120] In a specific implementation, the status monitoring module includes a communication module, a remote communication module, a mode switch and a voltage detection module. The voltage detection module is used to perform voltage detection on key measurement points and obtain key measurement point monitoring data; the communication module is connected to the platform door system to receive operation record data and fault record data uploaded by the platform door system; the remote communication module is connected to the server to upload key measurement point monitoring data, operation record data and fault record data to the server; the mode switch is used to switch the working mode of the status monitoring module.

[0121] The working modes of the status monitoring module include operation mode and maintenance mode. When using the maintenance mode, the mode switch is switched to the bypass position, and the system will no longer detect the operating status of the platform door system; when the maintenance is completed and the operation mode is to be entered, the mode switch is switched to the automatic position, and the system starts to detect the operating status of the platform door system.

[0122] It should be noted that there are some faults on site that cannot be detected by the platform door system, as shown in the following table:

[0123] Fault level Fault phenomenon illustrate Level 3 The sliding door vibrates, makes unusual noises, or opens and closes slowly The platform door system does not have the function to detect this type of fault. Level 1 Door glass cracks The platform door system does not have the function of detecting cracks in the door glass. Level 4 Abnormal indicator light The platform door system does not have the function of detecting the working status of various indicator lights on site. Level 4 End door failure The opening and closing of the end doors rely on manual operation, and the platform door system does not have the function of detecting such faults. Level 2 PSL switch or button failure The PSL switches or buttons rely on manual operation, and the platform door system does not have the function of detecting such faults.

[0124] When the above faults occur on site, the platform door system cannot identify the specific conditions of the on-site equipment. Under the original system, the impact of the above problems can only be analyzed manually, which requires a high level of personnel skills and may lead to misjudgment.

[0125] In order to solve the above technical problems, in a specific implementation, the fault diagnosis and processing system also includes a fault confirmation terminal, which is connected to the platform door system and the server respectively, and is used to display faults that cannot be identified by the platform door system, and upload manually confirmed fault record data to the server, so that after receiving the fault record data, the server directly compares the fault record data with the top events of multiple fault analysis models to determine the fault analysis model, so as to generate a fault troubleshooting process.

[0126] When using this system, station personnel only need to click on the corresponding component icon, select the corresponding fault phenomenon in the pop-up window, manually confirm the equipment fault phenomenon, and upload the equipment fault phenomenon, fault occurrence time and fault end time to the server; since this method uses manual judgment, it can directly judge that an equipment fault has occurred on site, and there is no need to perform fault effectiveness analysis in the server. Instead, it can directly perform emergency repair effectiveness analysis and determine the bottom event to complete the fault analysis work.

[0127] It can be understood that the specific steps for the status monitoring module to periodically read the operation record data and key measurement point monitoring data in the platform door system and upload them to the server are as follows:

[0128] With T as the period, periodically read the operation record data of the platform door system and the monitoring data of key measurement points;

[0129] When data is read for the i-th time, the data read for the i-th time is compared with the stored data read for the i-1-th time. If they are consistent, the data read for the i-th time is determined to be valid data, the data read for the i-th time is uploaded to the server, the data read for the i-1-th time is deleted, and the data read for the i-th time is stored;

[0130] If they are inconsistent, the data read for the i-1th time will be deleted first, and the data read for the ith time will be stored. When the data is read for the i+1th time, the stored data read for the ith time will be compared with the data read for the i+1th time. When the data are consistent, it is determined that the data read for the ith time and the data read for the i+1th time are both valid data, the data read for the ith time and the data read for the i+1th time will be uploaded to the server, the data read for the ith time will be deleted, and the data read for the i+1th time will be stored. If the data are inconsistent, the data read for the ith time will be deleted, the data read for the i+1th time will be stored, and the data read for the i+2th time will be waited for.

[0131] By judging the validity of data through the above steps, the occurrence of false alarms caused by accidental events can be eliminated.

[0132] Furthermore, after receiving the valid data, the server determines whether there is fault record data in the valid data. If so, the server starts the fault analysis process; otherwise, the server continues to wait for receiving the next valid data.

[0133] Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention and not to limit it. Although the present invention has been described in detail with reference to the preferred embodiments, ordinary technicians in the field should understand that the specific implementation methods of the present invention can still be modified or some technical features can be replaced by equivalents without departing from the spirit of the technical solution of the present invention. They should all be included in the scope of the technical solution for protection of the present invention.

Claims

1. A method for diagnosing and handling faults of a platform door system, characterized in that: The following steps are involved: A fault analysis model for various faults is established based on the key measurement point monitoring data, fault record data, and operation record data of the platform door system. The fault analysis model includes top events, intermediate events, and bottom events. Periodically obtain the platform door system's operation record data and key measurement point monitoring data; When a fault occurs in the platform door system, the fault record data of the platform door system is received, and a fault validity analysis is performed based on the fault record data and / or the operation record data. When it is determined to be a valid fault, the fault record data is compared with a preset emergency repair fault type and a preset conventional fault type to determine the fault type of the current fault phenomenon; If the fault is an emergency repair, the effectiveness of the emergency repair is analyzed based on the operation record data and / or the fault record data and the preset judgment criteria. If the operation record data meets the preset judgment criteria, the emergency repair is determined to be effective and the emergency repair process is entered; otherwise, the emergency repair is determined to be invalid and the emergency repair process is not entered, and the fault level determination step is entered; If it is a routine fault, there is no need to conduct emergency repair effectiveness analysis and the fault level determination step can be directly entered; If the current fault is neither an emergency repair fault nor a routine fault, the fault record data and the operation record data are sent to a technician for manual emergency repair effectiveness analysis to determine whether to enter the emergency repair process or the fault level determination step; The fault level determination step is to determine the fault level of the current fault phenomenon according to a preset fault level classification table, and send the fault level to maintenance personnel; Comparing the fault record data with top events of multiple fault analysis models to determine a fault analysis model, searching in the corresponding fault analysis model based on the fault record data and the operation record data to determine an intermediate event that causes the current fault phenomenon; Determine whether the current fault analysis model contains key measurement point monitoring data. If so, search all bottom events corresponding to the intermediate event based on the key measurement point monitoring data to determine the suspected bottom event that caused the current fault phenomenon. Otherwise, all bottom events corresponding to the intermediate event are regarded as suspected bottom events causing the current fault phenomenon; A troubleshooting process is generated based on the measurement difficulty, replacement difficulty and damage probability of the suspected faulty components corresponding to all suspected bottom events, and the fault record data, the suspected faulty components and the troubleshooting process are sent to maintenance personnel for maintenance personnel to handle the fault based on the fault level, the fault record data, the suspected faulty components and the troubleshooting process.

2. The platform door system fault diagnosis and treatment method according to claim 1, characterized in that: After generating the troubleshooting process, the suspected faulty parts are matched with special test tools by searching the material library, and when there are special test tools, the name of the special test tool is sent to the maintenance personnel along with the fault record data, the suspected faulty parts and the troubleshooting process.

3. The method for diagnosing and handling faults of a platform door system according to claim 1, characterized in that: The fault level classification table includes multiple fault levels and the fault phenomena corresponding to each fault level; wherein different fault levels have different fault impacts and fault potentials, and the greater the fault impact and fault potential, the higher the fault level; After receiving the fault level, the maintenance personnel will look up the fault level and processing flow comparison table, obtain the response priority and response strategy corresponding to the current fault level, and execute them. Different fault levels correspond to different response priorities and response strategies.

4. The platform door system fault diagnosis and treatment method according to claim 1, characterized in that: The specific steps for generating a troubleshooting process based on the measurement difficulty, replacement difficulty, and damage probability of the suspected faulty components corresponding to all suspected bottom events are as follows: If all suspected faulty components can only be diagnosed by measurement, the suspected faulty components are ranked comprehensively based on the difficulty of component measurement * the probability of component damage; If all suspected faulty parts can only be diagnosed by replacement, the suspected faulty parts are ranked comprehensively based on the difficulty of replacing the parts and the probability of damage to the faulty parts. If all suspected faulty components can be diagnosed using either the measurement method or the replacement method, the suspected faulty components are ranked comprehensively based on the measurement difficulty * probability of faulty component damage * difficulty of component replacement; If there are suspected faulty components that can only be diagnosed by the measurement method, only by the replacement method, or by both the measurement method and the replacement method, they will be ranked within the group according to their respective ranking calculation methods, and then comprehensively ranked according to the weights of the different ranking calculation methods.

5. A fault diagnosis and processing system for a platform door system, characterized by: It includes a platform door system, a status monitoring module, a server and a maintenance terminal. The server has a built-in fault analysis model for multiple faults based on the key measurement point monitoring data, fault record data and operation record data of the platform door system. The fault analysis model includes top events, intermediate events and bottom events. The status monitoring module is connected to the platform door system and the server respectively, and is used to periodically read the operation record data and key measurement point monitoring data in the platform door system and upload them to the server; The platform door system is further configured to upload fault record data to the server via the status monitoring module when a fault occurs; The server includes a fault validity analysis module, a fault level classification module, an intermediate event screening module, a bottom event screening module and a fault troubleshooting process generation module. The fault validity analysis module is configured to perform fault validity analysis based on the fault record data and / or the operation record data. When a fault is determined to be valid, the fault record data is compared with a preset emergency repair fault type and a preset conventional fault type to determine the fault type of the current fault phenomenon; If the fault is an emergency repair, the effectiveness of the emergency repair is analyzed based on the operation record data and / or the fault record data and the preset judgment criteria. If the operation record data meets the preset judgment criteria, the emergency repair is determined to be effective and the emergency repair process is entered; otherwise, the emergency repair is determined to be invalid and the emergency repair process is not entered, and the fault level determination step is entered; If it is a routine fault, there is no need to conduct emergency repair effectiveness analysis and the fault level determination step can be directly entered; If the current fault is neither an emergency repair fault nor a routine fault, the fault record data and the operation record data are sent to a technician for manual emergency repair effectiveness analysis to determine whether to enter the emergency repair process or the fault level determination step; The fault level classification module is connected to the fault validity analysis module and the maintenance terminal respectively, and is used to perform a fault level determination step, wherein the fault level determination step is to determine the fault level of the current fault phenomenon according to a preset fault level classification table and send the fault level to the maintenance terminal; The intermediate event screening module is connected to the fault validity analysis module and is used to compare the fault record data with the top events of multiple fault analysis models to determine the fault analysis model, and search in the corresponding fault analysis model based on the fault record data and the operation record data to determine the intermediate event that caused the current fault phenomenon; The bottom event screening module is connected to the intermediate event screening module and is used to search among all bottom events corresponding to the intermediate events based on the key measurement point monitoring data to determine the suspected bottom event causing the current fault phenomenon when the current fault analysis model contains key measurement point monitoring data; Alternatively, when the current fault analysis model does not include key measurement point monitoring data, all bottom events corresponding to the intermediate events are regarded as suspected bottom events causing the current fault phenomenon; The troubleshooting process generation module is connected to the bottom event screening module and the maintenance terminal respectively, and is used to generate a troubleshooting process based on the measurement difficulty, replacement difficulty and damage probability of the suspected faulty components corresponding to all suspected bottom events, and send the fault record data, the suspected faulty components and the troubleshooting process to the maintenance terminal. The maintenance personnel perform fault processing according to the fault level, the fault record data, the suspected faulty components and the troubleshooting process on the maintenance terminal.

6. A platform door system fault diagnosis and processing system according to claim 5, characterized in that: The status monitoring module includes a communication module, a remote communication module, a mode switch and a voltage detection module. The voltage detection module is used to perform voltage detection on key measurement points and obtain key measurement point monitoring data; the communication module is connected to the platform door system to receive operation record data and fault record data uploaded by the platform door system; the remote communication module is connected to the server to upload key measurement point monitoring data, operation record data and fault record data to the server; the mode switch is used to switch the working mode of the status monitoring module.

7. The platform door system fault diagnosis and processing system according to claim 5, characterized in that: The fault diagnosis and processing system also includes a fault confirmation terminal, which is connected to the platform door system and the server respectively, and is used to display faults that cannot be identified by the platform door system, and upload manually confirmed fault record data to the server, so that after receiving the fault record data, the server directly compares the fault record data with the top events of multiple fault analysis models to determine the fault analysis model, so as to generate a fault troubleshooting process.

8. A platform door system fault diagnosis and processing system according to claim 5, characterized in that: The specific steps for the status monitoring module to periodically read the operation record data and key measurement point monitoring data in the platform door system and upload them to the server are as follows: With T as the period, periodically read the operation record data of the platform door system and the monitoring data of key measurement points; When data is read for the i-th time, the data read for the i-th time is compared with the stored data read for the i-1-th time. If they are consistent, the data read for the i-th time is determined to be valid data, the data read for the i-th time is uploaded to the server, the data read for the i-1-th time is deleted, and the data read for the i-th time is stored; If they are inconsistent, the data read for the i-1th time will be deleted first, and the data read for the ith time will be stored. When the data is read for the i+1th time, the stored data read for the ith time will be compared with the data read for the i+1th time. When the data are consistent, it is determined that the data read for the ith time and the data read for the i+1th time are both valid data, the data read for the ith time and the data read for the i+1th time will be uploaded to the server, the data read for the ith time will be deleted, and the data read for the i+1th time will be stored. If the data are inconsistent, the data read for the ith time will be deleted, the data read for the i+1th time will be stored, and the data read for the i+2th time will be waited for.

9. A platform door system fault diagnosis and processing system according to claim 8, characterized in that: After receiving the valid data, the server determines whether there is fault record data in the valid data. If so, the server starts the fault analysis process; otherwise, the server continues to wait for receiving the next valid data.

Images