Method for transmitting and receiving FDC information on DTC and battery system using same

Abstract

The present disclosure relates to a method for transmitting and receiving fault detection counter (FDC) information for diagnosing a problem code (DTC) and a battery system using the same. According to an exemplary embodiment of the present disclosure, a method for transmitting and receiving FDC information for DTC by a battery system includes: receiving a request message; and transmitting a response message corresponding to the request message, in which a data information region of the request message includes a data separator of a first type for requesting reading of an FDC corresponding to each of the at least one piece of DTC information included in the request message and diagnostic information data of a second type for requesting reading of the FDC corresponding to each of the at least one piece of DTC information included in the request message. Or a second type for reading the plurality of FDCs according to a bitmap request, and the bitmap is a list in which the plurality of pieces of DTC diagnostic information match the plurality of bits constituting the diagnostic information data.

Description

Technical Field

[0001] Cross - Reference to Related Applications

[0002] This application claims priority and the benefit of Korean Patent Application No. 10 - 2023 - 0092579, filed with the Korean Intellectual Property Office on July 17, 2023, the entire content of which is incorporated herein by reference.

[0003] The present disclosure relates to a method for transmitting and receiving fault detection counter (FDC) information for diagnostic trouble codes (DTCs) and a battery system using the method. Background Art

[0004] According to the ISO - 14229 standard protocol definition, a response to a diagnostic trouble code (DTC) status request can express a fault status diagnosed by a fault detection counter (FDC).

[0005] Meanwhile, recently, there has been a need for diagnostic information for checking thermal events or isolation events regarding a battery to read and check multiple states simultaneously at a specific time point. Summary of the Invention

[0006]

Technical Problem

[0007] The present disclosure attempts to provide a method for transmitting and receiving fault detection counter (FDC) information for diagnostic trouble codes (DTCs), which can express multiple DTCs and their corresponding FDCs in one message, and a battery system using the method.

[0008]

Technical Solution

[0009] An exemplary embodiment of the present disclosure provides a method for a battery system to transmit and receive fault detection counter (FDC) information for diagnostic trouble codes (DTCs), the method including: receiving a request message; and transmitting a response message corresponding to the request message, wherein a data information area of the request message includes a data delimiter and diagnostic information data, the data delimiter is a first type for requesting to read an FDC corresponding to each of at least one DTC information included in the request message, or a second type for requesting to read multiple FDCs according to a bitmap, and the bitmap is a list in which multiple DTC diagnostic information matches multiple bits constituting the diagnostic information data.

[0010] If the data delimiter is the second type, the diagnostic information data may include binary data in which a binary value corresponds to each of the multiple bits, and bits having a first value among the binary data may match multiple first DTCs based on the bitmap.

[0011] The data information area of the response message may include a plurality of FDCs corresponding to a plurality of first DTCs.

[0012] If, based on a bitmap, the plurality of first DTCs include a DTC matching a first bit and a DTC matching a second bit greater than the first bit, the data information area of the response message may include an FDC corresponding to the DTC matching the first bit and an FDC corresponding to the DTC matching the second bit arranged in order in the data information area.

[0013] If the response message is of the first type, the diagnostic information data may include first DTC information and second DTC information.

[0014] The data information area of the response message may be configured by arranging the first DTC information, the FDC corresponding to the first DTC information, the second DTC information, and the FDC corresponding to the second DTC information in order.

[0015] Another exemplary embodiment of the present disclosure provides a battery system for sending fault detection counter (FDC) information for diagnostic trouble codes (DTCs) to a vehicle and receiving fault detection counter (FDC) information for diagnostic trouble codes (DTCs) from the vehicle. The battery system includes: a battery pack including a plurality of battery cells; and a battery management system (BMS) configured to manage the battery pack. The BMS receives a request message from the vehicle and sends a response message corresponding to the request message. The data information area of the request message includes a data separator and diagnostic information data. The data separator is of a first type for requesting to read the FDC corresponding to each of at least one DTC information included in the request message, or of a second type for requesting to read a plurality of FDCs according to a bitmap. The bitmap is a list in which multiple DTC diagnostic information matches multiple bits constituting the diagnostic information data.

[0016] If the data separator is of the second type, the diagnostic information data may include binary data in which the binary value corresponds to each of the multiple bits. Among the multiple bits represented by the binary data, multiple first bits that match the multiple DTC diagnostic information read based on the bitmap may have a first value, and other multiple bits excluding the multiple first bits may have a second value.

[0017] The data information area of the response message may include a plurality of FDCs corresponding to a plurality of first DTCs.

[0018] If, based on a bitmap, a plurality of first DTCs include a DTC that matches a first bit and a DTC that matches a second bit greater than the first bit, the BMS may configure the data information area of the response message by arranging in sequence the FDCs corresponding to the DTCs that match the first bit and the FDCs corresponding to the DTCs that match the second bit.

[0019] If the response message is of the first type, the diagnostic information data may include first DTC information and second DTC information.

[0020] The BMS may configure the data information area of the response message by arranging in sequence the first DTC information, the FDCs corresponding to the first DTC information, the second DTC information, and the FDCs corresponding to the second DTC information.

[0021]

Beneficial Effects

[0022] According to the present disclosure, the request message uses a bitmap of multiple DTC information to request DTC information, and the response message thereto includes all of the multiple diagnostic information according to the bitmap, so that a small amount of data can be used when diagnosing the FDC information corresponding to multiple DTCs.

[0023] According to the present disclosure, in the case of using the CAN FD channel, as much data as the DLC can be transmitted, so that the data buffer can be used flexibly.

[0024] If the response message includes one FDC corresponding to each DTC, it may be difficult to accurately diagnose the vehicle due to the time interval between the times when the corresponding response message packets are received. According to the present disclosure, since the response message includes multiple FDC information, multiple pieces of data indicating the vehicle state at a specific time point can be checked at once for diagnosis. Brief Description of the Drawings

[0025] Figure 1 illustrates a vehicle and a battery system to which an exemplary embodiment is applied.

[0026] Figure 2 is a diagram illustrating a partial configuration of a vehicle according to an exemplary embodiment.

[0027] Figure 3 is a diagram illustrating a partial configuration of a battery system according to an exemplary embodiment.

[0028] Figure 4 is a diagram illustrating the structure of a request message using a bitmap according to an exemplary embodiment.

[0029] Figure 5 is a diagram illustrating Figure 4 the structure of the data information area.

[0030] Figure 6 is an example showing a bitmap of bits corresponding to a plurality of DTCs according to an exemplary embodiment.

[0031] Figure 7 is a diagram showing the structure of a response message using a bitmap according to an exemplary embodiment.

[0032] Figure 8 is a diagram showing the structure of a request message not using a bitmap according to an exemplary embodiment.

[0033] Figure 9 is a diagram showing Figure 8 the structure of a data information area.

[0034] Figure 10 is a diagram showing the structure of a response message not in use according to an exemplary embodiment. Detailed Description

[0035] Hereinafter, exemplary embodiments will be described in detail with reference to the accompanying drawings, and the same or similar components will be given the same or similar reference numerals, and their repeated description will be omitted. The suffixes “module” and / or “unit” of the components used in the following description are assigned or mixed for the convenience of writing the specification, and they do not have a unique meaning or function by themselves. In addition, when the detailed description of related known technologies obscures the gist of the exemplary embodiments disclosed herein, they will be omitted. Furthermore, the drawings are provided only to help easily understand the exemplary embodiments disclosed herein, and it should be understood that the technical idea disclosed herein is not limited by the drawings, and covers all modifications, equivalents, and alternatives falling within the spirit and scope of the present disclosure.

[0036] Terms including ordinal numbers such as “first” and “second” may be used to describe various components, but these components are not limited by these terms. These terms are only used for the purpose of distinguishing one component from another.

[0037] It should be understood that when a component is referred to as being “connected to” or “coupled to” another component, a component can be directly connected to or coupled to another component, or connected to or coupled to another component through an intermediate component therebetween. On the other hand, it should be understood that when a component is referred to as being “directly connected to” or “directly coupled to” another component, a component can be connected to another component without an intermediate component therebetween.

[0038] It should be understood that the terms “comprising,” “having,” etc. used herein specify the presence of the features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, but do not exclude the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

[0039] Figure 1 The figure shows a vehicle and a battery system to which an exemplary embodiment is applied.

[0040] The vehicle 10 may send a request message to the battery system 20 to obtain diagnostic trouble code (DTC) related information (hereinafter referred to as DTC information) (S10).

[0041] The battery system 20 may receive the request message, generate a response message for the request message, and send the response message to the vehicle 10 (S20).

[0042] In Figure 1 the vehicle and the battery system are illustrated as an example of a diagnostic device and a diagnostic target for sending and receiving messages, but the present disclosure is not limited thereto. The exemplary embodiment may be applied to a device capable of diagnosing a battery and storing information on the result of performing the diagnosis, such as a battery system.

[0043] Figure 2 The figure illustrates a partial configuration of a vehicle according to an exemplary embodiment.

[0044] As Figure 2 illustrated, the vehicle 10 may include an electronic control unit (ECU) 100, a communication unit 110, and a memory 120.

[0045] The ECU 100 may generate a request message, collect necessary data from the received response message, and perform a series of operations for controlling the operation of the vehicle 10. The request message may be a message requesting information on DTCs belonging to a specific DTC status and a fault detection counter FDC corresponding to the DTCs.

[0046] The communication unit 110 may send a request message to the outside and receive a response message for the request message. For example, the communication unit 110 may send a request message to the battery system 20 and receive a response message from the battery system 20.

[0047] The memory 120 may store the data collected by the controller 100 from the response message. The memory 120 may store data required for the controller 100 to control operations for generating a request message, the operation of the vehicle 10, and so on.

[0048] Figure 3 The figure illustrates a partial configuration of a battery system according to an exemplary embodiment.

[0049] As Figure 3As shown in the figure, the battery system 20 may include: a battery pack 300 including a plurality of battery cells; and a battery management system (BMS) 310 that manages the battery pack by performing operations such as charging / discharging, monitoring, and protecting the battery pack 300. The BMS 310 may include a main control unit (MCU) 200, a communication unit 210, and a memory 220.

[0050] The MCU 200 performs diagnostics according to the received request message, generates a response message based on the diagnostic result, and performs a series of operations for controlling the operations of the BMS 20.

[0051] The communication unit 210 receives the request message and sends the response message to the outside. For example, the communication unit 210 may receive the request message from the vehicle 10 and send the response message to the vehicle 10.

[0052] The memory 220 stores the diagnostic content and the result according to the performed diagnostics. The MCU 200 may detect and read the necessary information from the memory 220 to generate the response message. The memory 220 may store the data necessary for the MCU 200 to control the BMS 20.

[0053] Figure 2 and Figure 3 Only the configurations necessary for describing the exemplary embodiments are illustrated. Figure 2 and Figure 3 The configurations not illustrated in may be included in the vehicle and the battery system.

[0054] Figure 4 is a diagram illustrating the structure of a request message using a bitmap according to an exemplary embodiment.

[0055] As Figure 4 shown in the figure, the request message 11 may include a packet size information area 111, a packet identification information area 112, and a data information area 113. Figure 4 The numbers shown in the figure may be hexadecimal, expressed as 1 byte, and shown as Figure 4 The size of one unit of data in may be 1 byte.

[0056] The packet size information area 111 may include a data length code (DLC). The DLC may define the size obtained by adding the amount of data in the packet identification information area 112 of the request message and the amount of data in the data information area 113. For example, as Figure 4 shown in the figure, the "0x05" recorded in byte number 1 of the packet size information area 111 may indicate that the size obtained by adding the amount of data in the packet identification information area 112 and the amount of data in the data information area 113 is 5 bytes.

[0057] The packet identification information area 112 may correspond to an area of 2 bytes or more. The Service ID may be recorded in the first byte of the packet identification information area 112, and the Data ID may be recorded in the second byte of the packet identification information area 112.

[0058] As Figure 4 illustrated, "0x19" recorded in byte number 2 of the packet identification information area 112 may be an example of the Service ID of the service that requests to read DTC information. That is, if the Service ID is "0x19", the message may be a message of the service that requests the ECU 100 to read the DTC information stored in the BMS 310. According to this request, the BMS 310 may read the stored DTC information and send the read DTC information to the ECU 100. At this time, the BMS 310 needs information to specify which one of the multiple stored DTC information to read.

[0059] As Figure 4 illustrated, "0x06" recorded in byte number 3 of the packet identification information area 112 may be an example of the Data ID of the FDC data corresponding to the DTC. That is, if the Data ID in the request message is "0x06", the request message may be a message that the ECU 100 requests the FDC data among the DTC information stored in the BMS 310. According to this request, the BMS 310 may read the FDC of the stored DTC and send the read FDC to the ECU 100.

[0060] The data information area 113 may correspond to multiple bytes starting from byte number 4. Although Figure 4 illustrates that the data information area 113 is an area corresponding to 3 bytes - byte numbers 4, 5, and 6 - this is for convenience of explanation, and the exemplary embodiment is not limited thereto.

[0061] Figure 5 is a diagram Figure 4 illustrating the structure of the data information area.

[0062] Referring to Figure 5 , the data information area 113 corresponds to multiple bytes, and the bits constituting each byte of the multiple bytes may include values for specifying the DTC requested to be read.

[0063] Figure 5 The numbers illustrated in Figure 5 may be binary and expressed as 1 bit, and the size of one unit of data illustrated as

[0064] As Figure 5 As shown, in the following description, it will be assumed that the data information area 113 is a 3-byte area.

[0065] The data information area 113 may include request data 1130 that can specify the DTC to be read. The request data 1130 may be binary data sorted and arranged in descending order of bits in the data information area 113. As Figure 5 shown, the 24-bit binary data "1100000000000000 00001011" from the data corresponding to bit number 23 to the data corresponding to bit number 0 may be an example of the request data 1130.

[0066] Referring to Figure 5 , the request data 1130 may include a communication channel identifier 1131, a response type identifier 1132, and data information 1133.

[0067] The communication channel identifier 1131 may specify the communication channel for receiving the response message. The communication channel for receiving the response message may be one of multiple communication channels. The multiple communication channels may include a first communication channel and a second communication channel.

[0068] The first communication channel may be a communication channel that sets the maximum data volume that can be sent to a predetermined first reference volume. The second communication channel may be a communication channel that sets the maximum data volume that can be sent to a predetermined second reference volume greater than the first reference volume.

[0069] Specifically, the first communication channel may be a channel that sets the total amount of message packet data that can be sent at one time to be less than the total amount of message packet data that can be sent at one time by the second communication channel. For example, the first communication channel may be a CAN communication channel, and the second communication channel may be a CAN FD channel.

[0070] The CAN FD channel is a communication standard developed to make up for the deficiencies of the CAN channel and is a communication channel whose maximum data volume that can be included is greater than the maximum data volume of the CAN channel. For example, if the maximum data volume that can be included in a packet sent through the CAN channel is 8 bytes, the maximum data volume that can be included in a packet sent through the CAN FD channel may be 64 bytes.

[0071] For example, as Figure 5 shown, the "1" recorded in bit number 23 representing the communication channel identifier 1131 may indicate that the communication channel for the request message 11 is the second communication channel.

[0072] The response type identifier 1132 may specify the requested data delimiter. The data delimiter may be one of multiple types. The multiple types may include a first type and a second type.

[0073] The first type may be a type that requests to read the FDC corresponding to each of at least one DTC information included in the request message without using a bitmap. The second type may be a type that requests to read the FDC corresponding to each DTC among multiple DTCs indicated by multiple bits indicated in the request message according to a bitmap. Here, the bitmap may be a list in which multiple DTC diagnostic information matches multiple bits. The DTC diagnostic information may include DTC information, a diagnostic name indicated by the DTC information, and the like.

[0074] For example, as Figure 5 illustrated, a "1" recorded in bit number 22 representing the response type identifier 1132 may indicate that the data delimiter is of the second type.

[0075] Although Figure 5 illustrates that each of the communication channel identifier 1131 and the response type identifier 1132 is a binary number corresponding to 1 bit, this is only for convenience of explanation and the present disclosure is not limited thereto. Each of the communication channel identifier 1131 and the response type identifier 1132 is a hexadecimal number corresponding to 1 byte.

[0076] Hereinafter, a case where the data delimiter is of the second type will be described with reference to Figures 5 to 7 .

[0077] Referring to Figure 5 , when the data delimiter is of the second type, the data information 1333 may include diagnostic information data included in multiple bits. The diagnostic information data may be binary data in which binary values correspond to each of the multiple bits. The diagnostic information data may include multiple DTCs requested to be read.

[0078] Among the multiple bits represented by the diagnostic information data, bits having a first value (for example, "1") may match multiple DTC information requested to be read based on the bitmap. In addition, among the multiple bits represented by the diagnostic information data, the remaining bits excluding the bits that match the multiple DTC information requested to be read may have a second value (for example, "0").

[0079] Figure 6 is an example of a bitmap indicating multiple bits corresponding to multiple DTCs according to an exemplary embodiment.

[0080] The multiple bits included in the bitmap may be sorted in ascending or descending order, and each of the bits may match to correspond to one of the multiple DTCs.

[0081] Refer to Figure 6 , the bitmap can be a list in which the numbers of each bit, DTCs, and the names of the diagnoses indicated by the DTCs (DTC names) represented by the diagnostic information data match each other. Multiple DTC diagnostic information indicated by multiple DTC information can correspond to multiple bits. As Figure 6 shown, "OA0001" to "OA0008", "0B0B00", "0B3C01" to "0B3C06", and "0C0A00" to "0C0A06" can be examples of multiple DTCs.

[0082] Hereinafter, an example of the bitmap shown Figure 6 will be described.

[0083] Bit number 0 may match the DTC "0A0001" representing the diagnostic name "DTC module error #1", and bit number 1 may match the DTC "0A0002" representing the diagnostic name "DTC module error #2". Bit number 2 may match the DTC "0A0003" representing the diagnostic name "DTC module error #3", and bit number 3 may match the DTC "0A0004" representing the diagnostic name "DTC module error #4". Bit number 4 may match the DTC "0A0005" representing the diagnostic name "DTC module error #5", and bit number 5 may match the DTC "0A0006" representing the diagnostic name "DTC module error #6". Bit number 6 may match the DTC "0A0007" representing the diagnostic name "DTC module error #7", and bit number 7 may match the DTC "0A0008" representing the diagnostic name "DTC module error #8". Among the diagnostic names, the name including "DTC module error" may indicate a predetermined error that has occurred in each of the multiple modules included in the battery pack 300.

[0084] Bit number 8 may match the DTC "0B0B00" representing the diagnostic name "DTC single cell error #1", and bit number 9 may match the DTC "0B3C01" representing the diagnostic name "DTC single cell error #2". Bit number 10 may match the DTC "0B3C02" representing the diagnostic name "DTC single cell error #3", and bit number 11 may match the DTC "0B3C03" representing the diagnostic name "DT single cell error #4". Bit number 12 may match the DTC "0B3C04" representing the diagnostic name "DTC single cell error #5", bit number 13 may match the DTC "0B3C05" representing the diagnostic name "DTC single cell error #6", and bit number 14 may match the DTC "0B3C06" representing the diagnostic name "DTC single cell error #7". Among the diagnostic names, names including "DTC single cell error" may indicate a predetermined error that has occurred in each of the plurality of battery cells included in the battery pack 300.

[0085] Bit number 15 may match the DTC "0C0A00" representing the diagnostic name "DTC_CELL_SENSE_OPEN", and bit number 16 may match the DTC "0C0A01" representing the diagnostic name "DTC_CELL_SENSE_OPEN". Bit number 17 may match the DTC "0C0A02" representing the diagnostic name "DTC_CELL_SENSE_OPEN", and bit number 18 may match the DTC "0C0A03" representing the diagnostic name "DTC_CELL_SENSE_OPEN". Bit number 19 may match the DTC "0C0A04" representing the diagnostic name "DTC_CELL_SENSE_OPEN", bit number 20 may match the DTC "0C0A05" representing the diagnostic name "DTC_CELL_SENSE_OPEN", and bit number 21 may match the DTC "0C0A06" representing the diagnostic name "DTC_CELL_SENSE_OPEN". Among the diagnostic names, names including "DTC_CELL_SENSE_OPEN" may indicate a predetermined error that occurs when detecting cell information (such as cell voltage, cell temperature, cell current, etc.) of each of the plurality of battery cells included in the battery pack 300.

[0086] Each of the multiple DTC diagnostic information indicated by the bit map may indicate the battery conditions of each of the plurality of battery cells included in the battery pack 300 and / or each of the plurality of battery modules included in the battery pack 300, such as temperature, voltage, isolation error, communication error, and abnormal operation.

[0087] Thus, each bit constituting the diagnostic information data may correspond to a bit number according to the bitmap. Figure 5 In the data information 1133 shown in the figure, bit number 21 to bit number 0 can be Figure 6 The bit number 21 to the bit number 0 of the illustrated bit map correspond. Figure 5 In the data information 1133 shown in the figure, Figure 6 Data corresponding to DTC “0C0A06” of bit number 21 of the illustrated bit map may be recorded in bit number 21 .

[0088] The value recorded in each of bit number 21 to bit number 0 of the diagnostic information data may be a first value (e.g., "1") or a second value (e.g., "0"). Among them, a DTC matching a bit recording a first value according to the bit map may indicate a DTC requested to be read by the request message 11.

[0089] because Figure 5 The data of bit numbers 0, 1, and 3 of the data information 1133 shown in the figure are "1", and the data of other bit numbers are "0", then the request message 11 including the data information 1133 indicates that the request to read the data related to Figure 6 The bit numbers 0, 1 and 3 of the bit map illustrated in FIG. 4 match the states of DTCs “0A0001”, “0A0002” and “0A0004”.

[0090] In an exemplary embodiment, the request message 11 may request a plurality of DTC information in one data packet using a bitmap, and the length of the data information area 113 may be increased or decreased according to the number of bits indicated by the bitmap.

[0091] In a method that does not use a bitmap, the request message may include at least one DTC in a packet and may require at least a 3-byte area for each of the at least one DTC. Therefore, a request message for requesting information about five DTCs may require five packets, each including one DTC, or may require at least 3*5=15 bytes of area, including five DTCs in one packet.

[0092] In contrast, in an exemplary embodiment using a bitmap, the size of the data information area 113 can be reduced because the DTC can be specified by switching bits predefined by the bitmap without including the DTC itself in the message.

[0093] In an exemplary embodiment, if the bitmap is indicative of a number greater than and less than or equal to For a list of bits for DTC matching, a data information area 113 of length m bytes is sufficient. However, this is for the case where each of the communication channel identifier 1131 and the response type identifier 1132 is a binary number corresponding to 1 bit. If the communication channel identifier 1131 and the response type identifier 1132 are k bits, and the bitmap is a list of bits indicating DTC matches greater than and less than or equal to then the request message 11 may require a data information area 113 of m bytes. Here, m is a natural number greater than or equal to 2, and k is a natural number greater than or equal to 1.

[0094] For example, if the bitmap is a list of 35 DTC diagnostic messages, each message matching 1 bit, the request message 11 may require a data information area 113 of 5 bytes.

[0095] Figure 7 FIG. is a diagram showing the structure of a response message using a bitmap according to an exemplary embodiment.

[0096] As Figure 7 shown, the response message 12 may include a packet size information area 121, a packet identification information area 122, and a data information area 123. Figure 7 The numbers shown may be hexadecimal, expressed as 1 byte, and shown as Figure 7 The size of one unit of data may be 1 byte.

[0097] The packet size information area 121 may include a data length code (DLC). The DLC may define the size obtained by adding the data amount of the packet identification information area 122 of the request message and the data amount of the data information area 123. For example, as Figure 6 shown, "0x05" recorded in byte number 1 of the packet size information area 121 may indicate that the size obtained by adding the data amount of the packet identification information area 122 and the data amount of the data information area 123 is 5 bytes.

[0098] The packet identification information area 122 may correspond to an area of 2 bytes or more, and a service identifier (ServiceID) may be recorded in the first byte of the packet identification information area 122, and a data identifier (Data ID) may be recorded in the second byte of the packet identification information area 122.

[0099] As Figure 7As shown, the "0x59" recorded in byte number 2 of the grouping identification information area 112 can be an example of a service identifier (DTC read information positive response service ID) indicating a response including DTC information. That is, if the service identifier is "0x59", then this message may be a message in which the ECU 100 responds with the DTC information stored in the BMS 310.

[0100] As Figure 7 As shown, the "0x06" recorded in byte number 3 of the grouping identification information area 122 can be an example of a data identifier (FDC read service ID) for requesting FDC data corresponding to a DTC. That is, if the data identifier in the response message is "0x06", then this message may be a message indicating the FDC data among the DTC information stored in the BMS 310.

[0101] When the number of DTC information requested to be read in the request message 11 is n (n is a natural number greater than or equal to 2), the data information area 123 can correspond to an area of n bytes.

[0102] For example, if the first bit and the second bit among the multiple bits included in the data information area 113 of the request message 11 are "1" and the other bits are "0", then the BMS 310 can configure the response message 12 in such a way that among the multiple bytes included in the data information area 123, the first byte includes the FDC corresponding to the DTC that matches the first bit, and the second byte includes the FDC corresponding to the DTC that matches the second bit. Here, if the second bit is greater than the first bit, the BMS 310 can configure the data information area 123 by arranging the first byte and the second byte in order.

[0103] Refer to Figure 7 , and a description will be made on the basis of assuming that n is 3. The BMS 310 can configure the data information area 123 by arranging n FDCs in order for n DTCs.

[0104] Each of the n bytes included in the data information area 123 can include the FDC of the corresponding DTC information among the n DTC information requested to be read in the request message 11.

[0105] The MCU 200 can sort the n DTC information in ascending order of the number of matching bits based on the bitmap, and arrange the FDCs of each DTC information in order in the n bytes of the data information area 113.

[0106] It can be assumed that the n DTC messages include a first DTC, a second DTC, and a third DTC, and the first DTC matches a first bit (e.g., bit number 0) based on a bitmap, the second DTC matches a second bit greater than the first bit (e.g., bit number 1) based on the bitmap, and the third DTC matches a third bit greater than the second bit (e.g., bit number 3) based on the bitmap.

[0107] In this case, the MCU 200 can configure the data information area 123 by arranging the FDCs corresponding to the first DTC, the FDCs corresponding to the second DTC, and the FDCs corresponding to the third DTC in the order of bit numbers.

[0108] For example, assume that the request message 11 requests DTC information that matches bits 0, 1, and 3 based on the bitmap. The MCU200 can sort the DTC information in ascending order of bit numbers 0, 1, and 3 that match these three pieces of information as "0A0001", "0A0002", "0A0004". The MCU 200 can record the FDC of DTC "0A0001" in byte number 4 of the data information area 123, record the FDC of DTC "0A0002" in byte number 5, and record the FDC of DTC "0A0004" in byte number 6.

[0109] As Figure 7 illustrated, "0x27" recorded in the fourth byte of the data information area 123 represents an example of the FDC of DTC "0A0001", "0x80" recorded in the fifth byte of the data information area 123 represents an example of the FDC of DTC "0A0002", and "0x7F" recorded in the sixth byte of the data information area 123 represents an example of the FDC of DTC "0A0004".

[0110] In the method without using a bitmap, the response message may require a relatively large amount of data, including the DTC information (DTC) and the corresponding status information (FDC) in the data information area. Additionally, in response to a request to read multiple DTC messages, each of the multiple packets can include one of the multiple DTCs and its corresponding FDC, and in this case, there may be a gap between the times when the multiple data packets representing the response to the request to read multiple DTC messages are generated.

[0111] In contrast, in the exemplary embodiment using a bitmap, multiple FDCs can be included in one packet according to the sorting order of the bit numbers indicated by the bitmap, without having to include the DTCs themselves in the response message 12, and the response message 12 can send multiple status information in one packet, thereby reducing distortion caused by gaps or delays.

[0112] In the following, reference will be made to Figures 8 to 10 to describe the case where the data delimiter is of the first type.

[0113] As described above, the first type may be a type that requests reading of an FDC corresponding to each of the DTCs included in the request message without using a bitmap.

[0114] Figure 8 is a diagram showing the structure of a request message without using a bitmap according to an exemplary embodiment.

[0115] As Figure 8 shown, the request message 11_1 may include a packet size information area 111, a packet identification information area 112, and a data information area 113_1. Figure 8 The descriptions of the packet size information area 111 and the packet identification information area 112 shown may be the same as Figure 4 those of the packet size information area 111 and the packet identification information area 112 shown. In the following, the descriptions of the packet size information area 111 and the packet identification information area 112 that overlap with the above description may be omitted.

[0116] Figure 8 The numbers shown may be hexadecimal, expressed as 1 byte, and the size of one unit of data in the request message 11_1 shown may be 1 byte.

[0117] The data information area 113_1 may correspond to a plurality of bytes starting from byte number 4. Although in Figure 4 it is shown that the data information area 113_1 is an area corresponding to 5 bytes - byte numbers 4 to 8 - this is for convenience of explanation, and the exemplary embodiment is not limited thereto.

[0118] Figure 9 is a diagram showing Figure 8 the structure of the data information area.

[0119] Referring to Figure 9 , the data information area 113_1 corresponds to a plurality of bytes, and the bits constituting each byte of the plurality of bytes may include values for specifying the DTCs for which reading is requested.

[0120] Figure 9 The numbers shown in Figure 9 may be binary, expressed as 1 bit, and the size of one unit of data in

[0121] As Figure 9 shown, in the following description, it will be assumed that the data information area 113_1 is a 5 - byte area including byte numbers 4 to 8.

[0122] The data information area 113_1 may include request data 1130_1 that can specify a DTC request to be read. The request data 1130_1 may be binary data sorted in descending order of bits and arranged in the data information area 113.

[0123] Reference Figure 9 , the request data 1130_1 may include a communication channel identifier 1131_1, a response type identifier 1132_1, and data information 1333_1.

[0124] For example, as Figure 9 illustrated, the "0" representing the response type identifier 1132_1 recorded in bit number 6 may indicate that the data separator is of the first type.

[0125] See Figure 9 , when the data separator is of the first type, the data information 1133_1 may include DTC information. For example, if as Figure 9 illustrated, the second bit of the request data 1130_1 is "0", then the other bits (bit numbers 0 to 5) in byte number 4 are "0", and byte numbers 5, 6, and 7 may include a DTC information.

[0126] When the communication channel identifier 1131 is the first communication channel, since the CAN communication channel is used, the request message 11 can be at most 8 bytes.

[0127] Therefore, if the communication channel identifier 1131 is the first communication channel and the response type identifier 1132 is of the first type, the request message 11 may include a DTC information corresponding to byte numbers 5, 6, and 7. This DTC information may indicate the DTC code information for requesting to read the FDC. For example, this DTC information may be "0A0001". If the response type identifier 1132 is of the first type, the request message 11 may also include separator information. Here, the separator information may be virtual data for separating multiple DTC information.

[0128] For example, byte numbers 5 to 7 may include the first DTC information, and byte number 8 may include separator information. In this way, the request message 11 of the first type using the first communication channel and not using the bitmap can request to read the FDC corresponding to at most one DTC.

[0129] Alternatively, if the communication channel identifier 1131 is the first communication channel and the response type identifier 1132 is the second type, the request message 11 may use multiple bits in byte numbers 4 to 8 to request reading of the FDC corresponding to each of the multiple DTCs. In this case, since the data information area of the request message 11 is 5 bytes, the request message 11 of the second type using the first communication channel and using a bitmap can request reading of the FDC corresponding to up to DTCs.

[0130] If the communication channel identifier 1131 is the second communication channel, since the CAN FD communication channel is used, the request message 11 can be up to 64 bytes at most.

[0131] Therefore, if the communication channel identifier 1131 is the second communication channel and the response type identifier 1132 is the first type, the request message 11 may include multiple DTC information and separation information in the area from byte number 5 to 64.

[0132] For example, byte numbers 5 to 7 may include the first DTC information, byte number 8 may include separation information, byte numbers 9 to 11 may include the second DTC information, byte number 12 may include separation information, byte numbers 13 to 15 may include the third DTC information, byte number 16 may include separation information, byte numbers 17 to 19 may include the fourth DTC information, and byte number 20 may include separation information.

[0133] In this way, the request message 11 of the first type using the second communication channel and not using a bitmap can request reading of the FDC corresponding to up to 15 DTCs at most.

[0134] In addition, if the communication channel identifier 1131 is the second communication channel and the response type identifier 1132 is the second type, the request message 11 may use multiple bits in byte numbers 4 to 64 to request reading of the FDC corresponding to each of the multiple DTCs. In this case, since the data information area of the request message 11 is 61 bytes, the request message 11 of the second type using the second communication channel and using a bitmap can request reading of the FDC corresponding to up to DTCs.

[0135] Figure 10 FIG. is a diagram illustrating the structure of a response message not used according to an exemplary embodiment.

[0136] As Figure 10 illustrated, the response message 12_1 may include a packet size information area 121, a packet identification information area 122, and a data information area 123_1. Figure 10The descriptions of the illustrated packet size information area 121 and packet identification information area 122 may be the same as Figure 7 the descriptions of the illustrated packet size information area 121 and packet identification information area 122. In the following, the descriptions of the packet size information area 121 and packet identification information area 122 that overlap with the above descriptions may be omitted.

[0137] Figure 10 The numbers illustrated in may be hexadecimal and expressed as 1 byte, and the size of one unit of data in the request message 11_1 illustrated may be 1 byte.

[0138] Figure 10 The illustrated response message 12_1 may be a response to Figure 8 the request message 11_1 with the illustrated response type identifier 1132 of the first type. Even when the response type identifier 1132 is of the first type, the communication channel identifier 1131 may be the first communication channel or the second communication channel.

[0139] First, the case where the communication channel identifier 1131 of the request message 11_1 is the first communication channel will be described.

[0140] The data information area 123_1 may correspond to multiple bytes starting from byte number 4. Although in Figure 4 it is illustrated that the data information area 113_1 is an area corresponding to five bytes - byte numbers 4 to 8 - for the sake of convenience of explanation, and the exemplary embodiment is not limited thereto.

[0141] The data information area 123_1 may include the DTC information requested to be read in the request message 11_1 and the diagnostic result corresponding to the DTC requested to be read. Here, the diagnostic result corresponding to the DTC requested to be read may include the FDC value of the corresponding DTC information.

[0142] The MCU 200 may record the DTC information included in byte numbers 5 to 7 of the request message 11_1 in byte numbers 4 to 6 of the data information area 123_1, and record the FDC corresponding to the DTC recorded in bytes 4 to 6 in byte 7 of the data information area 123_1.

[0143] For example, "0A0001" may be recorded in byte numbers 4 to 6 of the data information area 123_1, and the FDC "0x27" corresponding to "0A0001" may be recorded in byte number 7 of the data information area 123_1.

[0144] Next, the case where the communication channel identifier 1131 of the request message 11_1 is the second communication channel will be described.

[0145] If the communication channel identifier 1131 of the request message 11_1 is the second communication channel and the response type identifier 1132 is the first type, the response message 12_1 may include multiple DTC information, the FDC for each of the multiple DTC information, and separation information in the region from byte 5 to byte 64. Here, the separation information may be virtual data for separating the multiple DTC information or the FDC corresponding to the multiple DTC information. The BMS 310 may configure the data information region 123_1 by arranging in sequence the multiple DTCs included in the request message 11_1 and the FDCs corresponding to the respective DTCs.

[0146] For example, if the diagnostic information data excluding the separator information in the data information region 113_1 of the request message 11_1 includes first DTC information and second DTC information, the BMS 310 may configure the data information region 123_1 of the response message 12_1 by arranging in sequence the first DTC information, the FDC corresponding to the first DTC information, the second DTC information, and the FDC corresponding to the second DTC information. Here, the separator information in the data information region 113_1 may include the communication channel identifier 1131 (which is the second communication channel) and the response type identifier 1132 (which is the second type).

[0147] For example, byte numbers 5 to 7 may include first DTC information, byte number 8 may include the FDC value corresponding to the first DTC information, and byte number 9 may include separation information. Byte numbers 10 to 12 may include second DTC information, byte number 13 may include the FDC value corresponding to the second DTC information, and byte number 14 may include separation information. Byte numbers 15 to 17 may include third DTC information, byte number 18 may include the FDC value corresponding to the third DTC information, and byte number 19 may include separation information. Byte numbers 20 to 22 may include fourth DTC information, byte number 23 may include the FDC value corresponding to the fourth DTC information, and byte number 24 may include separation information.

[0148] Thus, when using the first type that does not use a bitmap, the length of the response message to the request message 11_1 requesting 4 DTC information may be 24 bytes.

[0149] Although the exemplary embodiments of the present invention have been described in detail above, the scope of the present disclosure is not limited thereto, and various modifications and improvements made by those of ordinary skill in the art to which the present invention pertains also fall within the scope of the present disclosure.

Claims

1. A method for transmitting and receiving fault detection counter (FDC) information for a diagnostic trouble code (DTC) by a battery system, the method comprising: Receive request message; as well as sending a response message corresponding to the request message, The data information area of ​​the request message includes a data separator and diagnostic information data. The data delimiter is a first type for requesting to read an FDC corresponding to each of at least one piece of DTC information included in the request message, or a second type for requesting to read a plurality of FDCs according to a bitmap, and The bitmap is a list in which a plurality of pieces of DTC diagnostic information are matched with a plurality of bits constituting the diagnostic information data.

2. The method according to claim 1, wherein If the data delimiter is of the second type, The diagnostic information data includes binary data in which a binary value corresponds to each of the plurality of bits, and Bits having a first value among the binary data match a plurality of first DTCs based on the bitmap.

3. The method according to claim 2, wherein The data information area of ​​the response message includes a plurality of FDCs corresponding to the plurality of first DTCs.

4. The method according to claim 2, wherein If, based on the bitmap, the plurality of first DTCs include a DTC matching a first bit and a DTC matching a second bit greater than the first bit, The data information area of ​​the response message includes a data information area in which an FDC corresponding to the DTC matching the first bit and an FDC corresponding to the DTC matching the second bit are arranged in sequence.

5. The method according to claim 1, wherein If the type of the response message is the first type, The diagnostic information data includes first DTC information and second DTC information.

6. The method according to claim 5, wherein The data information area of ​​the response message is configured by sequentially arranging the first DTC information, the FDC corresponding to the first DTC information, the second DTC information, and the FDC corresponding to the second DTC information.

7. A battery system for sending fault detection counter (FDC) information for a diagnostic trouble code (DTC) to a vehicle and receiving FDC information for the DTC from the vehicle, the battery system comprising: A battery pack, the battery pack comprising a plurality of battery cells; as well as a battery management system (BMS), the BMS being configured to manage the battery pack, The BMS receives a request message from the vehicle and sends a response message corresponding to the request message to the vehicle. The data information area of ​​the request message includes a data separator and diagnostic information data, The data delimiter is a first type for requesting to read an FDC corresponding to each of at least one piece of DTC information included in the request message, or a second type for requesting to read a plurality of FDCs according to a bitmap, and The bitmap is a list of matches between pieces of DTC diagnostic information and bits constituting the diagnostic information data.

8. The battery system according to claim 7, wherein If the data delimiter is of the second type, The diagnostic information data includes binary data in which a binary value corresponds to each of the plurality of bits, and Among the plurality of bits represented by the binary data, a plurality of first bits matching the plurality of pieces of DTC diagnostic information requested to be read based on the bitmap have a first value, and the other plurality of bits excluding the plurality of first bits have a second value.

9. The battery system according to claim 8, wherein The data information area of ​​the response message includes a plurality of FDCs corresponding to the plurality of first DTCs.

10. The battery system according to claim 8, wherein If, based on the bitmap, the plurality of first DTCs include a DTC matching a first bit and a DTC matching a second bit greater than the first bit, The BMS configures a data information area of ​​the response message by sequentially arranging an FDC corresponding to the DTC matched with the first bit and an FDC corresponding to the DTC matched with the second bit.

11. The battery system according to claim 7, wherein If the type of the response message is the first type, The diagnostic information data includes first DTC information and second DTC information.

12. The battery system according to claim 11, wherein The BMS configures a data information area of ​​the response message by sequentially arranging the first DTC information, the FDC corresponding to the first DTC information, the second DTC information, and the FDC corresponding to the second DTC information.

Images