Battery management system testing methods, apparatus, equipment, media, and procedures.

Abstract

This application provides a testing method, apparatus, device, medium, and program product for a battery management system, belonging to the field of battery technology. The testing method for the battery management system includes: determining a first interface system variable set, the first interface system variable set including at least one driving variable, the at least one driving variable indicating at least one state of a first test interface; determining a second interface system variable set, the second interface system variable set including at least one operating variable, the at least one operating variable indicating at least one state of any second test interface in the battery management system; and mapping the second test interface to the first test interface based on a pre-determined mapping relationship between the second interface system variable set and the first interface system variable set. This testing method can improve testing flexibility in multi-functional configuration scenarios.

Description

Technical Field

[0001] This application relates to the field of battery technology, and in particular to a testing method, apparatus, equipment, medium, and program product for a battery management system. Background Technology

[0002] Energy conservation and emission reduction are key to the sustainable development of the automotive industry, and electric vehicles, due to their energy-saving and environmentally friendly advantages, have become an important component of this sustainable development. For electric vehicles, battery technology is a crucial factor in their development.

[0003] The Battery Management System (BMS) is a crucial component of battery devices, playing a vital role in their operation. Currently, the Vehicle Test System (VT) is commonly used as a test platform to test the various hardware channels within the BMS. However, different functional configurations for the hardware channels in the BMS often require separate settings corresponding to different hardware channels on the test platform, which does not adequately accommodate flexible switching in multi-functional configuration scenarios. Summary of the Invention

[0004] This application aims to at least address the technical problem of poor testing flexibility in multi-functional configuration scenarios of BMS hardware channels, as described in the background art. Therefore, one objective of this application is to provide a testing method for a battery management system to improve testing flexibility in multi-functional configuration scenarios.

[0005] An embodiment of the first aspect of this application provides a testing method for a battery management system, comprising: determining a first interface system variable set, the first interface system variable set including at least one driving variable, the at least one driving variable indicating at least one state of a first test interface; determining a second interface system variable set, the second interface system variable set including at least one operating variable, the at least one operating variable indicating at least one state of any second test interface in the battery management system; and mapping the second test interface to the first test interface based on a predetermined mapping relationship between the second interface system variable set and the first interface system variable set.

[0006] In the technical solution of this application embodiment, by mapping any second test interface in the BMS to the first test interface, the different functions of each hardware channel in the BMS can be implemented in the interface of the test platform. Thus, without switching the test interface of the test platform, simulation testing of the functions of each hardware channel of the BMS can be achieved, simplifying the relevant test configuration and improving the flexibility of the test process.

[0007] In some embodiments, at least one operational variable corresponds one-to-one with at least one driving variable. Setting the operational variables and driving variables to a one-to-one correspondence allows for the simulation of setting the operational variables for the second test interface by configuring the driving variables of the first test interface, accurately simulating each hardware channel of the BMS and improving the accuracy of test results.

[0008] In some embodiments, determining the second interface system variable set includes: determining the second interface system variable set corresponding to the second test interface to be tested in the battery management system. For hardware channels with different functions in the BMS, the corresponding second interface system variable set can be determined according to the specific function of the hardware channel, thereby achieving accurate simulation of each hardware channel in the BMS.

[0009] In some embodiments, the testing method further includes: identifying the second test interface to be tested in the battery management system before determining the second interface system variable set. When testing the BMS, the functionality of the hardware channel to be tested is first identified, thereby accurately determining the corresponding second interface system variable set.

[0010] In some embodiments, mapping the second test interface to the first test interface based on a predetermined mapping relationship between the second set of interface system variables and the first set of interface system variables includes: assigning values ​​to the corresponding driving variables according to the mapping relationship for each of the at least one set of operational variables. After determining the mapping relationship between the second set of interface system variables and the first set of interface system variables, each operational variable is assigned a value to its corresponding driving variable, thereby enabling the first test interface to simulate the function of the second test interface in the BMS, improving the flexibility and accuracy of the test.

[0011] In some embodiments, the mapping relationship is predetermined according to the following steps: after determining the second interface system variable set: establishing a mapping function between each operand in at least one operand and its corresponding driving variable; and obtaining the mapping relationship based on the mapping function. Accurately establishing the mapping relationship between variables can improve the accuracy of simulation testing.

[0012] In some embodiments, the testing method further includes: after mapping the second test interface to the first test interface based on a predetermined mapping relationship between the second interface system variable set and the first interface system variable set, setting the first interface system variable set as the initial system variable set. By setting the first interface system variable set as the initial system variable set, the interface state can be initialized, interference with the test results can be reduced, and the test accuracy can be improved.

[0013] In some embodiments, the testing method further includes: identifying at least one test board. By accurately identifying the test boards in the testing platform, accurate simulation testing can be achieved, improving the accuracy of the test results.

[0014] In some embodiments, the testing method further includes: determining a first test board from at least one test board based on a first set of interface system variables, the first test board being used to test the battery management system. Based on the function to be tested, a test board for testing is determined from multiple test boards to achieve accurate simulation testing.

[0015] In some embodiments, the testing method further includes: configuring a first test board according to a first interface system variable set. Configuring the test board used for testing according to the first interface system variable set enables accurate simulation testing.

[0016] In some embodiments, at least one driving variable includes: a first driving variable indicating whether the first test interface is in a first driving state or a second driving state; and a second driving variable indicating a fault state injected into the first test interface. By setting different driving variables, simulation tests for different states can be implemented, improving the comprehensiveness of the test results.

[0017] In some embodiments, at least one operational variable includes: a first operational variable indicating whether the second test interface is in a third or fourth driving state; and a second operational variable indicating a fault state injected into the second test interface. By setting different operational variables, simulation tests for different states can be achieved, improving the comprehensiveness of the test results.

[0018] An embodiment of the second aspect of this application provides a testing apparatus for a battery management system, comprising: a first module for determining a first interface system variable set, the first interface system variable set including at least one driving variable, the at least one driving variable indicating at least one state of a first test interface; a second module for determining a second interface system variable set, the second interface system variable set including at least one operational variable, the at least one operational variable indicating at least one state of any second test interface in the battery management system; and a third module for mapping a second test interface to a first test interface based on a pre-determined mapping relationship between the second interface system variable set and the first interface system variable set.

[0019] An embodiment of the third aspect of this application provides a computing device, including: at least one processor; and at least one memory communicatively connected to the at least one processor, the at least one memory storing instructions that, when executed individually or jointly by the at least one processor, cause the computing device to perform the test method in the above embodiment.

[0020] An embodiment of the fourth aspect of this application provides a computer-readable storage medium storing instructions that, when executed individually or jointly by one or more processors of a computing device, cause the computing device to perform the test method described above.

[0021] An embodiment of the fifth aspect of this application provides a computer program product including instructions that, when executed individually or jointly by one or more processors of a computing device, cause the computing device to perform the test method described above.

[0022] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0023] In the accompanying drawings, unless otherwise specified, the same reference numerals throughout the various drawings denote the same or similar parts or elements. These drawings are not necessarily drawn to scale. It should be understood that these drawings depict only some embodiments disclosed in this application and should not be construed as limiting the scope of this application.

[0024] Figure 1 This is a flowchart illustrating a testing method for a battery management system according to some embodiments of this application;

[0025] Figure 2 This is a flowchart illustrating the process of determining mapping relationships in some embodiments of this application;

[0026] Figure 3 This is a schematic block diagram of a test apparatus for a battery management system according to some embodiments of this application;

[0027] Figure 4 This is a schematic block diagram of a computing device according to some embodiments of this application. Detailed Implementation

[0028] The embodiments of the technical solution of this application will now be described in detail with reference to the accompanying drawings. These embodiments are only used to more clearly illustrate the technical solution of this application and are therefore merely examples, and should not be used to limit the scope of protection of this application.

[0029] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains; the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the application; the terms “comprising” and “having”, and any variations thereof, in the specification, claims, and foregoing description of the drawings are intended to cover non-exclusive inclusion.

[0030] In the description of the embodiments of this application, technical terms such as "first" and "second" are used only to distinguish different objects and should not be construed as indicating or implying relative importance or implicitly specifying the number, specific order, or primary and secondary relationship of the indicated technical features. In the description of the embodiments of this application, "multiple" means two or more, unless otherwise explicitly defined.

[0031] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0032] In the description of the embodiments in this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0033] In the description of the embodiments of this application, the term "multiple" refers to two or more (including two), similarly, "multiple sets" refers to two or more (including two sets), and "multiple pieces" refers to two or more (including two pieces).

[0034] In the description of the embodiments of this application, the technical terms "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," "clockwise," "counterclockwise," "axial," "radial," and "circumferential" indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing the embodiments of this application and simplifying the description, and are not intended to indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the embodiments of this application.

[0035] In the description of the embodiments of this application, unless otherwise expressly specified and limited, technical terms such as "installation," "connection," "joining," and "fixing" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components. For those skilled in the art, the specific meaning of the above terms in the embodiments of this application can be understood according to the specific circumstances.

[0036] Currently, judging from market trends, the application of power batteries is becoming increasingly widespread. Power batteries are not only used in energy storage systems such as hydropower, thermal power, wind power, and solar power plants, but also extensively used in electric vehicles such as electric bicycles, electric motorcycles, and electric cars, as well as in military equipment and aerospace. With the continuous expansion of power battery applications, market demand is also constantly increasing.

[0037] The Battery Management System (BMS) is a crucial component of battery devices, playing a vital role in their operation. Currently, the Vehicle Test System (VT) is commonly used as a test platform to test the various hardware channels within the BMS. Testing these hardware channels often requires configuring the corresponding driver interfaces of the test platform. Different functions of the hardware channels also typically require different driver interface settings. When switching between hardware channels or different software versions of those channels, the required testing functions change, necessitating changes to the corresponding driver interface settings on the test platform. Previous settings become invalid, requiring reconfiguration. This approach is not well-suited for flexible switching in multi-functional configuration scenarios, making the process cumbersome.

[0038] To improve the flexibility and adaptability of testing different functions of the BMS, a mapping relationship can be pre-established between the configuration of each function of the BMS hardware channel and the test interface of the test platform. When different functions need to be tested, the corresponding function of the hardware channel to be tested will be mapped to the test interface of the test platform according to the mapping relationship, thereby realizing the testing of the function, such as performing fault injection and other operations.

[0039] The battery management system testing method disclosed in this application can be used, but is not limited to, in battery management systems of electrical devices such as vehicles, ships, or aircraft. Using the testing method for the battery management system disclosed in this application improves the testing flexibility and adaptability for multi-functional configuration scenarios of the battery management system.

[0040] This application provides a testing method for a battery management system. (See also...) Figure 1 Test method 100 includes steps 110 to 130.

[0041] Step 110: Determine the first interface system variable set. The first interface system variable set includes at least one driving variable. The at least one driving variable indicates at least one state of the first test interface.

[0042] Step 120: Determine the second interface system variable set. The second interface system variable set includes at least one operational variable. The at least one operational variable indicates at least one state of any second test interface in the battery management system.

[0043] Step 130: Based on the predetermined mapping relationship between the second interface system variable set and the first interface system variable set, map the second test interface to the first test interface.

[0044] A Battery Management System (BMS) includes various hardware channels, such as different dry contacts (i.e., passive switches). Each dry contact has only two states: on and off, and the polarity between two contacts cannot be interchanged. The hardware channels in the BMS may have different functions, which can be configured in the BMS software. For example, the same dry contact may be configured as dry contact A, electrical compartment fan dry contact, dry contact X, etc., depending on the software configuration.

[0045] In embodiments of this application, the "first test interface" may include a test interface of a test platform used to test the BMS, such as a test interface in a VT system (e.g., a test interface named DI_Contact8+_Drive). For each first test interface, a corresponding first interface system variable set can be determined. The first interface system variable set includes one or more drive variables. Each drive variable can be used to set the state of the first test interface. For example, when testing dry contacts in the BMS, the first test interface can be set to a closed or open state, or it can be set to a short circuit to power supply or a short circuit to ground state.

[0046] In embodiments of this application, the "second test interface" can be used to indicate hardware channels under different functions in the BMS. In one example, the second test interface can indicate a dry contact hardware channel in the BMS configured as an electrical silo fan dry contact function. Similar to the first test interface, a second interface system variable set can be determined for each second test interface. The second interface system variable set includes one or more operational variables. Each operational variable can be used to set the state of the second test interface. For example, when testing the aforementioned electrical silo fan dry contact, the second test interface can be set to a closed or open state, or it can be set to a short circuit to power supply, short circuit to ground, or other similar states.

[0047] After determining the first interface system variable set and the second interface system variable set, the second test interface to be tested in the BMS can be mapped to the first test interface of the test platform according to the predetermined mapping relationship. Thus, by setting different variables at the first test interface of the test platform, simulation testing of the second test interface to be tested in the BMS can be achieved.

[0048] In some embodiments, test method 100 may be executed by test software, such as the CANoe test tool.

[0049] By mapping any second test interface in the BMS to the first test interface, the different functions of each hardware channel in the BMS can be implemented in the interface of the test platform. This allows for simulation testing of the functions of each hardware channel of the BMS without switching the test interface of the test platform, simplifying the relevant test configuration and improving the flexibility of the test process.

[0050] According to some embodiments of this application, at least one operating variable corresponds one-to-one with at least one driving variable.

[0051] To simulate the second test interface in the BMS by setting different variables at the first test interface of the test platform, the driving variables of the first test interface and the operation variables of the second test interface need to be set to correspond one-to-one. This way, setting a driving variable can simulate the corresponding setting of its operation variable.

[0052] By setting the operation variables and driving variables to correspond one-to-one, the settings of the operation variables for the second test interface can be simulated by setting the driving variables of the first test interface, thus accurately simulating the various hardware channels of the BMS and improving the accuracy of the test results.

[0053] According to some embodiments of this application, step 120 includes: determining a second interface system variable set corresponding to the second test interface in the battery management system.

[0054] As mentioned above, hardware channels in a BMS may correspond to different functional settings with software switching. Therefore, the set of second interface system variables will also differ with software switching. When testing the second test interface in a BMS, it is necessary to first determine the specific function of the second test interface to be tested, such as the corresponding parameter configuration, and then determine the corresponding set of second interface system variables based on the second test interface. In one example, for a specific hardware channel in a BMS, in a certain version of the software, this hardware channel is set as an electrical compartment fan dry contact, that is, the second test interface is an electrical compartment fan dry contact. At this time, the set of second interface system variables corresponding to it can include several operational variables, such as operational variables indicating whether the electrical compartment fan dry contact is on or off, and operational variables indicating the fault mode of the electrical compartment fan dry contact (e.g., short-circuited to power supply, short-circuited to ground, short-circuited to busbar, etc.).

[0055] For hardware channels with different functions in the BMS, the corresponding second interface system variable set can be determined according to the specific function of the hardware channel, thereby realizing accurate simulation of each hardware channel in the BMS.

[0056] According to some embodiments of this application, the test method 100 further includes:

[0057] Before step 120: Identify the second test interface to be tested in the battery management system.

[0058] In some embodiments, the second test interface to be tested can be identified based on the software configuration table of the current BMS software. In one example, a software configuration mapping tool can be used to identify the second test interface. Taking the BMS software configuration table as input, the relevant functional configuration parameters of the second test interface in the software can be identified based on the configuration parameters for the relevant functions in the software configuration table. After identifying the second test interface corresponding to this version of the software, the corresponding set of system variables for the second interface can be determined.

[0059] When testing the BMS, the function of the hardware channel to be tested is first identified, so that the corresponding second interface system variable set can be accurately determined.

[0060] According to some embodiments of this application, step 130 includes:

[0061] Based on the mapping relationship, values ​​are assigned to the corresponding driving variables according to each of the at least one operand.

[0062] Since the operation variables of the second test interface correspond one-to-one with the driving variables of the first test interface, after determining the mapping relationship between the system variable set of the second interface and the system variable set of the first interface, the operation variables of the second test interface can be assigned to the corresponding driving variables of the first test interface.

[0063] Continuing with the example of the second test interface being the dry contact of the electrical chamber fan and the first test interface being the test interface named DI_Contact8+_Drive in the VT system, the driving variables for the DI_Contact8+_Drive test interface include driving variables representing on / off states and driving variables representing fault injection. In one example, the driving variable representing on / off states can be set to 1 or 2, where 1 represents closed and 2 represents open; the driving variable representing fault injection can be set to 1, 2, 3, or 4, where 1 represents short-circuiting to the power supply, 2 represents short-circuiting to ground, 3 represents short-circuiting to busbar A, and 4 represents short-circuiting to busbar B. Similarly, for the dry contact of the electrical chamber fan, the operating variables also include operating variables representing on / off states and operating variables representing fault injection. In one example, the operating variable representing on / off states can be set to 1 or 2, where 1 represents closed and 2 represents open; the operating variable representing fault injection can be set to 1, 2, 3, or 4, where 1 represents short-circuiting to the power supply, 2 represents short-circuiting to ground, 3 represents short-circuiting to busbar A, and 4 represents short-circuiting to busbar B. Based on the predetermined mapping relationship, the operation variable name corresponding to the dry contact of the electrical chamber fan, which represents on / off state, is assigned to the drive variable representing on / off state of the DI_Contact8+_Drive test interface. The operation variable name corresponding to the dry contact of the electrical chamber fan, which represents fault injection, is assigned to the drive variable representing fault injection of the DI_Contact8+_Drive test interface.

[0064] After determining the mapping relationship between the second interface system variable set and the first interface system variable set, each operation variable is assigned a value to its corresponding driving variable. This allows the first test interface to simulate the function of the second test interface in the BMS, improving the flexibility and accuracy of the test.

[0065] According to some embodiments of this application, the mapping relationship is predetermined according to process 200. (See reference...) Figure 2 Process 200 includes steps 210 to 220 following step 120.

[0066] Step 210: Establish a mapping function between each of the at least one operational variable and its corresponding driving variable.

[0067] Step 220: Obtain the mapping relationship based on the mapping function.

[0068] In one example, process 200 can be implemented using a software configuration mapping tool. After determining the specific functionality of the second test interface to be tested, the software configuration mapping tool can establish mapping functions between the various operational variables of the second test interface and the various driving variables of the first test interface. This can be done by creating mapping fields, creating indexes, migrating data, etc. Based on the obtained mapping functions, the mapping relationship between the second interface system variable set and the first interface system variable set can be obtained.

[0069] In some embodiments, after the software configuration mapping tool obtains the mapping relationship between the second interface system variable set and the first interface system variable set, it can generate a file that can be referenced by the testing software. Taking the CANoe testing tool as an example, the software configuration mapping tool can output the mapping relationship as a .can format file that the CANoe testing tool can reference. By referencing this file, the CANoe testing tool can obtain the mapping relationship between the second interface system variable set and the first interface system variable set, thereby mapping the second test interface to the first test interface.

[0070] By accurately establishing the mapping relationship between variables, the accuracy of simulation tests can be improved.

[0071] According to some embodiments of this application, the test method 100 further includes:

[0072] After step 130: Set the first interface system variable set to the initial system variable set.

[0073] After mapping the second test interface to the first test interface, the first test interface can be initialized. Continuing with the example of the second test interface being the dry contact of the electrical chamber fan, when the dry contact of the electrical chamber fan is mapped to the first test interface of the test platform, the corresponding variables can be initialized. For example, the initial system variable set could be to set the drive variable representing on / off state to a closed state.

[0074] By setting the first interface system variable set to the initial system variable set, the interface state can be initialized, reducing interference with test results and improving test accuracy.

[0075] According to some embodiments of this application, the testing method 100 further includes: identifying at least one test board.

[0076] In the example using the VT system as the test platform, the test board is the VT board. Before testing the BMS, it is necessary to identify each VT board and perform corresponding tests on the BMS based on the respective VT boards.

[0077] By accurately identifying the test boards in the testing platform, accurate simulation testing can be achieved, thereby improving the accuracy of test results.

[0078] According to some embodiments of this application, the testing method 100 further includes: determining a first test board from at least one test board based on a first interface system variable set. The first test board is used to test the battery management system.

[0079] Continuing with the example of the VT board as the test board, based on the functions required for the test, the VT board to be used in this test can be determined from multiple VT boards, and the VT board can be used to perform the corresponding tests on the BMS.

[0080] Based on the function to be tested, the test board to be used is selected from multiple test boards to achieve accurate simulation testing.

[0081] According to some embodiments of this application, the testing method 100 further includes: configuring a first test board according to a first interface system variable set.

[0082] After determining the test board to be used, the defined first interface system variable set can be assigned to the corresponding test board. For example, an assignment function can be used to assign all the driver variables in the first interface system variable set to the corresponding test board. The test board can then be used to implement the corresponding functions of the first test interface and perform the corresponding tests on the BMS.

[0083] By configuring the test board used for testing based on the first interface system variable set, accurate simulation testing can be achieved.

[0084] According to some embodiments of this application, at least one driving variable includes a first driving variable and a second driving variable.

[0085] The first driving variable indicates whether the first test interface is in the first driving state or the second driving state.

[0086] The second driving variable indicates the fault state injected into the first test interface.

[0087] In the example described above, the first driving variable can be a driving variable representing on / off states, and can be set to 1 or 2, where 1 represents closed and 2 represents open. The second driving variable can be a driving variable representing fault injection, and can be set to 1, 2, 3, or 4, where 1 represents shorting to the power supply, 2 represents shorting to ground, 3 represents shorting to busbar A, and 4 represents shorting to busbar B.

[0088] It should be understood that in other embodiments, the first driving variable and the second driving variable can be set according to usage requirements, and this disclosure does not limit them.

[0089] By setting different driving variables, simulation tests for different states can be achieved, thereby improving the comprehensiveness of the test results.

[0090] According to some embodiments of this application, at least one operand includes a first operand and a second operand.

[0091] The first operational variable indicates whether the second test interface is in the third or fourth driving state.

[0092] The second operand indicates the fault state injected into the second test interface.

[0093] In the example described above, the first operational variable can be an operational variable representing on / off states, and can be set to 1 or 2, where 1 represents closed and 2 represents open. The second operational variable can be an operational variable representing fault injection, and can be set to 1, 2, 3, or 4, where 1 represents short-circuiting to the power supply, 2 represents short-circuiting to ground, 3 represents short-circuiting to busbar A, and 4 represents short-circuiting to busbar B.

[0094] It should be understood that in other embodiments, the first and second operands can be set according to usage requirements, and this disclosure does not limit this.

[0095] After the second test interface is mapped to the first test interface, the simulation of the second test interface can be achieved by setting the corresponding drive variable of the first test interface. Continuing with the example of the dry contact of the electrical chamber fan, when the DI_Contact8+_Drive test interface of the test platform is mapped to the dry contact of the electrical chamber fan, setting the first drive interface of the DI_Contact8+_Drive test interface to 1 indicates that the dry contact of the electrical chamber fan is closed, and setting the second drive interface of the DI_Contact8+_Drive test interface to 1 indicates that the dry contact of the electrical chamber fan has a short circuit fault with the power supply.

[0096] By setting different operation variables, simulation tests for different states can be achieved, thereby improving the comprehensiveness of the test results.

[0097] Based on the same technical concept, embodiments of this application provide a testing apparatus for a battery management system. (Reference) Figure 3 The testing device 300 includes a first module 310, a second module 320, and a third module 330.

[0098] The first module 310 is used to determine a first interface system variable set. The first interface system variable set includes at least one driving variable. The at least one driving variable indicates at least one state of the first test interface.

[0099] The second module 320 is used to determine the second interface system variable set. The second interface system variable set includes at least one operational variable. The at least one operational variable indicates at least one state of any second test interface in the battery management system.

[0100] The third module 330 is used to map the second test interface to the first test interface based on a pre-determined mapping relationship between the second interface system variable set and the first interface system variable set.

[0101] The first module 310, the second module 320, and the third module 330 in the testing device 300 can respectively correspond to, as follows: Figure 1 Steps 110 to 130 in the test method 100 shown are not repeated here for the sake of brevity. It should be understood that, corresponding to the embodiment of test method 100, the embodiment of test apparatus 300 may also include more modules.

[0102] It should be noted that the functions of the modules discussed herein can be divided into multiple modules, and / or at least some functions of multiple modules can be combined into a single module. The specific actions performed by a particular module discussed herein include the specific module itself performing the action, or alternatively, the specific module calling or otherwise accessing another component or module that performs the action (or performs the action in conjunction with the specific module). Therefore, a specific module performing an action may include the specific module performing the action itself and / or another module that performs the action, called or otherwise accessed by the specific module. For example, in some embodiments, the first module 310 and the second module 320 may be combined into a single module.

[0103] It should also be understood that this article can describe various technologies in the general context of software and hardware components or program modules. The above regarding... Figure 3The various modules described can be implemented in hardware or in hardware in combination with software and / or firmware. For example, these modules can be implemented as computer program code / instructions configured to execute in one or more processors and stored in a computer-readable storage medium. Alternatively, these modules can be implemented as hardware logic / circuit. For example, in some embodiments, one or more of the first module 310, the second module 320, and the third module 330 can be implemented together in a System on Chip (SoC). The SoC may include an integrated circuit chip (which includes a processor (e.g., a Central Processing Unit (CPU), microcontroller, microprocessor, digital signal processor (DSP), etc.), memory, one or more communication interfaces, and / or one or more components of other circuitry) and may optionally execute received program code and / or include embedded firmware to perform functions.

[0104] This application provides a computing device. The computing device includes: at least one processor; and at least one memory communicatively connected to the at least one processor, the at least one memory storing instructions that, when executed individually or jointly by the at least one processor, cause the computing device to perform test method 100. The computing device is, for example, as shown in the example... Figure 4 The computing device 400 shown. Figure 4 An example configuration of a computing device 400 that can be used to implement the methods described herein is shown. For example, the test apparatus 300 described above can be implemented wholly or at least partially by the computing device 400 or a similar device or system.

[0105] The computing device 400 may include at least one processor 402, a memory 404, multiple communication interfaces 406, a display device 408, other input / output (I / O) devices 410, and one or more mass storage devices 412 capable of communicating with each other, such as via a system bus 414 or other suitable connections. Instructions are stored on the memory 404 that, when executed by the processor 402, cause the processor 402 to perform the methods described in the above embodiments.

[0106] The computing device 400 can be a variety of different types of devices. Examples of the computing device 400 include, but are not limited to: desktop computers, server computers, laptop or netbook computers, mobile devices (e.g., tablets, cellular or other wireless phones (e.g., smartphones), notebook computers, mobile stations), wearable devices (e.g., glasses, watches), entertainment devices (e.g., entertainment appliances, set-top boxes communicatively coupled to a display device, game consoles), televisions or other display devices, automotive computers, and so on.

[0107] Processor 402 may be a single processing unit or multiple processing units, and all processing units may include single or multiple computing units or multiple cores. Processor 402 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuits, and / or any device that manipulates signals based on operating instructions. Among other capabilities, processor 402 may be configured to acquire and execute computer-readable instructions stored in memory 404, mass storage device 412, or other computer-readable media, such as program code of operating system 416, program code of application program 418, program code of other program 420, etc.

[0108] Memory 404 and mass storage device 412 are examples of computer-readable storage media for storing instructions that are executed by processor 402 to perform the various functions described above. For example, memory 404 may generally include both volatile and non-volatile memory (e.g., RAM, ROM, etc.). Furthermore, mass storage device 412 may generally include hard disk drives, solid-state drives, removable media, including external and removable drives, memory cards, flash memory, floppy disks, optical disks (e.g., CDs, DVDs), storage arrays, network-attached storage, storage area networks, etc. Both memory 404 and mass storage device 412 may be collectively referred to herein as memory or computer-readable storage media, and may be non-transitory media capable of storing computer-readable, processor-executable program instructions as computer program code, which may be executed by processor 402 as a specific machine configured to perform the operations and functions described in the examples herein.

[0109] Multiple programs may be stored on mass storage device 412. These programs include operating system 416, one or more application programs 418, other programs 420, and program data 422, and they may be loaded into memory 404 for execution. Examples of such application programs or program modules may include, for example, computer program logic (e.g., computer program code or instructions) for implementing components / functions such as: test apparatus 300 (including first module 310, second module 320, and third module 330), test method 100 (including any suitable steps of test method 100), and / or other embodiments described herein.

[0110] Although Figure 4 The data is illustrated as being stored in memory 404 of computing device 400, but operating system 416, one or more application programs 418, other programs 420 and program data 422 or portions thereof may be implemented using any form of computer-readable medium accessible by computing device 400.

[0111] One or more communication interfaces 406 are used for exchanging data with other devices, such as via a network, direct connection, etc. Such communication interfaces can be one or more of the following: any type of network interface (e.g., a network interface card (NIC)), wired or wireless (such as IEEE 802.11 Wireless LAN (WLAN)) wireless interface, Wi-MAX interface, Ethernet interface, Universal Serial Bus (USB) interface, cellular network interface, Bluetooth™ interface, Near Field Communication (NFC) interface, etc. Communication interface 406 can facilitate communication across a variety of network and protocol types, including wired networks (e.g., LAN, cable, etc.) and wireless networks (e.g., WLAN, cellular, satellite, etc.), the Internet, etc. Communication interface 406 can also provide communication with external storage devices (not shown), such as storage arrays, network-attached storage, storage area networks, etc.

[0112] In some examples, a display device 408, such as a monitor, may be included for displaying information and images to the user. Other I / O devices 410 may be devices that receive various inputs from the user and provide various outputs to the user, and may include touch input devices, gesture input devices, cameras, keyboards, remote controls, mice, printers, audio input / output devices, and so on.

[0113] The technologies described herein can be supported by these various configurations of computing device 400, and are not limited to specific examples of the technologies described herein. For example, the functionality can also be implemented wholly or partially on a “cloud” using a distributed system. A cloud includes and / or represents a platform for resources. The platform abstracts the underlying functionality of the cloud’s hardware (e.g., servers) and software resources. Resources may include applications and / or data that can be used when performing computational processing on servers remote from computing device 400. Resources may also include services provided via the Internet and / or via subscriber networks such as cellular or Wi-Fi networks. The platform can abstract resources and functionality to connect computing device 400 to other computing devices. Therefore, the implementation of the functionality described herein can be distributed throughout the cloud. For example, the functionality may be implemented partly on computing device 400 and partly through a platform that abstracts the functionality of the cloud.

[0114] This application also provides a computer-readable storage medium storing instructions thereon, which, when executed by a processor, cause the processor to perform the method as described in any of the above embodiments.

[0115] Computer-readable storage media include volatile and non-volatile, removable and non-removable media implemented by any method or technology for storing information such as computer-readable instructions, data structures, program modules, or other data. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, Digital Universal Disc (DVD) or other optical storage devices, magnetic cassettes, magnetic tapes, disk storage devices or other magnetic storage devices, or any other non-transfer medium that can be used to store information for access by a computing device.

[0116] This application also provides a computer program product, including instructions that, when executed by a processor, cause the processor to perform the methods as described in any of the above embodiments.

[0117] A specific embodiment of this application is described below. It should be understood that this specific embodiment is described for illustrative purposes only and should not be construed as limiting the scope of this application.

[0118] Based on the current software configuration table of the BMS, the second test interface to be tested can be identified. Using the BMS software configuration table as input to the software configuration mapping tool, the relevant functional configuration parameters of the second test interface in the software can be identified based on the configuration parameters for related functions in the software configuration table. Taking the identified second test interface as the dry contact of the electrical compartment fan as an example, the corresponding second interface system variable set is determined. The second interface system variable set includes a first operational variable and a second operational variable. The first driving variable is a driving variable representing on / off switching, which can be set to 1 or 2, where 1 indicates the electrical compartment fan dry contact is closed, and 2 indicates the electrical compartment fan dry contact is open. The second driving variable is a driving variable representing fault injection, which can be set to 1, 2, 3, or 4, where 1 indicates the electrical compartment fan dry contact is shorted to the power supply, 2 indicates the electrical compartment fan dry contact is shorted to ground, 3 indicates the electrical compartment fan dry contact is shorted to busbar A, and 4 indicates the electrical compartment fan dry contact is shorted to busbar B.

[0119] Taking the test interface named DI_Contact8+_Drive in the VT system as an example, we determine the corresponding first interface system variable set. The first interface system variable set includes a first drive variable and a second drive variable. The first drive variable represents the on / off state and can be set to 1 or 2, where 1 represents closed and 2 represents open. The second drive variable represents the fault injection drive variable and can be set to 1, 2, 3, or 4, where 1 represents short-circuiting to the power supply, 2 represents short-circuiting to ground, 3 represents short-circuiting to busbar A, and 4 represents short-circuiting to busbar B.

[0120] The system identifies each VT board in the VT testing system and determines the VT board to be used in this test. Using an assignment function, all driver variables in the first interface system variable set are assigned to the corresponding test board, which then implements the corresponding function of the first test interface.

[0121] Based on the .can format file output by the software configuration mapping tool, the mapping relationship between the second interface system variable set and the first interface system variable set can be obtained. According to this mapping relationship, the second test interface (i.e., the dry contact of the electrical compartment fan) can be mapped to the first test interface (i.e., the DI_Contact8+_Drive test interface). Simulation of the second test interface can be achieved by setting the corresponding drive variable for the first test interface. For example, when the DI_Contact8+_Drive test interface is mapped to the electrical compartment fan dry contact, setting the first drive interface of the DI_Contact8+_Drive test interface to 1 indicates that the electrical compartment fan dry contact is closed, and setting the second drive interface of the DI_Contact8+_Drive test interface to 1 indicates that the electrical compartment fan dry contact has a short circuit fault with the power supply. This allows for the simulation switching of the electrical compartment fan dry contact state and related fault injection simulation tests.

[0122] When the BMS software version is switched or the BMS hardware channel is switched, the above steps can be repeated to identify the second test interface to be tested and map it to the first test interface. Thus, the simulation test of the second test interface to be tested can be realized through the first test interface.

[0123] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and not to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. These modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application, and they should all be covered within the scope of the claims and specification of this application. In particular, as long as there is no structural conflict, the various technical features mentioned in the embodiments can be combined in any way. This application is not limited to the specific embodiments disclosed herein, but includes all technical solutions falling within the scope of the claims.

Claims

1. A test method for a battery management system, characterized in that, include: A first interface system variable set is determined, the first interface system variable set includes at least one driving variable, the at least one driving variable indicates at least one state of the first test interface, the first test interface includes a test interface of a test platform for testing the battery management system; Identify a second test interface to be tested in the battery management system. The second test interface is used to indicate hardware channels under different functions in the battery management system. The identification of the second test interface to be tested in the battery management system includes: identifying the second test interface to be tested according to the software configuration table of the battery management system software. Determine a second interface system variable set, the second interface system variable set including at least one operational variable, the at least one operational variable indicating at least one state of any second test interface in the battery management system, wherein determining the second interface system variable set includes: determining a second interface system variable corresponding to the second test interface to be tested in the battery management system; and Based on a pre-determined mapping relationship between the second interface system variable set and the first interface system variable set, the second test interface is mapped to the first test interface. This mapping relationship is pre-determined according to the following steps: After determining the second interface system variable set: Establish a mapping function between each of the at least one operational variable and its corresponding driving variable; A reference file is generated based on the mapping function, and the reference file is used by test software that tests the battery management system; and The testing software obtains the mapping relationship based on the reference file.

2. The test method according to claim 1, characterized in that, The at least one operational variable corresponds one-to-one with the at least one driving variable.

3. The test method according to claim 1, characterized in that, The step of mapping the second test interface to the first test interface based on a pre-determined mapping relationship between the second interface system variable set and the first interface system variable set includes: Based on the mapping relationship, values ​​are assigned to the corresponding driving variables according to each of the at least one operational variable.

4. The test method according to any one of claims 1-3, characterized in that, The testing method also includes: After mapping the second test interface to the first test interface based on the predetermined mapping relationship between the second interface system variable set and the first interface system variable set: Set the first interface system variable set as the initial system variable set.

5. The test method according to any one of claims 1-3, characterized in that, The testing method also includes: Identify at least one test board.

6. The test method according to claim 5, characterized in that, The testing method also includes: Based on the first interface system variable set, a first test board is determined from the at least one test board, and the first test board is used to test the battery management system.

7. The test method according to claim 6, characterized in that, The testing method also includes: Configure the first test board according to the first interface system variable set.

8. The test method according to any one of claims 1-3, characterized in that, The at least one driving variable includes: A first driving variable, which indicates whether the first test interface is in a first driving state or a second driving state; and The second driving variable indicates the fault state injected into the first test interface.

9. The test method according to any one of claims 1-3, characterized in that, The at least one operational variable includes: A first operand, indicating whether the second test interface is in a third or fourth driving state; and The second operational variable indicates the fault state injected into the second test interface.

10. A testing apparatus for a battery management system, characterized in that, include: The first module is used to determine a first interface system variable set, the first interface system variable set including at least one driving variable, the at least one driving variable indicating at least one state of the first test interface, the first test interface including a test interface of a test platform for testing the battery management system. The second module is used to identify a second test interface to be tested in the battery management system. The second test interface indicates hardware channels under different functions in the battery management system. Identifying the second test interface to be tested in the battery management system includes: identifying the second test interface to be tested according to the software configuration table of the battery management system software; determining a set of second interface system variables, the second interface system variable set including at least one operational variable, the at least one operational variable indicating at least one state of any second test interface in the battery management system; and determining the set of second interface system variables includes: determining the second interface system variable corresponding to the second test interface in the battery management system based on the second test interface to be tested; and The third module is used to map the second test interface to the first test interface based on a predetermined mapping relationship between the second interface system variable set and the first interface system variable set. The mapping relationship is predetermined according to the following steps: after determining the second interface system variable set: establishing a mapping function between each of the at least one operational variable and its corresponding driving variable; generating a reference file according to the mapping function, the reference file being referenced by test software testing the battery management system; and the test software obtaining the mapping relationship based on the reference file.

11. A computing device, comprising: At least one processor; as well as At least one memory communicatively connected to the at least one processor, the at least one memory storing instructions that, when executed individually or jointly by the at least one processor, cause the computing device to perform the test method of any one of claims 1 to 9.

12. A computer-readable storage medium storing instructions that, when executed individually or jointly by one or more processors of a computing device, cause the computing device to perform the test method of any one of claims 1 to 9.

13. A computer program product comprising instructions that, when executed individually or jointly by one or more processors of a computing device, cause the computing device to perform the test method of any one of claims 1 to 9.

Images