Method for transmitting and receiving FDC (Fault Detection Counter) information for DTC (Diagnostic Trouble Code) and battery system using the same

Abstract

The present invention relates to a method for transmitting and receiving FDC (Fault Detection Counter) information for DTC (Diagnostic Trouble Code) and a battery system to which the same is applied. According to one aspect of the invention, a battery system for transmitting and receiving FDC (Fault Detection Counter) information for DTC (Diagnostic Trouble Code) includes the steps of receiving a request message and transmitting a response message corresponding to the request message, wherein a data field of the request message includes a data segment and diagnostic information data, and the data segment is of a first type requesting the reading of an FDC corresponding to at least one DTC included in the request message or a second type requesting the reading of multiple FDCs according to a bitmap, and the bitmap may be a list in which multiple DTC diagnostic information matches multiple bits constituting the diagnostic information data.

Description

[Technical Field]

[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] This application claims the benefit of priority based on Korean Patent Application No. 10-2023-0092579, dated July 17, 2023, and all contents disclosed in the documents of this Korean patent application are incorporated herein by reference.

[0002] The present disclosure relates to a method for transmitting and receiving FDC (Fault Detection Counter) information for DTC (Diagnostic Trouble Code) and a battery system to which the same is applied. [Background technology]

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

[0004] However, recently, diagnostic information for checking thermal events and isolation events in batteries requires reading and checking multiple statuses simultaneously at a specific point in time. Summary of the Invention [Problem to be solved by the invention]

[0005] The present invention provides a method for transmitting and receiving FDC (Fault Detection Counter) information for DTCs (Diagnostic Trouble Codes), which can display multiple DTCs and their corresponding FDCs as a single message when transmitting and receiving FDC information for DTCs, and a battery system to which the method is applied. [Means for solving the problem]

[0006] A method for transmitting and receiving FDC (Fault Detection Counter) information for DTC (Diagnostic Trouble Code) in a battery system according to one aspect of the invention includes the steps of receiving a request message and transmitting a response message corresponding to the request message, wherein a data field of the request message includes a data segment and diagnostic information data, the data segment being of a first type requesting the reading of an FDC corresponding to at least one DTC information included in the request message, or a second type requesting the reading of multiple FDCs according to a bitmap, and the bitmap being a list in which multiple DTC diagnostic information matches multiple bits constituting the diagnostic information data.

[0007] When the data division element is the second type, the diagnostic information data includes binary data in which a binary value corresponds to each of the plurality of bits, and a bit having a first value among the binary data can be matched to a plurality of first DTCs based on the bitmap.

[0008] The data field of the response message may include a plurality of FDCs corresponding to the plurality of first DTCs.

[0009] When the plurality of first DTCs include a DTC that matches a first bit based on the bitmap and a DTC that matches a second bit that is greater than the first bit, the data field of the response message may include a data field in which FDCs corresponding to the DTCs that match the first bit and FDCs corresponding to the DTCs that match the second bit are arranged consecutively.

[0010] When the response type is the first type, the diagnostic information data may include first DTC information and second DTC information.

[0011] The data field of the response message may be 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.

[0012] Another feature of the invention is a battery system that transmits and receives Fault Detection Counter (FDC) information for Diagnostic Trouble Codes (DTCs) to and from a vehicle, the battery system including a battery pack including a plurality of battery cells and a Battery Management System (BMS) that manages the battery pack, the BMS receiving a request message from the vehicle and transmitting a response message corresponding to the request message to the vehicle, the data field of the request message including a data segment and diagnostic information data, the data segment being of a first type that requests reading of an FDC corresponding to each of at least one DTC information included in the request message or a second type that requests reading of a plurality of FDCs according to a bitmap, the bitmap being a list in which a plurality of DTC diagnostic information matches a plurality of bits that constitute the diagnostic information data.

[0013] When the data division number is 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 indicated by the binary data, a plurality of first bits that match a plurality of DTC diagnostic information requested to be read based on the bitmap are first values, and the remaining plurality of bits excluding the plurality of first bits are second values, and the plurality of first bits can match a plurality of second DTCs based on the bitmap.

[0014] The data field of the response message may include a plurality of FDCs corresponding to the plurality of first DTCs.

[0015] When the plurality of first DTCs 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 field of the response message by consecutively arranging the FDCs corresponding to the DTCs that match the first bit and the FDCs corresponding to the DTCs that match the second bit.

[0016] When the response type is the first type, the diagnostic information data may include first DTC information and second DTC information.

[0017] The BMS may configure a data field 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 this order. [Effects of the Invention]

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

[0019] According to an embodiment of the present invention, when using a CAN FD channel, data can be transmitted by the DTC amount, allowing for the use of a flexible data buffer.

[0020] If the response message contains one FDC corresponding to each DTC, accurate vehicle diagnosis may be difficult due to the time interval between the reception of each response message packet. According to one embodiment of the present invention, the response message contains multiple FDC information, allowing multiple data indicating the vehicle's status at a specific point in time to be checked and diagnosed at once. [Brief explanation of the drawings]

[0021] [Figure 1]FIG. 1 is a diagram showing a vehicle and a battery system to which an embodiment is applied. [Figure 2] FIG. 2 is a diagram showing a partial configuration of a vehicle according to an embodiment. [Figure 3] FIG. 3 is a diagram showing a configuration of a part of a battery system according to one embodiment. [Figure 4] FIG. 4 is a diagram illustrating a structure of a request message using a bitmap according to an embodiment. [Figure 5] FIG. 5 is a diagram showing the structure of the data area in FIG. [Figure 6] FIG. 6 is an example of a bitmap showing multiple bits corresponding to multiple DTCs according to one embodiment. [Figure 7] FIG. 7 is a diagram illustrating a structure of a response message using a bitmap according to one embodiment. [Figure 8] FIG. 8 is a diagram illustrating a structure of a request message without using a bitmap according to an embodiment. [Figure 9] FIG. 9 is a diagram showing the structure of the data area in FIG. [Figure 10] FIG. 10 is a diagram illustrating a structure of a response message that does not use a bitmap according to one embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0022] Hereinafter, the embodiments disclosed herein will be described in detail with reference to the accompanying drawings. Identical or similar elements will be designated by identical or similar drawing numbers, and redundant descriptions thereof will be omitted. The suffixes "module" and / or "unit" used in the following description for elements are given or used interchangeably solely for ease of description and do not have any distinct meanings or functions. Furthermore, in describing the embodiments disclosed herein, if a detailed description of related prior art is deemed to obscure the gist of the embodiments disclosed herein, such a detailed description will be omitted. Furthermore, the accompanying drawings are merely intended to facilitate understanding of the embodiments disclosed herein, and the accompanying drawings should not be construed as limiting the technical concepts disclosed herein, and should be understood to include all modifications, equivalents, or alternatives within the concept and technical scope of the present invention.

[0023] Terms including ordinal numbers such as "first," "second," etc. may be used to describe various components, but the components are not limited by the terms. The terms are used only to distinguish one component from another.

[0024] When a component is said to be "coupled" or "connected" to another component, it should be understood that it can be directly coupled or connected to the other component, but that there may be other components in between. Conversely, when a component is said to be "directly coupled" or "directly connected" to another component, it should be understood that there are no other components in between.

[0025] In this application, the use of terms such as "comprise" or "have" is intended to specify the presence of any feature, number, step, operation, component, part, or combination thereof stated in the specification, but should be understood as not precluding the presence or possible addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

[0026] FIG. 1 is a diagram showing a vehicle and a battery system to which an embodiment is applied.

[0027] The vehicle 10 may transmit a request message to the battery system 20 to acquire diagnostic trouble code (DTC) related information (hereinafter, DTC information) (S10).

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

[0029] 1 shows a vehicle and a battery system as an example of a diagnostic target that transmits and receives messages to and from a diagnostic device, but the invention is not limited thereto. An embodiment can be applied to a device that can diagnose a battery, such as a battery system, and store information about the results of the diagnostic execution.

[0030] FIG. 2 is a diagram showing a partial configuration of a vehicle according to an embodiment.

[0031] As shown in FIG. 2, the vehicle 10 may include an electronic control unit (ECU) 100 , a communication unit 110 , and a memory 120 .

[0032] The ECU 100 generates a request message, collects necessary data from the 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 on a DTC belonging to a specific DTC state and an FDC (Fault Detection Counter) corresponding to the DTC.

[0033] The communication unit 110 may transmit a request message to an external device and receive a response message to the request message. For example, the communication unit 110 may transmit a request message to the battery system 20 and receive a response message from the battery system 20.

[0034] The memory 120 can store data collected from the response message by the ECU 100. The memory 120 can store data required for the ECU 100 to generate a request message, control the operation of the vehicle 10, and the like.

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

[0036] 3 , the battery system 20 may include a battery pack 300 including 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.

[0037] The MCU 200 performs a diagnosis in response to 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 310.

[0038] The communication unit 210 receives a request message and transmits a response message to the outside. For example, the communication unit 210 may receive a request message from the vehicle 10 and transmit a response message to the vehicle 10.

[0039] The memory 220 stores the diagnostic content and the results of the diagnostics. The MCU 200 can detect and read necessary information from the memory 220 and generate a response message. The memory 220 can store data necessary for the MCU 200 to control the BMS 310.

[0040] 2 and 3 show only the components necessary to explain one embodiment, and components not shown in Figures 2 and 3 may be included in the vehicle and battery system.

[0041] FIG. 4 is a diagram illustrating a structure of a request message using a bitmap according to an embodiment.

[0042] As shown in Fig. 4, the request message 11 can include a packet size information field 111, a packet identification information field 112, and a data field (Data Information) 113. The numbers shown in Fig. 4 are hexadecimal numbers and can be expressed as 1 byte, and the size of data shown as one cell in Fig. 4 can be 1 byte.

[0043] The packet size information area 111 may include a data length code (DLC). The DLC may define the combined size of the data amount in the packet identification information area 112 and the data area 113 of the request message. For example, as shown in FIG. 4, "0x05" recorded in the first byte area of ​​the packet size information area 111 may indicate that the combined size of the data amount in the packet identification information area 112 and the data area 113 is 5 bytes.

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

[0045] 4, "0x19" recorded in the second 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. In other words, when "0x19" is the service identifier, the message may be a message requesting a service from the ECU 100 to read DTC information stored in the BMS 310. In response to this request, the BMS 310 can read the stored DTC information and transmit it to the ECU 100. At this time, the BMS 310 needs information to identify which DTC information to read from among the multiple stored DTC information.

[0046] 4, "0x06" recorded in the third 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. In other words, when "0x06" is the data identifier in a request message, the request message may be a message in which the ECU 100 requests FDC data from the DTC information stored in the BMS 310. In response to this request, the BMS 310 can read the FDC for the stored DTC and transmit it to the ECU 100.

[0047] The data area 113 can correspond to a plurality of byte areas starting from Byte No. 4. In FIG. 4, the data area 113 is shown as an area corresponding to three bytes, namely Bytes Nos. 4, 5, and 6, but this is for convenience of explanation and the embodiment is not limited thereto.

[0048] FIG. 5 is a diagram showing the structure of the data area in FIG.

[0049] Referring to FIG. 5, the data area 113 corresponds to a plurality of bytes, and bits constituting each of the plurality of bytes may include a value for identifying the DTC requesting reading.

[0050] The numbers shown in FIG. 5 are binary numbers and can be represented as 1 bit, and the size of data shown as one cell in FIG. 5 can be 1 bit.

[0051] The following description will be given assuming that the data area 113 is a 3-byte area as shown in FIG.

[0052] The data field 113 may include request data 1130 that can identify the DTC that is requested to be read. The request data 1130 may be binary data arranged in descending bit order in the data field 113. As shown in FIG. 5, an example of the request data 1130 may be 24-bit binary data "11000000 00000000 00001011" from the data corresponding to the 23rd bit to the data corresponding to the 0th bit.

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

[0054] The communication channel identifier 1131 can identify a communication channel through which the response message is received. The communication channel through which the response message is received can be any one of a plurality of communication channels. The plurality of communication channels can include a first communication channel and a second communication channel.

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

[0056] Specifically, the first communication channel may be a channel configured such that the total amount of data of message packets that can be transmitted at one time is smaller than the total amount of data of message packets that can be transmitted 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.

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

[0058] For example, as shown in FIG. 5, a "1" recorded in the 23rd bit indicating the communication channel identifier 1131 may indicate that the communication channel of the request message 11 is the second communication channel.

[0059] The response type identifier 1132 may identify a requested data segment. The data segment may be one of a plurality of types. The plurality of types may include a first type and a second type.

[0060] The first type may be a type that requests the reading of an 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 the reading of an FDC corresponding to each of 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 items are matched with multiple bits. The DTC diagnostic information may include DTC information, the name of the diagnosis indicated by the DTC information, etc.

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

[0062] 5, the communication channel identifier 1131 and the response type identifier 1132 are each shown as a binary number corresponding to one 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 a hexadecimal number corresponding to one byte.

[0063] Hereinafter, the case where the data division element is of the second type will be described with reference to FIGS.

[0064] 5, when the data segment is of the second type, the data information 1133 may include diagnostic information data consisting of a plurality of bits. The diagnostic information data may be binary data in which a binary value corresponds to each of the plurality of bits. The diagnostic information data may include a plurality of DTCs to be read.

[0065] Among the plurality of bits indicated by the diagnostic information data, bits having a first value (e.g., "1") may match the plurality of DTC information requested to be read based on the bitmap, and among the plurality of bits indicated by the diagnostic information data, the remaining bits, excluding the bits matching the plurality of DTC information requested to be read, may be a second value (e.g., "0").

[0066] FIG. 6 is an example of a bitmap showing multiple bits corresponding to multiple DTCs according to one embodiment.

[0067] The order of the multiple bits included in the bitmap can be arranged in ascending or descending order, and each bit can correspond to and match any one of the multiple DTCs.

[0068] Referring to FIG. 6, the bitmap may be a list of the numbers of the bits indicated by the diagnostic information data, the DTCs, and the names of the diagnoses indicated by the DTCs. Multiple DTC diagnostic information items indicated by multiple DTC information items may correspond to multiple bits. As shown in FIG. 6, "OA0001-OA0008," "0B0B00," "0B3C01-0B3C06," and "0C0A00-0C0A06" may be examples of multiple DTCs.

[0069] An example of the bitmap shown in FIG. 6 will now be described.

[0070] Bit 0 can match DTC "0A0001" indicating the diagnosis name "DTC Module Error #1", bit 1 can match DTC "0A0002" indicating the diagnosis name "DTC Module Error #2", bit 2 can match DTC "0A0003" indicating the diagnosis name "DTC Module Error #3", bit 3 can match DTC "0A0004" indicating the diagnosis name "DTC Module Error #4", bit 4 can match DTC "0A0005" indicating the diagnosis name "DTC Module Error #5", and bit 5 can match DTC "0A0006" indicating the diagnosis name "DTC Module Error #6". The sixth bit can match the DTC "0A0007" indicating the diagnosis name "DTC Module Error #7," and the seventh bit can match the DTC "0A0008" indicating the diagnosis name "DTC Module Error #8." Among the diagnosis names, names including "DTC Module Error" can indicate a specific error that has occurred in each of the multiple battery modules included in the battery pack 300.

[0071] Bit 8 can match DTC "0B0B00" indicating the diagnosis name "DTC cell Error #1." Bit 9 can match DTC "0B3C01" indicating the diagnosis name "DTC cell Error #2." Bit 10 can match DTC "0B3C02" indicating the diagnosis name "DTC cell Error #3." Bit 11 can match DTC "0B3C03" indicating the diagnosis name "DTC cell Error #4." Bit 12 can match DTC "0B3C04" indicating the diagnosis name "DTC cell Error #5." Bit 13 can match DTC "0B3C05" indicating the diagnosis name "DTC cell Error #6." Bit 14 can match DTC "0B3C06" indicating the diagnosis name "DTC cell Error #7." Among the names of diagnoses, a name including “DTCcellError” may indicate a predetermined error that has occurred in each of the plurality of battery cells included in the battery pack 300.

[0072] The 15th bit can match the DTC "0C0A00" indicating the diagnosis name "DTC_CELL_SENSE_OPEN", the 16th bit can match the DTC "0C0A01" indicating the diagnosis name "DTC_CELL_SENSE_OPEN", the 17th bit can match the DTC "0C0A02" indicating the diagnosis name "DTC_CELL_SENSE_OPEN", and the 18th bit can match the DTC "0C0A03" indicating the diagnosis name "DTC_CELL_SENSE_OPEN". The 19th bit may match DTC "0C0A04" indicating the diagnosis name "DTC_CELL_SENSE_OPEN," the 20th bit may match DTC "0C0A05" indicating the diagnosis name "DTC_CELL_SENSE_OPEN," and the 21st bit may match DTC "0C0A06" indicating the diagnosis name "DTC_CELL_SENSE_OPEN." Among the diagnosis names, a name including "DTC_CELL_SENSE_OPEN" may indicate a predetermined error that occurred in sensing cell information (e.g., cell voltage, cell temperature, cell current, etc.) of each of the multiple battery cells included in the battery pack 300.

[0073] Each of the multiple DTC diagnostic information indicated by the bitmap may indicate a battery condition such as temperature, voltage, isolation error, communication error, abnormal operation, etc. for each of the multiple battery cells included in the battery pack 300 and / or each of the multiple battery modules included in the battery pack 300.

[0074] In this way, each bit constituting the diagnostic information data can correspond to a bit number in the bitmap. Bits 21 to 0 in the data information 1133 shown in Figure 5 can correspond to bits 21 to 0 in the bitmap shown in Figure 6. For example, bit 21 in the data information 1133 shown in Figure 5 can record data corresponding to DTC "0C0A06," which corresponds to bit 21 in the bitmap shown in Figure 6.

[0075] 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, a DTC that matches a bit recorded with the first value according to the bitmap may indicate that the DTC requested in the request message 11 is the DTC being read.

[0076] In the data information 1133 shown in FIG. 5, the data of bits 0, 1, and 3 are "1" and the remaining bits are "0," so the request message 11 including such data information 1133 indicates a state requesting reading of DTCs "0A0001," "0A0002," and "0A0004," which match bits 0, 1, and 3 in the bit map shown in FIG. 6.

[0077] In one embodiment, the request message 11 can request multiple DTC information as one data packet using a bitmap, and the length of the data field 113 can be increased or decreased depending on the number of bits indicated by the bitmap.

[0078] In a method that does not use a bitmap, a request message may contain at least one DTC in a packet, requiring at least 3 bytes of space for each DTC. Therefore, a request message requesting information on five DTCs may require five packets, each containing one DTC, or one packet containing five DTCs, requiring at least 3 x 5 = 15 bytes of space.

[0079] In contrast, in one embodiment using a bitmap, the DTC itself is not included in the message, but is identified by toggling bits already defined by the bitmap, thereby reducing the size of the data area 113.

[0080] In one embodiment, if the bitmap is a list indicating bits matching DTCs whose number is greater than 8×(m−1)−2 but not greater than 8×(m)−2, it is sufficient for the length of the data field 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 each corresponding to one bit. If the communication channel identifier 1131 and the response type identifier 1132 are k bits, and the bitmap is a list indicating bits matching DTCs whose number is greater than 8×(m−1)−2×k but not greater than 8×(m)−2×k, the request message 11 may require an m-byte data field 113. Here, m is a natural number greater than or equal to 2, and k is a natural number greater than or equal to 1.

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

[0082] FIG. 7 is a diagram illustrating a structure of a response message using a bitmap according to one embodiment.

[0083] As shown in Fig. 7, the response message 12 can include a packet size information field 121, a packet identification information field 122, and a data field 123. The numbers shown in Fig. 7 are hexadecimal numbers and can be expressed as 1 byte, and the size of data shown as one cell in Fig. 7 can be 1 byte.

[0084] The packet size information area 121 may include a data length code DLC. The DLC may define the combined size of the data amount in the packet identification information area 122 and the data area 123 of the response message. For example, as shown in FIG. 7, "0x05" recorded in the first byte area of ​​the packet size information area 121 may indicate that the combined size of the data amount in the packet identification information area 122 and the data area 123 is 5 bytes.

[0085] The packet identification information area 122 corresponds to an area of ​​2 bytes or more, and a service identifier (Service ID) can be 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.

[0086] 7, "0x59" recorded in the second byte area of ​​the packet identification information area 122 may be an example of a service identifier (DTC Read Information Positive Response Service ID) indicating a response including DTC information. In other words, when "0x59" is the service identifier, the message may be a message in which the ECU 100 responds with the DTC information stored in the BMS 310.

[0087] 7, "0x06" recorded in the third 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 the DTC. In other words, if "0x06" is the data identifier in a response message, the message may be a message indicating FDC data among the DTC information stored in the BMS 310.

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

[0089] For example, if the first and second bits of the multiple bits included in the data field 113 of the request message 11 are "1" and the remaining bits are 0, the BMS 310 can configure the first byte of the multiple bytes included in the data field 123 of the response message 12 to include an FDC corresponding to a DTC that matches the first bit, and the second byte to include an FDC corresponding to a DTC that matches the second bit. Here, if the second bit is larger than the first bit, the BMS 310 can configure the data field 123 by consecutively arranging the first and second bytes.

[0090] 7, it will be explained that n is 3. The BMS 310 can configure the data area 123 by consecutively arranging n FDCs for n DTCs.

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

[0092] The MCU 200 can sort n pieces of DTC information so that matching bit numbers are in ascending order based on the bitmap, and arrange the FDCs for each DTC information consecutively in n bytes in the data area 113 according to the sorting order.

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

[0094] 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 consecutively in the bit number order.

[0095] For example, assume that the request message 11 requests DTC information that matches bits 0, 1, and 3 based on the 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. In accordance with the sorting order, the MCU 200 can record the FDC for DTC "0A0001" in the fourth byte of the data area 123, the FDC for "0A0002" in the fifth byte, and the FDC for "0A0004" in the sixth byte.

[0096] As shown in Figure 7, "0x27" recorded in the fourth byte area of ​​data area 123 indicates an example of an FDC for DTC "0A0001", "0x80" recorded in the fifth byte area of ​​data area 123 indicates an example of an FDC for DTC "0A0002", and "0x7F" recorded in the sixth byte area of ​​data area 123 indicates an example of an FDC for DTC "0A0004".

[0097] In a method that does not use a bitmap, a response message may require a relatively large amount of data, including DTC information (DTC) and its corresponding status information (FDC) in the data field. Also, in a response to a request to read multiple DTC information, each of multiple packets may include one of the multiple DTCs and its corresponding FDC. In this case, gaps may occur between the generation points of multiple packets indicating responses to the request to read multiple DTC information.

[0098] In contrast, in one embodiment using a bitmap, the DTC itself does not need to be included in the response message 12; instead, multiple FDCs can be included in one packet in the order sorted by the bit numbers indicated by the bitmap. This allows the response message 12 to transmit multiple pieces of status information simultaneously as a single packet, thereby reducing distortion due to gaps and delays.

[0099] Hereinafter, the case where the data division element is the first type will be described with reference to FIGS.

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

[0101] FIG. 8 is a diagram illustrating a structure of a request message without using a bitmap according to an embodiment.

[0102] As shown in Fig. 8, the request message 11_1 may include a packet size information field 111, a packet identification information field 112, and a data field (Data Information) 113_1. The description of the packet size information field 111 and the packet identification information field 112 shown in Fig. 8 may be the same as the description of the packet size information field 111 and the packet identification information field 112 shown in Fig. 4. Hereinafter, the description of the packet size information field 111 and the packet identification information field 112 that overlaps with the above description may be omitted.

[0103] The numbers shown in FIG. 8 are hexadecimal numbers and can be expressed as 1 byte, and the size of the data indicated as one cell in the request message 11_1 can be 1 byte.

[0104] The data area 113_1 can correspond to a plurality of byte areas starting from Byte No. 4. In Fig. 8, the data area 113_1 is shown as an area corresponding to five bytes from Byte No. 4 to Byte No. 8, but this is for convenience of explanation and the embodiment is not limited thereto.

[0105] FIG. 9 is a diagram showing the structure of the data area in FIG.

[0106] Referring to FIG. 9, the data area 113_1 corresponds to a plurality of bytes, and bits constituting each of the plurality of bytes may include a value for identifying the DTC requesting reading.

[0107] The numbers shown in FIG. 9 are binary numbers and can be represented as 1 bit, and the size of the data shown as one cell in FIG. 9 can be 1 bit.

[0108] The following description will be given on the assumption that the data area 113_1 is a 5-byte area from the 4th byte to the 8th byte as shown in FIG.

[0109] The data field 113_1 may include request data 1130_1 that can identify the DTC requesting reading. The request data 1130_1 may be binary data arranged in descending bit order in the data field 113.

[0110] 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.

[0111] For example, as shown in FIG. 9, a '0' recorded in bit 6 indicating the response type identifier 1132_1 may indicate that the data segment is of the first type.

[0112] 9, when the data segment is the first type, the data information 1133_1 can 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 to 5) of the fourth byte are “0”, and the fifth, sixth, and seventh bytes can include one DTC information.

[0113] If 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.

[0114] Therefore, 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 item corresponding to the fifth, sixth, and seventh bytes. The one DTC information item may indicate code information of a DTC requesting FDC reading. For example, the one DTC information item may be "0A0001." When the response type identifier 1132 is the first type, the request message 11 may further include classification information. Here, the classification information may be dummy data for classifying multiple DTC information items.

[0115] For example, bytes 5 to 7 may contain first DTC information, and byte 8 may contain classification information. In this way, the first type of request message 11 using the first communication channel and not using a bitmap can request reading of an FDC corresponding to up to one DTC.

[0116] Also, 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 the reading of FDCs corresponding to each of a plurality of DTCs using multiple bits from Byte 4 to Byte 8. In this case, since the data area of ​​the request message 11 is 5 bytes, the second type request message 11 using the first communication channel and the bitmap can request the reading of FDCs corresponding to a maximum of 8 × 5 - 2 = 38 DTCs.

[0117] If 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.

[0118] 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 can include multiple DTC information and classification information in the area from byte 5 to byte 64.

[0119] For example, bytes 5 to 7 contain first DTC information, byte 8 contains classification information, bytes 9 to 11 contain second DTC information, byte 12 contains classification information, bytes 13 to 15 contain third DTC information, byte 16 contains classification information, bytes 17 to 19 contain fourth DTC information, and byte 20 contains classification information.

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

[0121] Also, when 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 the reading of FDCs corresponding to each of a plurality of 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 second type request message 11 using the second communication channel and the bitmap can request the reading of FDCs corresponding to a maximum of 8 × 61 - 2 = 486 DTCs.

[0122] FIG. 10 is a diagram illustrating a structure of a response message that does not use a bitmap according to one embodiment.

[0123] As shown in Fig. 10, the response message 12_1 may include a packet size information field 121, a packet identification information field 122, and a data field (Data Information) 123_1. The description of the packet size information field 121 and the packet identification information field 122 shown in Fig. 10 may be the same as the description of the packet size information field 121 and the packet identification information field 122 shown in Fig. 7. Hereinafter, the description of the packet size information field 121 and the packet identification information field 122 that overlaps with the above description may be omitted.

[0124] The numbers shown in FIG. 10 are hexadecimal numbers and can be expressed as 1 byte, and the size of the data indicated as one cell in the request message 11_1 can be 1 byte.

[0125] The response message 12_1 shown in Fig. 10 may be a response to the request message 11_1 shown in Fig. 8, whose response type identifier 1132 is type 1. Even when the response type identifier 1132 is type 1, the communication channel identifier 1131 may be the first communication channel or the second communication channel.

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

[0127] The data area 123_1 can correspond to a plurality of byte areas starting from Byte No. 4. In Fig. 10, the data area 123_1 is shown as an area corresponding to five bytes from Byte No. 4 to Byte No. 8, but this is for convenience of explanation and the embodiment is not limited thereto.

[0128] The data field 123_1 may include DTC information requested to be read in the request message 11_1 and a diagnostic result corresponding to the DTC, where the diagnostic result corresponding to the DTC may include an FDC value for the DTC information.

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

[0130] For example, "0A0001" may be recorded in bytes 4 to 6 of the data area 123_1, and "0x27", which is the FDC corresponding to "0A0001", may be recorded in byte 7 of the data area 123_1.

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

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

[0133] For example, if the diagnostic information data excluding the classifier information in the data field 113_1 of the request message 11_1 includes first DTC information and second DTC information, the BMS 310 may configure the data field 123_1 of the response message 12_1 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 this order. Here, the classifier information in the data field 113_1 may include a communication channel identifier 1131 that is a second communication channel and a response type identifier 1132 that is a second type.

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

[0135] In this way, when the first type that does not use a bitmap is used, the length of the response message to the request message 11_1 requesting four pieces of DTC information can be 24 bytes.

[0136] Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited to these examples, and various modifications and improvements made by those skilled in the art to which the present invention pertains also fall within the scope of the present invention.

Claims

1. A method for transmitting and receiving FDC information for a DTC in a battery system, comprising: receiving a request message; and transmitting a response message corresponding to the request message; The data field of the request message includes a data segment and diagnostic information data, The data division element is a first type requesting the reading of an FDC corresponding to at least one DTC information included in the request message, or a second type requesting the reading of a plurality of FDCs according to a bitmap; The bitmap is a list in which a plurality of DTC diagnostic information items are matched with a plurality of bits constituting the diagnostic information data. DTC information transmission and reception method.

2. When the data division element 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; The bit of the binary data that is a first value is matching a plurality of first DTCs based on the bitmap; The DTC information transmitting and receiving method according to claim 1.

3. The data area of ​​the response message is a plurality of FDCs corresponding to the plurality of first DTCs; The DTC information transmitting and receiving method according to claim 2.

4. the plurality of first DTCs include a DTC that matches a first bit based on the bitmap and a DTC that matches a second bit that is greater than the first bit; The data area of ​​the response message is a data area in which an FDC corresponding to a DTC matching the first bit and an FDC corresponding to a DTC matching the second bit are consecutively arranged; The DTC information transmitting and receiving method according to claim 2.

5. When the data division element is of the first type, The diagnostic information data includes first DTC information and second DTC information. The DTC information transmitting and receiving method according to any one of claims 1 to 4.

6. The data area of ​​the response message is 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 are arranged in this order. The DTC information transmitting and receiving method according to claim 5.

7. In a battery system that transmits and receives FDC information to and from a vehicle and a DTC, a battery pack including a plurality of battery cells; and a battery management system (BMS) that manages the battery pack; The BMS includes: receiving a request message from the vehicle and transmitting a response message corresponding to the request message to the vehicle; The data field of the request message includes a data segment and diagnostic information data, The data division element is a first type requesting the reading of an FDC corresponding to at least one DTC information included in the request message, or a second type requesting the reading of a plurality of FDCs according to a bitmap; The bitmap is a list in which a plurality of DTC diagnostic information items are matched with a plurality of bits constituting the diagnostic information data. Battery system.

8. When the data division element 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; Among the plurality of bits indicated by the binary data, a plurality of first bits that match a plurality of DTC diagnostic information pieces that are requested to be read based on the bitmap are a first value, and the remaining plurality of bits, excluding the plurality of first bits, are a second value; the plurality of first bits are matched to a plurality of second DTCs based on a bitmap; The battery system of claim 7.

9. The data area of ​​the response message is a plurality of FDCs corresponding to a plurality of first DTCs; The battery system of claim 8.

10. the plurality of first DTCs include a DTC that matches a first bit based on the bitmap and a DTC that matches a second bit that is greater than the first bit; The BMS includes: a data field of the response message is formed by consecutively arranging an FDC corresponding to a DTC that matches the first bit and an FDC corresponding to a DTC that matches the second bit; The battery system of claim 8.

11. When the data division element is of the first type, The diagnostic information data includes first DTC information and second DTC information.

11. A battery system according to any one of claims 7 to 10.

12. The BMS includes: 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 are arranged in this order to form a data field of the response message. The battery system of claim 11.

Images