Motor train unit braking system detection method, terminal equipment and computer readable storage medium

Abstract

The invention relates to the technical field of rail transit, and provides a motor train unit braking system detection method, terminal equipment and a computer readable storage medium. The method comprises the steps that a detection request for the braking system is received, the detection request comprises a safety identifier, and a safety detection condition corresponding to the detection request is obtained; acquiring working condition data corresponding to the safety detection condition; if the working condition data meets the security detection condition, executing a detection task corresponding to the detection request to obtain a detection result, and sending the detection result to the detection terminal; and if the working condition data does not meet the safety detection condition, not executing the detection task corresponding to the detection request, and sending a non-safety detection result to the detection terminal. The detection terminal only needs to send an instruction once to obtain a detection result or a result which does not accord with safety detection, so that the data interaction frequency between the detection terminal and the motor train unit braking system is greatly reduced, and the detection efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the field of rail transit technology, and in particular to a method for detecting a braking system of an EMU, a terminal device and a computer-readable storage medium. Background Art

[0002] The Harmony series, Fuxing series of distributed power EMUs and urban rail EMUs all use a microcomputer-controlled direct electric-pneumatic brake system. The brake system is mainly composed of a composite brake consisting of an electronic brake control unit EBCU (Electronic Brake Control Unit) and a pneumatic brake control unit PBCU (Pneumatic Brake Control Unit). The EBCU generates electric brakes for regenerative braking, which decelerate the EMU by generating electricity through the reverse rotation of the motor. The electric brake force of each EMU is affected by the specific characteristics of the traction system of the vehicle, which is calculated by the traction control unit (TCU) and sent to the electronic brake control unit (EBCU). Under the control of the EBCU, the PBCU generates air brakes corresponding to the braking instructions and controls the basic brake device to generate braking force. The PBCU is mainly composed of charging and exhaust solenoid valves, emergency brake solenoid valves, empty and loaded vehicle valves, relay valves, pressure sensors and pressure switches. The air brakes are distributed in all cars of the train, and the EMU is decelerated by the friction between the brake discs and the friction pairs. Its capacity value depends on the theoretical adhesion limit between the wheel and rail and the difference in the number of brake discs between each car.

[0003] Among them, the braking system includes not only EBCU and PBCU, but also EMU information control and monitoring platform, speed monitoring and safety processing unit, communication network unit, rescue supervision processing unit, base station and platform service terminal; and PBCU includes pneumatic clamps, brake pads and brake disc groups, and the brake disc group includes brake discs and disc hubs; and so on.

[0004] Currently, before performing a certain inspection task on the EMU brake system, it is necessary to send multiple instructions to obtain the corresponding working condition data to determine whether it meets the safety inspection conditions. However, the EMU brake system has many components and many inspection tasks, and each inspection task requires multiple instructions to be sent, resulting in low inspection efficiency. Summary of the invention

[0005] The purpose of the present invention is to provide a method for detecting a brake system of an EMU, a terminal device and a computer-readable storage medium, aiming to solve the technical problem of low detection efficiency in existing detection methods.

[0006] In a first aspect, the present application provides a method for detecting a brake system of an EMU, the method comprising:

[0007] receiving a detection request for a brake system, wherein the detection request includes a safety identifier, and obtaining a safety detection condition corresponding to the detection request;

[0008] Acquiring operating condition data corresponding to the safety detection condition;

[0009] If the working condition data meets the safety detection condition, the detection task corresponding to the detection request is executed, the detection result is obtained, and sent to the detection terminal;

[0010] If the operating condition data does not meet the safety detection condition, the detection task corresponding to the detection request is not executed, and a safety detection result that does not meet the requirements is sent to the detection terminal.

[0011] In a second aspect, the present application provides a terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements any of the methods described above when executing the computer program.

[0012] In a third aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method described in any one of the above items is implemented.

[0013] The beneficial effects of a motor vehicle brake system detection method, terminal device and computer-readable storage medium provided by the present invention are: identifying the safety detection conditions corresponding to the detection request, and obtaining the working condition data corresponding to the safety detection conditions; if the working condition data meets the safety detection conditions, executing the detection task corresponding to the detection request, obtaining the detection result, and sending it to the detection terminal; if the working condition data does not meet the safety detection conditions, then the detection task is not executed, and the non-compliant safety detection result is sent to the detection terminal; based on this, the detection terminal only needs to send an instruction (i.e., a detection request) once to obtain the detection result or the non-compliant safety detection result; the detection method is based on a detection A request is made to actively obtain corresponding multiple working condition data (for example, including the speed of the EMU, the start and stop status of the braking system, the working status of the corresponding detection component, the temperature of the corresponding detection component, etc.). The detection terminal does not need to send an inquiry instruction for each working condition data, that is, there is no need to send multiple instructions to obtain multiple working condition data corresponding to the safety detection conditions, and there is no need to judge whether the safety detection conditions are met based on the working condition data, and there is no need to send instructions to execute the detection task after the safety detection conditions are met. This greatly reduces the number of data exchanges between the detection terminal and the EMU braking system, solves the technical problem of low detection efficiency in existing detection methods, and improves detection efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0015] Figure 1 A schematic flow chart of a method for detecting a braking system of an EMU provided by an embodiment of the present invention;

[0016] Figure 2 A schematic diagram of another flow chart of the EMU braking system detection method provided in this embodiment;

[0017] Figure 3 A schematic diagram of another flow chart of the EMU braking system detection method provided in this embodiment;

[0018] Figure 4 A schematic diagram of another flow chart of the EMU braking system detection method provided in this embodiment;

[0019] Figure 5 A schematic diagram of a terminal device provided in this embodiment.

[0020] Among them, the reference numerals in the figure are:

[0021] 1. Terminal device; 11. Memory; 12. Processor; 13. Computer program. DETAILED DESCRIPTION

[0022] Embodiments of the present invention are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present invention, and should not be construed as limiting the present invention.

[0023] Reference throughout the specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, when the phrases "in one embodiment" or "in some embodiments" appear in various places throughout the specification, not all references are to the same embodiment. Furthermore, in one or more embodiments, the particular features, structures, or characteristics may be combined in any suitable manner.

[0024] In the description of the present invention, it should be understood that the terms "length", "width", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside", etc., indicating the orientation or position relationship are based on the orientation or position relationship shown in the drawings, and are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the present invention.

[0025] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features.

[0026] In the present invention, unless otherwise clearly specified and limited, the terms "installed", "connected", "connected", "fixed" and the like should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, it can be the internal connection of two elements or the interaction relationship between two elements. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0027] Embodiment 1

[0028] Combination Figure 1 The EMU braking system detection method provided in this embodiment includes the following steps:

[0029] S100: receiving a detection request for a braking system, and obtaining safety detection conditions corresponding to the detection request.

[0030] S200: Acquire operating condition data corresponding to safety detection conditions.

[0031] S300: If the operating condition data meets the safety detection conditions, the detection task corresponding to the detection request is executed, the detection result is obtained, and it is sent to the detection terminal. Specifically, executing the detection task may involve starting a specific detection program, algorithm or test process. For example, the detection task is to read the fault code and real-time data stream of the EMU through the OBD interface of the EMU. After the diagnostic system or sensor of the EMU performs the detection task, the braking system collects and organizes the detection results. Optionally, the braking system packages the detection results into a format suitable for transmission, which involves converting the data into a standardized message format, such as XML, and may include encryption and security measures to ensure the integrity of the data during transmission. The EMU braking system needs to select a suitable communication protocol to send data. Different protocols have different transmission speeds, power consumption and coverage.

[0032] S400: If the operating condition data does not meet the safety detection conditions, the detection task corresponding to the detection request is not executed, and the non-safety detection result is sent to the detection terminal. For example, if the air pressure of the EMU brake system exceeds the safety value, some detection tasks do not allow emission detection until the air pressure returns to normal.

[0033] The detection terminal refers to a device with detection functions, which is used for physical status, monitoring environment, equipment performance, etc. In the process of detecting or diagnosing the EMU, the detection terminal can be a high-speed train EMU equipment diagnostic service tool (PTU) or an EMU operation fault image detection system (TEDS), which reads the EMU fault code and real-time data stream through the EMU's OBD interface.

[0034] Generally, before performing a detection task on the EMU brake system, safety detection conditions must be met. For example, when detecting the wear of the brake pads or brake discs of the PBCU, it is necessary to meet the following working conditions: the EMU speed is zero, the PBCU is in a non-working state, the air pressure of the PBCU is within the safe air pressure range, and the brake pads or brake discs are in a released state. This detection method integrates the corresponding multiple working condition data into the safety detection conditions corresponding to the detection request, that is, one detection request corresponds to one safety detection condition, and one safety detection condition includes at least one working condition data, and generally includes multiple working condition data. In addition, one detection request corresponds to one detection task, and when the corresponding safety detection conditions are met, the corresponding detection task is executed.

[0035] The specific process of this detection method is: identify the safety detection conditions corresponding to the detection request, and obtain the operating condition data corresponding to the safety detection conditions; if the operating condition data meets the safety detection conditions, execute the detection task corresponding to the detection request, obtain the detection result, and send it to the detection terminal; if the operating condition data does not meet the safety detection conditions, do not execute the detection task, and send the non-compliant safety detection result to the detection terminal.

[0036] Based on this, the detection terminal only needs to send an instruction (i.e., a detection request) once to obtain the detection result or the result that does not meet the safety detection result; the detection method actively obtains the corresponding multiple working condition data (for example, including the speed of the EMU, the start and stop status of the braking system, the working status of the corresponding detection component, the temperature of the corresponding detection component, etc.) according to a detection request. The detection terminal does not need to send an inquiry instruction for each working condition data, that is, there is no need to send multiple instructions to obtain multiple working condition data corresponding to the safety detection conditions, and there is no need to judge whether the safety detection conditions are met based on the working condition data, and there is no need to send instructions to execute the detection task after the safety detection conditions are met. This greatly reduces the number of data exchanges between the detection terminal and the EMU braking system, solves the technical problem of low detection efficiency in existing detection methods, and improves detection efficiency.

[0037] Among them, the EMU braking system has a preset database, which stores the correspondence between detection requests and safety detection conditions, the correspondence between safety detection conditions and working condition data, the correspondence between detection requests and detection tasks, and so on.

[0038] Specifically, inside the EMU braking system, the EMU braking system - for example, a preset database - simultaneously sends the safety detection conditions and detection tasks corresponding to the detection request to the electronic brake control unit EBCU, and the EBCU will automatically determine whether the various operating conditions meet the safety detection conditions. If not, "does not meet the safety detection results" will be returned to the EMU braking system. If it meets, the detection task will be directly executed and the detection results will be returned. Based on this, the EMU braking system does not need to first send the safety detection conditions to the EBCU, wait for the EBCU to return that the safety detection conditions are met, and then send the detection task to the EBCU, which reduces the number of instructions sent and can improve detection efficiency.

[0039] Some inspection tasks do not require prior inspection to determine whether they meet safety inspection conditions. For example, when testing the air pressure or temperature of a certain component, they can be executed regardless of the surrounding environment, system operating status, EMU speed and other operating conditions.

[0040] In some embodiments, in combination Figure 2 , step S100 includes:

[0041] S111: Obtain the security detection symbol corresponding to the detection request.

[0042] S112: If the safety detection character is the first character, proceed to step S300. That is, the detection task is directly executed, reducing the steps of obtaining the safety detection conditions corresponding to the detection request and obtaining the working condition data corresponding to the safety detection conditions, and there is no need to determine whether the working condition data meets the safety detection conditions, thereby improving the processing efficiency and accuracy.

[0043] S113: If the security detection character is the second character, obtain the security detection condition corresponding to the detection request. In this application, the first character is "true" and the second character is "false".

[0044] In an embodiment of the present application, after receiving a detection request, the brake system obtains the corresponding safety detection character to determine whether it is necessary to pre-detect the safety detection condition. If the safety detection character is the first character, it means that the safety detection condition does not need to be detected, and the system can directly execute the detection request. If the safety detection character is the second character, it means that the detection request is rejected when the safety detection condition is not met.

[0045] Specifically, the preset database stores the corresponding relationship between the detection request and the security detection symbol.

[0046] Specifically, the EMU braking system obtains the model information, working status, surrounding environment and other information of each braking component through its own EMU information control and monitoring platform, and obtains the EMU speed, various fault codes and corresponding fault information through its own speed monitoring and safety processing unit.

[0047] In some embodiments, the safety detection condition includes multiple safety sub-conditions. The operating condition data includes data corresponding to each safety sub-condition. Figure 3 After step S200, the detection method further includes:

[0048] S210: Determine whether each safety sub-condition is satisfied according to the operating condition data corresponding to each safety sub-condition.

[0049] S220: If there is a safety sub-condition that is not met, it is determined that the operating condition data does not meet the safety detection condition.

[0050] S230: If all safety sub-conditions are met, it is determined that the operating condition data meets the safety detection conditions.

[0051] In the embodiment of the present application, the safety detection condition is composed of multiple safety sub-conditions, and these safety sub-conditions together define the complete safety detection condition that the system needs to meet.

[0052] In one embodiment, the detection method further comprises:

[0053] S211: If the security sub-condition is met, create or update the first sub-identifier in the preset database.

[0054] S212: If the security sub-condition is not satisfied, a second sub-identifier is created or updated in the preset database. The first sub-identifier is "true" and the second sub-identifier is "false". A security sub-condition has only one first sub-identifier or one second sub-identifier, that is, when the first sub-identifier of a security sub-condition is updated, the first sub-identifier or one second sub-identifier of the security sub-condition is deleted.

[0055] In the embodiment of the present application, the EBCU of the EMU needs to write logic to process the operation of storing the safety sub-condition and the first sub-identifier or the second sub-identifier in the preset database, which usually involves using SQL statements or other database operation languages ​​to perform insert operations, and the system executes the storage logic to store the safety sub-condition and the first sub-identifier or the second sub-identifier as records in the preset database. The storage operation may need to process details such as data format and data type conversion.

[0056] Based on this, the preset database stores the first sub-identifier or the second sub-identifier corresponding to the safety sub-condition that has been detected. When the next detection request is received, the safety detection condition corresponding to the detection request is obtained, and then several safety sub-conditions corresponding to the safety detection condition are obtained. If there is a safety sub-condition corresponding to the first sub-identifier or the second sub-identifier in the preset database, it is directly determined whether the safety sub-condition is met, without obtaining the working condition data corresponding to the safety sub-condition, thereby improving the detection efficiency.

[0057] For example, when executing step S210, there are three safety sub-conditions, namely "the speed of the EMU is lower than the first safety speed", "the temperature of the brake disc is lower than the first safety temperature", and "the brake disc is in a non-working state". If the safety sub-condition "the speed of the EMU is lower than the first safety speed" is met, step S211 is synchronously executed to create a first sub-identifier corresponding to the safety sub-condition in the preset database (if the first sub-identifier or the second sub-identifier of the safety sub-condition has been stored in the preset database before, it is updated). If the safety sub-condition "the temperature of the brake disc is lower than the first safety temperature" is not met, step S212 is synchronously executed to create a second sub-identifier corresponding to the safety sub-condition in the preset database (if the first sub-identifier or the second sub-identifier of the safety sub-condition has been stored in the preset database before, it is updated).

[0058] Specifically, when step S210 is executed next time, it is queried whether the safety sub-condition has a corresponding first sub-identifier or a second sub-identifier. If there is a corresponding first sub-identifier, the safety sub-condition is satisfied and there is no need to obtain the working condition data; if there is a corresponding second sub-identifier, the safety sub-condition is not satisfied and there is no need to obtain the working condition data, which greatly improves efficiency. In particular, when multiple detection requests are made, the multiple detection requests all include the same safety sub-condition, so there is no need to obtain the working condition data and judgment of the safety sub-condition multiple times; if there is no first sub-identifier and second sub-identifier, the working condition data of the safety sub-condition is obtained and judged.

[0059] Specifically, within the preset time or at the next braking, the first sub-identifier and the second sub-identifier in the preset database are cleared. Because the working condition data changes at the next braking, the original first sub-identifier and the second sub-identifier become invalid and can no longer be used to determine whether the corresponding safety sub-condition is met, and the working condition data needs to be re-acquired for determination. The preset time can be 24 hours.

[0060] The braking system includes a preset database and a cloud database. The preset database is stored locally, and the cloud database is stored in a cloud server. The preset database and the cloud database are heterogeneous databases. For example, the preset database is a relational database (RDBMS), and its data is stored in a table format to ensure data consistency and reliability, facilitate data structure pre-definition and perform complex queries, and improve detection efficiency. The cloud database is a NoSQL database, which contains data in a variety of different formats, such as text, pictures, videos, etc., which is convenient for data analysis and visualization.

[0061] In one embodiment, in combination Figure 4 After step S300, the detection method further includes:

[0062] S510: When data is updated in the preset database, the data table name where the source data involved in the data update is located and the corresponding synchronization strategy are retrieved.

[0063] The data perception engine operates in the preset database, and its mechanism relies on the built-in trigger function of the preset database. The trigger is responsible for monitoring the changes of data rows in the preset database, and recording the primary key and change type (update or delete) of the changed row in the update_records table and delete_records table respectively. The specific operation process is: the data collection perception engine of the preset database will regularly activate the data collector according to the preset time interval. The collector will scan the update_records table and the delete_records table to retrieve all the records in them. Once the scan is completed, the name of the data table where the source data is located and the type of change in the data table are extracted from these records, and the synchronization strategy is determined.

[0064] S520: Based on the retrieved data table name and synchronization strategy, evaluate whether the data update needs to be synchronized to the cloud database.

[0065] S530: If the source data needs to be synchronized to the cloud database after evaluation, determine the update mode of the source data. Once it is determined that the source data needs to be synchronized to the cloud database, the data collector determines the update mode of the source database based on the update_records table or the delete_records table.

[0066] Specifically, if the trigger records the primary key value of the source database corresponding to this update in the update_records table, the data collector will obtain the specific update mode of the source database by consulting the table, such as data insertion or data update. On the contrary, if the trigger records the primary key value of the source database corresponding to this update in the delete_records table, the update mode is marked as data deletion.

[0067] S540: Generate a transmission file according to the update mode and source data through the encryption mechanism of the preset database.

[0068] For example, when the key information such as the primary key of the updated data of the preset database is recorded in the update_records table, the database interface adapter is used to retrieve the corresponding synchronization table record through the table name and primary key information in the trigger record. Subsequently, the system will perform synchronization direction verification and synchronization record reordering operations on the synchronization table records to ensure that the records are arranged in the order of update time.

[0069] In one embodiment, the update_records table uses the ot field to record the update mode of the preset database. The system will integrate the value of the ot field into the synchronization table record, group the synchronization table records, and then pass these grouped records to the file security manager. The file security manager uses the national secret encryption algorithm to encrypt each group of synchronization table records, and writes the encrypted data into a separate transmission file. Each group of synchronization table records corresponds to a transmission file to prevent the generation of invalid files in the preset database and reduce resource consumption. After completing the above process, the data collector will remove the corresponding trigger record from the update_records table.

[0070] In another embodiment, when the delete_records table records the update mode of the preset database, the synchronization table records in the table will be extracted in batches. The synchronization table records will be passed to the file security manager, which also uses the national encryption algorithm to encrypt and write the encrypted data into a transmission file to prevent the generation of invalid files in the preset database and reduce resource consumption. After all processes are completed, the data collector will delete the corresponding synchronization table records from the delete_records table.

[0071] S550: The transmission file is transmitted to the cloud database and stored.

[0072] In an embodiment of the present application, the preset database is responsible for transmitting the generated transmission file to the sending directory of the source isolation device. At the same time, the write perception engine of the cloud database adopts a configurable timed polling mechanism to regularly scan the receiving area directory of the isolation device to retrieve and obtain the transmission file. Once the transmission file is successfully obtained, the cloud database will immediately pass it to the data writer through the event notification mechanism and trigger the corresponding data writing process.

[0073] Once the cloud database write executor receives the transfer file, it will immediately use the homology comparison algorithm and primary key conflict strategy library to quickly match the field type and value of the changed data. This process does not require the mapping relationship to be set in advance. When the data writer receives the event notification of the transfer file reception, it will first transfer the transfer file to the temporary directory to be written WRITE (this directory is a subdirectory under the workspace preset in the configuration file). Subsequently, the data writer will traverse all the transfer files under the WRITE directory and sort them in positive order according to the file name. After the sorting is completed, it uses the file security manager to parse the transfer file to obtain the synchronization table record. The core responsibility of the data writer is to perform deletion, update, and insertion operations on synchronization table records.

[0074] When executing a write task, the built-in monitoring module of the cloud database will track the execution process of the writer in real time, collect and summarize the data of each link by injecting embedded points. This monitoring mechanism can monitor the operation status of each stage in real time, and provide early warning and diagnostic information when anomalies are found, ensuring the accuracy and timeliness of data synchronization.

[0075] In one embodiment, step S520 specifically includes:

[0076] S521: Obtain a preset data table, where the preset data table stores the names of data tables that need to be synchronized to the cloud database.

[0077] The preset data table is set in the system initialization phase through the configuration module of the preset database. The configuration process can be completed through the user interface or by manually editing the configuration file. It specifically involves setting the workspace directory, specifying the database table to be synchronized, defining the primary key conflict handling strategy for each table, clarifying the database type, and whether to enable the synchronization deletion operation, and finally saving it as a synchronization configuration file. After the system is started and initialized, this configuration file will be loaded into the memory for subsequent use.

[0078] Specifically, when the data in the preset database changes, the data collector will access the preset data table in the memory to determine whether the updated preset database needs to synchronize data to the cloud database.

[0079] S522: Query the preset data table to determine whether it contains the data table name associated with the source data and the synchronization strategy corresponding to the source data. The synchronization strategy specifies the direction and method of data synchronization. When the preset database is updated, such as operating data, safety detection conditions, detection results, first sub-identifiers, and second sub-identifiers. Among them, each detection request, safety detection condition, detection result, and non-compliance with the safety detection result need to be synchronized and updated to the cloud database. For repeated safety sub-conditions and the corresponding first sub-identifiers and second sub-identifiers, if the data does not change and the data is short-lived, it will not be synchronized to the cloud database. Specifically, the first sub-identifier is "true", and the same safety sub-condition has multiple results that are all the first sub-identifier, so there is no need to synchronize.

[0080] S523: If the data table name and synchronization strategy of the source data are found in the preset data table, it is determined that the update of the source data needs to be synchronized to the cloud database. Specifically, if the source database table name is found to exist in the preset data table and the synchronization strategy associated with the data is successfully retrieved, it is determined that the updated content of the source database needs to be synchronized to the specified source database library. In the above method, data synchronization is performed only when the preset data table includes the data table name of the source database and the corresponding synchronization strategy, which can avoid processing data that does not need to be synchronized and improve the efficiency of the synchronization operation.

[0081] Specifically, for repeated security sub-conditions and the corresponding first sub-identifier and second sub-identifier, the synchronization strategy is that if the result of the security sub-condition changes from the first sub-identifier to the second sub-identifier, then synchronization is performed, otherwise no synchronization is performed. For example, if the first sub-identifier is "true", the same security sub-condition has the same result multiple times, which is the first sub-identifier, and there is no need to synchronize; if the result is different, for example, it changes from the first sub-identifier to the second sub-identifier, synchronization is required, and the synchronization time is recorded, so that it can be inferred from the synchronization time that the result between the two change times is the first sub-identifier.

[0082] In some embodiments, step S300 specifically includes:

[0083] S310: Acquire detection parameters of the detection task.

[0084] S320: Determine a detection method for the detection object according to the detection parameters. The detection methods include online monitoring, offline detection, laboratory testing, simulation testing, etc.

[0085] S330: Perform brake detection on the detection object according to the detection method. The brake detection may include multiple links such as drive control, data collection, data analysis, and fault diagnosis.

[0086] For example, the detection task is the brake cylinder pressure, the detection parameter is the time it takes for the pressure to drop from the first pressure to the second pressure, the detection method determines that the detection object is the brake cylinder, and the detection method selected is online testing. The brake detection is achieved by regulating the brake cylinder to drop from the first pressure to the second pressure, using a sensor to record the air pressure, and a clock to record the time.

[0087] Based on this, the detection terminal sends a detection request containing the detection parameter "brake cylinder pressure". The detection method can automatically determine whether the safety detection conditions are met, and automatically confirm the specific detection object and detection method when the safety detection conditions are met, and perform brake detection. That is, the user does not need to pay attention to the specific model of the EMU, braking system, braking components, component status, etc. The user sends the detection request item by item according to the detection standards, and the detection method automatically combines the specific model of the EMU, braking system, braking components, and component status to feedback the detection results.

[0088] Specifically, the preset database has a one-to-one mapping relationship between detection parameters, detection methods, and braking detection.

[0089] In this embodiment, judging whether the EMU is in a braking state, as well as the start and end braking times and braking time periods, are necessary steps in braking detection. Braking performance tests including braking distance test, braking time test, braking deceleration test, etc. all require obtaining the braking start and end times.

[0090] In one embodiment, the specific steps of step S330 are:

[0091] S331: Obtain the running speed of the EMU and the output signal of the driver.

[0092] S332: Determine whether the EMU starts braking based on the running speed and the output signal of the driver.

[0093] After the EMU starts braking, it continues to move forward on the track and maintains a certain driving speed, but its engine has stopped running and the corresponding driver output signal returns to zero, which is used as the basis for judging whether the EMU has entered the braking state.

[0094] Taking a specific scenario as an example, if the speed of the EMU drops below or equals to the first speed threshold, and the output signal of the driver remains 0, it can be determined that the EMU has started braking. On the contrary, if the speed exceeds the first speed threshold, or the output signal of the driver is not 0, it is determined that the EMU has not entered the braking state.

[0095] Specifically, step S332 includes:

[0096] S3321: Based on the driving speed, determine whether the EMU is in a low-speed driving state.

[0097] S3322: If the EMU is in a low-speed driving state, determine whether the braking system starts to work based on the status information of the electronic brake control unit and the pneumatic brake control unit.

[0098] In this way, when it is detected that the current driving speed of the EMU falls into the low-speed range, it is first confirmed that the EMU is in a low-speed driving state. Subsequently, it is further checked whether the output signal of the driver at the current moment is 0. If the output signal of the driver is 0, it is determined that the EMU has started braking at the current moment; conversely, if the output signal of the driver is not 0, it is determined that the EMU has not braked. If the driving speed is not in the low-speed range, it is confirmed that the EMU has ended the low-speed driving state, and based on this, it is determined that the EMU has not braked. On the basis of confirming that the EMU is in a low-speed driving state based on the driving speed, it is not directly determined that it has started braking, but further judged based on the output signal of the driver. The dual judgment mechanism combining the driving speed and the driver output signal can reduce misjudgment and improve the accuracy of braking state identification.

[0099] S333: After the EMU starts braking, it is determined whether the EMU stops braking based on the running speed and the output signal of the driver.

[0100] After the EMU starts braking, it is first determined whether the EMU has finished braking based on the running speed of the EMU and the output signal of the driver.

[0101] In a possible implementation, determining whether the EMU has finished braking according to the moving speed and the output signal of the driver includes:

[0102] S3331: After detecting that the EMU starts braking, it is determined that the braking is ended when it is detected that the EMU ends the low-speed driving state and / or the output signal of the driver is not zero.

[0103] S3332: The moment when the EMU braking is detected to be finished is determined as the second moment.

[0104] When the start of the EMU braking is detected, if the low-speed driving state is determined to have ended for the first time based on the driving speed, or the braking end is determined for the first time based on the output signal of the driver (i.e., the signal becomes non-zero), it is confirmed that the EMU has completed the braking process, and this moment is recorded as the second moment. This method can accurately lock the end time of the braking state at the moment when the EMU leaves the low-speed driving state or the output signal of the driver returns to non-zero for the first time, so as to accurately record the total length of time the EMU is in the braking state, thereby enhancing the credibility of the braking state identification.

[0105] S334: Determine that the EMU is in a braking state between a first moment and a second moment, the first moment being the moment when the EMU is detected to start braking, and the second moment being the moment when the EMU is detected to stop braking.

[0106] In the implementation case of this application, the driving speed and the output signal of the driver are combined to determine the start and end of braking of the EMU during travel. At the same time, the specific time period from the start to the end of each braking is recorded and included in the braking status record. This detection method can accurately track the duration of each braking, improve the accuracy of the braking duration record, and provide solid data support for subsequent braking performance analysis.

[0107] Considering that the vehicle often travels at a low speed when crossing a bridge or tunnel or going uphill, it is possible that the output signal of the driver is zero but the vehicle travels at a low speed on such a road section. In order to avoid identifying this situation as a braking state and further improve the reliability of the identification of the braking state, the detection method includes the following steps:

[0108] S335: Determine whether the EMU passes through the bridge or tunnel based on the locator or infrared sensor.

[0109] S336: Determine whether the EMU is going uphill based on the barometer.

[0110] In an example of realizing the state judgment of the EMU, the pressure altitude data is used to infer the height change of the section passed by the EMU in a specific time period (i.e., the first time period). First, the height change of the section where the EMU is located in the first time period is calculated based on the collected pressure altitude data. This change reflects the displacement of the EMU in the vertical direction. Then, the vertical speed of the EMU is calculated using the height change. The vertical speed indicates the speed of the EMU's movement in the vertical direction, which is an important basis for judging whether it is in an uphill or downhill section. Then, the slope information of the section where the EMU is located in the first time period is further determined by combining the moving speed of the EMU (i.e., its speed in the horizontal direction) and the vertical speed. The slope information is a comprehensive indicator that reflects the comprehensive changes of the section in the vertical and horizontal directions. Finally, it is judged whether the EMU is in an uphill section based on the slope information. If the slope information indicates that the vertical displacement of the EMU is upward, that is, the vertical velocity is positive and the moving speed is large enough to maintain driving on the uphill section, then the EMU is determined to be on the uphill section. Based on this, the pressure altitude data is used to accurately judge the height change of the EMU during driving, thereby providing an important basis for its status judgment and driving safety.

[0111] The first time period is the time interval between the current moment and the previous moment. During this time period, the first-order difference calculation of the pressure altitude data is performed to determine the altitude change of the EMU from the previous moment to the current moment on the section where it is located. This altitude change, divided by the time interval between the two moments (i.e., the first time period), can give the vertical speed of the EMU at the current moment. This vertical speed is a key indicator that intuitively reflects the dynamic situation of the EMU in the vertical direction. For example, if the altitude change is significant when comparing two consecutive moments, and the calculated vertical speed is also faster, then this often means that the EMU may be traveling on an uphill section.

[0112] After obtaining the vertical speed at the current moment, it is further compared with the moving speed of the EMU at the same moment, and the slope information is determined by calculating the ratio between the two. During the detection process, this slope information is compared with two preset thresholds - the first slope information threshold and the second slope information threshold. If the slope information is greater than or equal to the first slope information threshold, it is determined that the EMU is in an uphill section; if the slope information is less than or equal to the second slope information threshold, it is determined to be a downhill section; and when the slope information is between these two thresholds, it is determined that the EMU is traveling on a flat slope section. It should be noted that the first slope information threshold is less than the second slope information threshold.

[0113] It can be understood that the slope information refers to the degree of inclination of the slope surface, which can be expressed as the ratio of the vertical height change to the horizontal distance change. In actual calculations, the vertical speed approximately represents the rate of change of the vertical height, and the moving speed of the EMU at the current moment can be approximately regarded as the rate of change of the horizontal distance. Therefore, the ratio of the vertical speed to the moving speed is equivalent to calculating the ratio of the vertical height change to the horizontal distance change, which can be used as the slope information.

[0114] Among them, the slope information refers to the degree of inclination of the slope surface, which can essentially be regarded as the ratio between the vertical height change and the horizontal distance change. Specifically, the vertical speed of the EMU can be regarded as an approximate value of the vertical height change rate, which reflects the displacement change in the vertical direction per unit time; and the moving speed of the EMU at the current moment can be approximately regarded as a measure of the horizontal distance change rate, which reveals the speed of the EMU in the horizontal direction. By calculating the ratio of these two speed values, it is actually estimating the proportional relationship between the vertical height change and the horizontal distance change, and this ratio is used as a representation of the slope information. This method not only simplifies the calculation process, but also guarantees the accuracy and reliability of the slope information calculation to a certain extent.

[0115] S337: When it is detected that the EMU is not on an uphill section or crossing a bridge or tunnel, determine whether the user of the EMU is in a braking state based on the driving speed and the output signal of the driver.

[0116] In the embodiment of the present application, when it is detected that the EMU is not in an uphill section or crossing a bridge or tunnel, it is identified whether the EMU is in a braking state based on the driving speed and the output signal of the driver, thereby avoiding misidentification of uphill sections or bridge and tunnel sections as braking states, thereby further improving the reliability of braking state identification.

[0117] Embodiment 2

[0118] Combination Figure 5 This embodiment also provides a terminal device 1 including: at least one processor 12, a memory 11, and a computer program 13 stored in the memory 11 and executable on at least one processor 12. When the processor 12 executes the computer program 13, the steps in any one of the detection method embodiments in Embodiment 1 are implemented.

[0119] The terminal device 1 may be a computing device such as a desktop computer, a notebook, a PDA, or a cloud server. The terminal device 1 may include, but is not limited to, a processor 12 and a memory 11. Those skilled in the art will appreciate that the accompanying drawings are merely examples of the terminal device 1 and do not constitute a limitation on the terminal device 1. The terminal device 1 may include more or fewer components than shown in the drawings, or may combine certain components, or different components, and may also include, for example, input and output devices, network access devices, etc.

[0120] The processor 12 may be a central processing unit (CPU), or other general-purpose processors 12, digital signal processors 12 (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor 12 may be a microprocessor 12 or any conventional processor 12, etc.

[0121] In some embodiments, the memory 11 may be an internal storage unit of the terminal device 1, such as a hard disk or memory of the terminal device 1. In other embodiments, the memory 11 may also be an external storage device of the terminal device 1, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the terminal device 1. Further, the memory 11 may also include both an internal storage unit and an external storage device of the terminal device 1. The memory 11 is used to store an operating system, an application program, a boot loader, data, and other programs, such as the program code of the computer program 13. The memory 11 may also be used to temporarily store data that has been output or is to be output.

[0122] Embodiment 3

[0123] The embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps of any one of the detection methods in the first embodiment can be implemented.

[0124] An embodiment of the present application provides a computer program product. When the computer program product runs on a terminal device, the terminal device can implement the steps in the above-mentioned method embodiments when executing the computer program product.

[0125] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may at least include: any entity or device that can carry the computer program code to the device / terminal device, a recording medium, a computer memory, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), an electric carrier signal, a telecommunication signal, and a software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disk. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electric carrier signals and telecommunication signals.

[0126] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0127] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0128] In the embodiments provided in the present application, it should be understood that the disclosed devices / terminal equipment and methods can be implemented in other ways. For example, the device / terminal equipment embodiments described above are only schematic, for example, the division of modules or units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0129] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0130] In the above description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0131] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or their collections. It should also be understood that the term "and / or" used in the present specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes these combinations.

[0132] As used in the specification and appended claims of this application, the term "if" can be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "uponce it is determined" or "in response to determining" or "uponce [described condition or event] is detected" or "in response to detecting [described condition or event]", depending on the context.

[0133] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

[0134] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for detecting a brake system of an EMU, characterized in that: The method comprises: Receiving a detection request for a brake system, and obtaining a safety detection condition corresponding to the detection request; Acquiring operating condition data corresponding to the safety detection condition; If the working condition data meets the safety detection condition, the detection task corresponding to the detection request is executed, the detection result is obtained, and sent to the detection terminal; If the operating condition data does not meet the safety detection condition, the detection task corresponding to the detection request is not executed, and a safety detection result that does not meet the requirements is sent to the detection terminal.

2. The method for detecting the brake system of a motor vehicle according to claim 1, characterized in that: The safety detection condition includes a plurality of safety sub-conditions; the operating condition data includes data corresponding to each of the safety sub-conditions; After obtaining the operating condition data corresponding to the safety detection condition, the method further includes: Determining whether each of the safety sub-conditions is satisfied according to the data corresponding to each of the safety sub-conditions; If there is a safety sub-condition that is not met, it is determined that the operating condition data does not meet the safety detection condition; If all safety sub-conditions are met, it is determined that the operating condition data meets the safety detection condition.

3. The method for detecting the brake system of a motor vehicle according to claim 2, characterized in that: The method further comprises: If the security sub-condition is met, creating or updating a first sub-identifier in a preset database; If the security sub-condition is not satisfied, a second sub-identifier is created or updated in a preset database.

4. The method for detecting the brake system of a motor vehicle according to claim 3, characterized in that: The EMU braking system includes a preset database and a cloud database. After the step of executing the detection task corresponding to the detection request, the detection method further includes: When data in the preset database is updated, the data table name and the corresponding synchronization strategy of the source data involved in the data update are retrieved; Based on the retrieved data table name and the synchronization strategy, evaluating whether the data update needs to be synchronized to the cloud database; If synchronization to the cloud database is required after evaluation, then determining an update mode for the source data; Generate a transmission file through the encryption mechanism of the preset database according to the update mode and the source data; The transmission file is transmitted to the cloud database and stored.

5. The method for detecting the brake system of a motor vehicle according to claim 4, characterized in that: The step of evaluating whether the data update needs to be synchronized to the cloud database based on the retrieved data table name and the synchronization strategy specifically includes: Obtain a preset data table, wherein the preset data table stores the data table name that needs to be synchronized to the cloud database; Querying the preset data table to determine whether it contains the data table name associated with the source data and the synchronization strategy corresponding to the source data; If the data table name and the synchronization strategy corresponding to the source data are found in the preset data table, it is determined that the update of the source data needs to be synchronized to the cloud database.

6. The method for detecting the brake system of a motor vehicle according to claim 1, characterized in that: The specific steps of executing the detection task corresponding to the detection request include: Obtaining detection parameters of the detection task; Determining a detection method for the detection object according to the detection parameters; The braking detection of the detection object is performed according to the detection method.

7. The method for detecting the brake system of a motor vehicle according to claim 6, characterized in that: The specific steps of performing the braking detection of the detection object according to the detection method include: Obtain the running speed of the EMU and the output signal of the driver; Determining whether the EMU starts braking according to the travel speed and the output signal of the driver; After the EMU starts braking, judging whether the EMU stops braking according to the travel speed; It is determined that the EMU is in a braking state between a first moment and a second moment, the first moment being the moment when the EMU is detected to start braking, and the second moment being the moment when the EMU is detected to stop braking.

8. The method for detecting the brake system of a motor vehicle according to claim 7, characterized in that: The step of judging whether the EMU starts braking according to the travel speed and the output signal of the driver specifically comprises: Based on the driving speed, determining whether the EMU is in a low-speed driving state; If the EMU is in a low-speed driving state, it is determined whether the brake system starts to work in combination with the state information of the electronic brake control unit and the pneumatic brake control unit.

9. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 8 is implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 8 is implemented.

Images