FDC (fault detection counter) information about DTC (diagnostic trouble code) transceiving method and battery system using same method

Abstract

The present invention relates to a method for transmitting and receiving fault detection counter (FDC) information about diagnostic trouble code (DTC), and a battery system using the method. The method by which the battery system transmits and receives FDC information about DTC, according to one feature of the invention, includes the steps of: receiving a request message; and transmitting a response message corresponding to the request message, wherein a data area of the request message includes a data delimiter and diagnostic information data, the data delimiter is a first type for requesting an FDC read corresponding to each of at least one piece of DTC information included in the request message or a second type for requesting a plurality of FDC reads according to a bitmap, and the bitmap may be a list in which a plurality of pieces of DTC diagnostic information are matched to a plurality of bits configuring the diagnostic information data.

Description

Method for transmitting and receiving FDC information for DTC and battery system applying the same

[0001] Cross-citation with related application(s)

[0002] This application claims the benefit of priority to Korean Patent Application No. 10-2023-0092579, filed July 17, 2023, the entire contents of which are incorporated herein by reference.

[0003] 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 applying the same.

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

[0005] However, diagnostic information for checking recent battery thermal events or isolation events requires reading and checking multiple states simultaneously at a specific point in time.

[0006] The present invention provides a method for transmitting and receiving FDC (Fault Detection Counter) information for a DTC (Diagnostic Trouble Code) that can express multiple DTCs and their corresponding FDCs in a single message, and a battery system applying the method.

[0007] According to one aspect of the invention, a method for transmitting and receiving FDC (Fault Detection Counter) information for a DTC (Diagnostic Trouble Code) by a battery system comprises the steps of receiving a request message, and transmitting a response message corresponding to the request message, wherein a data area of ​​the request message includes a data delimiter and diagnostic information data, and the data delimiter is 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, 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.

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

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

[0010] If the plurality of first DTCs include a DTC matching a first bit based on the bitmap and a DTC matching 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 a DTC matching the first bit and an FDC corresponding to a DTC matching the second bit are arranged consecutively.

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

[0012] The data area of ​​the above 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.

[0013] According to another aspect of the invention, a battery system for transmitting and receiving FDC (Fault Detection Counter) information for a vehicle and a DTC (Diagnostic Trouble Code) includes a battery pack including a plurality of battery cells, and a battery management system (BMS) for managing 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, and a data area of ​​the request message includes a data delimiter and diagnostic information data, and the data delimiter is 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, and the bitmap is a list in which a plurality of DTC diagnostic information matches a plurality of bits constituting the diagnostic information data.

[0014] 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 among the plurality of bits represented by the binary data, a plurality of first bits that match a plurality of DTC diagnostic information to be requested to be read among the plurality of bits based on the bitmap may be a first value, and among the plurality of bits, a plurality of bits remaining except for the plurality of first bits may be a second value.

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

[0016] If the plurality of first DTCs include a DTC matching a first bit based on the bitmap and a DTC matching a second bit greater than the first bit, the BMS can configure a data area of ​​the response message by sequentially arranging an FDC corresponding to the DTC matching the first bit and an FDC corresponding to the DTC matching the second bit.

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

[0018] The BMS may 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.

[0019] According to the present invention, a request message requests DTC information using a bitmap for a plurality of DTC information, and a response message thereto includes all of the plurality of diagnostic information according to the bitmap, so that less data can be used in diagnosing FDC information corresponding to a plurality of DTCs.

[0020] According to the present invention, when utilizing a CAN FD channel, data can be transmitted only as much as the DLC, enabling flexible use of a data buffer.

[0021] If the 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, and according to the present invention, since the response message includes multiple FDC information, multiple data indicating the state of the vehicle at a specific point in time can be checked at once for diagnosis.

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

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

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

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

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

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

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

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

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

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

[0032] Hereinafter, the embodiments disclosed in this specification will be described in detail with reference to the attached drawings. The same or similar components will be given the same or similar drawing reference numerals, and redundant descriptions thereof will be omitted. The suffixes "module" and / or "part" used for components in the following description are given or used interchangeably only for the convenience of writing the specification, and do not in themselves have distinct meanings or roles. In addition, when describing the embodiments disclosed in this specification, if it is determined that a specific description of a related known technology may obscure the gist of the embodiments disclosed in this specification, a detailed description thereof will be omitted. In addition, the attached drawings are only intended to facilitate easy understanding of the embodiments disclosed in this specification, and the technical ideas disclosed in this specification are not limited by the attached drawings, and should be understood to include all modifications, equivalents, and substitutes included in the spirit and technical scope of the present invention.

[0033] Terms that include ordinal numbers, such as first, second, etc., may be used to describe various components, but the components are not limited by these terms. These terms are used solely to distinguish one component from another.

[0034] When a component is referred to as being "connected" or "connected" to another component, it should be understood that it may be directly connected or connected to that other component, but that there may be other components intervening. Conversely, when a component is referred to as being "directly connected" or "connected" to another component, it should be understood that there are no other components intervening.

[0035] In this application, terms such as “include” or “have” are intended to specify the presence of a feature, number, step, operation, component, part or combination thereof described in the specification, but should be understood not to exclude in advance the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts or combinations thereof.

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

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

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

[0039] While FIG. 1 illustrates a vehicle and a battery system as examples of diagnostic devices and diagnostic targets that transmit and receive messages, the invention is not limited thereto. One embodiment may also be applied to a device capable of performing battery diagnostics and storing information on the diagnostic results, such as a battery system.

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

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

[0042] 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 about a DTC belonging to a specific DTC state and an FDC (Fault Detection Counter) corresponding to the DTC.

[0043] The communication unit (110) can transmit a request message to an external source and receive a response message to the request message. For example, the communication unit (110) can transmit a request message to a battery system (20) and receive a response message from the battery system (20).

[0044] The memory (120) can store data collected from a response message by the control unit (100). The memory (120) can store data necessary for the operation of the control unit (100) to generate a request message, control the operation of the vehicle (10), etc.

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

[0046] As illustrated in FIG. 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 circuit (Main Control Unit, MCU) (200), a communication unit (210), and a memory (220).

[0047] The MCU (200) performs a diagnosis according 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 (20).

[0048] 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 a vehicle (10) and transmit a response message to the vehicle (10).

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

[0050] Figures 2 and 3 illustrate only the components necessary to explain one embodiment. Components not illustrated in Figures 2 and 3 may be included in the vehicle and battery system.

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

[0052] 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 numbers illustrated in FIG. 4 are in hexadecimal and may be expressed as 1 byte, and the size of the data illustrated as one block in FIG. 4 may be 1 byte.

[0053] The packet size information area (111) may include a data length code (DLC). The DLC may define the size of the sum of the data amount of the packet identification information area (112) and the data amount of the data area (113) among the request messages. For example, as illustrated in FIG. 4, "0x05" recorded in the 1st Byte area of ​​the packet size information area (111) may indicate that the sum of the data amount of the packet identification information area (112) and the data amount of the data area (113) is 5 Bytes.

[0054] The packet identification information area (112) may correspond to an area of ​​2 bytes or more. A service identifier (Service ID) may be 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).

[0055] 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 for reading 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). According 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) needs information to specify which DTC information among the plurality of stored DTC information to read.

[0056] 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 DTC. That is, if "0x06" is a data identifier in the request message, the request message may be a message in which the ECU (100) requests FDC data among the DTC information stored in the BMS (310). According to this request, the BMS (310) may read the FDC for the stored DTC and transmit it to the ECU (100).

[0057] The data area (113) may correspond to multiple byte areas starting from Byte 4. In Fig. 4, the data area (113) is illustrated as an area corresponding to three bytes, Byte 4, 5, and 6, but this is for convenience of explanation and the embodiment is not limited thereto.

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

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

[0060] The numbers shown in Figure 5 are binary numbers and can be expressed as 1 bit, and the size of the data shown as one cell in Figure 5 can be 1 bit.

[0061] Hereinafter, as shown in Fig. 5, it is assumed that the data area (113) is a 3-byte area.

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

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

[0064] The communication channel identifier (1131) may specify a communication channel through which a response message is to be received. The communication channel through which the response message is to be received may be one of multiple communication channels. The multiple communication channels may include a first communication channel and a second communication channel.

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

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

[0067] The CAN FD channel is a communication standard developed to complement the shortcomings of the CAN channel. It is a communication channel that can contain a maximum amount of data greater than the CAN channel. For example, while a packet transmitted via a CAN channel can contain up to 8 bytes of data, a packet transmitted via a CAN FD channel can contain up to 64 bytes of data.

[0068] For example, as shown in FIG. 5, “1” written in bit 23 indicating a communication channel identifier (1131) may indicate that the communication channel of the request message (11) is the second communication channel.

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

[0070] 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 indicated by a plurality of bits indicated in the request message according to a bitmap. Here, the bitmap may be a list in which a plurality of DTC diagnostic information items are matched to a plurality of bits. The DTC diagnostic information may include DTC information, the name of the diagnosis indicated by the DTC information, etc.

[0071] For example, as illustrated in FIG. 5, a “1” written in bit 22 representing the response type identifier (1132) may indicate that the data delimiter is of the second type.

[0072] Each of the communication channel identifier (1131) and the response type identifier (1132) illustrated in FIG. 5 is illustrated as a binary number corresponding to 1 bit, but this is for convenience of explanation and the invention is not limited thereto. Each of the communication channel identifier (1131) and the response type identifier (1132) may also be a hexadecimal number corresponding to 1 byte.

[0073] Hereinafter, with reference to FIGS. 5 to 7, a case in which the data separator is of the second type will be described.

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

[0075] Among the plurality of bits indicated by the diagnostic information data, bits having a first value (e.g., "1") may be matched to a plurality of DTC information items to be requested to be read based on the bitmap. In addition, among the plurality of bits indicated by the diagnostic information data, bits other than those matching the plurality of DTC information items to be requested to be read may be a second value (e.g., "0").

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

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

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

[0079] Below, an example of the bitmap shown in Fig. 6 is described.

[0080] Bit 0 may match DTC "0A0001" with the diagnostic name "DTC Module Error #1", bit 1 may match DTC "0A0002" with the diagnostic name "DTC Module Error #2", bit 2 may match DTC "0A0003" with the diagnostic name "DTC Module Error #3", bit 3 may match DTC "0A0004" with the diagnostic name "DTC Module Error #4", bit 4 may match DTC "0A0005" with the diagnostic name "DTC Module Error #5", and bit 5 may match DTC "0A0006" with the diagnostic name "DTC Module Error #6". Bit 6 may match DTC "0A0007" indicating the name of the diagnosis "DTC Module Error #7", and bit 7 may match DTC "0A0008" indicating the name of the diagnosis "DTC Module Error #8". Names of the diagnosis that include "DTC Module Error" may indicate a specific error that occurred in each of the plurality of battery modules included in the battery pack (300).

[0081] Bit 8 may match DTC "0B0B00" indicating diagnostic name "DTC cell Error #1", bit 9 may match DTC "0B3C01" indicating diagnostic name "DTC cell Error #2", bit 10 may match DTC "0B3C02" indicating diagnostic name "DTC cell Error #3", bit 11 may match DTC "0B3C03" indicating diagnostic name "DTC cell Error #4", bit 12 may match DTC "0B3C04" indicating diagnostic name "DTC cell Error #5", bit 13 may match DTC "0B3C05" indicating diagnostic name "DTC cell Error #6", and bit 14 may match DTC "0B3C06" indicating diagnostic name "DTC cell Error #7". A name including “DTC cell Error” among the names of the diagnostics may indicate a specific error that has occurred in each of the plurality of battery cells included in the battery pack (300).

[0082] Bit 15 can match DTC "0C0A00" which indicates diagnostic name "DTC_CELL_SENSE_OPEN", bit 16 can match DTC "0C0A01" which indicates diagnostic name "DTC_CELL_SENSE_OPEN", bit 17 can match DTC "0C0A02" which indicates diagnostic name "DTC_CELL_SENSE_OPEN", and bit 18 can match DTC "0C0A03" which indicates diagnostic name "DTC_CELL_SENSE_OPEN". Bit 19 may match DTC "0C0A04" indicating the name of the diagnosis "DTC_CELL_SENSE_OPEN", bit 20 may match DTC "0C0A05" indicating the name of the diagnosis "DTC_CELL_SENSE_OPEN", and bit 21 may match DTC "0C0A06" indicating the name of the diagnosis "DTC_CELL_SENSE_OPEN". A name including "DTC_CELL_SENSE_OPEN" among the names of the diagnosis may indicate a predetermined 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).

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

[0084] 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) illustrated in FIG. 5, bits 21 to 0 can correspond to bits 21 to 0 of the bitmap illustrated in FIG. 6. For example, in the data information (1133) illustrated in FIG. 5, data corresponding to DTC "0C0A06" corresponding to bit 21 of the bitmap illustrated in FIG. 6 can be recorded in bit 21.

[0085] 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 matched according to the bitmap for a bit recorded as the first value may indicate that the request message (11) is a DTC that is requested to be read.

[0086] Among the data information (1133) illustrated in FIG. 5, data of bit 0, bit 1, and bit 3 are “1”, and the remaining bits are “0”, so the request message (11) including 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 illustrated in FIG. 6.

[0087] In one embodiment, the request message (11) can request multiple DTC information as one data packet using a bitmap, and can increase or decrease the length of the data area (113) according to the number of multiple bits indicated by the bitmap.

[0088] In a method that does not use a bitmap, the request message may include at least one DTC in a packet, and may require an area of ​​at least 3 bytes for each DTC. Therefore, a request message requesting information on 5 DTCs may require 5 packets, with each packet including one DTC, or may include 5 DTCs in a packet, requiring an area of ​​at least 3*5=15 bytes.

[0089] In comparison, in one embodiment using a bitmap, the size of the data area (113) can be reduced because the DTC can be specified by toggling a bit defined by the bitmap without including the DTC itself in the message.

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

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

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

[0093] 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 numbers illustrated in FIG. 7 are in hexadecimal and may be expressed as 1 byte, and the size of the data illustrated as one square in FIG. 7 may be 1 byte.

[0094] The packet size information area (121) may include a data length code (DLC). The DLC may define the size of the sum of the data amount of the packet identification information area (122) and the data amount of the data area (123) among the request messages. For example, as illustrated in FIG. 6, "0x05" recorded in the 1st Byte area of ​​the packet size information area (121) may indicate that the sum of the data amount of the packet identification information area (122) and the data amount of the data area (123) is 5 Bytes.

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

[0096] 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) indicating a response including DTC information. That is, if "0x59" is a service identifier, the message may be a message in which the ECU (100) responds to DTC information stored in the BMS (310).

[0097] 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 DTC. That is, if "0x06" is a data identifier in the response message, the message may be a message indicating FDC data among the DTC information stored in the BMS (310).

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

[0099] For example, if the first bit and the second bit among the plurality of bits included in the data area (113) of the request message (11) are “1” and the remaining bits are 0, the BMS (310) can configure the first Byte among the plurality of Bytes included in the data area (123) of the response message (12) to include an FDC corresponding to a DTC matching the first bit, and the second Byte to include an FDC corresponding to a DTC matching 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.

[0100] Referring to Fig. 7, n is described as 3. BMS (310) can configure a data area (123) by sequentially arranging n FDCs for n DTCs.

[0101] 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).

[0102] The MCU (200) can sort n pieces of DTC information in ascending order of matching bit numbers based on a bitmap, and can sequentially arrange FDCs for each piece of DTC information in n bytes of the data area (113) according to the sorting order.

[0103] It can be assumed that 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 a bitmap, the second DTC matches a second bit (e.g., bit 1) greater than the first bit based on the bitmap, and the third DTC matches a third bit (e.g., bit 3) greater than the second bit based on the bitmap.

[0104] 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 sequence according to the bit number order.

[0105] For example, assume that the request message (11) requests DTC information matching 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 matching the three pieces of information are sorted in ascending order. The MCU (200) can record the FDC for DTC "0A0001" in Byte 4 of the data area (123) according to the sorting order, record the FDC for "0A0002" in Byte 5, and record the FDC for "0A0004" in Byte 6.

[0106] As illustrated in FIG. 7, “0x27” written in the 4th Byte area of ​​the data area (123) represents an example of FDC for DTC “0A0001”, “0x80” written in the 5th Byte area of ​​the data area (123) represents an example of FDC for DTC “0A0002”, and “0x7F” written in the 6th Byte area of ​​the data area (123) represents an example of FDC for DTC “0A0004”.

[0107] In a method that does not utilize 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. Furthermore, in 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, a gap may occur between the generation times of multiple packets representing responses to the request to read multiple DTC information.

[0108] In comparison, in one embodiment using a bitmap, multiple FDCs can be included in one packet in the sorted order according to the bit numbers indicated by the bitmap without having to include the DTC itself in the response message (12), and multiple pieces of status information can be transmitted simultaneously in one packet of the response message (12), thereby reducing distortion due to gaps or delays.

[0109] Hereinafter, with reference to FIGS. 8 to 10, a case in which the data separator is of the first type will be described.

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

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

[0112] 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 of the packet size information area (111) and the packet identification information area (112) that overlap with the previous description may be omitted.

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

[0114] The data area (113_1) may correspond to multiple byte areas starting from Byte 4. In Fig. 4, the data area (113_1) is illustrated as an area corresponding to five bytes from Byte 4 to Byte 8, but this is for convenience of explanation and the embodiment is not limited thereto.

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

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

[0117] The numbers shown in Figure 9 are binary numbers and can be expressed as 1 bit, and the size of the data shown as one cell in Figure 9 can be 1 bit.

[0118] Hereinafter, as shown in Fig. 9, it is assumed that the data area (113_1) is a 5-byte area from Byte 4 to Byte 8.

[0119] The data area (113_1) may include request data (1130_1) that can specify a DTC requesting a read. The request data (1130_1) may be binary data arranged in bit descending order in the data area (113).

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

[0121] For example, as illustrated in FIG. 9, a “0” written in bit 6 representing the response type identifier (1132_1) may indicate that the data delimiter is of the first type.

[0122] Referring to FIG. 9, if the data delimiter is of the first type, the data information (1333_1) may include DTC information. For example, as illustrated in FIG. 9, if the second bit of the request data (1130_1) is "0", the remaining bits (bits 0 to 5) of Byte 4 are "0", and Byte 5, Byte 6, and Byte 7 may include one DTC information.

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

[0124] Therefore, if 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 indicate code information of the DTC requesting FDC reading. For example, the one DTC information may be "0A0001." If the response type identifier (1132) is the first type, the request message (11) may further include distinguishing information. Here, the distinguishing information may be dummy data for distinguishing multiple DTC information.

[0125] For example, Byte 5 to 7 may contain first DTC information, and Byte 8 may contain distinction information. In this way, a first type of request message (11) that utilizes the first communication channel and does not utilize a bitmap may request reading of an FDC corresponding to at most one DTC.

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

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

[0128] Therefore, 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 pieces of DTC information and classification information in the area from Byte 5 to Byte 64.

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

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

[0131] In addition, if the communication channel identifier (1131) is a second communication channel and the response type identifier (1132) is a second type, the request message (11) can request reading of FDCs corresponding to each of a plurality of DTCs using multiple bits of Byte 4 to Byte 64. In this case, since the data area of ​​the request message (11) is 61 bytes, the second type of request message (11) using the second communication channel and the bitmap can request reading of FDCs corresponding to a maximum of 8*61-2=486 DTCs.

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

[0133] 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 description of the packet size information area (121) and the packet identification information area (122) that overlap with the previous description may be omitted.

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

[0135] The response message (12_1) illustrated in FIG. 10 may be a response to the request message (11_1) illustrated in FIG. 8, in which the response type identifier (1132) is of the first type. Even when the response type identifier (1132) is of the first type, the communication channel identifier (1131) may be of the first communication channel or the second communication channel.

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

[0137] The data area (123_1) may correspond to multiple byte areas starting from Byte 4. In Fig. 4, the data area (113_1) is illustrated as an area corresponding to five bytes from Byte 4 to Byte 8, but this is for convenience of explanation and the embodiment is not limited thereto.

[0138] 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 corresponding DTC information.

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

[0140] For example, “0A0001” may be recorded in Byte 4 to Byte 6 of the data area (123_1), and “0x27”, which is an FDC corresponding to “0A0001”, may be recorded in Byte 7 of the data area (123_1).

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

[0142] If the communication channel identifier (1131) of the request message (11_1) is the second communication channel and the response type identifier (1132) is the first type, the response message (12_1) may include a plurality of DTC information, an FDC for each of the plurality of DTC information, and identification information in the area from Byte 5 to Byte 64. Here, the identification information may be dummy data for identifying 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 the plurality of DTCs included in the request message (11_1) in the order of each of the DTCs and the FDC corresponding to each DTC.

[0143] For example, if the diagnostic information data excluding the delimiter information in the data area (113_1) of the request message (11_1) includes the first DTC information and the second DTC information, the BMS (310) can configure the data area (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 that order. Here, the delimiter information of the data area (113_1) can include a communication channel identifier (1131) which is a second communication channel and a response type identifier (1132) which is a second type.

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

[0145] 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 pieces of DTC information can be 24 bytes.

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

Claims

1. In a method for transmitting and receiving FDC (Fault Detection Counter) information for DTC (Diagnostic Trouble Code) by a battery system, A step of receiving a request message; and comprising a step of transmitting a response message corresponding to the above request message, The data area of ​​the above request message includes a data delimiter and diagnostic information data. The above data delimiter is 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 multiple FDCs according to a bitmap, The above bitmap is a list in which multiple DTC diagnostic information is matched with multiple bits constituting the diagnostic information data. How to transmit and receive DTC information.

2. In paragraph 1, If the above data separator is of the second type, The above diagnostic information data includes binary data in which a binary value corresponds to each of the plurality of bits, The bits that are the first values ​​of the above binary data are, Matching multiple first DTCs based on the above bitmap How to transmit and receive DTC information.

3. In paragraph 2, The data area of ​​the above response message is: including a plurality of FDCs corresponding to the plurality of first DTCs, How to transmit and receive DTC information.

4. In paragraph 2, If the plurality of first DTCs include a DTC matching a first bit based on the bitmap and a DTC matching a second bit greater than the first bit, The data area of ​​the above response message is: A data area including an FDC corresponding to a DTC matching the first bit and an FDC corresponding to a DTC matching the second bit are arranged consecutively. How to transmit and receive DTC information.

5. In paragraph 1, If the type of the above response is the first type, The above diagnostic information data includes first DTC information and second DTC information, How to transmit and receive DTC information.

6. In paragraph 5, The data area of ​​the above response message is: It is configured and 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. How to transmit and receive DTC information.

7. In the battery system that transmits and receives FDC (Fault Detection Counter) information about the vehicle and DTC (Diagnostic Trouble Code). A battery pack comprising a plurality of battery cells; and Includes a battery management system (BMS) that manages the above battery pack, The above BMS is, Receive a request message from the vehicle and transmit a response message corresponding to the request message to the vehicle, The data area of ​​the above request message includes a data delimiter and diagnostic information data, The above data delimiter is 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 multiple FDCs according to a bitmap, The above bitmap is a list in which multiple DTC diagnostic information is matched with multiple bits constituting the diagnostic information data. Battery system.

8. In paragraph 7, If the above data separator is of the second type, The above diagnostic information data includes binary data in which a binary value corresponds to each of the plurality of bits, Among the plurality of bits represented by the binary data, a plurality of first bits that match a plurality of DTC diagnostic information to be requested to be read based on the bitmap among the plurality of bits are a first value, and among the plurality of bits, a plurality of bits remaining except for the plurality of first bits are a second value. Battery system.

9. In paragraph 8, The data area of ​​the above response message is: including a plurality of FDCs corresponding to the plurality of first DTCs, Battery system.

10. In paragraph 8, If the plurality of first DTCs include a DTC matching a first bit based on the bitmap and a DTC matching a second bit greater than the first bit, The above BMS is, The data area of ​​the response message is configured by sequentially arranging the FDC corresponding to the DTC matching the first bit and the FDC corresponding to the DTC matching the second bit. Battery system.

11. In paragraph 7, If the type of the above response is the first type, The above diagnostic information data includes first DTC information and second DTC information, Battery system.

12. In paragraph 11, The above BMS is, The data area of ​​the response message is configured by arranging the first DTC information, the FDC corresponding to the first DTC information, the second DTC information, and the FDC corresponding to the second DTC information in that order. Battery system.

Images