ECU control method, device and system and storage medium

Automatically sending ban instructions through the ECU control script, solving the problem of inefficient testing by inputting a large number of instructions on the ECU ban operation, and achieving more efficient vehicle functional testing.

CN119511793APending Publication Date: 2025-02-25CHONGQING LANDIAN TECHNOLOGY CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202311059353.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-08-22
Publication Date
2025-02-25

AI Technical Summary

Technical Problem

In vehicle functional tests, ECU ban operation requires staff to enter a large number of service instructions, resulting in inefficient testing.

Method used

Through the ECU control script, respond to the staff's ban operation, send ban instructions to the ECU, and receive ban response information to realize the automatic ban and ban release of the ECU.

Benefits of technology

It greatly shortens the time required for vehicle functional testing, improves testing efficiency, and reduces the operating burden of staff.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119511793A_ABST
    Figure CN119511793A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides an ECU (Electronic Control Unit) control method, device and system and a storage medium, and the method comprises the steps that in response to an ECU prohibition operation triggered by a worker, a computer sends a prohibition instruction to an ECU through a CANoe device based on an ECU control script, and the prohibition instruction is used for indicating to prohibit the ECU from sending a message to controlled equipment; after the ECU receives the prohibition instruction and performs related operation, prohibition response information is sent to the computer through the CANoe device, and the prohibition response information is used for prompting whether the ECU successfully prohibits the speech or not. In the embodiment of the invention, a worker executes the speaking forbidding operation on the ECU through the ECU control script, and a related service instruction does not need to be input in the process of executing the speaking forbidding operation on the ECU, so that the time consumed when the function test is carried out on the vehicle can be greatly shortened, and the function test efficiency of the vehicle is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to an ECU control method, device, system, and storage medium. Background Art

[0002] As major automobile companies and parts companies have increasingly higher requirements for vehicle functional safety, more rigorous functional testing of vehicles is required.

[0003] During vehicle functional testing, to prevent the Electronic Control Unit (ECU) from performing irrelevant tasks during the test, which could result in inaccurate test results and circuit overload, the ECU must be muted before the vehicle functional test is performed to prevent it from sending messages to the controlled device.

[0004] In the prior art, it is usually necessary for staff to input a large number of relevant service commands to the ECU to achieve ECU mute. Since the staff needs to spend a lot of time to input relevant service commands when mute the ECU, the efficiency of the entire vehicle function test is low.

[0005] It should be pointed out that the information disclosed in the background technology section of this application is only intended to deepen the understanding of the general background technology of this application, and should not be regarded as an admission or any form of implication that the information constitutes prior art already known to those skilled in the art. Summary of the Invention

[0006] In view of this, the present application provides an ECU control method, device, system and storage medium to help solve the problem in the prior art that when performing a mute operation on the ECU, staff need to spend a lot of time entering relevant service instructions, resulting in low efficiency of functional testing of the entire vehicle.

[0007] In a first aspect, an embodiment of the present application provides a method for controlling an ECU, including:

[0008] In response to an ECU mute operation triggered by a staff member, a mute instruction is sent to the ECU based on the ECU control script, wherein the mute instruction is used to instruct the ECU to prohibit sending messages to the controlled device;

[0009] Receive a mute response message sent by the ECU, where the mute response message is used to prompt whether the ECU is successfully mute.

[0010] In a possible implementation, after receiving the mute response information sent by the ECU, the method further includes:

[0011] In response to an ECU muting release operation triggered by a staff member, sending a muting release instruction to the ECU based on the ECU control script, wherein the muting release instruction is used to indicate that the ECU is allowed to send messages;

[0012] Receive the muting release response information sent by the ECU, where the muting release response information is used to indicate whether the ECU has successfully released the muting.

[0013] In one possible implementation, before sending the mute instruction to the ECU based on the ECU control script, the method further includes: receiving a request ID and a response ID of a target ECU input by a staff member, the target ECU being the ECU that needs to be mute;

[0014] The sending of a mute instruction to the ECU based on the ECU control script includes: sending a mute instruction to the request ID of the target ECU based on the ECU control script;

[0015] The receiving the mute response information sent by the ECU includes: receiving the mute response information sent by the response ID of the target ECU.

[0016] In a possible implementation, the sending a muting release instruction to the ECU based on the ECU control script includes: sending a muting release instruction to the request ID of the target ECU based on the ECU control script;

[0017] The receiving the muting release response information sent by the ECU includes: receiving the muting release response information sent by the response ID of the target ECU.

[0018] In one possible implementation, before sending a mute instruction to the ECU based on the ECU control script in response to the ECU mute operation triggered by the staff, the method further includes: setting a mute button in response to a mute button setting instruction input by the staff;

[0019] The method of sending a mute instruction to the ECU based on an ECU control script in response to an ECU mute operation triggered by a staff member includes sending a mute instruction to the ECU based on an ECU control script in response to an ECU mute operation triggered by a staff member through the mute button.

[0020] In one possible implementation, before sending a mute release instruction to the ECU based on the ECU control script in response to the ECU mute release operation triggered by the staff, the method further includes: setting a mute release button in response to a mute release button setting instruction input by the staff;

[0021] The method of sending a muting release instruction to the ECU based on the ECU control script in response to the ECU muting release operation triggered by the staff includes sending a muting release instruction to the ECU based on the ECU control script in response to the ECU muting release operation triggered by the staff through the muting release button.

[0022] In a possible implementation, the ECU control script is a CAPL script.

[0023] In a second aspect, an embodiment of the present application provides an ECU control device, comprising:

[0024] processor;

[0025] Memory;

[0026] and a computer program, wherein the computer program is stored in the memory, and the computer program includes instructions, which, when executed by the processor, cause the ECU control device to execute any one of the methods according to the first aspect.

[0027] In a third aspect, an embodiment of the present application provides an ECU control system, including:

[0028] The ECU control device according to claim 8;

[0029] CANoe device;

[0030] ECU;

[0031] The ECU is communicatively connected to the CANoe device, and the CANoe device is communicatively connected to the ECU control device.

[0032] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, comprising a stored program, wherein when the program is running, the device where the computer-readable storage medium is located is controlled to execute any one of the methods in the first aspect.

[0033] In an embodiment of the present application, the staff performs a mute operation on the ECU through the ECU control script. Since there is no need to enter relevant service instructions during the process of performing the mute operation on the ECU, the time consumed in the functional testing of the vehicle can be greatly shortened, thereby improving the functional testing efficiency of the vehicle. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0035] Figure 1 A schematic diagram of an application scenario provided for an embodiment of the present application.

[0036] Figure 2 A flowchart of an ECU control method provided in an embodiment of the present application.

[0037] Figure 3 A flowchart of another ECU control method provided in an embodiment of the present application.

[0038] Figure 4 A flowchart of another ECU control method provided in an embodiment of the present application.

[0039] Figure 5 A flowchart of another ECU control method provided in an embodiment of the present application.

[0040] Figure 6 A flowchart of another ECU control method provided in an embodiment of the present application.

[0041] Figure 7 A schematic structural diagram of an ECU control device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0042] In order to better understand the technical solution of the present application, the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0043] It should be clear that the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0044] The terms used in the embodiments of the present application are for the purpose of describing specific embodiments only and are not intended to limit the present application. The singular forms "a", "an", "the" and "the" used in the embodiments of the present application and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise.

[0045] It should be understood that the term "and / or" as used herein simply describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A alone, A and B together, or B alone. Furthermore, the character " / " in this document generally indicates an "or" relationship between the associated objects.

[0046] To facilitate understanding, a specific application scenario is first exemplified below.

[0047] See also Figure 1 , is a schematic diagram of an application scenario provided by an embodiment of the present application. Figure 1 As shown, this application scenario shows a vehicle 100, a CANoe device 200, and an ECU control device 300. Vehicle 100 contains an ECU 101, also known as the vehicle's "driving computer." Its purpose is to control the vehicle's driving state and implement its various functions. Specifically, it utilizes data collection and exchange from various sensors and buses to determine the vehicle's state and the driver's intentions, and to control the vehicle through various actuators, where these actuators can be understood as controlled devices. CANoe device 200 is a device based on the CAN bus development environment, capable of modeling, simulating, testing, and developing CAN communication networks. ECU control device 300 is a program-controlled processing device, which can be a computer, etc. in practical applications. ECU control device 300 is communicatively connected to CANoe device 200, which in turn is communicatively connected to vehicle 100. Specifically, the communication connection between CANoe device 200 and vehicle 100 is a communication connection between CANoe device 200 and ECU 101 within vehicle 100.

[0048] It should be pointed out that Figure 1 This is only an illustrative description of the application scenario involved in the embodiment of the present application and should not be used as a limitation on the scope of protection of this application. For example, the vehicle 100 involved in the above application scenario can be a sports car, a sedan, a van, etc. The embodiment of the present application does not limit the specific form of the vehicle 100. In addition, it is understood that in addition to the vehicle 100 in the application scenario, Figure 1 In addition to the vehicle 100, ECU 101, CANoe device 102 and computer 103 involved, there are other functional units or modules, which will not be described in detail in the embodiments of the present application.

[0049] In the prior art, when an ECU needs to be muted, a worker typically needs to input a large number of relevant service commands via a computer to achieve the ECU muting control. Understandably, in the prior art, when muting an ECU, the worker needs to spend a considerable amount of time inputting the relevant service commands, which makes the entire vehicle functional testing inefficient.

[0050] To address the above issues, the present invention provides an electronic control unit control method. By compiling a mute instruction for silencing the ECU and configuring related mute operations within the ECU control script, personnel can directly mute the ECU, significantly reducing the time required for vehicle functional testing and improving vehicle testing efficiency. This is described in detail below.

[0051] See also Figure 2, is a flow chart of an ECU control method provided in an embodiment of the present application. This method can be applied to Figure 1 The application scenarios shown are as follows: Figure 2 As shown, it mainly includes the following steps.

[0052] Step S201: In response to the ECU mute operation triggered by the staff, a mute instruction is sent to the ECU based on the ECU control script.

[0053] In practice, a worker can trigger an ECU mute operation on a computer. Upon receiving this trigger, the computer sends a mute command to the ECU via the CANoe device. Specifically, an ECU control script can be preconfigured on the computer, and mute commands can be sent to the ECU based on this script. ECU mute operations can include keystrokes, voice commands, and fingerprints defined in the ECU control script. A mute command prohibits the ECU from sending messages to the controlled device.

[0054] For example, "Pressing the S key on the keyboard" is an ECU mute operation configured in the ECU control script. To mute the ECU, the operator presses the S key on the keyboard. Following the instructions written in the ECU control script, the computer sends a mute command to the ECU via the CANoe device, preventing the ECU from sending messages to the devices it controls.

[0055] It's worth noting that the CANoe software interface contains a program input box for compiling CANoe projects. Therefore, when pressing the "S" button, the computer display must not be on the CANoe software interface with the program input box. This prevents the "S" button from compiling the CANoe project instead of disabling the ECU.

[0056] In one possible implementation, the ECU control script described above can be a Communication Access Programming Language (CAPL). CAPL is a CAN bus access programming language, similar to C language, which can be applied to CANoe projects. It is a very mature programming language used in automotive electronics development. In the embodiment of the present application, CAPL is used as the script development language, which is easy to write and is also conducive to loading in the CANoe project.

[0057] Step S202: Receive the mute response information sent by the ECU, which is used to prompt the ECU whether the mute is successful.

[0058] In an embodiment of the present application, the ECU receives a mute instruction, performs mute processing according to the mute instruction, and after the mute processing is completed, determines whether the mute is successfully performed. The ECU sends a mute response message to the computer based on whether the mute is successfully performed. Specifically, the ECU sends the mute response message to the CANoe device, and the CANoe device then sends the received mute response message to the computer. The mute response message is used to indicate whether the ECU has successfully mute.

[0059] Specifically, the mute response information may include a mute success response information and a mute failure response information. The mute success response information indicates that the ECU has successfully muted, while the mute failure response information indicates that the ECU has failed to mute. For example, the mute success response information is 0 or 1, and the mute failure response information is 1 or 0.

[0060] In one possible implementation, if the ECU is successfully disabled and the disable command is executed successfully, the computer will receive a successful disable response from the ECU via the CANoe device and display the corresponding "S" button on the CANoe software interface. CANoe software analysis interfaces, such as the Trace interface, will also indicate that the target ECU has stopped sending messages, and the vehicle's instrument panel fault light will illuminate. If the ECU is not successfully disabled, the ECU will send a failed disable response to the computer via the CANoe device, and the corresponding "S" button will not be displayed on the CANoe software interface.

[0061] In an embodiment of the present application, the staff performs a mute operation on the ECU through the ECU control script. Since there is no need to enter relevant service instructions during the process of performing the mute operation on the ECU, the time consumed in the functional testing of the vehicle can be greatly shortened, thereby improving the functional testing efficiency of the vehicle.

[0062] See also Figure 3 , is a flow chart of another ECU control method provided in an embodiment of the present application. This method can be applied to Figure 1 The application scenarios shown are as follows: Figure 3 As shown, this method Figure 2 The following steps are also included after step S202.

[0063] Step S301: In response to the ECU mute release operation triggered by the staff, a mute release instruction is sent to the ECU based on the ECU control script.

[0064] In actual applications, after the ECU receives the mute instruction and completes the mute, the vehicle needs to be functionally tested. When the functional test is completed, the normal operation of the ECU needs to be restored. At this time, the ECU needs to be unbanned. The staff can trigger the ECU mute release operation in the computer. After the computer receives the ECU mute release operation triggered by the staff, it sends the mute release instruction to the ECU through the CANoe device. Specifically, the ECU control script can be pre-configured in the computer. The computer sends the mute release instruction to the ECU based on the ECU control script. Specifically, the computer sends the mute release instruction to the CANoe device, and the CANoe device then sends the received mute release instruction to the ECU. Among them, the mute release instruction is used to indicate that the ECU is allowed to send messages to the controlled device; the ECU mute release operation can be a button, voice, fingerprint, etc. defined in the ECU control script.

[0065] For example, "pressing the R key on the keyboard" is an ECU mute removal operation configured in the ECU control script. When the ECU needs to be muted, the operator can press the R key on the keyboard. Following the instructions programmed in the ECU control script, the computer sends a mute removal command to the ECU via the CANoe device, restoring the ECU to its working state.

[0066] It is worth noting that, as mentioned above, when pressing the "R" button, the display interface on the computer cannot be the CANoe software interface with a program input box, to prevent the "R" button from being used to compile the CANoe project instead of being used as an ECU disable operation to unlock the ECU.

[0067] Step S302: receiving a muting release response message sent by the ECU, and using the message to indicate whether the ECU has successfully released the muting.

[0068] In an embodiment of the present application, the ECU receives a ban release instruction, performs ban release processing according to the ban release instruction, and after the ban release processing is completed, determines whether the ban is successfully released. The ECU sends a ban release response message to the computer through the CANoe device based on whether it has successfully lifted the ban. The ban release response message is used to prompt the ECU whether the ban is successfully lifted.

[0069] Specifically, the muting release response information may include a muting release success response information and a muting release failure response information. The muting release success response information indicates that the ECU has successfully released the muting; the muting release failure response information indicates that the ECU has failed to release the muting. For example, the muting release success response information displays the corresponding button, while the muting release failure response information does not display the corresponding button.

[0070] In one possible implementation, if the ECU successfully removes the mute, the ECU mute removal command is successfully executed, and the computer receives a mute removal success response message sent by the ECU via the CANoe device, displays the corresponding button "R" on the CANoe software interface, and the vehicle's instrument panel returns to normal. If the ECU fails to remove the mute, the ECU sends a mute removal failure response message to the computer via the CANoe device, and does not display the corresponding button "R" on the CANoe software interface.

[0071] In some possible application scenarios, different ECUs need to be muted during vehicle functional testing. During testing, in order to determine the current ECU, the ID information of the target ECU can be configured in the ECU control script. The details are explained in detail below.

[0072] See also Figure 4 , is a flow chart of another ECU control method provided in an embodiment of the present application. This method can be applied to Figure 1 The application scenarios shown are as follows: Figure 4 As shown, this method Figure 3 As shown, step S401 is added before step S201.

[0073] Step S401: Receive the request ID and response ID of the target ECU input by the staff.

[0074] In actual applications, before the staff triggers the ECU mute operation defined in the control script, they also need to enter the target ECU's request ID and response ID in the ECU control script to achieve more precise control of the target ECU. The request ID is the address used by the target ECU to receive control instructions, and the response ID is the address used by the target ECU to send a response to whether the mute operation is successful.

[0075] In the embodiment of the present application, each ECU has a corresponding request ID and response ID. For example, the correspondence between the ECU and the request ID and response ID is shown in Table 1.

[0076] Table 1:

[0077]

[0078]

[0079] In one possible implementation, when the target ECU is ECU1, according to the ECU mute operation triggered by the staff, the computer can send a mute instruction to the request ID1 through the CANoe device, so that ECU1 performs the mute operation, and then receives the success response information or failure response information sent from the response ID1, so that the staff can know whether the ECU mute instruction is successfully responded to.

[0080] Step S2011, Figure 3 In addition to step S201, the method further includes: in response to the ECU mute operation triggered by the staff, sending a mute instruction to the request ID of the target ECU based on the ECU control script.

[0081] Step S2021, in Figure 3 In addition to step S202, the method further includes: receiving a mute response message sent by the response ID of the target ECU, where the mute response message is used to prompt the ECU whether the mute is successfully performed.

[0082] The specific process of step S2011 and step S2021 is described above and will not be repeated here.

[0083] Step S3011, Figure 3 In addition to step S301, the method further includes: in response to the ECU mute release operation triggered by the staff, sending a mute release instruction to the request ID of the target ECU based on the ECU control script.

[0084] Step S3021, Figure 3 In addition to step S302, the method further includes: receiving a muting release response message sent by the response ID of the target ECU, where the muting release response message is used to indicate whether the ECU has successfully released the muting.

[0085] For example, referring to Table 1, when the target ECU1 is muted, according to the ECU muting operation triggered by the staff, the computer can send a muting removal instruction to the request ID1 through the CANoe device, so that the target ECU1 executes the muting removal operation, and then receives the success response information or failure response information sent from the response ID1, so that the staff can know whether the ECU muting removal instruction is successfully responded to.

[0086] See also Figure 5 , is a flow chart of another ECU control method provided in an embodiment of the present application. This method can be applied to Figure 1 The application scenarios shown are as follows: Figure 5 As shown, this method Figure 4 As shown, step S501 is added before step S2011.

[0087] Step S501: In response to a mute button setting instruction input by a staff member, a mute button is set.

[0088] In an embodiment of the present application, a staff member can set a mute operation in the ECU control script to be a key pressed on a computer keyboard. For example, the mute operation can be defined as letter keys such as "A," "B," and "C," or as numeric keys or other character keys on the keyboard. This application does not impose specific limitations on this. When the mute operation is defined as pressing a defined key on the keyboard, there is no need to add a separate trigger device to the device, reducing the complexity of the device while ensuring performance.

[0089] In addition, if Figure 5 As shown, this method Figure 4 As shown, step S502 is added before step S3011.

[0090] Step S502: In response to the muting release button setting instruction input by the staff, a muting release button is set.

[0091] In an embodiment of the present application, a staff member can set the ECU control script to press a key on the computer keyboard as the muting release operation. For example, the keyboard letter keys "A," "B," "C," etc. can be defined, or numeric keys or other character keys can be defined, which is not specifically limited in this application. When the muting release operation is defined as pressing a defined key on the keyboard, there is no need to add a separate trigger device to the device, which reduces the complexity of the device while ensuring performance.

[0092] Step S20111, in Figure 4 On the basis of step S2011 shown, it also includes: in response to the ECU mute operation triggered by the staff through the mute button, sending a mute instruction to the request ID of the target ECU based on the ECU control script.

[0093] Step S30111, in Figure 4 On the basis of step S3011 shown, it also includes: in response to the ECU mute release operation triggered by the staff through the mute release button, sending a mute release instruction to the request ID of the target ECU based on the ECU control script.

[0094] For ease of understanding, the control method of the electronic control unit provided in the embodiment of the present application is described in detail below in conjunction with a specific implementation method.

[0095] See also Figure 6 , a flow chart of another ECU control method provided in an embodiment of the present application. This method can be applied to Figure 1 The application scenarios shown are as follows: Figure 6As shown, the specific steps include the following steps.

[0096] Step S601: The vehicle is connected to the CANoe device.

[0097] Step S602: Open the CANoe project and load the CAPL script.

[0098] Step S603: Set the request ID and response ID of the ECU to be muted in the CAPL script.

[0099] Step S604: Setting a customized mute button and unmute button in the CAPL script.

[0100] Step S605: Compile and save the CAPL script.

[0101] Step S606: Run the CANoe project and press the custom mute button in the CANoe software interface.

[0102] Step S607: The muting is successful, the customized button responds successfully, and the CANoe software interface will display the corresponding button.

[0103] Step S608: The ECU is prohibited from sending messages to the controlled device, and the vehicle instrument fault light is turned on.

[0104] Step S609: Run the CANoe project and press the custom mute release button in the CANoe software interface.

[0105] Step S610: The ban is successfully lifted, the customized button responds successfully, and the CANoe software interface will display the corresponding button.

[0106] Step S611: Exit the mute mode and the instrument returns to normal.

[0107] Corresponding to the above embodiment, the present application also provides a structural schematic diagram of a control device of an electronic control unit.

[0108] See also Figure 7 , is a structural diagram of an ECU control device provided in an embodiment of the present application. Figure 7 As shown, the ECU control device 700 may include: a processor 701, a memory 702, and a communication unit 703. These components communicate via one or more buses. Those skilled in the art will appreciate that the server structure shown in the figure does not limit the embodiments of the present invention. It may be a bus structure or a star structure, and may include more or fewer components than shown, or combine certain components, or arrange the components differently.

[0109] The communication unit 703 is configured to establish a communication channel so that the storage device can communicate with other devices, receive staff data sent by other devices, or send staff data to other devices.

[0110] The processor 701 is the control center of the storage device. It uses various interfaces and lines to connect various parts of the entire electronic device. It runs or executes software programs and / or modules stored in the memory 702, and calls data stored in the memory to perform various functions of the electronic device and / or process data. The processor can be composed of an integrated circuit (IC), for example, it can be composed of a single packaged IC, or it can be composed of multiple packaged ICs with the same or different functions. For example, the processor 701 can only include a central processing unit (CPU). In an embodiment of the present invention, the CPU can be a single computing core or multiple computing cores.

[0111] The memory 702 is used to store execution instructions of the processor 701. The memory 702 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0112] When the execution instructions in the memory 702 are executed by the processor 701, the terminal 700 is enabled to execute some or all of the steps in the above method embodiments. In a specific implementation, the present application also provides a computer storage medium, wherein the computer storage medium may store a program, and when the program is executed, the program may include some or all of the steps in each embodiment provided in the present application. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM) or a random access memory (RAM).

[0113] Corresponding to the above embodiments, an embodiment of the present application also provides an ECU control system, which includes an ECU control device, a CANoe device and an ECU, wherein the ECU is communicatively connected to the CANoe device, and the CANoe device is communicatively connected to the ECU control device. The system is used to execute some or all of the steps in the above method embodiments.

[0114] Corresponding to the above embodiment, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium may store a program, wherein, when the program is executed, the device containing the computer-readable storage medium may be controlled to perform some or all of the steps in the above method embodiment. In a specific implementation, the computer-readable storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

[0115] In the embodiments of the present application, "at least one" refers to one or more, and "more" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent the existence of A alone, the existence of A and B at the same time, and the existence of B alone. Among them, A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" and similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b and c can be represented by: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0116] Those skilled in the art will appreciate that the various units and algorithm steps described in the embodiments disclosed herein can be implemented using a combination of electronic hardware, computer software, and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.

[0117] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0118] In the several embodiments provided by the present invention, if any function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, etc., various media that can store program codes.

[0119] The above description is merely a specific embodiment of the present invention. Any modifications or substitutions that may be readily conceived by a person skilled in the art within the technical scope disclosed herein are intended to be encompassed within the scope of protection of the present invention. The scope of protection of the present invention shall be subject to the scope of protection of the claims.

Claims

1. An ECU control method, characterized in that: The method comprises: In response to an ECU mute operation triggered by a staff member, a mute instruction is sent to the ECU based on an ECU control script, wherein the mute instruction is used to instruct the ECU to prohibit sending messages to the controlled device; The mute response information sent by the ECU is received, where the mute response information is used to prompt whether the ECU is successfully mute.

2. The method according to claim 1, characterized in that After receiving the mute response information sent by the ECU, the method further includes: In response to an ECU muting release operation triggered by a staff member, a muting release instruction is sent to the ECU based on the ECU control script, wherein the muting release instruction is used to indicate that the ECU is allowed to send messages; The muting release response information sent by the ECU is received, where the muting release response information is used to indicate whether the ECU has successfully released the muting.

3. The method according to claim 2, characterized in that Before sending the mute instruction to the ECU based on the ECU control script, the method further includes: receiving a request ID and a response ID of a target ECU input by a staff member, the target ECU being the ECU that needs to be mute; The sending a mute instruction to the ECU based on the ECU control script includes: sending a mute instruction to the request ID of the target ECU based on the ECU control script; The receiving the mute response information sent by the ECU includes: receiving the mute response information sent by the response ID of the target ECU.

4. The method according to claim 3, characterized in that The sending a muting release instruction to the ECU based on the ECU control script includes: sending a muting release instruction to the request ID of the target ECU based on the ECU control script; The receiving the muting release response information sent by the ECU includes: receiving the muting release response information sent by the response ID of the target ECU.

5. The method according to claim 1, characterized in that Before sending a mute instruction to the ECU based on the ECU control script in response to the ECU mute operation triggered by the staff, the method further includes: setting a mute button in response to a mute button setting instruction input by the staff; The method of sending a mute instruction to the ECU based on an ECU control script in response to an ECU mute operation triggered by a staff member includes sending a mute instruction to the ECU based on an ECU control script in response to an ECU mute operation triggered by a staff member through the mute button.

6. The method according to claim 2, characterized in that Before sending a muting release instruction to the ECU based on the ECU control script in response to the ECU muting release operation triggered by the staff, the method further includes: setting a muting release button in response to a muting release button setting instruction input by the staff; The method of sending a muting release instruction to the ECU based on the ECU control script in response to an ECU muting release operation triggered by a staff member includes sending a muting release instruction to the ECU based on the ECU control script in response to an ECU muting release operation triggered by a staff member through the muting release button.

7. The method according to claim 1, characterized in that The ECU control script is a CAPL script.

8. An ECU control device, characterized in that: The device comprises: processor; Memory; and a computer program, wherein the computer program is stored in the memory, and the computer program includes instructions, and when the instructions are executed by the processor, the ECU control device executes the method according to any one of claims 1 to 7.

9. An ECU control system, characterized in that: The system comprises: The ECU control device as claimed in claim 8; CANoe device; ECU; Among them, the ECU is communicatively connected to the CANoe device, and the CANoe device is communicatively connected to the ECU control device.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the method according to any one of claims 1 to 7.

Citation Information

Cited By

  • ECU speech forbidding method and device, electronic equipment and readable storage medium

    CN121056267A