A vehicle domain controller debugging method, system, device and medium

Abstract

This application provides a vehicle domain controller debugging method, system, device, and medium. The method includes: interacting with the vehicle controller via a request message to enter debugging mode; inputting a debugging message and assigning values to corresponding parameters in the vehicle domain controller via the debugging message, completing vehicle debugging based on the assigned parameters, and obtaining a debugging result. This application is suitable for rapid calibration and verification of minor code changes and single functions.

Description

Technical Field

[0001] The present application relates to the field of vehicle control technology, and in particular to a method, system, device and medium for debugging a vehicle domain controller. Background Art

[0002] Existing patent CN202453728U describes a CAN bus-based debugging system for electric vehicles, including a vehicle controller, motor controller, instrument unit, and BMS. The system is characterized by: the vehicle controller, motor controller, instrument unit, and BMS are each connected to and communicate with the CAN bus; the CAN bus is also connected to a PC platform, which communicates with the vehicle controller, motor controller, instrument unit, and BMS via the CAN bus. During the electric vehicle debugging process, the debugger can use the PC platform in the CAN bus-based debugging system to access information from any electrical device on the vehicle's CAN bus network in real time, intuitively converting the vehicle's current status and performance information into text and icons.

[0003] This patented debugging entry only involves CAN communication, which carries the risk of accidental touch, and does not mention the strategy for storing internal debugging values.

[0004] The existing patent CN106404423A is a real-time monitoring system for electric vehicle debugging. The present invention solves the problem of inconvenience in detecting CAN bus data in the prior art, and designs a real-time monitoring system for electric vehicle debugging that can perform real-time monitoring indoors and one inspector can simultaneously detect the operating conditions of multiple vehicles.

[0005] This patent only monitors the vehicle status through the CAN bus and cannot perform testing and debugging work to modify internal variables.

[0006] CN103916452A discloses a gas vehicle debugging system and method based on mobile devices and the Internet. The system includes a mobile terminal connected to a control system inside the gas vehicle, a server connected to the mobile terminal via the Internet, and a cloud server connected to the server via the network. The mobile terminal is used to register and log in the customer, and obtain debugging information content after logging in.

[0007] This patent describes the interaction logic between the vehicle and external parties, but does not mention the vehicle's internal software processing strategy. Summary of the Invention

[0008] In view of the above problems existing in the existing technology, this application proposes a vehicle domain controller debugging method, system, device and medium, which mainly solves the problem that the existing debugging methods do not involve the internal debugging logic of the vehicle and are difficult to meet actual debugging needs.

[0009] In order to achieve the above-mentioned objectives and other objectives, the technical solutions adopted in this application are as follows.

[0010] This application provides a vehicle domain controller debugging method, including:

[0011] Interact with the vehicle controller through request messages to enter the debugging mode;

[0012] Input the debugging message and assign the corresponding parameters in the vehicle domain controller through the debugging message, so as to complete the vehicle debugging according to the assigned corresponding parameters and obtain the debugging result.

[0013] In an embodiment of the present application, before interacting with the vehicle controller through a request message to enter the debugging mode, it also includes: executing a first preset action within a preset time to trigger the request message.

[0014] In one embodiment of the present application, interacting with the vehicle controller via a request message to enter the debugging mode includes:

[0015] Sending the request message to the vehicle domain controller, wherein the request message includes an identity identifier;

[0016] The obtained response information of the vehicle domain controller is verified, and the debugging mode is entered after the verification passes, wherein the response information includes a response identifier and a response message generated by the vehicle domain controller according to the identity identifier.

[0017] In one embodiment of the present application, verifying the acquired response information of the vehicle domain controller includes:

[0018] Comparing the response identifier and the response message with pre-stored verification data, respectively, wherein the verification data includes a target identifier and a target message;

[0019] When the identity identifier is consistent with the target identifier and the response message is consistent with the target message, the verification is passed and the debugging mode is entered.

[0020] In one embodiment of the present application, inputting a debugging message and assigning values to corresponding parameters in the vehicle domain controller through the debugging message includes:

[0021] Determining parameters to be assigned in the vehicle domain controller according to coding information corresponding to different frames of the debug message, wherein the coding information of different frames in the debug message corresponds to different vehicle domain controller parameters;

[0022] The target script of the vehicle domain controller is called according to the value of the parameter to be assigned in the debugging message to perform corresponding parameter assignment, wherein the target script contains the execution order and execution logic between different vehicle domain controller parameters.

[0023] In one embodiment of the present application, after completing vehicle debugging according to the assigned corresponding parameters, it includes: executing a second preset action to exit the debugging mode.

[0024] In an embodiment of the present application, after exiting the debugging mode, the method further includes: restoring the value of the corresponding parameter of the vehicle domain controller to the value before the debugging assignment.

[0025] This application also provides a vehicle domain controller debugging system, including:

[0026] The debugging access module is used to interact with the vehicle controller through request messages to enter the debugging mode;

[0027] The debugging module is used to input the debugging message and assign the corresponding parameters in the vehicle domain controller through the debugging message, so as to complete the vehicle debugging according to the assigned corresponding parameters and obtain the debugging result.

[0028] The present application also provides a computer device, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the vehicle domain controller debugging method when executing the computer program.

[0029] The present application also provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the vehicle domain controller debugging method.

[0030] As described above, the present application provides a vehicle domain controller debugging method, system, device and medium, which have the following beneficial effects.

[0031] This application interacts with the vehicle domain feeder through a request message to enter the debugging mode, and completes the debugging function verification by assigning parameters based on the debugging mode, which can reduce the debugging equipment, reduce the complexity of the debugging work, and improve the debugging efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 This is a flow chart of a vehicle domain controller debugging method in one embodiment of the present application.

[0033] Figure 2 This is a flow chart of parameter assignment based on a message in one embodiment of the present application.

[0034] Figure 3This is a schematic diagram of the overall process of debugging the vehicle domain controller in one embodiment of the present application.

[0035] Figure 4 This is a module diagram of the vehicle domain controller debugging system in one embodiment of the present application.

[0036] Figure 5 This is a schematic structural diagram of a device in one embodiment of the present application. DETAILED DESCRIPTION

[0037] The following describes the embodiments of the present application through specific examples. Those skilled in the art can easily understand the other advantages and effects of the present application from the content disclosed in this specification. The present application can also be implemented or applied through other different specific embodiments. The details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present application. It should be noted that the following embodiments and features in the embodiments can be combined with each other unless they conflict.

[0038] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present application. Therefore, the illustrations only show components related to the present application and are not drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component can be changed at will, and the component layout type may also be more complicated.

[0039] See also Figure 1 , the present application provides a vehicle domain controller debugging method, the method comprising the following steps:

[0040] Step S100: interact with the vehicle controller via a request message to enter a debugging mode.

[0041] In one embodiment, before interacting with the vehicle controller via a request message to enter the debugging mode, the method further includes: executing a first preset action within a preset time to trigger the request message.

[0042] Specifically, in Ready P gear with the handbrake pulled up, press the accelerator pedal three times within 1 minute, and then press the brake pedal three times. There is more than one way to enter through hardware, such as using a hard-wired switch in combination with other operations. The specific entry method can be adjusted according to actual application needs and is not restricted here.

[0043] In one embodiment, interacting with the vehicle controller via a request message to enter the debugging mode includes:

[0044] Sending the request message to the vehicle domain controller, wherein the request message includes an identity identifier;

[0045] The obtained response information of the vehicle domain controller is verified, and the debugging mode is entered after the verification passes, wherein the response information includes a response identifier and a response message generated by the vehicle domain controller according to the identity identifier.

[0046] In one embodiment, verifying the acquired response information of the vehicle domain controller includes:

[0047] Comparing the response identifier and the response message with pre-stored verification data, respectively, wherein the verification data includes a target identifier and a target message;

[0048] When the identity identifier is consistent with the target identifier and the response message is consistent with the target message, the verification is passed and the debugging mode is entered.

[0049] Specifically, a request message is sent through the request ID. After receiving the response ID and response message from the vehicle domain controller, the vehicle enters the debugging mode and implements fault injection testing (such as fault limp, emergency high voltage, charging into P gear, and other strategy verification) and parameter debugging (such as drive feedback map debugging, etc.) through the debugging message.

[0050] Step S110: input a debugging message and assign values to corresponding parameters in the vehicle domain controller through the debugging message, so as to complete vehicle debugging according to the assigned corresponding parameters and obtain a debugging result.

[0051] In one embodiment, inputting a debugging message and assigning values to corresponding parameters in the vehicle domain controller through the debugging message includes:

[0052] Determining parameters to be assigned in the vehicle domain controller according to coding information corresponding to different frames of the debug message, wherein the coding information of different frames in the debug message corresponds to different vehicle domain controller parameters;

[0053] The target script of the vehicle domain controller is called according to the value of the parameter to be assigned in the debugging message to perform corresponding parameter assignment, wherein the target script contains the execution order and execution logic between different vehicle domain controller parameters.

[0054] Specifically, after the message interaction enters the debugging mode, the corresponding value of the debugging message is assigned to the fault flag and the parameter debugging variable usage to ensure that the internal variables of the code are successfully modified.

[0055] See also Figure 2 , Figure 2This is a flow chart illustrating the message-based parameter assignment process in one embodiment of the present application. The vehicle controller high voltage and speed-related parameters are assigned values. After the assignment is complete, the vehicle status is determined. Based on this status, a theoretical range value is calculated: 100 * SOE / 100km of energy consumption. A reference range value, a weighted range value, and a displayed range value are further calculated. A determination is made as to whether the displayed value meets the requirements. After debugging is complete, the displayed range value is restored from the previous cycle or the EEPROM.

[0056] In one embodiment, after the vehicle debugging is completed according to the assigned corresponding parameters, the method includes: executing a second preset action to exit the debugging mode.

[0057] In one embodiment, after exiting the debugging mode, the method further includes: restoring the value of the corresponding parameter of the vehicle domain controller to the value before the debugging assignment.

[0058] Specifically, see Figure 3 , Figure 3 This is a schematic diagram of the overall debugging process for a vehicle domain controller in one embodiment of this application. First, determine whether hard-wired signals such as the accelerator and brake pedals are available. If so, operate the accelerator and brake pedals to send a request ID and verify the response ID. After verification, enter debugging mode and set calibration values according to the settings. After debugging is complete, operate the accelerator and brake pedals or turn off the power to exit debugging mode.

[0059] In one embodiment, the first bit of the provisional message within the code indicates an emergency high-voltage fault, and the second bit indicates a change in the preset coordinate point on the drive map. A request ID and message are sent. Upon receiving the VCU response ID and message, a debug message is sent, with a frame rate of 10ms. The first bit of the message is 0x1, triggering the fault. The high-voltage status is observed for any changes. The second bit of the message is 0x1, and the coordinate point is shifted by the code preset + 5, observing changes in vehicle dynamics. The values of variables modified by this calibration method are not saved after power cycling, meaning they are restored to the original code values. This calibration method requires re-entry after power cycling; unsuccessful entry or exit operations require re-entry.

[0060] Based on the above technical solution, this application can be applied to rapid calibration and verification of small code changes or single functions.

[0061] See also Figure 4 This embodiment provides a vehicle domain controller debugging system for executing the vehicle domain controller debugging method described in the aforementioned method embodiment. Because the technical principles of the system embodiment are similar to those of the aforementioned method embodiment, the same technical details will not be repeated here.

[0062] In one embodiment, a vehicle domain controller debugging system includes: a debugging access module 10, which is used to interact with the vehicle controller through a request message to enter a debugging mode; a debugging module 11, which is used to input a debugging message and assign values to corresponding parameters in the vehicle domain controller through the debugging message, so as to complete vehicle debugging according to the assigned corresponding parameters and obtain a debugging result.

[0063] The embodiment of the present application also provides a vehicle domain controller debugging device, which may include: one or more processors; and one or more machine-readable media having instructions stored thereon, which, when executed by the one or more processors, enable the device to perform Figure 1 In practical applications, the device can be used as a terminal device or as a server. Examples of terminal devices may include: smartphones, tablet computers, e-book readers, MP3 (Moving Picture Experts Group Audio Layer III) players, MP4 (Moving Picture Experts Group Audio Layer IV) players, laptop computers, car computers, desktop computers, set-top boxes, smart TVs, wearable devices, etc. The embodiments of this application do not limit the specific devices.

[0064] The embodiment of the present application further provides a machine-readable medium in which one or more modules (programs) are stored. When the one or more modules are applied to a device, the device can execute the embodiment of the present application. Figure 1 Instructions for the steps included in the vehicle domain controller debugging method. The machine-readable medium can be any available medium capable of computer storage, or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, hard disk, or tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

[0065] See Figure 5 This embodiment provides a device 80, which can be a desktop computer, a portable computer, a smartphone, or other device. Specifically, device 80 includes at least a memory 82 and a processor 83 connected via a bus 81. The memory 82 is configured to store computer programs, and the processor 83 is configured to execute the computer programs stored in the memory 82 to perform all or part of the steps in the aforementioned method embodiment.

[0066] The system bus mentioned above can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The system bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus. The communication interface is used to realize communication between the database access device and other devices (such as clients, read-write libraries, and read-only libraries). The memory may include random access memory (RAM), and may also include non-volatile memory, such as at least one disk storage.

[0067] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components.

[0068] The above embodiments are merely illustrative of the principles and effects of this application and are not intended to limit this application. Anyone skilled in the art may modify or alter the above embodiments without departing from the spirit and scope of this application. Therefore, all equivalent modifications or alterations made by one of ordinary skill in the art without departing from the spirit and technical concepts disclosed in this application shall be covered by the claims of this application.

Claims

1. A vehicle domain controller debugging method, characterized in that: include: Interact with the vehicle controller through request messages to enter the debugging mode; Before interacting with the vehicle controller through a request message to enter the debugging mode, the method further includes: executing a first preset action within a preset time to trigger the request message; Interacting with the vehicle controller via a request message to enter a debugging mode includes: sending the request message to the vehicle domain controller, the request message including an identity identifier; verifying the obtained response information of the vehicle domain controller, and entering the debugging mode after the verification passes, wherein the response information includes a response identifier and a response message generated by the vehicle domain controller based on the identity identifier; Input a debugging message and assign values to corresponding parameters in the vehicle domain controller through the debugging message, so as to complete vehicle debugging according to the assigned corresponding parameters and obtain a debugging result; input a debugging message and assign values to corresponding parameters in the vehicle domain controller through the debugging message, including: determining the parameters to be assigned in the vehicle domain controller according to the coding information corresponding to different frames of the debugging message, wherein the coding information of different frames in the debugging message corresponds to different vehicle domain controller parameters; calling a target script of the vehicle domain controller according to the value of the parameter to be assigned in the debugging message to assign the corresponding parameter, wherein the target script includes the execution order and execution logic between different vehicle domain controller parameters; after completing vehicle debugging according to the assigned corresponding parameters, including: executing a second preset action to exit the debugging mode.

2. The vehicle domain controller debugging method according to claim 1, characterized in that: Verifying the obtained response information of the vehicle domain controller includes: Comparing the response identifier and the response message with pre-stored verification data, respectively, wherein the verification data includes a target identifier and a target message; When the identity identifier is consistent with the target identifier and the response message is consistent with the target message, the verification is passed and the debugging mode is entered.

3. The vehicle domain controller debugging method according to claim 1, characterized in that: After exiting the debugging mode, the method further includes: restoring the value of the corresponding parameter of the vehicle domain controller to the value before the debugging assignment.

4. A vehicle domain controller debugging system for executing the vehicle domain controller debugging method according to any one of claims 1 to 3, characterized in that: include: The debugging access module is used to interact with the vehicle controller through request messages to enter the debugging mode; The debugging module is used to input the debugging message and assign the corresponding parameters in the vehicle domain controller through the debugging message, so as to complete the vehicle debugging according to the assigned corresponding parameters and obtain the debugging result.

5. A computer device comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the vehicle domain controller debugging method according to any one of claims 1 to 3 when executing the computer program.

6. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the vehicle domain controller debugging method according to any one of claims 1 to 3 are implemented.

Images