Testing Method and System for Passenger Car Parking Brake System Based on Data Closed-Loop Technology

Abstract

The present invention relates to the technical field of intelligent connected vehicle testing, and discloses a testing method and system for a passenger vehicle parking brake system based on data closed-loop technology, including a data processing subsystem, a fault injection subsystem, a subsystem under test, a cockpit simulation subsystem, and a bench subsystem; the data processing subsystem is used for importing and processing real vehicle target data; the fault injection subsystem is used for simulating and injecting vehicle hardware faults and vehicle communication faults; the subsystem under test includes the EPB controller system of the vehicle; the cockpit simulation subsystem is used for providing a simulated driving environment for testers; the bench subsystem includes a scenario simulation module, a vehicle simulation module, a data acquisition module, and a test bench; wherein, the test bench is used for interacting with the subsystem under test. The present invention can perform comprehensive data closed-loop testing on the functions and performance of the vehicle parking brake system driven by various test data, with relatively high testing efficiency and good testing reliability.

Description

Technical Field

[0001] The present invention relates to the technical field of intelligent networked vehicle testing, and in particular to a method and system for testing a parking brake system of a passenger vehicle based on a data closed-loop technology. Background Art

[0002] China has promulgated a number of national standards related to braking systems, such as GB / T 34590 "Functional Safety of Vehicle Roads" and GB / T 39901-2021 "Performance Requirements and Test Methods for Automatic Emergency Braking Systems (AEBS) of Passenger Vehicles", which aim to guide and standardize the vehicle and system development and testing processes. The latest national braking standard GB 21670 "Technical Requirements and Test Methods for Passenger Vehicle Braking Systems" provides detailed testing guidelines for the functional safety of parking systems. Hardware-in-the-loop (HIL) testing plays a core role in the functional safety verification of parking brake systems. This technology can simulate extreme conditions and comprehensively evaluate the performance of electronic parking brake systems to ensure that they are stable, reliable and safe. It also helps to identify and optimize design defects and enhance system efficiency and robustness.

[0003] Data closed-loop technology is particularly important in the context of automotive informatization and intelligence. It promotes the iteration and upgrade of automotive systems by continuously monitoring, analyzing and solving data problems. If the automotive electronic parking brake system lacks a data closed-loop, it may face real-time monitoring failure, limited adaptive capabilities and fault diagnosis problems. Especially in complex environments, the system safety and reliability will be greatly reduced. Therefore, the use of data closed-loop technology for full-chain testing is crucial to improving the quality of the parking system and the safety of actual vehicle applications.

[0004] In view of the characteristics of new energy intelligent connected vehicle data and its impact on the quality of the parking system, it is urgent to build a test system based on data closed-loop technology to cope with the challenges of complex operating scenarios and high-frequency data updates. However, the industry still faces technical obstacles such as vague data management standards, insufficient integration of closed-loop technology and test performance, and lack of cross-domain integration of HIL testing. These problems are directly related to the functional performance and quality level of passenger cars. At present, various OEMs and R&D institutions are working hard to solve the technical problem of disconnection between real vehicle test data and software simulation information, in order to comprehensively improve vehicle functional safety and user experience. Summary of the invention

[0005] The present invention aims to provide a passenger car parking brake system testing method and system based on data closed-loop technology, which can perform comprehensive data closed-loop testing on the functions and performance of the vehicle parking brake system driven by various test data, with high test efficiency and good test reliability.

[0006] To achieve the above objectives, the present invention provides the following basic solutions.

[0007] Solution 1

[0008] Passenger car parking brake system test system based on data closed-loop technology, including data processing subsystem, fault injection subsystem, target subsystem, cockpit simulation subsystem and test bench subsystem;

[0009] The data processing subsystem is used to import and process real vehicle target data; the processing includes systematically identifying the real vehicle target data and marking the data to form a test signal set;

[0010] The fault injection subsystem is used to simulate the injection of vehicle hardware faults and vehicle communication faults; the target subsystem under test includes the vehicle's EPB controller system; the cockpit simulation subsystem is used to provide a simulated driving environment for testers;

[0011] The test bench subsystem includes a scenario simulation module, a vehicle simulation module, a data acquisition module and a test bench; the scenario simulation module is used to set environmental operating condition information and transmit the environmental operating condition information to the test bench so that the EPB controller system can perceive different environmental conditions; the vehicle simulation module is used to build a vehicle dynamics model and a test environment model; the data acquisition module is used to monitor and record test data; and the test bench is used to interact with the target subsystem under test.

[0012] Solution 2

[0013] The method for testing a parking brake system of a passenger car based on a data closed loop technology is performed by using a parking brake system testing system of a passenger car based on a data closed loop technology as described in Scheme 1; the method comprises the following steps:

[0014] Step 1, configuring a test system; the test system is a passenger car parking brake system test system based on data closed-loop technology;

[0015] Step 2, verify whether there is fault information in the test system. If there is no fault information in the test system, execute the next step; if there is fault information in the test system, generate a warning message and send it to the tester, and end the process;

[0016] Step 3, set the test case, and assign and configure the driving operation signal, gear signal, test scenario characteristic parameters and the parking brake system's own characterization signal based on the test case, and verify the validity of the switch state of the EPB controller system. If the verification fails, return to step 2; if the verification passes, execute the next step;

[0017] Step 4, start the test, and during the test, the data acquisition module monitors and records the test data until the speed of the vehicle under test is reduced to zero or the maximum test time of this test case is reached; when the test system reports no fault information, proceed to the next step;

[0018] Step 5: End the test.

[0019] The working principle and advantages of the present invention are:

[0020] First, the test system set up in this solution includes a scenario simulation module, which can integrate scenario simulation into the parking brake system test to overcome the limitations of traditional hardware-in-the-loop (HIL) testing. Compared with traditional hardware-in-the-loop testing, although traditional HIL testing can effectively verify the response of the vehicle's electronic control unit (ECU), it is often difficult to fully cover the key parameters of external scene characteristics in the simulation of the parking system's operating conditions, such as terrain, slope, weather changes, etc. This solution can fill the gap in the lack of key parameters of external scene characteristics in the parking system's operating conditions, and effectively alleviate the difficulty of executing extreme condition test cases in the current real vehicle road testing due to random changes in the external environment. It can significantly improve test efficiency, reduce losses to actual vehicles, and reduce testing costs. At the same time, it also avoids dependence on the external environment and ensures the repeatability and consistency of the test.

[0021] Second, the test system set up in this solution includes a fault injection subsystem, which has automated fault injection technology and can effectively replicate the extreme test scenarios encountered during the actual vehicle testing phase, making it easier for testers to fully discover the defects of each function under test during the development phase. In addition, the types of fault injection cover vehicle hardware failures and vehicle communication failures, and can observe the real response mechanism of the vehicle system under typical extreme test conditions under laboratory conditions, and can meet the strong standard-related safety function testing requirements related to the chassis domain associated with the parking brake system. Compared with pure hardware-in-the-loop testing solutions, this solution has the ability to automate fault injection. Through software control, the timing and duration of fault injection can be accurately set (accurate to milliseconds), which eliminates the reliance on manual judgment and operation, overcomes the inconsistencies and omissions that may be caused by previous testers' experience-based operations, and can effectively improve the test coverage conditions.

[0022] Third, this solution uses a comprehensive data closed-loop technology to provide a strong basic test platform for passenger car parking system function assurance. For the actual vehicle field test of the parking system, this solution can directly import the operating data of the failed or failed conditions, accurately identify the key factors or signals that cause the test failure, and conduct summary analysis; then the bench subsystem performs hardware-in-the-loop testing based on the signal pool, which can achieve efficient use of actual vehicle data, thereby reproducing real-world test scenarios in a laboratory environment. In this way, not only the utilization rate of data is improved, but also the experience accumulated from simulation testing can be fed back to actual vehicle testing, forming a virtuous circle and continuously improving the accuracy and efficiency of testing. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 It is a first schematic diagram of the system structure of a first embodiment of a passenger car parking brake system testing method and system based on a data closed-loop technology of the present invention;

[0024] Figure 2 A second schematic diagram of the system structure of a first embodiment of a passenger car parking brake system testing method and system based on a data closed-loop technology of the present invention;

[0025] Figure 3 The present invention is a flow chart of a method for testing a parking brake system of a passenger vehicle based on a data closed-loop technology and a method of system embodiment 1. DETAILED DESCRIPTION

[0026] The following is a further detailed description through specific implementation methods.

[0027] Embodiment 1

[0028] The embodiment is basically as shown in the attached Figure 1 , Figure 2 As shown: A passenger car parking brake system test system based on data closed-loop technology includes a data processing subsystem, a fault injection subsystem, a test target subsystem, a cockpit simulation subsystem and a test bench subsystem.

[0029] The data processing subsystem is used to import and process real vehicle target data; the processing includes systematically identifying the real vehicle target data and performing data marking on it to form a test signal set.

[0030] The real vehicle target data includes real vehicle road test result data, tester experience data and preset log information in the vehicle development process. The format of the real vehicle target data can be data in different formats such as ASCII, BLF, PCAP, etc. The test signal set includes function classification signal, fault injection signal and pass indication signal.

[0031] Specifically, when the data processing subsystem systematically identifies the real vehicle target data, it first decodes the real vehicle target data and converts it into specific physical quantities or state information for identification by reading the DBC file (i.e., the vehicle network data description file, which defines the signal structure, message ID, signal range, and physical unit of each node in the vehicle network (such as the CAN bus)). Through the analysis and processing of the real vehicle target data, the test pass flag signal contained in the real vehicle data is used to dig out the characterization signals that fail in specific failed test cases, and forward and reverse scenarios are selected to cover the discovered problems. Specifically, targeted solutions are provided through functional testing and fault injection testing scenarios to clarify the needs of the next test. The data processing subsystem can promptly discover potential problems and provide targeted solutions to help clarify the required scenarios for the next test.

[0032] The data processing subsystem is provided with a calling unit; the calling unit is used to customize the signal composition in the test signal set so as to set the test scenario more accurately.

[0033] The fault injection subsystem is used to simulate and inject vehicle hardware faults and vehicle communication faults.

[0034] The fault injection subsystem realizes the analogy of the EPB controller system through hard-wire connection and BOB module; during the fault injection process, the BOB module captures and redirects the Ethernet frame from the ECU to monitor the real-time Ethernet data flow, and injects the vehicle communication fault on this basis; the circuit connection state is changed by hard-wire connection, and the vehicle hardware fault is injected on this basis. The fault injection subsystem controls the modification time of the data flow or circuit connection state to control the fault injection time and duration.

[0035] Through the fault injection subsystem, reproducible hardware fault injection operations can be provided, making the safety assessment of this test system more accurate and reliable. In addition, it helps to fully verify the vehicle's fault diagnosis and fault-tolerance mechanisms, ensuring that the vehicle's parking brake system can correctly identify and handle faults when they occur. In addition, compared to existing fault injection boards, the fault injection subsystem provided in this embodiment has higher flexibility and stronger compatibility, can achieve more sophisticated fault injection, and supports automated fault injection, which can overcome and solve the technical deficiencies of testers operating based on experience, thereby improving test coverage conditions.

[0036] The target subsystem under test includes the EPB controller system of the vehicle. The cockpit simulation subsystem is used to provide a simulated driving environment for the tester.

[0037] In this embodiment, the cockpit simulation subsystem includes a simulated cockpit corresponding to the cockpit of the vehicle under test, which is provided with functional components such as dashboard display, acceleration and braking operation signals, steering wheel force feedback, etc., so that the tester can simulate the real driving scene in the experimental environment. A communication interface and an input and output interface are also provided in the simulated cockpit; the communication interface can be used to interact with the vehicle controller to simulate the signal and response under real driving conditions. The input and output interface includes an interface for simulating sensor input (such as speed, acceleration, angle, etc.) and actuator output (such as lighting, sound system) to ensure seamless connection between the simulated environment and the real vehicle. Preferably, sensors and data acquisition equipment are also integrated in the simulated cockpit to collect the brake pedal and accelerator pedal signals operated by the driver. The specific implementation method is to realize the acquisition of the driver's acceleration depth through one switch signal and one analog signal (sensor); two switch signals are used to realize the acquisition of the driver's braking state, and then monitor the vehicle performance and condition in real time, provide accurate data support for the automobile development process, and realize the test closed loop.

[0038] The test bench subsystem includes a scene simulation module, a vehicle simulation module, a data acquisition module and a test bench.

[0039] The scenario simulation module is used to set environmental condition information and transmit the environmental condition information to the test bench so that the EPB controller system can perceive different environmental conditions.

[0040] When transmitting environmental working condition information, the scenario simulation module includes the following steps: using the UDP / TCP protocol, based on the set environmental working condition information, a signal communication matrix is ​​formulated; based on the signal communication matrix, the environmental working condition information is packaged and sent to the test bench through the CAN protocol.

[0041] In practical applications, existing scenario simulation software such as modlebase can be used to generate environmental condition information, and then based on this scenario simulation module, a communication channel can be built for the scenario simulation software and the test bench to complete the transmission of environmental condition information. Compared with existing test systems, existing systems often do not have and find it difficult to integrate scenario simulation in in-the-loop testing. The reasons are as follows: it is difficult to integrate existing scenario simulation software with hardware benches. If a dedicated data conversion system is used for integration, it will lead to a significant increase in testing costs. In this solution, a simple module is used to improve the communication and transmission method of environmental condition information, which can effectively realize the linkage between scenario simulation software and test benches, and the testing cost is low.

[0042] The vehicle simulation module is used to build a vehicle dynamics model and a test environment model. The vehicle dynamics model is a vehicle dynamics model without the corresponding controller model of the EPB controller system, so as to ensure that the tested EPB controller system can work normally.

[0043] The data acquisition module is used to monitor and record test data. The data acquisition module is a multi-channel data acquisition module, which helps to ensure the stability of data acquisition during the test process.

[0044] The test bench is used to interact with the target subsystem under test. In this embodiment, the test bench adopts a conventional HIL cabinet, and on this basis, different types of controller interfaces (specifically including hard-line input / output, CAN communication, PWM interface, resistor interface, etc.) are provided in the cabinet to be compatible with different types of parking system controllers, ensuring the versatility and flexibility of the test.

[0045] In the test of the EPB controller system, the test is started after the characteristic signals are extracted from the test signal set and combined in order.

[0046] like Figure 3 As shown, this embodiment also provides a passenger car parking brake system test method based on data closed loop technology, which uses the passenger car parking brake system test system based on data closed loop technology as mentioned above to perform the test; the test comprises the following steps:

[0047] Step 1, configuring a test system; the test system is a passenger car parking brake system test system based on data closed-loop technology.

[0048] Step 2, check whether there is fault information in the test system. If there is no fault information in the test system, the test system is globally configured based on ECUtest to facilitate setting of test cases and execute the next step; if there is fault information in the test system, a warning message is generated and sent to the tester, and the process is ended (that is, this test is ended).

[0049] Step 3, set the test case, and based on the test case, assign and configure the driving operation signal, gear signal, test scenario characteristic parameters and the parking brake system's own characterization signal, and verify the validity of the switch state of the EPB controller system. If the verification fails, return to step 2; if the verification passes, execute the next step.

[0050] Specifically, during validity verification, if the test scenario feature parameters and vehicle data are incorrect, the configuration object is invalid and the verification fails.

[0051] Incorrect means that during the verification process, the data monitored by the system does not match expectations or violates the preset safety boundary. For example, the vehicle sensor reports the wrong speed, or the test scene feature parameters exceed the preset range, which are all considered incorrect data.

[0052] If the test scenario characteristic parameters change in the predetermined manner of the test case, the verification passes.

[0053] Step 4, start the test, and during the test, the data acquisition module monitors and records the test data until the speed of the vehicle under test slows down to zero or reaches the maximum test time of this test case; when the test system reports no fault information (such as a fault Flag signal), execute the next step.

[0054] The test data includes characteristic parameters of the parking brake system (corresponding to the EPB controller system) under test, including system fault flag, brake switch status, requested braking force, current size, etc.; simulated vehicle motion state, and test environment characteristic parameters.

[0055] Step 5, end the test.

[0056] In this step, the speed of the vehicle under test is reset to zero, the data recording of the test process is terminated, and the data acquisition module automatically saves the recorded data under this test case to a specific folder to facilitate subsequent data management by relevant personnel and provide a basis for data closed-loop testing.

[0057] The present embodiment provides a passenger car parking brake system testing method and system based on data closed-loop technology, which can perform comprehensive data closed-loop testing on the functions and performance of the vehicle parking brake system driven by various test data. It has high test efficiency, good test reliability, and strong versatility. It can be used to complete major functional safety testing activities related to passenger car parking brake systems, such as functional safety test strategy formulation, test environment development and debugging, test case development, test execution, and test report preparation.

[0058] Embodiment 2

[0059] A passenger car parking brake system test method based on data closed loop technology is based on the first embodiment, and the difference is that the passenger car parking brake system test system based on data closed loop technology as described in the first embodiment is used to perform a functional test; the method comprises the following steps:

[0060] Step 1, reset the test system. According to the edited test cases, the test system is globally configured based on ECUtest to put the entire test system in place, and the working condition information to be tested, such as the slope value, the vehicle head direction and other environmental parameters, is sent to the EPB controller system under test through bus communication as a 10ms periodic event through the scenario simulation software modlebase, in coordination with the scenario simulation module, so that it can sense that it is working in a slope condition greater than 8% (as specified in the national standard).

[0061] Step 2: To facilitate the query of test cases, the characteristic parameters of the parking brake system must be determined immediately after the environmental condition information is stabilized.

[0062] Taking the CDP dynamic braking condition as an example, the absolute speed of the vehicle under test is first increased to 60km / h by the driver operating the accelerator pedal, and in the following test project configuration, it is selected whether the driver participates in the EPB switch misoperation (i.e., the fault injection subsystem simulates the fault injection), and the duration of pressing the panel PAD switch is set to 30 sampling cycles, i.e., 0.6s (the system judgment threshold is 500ms). The PAD switch refers to the control switch that activates the parking brake system (EPB).

[0063] The "sampling period" refers to the time interval for the test system to record data, and the "system judgment threshold is 500ms" means that the system will regard operations lasting more than 500 milliseconds as valid EPB trigger events. This setting is used to distinguish between erroneous operations and normal operations, ensuring that only triggers that are long enough can be regarded as EPB activation instructions, avoiding unnecessary braking actions caused by short touches.

[0064] Step 3: The tester operates the system for normal operation and clicks the data save button after the vehicle under test exits the stable state due to dynamic braking. At the same time, the tester observes whether the tested function meets the preset standards for the control strategy design of the parking system input end under conditions of human misoperation and key signal mutations (bus fault injection and hardware fault injection).

[0065] The present embodiment provides a passenger car parking brake system test method and system based on data closed-loop technology. Compared with the first embodiment, it can further prospectively consider the brake standard (GB 21670) to be released soon, integrate and redevelop the domestic scene simulation software modelbase and hardware-in-the-loop technology; and assist in transmitting environmental working condition information through the scene simulation module, solve the integration problem of scene simulation software and hardware-in-the-loop test bench, and achieve a significant reduction in project costs. In addition, compared with traditional hardware-in-the-loop testing, this solution can fill the gap of the lack of key parameters of external scene characteristics in the operating conditions of the parking system, effectively alleviate the difficulty of executing extreme working condition use cases due to the random changes in the external environment in the current real vehicle road test, so that the existing typical solutions are concentrated from objective conditions such as terrain, slope and weather to system hardware-in-the-loop laboratory testing methods, greatly improving the testing efficiency of passenger car parking system functions.

[0066] Embodiment 3

[0067] A passenger car parking brake system test method based on data closed loop technology is based on the first embodiment, and the difference is that the passenger car parking brake system test system based on data closed loop technology as described in the first embodiment is used to perform environmental reconstruction test; the method comprises the following steps:

[0068] Step 1: The data processing subsystem imports and processes the real vehicle target data. The processing includes systematically identifying the real vehicle target data and marking the data to form a test signal set. Before processing, the real vehicle target data is also cleaned to ensure that the data is accurate and valid.

[0069] Step 2: Import the test signal set and use data analysis tools to analyze the test signal set, locate problems, and explore abnormal situations. Based on the data analysis results, establish the corresponding test target signal set for the next test case development.

[0070] Step 3: Orderly combine the characteristic signals in the signal pool formed after the test signal set data is imported.

[0071] Taking the high-speed EPB failure condition as an example, the tester selected the key inducing signals of the failure condition for environmental reconstruction, and selected software induction (CAN communication failure) or hardware induction (hardware open circuit, short circuit failure) in the subsequent test project configuration, that is, the fault injection subsystem selected vehicle hardware failure or vehicle communication failure to be injected, and set the fault duration to be greater than the sampling period of the fault tolerance time interval (FTTI) of 3s to verify the safety handling mechanism of the parking brake system.

[0072] Step 4: During the test, the data acquisition module monitors and records the test data. After the test is completed, the feedback data is collected and organized, and it is iterated based on the data feedback and improvement results to guide the actual vehicle test, thereby achieving a data closed loop.

[0073] The present embodiment provides a passenger car parking brake system testing method and system based on data closed-loop technology. Compared with the first embodiment, the present embodiment further adopts data closed-loop technology, and can timely call key case data in actual vehicle testing, reproduce the functional safety integration test requirements of the parking brake control system in the HiL test bench environment, and realize the closed-loop operation and safety status monitoring functions of the parking brake control system, which has stronger functionality and higher test authenticity.

[0074] The above is only an embodiment of the present invention. The common sense such as the known specific structure and characteristics in the scheme is not described in detail here. The ordinary technicians in the relevant field are aware of all the common technical knowledge in the technical field of the invention before the application date or priority date, can obtain all the existing technologies in the field, and have the ability to apply the conventional experimental means before that date. The ordinary technicians in the relevant field can improve and implement the scheme in combination with their own abilities under the enlightenment given by this application. Some typical known structures or known methods should not become obstacles for the ordinary technicians in the relevant field to implement this application. It should be pointed out that for the technicians in this field, without departing from the structure of the present invention, several deformations and improvements can be made, which should also be regarded as the protection scope of the present invention, and these will not affect the effect of the implementation of the present invention and the practicality of the patent.

Claims

1. The passenger car parking brake system test system based on data closed-loop technology is characterized by: It includes data processing subsystem, fault injection subsystem, target subsystem, cockpit simulation subsystem and test bench subsystem; The data processing subsystem is used to import and process real vehicle target data; the processing of real vehicle target data includes systematically identifying the real vehicle target data and marking the data to form a test signal set; The fault injection subsystem is used to simulate the injection of vehicle hardware faults and vehicle communication faults; the target subsystem under test includes the vehicle's EPB controller system; the cockpit simulation subsystem is used to provide a simulated driving environment for testers; The test bench subsystem includes a scenario simulation module, a vehicle simulation module, a data acquisition module and a test bench; the scenario simulation module is used to set environmental working condition information and transmit the environmental working condition information to the test bench so that the EPB controller system can perceive different environmental working conditions; the vehicle simulation module is used to build a vehicle dynamics model and a test environment model; the data acquisition module is used to monitor and record test data; the test bench is used to interact with the target subsystem under test; The real vehicle target data includes real vehicle road test result data, tester experience data and preset log information in the vehicle development process; when the data processing subsystem systematically identifies the real vehicle target data, it first decodes the real vehicle target data and converts it into physical quantity or state information by reading the DBC vehicle network data description file based on the real vehicle target data for identification; When transmitting the environmental working condition information, the scenario simulation module includes the following steps: using the UDP / TCP protocol, based on the set environmental working condition information, formulating a signal communication matrix; Based on the signal communication matrix, the environmental condition information is packaged and sent to the test bench via the CAN protocol.

2. The passenger car parking brake system test system based on data closed loop technology according to claim 1, characterized in that: The data processing subsystem is provided with a calling unit; the calling unit is used to customize the signal composition in the test signal set.

3. The passenger car parking brake system test system based on data closed loop technology according to claim 1, characterized in that: The test signal set includes a function classification signal, a fault injection signal and a pass indication signal.

4. The passenger car parking brake system test system based on data closed loop technology according to claim 1, characterized in that: The fault injection subsystem realizes the analogy of the EPB controller system through hard-wired connection and BOB module; during the fault injection process, the BOB module captures and redirects the Ethernet frames from the ECU to monitor the real-time Ethernet data flow, and injects the vehicle communication fault on this basis; The circuit connection state is changed by hard-wire connection, and the vehicle hardware fault is injected on this basis.

5. The passenger car parking brake system test system based on data closed loop technology according to claim 4, characterized in that: The fault injection subsystem controls the timing and duration of fault injection by controlling the modification timing of data flow or circuit connection status.

6. The passenger car parking brake system test system based on data closed loop technology according to claim 1, characterized in that: In the test of the EPB controller system, the test is started after the characteristic signals are extracted from the test signal set and combined in order.

7. A passenger car parking brake system testing method based on data closed-loop technology, characterized in that: The test is performed using a passenger car parking brake system test system based on a data closed loop technology as described in any one of claims 1 to 6; the test comprises the following steps: Step 1, configuring a test system; the test system is a passenger car parking brake system test system based on data closed-loop technology; Step 2, verify whether there is fault information in the test system. If there is no fault information in the test system, execute the next step; if there is fault information in the test system, generate a warning message and send it to the tester, and end the process; Step 3, set the test case, and assign and configure the driving operation signal, gear signal, test scenario characteristic parameters and the parking brake system's own characterization signal based on the test case, and verify the validity of the switch state of the EPB controller system. If the verification fails, return to step 2; if the verification passes, execute the next step; Step 4, start the test, and during the test, the data acquisition module monitors and records the test data until the speed of the vehicle under test is reduced to zero or the maximum test time of this test case is reached; when the test system reports no fault information, proceed to the next step; Step 5: End the test.

Images