FDC(Fault Detection Counter) INFORMATION ABOUT DTC(Diagnostic Trouble Code) TRANSCEIVING METHOD AND BATTERY SYSTEM USING THE METHOD

Abstract

A method for a battery system to transmit and receive Fault Detection Counter (FDC) information for a Diagnostic Trouble Code (DTC) according to one feature of the invention comprises the steps of receiving a request message and transmitting a response message corresponding to the request message, wherein the data area of ​​the request message includes a data separator and diagnostic information data, the data separator is a first type requesting an FDC read corresponding to each of at least one DTC information included in the request message or a second type requesting a plurality of FDC reads according to a bitmap, and the bitmap may be a list in which a plurality of DTC diagnostic information is matched with a plurality of bits constituting the diagnostic information data.

Description

Technology Field

[0001] The present disclosure relates to a method for transmitting and receiving Fault Detection Counter (FDC) information regarding Diagnostic Trouble Code (DTC) and a battery system applying the same. Background Technology

[0002] According to the ISO-14229 standard protocol definition, regarding the status of a Diagnostic Trouble Code (DTC), the response to a single request can represent the fault status for a single diagnosis through a Fault Detection Counter (FDC).

[0003] However, to verify diagnostic information for recent battery thermal or isolation issues, it is necessary to read and check multiple states simultaneously at a specific point in time. The problem to be solved

[0004] The present invention aims to provide a method for transmitting and receiving FDC (Fault Detection Counter) information for a Diagnostic Trouble Code (DTC), which can represent multiple DTCs and their corresponding FDCs as a single message when transmitting and receiving FDC information for a DTC, and a battery system applying the same. means of solving the problem

[0005] A method for a battery system to transmit and receive Fault Detection Counter (FDC) information for a Diagnostic Trouble Code (DTC) according to one feature of the invention comprises the steps of receiving a request message and transmitting a response message corresponding to the request message, wherein the data area of ​​the request message includes a data separator and diagnostic information data, the data separator is a first type requesting an FDC read corresponding to each of at least one DTC information included in the request message or a second type requesting a plurality of FDC reads according to a bitmap, and the bitmap is a list in which a plurality of DTC diagnostic information is matched with a plurality of bits constituting the diagnostic information data.

[0006] When the above data separator 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 the bits that are first values ​​among the binary data can be matched to a plurality of first DTCs based on the bitmap.

[0007] The data area of ​​the above response message may include a plurality of FDCs corresponding to the plurality of first DTCs.

[0008] If the plurality of first DTCs above include a DTC that matches a first bit based on the bitmap and a DTC that matches a second bit greater than the first bit, the data area of ​​the response message may include a data area in which an FDC corresponding to the DTC that matches the first bit and an FDC corresponding to the DTC that matches the second bit are arranged consecutively.

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

[0010] The data area of ​​the above response message may be configured by being arranged in the order of 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.

[0011] A battery system according to another feature of the invention, in a battery system that transmits and receives Fault Detection Counter (FDC) information regarding Diagnostic Trouble Codes (DTCs) to and from a vehicle, comprises a battery pack including a plurality of battery cells and a Battery Management System (BMS) that manages the battery pack, wherein the BMS receives a request message from the vehicle and transmits a response message corresponding to the request message to the vehicle, wherein the data area of ​​the request message includes a data separator and diagnostic information data, wherein the data separator is a first type requesting an FDC read corresponding to each of at least one DTC information included in the request message or a second type requesting a plurality of FDC reads according to a bitmap, and the bitmap is a list in which a plurality of DTC diagnostic information is matched with a plurality of bits constituting the diagnostic information data.

[0012] When the above data separator 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, the plurality of first bits that match the plurality of DTC diagnostic information to be read among the plurality of bits based on the bitmap are the first values, and the remaining plurality of bits excluding the plurality of first bits among the plurality of bits may be the second values.

[0013] The data area of ​​the above response message may include a plurality of FDCs corresponding to the plurality of first DTCs.

[0014] If the plurality of first DTCs above include a DTC that matches a first bit based on the bitmap and a DTC that matches a second bit greater than the first bit, the BMS can configure the data area of ​​the response message by arranging the FDC corresponding to the DTC that matches the first bit and the FDC corresponding to the DTC that matches the second bit in succession.

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

[0016] The above BMS can configure the data area of ​​the response message 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 that order. Effects of the invention

[0017] According to the present invention, a request message requests DTC information using a bitmap for multiple DTC information, and a response message includes all of multiple diagnostic information according to the bitmap, thereby enabling the use of less data in diagnosing FDC information corresponding to multiple DTCs.

[0018] According to the present invention, when utilizing a CAN FD channel, data is transmitted only as much as the DLC, allowing for flexible data buffer utilization.

[0019] When a response message includes one FDC corresponding to each DTC, accurate vehicle diagnosis may be difficult due to the time interval between the packet reception times of each response message. According to the present invention, a response message includes multiple FDC information, allowing diagnosis by simultaneously verifying multiple data representing the vehicle's status at a specific point in time. Brief explanation of the drawing

[0020] FIG. 1 is a drawing showing a vehicle and battery system to which one embodiment is applied. FIG. 2 is a drawing showing a part of the configuration of a vehicle according to one embodiment. FIG. 3 is a diagram showing a part of the configuration of a battery system according to one embodiment. FIG. 4 is a diagram showing the structure of a request message using a bitmap according to one embodiment. Figure 5 is a diagram showing the structure of the data area of ​​Figure 4. FIG. 6 is an example of a bitmap representing a plurality of bits corresponding to a plurality of DTCs according to one embodiment. FIG. 7 is a diagram showing the structure of a response message using a bitmap according to one embodiment. FIG. 8 is a diagram showing the structure of a request message that does not use a bitmap according to one embodiment. Figure 9 is a diagram showing the structure of the data area of ​​Figure 8. FIG. 10 is a diagram showing the structure of an unused response message according to one embodiment. Specific details for implementing the invention

[0021] Hereinafter, embodiments disclosed in this specification will be described in detail with reference to the attached drawings. Identical or similar components are assigned identical or similar reference numerals, and redundant descriptions thereof will be omitted. The suffixes "module" and / or "part" for components used in the following description are assigned or used interchangeably solely for the ease of drafting the specification and do not have distinct meanings or roles in themselves. Furthermore, in describing the embodiments disclosed in this specification, if it is determined that a detailed description of related prior art could obscure the essence of the embodiments disclosed in this specification, such detailed description will be omitted. Additionally, the attached drawings are intended only to facilitate understanding of the embodiments disclosed in this specification; the technical concept disclosed in this specification is not limited by the attached drawings, and it should be understood that they include all modifications, equivalents, and substitutions that fall within the spirit and technical scope of the invention.

[0022] Terms including ordinal numbers, such as first, second, etc., may be used to describe various components, but said components are not limited by said terms. These terms are used solely for the purpose of distinguishing one component from another.

[0023] When it is stated that one component is "connected" or "connected" to another component, it should be understood that while it may be directly connected or connected to that other component, there may also be other components in between. On the other hand, when it is stated that one component is "directly connected" or "directly connected" to another component, it should be understood that there are no other components in between.

[0024] In this application, terms such as “comprising” or “having” are intended to specify the existence of the features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

[0025] FIG. 1 is a drawing showing a vehicle and battery system to which one embodiment is applied.

[0026] The vehicle (10) can send a request message to the battery system (20) to obtain information related to a Diagnostic Trouble Code (DTC) (hereinafter, DTC information) (S10).

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

[0028] In FIG. 1, a vehicle and a battery system are illustrated as examples of diagnostic targets that transmit and receive messages to and from a diagnostic device, but the invention is not limited thereto. An embodiment may be applied to a device capable of performing a diagnosis on a battery, such as a battery system, and storing information about the results of the diagnosis.

[0029] FIG. 2 is a drawing showing a part of the configuration of a vehicle according to one embodiment.

[0030] As illustrated in FIG. 2, the vehicle (10) may include an Electronic Control Unit (ECU) (100), a communication unit (110), and a memory (120).

[0031] The ECU (100) generates a request message, collects necessary data from a received response message, and performs a series of operations to control the operation of the vehicle (10). The request message may be a message requesting information about a DTC belonging to a specific DTC state and a FDC (Fault Detection Counter) corresponding to the DTC.

[0032] The communication unit (110) can transmit a request message to the outside and receive a response message for the request message. For example, the communication unit (110) can transmit a request message to the battery system (20) and receive a response message from the battery system (20).

[0033] The memory (120) can store data collected from response messages by the control unit (100). The memory (120) can store data necessary for the operation of the control unit (100) generating request messages, controlling the operation of the vehicle (10), etc.

[0034] FIG. 3 is a diagram showing a part of the configuration of a battery system according to one embodiment.

[0035] As illustrated in FIG. 3, the battery system (20) may include a battery pack (300) comprising a plurality of battery cells and a battery management system (BMS) (310) that performs battery pack management such as charging / discharging, monitoring, and protection operations for the battery pack (300). The BMS (310) may include a main control unit (MCU) (200), a communication unit (210), and a memory (220).

[0036] The MCU (200) performs a diagnosis based on the received request message, generates a response message based on the diagnosis result, and performs a series of operations to control the operation of the BMS (20).

[0037] The communication unit (210) receives a request message and transmits a response message externally. For example, the communication unit (210) can receive a request message from the vehicle (10) and transmit a response message to the vehicle (10).

[0038] The memory (220) stores diagnostic content and results based on the performed diagnosis. The MCU (200) can detect and read necessary information from the memory (220) to generate a response message. The memory (220) can store data necessary for the MCU (200) to control the BMS (20).

[0039] FIGS. 2 and 3 illustrate only the configurations necessary to explain one embodiment. Configurations not illustrated in FIGS. 2 and 3 may be included in the vehicle and battery system.

[0040] FIG. 4 is a diagram showing the structure of a request message using a bitmap according to one embodiment.

[0041] As illustrated in FIG. 4, the request message (11) may include a packet size information area (111), a packet identification information area (112), and a data area (Data Information) (113). The number illustrated in FIG. 4 may be expressed in hexadecimal as 1 Byte, and the size of the data illustrated as one cell in FIG. 4 may be 1 Byte.

[0042] The packet size information area (111) may include a Data Length Code (DLC). The DLC may define the size obtained by summing the amount of data in the packet identification information area (112) and the amount of data in the data area (113) in the request message. For example, as shown in FIG. 4, "0x05" recorded in the 1st Byte area, which is the packet size information area (111), may indicate that the size obtained by summing the amount of data in the packet identification information area (112) and the amount of data in the data area (113) is 5 Bytes.

[0043] The packet identification information area (112) may correspond to an area of ​​2 bytes or more. A service identifier (Service ID) is recorded in the first byte of the packet identification information area (112), and a data identifier (Data ID) may be recorded in the second byte of the packet identification information area (112).

[0044] As illustrated in FIG. 4, "0x19" recorded in the 2nd byte area of ​​the packet identification information area (112) may be an example of a service identifier (DTC Read Service ID) requesting a service to read DTC information. That is, if "0x19" is a service identifier, the message may be a message requesting a service for the ECU (100) to read DTC information stored in the BMS (310). In response to this request, the BMS (310) may read the stored DTC information and transmit it to the ECU (100). At this time, the BMS (310) requires information to specify which of the multiple stored DTC information to read.

[0045] As illustrated in FIG. 4, "0x06" recorded in the 3rd byte area of ​​the packet identification information area (112) may be an example of a data identifier (FDC Read Service ID) requesting FDC data corresponding to a DTC. That is, if "0x06" is a data identifier in a request message, the request message may be a message in which the ECU (100) requests FDC data from among the DTC information stored in the BMS (310). In accordance with this request, the BMS (310) may read the FDC for the stored DTC and transmit it to the ECU (100).

[0046] The data area (113) may correspond to multiple byte areas starting from Byte 4. In FIG. 4, the data area (113) is depicted as a region corresponding to three Bytes, Bytes 4, 5, and 6, but this is for convenience of explanation and the embodiment is not limited thereto.

[0047] Figure 5 is a diagram showing the structure of the data area of ​​Figure 4.

[0048] Referring to FIG. 5, the data area (113) corresponds to a plurality of Bytes, and the bits constituting each of the plurality of Bytes may include a value for specifying the DTC requesting a read.

[0049] The number shown in Fig. 5 can be represented as a binary number and as 1 bit, and the size of the data shown as one unit in Fig. 5 can be 1 bit.

[0050] Hereinafter, as shown in FIG. 5, the explanation assumes that the data area (113) is a 3-byte area.

[0051] The data area (113) may include request data (1130) that can identify a DTC requesting to read. The request data (1130) may be binary data arranged in descending order of bits in the data area (113). As shown in FIG. 5, 24-bit binary data "11000000 00000000 00001011", ranging from data corresponding to bit 23 to data corresponding to bit 0, may be an example of the request data (1130).

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

[0053] The communication channel identifier (1131) can specify a communication channel to receive a response message. The communication channel to receive the response message may be one of a plurality of communication channels. The plurality of communication channels may include a first communication channel and a second communication channel.

[0054] The first communication channel may be a communication channel in which the maximum amount of data that can be transmitted is set to a predetermined first reference amount. The second communication channel may be a communication channel in which the maximum amount of data that can be transmitted is set to a predetermined second reference amount that is greater than the first reference amount.

[0055] Specifically, the first communication channel may be a channel in which the total amount of data of message packets that can be transmitted at once is less than the total amount of data of message packets that the second communication channel can transmit at once. For example, the first communication channel may be a CAN communication channel and the second communication channel may be a CAN FD channel.

[0056] The CAN FD channel is a communication standard developed to compensate for the shortcomings of the CAN channel, and it is a communication channel that can contain a larger maximum amount of data than the CAN channel. For example, if the maximum amount of data that can be included in a packet transmitted through the CAN channel is 8 Bytes, the maximum amount of data that can be included in a packet transmitted through the CAN FD channel is 64 Bytes.

[0057] For example, as illustrated in FIG. 5, the "1" recorded in bit 23 representing the communication channel identifier (1131) may indicate that the communication channel of the request message (11) is the second communication channel.

[0058] The response type identifier (1132) can specify the requested data separator. The data separator may be one of a plurality of types. The plurality of types may include a first type and a second type.

[0059] The first type may be a type that requests an FDC read 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 an FDC read corresponding to each of a plurality of DTCs represented by a plurality of bits indicated in the request message according to the bitmap. Here, the bitmap may be a list in which a plurality of DTC diagnostic information is matched with a plurality of bits. The DTC diagnostic information may include DTC information, the name of the diagnosis indicated by the DTC information, etc.

[0060] For example, as shown in FIG. 5, the "1" recorded in bit 22 representing the response type identifier (1132) may indicate that the data separator is of the second type.

[0061] The communication channel identifier (1131) and the response type identifier (1132) illustrated in FIG. 5 are each depicted as binary numbers corresponding to 1 bit, but this is for convenience of explanation and the invention is not limited thereto. The communication channel identifier (1131) and the response type identifier (1132) may each be hexadecimal numbers corresponding to 1 byte.

[0062] Hereinafter, with reference to FIGS. 5 to 7, the case where the data separator is of the second type will be explained.

[0063] Referring to FIG. 5, when the data separator is of the second type, the data information (1333) may include diagnostic information data composed of multiple bits. The diagnostic information data may be binary data in which a binary value corresponds to each of the multiple bits. The diagnostic information data may include multiple DTCs that request to be read.

[0064] Among the multiple bits represented by the diagnostic information data, the bits having a first value (e.g., "1") can be matched with multiple DTC information to be read based on the bitmap. Additionally, among the multiple bits represented by the diagnostic information data, the remaining bits, excluding those that match the multiple DTC information to be read, can be a second value (e.g., "0").

[0065] FIG. 6 is an example of a bitmap representing a plurality of bits corresponding to a plurality of DTCs according to one embodiment.

[0066] The order of multiple bits included in the bitmap can be sorted in ascending or descending order, and each bit can be matched to one of the multiple DTCs.

[0067] Referring to FIG. 6, the bitmap may be a list in which the number of each bit represented by the diagnostic information data, the DTC, and the name of the diagnosis represented by the DTC (DTC Name) are matched with each other. The multiple DTC diagnostic information represented by the multiple DTC information may correspond to multiple bits. As shown in FIG. 6, "OA0001-OA0008", "0B0B00", "0B3C01-0B3C06", and "0C0A00-0C0A06" may be examples of multiple DTCs.

[0068] Below, an example of the bitmap shown in FIG. 6 is described.

[0069] Bit 0 is matched to DTC "0A0001" representing the diagnosis name "DTC Module Error #1", and bit 1 can be matched to DTC "0A0002" representing the diagnosis name "DTC Module Error #2". Bit 2 is matched to DTC "0A0003" representing the diagnosis name "DTC Module Error #3", and bit 3 can be matched to DTC "0A0004" representing the diagnosis name "DTC Module Error #4". Bit 4 is matched to DTC "0A0005" representing the diagnosis name "DTC Module Error #5", and bit 5 can be matched to DTC "0A0006" representing the diagnosis name "DTC Module Error #6". Bit 6 can be matched to DTC "0A0007" representing the diagnosis name "DTC Module Error #7", and bit 7 can be matched to DTC "0A0008" representing the diagnosis name "DTC Module Error #8". Among the diagnosis names, names including "DTC Module Error" can represent a predetermined error that occurred in each of the plurality of battery modules included in the battery pack (300).

[0070] Bit 8 matches DTC "0B0B00" representing the diagnosis name "DTC cell Error #1", and bit 9 can match DTC "0B3C01" representing the diagnosis name "DTC cell Error #2". Bit 10 matches DTC "0B3C02" representing the diagnosis name "DTC cell Error #3", and bit 11 can match DTC "0B3C03" representing the diagnosis name "DTC cell Error #4". Bit 12 matches DTC "0B3C04" representing the diagnosis name "DTC cell Error #5", bit 13 matches DTC "0B3C05" representing the diagnosis name "DTC cell Error #6", and bit 14 can match DTC "0B3C06" representing the diagnosis name "DTC cell Error #7". Among the names of the diagnoses, a name including "DTC cell Error" may indicate a specific error that occurred in each of the plurality of battery cells included in the battery pack (300).

[0071] Bit 15 is matched to DTC "0C0A00" representing the diagnosis name "DTC_CELL_SENSE_OPEN", and bit 16 can be matched to DTC "0C0A01" representing the diagnosis name "DTC_CELL_SENSE_OPEN". Bit 17 is matched to DTC "0C0A02" representing the diagnosis name "DTC_CELL_SENSE_OPEN", and bit 18 can be matched to DTC "0C0A03" representing the diagnosis name "DTC_CELL_SENSE_OPEN". Bit 19 may be matched to DTC "0C0A04" representing the diagnosis name "DTC_CELL_SENSE_OPEN", bit 20 may be matched to DTC "0C0A05" representing the diagnosis name "DTC_CELL_SENSE_OPEN", and bit 21 may be matched to DTC "0C0A06" representing the diagnosis name "DTC_CELL_SENSE_OPEN". Among the diagnosis names, a name including "DTC_CELL_SENSE_OPEN" may indicate a certain error that occurred in detecting cell information (e.g., cell voltage, cell temperature, cell current, etc.) of each of the plurality of battery cells included in the battery pack (300).

[0072] Each of the multiple DTC diagnostic information represented by the bitmap can indicate the battery status, such as temperature, voltage, isolation error, communication error, abnormal operation, etc., for each of the multiple battery cells and / or multiple battery modules included in the battery pack (300) included in the battery pack (300).

[0073] In this way, each bit constituting the diagnostic information data can correspond to a bit number according to the bitmap. In the data information (1133) shown in FIG. 5, bits 21 through 0 can correspond to bits 21 through 0 of the bitmap shown in FIG. 6. For example, in the data information (1133) shown in FIG. 5, data corresponding to DTC "0C0A06" corresponding to bit 21 of the bitmap shown in FIG. 6 can be recorded in bit 21.

[0074] The value recorded in each bit from bit 21 to bit 0 of the diagnostic information data may be a first value (e.g., "1") or a second value (e.g., "0"). Among these, the DTC matched according to the bitmap for the bit recorded as the first value may indicate that the request message (11) is requesting to read the DTC.

[0075] Since the data of bit 0, bit 1, and bit 3 of the data information (1133) shown in FIG. 5 is "1" and the remaining bits are "0", the request message (11) containing this data information (1133) indicates a state of requesting a read for DTCs "0A0001", "0A0002", and "0A0004" that match bits 0, 1, and 3 in the bitmap shown in FIG. 6.

[0076] In one embodiment, the request message (11) can request multiple DTC information as a single data packet using a bitmap, and the length of the data area (113) can be increased or decreased according to the number of multiple bits represented by the bitmap.

[0077] In a method that does not use bitmaps, the request message may include at least one DTC in the packet and require at least 3 bytes of area for each of the at least one DTC. Therefore, a request message to request information on 5 DTCs may require 5 packets by including one DTC in each packet, or it may require at least 3*5=15 bytes of area by including 5 DTCs in one packet.

[0078] In comparison to this, in an embodiment using a bitmap, the DTC itself is not included in the message, and the DTC can be identified by toggling a bit defined by the bitmap, so the size of the data area (113) can be reduced.

[0079] In one embodiment, if the bitmap is a list representing bits that match DTCs with a number greater than 8*(m-1)-2 and less than or equal to 8*(m)-2, it is sufficient for the length of the data area (113) to be m Bytes. However, this applies to the case where the communication channel identifier (1131) and the response type identifier (1132) are binary numbers corresponding to 1 bit each, and if the communication channel identifier (1131) and the response type identifier (1132) are k bits, the request message (11) may require a data area (113) of m Bytes, in the case where the bitmap is a list representing bits that match DTCs with a number greater than 8*(m-1)-2*k and less than or equal to 8*(m)-2*k. Here, m is a natural number greater than or equal to 2, and k is a natural number greater than or equal to 1.

[0080] For example, if the bitmap is a list in which each of the 35 DTC diagnostic information items is matched with a bit, the request message (11) may require a 5-byte data area (113).

[0081] FIG. 7 is a diagram showing the structure of a response message using a bitmap according to one embodiment.

[0082] As illustrated in FIG. 7, the response message (12) may include a packet size information area (121), a packet identification information area (122), and a data area (123). The number illustrated in FIG. 7 may be expressed in hexadecimal as 1 Byte, and the size of the data illustrated as one cell in FIG. 7 may be 1 Byte.

[0083] The packet size information area (121) may include a data length code (DLC). The DLC may define the size obtained by summing the amount of data in the packet identification information area (122) and the amount of data in the data area (123) in the request message. For example, as shown in FIG. 6, "0x05" recorded in the 1st Byte area, which is the packet size information area (121), may indicate that the size obtained by summing the amount of data in the packet identification information area (122) and the amount of data in the data area (123) is 5 Bytes.

[0084] The packet identification information area (122) corresponds to an area of ​​2 bytes or more, and a service identifier (Service ID) is recorded in the first byte of the packet identification information area (122), and a data identifier (Data ID) can be recorded in the second byte of the packet identification information area (122).

[0085] As illustrated in FIG. 7, "0x59" recorded in the 2nd byte area of ​​the packet identification information area (112) may be an example of a service identifier (DTC Read Information Positive Response Service ID) representing a response containing DTC information. That is, if "0x59" is a service identifier, the message may be a message in which the ECU (100) responds with DTC information stored in the BMS (310).

[0086] As illustrated in FIG. 7, "0x06" recorded in the 3rd byte area of ​​the packet identification information area (122) may be an example of a data identifier (FDC Read Service ID) requesting FDC data corresponding to a DTC. That is, if "0x06" is a data identifier in the response message, the message may be a message representing FDC data among the DTC information stored in the BMS (310).

[0087] When the number of multiple 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 area (123) may correspond to an n Byte area.

[0088] For example, if the first bit and the second bit among the multiple bits included in the data area (113) of the request message (11) are "1" and the remaining bits are 0, the BMS (310) can be configured such that among the multiple Bytes included in the data area (123) of the response message (12), the first Byte includes an FDC corresponding to the DTC that matches the first bit, and the second Byte includes an 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 area (123) by arranging the first Byte and the second Byte consecutively.

[0089] Referring to FIG. 7, n is described as being 3. The BMS (310) can form a data area (123) by arranging n FDCs for n DTCs in a continuous sequence.

[0090] Each of the n bytes included in the data area (123) may contain an FDC for the corresponding DTC information among the n DTC information requested to be read in the request message (11).

[0091] The MCU (200) can sort n DTC information based on a bitmap so that the matching bit numbers are in ascending order, and arrange the FDC for each DTC information in n bytes of the data area (113) in the sorting order.

[0092] It can be assumed that n DTC information includes a first DTC, a second DTC, and a third DTC, and that the first DTC is matched to a first bit (e.g., bit 0) based on a bitmap, the second DTC is matched to a second bit (e.g., bit 1) greater than the first bit based on a bitmap, and the third DTC is matched to a third bit (e.g., bit 3) greater than the second bit based on a bitmap.

[0093] In this case, the MCU (200) can configure the data area (123) by arranging the FDC corresponding to the first DTC, the FDC corresponding to the second DTC, and the FDC corresponding to the third DTC in succession according to the bit number order.

[0094] For example, assume that a request message (11) requests DTC information that matches bits 0, 1, and 3 based on a bitmap. The MCU (200) can sort the DTC information into "0A0001", "0A0002", and "0A0004" so that the bit numbers 0, 1, and 3 that match the three pieces of information are sorted in ascending order. The MCU (200) can write the FDC for DTC "0A0001" to the 4th byte of the data area (123) according to the sorting order, write the FDC for "0A0002" to the 5th byte, and write the FDC for "0A0004" to the 6th byte.

[0095] As shown in FIG. 7, "0x27" recorded in the 4th byte area of ​​the data area (123) represents an example of FDC for DTC "0A0001", "0x80" recorded in the 5th byte area of ​​the data area (123) represents an example of FDC for DTC "0A0002", and "0x7F" recorded in the 6th byte area of ​​the data area (123) represents an example of FDC for DTC "0A0004".

[0096] In a method that does not use a bitmap, the response message may require a relatively large amount of data, including DTC information (DTC) and corresponding status information (FDC) in the data area. Additionally, in a response to a request to read multiple DTC information, each of the multiple packets may include one of the multiple DTCs and its corresponding FDC; in this case, a gap may occur between the creation times of the multiple packets representing the response to the request to read multiple DTC information.

[0097] In comparison, in an embodiment using a bitmap, it is not necessary to include the DTC itself in the response message (12), but rather multiple FDCs can be included in a single packet according to the order sorted by the bit numbers represented by the bitmap, and multiple status information can be transmitted simultaneously in a single packet of the response message (12), thereby reducing distortion caused by gaps or delays.

[0098] Hereinafter, with reference to FIGS. 8 to 10, the case where the data separator is of the first type will be described.

[0099] As described above, the first type may be a type that requests an FDC read corresponding to each DTC included in the request message without using a bitmap.

[0100] FIG. 8 is a diagram showing the structure of a request message that does not use a bitmap according to one embodiment.

[0101] As illustrated in FIG. 8, the request message (11_1) may include a packet size information area (111), a packet identification information area (112), and a data area (Data Information) (113_1). The description of the packet size information area (111) and the packet identification information area (112) illustrated in FIG. 8 may be the same as the description of the packet size information area (111) and the packet identification information area (112) illustrated in FIG. 4. Hereinafter, descriptions of parts of the description regarding the packet size information area (111) and the packet identification information area (112) that overlap with the previously described description may be omitted.

[0102] The number shown in Fig. 8 can be expressed in hexadecimal as 1 byte, and the size of the data shown as one cell in the request message (11_1) can be 1 byte.

[0103] The data area (113_1) may correspond to multiple byte areas starting from Byte 4. In FIG. 4, the data area (113_1) is depicted as a region corresponding to 5 Bytes from Byte 4 to Byte 8, but this is for convenience of explanation and the embodiment is not limited thereto.

[0104] Figure 9 is a diagram showing the structure of the data area of ​​Figure 8.

[0105] Referring to FIG. 9, the data area (113_1) corresponds to a plurality of Bytes, and the bits constituting each of the plurality of Bytes may include a value for specifying the DTC requesting a read.

[0106] The number shown in Fig. 9 can be represented as a binary number and as 1 bit, and the size of the data shown as one unit in Fig. 9 can be 1 bit.

[0107] Hereinafter, as illustrated in FIG. 9, the explanation assumes that the data area (113_1) is a 5-byte area of ​​4 to 8 bytes.

[0108] The data area (113_1) may include request data (1130_1) that can identify the DTC requesting to read. The request data (1130_1) may be binary data arranged in descending order of bits in the data area (113).

[0109] Referring to FIG. 9, the request data (1130_1) may include a communication channel identifier (1131_1), a response type identifier (1132_1), and data information (1133_1).

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

[0111] Referring to FIG. 9, when the data separator is of the first type, the data information (1333_1) may include DTC information. For example, as shown in FIG. 9, when the second bit of the request data (1130_1) is "0", the remaining bits (bits 0 through 5) of the 4th byte are "0", and the 5th byte, 6th byte, and 7th byte may contain one DTC information.

[0112] When the communication channel identifier (1131) is the first communication channel, the CAN communication channel is used, so the request message (11) can be up to 8 Bytes.

[0113] Accordingly, when the communication channel identifier (1131) is the first communication channel and the response type identifier (1132) is the first type, the request message (11) may include one DTC information corresponding to Byte 5, Byte 6, and Byte 7. The one DTC information may represent code information of a DTC requesting FDC read. For example, the one DTC information may be "0A0001". When the response type identifier (1132) is the first type, the request message (11) may further include distinction information. Here, the distinction information may be dummy data for distinguishing multiple DTC information.

[0114] For example, Bytes 5 through 7 may contain first DTC information, and Byte 8 may contain distinction information. In this way, a first type of request message (11) that uses the first communication channel and does not use a bitmap may request FDC reading corresponding to up to 1 DTC.

[0115] In addition, when the communication channel identifier (1131) is the first communication channel and the response type identifier (1132) is the second type, the request message (11) can request FDC reading corresponding to each of the multiple DTCs using multiple bits of 4 to 8 bytes. In this case, since the data area of ​​the request message (11) is 5 bytes, the request message (11) of the second type, which uses the first communication channel and bitmap, can request FDC reading corresponding to up to 8*5-2=38 DTCs.

[0116] When the communication channel identifier (1131) is the second communication channel, the CAN FD communication channel is used, so the request message (11) can be up to 64 Bytes.

[0117] Accordingly, when 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 distinction information in the area from Byte 5 to Byte 64.

[0118] For example, Bytes 5 through 7 may contain first DTC information, Byte 8 may contain classification information, Bytes 9 through 11 may contain second DTC information, Byte 12 may contain classification information, Bytes 13 through 15 may contain third DTC information, Byte 16 may contain classification information, Bytes 17 through 19 may contain fourth DTC information, and Byte 20 may contain classification information.

[0119] In this way, a first type of request message (11) that uses a second communication channel and does not use a bitmap can request FDC readings corresponding to up to 15 DTCs.

[0120] 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) can request FDC readings corresponding to each of the multiple DTCs using multiple bits from byte 4 to byte 64. In this case, since the data area of ​​the request message (11) is 61 bytes, the request message (11) of the second type, which uses the second communication channel and bitmap, can request FDC readings corresponding to up to 8*61-2=486 DTCs.

[0121] FIG. 10 is a diagram showing the structure of an unused response message according to one embodiment.

[0122] As illustrated in FIG. 10, the response message (12_1) may include a packet size information area (121), a packet identification information area (122), and a data area (Data Information) (123_1). The description of the packet size information area (121) and the packet identification information area (122) illustrated in FIG. 10 may be the same as the description of the packet size information area (121) and the packet identification information area (122) illustrated in FIG. 7. Hereinafter, descriptions of parts of the descriptions regarding the packet size information area (121) and the packet identification information area (122) that overlap with the previously described descriptions may be omitted.

[0123] The number shown in Fig. 10 can be expressed in hexadecimal as 1 byte, and the size of the data shown as one cell in the request message (11_1) can be 1 byte.

[0124] The response message (12_1) illustrated in FIG. 10 may be a response to a request message (11_1) in which the response type identifier (1132) illustrated in FIG. 8 is 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.

[0125] First, the case where the communication channel identifier (1131) of the request message (11_1) is the first communication channel will be explained.

[0126] The data area (123_1) may correspond to multiple byte areas starting from Byte 4. In FIG. 4, the data area (113_1) is depicted as a region corresponding to 5 Bytes from Byte 4 to Byte 8, but this is for convenience of explanation and the embodiment is not limited thereto.

[0127] The data area (123_1) may include DTC information requested to be read in the request message (11_1) and a diagnostic result corresponding to the requested DTC. Here, the diagnostic result corresponding to the requested DTC may include an FDC value for the DTC information.

[0128] The MCU (200) can record DTC information included in Bytes 5 through 7 of the request message (11_1) in Bytes 4 through 6 of the data area (123_1), and record FDC corresponding to the DTC recorded in Bytes 4 through 6 in Byte 7 of the data area (123_1).

[0129] For example, "0A0001" may be written to Bytes 4 through 6 of the data area (123_1), and "0x27", which is an FDC corresponding to "0A0001", may be written to Byte 7 of the data area (123_1).

[0130] Next, the case where the communication channel identifier (1131) of the request message (11_1) is the second communication channel is described.

[0131] When 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, an FDC for each of the multiple DTC information, and classification information in the area from Byte 5 to Byte 64. Here, the classification information may be dummy data for distinguishing the multiple DTC information or the FDC corresponding to the multiple DTC information. The BMS (310) may configure the data area (123_1) by arranging each of the multiple DTCs included in the request message (11_1) and the FDC corresponding to each DTC in order.

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

[0133] For example, Bytes 5 through 7 contain first DTC information, Byte 8 contains an FDC value corresponding to the first DTC information, and Byte 9 may contain classification information. Bytes 10 through 12 contain second DTC information, Byte 13 contains an FDC value corresponding to the second DTC information, and Byte 14 may contain classification information. Bytes 15 through 17 contain third DTC information, Byte 18 contains an FDC value corresponding to the third DTC information, and Byte 19 may contain classification information. Bytes 20 through 22 contain fourth DTC information, Byte 23 contains an FDC value corresponding to the fourth DTC information, and Byte 24 may contain classification information.

[0134] In the case of using the first type that does not use a bitmap, the length of the response message to the request message (11_1) requesting four DTC information may be 24 Bytes.

[0135] Although embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modified and improved forms by those skilled in the art to which the present invention pertains also fall within the scope of the present invention. Explanation of the symbols

[0136] 10: Vehicle 20: Battery System 100: Electronic Control Unit (ECU) 110, 210: Communications Department 120, 220: Memory 200: Main Control Unit (MCU) 300: Battery pack 310: Battery Management System (BMS)

Claims

Claim 1 A method for a battery system to transmit and receive FDC (Fault Detection Counter) information regarding a DTC (Diagnostic Trouble Code), comprising the step of receiving a request message; A method for transmitting and receiving DTC information, comprising the step of transmitting a response message corresponding to the request message, wherein the data area of ​​the request message includes a data separator and diagnostic information data, wherein the data separator is a first type requesting an FDC read corresponding to each of at least one DTC information included in the request message or a second type requesting a plurality of FDC reads according to a bitmap, and the bitmap is a list in which the plurality of DTC diagnostic information is matched with a plurality of bits constituting the diagnostic information data, and when the data separator 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 the bits that are first values ​​among the binary data are matched to a plurality of first DTCs based on the bitmap, and the plurality of first DTCs include a DTC that is matched to a first bit based on the bitmap and a DTC that is matched to a second bit greater than the first bit, wherein the data area of ​​the response message includes a data area in which an FDC corresponding to the DTC that is matched to the first bit and an FDC corresponding to the DTC that is matched to the second bit are arranged in succession. Claim 2 delete Claim 3 A method for transmitting and receiving DTC information according to claim 1, wherein the data area of ​​the response message includes a plurality of FDCs corresponding to the plurality of first DTCs. Claim 4 delete Claim 5 A method for transmitting and receiving DTC information, wherein, in the case where the type of response is the first type, the diagnostic information data includes first DTC information and second DTC information. Claim 6 A method for transmitting and receiving DTC information according to claim 5, wherein the data area of ​​the response message is configured to be arranged in the order of 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. Claim 7 A battery pack comprising a plurality of battery cells in a battery system that transmits and receives FDC (Fault Detection Counter) information regarding a vehicle and a DTC (Diagnostic Trouble Code); The system includes a Battery Management System (BMS) that manages the battery pack, wherein the BMS receives a request message from the vehicle and transmits a response message corresponding to the request message to the vehicle, wherein the data area of ​​the request message includes a data separator and diagnostic information data, wherein the data separator is a first type requesting an FDC read corresponding to each of at least one DTC information included in the request message or a second type requesting a plurality of FDC reads according to a bitmap, wherein the bitmap is a list in which a plurality of DTC diagnostic information is matched with a plurality of bits constituting the diagnostic information data, and when the data separator 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, wherein among the plurality of bits represented by the binary data, a plurality of first bits that match the plurality of DTC diagnostic information to be read among the plurality of bits based on the bitmap are a first value, and among the plurality of bits, the remaining plurality of bits excluding the plurality of first bits are a second value, and wherein the plurality of first DTCs are a DTC that matches the first bit based on the bitmap and a second bit that is greater than the first bit A battery system comprising a DTC, wherein the BMS arranges in succession an FDC corresponding to a DTC matched to the first bit and an FDC corresponding to a DTC matched to the second bit to form a data area of ​​the response message. Claim 8 delete Claim 9 In claim 7, the data area of ​​the response message comprises a plurality of FDCs corresponding to the plurality of first DTCs, in a battery system. Claim 10 delete Claim 11 In claim 7, if the type of the above response is the above first type, the above diagnostic information data includes the first DTC information and the second DTC information, a battery system. Claim 12 A battery system according to claim 11, wherein the BMS configures the data area of ​​the response message 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 that order.

Images