KR20200029939A - Apparatus for monitoring automotive software, monitoring method using the same and BMS monitoring apparatus comprising the same - Google Patents

Abstract

The present invention relates to an apparatus for monitoring software for electrical equipment, a monitoring method using the same, and a BMS monitoring apparatus including the same which can effectively monitor software for electrical equipment in a process of monitoring software for electrical equipment arranged in a vehicle. According to an embodiment of the present invention, the BMS monitoring apparatus monitors a BMS arranged in a vehicle, and comprises: a diagnosis counting module to count a fault diagnosis count set in diagnosis codes corresponding to diagnosis items of software for electrical equipment of the BMS based on diagnosis results of the diagnosis items; a sensor which generates a diagnosis signal for the BMS, and is electrically connected to the diagnosis counting module to transfer the diagnosis signal to the diagnosis counting module; a diagnosis action module to generate a flag defining an action list for the diagnosis items among action lists corresponding to the diagnosis codes based on the fault diagnosis count; and a diagnosis monitoring module to set the diagnosis codes set in the diagnosis counting module based on the diagnosis items, set the action list set in the diagnosis action module based on the diagnosis codes, and monitor whether at least one between the diagnosis counting module and the diagnosis action module operates normally based on the fault diagnosis count and the flag.

Description

Apparatus for monitoring automotive software, monitoring method using the same and BMS monitoring apparatus comprising the same}

The present invention relates to a software monitoring device for a battlefield, a monitoring method using the same, and a BMS monitoring device including the same, and more specifically, a battlefield capable of effectively monitoring the battlefield software in the process of monitoring the battlefield software provided in the vehicle. Software monitoring device, a monitoring method using the same, and a BMS monitoring device including the same.

In recent years, as demand for portable electronic products such as laptops, video cameras, and portable telephones has rapidly increased, and electric vehicles, energy storage batteries, robots, and satellites have been developed in earnest, high-performance secondary batteries capable of repeated charging and discharging are possible. Research is actively underway.

Currently commercialized secondary batteries include nickel-cadmium batteries, nickel-metal hydride batteries, nickel-zinc batteries, and lithium secondary batteries. Among these, lithium secondary batteries are free of charge and discharge because they have little memory effect compared to nickel-based secondary batteries, The self-discharge rate is very low, and it is spotlighted for its high energy density.

Accordingly, as technology development and demand for mobile devices, electric vehicles, hybrid vehicles, power storage devices, and uninterruptible power supplies increase, the demand for secondary batteries as an energy source is rapidly increasing. In particular, a secondary battery used in an electric vehicle or a hybrid vehicle is a high-power, high-capacity secondary battery, and many studies have been conducted.

In addition, research on peripheral components and devices related to the secondary battery is being conducted along with a great demand for the secondary battery. That is, by connecting a plurality of secondary batteries, a battery module made of a single module, a BMS that controls charging and discharging of a battery module and monitors the status of each secondary battery, a battery module and a battery pack made of one BMS pack, and a battery module Research is being conducted on various parts and devices, such as a switch that connects the load to a motor.

Recently, with the diversification and advancement of software for automotive electronics, the automotive electronics market is also rapidly growing. In addition, efforts are being made to standardize to improve manufacturing efficiency and prevent defects in automotive electronics software. In particular, many automakers are developing software for battlefields based on ISO 26262 automotive electrical / electronic system safety certification standards and AUTOSAR BSW development platform.

On the other hand, the software for the battlefield can cause irreparable damage in the event of an error due to its characteristics. In addition, various accidents and incidents due to errors in battlefield software are steadily occurring, and accordingly, interest in safety of battlefield software is increasing day by day. In addition, due to the advancement and diversification of software for battlefields, the damages caused by defects or failures of software are becoming more serious. Accidents caused by software defects can seriously damage customer safety and the image of automobile companies. have. Therefore, it is important to predict the possibility of defects in the software for battlefields at the beginning of the life of the software and to correct them quickly, and even in the case of software created based on the AUTOSAR BSW development platform, the prediction and verification of such defects is very important. Is an issue.

However, the analysis and monitoring of defects in various software including software for battlefield has been conventionally performed manually by a human hand. For example, in the case of battlefield software, mainly software experts have manually maintained the level of verifying compliance with coding rules of the Motors Industry Software Reliability Association (MISRA) specification for each software module. However, such a manual monitoring method, in the current situation in which the complexity of the code structure of the battlefield software is increasing day by day, has a problem that analysis accuracy is low and stability of analysis is difficult to be expected. In addition, this manual monitoring result is provided only as a simple list listing, and as a real software developer / repairer, it is difficult to identify which part of the large-scale battlefield software is urgently repaired. In addition, there has been a difficulty in efficiently allocating limited resources in the software development / repair area (eg, distribution of development / repair personnel).

The present invention was created under the background of the prior art as described above, and an improved software monitoring device for electric equipment capable of effectively monitoring software for electric equipment in the process of monitoring software for electric equipment provided in a vehicle, a monitoring method using the same, and a monitoring method using the same It relates to a BMS monitoring device.

Other objects and advantages of the present invention can be understood by the following description, and will be more clearly understood by examples of the present invention. In addition, it will be readily understood that the objects and advantages of the present invention can be realized by means and combinations thereof.

BMS monitoring apparatus according to an embodiment of the present invention for achieving the above object is a device for monitoring the BMS provided in the vehicle, the diagnostic items based on the diagnostic results of the diagnostic items of the software for the battlefield of the BMS A diagnostic counting module configured to count a fault diagnostic count set in a diagnostic code corresponding to; A sensor configured to generate a diagnostic signal for the BMS and electrically connected to the diagnostic counting module to transmit the diagnostic signal to the diagnostic counting module; A diagnostic action module configured to generate a flag in which an action list for the diagnostic item is defined among action lists corresponding to the diagnostic code based on the fault diagnostic count; And setting the diagnostic code set in the diagnostic counting module based on the diagnostic item, setting the action list set in the diagnostic action module based on the diagnostic code, and based on the fault diagnostic count and the flag. And a diagnostic monitoring module configured to monitor whether at least one of the diagnostic counting module and the diagnostic action module is operating normally.

In addition, the diagnostic monitoring module may be configured to set at least one of a diagnostic cycle counting the fault diagnostic count of the diagnostic counting module and a counting maximum value of the fault diagnostic count.

In addition, the diagnostic action module may be configured to generate the flag when the fault diagnostic count counted in the diagnostic counting module corresponds to the counting maximum value.

In addition, the diagnostic monitoring module may be configured to monitor whether the diagnostic counting module operates normally based on the increase or decrease of the fault diagnostic count.

Further, the diagnostic monitoring module may be configured to monitor whether the diagnostic action module is operating normally based on whether the flag includes an action list for the diagnostic item.

In addition, the BMS according to an embodiment of the present invention for achieving the above object includes a BMS monitoring device according to the present invention.

In addition, the battery pack according to an embodiment of the present invention for achieving the above object includes a BMS monitoring device according to the present invention.

In addition, a software monitoring device for a battlefield according to an embodiment of the present invention for achieving the above object is provided in a vehicle and is set in a diagnostic code corresponding to the diagnostic item based on a diagnosis result of the diagnostic item of the vehicle A software for battlefield, comprising a diagnostic counting module for counting the fault diagnostic count and a diagnostic action module for generating a flag in which an action list for the diagnostic item is defined in an action list corresponding to the diagnostic code based on the fault diagnostic count. An apparatus for monitoring, comprising: a sensor configured to generate a diagnostic signal for the vehicle and electrically connected to the diagnostic counting module to transmit the diagnostic signal to the diagnostic counting module; And setting the diagnostic code set in the diagnostic counting module, setting the action list set in the diagnostic action module, and at least one of the diagnostic counting module and the diagnostic action module based on the fault diagnosis count and the flag. And a processor configured to monitor one normal operation.

In addition, the processor may be configured to monitor whether the diagnostic counting module operates normally based on the increase or decrease of the fault diagnostic count.

In addition, the processor may be configured to monitor whether the diagnostic action module is operating normally based on whether the flag includes an action list for the diagnostic item.

In addition, a software monitoring method for a battlefield according to an embodiment of the present invention for achieving the above object is a method for monitoring a software for a battlefield provided in a vehicle, based on a diagnosis result of a diagnostic item of the battlefield software Counting a fault diagnosis count set in a diagnosis code corresponding to the diagnosis item; Generating a flag in which an action list for the diagnosis item is defined in an action list corresponding to the diagnosis code based on the fault diagnosis count; And setting the diagnostic code based on the diagnostic item, setting the action list based on the diagnostic code, and monitoring whether the software for the battlefield is operating normally based on the fault diagnostic count and the flag. Includes.

According to one aspect of the present invention, by checking the fault diagnosis count and flag, there is an effect that can effectively monitor whether the software for the battlefield is operating normally.

In particular, according to an embodiment of the present invention, by improving the software for the battlefield based on the diagnosis items of the BMS, an improved battlefield software monitoring device capable of minimizing problems that may occur due to errors in the battlefield software, A monitoring method to be used and a BMS monitoring device including the same may be provided.

In addition, the present invention may have various other effects, and other effects of the present invention may be understood by the following description, and may be more clearly understood by examples of the present invention.

The following drawings attached to this specification are intended to illustrate preferred embodiments of the present invention, and serve to further understand the technical idea of the present invention together with the detailed description of the invention described below, and thus the present invention is described in such drawings. It is not limited to interpretation.
1 is a view schematically showing a configuration in which a BMS monitoring apparatus according to an embodiment of the present invention is connected to some components of a vehicle.
2 is a block diagram schematically showing some components of a processor according to an embodiment of the present invention.
3 is a flowchart schematically showing a software monitoring method for a battlefield according to an embodiment of the present invention.
4 is a flowchart schematically illustrating a software monitoring method for a battlefield according to another embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. Prior to this, the terms or words used in the specification and claims should not be interpreted as being limited to ordinary or lexical meanings, and the inventor appropriately explains the concept of terms in order to explain his or her invention in the best way. Based on the principle that it can be defined, it should be interpreted as meanings and concepts consistent with the technical spirit of the present invention.

Therefore, the embodiments shown in the embodiments and the drawings described in this specification are only the most preferred embodiments of the present invention and do not represent all of the technical spirit of the present invention. It should be understood that there may be equivalents and variations.

In addition, in the description of the present invention, when it is determined that detailed descriptions of related well-known structures or functions may obscure the subject matter of the present invention, detailed descriptions thereof are omitted.

Throughout the specification, when a part “includes” a certain component, this means that other components may be further included, rather than excluding other components, unless otherwise specified. Also, terms such as 'processor' described in the specification mean a unit that processes at least one function or operation, and may be implemented by hardware or software, or a combination of hardware and software.

In addition, throughout the specification, when a part is "connected" to another part, it is not only "directly connected" but also "indirectly connected" with another element in between. Includes.

In the present specification, the secondary battery includes a negative terminal and a positive terminal, and means one independent cell that is physically separable. For example, one pouch-type lithium polymer cell may be considered as a secondary battery.

The BMS monitoring device according to an embodiment of the present invention may be a device for monitoring a BMS provided in a vehicle. For example, as shown in the configuration of FIG. 1, the BMS monitoring device may be provided in a battery pack configured to have both ends connected to the vehicle load 50. In addition, the BMS monitoring device according to an embodiment of the present invention may include a software monitoring device for battlefield. For example, the battlefield software may be provided in a vehicle BMS (Battery Management System) and may be program code in which the operation of the BMS is defined.

1 is a view schematically showing a configuration in which a BMS monitoring apparatus according to an embodiment of the present invention is connected to some components of a vehicle, and FIG. 2 schematically shows some components of a processor according to an embodiment of the present invention. It is a block diagram represented by.

1 and 2, the BMS monitoring device according to an embodiment of the present invention may include a software monitoring device for a battlefield.

An electronic software monitoring device according to an embodiment of the present invention may include a processor 200 and a sensor 100.

The processor 200 according to an embodiment of the present invention may include a diagnostic counting module 210, a diagnostic action module 220, and a diagnostic monitoring module 230.

The diagnostic counting module 210 may be configured to count the fault diagnostic count set in the diagnostic code corresponding to the diagnostic item based on the diagnostic result of the diagnostic item of the electronic software. For example, the diagnostic items may include voltage, current, temperature, SOC (State Of Charge), and State Of Health (SOH) of the BMS. Further, the diagnostic code may be a Diagnostic Trouble Code (DTC) defined as a program code for a diagnostic item of a BMS or an ECU (Electric Control Unit) mounted on a vehicle. For example, the diagnostic code may be DTC A, DTC B or DTC C. Here, the diagnostic code for the overvoltage diagnosis item may be DTC A.

In addition, the fault diagnosis count may be increased by one step when a fault condition is diagnosed for a diagnostic item, and may be decreased by one step when a fault condition is resolved for a diagnostic item.

For example, the diagnostic counting module 210 according to an embodiment of the present invention may count the count of DTC A to 1 when an overvoltage is diagnosed with respect to DTC A, which is a diagnostic code of an overvoltage diagnosis item. For example, the fault diagnosis count may be a FDC (Fault Detection Count).

Preferably, the software for the battlefield may include the diagnostic counting module 210. The diagnostic counting module 210 may count a fault diagnostic count provided in the vehicle and set in a diagnostic code corresponding to the diagnostic item based on the diagnostic result of the diagnostic item of the vehicle. For example, the diagnostic counting module 210 according to an embodiment of the present invention may be a Diagnostic Event Manager (DEM).

The diagnostic action module 220 may be configured to generate a flag in which an action list for a diagnosis item is defined among action lists corresponding to a diagnostic code based on a fault diagnosis count. For example, the action list corresponding to the diagnostic code may be a corresponding list of BMS for overvoltage diagnosis. For example, the action list may be a list of actions for switching the contactor to an open state for overvoltage diagnosis. For example, the action list may be FID (Function Identifier Direction).

For example, the diagnostic action module 220 may generate a flag in which an action is defined for switching the contactor to an open state with respect to the overvoltage based on the fault diagnostic count for the overvoltage. In this case, the processor 200 may switch the contactor to the open state with respect to overvoltage based on the flag generated by the diagnostic action module 220.

Preferably, the battlefield software may include the diagnostic action module 220. The diagnostic action module 220 may generate a flag in which an action list for a diagnosis item is defined among action lists corresponding to a diagnostic code based on a fault diagnosis count. For example, the diagnostic action module 220 according to an embodiment of the present invention may be a FIM (Function Inhibition Manager).

The diagnostic monitoring module 230 may set a diagnostic code set in the diagnostic counting module 210. For example, the diagnostic monitoring module 230 may set a diagnostic code for a diagnostic item. For example, the diagnostic monitoring module 230 may set the diagnostic code DTC A for overvoltage diagnosis.

Also, the diagnostic monitoring module 230 may set an action list set in the diagnostic action module 220. For example, the diagnostic monitoring module 230 may set an action list for the diagnostic code. For example, the diagnostic monitoring module 230 may set an action list for switching the contactor to an open state for overvoltage diagnosis.

In addition, the diagnostic monitoring module 230 may monitor whether at least one of the diagnostic counting module 210 and the diagnostic action module 220 is operating normally based on the fault diagnostic count and flag. For example, the diagnostic monitoring module 230 may monitor whether the diagnostic counting module 210 operates normally based on the fault diagnostic count. In addition, the diagnostic monitoring module 230 may monitor whether the diagnostic action module 220 is operating normally based on the flag.

Preferably, the processor 200 according to an embodiment of the present invention sets a diagnostic code set in the diagnostic counting module 210, sets a list of actions set in the diagnostic action module 220, and fault diagnosis It may be configured to monitor whether at least one of the diagnostic counting module 210 and the diagnostic action module 220 is operating normally based on the count and flag.

The sensor 100 may be configured to generate a diagnostic signal for the BMS and to be electrically connected to the diagnostic counting module 210 to transmit the diagnostic signal to the diagnostic counting module 210. In addition, the sensor 100 may be configured to generate a diagnostic signal for the vehicle and electrically connect to the diagnostic counting module 210 to transmit the diagnostic signal to the diagnostic counting module 210. For example, the diagnostic signal generated by the sensor 100 may include at least one of voltage, current, and temperature.

The sensor 100 may be electrically connected to the cell assembly 10 provided in the battery pack. For example, as illustrated in the configuration of FIG. 1, the sensors 100 may be electrically connected to both ends of the cell assembly 10 so as to send and receive electrical signals.

In addition, the sensor 100 may be configured to measure the voltage across the cell assembly 10. More specifically, the sensor 100 may measure the voltage across the cell assembly 10 based on electrical signals received from both ends of the cell assembly 10.

Preferably, the sensor 100 may be electrically connected to the processor 200 to send and receive electrical signals. In addition, the sensor 100 measures the potential difference between the positive terminal of the cell assembly 10 and the negative terminal of the cell assembly 10 at a time interval under the control of the processor 200, and a signal indicating the magnitude of the measured voltage Can be output to the processor 200. For example, the sensor 100 may be implemented using a voltage measurement circuit generally used in the art.

For example, the sensor 100 may generate a diagnostic signal for the voltage across the cell assembly 10 and transmit a diagnostic signal for the voltage across the cell assembly 10 to the diagnostic counting module 210. For example, as shown in the configuration of FIG. 1, the sensor 100 measures voltage across both ends of the cell assembly 10 and diagnoses a diagnostic signal for the voltage value of the cell assembly 10 in the diagnostic counting module 210 ). For example, the diagnostic counting module 210 may diagnose a diagnostic item based on a diagnostic signal received from the sensor 100. For example, if the diagnostic counting module 210 has an overvoltage threshold of 5v and receives a diagnostic signal corresponding to a voltage of 5.8v of the cell assembly 10 from the sensor 100, the diagnostic counting module 210 is based on the cell assembly 10 ) It can be diagnosed that the voltage at both ends corresponds to the overvoltage. Here, the diagnostic counting module 210 may store a diagnostic threshold value that is the basis of the diagnosis in advance. Alternatively, the diagnostic counting module 210 may receive the diagnostic threshold value from the memory device 300.

Preferably, the diagnostic monitoring module 230 according to an embodiment of the present invention may set a diagnostic cycle counting the fault diagnostic count of the diagnostic counting module 210. For example, when the diagnostic counting module 210 diagnoses overvoltage, the diagnostic monitoring module 230 may set the diagnostic cycle counting the fault diagnostic count to 1 day. In this case, the diagnostic counting module 210 may reset the fault diagnostic count after one day. In addition, the diagnostic monitoring module 230 may set a diagnostic cycle counting a fault diagnostic count for an overvoltage diagnosis of the diagnostic counting module 210 to 1 minute. In this case, the diagnostic counting module 210 can diagnose the overvoltage every minute.

In addition, the diagnostic monitoring module 230 may set a counting maximum value of the fault diagnostic count. For example, the diagnostic monitoring module 230 may set the counting maximum value of the fault diagnostic count to 3 when diagnosing overvoltage in the diagnostic counting module 210. In this case, the diagnostic counting module 210 may sequentially count the fault diagnostic counts from 1 to 3 until the overvoltage is diagnosed three times.

Preferably, the diagnostic action module 220 according to an embodiment of the present invention may generate a flag when the fault diagnosis count counted by the diagnostic counting module 210 corresponds to the counting maximum value. For example, the diagnostic action module 220 may receive a fault diagnostic count from the diagnostic counting module 210. Also, the diagnostic action module 220 may receive a signal from the diagnostic counting module 210 indicating that the counting maximum has been reached when the fault diagnostic count corresponds to the counting maximum. In addition, the diagnostic action module 220 may generate a flag based on the fault diagnostic count when the counting maximum value corresponds to the counting maximum value. Here, an action list for a diagnosis item for a diagnosis item may be defined in the flag. For example, the diagnostic action module 220 defines a list of actions for switching the contactor to the open state when the fault diagnosis count corresponds to a counting maximum value of 3 by overvoltage diagnosis in the diagnostic counting module 210. Flags can be generated.

Preferably, the diagnostic monitoring module 230 according to an embodiment of the present invention may monitor whether the diagnostic counting module 210 operates normally based on the increase or decrease of the fault diagnostic count. For example, when the diagnostic counting module 210 diagnoses a diagnostic item, the diagnostic monitoring module 230 may monitor whether the diagnostic counting module 210 operates normally based on whether the fault diagnostic count increases or decreases normally. have. For example, when the diagnostic counting module 210 diagnoses overvoltage, the diagnostic monitoring module 230 may monitor whether the diagnostic counting module 210 is operating normally based on whether the fault diagnostic count increases. . In addition, when the diagnostic counting module 210 does not diagnose the overvoltage, the diagnostic monitoring module 230 may monitor whether the diagnostic counting module 210 operates normally based on whether the fault diagnostic count decreases.

Preferably, the diagnostic monitoring module 230 according to an embodiment of the present invention is to monitor the normal operation of the diagnostic action module 220 based on whether the flag includes an action list for the diagnostic item. You can. For example, the diagnostic monitoring module 230 may receive a flag generated by the diagnostic action module 220. In addition, the diagnostic monitoring module 230 may monitor whether the diagnostic action module 220 is operating normally based on whether the action list defined in the flag is an action list corresponding to the diagnostic item. Here, the diagnostic monitoring module 230 may previously store a table in which a diagnosis item and an action list are mapped. In addition, the diagnostic monitoring module 230 may receive a table to which a diagnosis item and an action list are mapped from the memory device 300.

Preferably, the software monitoring device for battlefield according to an embodiment of the present invention may further include a memory device 300, as shown in the configuration of FIG. 1.

The memory device 300 may be electrically connected to the processor 200 to send and receive electrical signals. In addition, the memory device 300 may store information necessary for the operation of the software monitoring device for battlefield in advance. For example, the memory device 300 may store a diagnostic threshold value that is the basis of the diagnosis in advance. Also, the memory device 300 may previously store a table in which diagnosis items and action lists are mapped.

On the other hand, the processor 200, in order to perform the operation as described above, the processor 200, an application-specific integrated circuit (ASIC), other chipsets, logic circuits, registers, communication modems and / or data known in the art It may be implemented in a form that selectively includes a processing device.

On the other hand, the memory device 300 has no particular limitation on its type as long as it is a storage medium capable of recording and erasing information. For example, the memory device 300 may be a RAM, ROM, register, hard disk, optical recording medium, or magnetic recording medium. The memory device 300 may also be electrically connected to the processor 200 through, for example, a data bus or the like, so that each can be accessed by the processor 200. The memory device 300 may also store and / or update and / or erase and / or transmit data generated when a program that includes various control logics performed by the processor 200 and / or control logic is executed. have.

The BMS monitoring device according to the present invention can be applied to BMS. That is, the BMS according to the present invention may include the BMS monitoring device according to the present invention described above. In this configuration, at least a part of each component of the BMS monitoring apparatus according to the present invention may be implemented by supplementing or adding functions of a configuration included in a conventional BMS. For example, the processor 200 and the memory device 300 of the BMS monitoring apparatus according to the present invention may be implemented as components of a battery management system (BMS). In addition, preferably, the software monitoring device for battlefield according to the present invention can be applied to a BMS.

In addition, the BMS monitoring device according to the present invention may be provided in a battery pack. That is, the battery pack according to the present invention may include the BMS monitoring device according to the present invention described above. Here, the battery pack may include one or more secondary cells, the BMS monitoring device, electronic components (including BMS, relays, fuses, etc.) and a case. In addition, preferably, the software monitoring device for battlefield according to the present invention may be provided in the battery pack.

3 is a flowchart schematically showing a software monitoring method for a battlefield according to an embodiment of the present invention. In FIG. 3, the subject of each step may be referred to as each component of the software monitoring device for battlefield according to the present invention described above.

As shown in FIG. 3, the software monitoring method for battlefield according to the present invention includes a fault diagnosis count counting step (S100), a flag generation step (S110), and a monitoring step (S120).

In the fault diagnosis count counting step (S100), the fault diagnosis count set in the diagnostic code corresponding to the diagnosis item may be counted based on the diagnosis result of the diagnosis item of the software for battlefield.

Subsequently, in the flag generating step (S110), a flag in which an action list for a diagnosis item is defined among action lists corresponding to a diagnostic code may be generated based on a fault diagnosis count.

Subsequently, in the monitoring step (S120), a diagnostic code set in the diagnostic counting module is set, an action list set in the diagnostic action module is set, and among the diagnostic counting module and the diagnostic action module based on the fault diagnostic count and flag At least one normal operation can be monitored.

Preferably, in the monitoring step (S120) according to an embodiment of the present invention, it is possible to monitor whether the diagnostic counting module operates normally based on the increase or decrease of the fault diagnostic count.

Preferably, in the monitoring step (S120) according to an embodiment of the present invention, it is possible to monitor whether the diagnostic action module is operating normally based on whether the flag includes an action list for the diagnostic item. have.

4 is a flowchart schematically illustrating a software monitoring method for a battlefield according to another embodiment of the present invention. In FIG. 4, the subject of each step may be referred to as each component of the software monitoring device for battlefield according to the present invention described above.

In step S200, the processor may select a diagnostic item and a diagnostic code. For example, the processor may select overvoltage diagnosis as a diagnostic item and select a diagnostic code as DTC A for overvoltage diagnosis.

In step S210, the processor may determine whether the diagnostic code is achieved. For example, the processor may diagnose whether the overvoltage is based on the diagnostic signal received from the sensor, and when the overvoltage is diagnosed, may determine that the diagnostic code has been achieved. In addition, the processor may diagnose whether the overvoltage is based on the diagnostic signal received from the sensor, and if the overvoltage is not diagnosed, may determine that the diagnostic code has not been achieved. If the value of step S210 is "yes", the method proceeds to step S220. Otherwise, the method proceeds to step S225.

In step S220, the processor may set a pre-fail based on that the diagnostic code has been achieved. For example, if the overvoltage is diagnosed, the processor may set a pre-fail based on that the diagnostic code has been achieved. Subsequently, the method proceeds to step S230.

In step S225, the processor may set a pre-pass based on that the diagnostic code has not been achieved. For example, if the overvoltage is not diagnosed, the processor may set a pre-pass based on that the diagnostic code has not been achieved. Then, the method proceeds to step S235.

In step S230, the processor may determine whether to increase the fault diagnosis count. For example, the processor may count to increase the fault diagnosis count based on the pre-fail and determine whether the fault diagnosis count is increased. For example, the fault diagnosis count may be sequentially increased by 1 unit. If the value of step S230 is "yes", the method proceeds to step S240. Otherwise, the method proceeds to step S245.

In step S235, the processor may determine whether the fault diagnosis count is decreased. For example, the processor may count the fault diagnosis count to decrease based on the pre-pass and determine whether the fault diagnosis count is decreased. For example, the fault diagnosis count may be sequentially decreased by 1 unit. If the value of step S235 is "yes", the method proceeds to step S240. Otherwise, the method proceeds to step S245.

In step S240, the processor may determine that the diagnostic counting module is operating normally. After step S240, the method proceeds to step S250.

In step S245, the processor may determine that the diagnostic counting module does not operate normally. After step S245, the method may end. For example, if it is determined that the diagnostic counting module is in an abnormal state, the processor may transmit an alarm to the upper level control device.

In step S250, the processor may determine whether the fault diagnosis count corresponds to a full count. For example, when the counting maximum value of the fault diagnosis count is 3 and the fault diagnosis count corresponds to 3, the processor may determine that the fault diagnosis count corresponds to the full count. If the value of step S250 is "yes", the method proceeds to step S260. Otherwise, the method proceeds to step S210.

In step S260, the processor may generate a flag. For example, the processor may generate a flag based on the fact that the fault diagnostic count corresponds to a full count. After step S260, the method proceeds to step S270.

In step S270, the processor may determine whether an action list is included in the flag. For example, the processor may determine whether the flag includes a list of actions corresponding to the diagnosis item. If the value of step S270 is "yes", the method proceeds to step S280. Otherwise, the method proceeds to step S285.

In step S280, the processor may determine that the diagnostic action module is operating normally. After step S280, the method may end.

In step S285, the processor may determine that the diagnostic action module does not operate normally. After step S285, the method may end. For example, if it is determined that the diagnostic action module is in an abnormal state, the processor may transmit an alarm to the upper control device.

Further, when the control logic is implemented in software, the processor may be implemented as a set of program modules. At this time, the program module may be stored in the memory device and executed by the processor.

In addition, at least one of the various control logics of the processor is combined, and the combined control logics are written in a computer-readable code system so that the computer-readable accessibility is not limited. As one example, the recording medium includes at least one or more selected from the group comprising ROM, RAM, registers, CD-ROM, magnetic tape, hard disk, floppy disk, and optical data recording device. In addition, the code system can be distributed and stored on a networked computer and executed. In addition, functional programs, codes and segments for implementing the combined control logics can be easily inferred by programmers in the art to which the present invention pertains.

As described above, although the present invention has been described by limited embodiments and drawings, the present invention is not limited by this, and the technical idea of the present invention and the following will be described by those skilled in the art to which the present invention pertains. Of course, various modifications and variations are possible within the equivalent scope of the claims to be described.

10: cell assembly
50: vehicle load
100: sensor
200: processor
210: diagnostic counting module
220: diagnostic action module
230: diagnostic monitoring module
300: memory device

Claims (11)

In the device for monitoring the BMS provided in the vehicle,
A diagnostic counting module configured to count a fault diagnostic count set in a diagnostic code corresponding to the diagnostic item based on a diagnosis result of the diagnostic item of the software for the battlefield of the BMS;
A sensor configured to generate a diagnostic signal for the BMS and electrically connected to the diagnostic counting module to transmit the diagnostic signal to the diagnostic counting module;
A diagnostic action module configured to generate a flag in which an action list for the diagnostic item is defined among action lists corresponding to the diagnostic code based on the fault diagnostic count; And
The diagnostic code set in the diagnostic counting module is set based on the diagnostic item, the action list set in the diagnostic action module is set based on the diagnostic code, and the fault diagnostic count and the flag are set. A diagnostic monitoring module configured to monitor whether at least one of the diagnostic counting module and the diagnostic action module is operating normally.
BMS monitoring device comprising a.
According to claim 1,
The diagnostic monitoring module is configured to set at least one of a diagnostic cycle counting the fault diagnostic count of the diagnostic counting module and a counting maximum value of the fault diagnostic count.
According to claim 2,
The diagnostic action module is configured to generate the flag when the fault diagnostic count counted by the diagnostic counting module corresponds to the counting maximum value.
According to claim 3,
The diagnostic monitoring module, BMS monitoring device, characterized in that configured to monitor whether the normal operation of the diagnostic counting module based on the increase or decrease of the fault diagnostic count.
According to claim 4,
The diagnostic monitoring module is configured to monitor whether the diagnostic action module is operating normally based on whether the flag includes an action list for the diagnostic item.
A BMS comprising the BMS monitoring device according to claim 1.
A battery pack comprising the BMS monitoring device according to claim 1.
A diagnostic counting module provided in a vehicle to count a fault diagnostic count set in a diagnostic code corresponding to the diagnostic item based on a diagnosis result of the diagnostic item of the vehicle, and an action corresponding to the diagnostic code based on the fault diagnostic count In the apparatus for monitoring the software for the battlefield having a diagnostic action module for generating a flag defined action list for the diagnostic item in the list,
A sensor configured to generate a diagnostic signal for the vehicle and electrically connected to the diagnostic counting module to transmit the diagnostic signal to the diagnostic counting module; And
Set the diagnostic code set in the diagnostic counting module, set the action list set in the diagnostic action module, and at least one of the diagnostic counting module and the diagnostic action module based on the fault diagnostic count and the flag Processor configured to monitor the normal operation of the
Software monitoring device for the battlefield, characterized in that it comprises a.
The method of claim 8,
And the processor is configured to monitor whether the diagnostic counting module is operating normally based on the increase or decrease of the fault diagnostic count.
The method of claim 9,
And the processor is configured to monitor whether the diagnostic action module is operating normally based on whether the flag includes an action list for the diagnostic item.
In the method for monitoring the software for the battlefield provided in the vehicle,
Counting a fault diagnostic count set in a diagnostic code corresponding to the diagnostic item based on a diagnosis result of the diagnostic item of the electronic software;
Generating a flag in which an action list for the diagnosis item is defined in an action list corresponding to the diagnosis code based on the fault diagnosis count; And
Setting the diagnostic code based on the diagnostic item, setting the action list based on the diagnostic code, and monitoring whether the software for the battlefield is operating normally based on the fault diagnostic count and the flag
Battlefield software monitoring method comprising a.

Images