Dcb file processing method and apparatus, communication device, and readable storage medium

Abstract

This application discloses a DBC file processing method, apparatus, communication device, and readable storage medium, relating to the field of communication technology. The DBC file processing method obtains the CAN database DBC file of the CAN bus of a controller area network (CAN), then obtains CAN messages through the DBC file, and parses the CAN messages to obtain message identifiers and signal description information. Based on the message identifiers and signal description information, additional description information is determined. The message identifiers, the basic description information, and the additional description information are stored in a created target structure. This allows for the simultaneous definition of a structure compatible with multiple scenarios such as sending CAN messages, receiving CAN messages, and multiplexing signals, based on a single processing code, thereby improving the compatibility of the processing code with different CAN protocols, reducing the development and testing costs related to CAN bus communication, and improving efficiency.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a DBC file processing method, apparatus, communication device, and readable storage medium. Background Technology

[0002] A DBC (Database for CAN) file is an XML (Extensible Markup Language) format file used to define the CAN (Controller Area Network) bus communication protocol. It primarily describes the communication of Electronic Control Units (ECUs) within a CAN bus network. The DBC file contains information such as CAN communication signals, message IDs, data lengths, and transmission cycles, assisting developers in developing, testing, diagnosing, and analyzing CAN communication protocols.

[0003] In current DBC file receiving or sending schemes, the data storage order of more than 2 bytes is usually fixed, and the sent and received messages cannot be stored in the same structure. Furthermore, single-channel signals and multiplexed signals in the DCB file need to be processed separately using different processing codes.

[0004] It is evident that using the current DBC file receiving or sending scheme for CAN bus communication results in high development and testing costs and low efficiency because its processing code has poor compatibility with different CAN protocols. This necessitates frequent modifications to the processing code based on the DBC file content during communication. Summary of the Invention

[0005] The main objective of this application is to propose a DBC file processing method, apparatus, communication device, and readable storage medium, aiming to improve the compatibility of processing code based on DBC files with different CAN protocols, thereby reducing the development and testing costs related to CAN bus communication and improving efficiency.

[0006] In a first aspect, the present invention provides a DBC file processing method, the method comprising:

[0007] Obtain the CAN database DBC file of the CAN bus of the controller area network, wherein the DBC file is used to describe the protocol messages of the CAN bus;

[0008] The CAN message is obtained through the DBC file and parsed to obtain the message identifier and signal description information. The signal description information includes: signal name and basic description information.

[0009] Based on the message identifier and the signal description information, determine to add description information;

[0010] The message identifier, the basic description information, and the additional description information are stored in the created target structure. The target structure is used to parse the received CAN message or to encode the CAN message to be sent.

[0011] In an optional implementation, the signal description information includes: the signal name of at least one signal and basic description information of each signal; the additional description information includes: the additional description information of at least one signal.

[0012] The step of determining to add description information based on the message identifier and the signal description information includes:

[0013] Based on the message identifier and the signal description information of at least one signal, the additional description information of each signal is determined respectively;

[0014] The added description information includes: group index value, signal value description information, message value description information, signal storage order information, signal transmission time interval information, and signal reception timestamp information.

[0015] In an optional implementation, the target structure includes: at least one first structure and a second structure;

[0016] The method further includes:

[0017] Create at least one of the first structures and store the signal name, the basic description information, and the additional description information of at least one signal into at least one corresponding first structure;

[0018] The second structure is created, and the signal list information, group index signal information, multiplexing flag information, message identifier, message name description information, message frame type and message sending node description information of at least one signal are stored in the second structure.

[0019] In an optional implementation, the method further includes:

[0020] Receive CAN messages to be received;

[0021] Determine the second structure corresponding to the message identifier of the CAN message to be received from the target structure;

[0022] Based on the multiplexing flag information in the second structure, determine whether the message identifier corresponding to the CAN message to be received is a message identifier of multiplexed signals;

[0023] If it is a message identifier for multiplexed signals, then the second structure is used to locate the first group index number of the multiplexed signals to which the CAN message to be received belongs;

[0024] Based on the first set of index numbers, the second structure and at least one of the first structures are used to parse the signal values ​​of the CAN message to be received.

[0025] In an optional implementation, the method further includes:

[0026] If the message identifier is a single signal, then the second structure and at least one of the first structures are used to parse the signal value of the CAN message to be received.

[0027] In an optional implementation, the method further includes:

[0028] Obtain the CAN message to be sent;

[0029] The CAN message to be sent is parsed to obtain and set the signal name and signal value corresponding to the CAN message to be sent, and then stored in the preset message sending buffer.

[0030] Determine the second structure corresponding to the message identifier of the CAN message to be sent from the target structure;

[0031] Based on the multiplexing flag information in the second structure, determine whether the message identifier corresponding to the CAN message to be sent is a message identifier of multiplexed signals;

[0032] If it is a message identifier for multiplexed signals, then the second structure is used to locate the second group index number of the multiplexed signals to which the CAN message to be sent belongs;

[0033] Based on the second set of index numbers, the second structure and at least one of the first structures are used to encode the signal value of the CAN message to be sent, and the encoded CAN message to be sent is then sent.

[0034] In an optional implementation, the method further includes:

[0035] If the message identifier is a single signal, then the second structure and at least one of the first structures are used to encode the signal value of the CAN message to be sent, and the encoded CAN message to be sent is sent.

[0036] In a second aspect, the present invention provides a DBC file processing apparatus, comprising:

[0037] The acquisition module is used to acquire the DBC file of the CAN bus, wherein the DBC file is used to describe the protocol messages of the CAN bus;

[0038] The parsing module is used to obtain CAN messages through the DBC file and parse the CAN messages to obtain message identifiers and signal description information. The signal description information includes: signal name and basic description information.

[0039] The determining module is used to determine the addition of description information based on the message identifier and the signal description information;

[0040] A creation module is used to create a target structure and store the message identifier, the basic description information, and the additional description information into the target structure. The target structure is used to parse the received CAN message or encode the CAN message to be sent.

[0041] Thirdly, the present invention provides a communication device, comprising: a processor, a storage medium, and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform a method as described in any of the foregoing embodiments.

[0042] Fourthly, the present invention provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the method as described in any of the foregoing embodiments.

[0043] The beneficial effects of this application are:

[0044] The DBC file processing method provided in this application includes: obtaining a CAN database DBC file of a controller area network (CAN) bus, wherein the DBC file is used to describe the protocol messages of the CAN bus; obtaining CAN messages through the DBC file and parsing the CAN messages to obtain message identifiers and signal description information, wherein the signal description information includes: signal name and basic description information; determining additional description information based on the message identifiers and the signal description information; and storing the message identifiers, the basic description information, and the additional description information into a created target structure, wherein the target structure is used to parse received CAN messages or encode CAN messages to be sent. In this embodiment, a specific method is implemented by running processing code. CAN messages are obtained through a DBC file, parsed to obtain message identifiers and signal description information, and additional description information is determined based on these identifiers and information. The message identifier, basic description information, and additional description information are then stored in a created target structure. This target structure is used to parse received CAN messages or encode CAN messages to be sent. This allows for the creation of a target structure stored in a DBC file that is compatible with sending and receiving CAN messages and multiplexing signals, all using only one set of processing code. This structure can be used for subsequent CAN message transmission and reception without modifying the processing code. Different CAN protocols can be received, parsed, encoded, and sent by importing the DBC file, thus improving the compatibility of the processing code with different CAN protocols, reducing CAN bus communication development and testing costs, and increasing efficiency. Attached Figure Description

[0045] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on the structures shown in these drawings without creative effort.

[0046] Figure 1 This is a schematic flowchart of a DBC file processing method provided in an embodiment of this application;

[0047] Figure 2 This is a schematic diagram of the target structure provided in an embodiment of this application;

[0048] Figure 3 This is a schematic flowchart of a DBC file processing method provided in another embodiment of this application;

[0049] Figure 4 A schematic flowchart of a DBC file processing method provided in another embodiment of this application;

[0050] Figure 5 This is a schematic diagram of the structure of the DBC file processing device provided in the embodiments of this application;

[0051] Figure 6 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0052] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0053] Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0054] It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. The terms "comprising," "including," or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0055] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0056] The DBC file processing code currently used in CAN communication does not include flags to indicate single-channel and multiplexed signals in its structure. Therefore, it cannot support compatibility with transmitted messages, received messages, and multiplexed signals. Furthermore, when storing signals of more than 2 bytes, the signal storage order cannot be adjusted. If the CAN communication process involves receiving, parsing, encoding, and transmitting different CAN protocols, the relevant code needs to be frequently modified to adapt to these different CAN protocols, resulting in low CAN bus communication efficiency. The main purpose of this application is to propose a DBC file processing method that aims to improve the compatibility of the processing code based on DBC files with different CAN protocols, thereby reducing the development and testing costs related to CAN bus communication and improving efficiency.

[0057] Figure 1 This is a schematic flowchart of a DBC file processing method provided in an embodiment of this application. The executing entity of this method can be a computer or other device. The storage space of the computer or other device can be equipped with relevant software programs for the aforementioned DBC file processing. The software program can include processing code based on the DBC file. When the processing code is executed, the computer or other device can execute the aforementioned DBC file processing method to complete the sending and receiving of CAN messages in the DBC file, etc. Figure 1 As shown, the method includes:

[0058] S101. Obtain the CAN database DBC file of the CAN bus of the controller area network. The DBC file is used to describe the protocol messages of the CAN bus.

[0059] For example, the aforementioned acquisition of the CAN database DBC file of the Controller Area Network (CAN) bus can refer to receiving a DBC file sent from a transmitting device via the CAN bus. This transmitting device can be, but is not limited to, a computer, or a DBC file imported into local storage through other means. The aforementioned CAN bus protocol message can also be called a CAN message. This can refer, for example, to a frame transmitting data. This frame can be represented in hexadecimal numbers and can consist of seven parts, such as a frame start, arbitration segment, control segment, data segment, CRC (Cyclic Redundancy Check) segment, ACK (Acknowledge character) segment, and frame end. Furthermore, the CAN bus protocol messages can have two formats, such as a standard format and an extended format. The identifier (ID, IdentityDocument) length of the standard format and the extended format CAN bus protocol messages can be different. For example, the standard format can be 11 bits and the extended format can be 29 bits. The identifier of the CAN bus protocol message can also be called CAN_ID, which can be used to indicate whether the corresponding CAN bus protocol message is multiplexed, the number of signals it contains, the byte position of each signal, the conversion relationship between the message and the actual physical quantity, etc.

[0060] Of course, the above are just possible examples. The specific methods for obtaining the CAN bus DBC file, the specific types and formats of CAN bus protocol messages, and the specific content that the CAN_ID can indicate can all be selected and determined according to actual needs, and are not limited to the above.

[0061] S102. Obtain the CAN message through the above DBC file, and parse the above CAN message to obtain the message identifier and signal description information. The above signal description information includes: signal name and basic description information.

[0062] For example, the parsing of the CAN message to obtain the message identifier and signal description information can be implemented in the DBC file using a preset parsing algorithm or preset parsing program, such as the processing code. The message identifier can refer to the identifier of the CAN bus protocol message, i.e., CAN_ID, in the example above, while the basic description information can refer to the specific content that the CAN_ID can be used to indicate, such as whether the corresponding CAN bus protocol message is multiplexed (if it is multiplexed, the multiplexing group number can be further indicated), the number of signals contained, the byte position of each signal, and the conversion relationship between the message and the actual physical quantity.

[0063] Of course, the above are just possible examples. The specific way to parse the DBC file, the specific form of the above message identifier, and the specific information included in the above basic description information can all be selected and determined according to the actual situation, and there are no restrictions here.

[0064] S103. Based on the above message identifier and the above signal description information, determine to add description information.

[0065] For example, the aforementioned added descriptive information may include signal storage order of more than 2 bytes, time interval parameters, signal timestamps, etc. The aforementioned signal storage order of more than 2 bytes may be used to indicate the arrangement order between fields corresponding to signals of more than 2 bytes. The aforementioned signal timestamp may be used to indicate the time of signal reception. The aforementioned signal reception time interval may be used to indicate that after a preset duration, such as 30 seconds, 45 seconds, 60 seconds, etc., has elapsed since the signal reception time indicated by the aforementioned signal timestamp, the signal corresponding to the signal timestamp will be cleared to prevent communication blockage caused by the protocol message reception timeout of the aforementioned CAN bus.

[0066] Of course, the specific content, form, and content of the above-mentioned additional descriptive information can be selected and determined according to the actual situation, and there are no restrictions here.

[0067] S104. Store the above message identifier, the above basic description information, and the above additional description information into the created target structure. The target structure is used to parse the received CAN message or to encode the above CAN message to be sent.

[0068] For example, the target structure mentioned above can be a secondary structure stored in a DBC file. This secondary structure can be created by the processing code and can consist of a signal storage container and a variable. The basic description information and the additional description information mentioned above can correspond to the signals contained in the protocol message of the CAN bus. Each signal can have corresponding basic description information and additional description information. The signals contained in the protocol message of the CAN bus can be stored in the signal storage container of the secondary structure, and the message identifier can be stored in the variable mentioned above. It should be noted that there can be multiple target structures.

[0069] Of course, the above are just possible examples. The specific number, type and composition of target structures, specific message identifiers, the above basic description information and the storage location of the above additional description information can all be selected and determined according to the actual situation, and there are no restrictions here.

[0070] The DBC file processing method provided in this application includes: obtaining a CAN database DBC file of a controller area network (CAN) bus, wherein the DBC file is used to describe the protocol messages of the CAN bus; obtaining CAN messages through the DBC file and parsing the CAN messages to obtain message identifiers and signal description information, wherein the signal description information includes a signal name and basic description information; determining additional description information based on the message identifiers and the signal description information; and storing the message identifiers, the basic description information, and the additional description information into a created target structure, wherein the target structure is used to parse received CAN messages or encode CAN messages to be sent. In this embodiment, a specific method is implemented by running processing code. CAN messages are obtained through a DBC file, parsed to obtain message identifiers and signal description information, and additional description information is determined based on these identifiers and information. The message identifier, basic description information, and additional description information are then stored in a created target structure. This target structure is used to parse received CAN messages or encode CAN messages to be sent. This allows for the creation of a target structure stored in a DBC file that is compatible with sending and receiving CAN messages and multiplexing signals, all using only one set of processing code. This structure can be used for subsequent CAN message transmission and reception without modifying the processing code. Different CAN protocols can be received, parsed, encoded, and sent by importing the DBC file, thus improving the compatibility of the processing code with different CAN protocols, reducing the development and testing costs related to CAN bus communication, and improving efficiency.

[0071] Optionally, in Figure 1 Based on the embodiments, the above signal description information may include: the signal name of at least one signal and the basic description information of each signal, and the above additional description information may include: the above additional description information of at least one signal.

[0072] The above determination of additional description information based on the above message identifier and the above signal description information may include: determining the above additional description information for each signal based on the above message identifier and the above signal description information of at least one signal respectively;

[0073] The added descriptive information includes: group index value, signal value description information, message value description information, signal storage order information, signal transmission time interval information, and signal reception timestamp information.

[0074] Typically, the CAN bus protocol message contains multiple signals, each with a corresponding signal name, basic description information, and additional description information. Optionally, the signal name, basic description information, and additional description information corresponding to each signal can be the same or different.

[0075] For example, the aforementioned group index value can be used to indicate the group number corresponding to the multiplexed signal, that is, the aforementioned multiplexed group number. When the corresponding signal is a multiplexed signal, the group index value can be an integer greater than or equal to 0, such as 0, 1, 2, 3, etc. When the corresponding signal is a single signal, the group index value can be, for example, -2, etc.

[0076] Based on this, the additional description information can further include group index signal description information. This group index signal description information can be used to store the group index signal information of the corresponding multiplexed signal. For example, it can include information such as its start bit and length in the CAN message. If the corresponding signal is a single signal, the group index signal description information can be invalid or empty, etc., without any restrictions.

[0077] The aforementioned signal value description information can be used to indicate the physical quantity with practical significance obtained after the corresponding signal is parsed and converted according to a specific conversion relationship, while the aforementioned message value description information can be used to indicate the message value of the signal before parsing and conversion according to a specific conversion relationship. The message value can be, for example, a hexadecimal value.

[0078] Similar to the examples above, the signal storage order information can refer to the storage order of signals of 2 bytes or more, for example, it can be used to arrange the fields corresponding to signals of 2 bytes or more. The signal reception timestamp information can refer to the signal timestamp, for example, it can be used to indicate the time of signal reception. The signal transmission time interval information can refer to the signal reception time interval, for example, it can be used to indicate that after a preset time, such as 30 seconds, 45 seconds, 60 seconds, etc., has elapsed since the signal reception time indicated by the signal timestamp, the signal corresponding to the signal timestamp will be cleared to prevent communication blockage caused by the protocol message reception timeout of the CAN bus.

[0079] It is understood that the above content is only a possible example. The specific form and meaning of the group index value, group index signal description information, signal value description information, message value description information, signal storage order information, signal transmission time interval information, and signal reception timestamp information can be adjusted and determined according to the actual situation, and are not limited here.

[0080] Furthermore, based on the above embodiments, a target structure needs to be created, which may include: at least one first structure and a second structure. Figure 1The target structures in the embodiments are the same. The target structure can be, for example, a secondary structure stored in a DBC file. Each target structure can correspond to a CAN message. It can consist of a signal storage container and a variable. At least one of the first structures can be stored in the signal storage container. Each first structure can correspond to a signal in the CAN message. The second structure can be stored in the variable and correspond to the signal storage container. Therefore, the first structure can store, for example, the signal name, basic description information and additional description information of the corresponding signal. The second structure can store, for example, the relevant information of the corresponding signal storage container.

[0081] Accordingly, the above methods may also include:

[0082] Create at least one of the aforementioned first structures and store the signal name, basic description information, and additional description information of at least one signal into at least one corresponding aforementioned first structure.

[0083] The second structure is created to store the signal list information, group index signal information, multiplexing flag information, message identifier, message name description information, message frame type, and message sending node description information of at least one signal.

[0084] For example, at least one first structure created above is shown below:

[0085]

[0086]

[0087] Of course, the above content is only one possible example of the first structure. The comments after " / / " are the names of the corresponding fields. It is understood that the number and type of fields in the first structure corresponding to different signals may be different, and the names and specific uses of the above fields can be adjusted according to the actual situation, and are not limited to the above examples.

[0088] Based on this, the second structure instance created above is shown below:

[0089]

[0090] The aforementioned signal list information may refer to the aforementioned signal storage container, which can be used to store at least one of the aforementioned first structures corresponding to a signal; the aforementioned group index signal information may correspond to the group index value in the aforementioned first structure; the aforementioned multiplexing flag information may be used to indicate whether the signal in the aforementioned signal list information is a single-channel signal or a multiplexed signal. For example, the initial value of the aforementioned group index signal information may be -1. When the signal in the aforementioned signal list information is a single-channel signal, the value of the multiplexing flag information may be false, and the aforementioned group index signal information may be -2 after the processing code runs. When the signal in the aforementioned signal list information is a multiplexed signal, the value of the multiplexing flag information may be true, and the aforementioned group index signal information may be true after the processing code runs, corresponding to the aforementioned first structure. The group index value in the structure corresponds to a positive integer greater than 0, that is, the value of the above m_groupIndex field matches the value of the above M_Sinal; the above message identifier can refer to the identifier of the above CAN bus protocol message, that is, CAN_ID; the above message name description information can be used to indicate the message name corresponding to the above message identifier. It should be noted that the message name corresponds to the message, not the signal name; the above message frame type can be used to indicate the format of the above CAN bus protocol message frame, that is, the above standard format and extended format. The identifier (ID, Identitydocument) length of the above standard format and extended format CAN bus protocol message can be different. For example, it can be 11 bits for the standard format and 29 bits for the extended format; the above message sending node description information can be used to indicate the sending node name.

[0091] Of course, the above content is just one possible example of the second structure. The comments after " / / " are the names of the corresponding fields. It is understood that the number and type of fields in the second structure corresponding to different signals may be different, and the names and specific uses of the above fields can be adjusted according to the actual situation, and are not limited to the above examples.

[0092] For example, Figure 2 For a schematic diagram of the target structure provided in an embodiment of this application, please refer to... Figure 2 The aforementioned target structure may include: at least one first structure and a second structure, wherein the at least one first structure may be stored in... Figure 1 In the signal storage container of the target structure disclosed in the embodiment, the signal list information in the second structure can be used to indicate the signals in the signal storage container of the target structure, and the second structure can be stored in... Figure 1 The variables of the target structure disclosed in the embodiments correspond to the signal storage containers of their respective target structures. It is understood that... Figure 2 The content provided is merely a possible example. The target structure, the number of first structures, and the information within the first and second structures can all be adjusted and determined based on the actual situation, and are not intended to be fixed. Figure 2 The content is limited to what is included.

[0093] Figure 3 This is a schematic flowchart of a DBC file processing method provided in another embodiment of this application, as shown below. Figure 3 As shown, based on the above embodiments, the above method may further include:

[0094] S301, Receive CAN messages to be received.

[0095] For example, the aforementioned CAN message to be received may belong to Figure 1 The CAN bus protocol message in this embodiment is similar to the CAN bus protocol message described above. For example, it can refer to a data transmission frame. This frame can be represented by hexadecimal numbers and can consist of 7 parts, such as frame start, arbitration segment, control segment, data segment, CRC segment, ACK segment, and frame end. The CAN message to be received can also have two formats, such as a standard format and an extended format. The identifier (ID, IdentityDocument) length of the CAN bus protocol message in the standard format and the extended format can be different. For example, the standard format can be 11 bits and the extended format can be 29 bits. Receiving the CAN message to be received can refer to receiving the CAN message to be received sent from the transmitting device via the CAN bus. The transmitting device can be a device including but not limited to a computer. Of course, the above content is only a possible example. The specific form of the CAN message to be received and the specific receiving method can be selected and determined according to the actual situation, and are not limited here.

[0096] S302. Determine the second structure corresponding to the message identifier of the CAN message to be received from the target structure.

[0097] For example, the receiving of the CAN message to be received can be done by the first thread. Each time the first thread receives a CAN message, it can add it to the buffer queue. The determination of the second structure corresponding to the message identifier of the CAN message to be received from the target structure can be done by the second thread. When the second thread detects that the buffer is not empty, it can retrieve a message from the buffer and search for the CAN_ID corresponding to the CAN message to be received in the DBC file where the CAN message to be received is located. Then, it searches for the second structure stored in the local storage space according to the CAN_ID corresponding to the CAN message to be received until it finds a second structure with the same CAN_ID as the CAN_ID corresponding to the CAN message to be received.

[0098] S303. Based on the multiplexing flag information in the second structure, determine whether the message identifier corresponding to the CAN message to be received is a message identifier for multiplexing signals.

[0099] Continuing with the example above, the determination of whether the message identifier corresponding to the CAN message to be received is a multiplexed message identifier based on the multiplexing flag information in the second structure can be, for example, after finding a second structure with the same CAN_ID as the CAN message to be received, by obtaining the multiplexing flag of the second structure, such as the data in the MultiIDFlag field of the second structure example above, to determine whether the first structure in the signal storage container of the target structure to which the second structure corresponding to the CAN_ID belongs corresponds to a single signal or a multiplexed signal.

[0100] S304. If it is a message identifier for multiplexed signals, the second structure described above is used to locate the first group index number of the multiplexed signals to which the CAN message to be received belongs.

[0101] Continuing with the example above, if the above is a message identifier for multiplexed signals, then the second structure described above is used to locate the first group index number of the multiplexed signal to which the CAN message to be received belongs. This can be because when the second structure corresponding to the above CAN_ID corresponds to a multiplexed signal, for example, when the value in the MultiIDFlag field in the example of the above second structure is true, then the start bit, bit length, offset, and other information corresponding to the first group index number of the multiplexed signal can be obtained according to, for example, the data in the M_signal field in the example of the above second structure. And the first group index number of the multiplexed signal can be obtained by parsing and converting it through a preset parsing algorithm or preset parsing program.

[0102] S305. Based on the first set of index numbers, the second structure and at least one of the first structures are used to parse the signal values ​​of the CAN message to be received.

[0103] Continuing with the example above, the above-mentioned second structure and at least one of the first structures are used to parse the signal value of the CAN message to be received, based on the first group of index numbers. For example, this can involve traversing the signal list information corresponding to the second structure to search for at least one first structure corresponding to the first group of index numbers (for example, the first structure whose value in the m_groupIndex field is the same as the first group of index numbers) to find the start bit, bit length, offset, and other information of the signal. Then, through a preset parsing algorithm or preset parsing program, the start bit, bit length, offset, and other information of the signal corresponding to the at least one first structure are parsed and converted to obtain the physical quantity with practical significance corresponding to the first structure. Finally, the physical quantity with practical significance corresponding to the first structure can be stored in the signal value description information of the first structure in the DBC file, for example, in the Value field.

[0104] Finally, you can also use, for example, encapsulated API functions based on parameters such as CAN channel, signal name, and signal value storage address to match and obtain the above signal value description information, and store it in the signal value parameter of the function.

[0105] It is understood that the above are all possible examples, and the specific examples can be adjusted according to the actual situation, and are not limited to the above.

[0106] In this embodiment, a CAN message to be received is received; the second structure corresponding to the message identifier of the CAN message to be received is determined from the target structure; based on the multiplexing flag information in the second structure, it is determined whether the message identifier corresponding to the CAN message to be received is a multiplexed message identifier; if it is a multiplexed message identifier, the second structure is used to locate the first group index number of the multiplexed signal to which the CAN message to be received belongs; based on the first group index number, the second structure and at least one of the first structures are used to parse the signal value of the CAN message to be received. By traversing the target structure to find a second structure with the same CAN_ID using the CAN_ID of the CAN message to be received, and then determining whether the signal corresponding to the CAN message to be received is a multiplexed signal based on the multiplexing flag information in the second structure, if the signal corresponding to the CAN message to be received is a multiplexed signal, then the first set of index numbers is parsed and obtained, and at least one first structure corresponding to the first set of index numbers is traversed in the signal list information corresponding to the second structure. This realizes the extraction, parsing and conversion of information such as its start bit, bit length, offset, etc. of the signal corresponding to the first structure, and obtains the physical quantity with practical significance corresponding to the signal and stores it in its corresponding signal value description information. This improves the compatibility of the above processing code with different CAN protocols, thereby reducing the development and testing costs related to CAN bus communication and improving efficiency.

[0107] Furthermore, based on the above embodiments, the method may further include:

[0108] If the message identifier is a single signal, then the above-mentioned second structure and at least one of the above-mentioned first structures are used to parse the signal value of the above-mentioned CAN message to be received.

[0109] Continuing with the example above, if the message identifier is a single signal, then the second structure and at least one of the first structures are used to parse the signal value of the CAN message to be received. This means that when the first structure in the signal storage container of the target structure to which the second structure corresponding to the CAN_ID belongs corresponds to a single signal, for example, when the value in the MultiIDFlag field in the example of the second structure is -2, then the first group index number of the multiplexed signal to which the CAN message to be received belongs does not exist. The start bit, bit length, offset and other information of all signals corresponding to the first structure can be directly traversed in the signal list information corresponding to the second structure. And the start bit, bit length, offset and other information of each signal corresponding to the first structure can be parsed and converted by a preset parsing algorithm or preset parsing program to obtain the physical quantity with actual meaning corresponding to each first structure. Finally, the physical quantity with actual meaning corresponding to each first structure can be stored in the signal value description information of the first structure in the DBC file, for example, in the Value field.

[0110] Figure 4 This is a schematic flowchart of a DBC file processing method provided in another embodiment of this application, as shown below. Figure 4 As shown, based on the above embodiments, the above method may further include:

[0111] S401, Obtain the CAN message to be sent.

[0112] For example, the aforementioned CAN message to be sent may refer to the signal value to be sent that has not yet been encoded into a frame of transmitted data. It can be encoded into a frame of transmitted data. The CAN message to be sent can be stored in the local storage space of the transmitting device. The transmitting device may be a device including but not limited to a computer. Of course, the specific storage method of the CAN message to be sent can be selected and determined according to the actual situation, and is not limited here.

[0113] S402. Parse the above-mentioned CAN message to be sent, obtain and set the signal name and signal value corresponding to the above-mentioned CAN message to be sent, and store them in the preset message sending buffer.

[0114] For example, before parsing the CAN message to be sent, obtaining and setting the signal name and signal value corresponding to the CAN message to be sent, and storing them in the preset message sending buffer, a preset message sending buffer corresponding to the CAN message to be sent can be defined first. The specific process of defining the preset message sending buffer corresponding to the CAN message to be sent can be as follows: when the signal corresponding to the CAN message to be sent is a single signal, a preset message sending buffer of, for example, 8 bytes is allocated for each CAN_ID of the CAN message to be sent; when the signal corresponding to the CAN message to be sent is a multiplexed signal, a preset message sending buffer of, for example, 8 bytes is allocated for each multiplexed group of each CAN_ID of the CAN message to be sent, and the group index bit in the above 8 bytes is assigned according to its corresponding multiplexed group index.

[0115] Based on the above, the CAN message to be sent is parsed, and the signal name and signal value to be set are set and stored in the preset message sending buffer by, for example, the first thread calling the encapsulation API function.

[0116] S403. Determine the second structure corresponding to the message identifier of the CAN message to be sent from the DBC structure stored this time.

[0117] For example, the second structure that determines the message identifier of the CAN message to be sent from the DBC structure stored in this instance can refer to, for example, when the second thread detects that the buffer is not empty, retrieving a signal from the buffer, searching for the signal name in the structure corresponding to the signal, and then searching for the CAN_ID in the DBC structure stored in this instance, which is the message identifier of the CAN message to be sent, through the signal name.

[0118] S404. Based on the multiplexing flag information in the second structure, determine whether the message identifier corresponding to the CAN message to be sent is a message identifier for multiplexed signals.

[0119] Continuing with the example above, the determination of whether the message identifier corresponding to the CAN message to be sent is a multiplexed message identifier based on the multiplexing flag information in the second structure can be, for example, by judging whether the message identifier corresponding to the CAN message to be sent is a multiplexed message identifier through the value of the MultiIDFlag field in the second structure.

[0120] S405. If it is a message identifier for multiplexed signals, the second structure described above is used to locate the second group index number of the multiplexed signals to which the CAN message to be sent belongs.

[0121] Continuing with the example above, if the message identifier corresponding to the CAN message to be sent is a message identifier of multiplexed signals, then the multiplexing group index value corresponding to the signal can be obtained by referring to the process in S204 above, and the second group index number of the multiplexing group to which the CAN message to be sent belongs can be located.

[0122] S406. Based on the second set of index numbers, the second structure and at least one first structure are used to encode the signal value of the CAN message to be sent, and the encoded CAN message to be sent is sent.

[0123] Continuing with the example above, the above-mentioned second set of index numbers, using the second structure and at least one first structure, encodes the signal value of the CAN message to be sent and sends the encoded CAN message. For example, it can refer to searching the preset message transmission buffer according to the message identifier corresponding to the CAN message to be sent. After finding the corresponding preset message transmission buffer, it further searches the multiplexing group corresponding to the current signal name and modifies the specified byte of the preset message transmission buffer corresponding to the multiplexing group according to the start bit, bit length, offset and other information of the signal. That is, the above-mentioned signal value encoding of the CAN message to be sent is performed, and finally the encoded CAN message to be sent can be sent through, for example, a CAN driver function.

[0124] It is understood that the steps S401 to S406 above can be completed, for example, in a local DBC file, and the above content are all possible examples. The specific steps can be selected and adjusted according to the actual situation, and are not limited to the above content.

[0125] In this embodiment, a CAN message to be sent is acquired; the CAN message to be sent is parsed to obtain and set the signal name and signal value corresponding to the CAN message to be sent, and store them in a preset message transmission buffer; the second structure corresponding to the message identifier of the CAN message to be sent is determined from the target structure; based on the multiplexing flag information in the second structure, it is determined whether the message identifier corresponding to the CAN message to be sent is a message identifier of multiplexed signals; if it is a message identifier of multiplexed signals, the second structure is used to locate the second group index number of the multiplexed signals to which the CAN message to be sent belongs; based on the second group index number, the second structure and at least one of the first structures are used to encode the signal value of the CAN message to be sent, and the encoded CAN message to be sent is sent. By parsing the signal name and signal value settings corresponding to the CAN message to be sent, and storing them in the preset message transmission buffer, the second structure corresponding to the message identifier of the CAN message to be sent is determined from the stored DBC structure. This allows for the determination of whether the message identifier is a multiplexed message identifier. If it is, the second structure is used to locate the second set of index numbers for the multiplexed signal to which the CAN message to be sent belongs. Based on the second set of index numbers, the second structure and at least one first structure are used to encode the signal value of the CAN message to be sent, and then the encoded CAN message is sent. This improves the compatibility of the processing code with different CAN protocols, thereby reducing the development and testing costs related to CAN bus communication and improving efficiency.

[0126] Furthermore, based on the above embodiments, the method may further include:

[0127] If the message identifier is a single signal, the above-mentioned second structure and at least one of the above-mentioned first structures are used to encode the signal value of the above-mentioned CAN message to be sent, and the encoded above-mentioned CAN message to be sent is sent.

[0128] For example, if the above is a message identifier for a single signal, then the above-mentioned second structure and at least one of the above-mentioned first structures are used to encode the signal value of the CAN message to be sent, and the encoded CAN message to be sent is sent. For example, when the message identifier corresponding to the CAN message to be sent is a message identifier for a single signal, then it is not necessary to further obtain the above-mentioned second set of index numbers. The above-mentioned preset message sending buffer can be searched according to the message identifier corresponding to the CAN message to be sent. After the corresponding preset message sending buffer is found, the specified byte of the preset message sending buffer is directly modified according to the start bit, bit length, offset and other information of the signal. That is, the above-mentioned signal value encoding of the CAN message to be sent is performed. Finally, the above-mentioned encoded CAN message to be sent can be sent through, for example, a CAN driver function. It can be understood that the above content can also be completed in, for example, a local DBC file.

[0129] Of course, the above are just possible examples, and the specific content can be determined and adjusted according to the actual situation, without any restrictions.

[0130] Figure 5 This is a schematic diagram of a DBC file processing device provided in an embodiment of this application. This DBC file processing device can execute the aforementioned DBC file processing method to receive or send CAN messages in a DBC file. This device can be integrated into the aforementioned computer or other equipment, such as... Figure 5 As shown, the device includes:

[0131] The acquisition module 510 is used to acquire the CAN database DBC file of the controller area network CAN bus. The DBC file is used to describe the protocol messages of the CAN bus.

[0132] The parsing module 520 is used to obtain CAN messages through the aforementioned DBC file and parse the aforementioned CAN messages to obtain message identifiers and signal description information. The aforementioned signal description information includes: signal name and basic description information.

[0133] The determination module 530 is used to determine the additional description information based on the above message identifier and the above signal description information;

[0134] The creation module 540 is used to store the above message identifier, the above basic description information and the above additional description information into the created target structure. The target structure is used to parse the received CAN message or to encode the above CAN message to be sent.

[0135] The DBC file processing method provided in this application includes: obtaining a CAN database DBC file of a controller area network (CAN) bus, wherein the DBC file is used to describe the protocol messages of the CAN bus; obtaining CAN messages through the DBC file and parsing the CAN messages to obtain message identifiers and signal description information, wherein the signal description information includes a signal name and basic description information; determining additional description information based on the message identifiers and the signal description information; and storing the message identifiers, the basic description information, and the additional description information into a created target structure, wherein the target structure is used to parse received CAN messages or encode CAN messages to be sent. In this embodiment, a specific method is implemented by running processing code. CAN messages are obtained through a DBC file, parsed to obtain message identifiers and signal description information, and additional description information is determined based on these identifiers and information. The message identifier, basic description information, and additional description information are then stored in a created target structure. This target structure is used to parse received CAN messages or encode CAN messages to be sent. This allows for the creation of a target structure stored in a DBC file that is compatible with sending and receiving CAN messages and multiplexing signals, all using only one set of processing code. This structure can be used for subsequent CAN message transmission and reception without modifying the processing code. Different CAN protocols can be received, parsed, encoded, and transmitted by importing the DBC file, thus improving the compatibility of the processing code with different CAN protocols, reducing the development and testing costs related to CAN bus communication, and improving efficiency.

[0136] Optionally, the signal description information includes: the signal name of at least one signal and the basic description information of each signal, and the additional description information includes: the additional description information of at least one signal.

[0137] The aforementioned determining module 430 is specifically used to determine the aforementioned additional description information of each signal based on the aforementioned message identifier and the aforementioned signal description information of at least one signal;

[0138] The added descriptive information includes: group index value, signal value description information, message value description information, signal storage order information, signal transmission time interval information, and signal reception timestamp information.

[0139] Optionally, the target structure mentioned above includes: at least one first structure and a second structure;

[0140] The creation module 440 can also be used to create at least one of the first structures, storing the signal name, basic description information, and additional description information of at least one signal into at least one corresponding first structure; and to create the second structure, storing the signal list information, group index signal information, multiplexing flag information, message identifier, message name description information, message frame type, and message sending node description information of at least one signal into the second structure.

[0141] Optionally, the above apparatus may further include: a receiving module, configured to receive a CAN message to be received; determine from the target structure the second structure corresponding to the message identifier of the CAN message to be received; determine, based on the multiplexing flag information in the second structure, whether the message identifier corresponding to the CAN message to be received is a multiplexed message identifier; if it is a multiplexed message identifier, then use the second structure to locate the first group index number of the multiplexed signal to which the CAN message to be received belongs; and based on the first group index number, use the second structure and at least one of the first structures to perform signal value parsing on the CAN message to be received.

[0142] Optionally, the receiving module can also be used to parse the signal value of the CAN message to be received by employing the second structure and at least one of the first structures if the message identifier is a separate signal.

[0143] Optionally, the above apparatus may further include: a transmitting module, configured to acquire a CAN message to be transmitted; parse the CAN message to be transmitted to obtain and set the signal name and signal value corresponding to the CAN message to be transmitted to a preset message transmission buffer; determine the second structure corresponding to the message identifier of the CAN message to be transmitted from the target structure; determine whether the message identifier corresponding to the CAN message to be transmitted is a message identifier of multiplexed signals according to the multiplexing flag information in the second structure; if it is a message identifier of multiplexed signals, then use the second structure to locate the second group index number of the multiplexed signals to which the CAN message to be transmitted belongs; and encode the signal value of the CAN message to be transmitted using the second structure and at least one of the first structures according to the second group index number, and transmit the encoded CAN message to be transmitted.

[0144] Optionally, the above-mentioned sending module can also be used to encode the signal value of the CAN message to be sent using the second structure and at least one of the first structures if the message identifier is a single signal, and then send the encoded CAN message to be sent.

[0145] The above-described device is used to execute the method provided in the foregoing embodiments, and its implementation principle and technical effect are similar, so they will not be described again here.

[0146] Figure 6 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. The communication device can be the aforementioned computer or other similar equipment. Figure 6 As shown, the device 600 includes:

[0147] The processor 610, storage medium 620, and bus 630 are connected in communication via bus 630.

[0148] The storage medium 620 stores machine-readable instructions that can be executed by the processor 610. When the communication device is running, the processor 610 executes the machine-readable instructions to perform the DBC file processing method.

[0149] It should be understood that, Figure 6 The structure shown is only a schematic diagram of the communication device; the communication device may also include components that are larger than those shown. Figure 6 The more or fewer components shown, or having the same Figure 6 The different configurations shown. Figure 6 The components shown can be implemented using hardware, software, or a combination thereof.

[0150] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the DBC file processing method described in the above method embodiments.

[0151] Computer-readable storage media can be electronic storage devices such as flash memory, EEPROM (Electrically Erasable Programmable Read-Only Memory), EPROM, hard disk, or ROM. Optionally, computer-readable storage media includes non-transitory computer-readable storage medium. The computer-readable storage medium has storage space for program code that performs any of the method steps described above. This program code can be read from or written to one or more computer program products. The program code can be compressed, for example, in a suitable form.

[0152] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can also be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0153] In addition, the functional modules in the various embodiments of this application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0154] If a function is implemented as a software module 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 this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0155] The above description is merely a preferred embodiment of this application and does not limit the scope of the patent application. Any equivalent structural transformations made based on the inventive concept of this application and the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included within the scope of patent protection of this application.

Claims

1. A DBC file processing method, characterized in that, The method includes: Obtain the CAN database DBC file of the CAN bus of the controller area network, wherein the DBC file is used to describe the protocol messages of the CAN bus; The CAN message is obtained through the DBC file, and the CAN message is parsed to obtain the message identifier and signal description information; Based on the message identifier and the signal description information, determine to add description information; The message identifier, basic description information, and additional description information are stored in the created target structure. The target structure is used to parse the received CAN message or encode the CAN message to be sent. The basic description information is the content indicated by the identifier of the CAN bus protocol message; The signal description information includes: the signal name of at least one signal and the basic description information of each signal; the additional description information includes: the additional description information of at least one signal. The step of determining to add description information based on the message identifier and the signal description information includes: Based on the message identifier and the signal description information of at least one signal, the additional description information of each signal is determined respectively; The added description information includes: group index value, signal value description information, message value description information, signal storage order information, signal transmission time interval information, and signal reception timestamp information; The target structure includes: at least one first structure and a second structure; The method further includes: Create at least one of the first structures and store the signal name, the basic description information, and the additional description information of at least one signal into at least one corresponding first structure; The second structure is created, and the signal list information, group index signal information, multiplexing flag information, message identifier, message name description information, message frame type and message sending node description information of at least one signal are stored in the second structure.

2. The method according to claim 1, characterized in that, The method further includes: Receive CAN messages to be received; Determine the second structure corresponding to the message identifier of the CAN message to be received from the target structure; Based on the multiplexing flag information in the second structure, determine whether the message identifier corresponding to the CAN message to be received is a message identifier of multiplexed signals; If it is a message identifier for multiplexed signals, then the second structure is used to locate the first group index number of the multiplexed signals to which the CAN message to be received belongs; Based on the first set of index numbers, the second structure and at least one of the first structures are used to parse the signal values ​​of the CAN message to be received.

3. The method according to claim 2, characterized in that, The method further includes: If the message identifier is a single signal, then the second structure and at least one of the first structures are used to parse the signal value of the CAN message to be received.

4. The method according to claim 1, characterized in that, The method further includes: Obtain the CAN message to be sent; The CAN message to be sent is parsed to obtain and set the signal name and signal value corresponding to the CAN message to be sent, and then stored in the preset message sending buffer. Determine the second structure corresponding to the message identifier of the CAN message to be sent from the target structure; Based on the multiplexing flag information in the second structure, determine whether the message identifier corresponding to the CAN message to be sent is a message identifier of multiplexed signals; If it is a message identifier for multiplexed signals, then the second structure is used to locate the second group index number of the multiplexed signals to which the CAN message to be sent belongs; Based on the second set of index numbers, the second structure and at least one of the first structures are used to encode the signal value of the CAN message to be sent, and the encoded CAN message to be sent is then sent.

5. The method according to claim 4, characterized in that, The method further includes: If the message identifier is a single signal, then the second structure and at least one of the first structures are used to encode the signal value of the CAN message to be sent, and the encoded CAN message to be sent is sent.

6. A DBC file processing device, characterized in that, include: The acquisition module is used to acquire the CAN database DBC file of the CAN bus of the controller area network, wherein the DBC file is used to describe the protocol messages of the CAN bus; The parsing module is used to obtain CAN messages through the DBC file and parse the CAN messages to obtain message identifiers and signal description information; The determining module is used to determine the addition of description information based on the message identifier and the signal description information; A creation module is used to store the message identifier, basic description information, and additional description information into a created target structure. The target structure is used to parse the received CAN message or encode the CAN message to be sent. The basic description information is the content indicated by the identifier of the CAN bus protocol message; The signal description information includes: the signal name of at least one signal and the basic description information of each signal; the additional description information includes: the additional description information of at least one signal. The determining module is specifically used to determine the additional description information of each signal based on the message identifier and the signal description information of at least one signal; wherein, the additional description information includes: group index value, signal value description information, message value description information, signal storage order information, signal transmission time interval information, and signal reception timestamp information; The target structure includes: at least one first structure and a second structure; The creation module is further configured to create at least one of the first structures, storing the signal name, basic description information, and additional description information of at least one signal into at least one corresponding first structure; and to create a second structure, storing the signal list information, group index signal information, multiplexing flag information, message identifier, message name description information, message frame type, and message sending node description information of at least one signal into the second structure.

7. A communication device, characterized in that, include: A processor, a storage medium, and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the method as described in any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the method as described in any one of claims 1-5.

Images