CN115426381A - Method, system and electronic equipment for sending message - Google Patents

Method, system and electronic equipment for sending message Download PDF

Info

Publication number
CN115426381A
CN115426381A CN202210960951.8A CN202210960951A CN115426381A CN 115426381 A CN115426381 A CN 115426381A CN 202210960951 A CN202210960951 A CN 202210960951A CN 115426381 A CN115426381 A CN 115426381A
Authority
CN
China
Prior art keywords
message
error
parameter data
sending
type
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210960951.8A
Other languages
Chinese (zh)
Inventor
孙运跃
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hozon New Energy Automobile Co Ltd
Original Assignee
Hozon New Energy Automobile Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hozon New Energy Automobile Co Ltd filed Critical Hozon New Energy Automobile Co Ltd
Priority to CN202210960951.8A priority Critical patent/CN115426381A/en
Publication of CN115426381A publication Critical patent/CN115426381A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/24—Testing correct operation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]

Abstract

The application provides a method, a system and an electronic device for sending messages, wherein the method comprises the following steps: acquiring parameter data; generating an error message containing a message error type according to the message error type in the parameter data; and continuously sending the error message to a controller for checking the error message according to the preset error times. By the technical scheme provided by the embodiment of the application, the continuous message sending by repeatedly starting the vehicle information module is avoided, the time is reduced, and the message sending efficiency is improved.

Description

Method, system and electronic equipment for sending message
Technical Field
The present application relates to the field of electronic technologies, and in particular, to a method, a system, and an electronic device for sending a message.
Background
At present, most faults of automobiles are diagnosed through fault codes, such as chassis detection, automobile body and accessory detection, automobile pollutant and noise processing part related detection and the like, and the purpose is to find out the places and reasons of the automobile faults under the condition that the automobiles are not disassembled. Therefore, diagnostic Trouble Codes (DTCs) are of great importance.
With the continuous development of automobile technology and electronic technology, a Controller Area Network (CAN) is the most common vehicle-mounted Network applied at home and abroad at present. The fault diagnosis test is realized by the strong CAN bus development capability of the CANoe (CAN Open Environment), and based on the CANoe and the CAN bus Access Programming Language (CAPL), the method becomes a simple and low-cost mode. Currently, in a vehicle fault recording strategy, a CANoe-owned vehicle information (Automation) module is generally used to test a fault DTC of a rolling counter (periodic counter) and a fault DTC of a checksum (checksum).
However, when the automatic test rolling counter error DTC and the checksum error DTC are called, the automatic module needs to be continuously closed and restarted to send a message due to a complex use process, which consumes a lot of time and has low message sending efficiency.
Disclosure of Invention
The application provides a method, a system and an electronic device for sending messages, which are used for solving the problems that continuous message sending repeatedly started when an Automation module is used consumes a large amount of time and the message sending efficiency is low. The specific implementation scheme is as follows:
in a first aspect, the present application provides a method for sending a packet, where the method includes:
acquiring parameter data, wherein the parameter data at least comprises a message error type and preset error times, and the preset error times are the times for sending the message;
generating an error message containing the message error type according to the message error type in the parameter data;
and continuously sending the error message to a controller for checking the error message according to the preset error times.
And generating an error message containing the message error type according to the message error type in the parameter data, and continuously sending the error message to the controller according to the preset error times, so that the continuous message sending started repeatedly by using an Automation module is avoided, the time is reduced, and the message sending efficiency is improved.
In a possible design, the generating an error packet including the packet error type according to the packet error type in the parameter data includes:
acquiring a message identifier from the parameter data, and determining an original message corresponding to the message identifier;
and adjusting the original message according to the message error type to generate an error message containing the message error type.
The message identification is determined through the target node message, so that the problem that a large amount of time is consumed when the message received by the controller is determined to be the target node message is solved, the time for the controller to detect the target node message is saved, the testing efficiency is improved, and system resources are saved.
In one possible design, the generating an error packet including the packet error type includes:
acquiring the message length in the parameter data;
and generating an error message containing the message error type and the message length.
The message length is determined through the target node message, so that the problem that a large amount of time is consumed when the message received by the controller is determined to be the target node message is solved, the time for the controller to detect the target node message is saved, the testing efficiency is improved, and system resources are saved.
In one possible design, the continuously sending the error message to a controller that checks the error message includes:
acquiring a message period in the parameter data, wherein the message period is the sending time interval of two adjacent messages;
and continuously sending the error message to a controller for checking the error message periodically according to the message.
The message period is determined by the target node message, so that the problem of frame loss of the original message or DTC error recording is avoided, and the test accuracy is improved.
In a second aspect, the present application further provides a system for sending a message, where the system includes:
the device comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring parameter data, the parameter data at least comprises a message error type and preset error times, and the preset error times are the times of sending a message;
the generating module is used for generating an error message containing the message error type according to the message error type in the parameter data;
and the processing module is used for continuously sending the error message to a controller for checking the error message according to the preset error times.
In a possible design, the generating module is specifically configured to obtain a packet identifier from the parameter data, and determine an original packet corresponding to the packet identifier;
and adjusting the original message according to the message error type to generate an error message containing the message error type.
In a possible design, the generating module is specifically configured to obtain a message length from the parameter data;
and generating an error message containing the message error type and the message length.
In a possible design, the processing module is specifically configured to obtain a packet cycle in the parameter data, where the packet cycle is a transmission time interval between two adjacent packets;
and continuously sending the error message to a controller for checking the error message periodically according to the message.
In a third aspect, the present application provides an electronic device, comprising:
a memory for storing a computer program;
and the processor is used for realizing the steps of the message sending method when executing the computer program stored in the memory.
In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored therein, where the computer program is executed by a processor to implement the steps of a method for sending a message.
For each of the second to fourth aspects and possible technical effects of each aspect, please refer to the above description of the first aspect or the possible technical effects of each of the possible solutions in the first aspect, and no repeated description is given here.
Drawings
Fig. 1 is a flowchart of a method for sending a message according to the present application;
FIG. 2 is a schematic diagram of the parameter input interface;
FIG. 3 is a schematic diagram of a processing procedure of the method for sending a message;
fig. 4 is a schematic diagram of a system for sending messages according to the present application;
fig. 5 is a schematic view of an electronic device provided in the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be described in further detail with reference to the accompanying drawings. The particular methods of operation in the method embodiments may also be applied to apparatus embodiments or system embodiments. It should be noted that "a plurality" is understood as "at least two" in the description of the present application. "and/or" describes the association relationship of the associated object, indicating that there may be three relationships, for example, a and/or B, which may indicate: a exists alone, A and B exist simultaneously, and B exists alone. A is connected with B and can represent: a and B are directly connected and A and B are connected through C. In addition, in the description of the present application, the terms "first," "second," and the like are used for descriptive purposes only and are not intended to indicate or imply relative importance nor order to be construed.
The embodiments of the present application will be described in detail below with reference to the accompanying drawings.
Currently, in a vehicle fault recording strategy, an Automation module of a CANoe is generally used to test a fault DTC of a rolling counter and a fault DTC of a checksum. However, when the automatic test rolling counter error DTC and the checksum error DTC are called, the automatic module needs to be continuously closed and restarted to send a message due to a complex use process, which consumes a lot of time and has low message sending efficiency.
Therefore, the method for sending the message is provided, the error message containing the message error type is generated according to the message error type in the parameter data, and the error message is continuously sent to the controller according to the preset error times, so that the continuous message sending started repeatedly by using the Automation module is avoided, the time is reduced, and the message sending efficiency is improved.
Referring to fig. 1, a flowchart of a method for sending a packet according to an embodiment of the present application is shown, where the method includes:
s1, acquiring parameter data;
acquiring parameter data and starting a program for sending messages.
In the embodiment of the present application, the parameter data includes a packet error type, a preset error number, a packet length, a packet identifier, and a packet period.
It should be noted that the preset error times is the number of the transmitted messages, and the message period is the transmission time interval between two adjacent messages.
For example, as shown in fig. 2, the parameter input interface includes a fault type (i.e. a message error type), an error number (i.e. a preset error number), an ID (i.e. a message identifier), a DLC (i.e. a message length), a period (i.e. a message period), and a DataID List, which are input by a user, a trigger button and a stop button, wherein the Data List is used for inputting Data in an end-to-end calculation formula, when the trigger button is clicked, a program starts to run, automatically and continuously sends messages, and when the stop button is clicked, the program ends, and stops sending messages.
S2, generating an error message containing a message error type according to the message error type in the parameter data;
specifically, first, the parameter data acquired in step S1 is retrieved; the parameter data may include a packet identifier and a packet length. It should be noted that the parameter data may be various parameters input by the user in the parameter input interface shown in fig. 2.
Further, acquiring a message identifier and a message length from the parameter data, and then determining an original message corresponding to the message identifier; adjusting the original message according to the message error type; and finally generating an error message containing the message error type and the message length.
It should be noted here that, when acquiring a packet identifier, the packet identifier needs to correspond to a packet identifier of a target node packet, and if the packet identifier does not correspond to the packet identifier of the target node packet, a packet corresponding to any packet identifier is directly sent.
Therefore, in the embodiment of the present application, a target node packet received by a target controller is determined first, and then a corresponding packet identifier is determined according to a packet identifier of the target node packet, where the packet identifier represents the target node packet received by the controller. Therefore, the method avoids the problem that a large amount of time is consumed when the controller determines that the received message is the target node message, thereby saving the time for the controller to detect the target node message, improving the testing efficiency and saving the system resources.
For example, as shown in the schematic diagram of the parameter input interface shown in fig. 2, when a class a controller needs to be tested, it is first determined that the controller is a class a controller, and it is determined that the type of a message of a node B message received by the class a controller is 0x001, so that an ID (i.e., a message identifier) input in the parameter input interface diagram shown in fig. 2 is 0x001, and after a trigger button is touched, the message is sent to the class a controller, and at this time, the node B message received by the class a controller is a message with an ID of 0x 001.
It should be noted that, when the message length is obtained, the message length needs to correspond to the message length of the target node message, and if the message length does not correspond to the message length of the target node message, a message with any message length is directly generated and then sent to the controller.
Therefore, in the embodiment of the application, the message length is determined through the target node message, so that the problem that the controller determines that a large amount of time is consumed for determining the received message as the target node message is solved, the time for the controller to detect the target node message is saved, the test efficiency is improved, and system resources are saved.
For example, as shown in the schematic diagram of the parameter input interface shown in fig. 2, when a type a controller needs to be tested, first, a message type and a message length of a target node message received by the controller need to be determined, and if the message type of a node B message received by the type a controller is 0x001, then an input message ID (i.e., a message identifier) is 0x001 in an ID input area of the parameter input interface shown in fig. 2; if the message length of the node B message received by the type a controller is 8 bits, the DLC (i.e., the message length) on the parameter input interface shown in fig. 2 is 8, so the node B message received by the type a controller is a 0x001 type message with a message length of 8, and therefore, after the trigger button is touched, the message is sent to the type a controller, and at this time, the ID of the node B message received by the type a controller is 0x001 and the DLC is 8.
Further, it is also necessary to configure a message error type in the parameter input interface shown in fig. 2, for example, the fault type shown in fig. 2, where the message error type in the message may be configured in the area, it should be noted that, in this embodiment of the present application, the adjusting of the original message according to the message error type is mainly divided into the following three cases:
the first situation is as follows:
and if the message error type is the first type of error type, determining the value of a preset position in the original message by an assignment method so as to adjust the original message.
For example, as shown in the schematic diagram of the parameter input interface shown in fig. 2, the message error type is counter (i.e., the first type of error type), when the class a controller needs to be tested, it is determined that the message type of the B node message received by the class a controller is 0x001, and the message length is 8 bits, therefore, when the ID (i.e., the message identifier) of the parameter input interface shown in fig. 2 is 0x001, and DLC (i.e., the message length) is 8, for the message, the value of the 7 th byte position of the message is assigned to 1 by an assignment method, that is, the value of the preset position of the original message is 1, a counter error message with a message length of 8 bits is generated at this time, and the counter error message is sent to the class a controller, and at this time, the B node message received by the class a controller is a counter error message with an ID of 0x001, and DLC is 8.
Case two:
and if the message error type is the second type error type, determining the value of the preset position in the original message through an XOR algorithm so as to adjust the original message.
For example, as shown in the schematic diagram of the parameter input interface shown in fig. 2, the packet error type is checksum (i.e., the second type error type), when the class a controller needs to be tested, it is determined that the packet type of the node B packet received by the class a controller is 0x001 and the packet length is 8 bits, therefore, the ID (i.e., the packet identifier) of the parameter input interface shown in fig. 2 is 0x001 and the DLC (i.e., the packet length) is 8, for the packet, the value of the 8 th byte position of the packet is determined to be 1 by an xor algorithm, that is, the value of the preset position of the original packet is 1, at this time, a checksum error packet with a packet length of 8 bits is generated, and the checksum error packet is sent to the class a controller, at this time, the node B packet received by the class a controller is a checksum error packet with an ID of 0x001 and a DLC of 8.
Case three:
if The message error type is The third type error type, determining The value of The preset position in The original message through an end-to-end (E2E) calculation formula so as to adjust The original message.
For example, as shown in the schematic diagram of the parameter input interface shown in fig. 2, the packet error type is E2E (i.e., the third type error type), the DataID List is [01, 02, 03, 04], when a class a controller needs to be tested, it is determined that the packet type of a B node packet received by the class a controller is 0x001, and the length of a packet that can be received is 8 bits, therefore, the ID (i.e., the packet identifier) of the parameter input interface shown in fig. 2 is 0x001, and DLC (i.e., the packet length) is 8, for the packet, the value of the 7 th byte position of the packet is assigned as 1 by an assignment method, the value of the 8 th byte position of the packet is determined as 2 by an E2E calculation formula, that the value of the first preset position of the original packet is 1, the value of the second preset position is 2, at this time, an E2E error packet having a packet length of 8 bits is generated, and the E2E error packet is sent to the class a controller, at this time, the B node ID received by the class a controller is 0x001, and the E2E error packet is 8E error packet.
S3, continuously sending error messages to a controller for checking the error messages according to preset error times;
specifically, parameter data is retrieved; and determining the message period and the preset error times in the parameter data. It should be noted that, in the embodiment of the present application, the message period is a transmission time interval of two adjacent messages, and the preset number of errors is the number of the transmitted messages. Further, after the error message generated in step S2 is acquired; and continuously sending the error message to a controller for checking the error message periodically according to the preset error times and the message period.
It should be noted here that, when a packet period is obtained, the packet period needs to correspond to a period of a target node packet, and if the packet period does not correspond to the period of the target node packet, the packet is directly sent periodically according to any packet period, and when the period is too small, an original packet may be dropped, and when the period is too large, a DTC error record may be caused.
Therefore, in the embodiment of the application, the message period is determined according to the period of the target node message, so that the problem of frame loss of the original message or error recording of a DTC (digital time series controller) is avoided, and the test accuracy is improved.
For example, as shown in the schematic diagram of the parameter input interface shown in fig. 2, where the message error type is counter (i.e., the first type of error type), when the class a controller needs to be tested, it is determined that the message type of the node B message received by the class a controller is 0x001, and the message length is 8 bits, and a message can be received at intervals of 25 milliseconds (ms), so that the ID (i.e., the message identifier) of the parameter input interface shown in fig. 2 is 0x001, the DLC (i.e., the message length) is 8, and the period (i.e., the message period) is 25, for this message, the value of the 7 th byte position of this message is assigned to be 1 by an assignment method, i.e., the value of the preset position of the original message is 1, at this time, a counter error message with a message length of 8 bits is generated, and this counter error message is continuously sent to the class a controller at a period of 25ms, at this time, the node B message received by the class a controller is a counter message with an ID of 0x DLC, and a message period of 8, and a message period of 25.
It should be noted that, in this embodiment of the present application, after the number of error messages received by the controller has not reached the preset number of errors, the original message is continuously adjusted according to the message error type, an error message containing the message error type and having the message length is generated, and the error message is sent to the controller.
When the number of the error messages received by the controller reaches a preset number of error times, the controller sends a response, and can select to stop the program or continue to send the messages, and if the controller selects to continue to send the messages, the sent messages are all correct messages.
For example, in the schematic diagram of the parameter input interface shown in fig. 2, the number of errors (i.e., the preset number of errors) is 10 (i.e., a message is continuously sent 10 times to generate an error DTC), the message error type is counter, and when a class a controller needs to be tested, it is determined that the type of a B node message received by the class a controller is 0x001, the length of the message is 8, and a message can be received at an interval of 25ms, so that the ID (i.e., the message identifier) of the parameter input interface shown in fig. 2 is 0x001, the dlc (i.e., the length of the message) is 8, the period (i.e., the message period) is 25, it is determined by an assignment method that the value of the 7 th byte position in 10 continuous original messages is 1, 10 error messages are continuously sent to the controller in a period of 25ms, the messages subsequently sent to the controller are all correct messages, and since the number of the sent error messages reaches the preset number of errors, the controller records the DTC.
In summary, the method for sending a message provided by the present application generates an error message based on a preset fault type and a preset error frequency, and sends the generated error message to a controller. By the method, a small amount of data can be input, time is reduced, and message sending efficiency is improved. Meanwhile, each parameter is determined by matching the target node message, so that the problem that a large amount of time is consumed when the message received by the controller is determined to be the target node message is solved, and system resources are saved.
The technical solution of the present application is further described below with reference to specific application processes.
As shown in fig. 3, which is a schematic diagram of a processing procedure of a method for sending a message, parameter data is first obtained, where the parameter data includes a fault type, error times, an ID, a DLC, and a message period;
acquiring an original message corresponding to the ID;
if the preset fault type is the counter, determining the value of the specified position in the message through an assignment method;
if the fault type is checksum, determining the value of the appointed position in the message through an XOR algorithm;
if the fault type is E2E, determining the value of the specified position in the message through an E2E calculation formula;
generating an error message;
sending the error message to a controller;
judging whether the number of generated error messages is larger than the error times or not;
if not, continuing to generate the next error message;
if yes, the original message (i.e. the correct message) is sent to the controller.
Error messages are generated through fault types and are continuously sent to the controller, and correct messages can be sent to the controller all the time after preset error times are reached, so that the input data volume and time are reduced, the message sending efficiency is improved, and problems are convenient to troubleshoot.
Based on the same inventive concept, an embodiment of the present application further provides a message sending system, as shown in fig. 4, which is a schematic structural diagram of the message sending system provided by the present application, and the system includes:
an obtaining module 401, configured to obtain parameter data, where the parameter data at least includes a message error type and a preset error frequency, and the preset error frequency is a frequency of sending a message;
a generating module 402, configured to generate an error message including a message error type according to the message error type in the parameter data;
the processing module 403 is configured to continuously send the error message to the controller for verifying the error message according to the preset error times.
In a possible design, the generating module 402 is specifically configured to obtain a message identifier from the parameter data, and determine an original message corresponding to the message identifier;
and adjusting the original message according to the message error type to generate an error message containing the message error type.
In a possible design, the generating module 402 is specifically configured to obtain a message length in the parameter data;
and generating an error message containing the message error type and the message length.
In a possible design, the processing module 403 is specifically configured to obtain a message cycle in the parameter data, where the message cycle is a transmission time interval between two adjacent messages;
and continuously sending error messages to a controller for checking the error messages periodically according to the message period.
Based on the same inventive concept, an embodiment of the present application further provides an electronic device, where the electronic device can implement the function of the foregoing message sending system, and with reference to fig. 5, the electronic device includes:
at least one processor 501 and a memory 502 connected to the at least one processor 501, in this embodiment, a specific connection medium between the processor 501 and the memory 502 is not limited in this application, and fig. 5 illustrates an example where the processor 501 and the memory 502 are connected through a bus 500. The bus 500 is shown in fig. 5 by a thick line, and the connection manner between other components is merely illustrative and not limited thereto. The bus 500 may be divided into an address bus, a data bus, a control bus, etc., and is shown in fig. 5 with only one thick line for ease of illustration, but does not represent only one bus or type of bus. Alternatively, the processor 501 may also be referred to as a controller, without limitation to name a few.
In the embodiment of the present application, the memory 502 stores instructions executable by the at least one processor 501, and the at least one processor 501 can execute the method for sending a message discussed above by executing the instructions stored in the memory 502. The processor 501 may implement the functions of the various modules in the electronic device shown in fig. 5.
The processor 501 is a control center of the apparatus, and may connect various parts of the entire control device by using various interfaces and lines, and perform various functions and process data of the apparatus by operating or executing instructions stored in the memory 502 and calling data stored in the memory 502, thereby performing overall monitoring of the apparatus.
In one possible design, processor 501 may include one or more processing units and processor 501 may integrate an application processor that handles primarily operating systems, user interfaces, application programs, and the like, and a modem processor that handles primarily wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 501. In some embodiments, processor 501 and memory 502 may be implemented on the same chip, or in some embodiments, they may be implemented separately on separate chips.
The processor 501 may be a general-purpose processor, such as a Central Processing Unit (CPU), digital signal processor, application specific integrated circuit, field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, that may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method for sending a message disclosed in the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor.
Memory 502, which is a non-volatile computer-readable storage medium, may be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The Memory 502 may include at least one type of storage medium, and may include, for example, a flash Memory, a hard disk, a multimedia card, a card-type Memory, a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Programmable Read Only Memory (PROM), a Read Only Memory (ROM), a charge Erasable Programmable Read Only Memory (EEPROM), a magnetic Memory, a magnetic disk, an optical disk, and so on. The memory 502 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory 502 in the embodiments of the present application may also be circuitry or any other device capable of performing a storage function for storing program instructions and/or data.
By programming the processor 501, the code corresponding to the method for sending a message described in the foregoing embodiment may be solidified in the chip, so that the chip can execute the steps of the method for sending a message in the embodiment shown in fig. 4 when running. How to program the processor 501 is well known to those skilled in the art and will not be described in detail herein.
Based on the same inventive concept, embodiments of the present application further provide a storage medium storing computer instructions, which when executed on a computer, cause the computer to perform the method for sending a message discussed above.
In some possible embodiments, the aspects of the method for sending a message provided by the present application may also be implemented in the form of a program product, which includes program code for causing the control apparatus to perform the steps of the method for sending a message according to various exemplary embodiments of the present application described above in this specification, when the program product is run on a device.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims (10)

1. A method for sending a message, comprising:
acquiring parameter data, wherein the parameter data at least comprises a message error type and preset error times, and the preset error times are the times of sending the message;
generating an error message containing the message error type according to the message error type in the parameter data;
and continuously sending the error message to a controller for checking the error message according to the preset error times.
2. The method of claim 1, wherein generating an error message including the message error type according to the message error type in the parameter data comprises:
acquiring a message identifier from the parameter data, and determining an original message corresponding to the message identifier;
and adjusting the original message according to the message error type to generate an error message containing the message error type.
3. The method of claim 1, wherein generating an error message containing the message error type comprises:
acquiring the message length in the parameter data;
and generating an error message containing the message error type and the message length.
4. The method of claim 1, wherein continuously sending the error message to a controller that verifies the error message comprises:
acquiring a message period in the parameter data, wherein the message period is the sending time interval of two adjacent messages;
and continuously sending the error message to a controller for checking the error message periodically according to the message.
5. A system for sending messages, comprising:
the device comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring parameter data, the parameter data at least comprises a message error type and preset error times, and the preset error times are the times of sending a message;
the generating module is used for generating an error message containing the message error type according to the message error type in the parameter data;
and the processing module is used for continuously sending the error message to a controller for checking the error message according to the preset error times.
6. The system according to claim 5, wherein the generating module is configured to obtain a packet identifier in the parameter data, and determine an original packet corresponding to the packet identifier;
and adjusting the original message according to the message error type to generate an error message containing the message error type.
7. The system of claim 5, wherein the generating module is configured to obtain a message length in the parameter data;
and generating an error message containing the message error type and the message length.
8. The system of claim 5, wherein the processing module is configured to obtain a packet cycle in the parameter data, where the packet cycle is a transmission time interval between two adjacent packets;
and continuously sending the error message to a controller for checking the error message periodically according to the message.
9. An electronic device, comprising:
a memory for storing a computer program;
a processor for implementing the method steps of any one of claims 1-4 when executing the computer program stored on the memory.
10. A computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium, which computer program, when being executed by a processor, carries out the method steps of any one of claims 1-4.
CN202210960951.8A 2022-08-11 2022-08-11 Method, system and electronic equipment for sending message Pending CN115426381A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210960951.8A CN115426381A (en) 2022-08-11 2022-08-11 Method, system and electronic equipment for sending message

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210960951.8A CN115426381A (en) 2022-08-11 2022-08-11 Method, system and electronic equipment for sending message

Publications (1)

Publication Number Publication Date
CN115426381A true CN115426381A (en) 2022-12-02

Family

ID=84198093

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210960951.8A Pending CN115426381A (en) 2022-08-11 2022-08-11 Method, system and electronic equipment for sending message

Country Status (1)

Country Link
CN (1) CN115426381A (en)

Similar Documents

Publication Publication Date Title
CN110719199B (en) Network automatic testing and fault positioning method and device
CN111897724A (en) Automatic testing method and device suitable for cloud platform
CN113050601A (en) Vehicle offline diagnosis method and device, diagnosis equipment and storage medium
CN105975373A (en) Running monitoring method and apparatus for software program
CN115657521A (en) Method, device, vehicle and storage medium for analyzing CAN message data
CN112596447B (en) Method and device for determining length of ECU (electronic control Unit) flash data, electronic equipment and medium
CN110244972A (en) A kind of controller method for refreshing and diagnostic device
CN113157504A (en) Touch screen equipment testing method and touch screen equipment testing system
CN115426381A (en) Method, system and electronic equipment for sending message
CN112462727A (en) Vehicle-mounted part testing method and device
CN113127314A (en) Method and device for detecting program performance bottleneck and computer equipment
CN114837776B (en) SCR system control method, electronic device and storage medium
CN116383021A (en) Software package performance testing method, system, computing device and readable storage medium
CN116126832A (en) Database switching method, switching device, electronic equipment and storage medium
CN115657639A (en) System, method, device and storage medium for monitoring functions of vehicle-mounted chip
CN114218011A (en) Test simulation method and device, terminal equipment and storage medium
CN111611186B (en) Transmission control method and device in embedded chip
CN114879647A (en) ECU fault code test system, electronic controller and car
CN114327981A (en) Safety verification system, method and device of function safety mechanism
CN112965906A (en) Test system and test method
CN117076182B (en) Error reporting method, system on chip, computer equipment and storage medium
CN116991651B (en) Error injection method, system on chip, computer equipment and storage medium
CN115543657A (en) Application method and device of upper computer and electronic equipment
JP2002077071A (en) Automatic fault diagnosis and correction method for private wireless network
CN112598816B (en) Vehicle data acquisition method and device and vehicle diagnosis system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
CB02 Change of applicant information
CB02 Change of applicant information

Address after: 314500 988 Tong Tong Road, Wu Tong Street, Tongxiang, Jiaxing, Zhejiang

Applicant after: United New Energy Automobile Co.,Ltd.

Address before: 314500 988 Tong Tong Road, Wu Tong Street, Tongxiang, Jiaxing, Zhejiang

Applicant before: Hezhong New Energy Vehicle Co.,Ltd.