Vehicle testing platform based on virtual environment

Abstract

The present invention relates to the field of vehicle testing technology, and in particular, to a vehicle testing platform based on a virtual environment. The present invention comprises a virtual vehicle testing system, which comprises a communication unit, a display unit, a debugging unit and a monitoring unit. The communication unit is used to provide a virtual testing environment for a diagnostic device to be tested, the display unit is used to display the communication status, bus status, prompt information and current engineering storage location of the communication unit through a status bar, the debugging unit is used to debug and verify the electrical appliances of the vehicle, and the monitoring unit is used to monitor the bus. In the present invention, high-speed, stable and real-time data communication is achieved between a simulation vehicle ECU modeling processor and a diagnostic module, and the ECU modeling processor is provided with an expansion interface, which is convenient for interconnection of other systems, and is also convenient for future upgrades and maintenance, and has strong adaptability.

Description

Technical Field

[0001] The present invention relates to the technical field of whole vehicle testing, in particular to a whole vehicle testing platform based on a virtual environment. Background Art

[0002] With the steady development of the automotive industry, hybrid electric vehicles have received extensive attention and research worldwide. Hybrid electric vehicles require a lot of testing work. However, real vehicle testing is often accompanied by high costs, long time consumption, and a large number of staff requirements. Vehicle companies will bear huge cost and time pressures. Therefore, virtual vehicle testing is adopted by many car companies to conduct comprehensive performance tests on the virtual driving platform before the real vehicle road test to reduce the workload of the real vehicle road test.

[0003] However, in the process of virtual vehicle assembly, the interface of the vehicle test platform is relatively simple and very unstable, and the diagnostic data communication is very slow, which cannot meet customer needs. Summary of the invention

[0004] The purpose of the present invention is to provide a whole vehicle testing platform based on a virtual environment to solve the problems raised in the above background technology.

[0005] To achieve the above-mentioned object, the present invention provides a whole vehicle test platform based on a virtual environment, including a virtual whole vehicle test system, wherein the virtual whole vehicle test system includes a communication unit, a display unit, a debugging unit and a monitoring unit; the communication unit is used to provide a virtual test environment for the diagnostic equipment to be tested; the display unit is used to display the communication status, bus status, prompt information and current project storage location of the communication unit through a status bar; the debugging unit is used to debug and verify the electrical appliances of the whole vehicle; the monitoring unit is used to monitor the bus;

[0006] The communication unit includes a simulation module, a diagnosis module and a control module; the simulation module is used to simulate the communication message and protocol, and provide a virtual test environment for the diagnosis module; the diagnosis module is used to perform a simulation test on the whole vehicle in the virtual environment of the simulation module; the control module is used to control the diagnosis module to perform diagnostic operations;

[0007] The display unit includes a message prompt module and an engineering prompt module; the message prompt module is used to display the message in real time when the diagnostic module is tested; the engineering prompt module is used to display the bus type and ECU number of the current engineering configuration in the status bar, so that the bus type and ECU number of the current engineering configuration can be intuitively seen. Each ECU has a window, and its main functions include dynamically editing ECU response messages and displaying ECU communication messages in real time, importing and exporting XML files, which include basic information, dynamic data, fault codes, etc., and importing algorithm files dll, etc.

[0008] The debugging unit includes a virtual vehicle debugging module, a controller single-piece debugging module, a bench debugging module and an electrical software debugging module; the virtual vehicle debugging module is used to verify the electrical inspection program and product design logic of the vehicle; the controller single-piece debugging module is used to read and write, flash and test electrical single-pieces and diagnose functions; the bench debugging module is used to verify the electrical inspection program on the bench; the electrical software debugging module is used to test the electrical software of the real vehicle;

[0009] The monitoring unit includes a bus monitoring module and a verification module; the bus monitoring module is used to monitor and record the bus content in the debugging unit; the monitoring verification module is used to verify the diagnostic data in the debugging unit.

[0010] As a further improvement of the present technical solution, the simulation module includes an ECU modeling processor and a process editor, which are used to implement modeling processing, and its parameters allow editing and importing and exporting XML files; the process editor is used to generate XML files, and supports importing algorithm files dll, and also supports custom addition of scripts and loading dynamic database calculation seed / key.

[0011] As a further improvement of the technical solution, a diagnostic project is established between the ECU modeling processor and the diagnostic module, and the method for establishing the diagnostic project is as follows:

[0012] S1.1, set system parameters, including communication parameters such as IP and Port, and auxiliary parameters such as log and path;

[0013] S1.2, maintain ECU library;

[0014] S1.3, configure ECU basic parameters;

[0015] S1.4, configure the ECU bottom layer protocol, which includes the network layer protocol and the application layer protocol;

[0016] S1.5. Configure ECU flashing information and save it in the electronic control library.

[0017] It is worth mentioning that users can edit the response message of ECU according to the service ID. At the same time, it supports extracting the response message from the monitoring result message, allowing users to edit the response message for the second time, display the monitoring data message, support multiple classification displays such as network layer messages and application layer messages, and the displayed message supports multiple user operations such as pausing and clearing information.

[0018] As a further improvement of the technical solution, the process of ECU flashing information in S1.5 is as follows:

[0019] S2.1. Run the default session service to enter programmingSession;

[0020] S2.2. Run the security access service to enter a specific security level;

[0021] S2.3, run the write service to write the fingerprint information into the ECU;

[0022] S2.4. Run the data transmission service to write the default value into the permanent storage area;

[0023] S2.5. Run the routine control service to check whether S2.4 is successful;

[0024] S2.6, run the routine control service to erase the specific Flash;

[0025] S2.7, respectively run the data transmission service to download the Flashdriver into the memory;

[0026] S2.8, Run the routine control service to check whether the Flashdriver download is successful;

[0027] S2.9, respectively run the data transmission service to download the software and data to the flash of the ECU;

[0028] S2.10, run the routine control service to check whether the download in S2.9 is successful;

[0029] S2.11. Run the routine control service to verify whether the program can run normally.

[0030] As a further improvement of the present technical solution, the monitoring module adopts carrier monitoring, which is used to enable the station to continue to monitor the bus during the transmission time. Once a conflict is detected, the transmission is immediately stopped, and a series of short blocking messages are sent to the bus to notify each station on the bus that a conflict has occurred, thereby improving the utilization rate of the bus.

[0031] As a further improvement of the technical solution, the carrier sensing adopts a backoff algorithm to determine the avoidance time, and the algorithm includes the following steps:

[0032] S3.1, monitor the bus, the bus is idle, send with probability P, and delay one time unit with probability (1-P), one time unit is usually equal to twice the maximum propagation delay;

[0033] S3.2, after a delay of one time unit, repeat S3.1;

[0034] S3.3: The bus is in a non-idle state, and the monitoring continues until the medium is idle and S3.1 is repeated.

[0035] Among them, when determining the P value, first assume that when the bus is in a non-idle state, there are N stations with data waiting to be sent. Once the current transmission is completed, the total expected number of stations that will attempt to transmit is NP; if P is selected too large, so that NP>1, it indicates that there are multiple stations trying to send, and conflict is inevitable; the worst case is that as the probability of conflict continues to increase, the throughput is reduced to zero, so an appropriate P value must be selected to make NP<1. Of course, if the P value is selected too small, the bus utilization will be greatly reduced.

[0036] As a further improvement of the technical solution, the verification module includes overall function verification, sequence flow verification and simulated ECU verification.

[0037] As a further improvement of this technical solution, the overall function verification process is as follows:

[0038] S4.1. Receive the message and record the current ECU session mode as "extended";

[0039] S4.2. Perform security access to the ECU session. After the security access is passed, record that the current ECU security access has passed.

[0040] S4.3. Record the time interval for receiving the last instruction. If the timeout occurs, the session will be automatically returned to the default session and the security access will not be passed.

[0041] As a further improvement of this technical solution, the sequence flow verification process is as follows:

[0042] S5.1. Manually assemble the sequence flow according to the import protocol content;

[0043] S5.2, configure the time interval between commands and the necessary conditions for command execution;

[0044] S5.3. Verify that the process sequence is correct.

[0045] As a further improvement of this technical solution, the simulation ECU verification process is as follows:

[0046] S6.1. Simulate the real ECU working scenario according to the ECU working mode;

[0047] S6.2. After receiving the instruction, determine whether the instruction meets the session mode requirements, whether it has passed the security access, whether it meets the time requirements, whether it meets the sequence requirements, and whether it meets the precondition requirements according to the standard protocol mode;

[0048] S6.3. After the requirements of S6.2 are met, the response content is automatically generated and replied.

[0049] Compared with the prior art, the present invention has the following beneficial effects: high-speed, stable and real-time data communication is achieved between the simulation vehicle ECU modeling processor and the diagnostic module, and the ECU modeling processor is provided with an expansion interface to facilitate interconnection with other systems, and also to facilitate future upgrades and maintenance, and has strong adaptability. In addition, the bus is monitored through the monitoring module, and once a conflict is detected, the transmission is immediately stopped, and a series of short blocking messages are sent to the bus to notify each station on the bus that a conflict has occurred, thereby improving the utilization rate of the bus. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 Schematic diagram of the module structure of the virtual vehicle test system in the embodiment;

[0051] Figure 2 is a schematic diagram of the communication unit module structure in the embodiment;

[0052] Figure 3 is a schematic diagram of the structure of a display unit module in an embodiment;

[0053] Figure 4 Schematic diagram of the debugging unit module structure in the embodiment;

[0054] Figure 5 Schematic diagram of the monitoring unit module structure in the embodiment.

[0055] The meaning of each number in the figure is:

[0056] 100. Virtual vehicle testing system;

[0057] 110, communication unit; 111, simulation module; 112, diagnosis module; 113, control module;

[0058] 120, display unit; 121, message prompt module; 122, engineering prompt module;

[0059] 130. Debugging unit; 131. Virtual vehicle debugging module; 132. Controller single-piece debugging module; 133. Bench debugging module; 134. Electrical software debugging module;

[0060] 140. Monitoring unit; 141. Bus monitoring module; 142. Verification module. DETAILED DESCRIPTION

[0061] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0062] Example 1

[0063] The present invention provides a vehicle testing platform based on a virtual environment, please refer to Figure 1-Figure 5 , including a virtual vehicle test system 100, the virtual vehicle test system 100 includes a communication unit 110, a display unit 120, a debugging unit 130 and a monitoring unit 140; the communication unit 110 is used to provide a virtual test environment for the diagnostic equipment to be tested; the display unit 120 is used to display the communication status, bus status, prompt information and current project storage location of the communication unit 110 through a status bar; the debugging unit 130 is used to debug and verify the electrical appliances of the whole vehicle; the monitoring unit 140 is used to monitor the bus;

[0064] The communication unit 110 includes a simulation module 111, a diagnosis module 112 and a control module 113; the simulation module 111 is used to simulate the communication message and protocol, and the diagnosis service operation of the ECU with different communication rates and different communication protocols in the vehicle is simulated through the simulation module 111, and multiple ECUs are supported to communicate in parallel, and the data of the actual diagnosis communication of the ECU can be simulated, and the CAN protocol, K protocol, and DOIP protocol interface are reserved, and parallel diagnosis can be supported, and multiple CANs can be simulated to perform diagnostic operation diagnosis at the same time, so as to provide a virtual test environment for the diagnosis module 112; the diagnosis module 112 is used to perform simulation test on the whole vehicle in the virtual environment of the simulation module 111; the control module 113 is used to control the diagnosis module 112 to perform diagnostic operations;

[0065] The display unit 120 includes a message prompt module 121 and an engineering prompt module 122; the message prompt module 121 is used to display the message in real time when the diagnosis module 112 is tested; the engineering prompt module 122 is used to display the bus type and the number of ECUs configured in the current project in the status bar, so that the bus type and the number of ECUs configured in the current project can be intuitively seen. Each ECU has a window, and its main functions include dynamically editing ECU response messages and displaying ECU communication messages in real time, importing and exporting XML files, which include basic information, dynamic data, fault codes, etc., and importing algorithm files dll, etc.

[0066] The debugging unit 130 includes a virtual vehicle debugging module 131, a controller single-piece debugging module 132, a bench debugging module 133 and an electrical software debugging module 134; the virtual vehicle debugging module 131 is used to verify the electrical inspection program and product design logic of the vehicle; the controller single-piece debugging module 132 is used to read and write, flash and test the electrical single-piece and diagnose functions; the bench debugging module 133 is used to verify the electrical inspection program on the bench; the electrical software debugging module 134 is used to test the electrical software of the real vehicle;

[0067] The monitoring unit 140 includes a bus monitoring module 141 and a verification module 142 ; the bus monitoring module 141 is used to monitor and record the bus content in the debugging unit 130 ; the monitoring verification module 142 is used to verify the diagnostic data in the debugging unit 130 .

[0068] In this embodiment, the simulation module 111 includes an ECU modeling processor and a process editor, which are used to implement modeling processing. Its parameters allow editing and importing and exporting XML files. High-speed, stable and real-time data communication is achieved between the simulated vehicle ECU modeling processor and the diagnostic module 112. In addition, the ECU modeling processor is provided with an expansion interface to facilitate interconnection with other systems, and is also convenient for future upgrades and maintenance, and has strong adaptability. The process editor is used to generate XML files, and supports importing algorithm files dll, and also supports custom addition of scripts and loading dynamic database calculation seeds / keys.

[0069] Furthermore, a diagnostic project is established between the ECU modeling processor and the diagnostic module 112. The method for establishing the diagnostic project is as follows:

[0070] S1.1, set system parameters, including communication parameters such as IP and Port, and auxiliary parameters such as log and path;

[0071] S1.2, maintain ECU library;

[0072] S1.3, configure ECU basic parameters;

[0073] S1.4, configure the ECU bottom layer protocol, which includes the network layer protocol and the application layer protocol;

[0074] S1.5. Configure ECU flashing information and save it in the electronic control library.

[0075] It is worth mentioning that users can edit the response message of ECU according to the service ID. At the same time, it supports extracting the response message from the monitoring result message, allowing users to edit the response message for the second time, display the monitoring data message, support multiple classification displays such as network layer messages and application layer messages, and the displayed message supports multiple user operations such as pausing and clearing information.

[0076] Specifically, the process of ECU flashing information in S1.5 is as follows:

[0077] S2.1. Run the default session service to enter programmingSession;

[0078] S2.2. Run the security access service to enter a specific security level;

[0079] S2.3, run the write service to write the fingerprint information into the ECU;

[0080] S2.4. Run the data transmission service to write the default value into the permanent storage area;

[0081] S2.5. Run the routine control service to check whether S2.4 is successful;

[0082] S2.6, run the routine control service to erase the specific Flash;

[0083] S2.7, respectively run the data transmission service to download the Flashdriver into the memory;

[0084] S2.8, Run the routine control service to check whether the Flashdriver download is successful;

[0085] S2.9, respectively run the data transmission service to download the software and data to the flash of the ECU;

[0086] S2.10, run the routine control service to check whether the download in S2.9 is successful;

[0087] S2.11. Run the routine control service to verify whether the program can run normally.

[0088] In addition, the monitoring module 141 adopts carrier monitoring, which is used to enable the station to continue to monitor the bus during the transmission time. Once a conflict is detected, it immediately stops sending and sends a series of short blocking messages to the bus to notify each station on the bus that a conflict has occurred, which can improve the utilization of the bus.

[0089] In addition, carrier sensing uses a backoff algorithm to determine the avoidance time. The steps of the backoff algorithm are as follows:

[0090] S3.1, monitor the bus, the bus is idle, send with probability P, and delay one time unit with probability (1-P), one time unit is usually equal to twice the maximum propagation delay;

[0091] S3.2, after a delay of one time unit, repeat S3.1;

[0092] S3.3: The bus is in a non-idle state. Continue to monitor until the medium is idle and repeat S3.1.

[0093] Among them, when determining the P value, first assume that when the bus is in a non-idle state, there are N stations with data waiting to be sent. Once the current transmission is completed, the total expected number of stations that will attempt to transmit is NP; if P is selected too large, so that NP>1, it indicates that there are multiple stations trying to send, and conflict is inevitable; the worst case is that as the probability of conflict continues to increase, the throughput is reduced to zero, so an appropriate P value must be selected to make NP<1. Of course, if the P value is selected too small, the bus utilization will be greatly reduced.

[0094] Furthermore, the verification module 142 includes overall function verification, sequence flow verification and simulated ECU verification.

[0095] Specifically, the overall functional verification process is as follows:

[0096] S4.1. Receive the message and record the current ECU session mode as "extended";

[0097] S4.2. Perform security access to the ECU session. After the security access is passed, record that the current ECU security access has passed.

[0098] S4.3. Record the time interval for receiving the last instruction. If the timeout occurs, the session will be automatically returned to the default session and the security access will not be passed.

[0099] In addition, the sequence process verification process is as follows:

[0100] S5.1. Manually assemble the sequence flow according to the import protocol content;

[0101] S5.2, configure the time interval between commands and the necessary conditions for command execution;

[0102] S5.3. Verify that the process sequence is correct.

[0103] In addition, the simulation ECU verification process is as follows:

[0104] S6.1. Simulate the real ECU working scenario according to the ECU working mode;

[0105] S6.2. After receiving the instruction, determine whether the instruction meets the session mode requirements, whether it has passed the security access, whether it meets the time requirements, whether it meets the sequence requirements, and whether it meets the precondition requirements according to the standard protocol mode;

[0106] After the requirements of S6.3 and S6.2 are met, the response content is automatically generated and replied.

[0107] The above shows and describes the basic principles, main features and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited by the above embodiments. The above embodiments and descriptions are only preferred examples of the present invention and are not intended to limit the present invention. Without departing from the spirit and scope of the present invention, the present invention may have various changes and improvements, which fall within the scope of the present invention. The scope of protection of the present invention is defined by the attached claims and their equivalents.

Claims

1. A whole vehicle testing platform based on a virtual environment, comprising a virtual whole vehicle testing system (100), characterized in that: The virtual vehicle test system (100) comprises a communication unit (110), a display unit (120), a debugging unit (130) and a monitoring unit (140); the communication unit (110) is used to provide a virtual test environment for the diagnostic equipment to be tested; the display unit (120) is used to display the communication status, bus status, prompt information and current project storage location of the communication unit (110) through a status bar; the debugging unit (130) is used to debug and verify the electrical appliances of the vehicle; and the monitoring unit (140) is used to monitor the bus; The communication unit (110) comprises a simulation module (111), a diagnosis module (112) and a control module (113); the simulation module (111) is used to simulate the communication message and protocol; the diagnosis module (112) is used to perform a simulation test on the whole vehicle in the virtual environment of the simulation module (111); and the control module (113) is used to control the diagnosis module (112) to perform a diagnosis operation; The display unit (120) comprises a message prompt module (121) and an engineering prompt module (122); the message prompt module (121) is used for real-time display of messages during the test of the diagnostic module (112); the engineering prompt module (122) is used for displaying the bus type and the number of ECUs configured in the current engineering in a status bar; The debugging unit (130) comprises a virtual vehicle debugging module (131), a controller single-piece debugging module (132), a bench debugging module (133) and an electrical appliance software debugging module (134); the virtual vehicle debugging module (131) is used to verify the electrical inspection program and product design logic of the vehicle; the controller single-piece debugging module (132) is used to read and write, flash and test the electrical appliance single-piece and perform diagnostic functions; the bench debugging module (133) is used to verify the electrical inspection program on the bench; and the electrical appliance software debugging module (134) is used to test the electrical appliance software of the real vehicle; The monitoring unit (140) comprises a bus monitoring module (141) and a verification module (142); the bus monitoring module (141) is used to monitor and record the bus content in the debugging unit (130); and the verification module (142) is used to verify the diagnostic data in the debugging unit (130).

2. The whole vehicle testing platform based on virtual environment according to claim 1 is characterized by: The simulation module (111) comprises an ECU modeling processor and a process editor for implementing modeling processing, and its parameters allow editing and importing and exporting XML files; the process editor is used to generate XML files.

3. The whole vehicle testing platform based on virtual environment according to claim 2 is characterized by: A diagnostic project is established between the ECU modeling processor and the diagnostic module (112), and the method for establishing the diagnostic project is as follows: S1.1, set system parameters; S1.2, maintain ECU library; S1.3, configure ECU basic parameters; S1.4, configure the ECU underlying protocol; S1.

5. Configure ECU flashing information and save it in the electronic control library.

4. The whole vehicle testing platform based on virtual environment according to claim 3 is characterized by: The process of ECU flashing information in S1.5 is as follows: S2.

1. Run the default session service to enter programmingSession; S2.

2. Run the security access service to enter a specific security level; S2.3, run the write service to write the fingerprint information into the ECU; S2.

4. Run the data transmission service to write the default value into the permanent storage area; S2.

5. Run the routine control service to check whether S2.4 is successful; S2.6, run the routine control service to erase the specific Flash; S2.7, respectively run the data transmission service to download the Flashdriver into the memory; S2.8, Run the routine control service to check whether the Flashdriver download is successful; S2.9, respectively run the data transmission service to download the software and data to the flash of the ECU; S2.10, run the routine control service to check whether the download in S2.9 is successful; S2.

11. Run the routine control service to verify whether the program can run normally.

5. The whole vehicle testing platform based on virtual environment according to claim 1 is characterized by: The monitoring module (141) adopts carrier monitoring, and the carrier monitoring is used to enable the station to continue to monitor the bus during transmission.

6. The whole vehicle testing platform based on virtual environment according to claim 5 is characterized by: The carrier sensing adopts a backoff algorithm to determine the avoidance time, and the algorithm includes the following steps: S3.1, monitor the bus, the bus is idle, send with probability P, and delay one time unit with probability (1-P); S3.2, after a delay of one time unit, repeat S3.1; S3.3: The bus is in a non-idle state, and the monitoring continues until the medium is idle and S3.1 is repeated.

7. The whole vehicle testing platform based on virtual environment according to claim 1 is characterized by: The verification module (142) includes overall function verification, sequence flow verification and simulated ECU verification.

8. The whole vehicle testing platform based on virtual environment according to claim 7 is characterized by: The overall functional verification process is as follows: S4.

1. Receive the message and record the current ECU session mode as "extended"; S4.

2. Perform security access to the ECU session. After the security access is passed, record that the current ECU security access has passed. S4.

3. Record the time interval for receiving the last instruction. If the timeout occurs, the session will be automatically returned to the default session and the security access will not be passed.

9. The whole vehicle testing platform based on virtual environment according to claim 7 is characterized in that: The sequence process verification process is as follows: S5.

1. Manually assemble the sequence flow according to the import protocol content; S5.2, configure the time interval between commands and the necessary conditions for command execution; S5.

3. Verify that the process sequence is correct.

10. The whole vehicle testing platform based on virtual environment according to claim 7, characterized in that: The simulation ECU verification process is as follows: S6.

1. Simulate the real ECU working scenario according to the ECU working mode; S6.

2. After receiving the instruction, determine whether the instruction meets the session mode requirements, whether it has passed the security access, whether it meets the time requirements, whether it meets the sequence requirements, and whether it meets the precondition requirements according to the standard protocol mode; S6.

3. After the requirements of S6.2 are met, the response content is automatically generated and replied.

Images