Parameter calibration method and device, equipment and storage medium

Abstract

The embodiment of the invention provides a parameter calibration method and device, equipment and a storage medium, and relates to the technical field related to batteries. The method is applied to a main control unit of the distributed battery management system, the main control unit is connected with a plurality of slave control units of the distributed battery management system through a CAN bus, and the method comprises the following steps: reading parameter configuration information of each slave control unit from a memory in a power-on initialization process of the distributed battery management system, calculating a first check code of the slave control unit according to the parameter configuration information of the slave control unit; waking up the slave control unit, and receiving a second check code uploaded by the slave control unit; wherein the second check code is a check code calculated by the slave control unit according to respective parameter configuration information; and calibrating the slave control unit according to the first check code and the second check code. The method is used for achieving the effects of improving calibration reliability, safety, efficiency and the like.

Description

Technical Field

[0001] The present application relates to the technical field of batteries, and in particular to a parameter calibration method, apparatus, device and storage medium. Background Art

[0002] A distributed battery management system (BMS) is an emerging battery management architecture that enables real-time monitoring and management of battery packs through the collaboration of multiple slave control units (SCUs) and a master control unit (SCU). To accurately monitor and control battery status, parameter calibration of the slave control units in a distributed BMS is required.

[0003] In the prior art, parameter calibration of a distributed battery management system usually relies on all slave control units uploading all parameter configuration information after the initial parameter configuration is completed, and then the master control unit compares these parameter configuration information one by one.

[0004] However, when calibrating a large number of slave control units, the above method may cause the calibration process to take a long time, and errors are prone to occur during the communication process. There is also a risk of parameter configuration information leakage, and the reliability is not high enough. Summary of the Invention

[0005] The embodiments of the present application provide a parameter calibration method, apparatus, device, and storage medium to achieve the effects of improving calibration reliability, safety, and efficiency.

[0006] In a first aspect, an embodiment of the present application provides a parameter calibration method, which is applied to a master control unit of a distributed battery management system, wherein the master control unit is connected to multiple slave control units of the distributed battery management system via a CAN bus, and the method includes:

[0007] During the power-on initialization process of the distributed battery management system, parameter configuration information of each slave control unit is read from a memory, and a first check code of the slave control unit is calculated according to the parameter configuration information of the slave control unit;

[0008] Waking up the slave control unit and receiving a second verification code uploaded by the slave control unit; wherein the second verification code is a verification code calculated by the slave control unit according to its own parameter configuration information;

[0009] The slave control unit is calibrated according to the first check code and the second check code.

[0010] In a possible implementation manner, calibrating the slave control unit according to the first verification code and the second verification code includes:

[0011] If it is determined that among the plurality of slave control units, there is a slave control unit whose first check code is inconsistent with the second check code, performing configuration processing on the target slave control unit; wherein the target slave control unit is a slave control unit that needs to be reconfigured;

[0012] After determining that the first check code and the second check code of each slave control unit are respectively consistent, a collection instruction is sent to each slave control unit; wherein the collection instruction is used to instruct the slave control unit to perform data collection.

[0013] In a possible implementation manner, the configuring the target slave control unit includes:

[0014] Determine the target slave control unit;

[0015] According to the address number of the target slave control unit, parameter calibration instructions are sent to the target slave control unit in sequence; wherein the parameter calibration instructions include parameter configuration information of the target slave control unit, and the parameter calibration instructions are used to instruct the target slave control unit to perform parameter configuration based on the parameter configuration information.

[0016] In a possible implementation, determining the target slave control unit includes:

[0017] Make sure all slave units are target slave units.

[0018] In a possible implementation, determining the target slave control unit includes:

[0019] Obtaining a proportion of slave control units whose first check code and second check code are inconsistent;

[0020] If the proportion is greater than or equal to a preset threshold, it is determined that all slave-controlled units are target slave-controlled units;

[0021] If the proportion is smaller than the preset threshold, the slave control unit whose first verification code and second verification code are inconsistent is determined to be the target slave control unit.

[0022] In a possible implementation manner, sending parameter calibration instructions to the target slave control units in sequence according to the address numbers of the target slave control units includes:

[0023] Generating parameter calibration instructions of the target slave control units in sequence according to the order of the address numbers of the target slave control units;

[0024] The address number of the target slave control unit is filled in the message of the parameter calibration instruction of the target slave control unit, and the message is sent through the CAN bus.

[0025] In one possible implementation, the method further includes:

[0026] If after a preset time period, there is still a slave control unit among the multiple slave control units whose first verification code is inconsistent with the second verification code, an alarm message is output; wherein the alarm message is used to indicate that the slave control unit whose first verification code is inconsistent with the second verification code is faulty.

[0027] In a second aspect, an embodiment of the present application provides a parameter calibration device, which is applied to a master control unit of a distributed battery management system, wherein the master control unit is connected to multiple slave control units of the distributed battery management system via a CAN bus, and the device includes:

[0028] a first processing unit, configured to read parameter configuration information of each slave control unit from a memory during power-on initialization of the distributed battery management system, and calculate a first check code of the slave control unit according to the parameter configuration information of the slave control unit;

[0029] A second processing unit is configured to wake up the slave control unit and receive a second verification code uploaded by the slave control unit; wherein the second verification code is a verification code calculated by the slave control unit according to its own parameter configuration information;

[0030] The third processing unit is configured to calibrate the slave control unit according to the first check code and the second check code.

[0031] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a memory, a processor;

[0032] The memory stores computer-executable instructions;

[0033] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the above first aspect and / or various possible implementations of the first aspect.

[0034] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the first aspect above and / or various possible implementation methods of the first aspect.

[0035] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the above first aspect and / or various possible implementation methods of the first aspect.

[0036] The parameter calibration method, device, equipment and storage medium provided in the embodiments of the present application are applied to the main control unit of the distributed battery management system. The main control unit actively verifies and calibrates the slave control according to the parameter configuration information of the internally stored slave control unit during each power-on initialization process of the distributed battery management system. This not only ensures the normal operation of the BMS system and significantly improves the reliability and safety of the distributed battery management system, but also facilitates the standardized production of the slave control unit and realizes the automatic calibration of the slave control. At the same time, in the case where the parameter configuration information of the slave control unit changes, there is no need to repeatedly confirm the slave control configuration information. It is only necessary to modify and update the configuration information stored in the main control unit. By re-powering on the distributed battery management system, the main control unit can be triggered to actively calibrate the slave control unit. In addition, the present application utilizes the efficient communication capability of the CAN bus to ensure the real-time nature of parameter verification, and can quickly identify and handle configuration inconsistencies, reducing the potential safety hazards that may be caused by configuration errors. In addition, the master and slave controllers each calculate a check code using their own stored parameter configuration information, and the master control unit determines whether they are consistent, rather than comparing the parameters one by one. This not only simplifies the verification steps, making the interaction process shorter and more efficient, and making it easier to implement, but also reduces the risk of parameter configuration information leakage. The automated parameter calibration method provided in the embodiment of the present application not only simplifies the calibration process but also improves the reliability and security of calibration. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0038] Figure 1 A schematic diagram of the connection between a master control unit and a slave control unit in a distributed battery management system provided in an embodiment of the present application;

[0039] Figure 2 A flow chart of a parameter calibration method provided in an embodiment of the present application;

[0040] Figure 3 A flow chart of another parameter calibration method provided in an embodiment of the present application;

[0041] Figure 4 A schematic diagram of the structure of a parameter calibration device provided in an embodiment of the present application;

[0042] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

[0043] The above drawings illustrate specific embodiments of the present application, which will be described in more detail below. These drawings and the textual description are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0044] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0045] The Battery Management System (BMS) plays a vital role in ensuring the safety, reliability, and performance of power battery packs. With the rapid development of electric vehicles and energy storage systems, distributed battery management systems (BMSs), an emerging battery management architecture, are being widely adopted in electric vehicles, electric heavy-duty trucks, and other fields. Distributed BMSs monitor and manage battery packs through multiple slave control units (SCUs). These SCUs work in conjunction with the master control unit (SCU) to precisely monitor and control battery status. In this architecture, parameter calibration is a key step in ensuring proper system operation and optimizing performance.

[0046] In one example, during parameter calibration of a distributed battery management system, parameter write confirmation is performed on slave control units only at the end of production, and no further verification is performed during subsequent system operation. This approach struggles to meet the requirements for efficiency, convenience, and stability during production and use. In particular, it cannot adaptively adjust parameter configurations when battery packs are replaced (parameter configuration information remains unchanged) or when battery pack specifications change in new projects (parameter configuration information changes), limiting the system's adaptability.

[0047] In another example, the parameter calibration of a distributed battery management system relies on all slave control units uploading all parameter configuration information or corresponding verification codes after the initial parameter configuration is completed, and then the master control unit compares these parameter configuration information or verification codes one by one. When processing a large number of slave control units, this method may cause the calibration process to take a long time, and errors are prone to occur during the communication process. There is also a risk of parameter configuration information leakage, and the reliability is not high enough; in addition, whether to perform parameter calibration is determined by the slave control unit, and the calibration result depends only on the information exchanged between the slave control unit and the master control unit, which is not conducive to fault analysis during the parameter calibration process. At the same time, for the situation where the parameter configuration information of the battery pack changes during use, no effective parameter calibration solution is provided.

[0048] In order to solve the above technical problems, the present application provides a parameter calibration method for a master control unit applied to a distributed battery management system, wherein the master control unit triggers the parameter calibration process during the power-on initialization process of the distributed battery management system, and parameter calibration is performed during each power-on initialization process. During each parameter calibration, the master control unit actively calculates the check code in real time based on the parameter configuration information in the memory, and compares it with the check code uploaded by the slave control unit, thereby completing the parameter calibration of the slave control unit. This not only ensures the normal operation of the battery management system, but also is conducive to the standardized production of the slave control unit and realizes automatic calibration of the slave control unit, thereby improving the calibration reliability and avoiding the problem of inaccurate calibration results due to parameter changes.

[0049] The following specific embodiments describe in detail the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0050] For example, Figure 1 This is a schematic diagram of the connection between the master control unit and the slave control unit in a distributed battery management system provided in an embodiment of the present application. Figure 1 As shown, the distributed battery management system includes at least one master control unit and multiple slave control units. The master control unit is connected to the multiple slave control units via a CAN (Controller Area Network) bus. The number of slave control units is typically the same as the number of battery modules, meaning that one slave control unit is responsible for monitoring and managing one battery module. The specific details depend on the battery design and are not limited in this embodiment of the application.

[0051] Figure 2 The parameter calibration method provided in the embodiment of the present application can be applied to the following examples: Figure 1 The main control unit of the distributed battery management system shown is connected to multiple slave control units of the distributed battery management system via a CAN bus. Figure 2 As shown, the parameter calibration method provided in the embodiment of the present application may include:

[0052] S201 . During power-on initialization of a distributed battery management system, parameter configuration information of each slave control unit is read from a memory, and a first check code of the slave control unit is calculated based on the parameter configuration information of the slave control unit.

[0053] For example, in a distributed battery management system (hereinafter referred to as a distributed BMS), a master control unit needs to work in conjunction with multiple slave control units. Each slave control unit has corresponding parameter configurations, which may be the same or different. These configurations may include parameter information such as the number of single cell voltage and temperature collections and channel allocation. To ensure battery status monitoring accuracy, system safety, and consistency, it is necessary to verify the correctness of the slave control unit parameter configurations.

[0054] In this embodiment of the present application, to ensure reliable operation of the distributed BMS in any operating cycle, the master unit performs a parameter calibration process during initialization each time the system is powered on. Specifically, the master unit first verifies the parameter configuration information of the slave unit and, based on the verification result, determines whether to issue a reconfiguration instruction. If so, the slave unit parameter information configuration process begins; if not, the verification process exits, and the master and slave units continue to exchange data collection values ​​such as cell voltage and temperature as normal.

[0055] When verifying the parameter configuration information of a slave control unit, the master control unit first reads each slave control unit's parameter configuration information from memory. This parameter configuration information is either a pre-stored standard configuration or the most recently calibrated configuration parameters. Based on the parameter configuration information read from each slave control unit, the master control unit uses a cyclic redundancy check (CRC) algorithm to calculate a check code for each slave control unit. This code serves as the first check code for that slave control unit and is used for subsequent parameter verification.

[0056] It should be noted that the CRC algorithm is an algorithm used to detect errors during data transmission or storage. It generates a short, fixed-length (e.g., 16-bit, 32-bit, etc.) binary sequence by performing mathematical operations on data, known as a checksum or checksum. It has advantages such as high computational efficiency and simple implementation. In practical applications, other algorithms may also be used to calculate the checksum, and this is not a limitation in the present embodiment.

[0057] S202 , waking up the slave control unit and receiving a second verification code uploaded by the slave control unit; wherein the second verification code is a verification code calculated by the slave control unit according to its own parameter configuration information.

[0058] For example, the master control unit can send a specific signal or command to each slave control unit via the CAN bus to wake up each slave control unit. After being woken up, each slave control unit will calculate a corresponding check code based on its internally stored parameter configuration information using the same algorithm as the master control unit (such as a CRC algorithm), which serves as the second check code and is then uploaded to the master control unit.

[0059] S203: Calibrate the slave control unit according to the first check code and the second check code.

[0060] For example, after receiving the second verification code uploaded by the slave unit, the master unit compares it with the previously calculated first verification code to calibrate the slave unit. If the first and second verification codes match, the slave unit's parameter configuration is correct, and the master unit can confirm the slave unit's status and continue normal operation. If the verification codes disagree, the slave unit's parameter configuration may be incorrect, and the master unit needs to take appropriate measures for the slave unit, such as reconfiguring parameters, issuing warnings, or shutting down the system, to prevent potential risks. By automatically verifying the slave unit's parameter configuration during the initialization phase, the safety and reliability of the entire battery management system can be ensured.

[0061] Optionally, in a possible embodiment, calibrating the slave control unit according to the first check code and the second check code may include:

[0062] S1. If it is determined that among the multiple slave control units, there is a slave control unit whose first check code and second check code are inconsistent, then configure the target slave control unit; wherein the target slave control unit is the slave control unit that needs to be reconfigured;

[0063] S2. After determining that the first check code and the second check code of each slave control unit are respectively consistent, sending a collection instruction to each slave control unit; wherein the collection instruction is used to instruct the slave control unit to perform data collection.

[0064] For example, after the master control unit calculates and compares the first check code and the second check code of each slave control unit, it may be found that the check codes of some slave control units are inconsistent. These slave control units with inconsistent check codes are the slave control units that failed this verification. When there are slave control units that failed the verification, it is necessary to enter the parameter configuration process and perform configuration processing on the target slave control unit. For example, the master control unit can re-issue the correct parameter configuration to the target slave control unit to overwrite its incorrect configuration. Through the configuration processing, the parameter configuration of the target slave control unit is corrected to ensure that its check code is consistent with the check code calculated by the master control unit.

[0065] In an embodiment of the present application, after determining that the first check code and the second check code of all slave control units are consistent, the master control unit will confirm that the parameter configuration of the entire system is correct. At this time, the master control unit will send an acquisition instruction to all slave control units to instruct the slave control units to start performing normal operating tasks, that is, to collect data. Optionally, data collection can include monitoring key parameters such as battery voltage and temperature to ensure the safety and efficient operation of the battery, which is not limited by the embodiment of the present application. After the acquisition instruction is issued, the entire distributed battery management system enters a normal operating state, and each slave control unit begins to perform its monitoring and management tasks.

[0066] Through the above method, not only can the parameter configuration of the slave control unit be automatically verified and corrected during the initialization phase, but it can also quickly enter the normal operation state after confirming that the configuration is correct. This mechanism improves the automation and reliability of the system, reduces the need for human intervention, and ensures the safety and efficiency of the battery management system.

[0067] Optionally, in a possible embodiment, performing configuration processing on the target slave control unit may include:

[0068] S11, determining the target slave control unit;

[0069] S12. Send parameter calibration instructions to the target slave control unit in sequence according to the address number of the target slave control unit; wherein the parameter calibration instruction includes parameter configuration information of the target slave control unit, and the parameter calibration instruction is used to instruct the target slave control unit to perform parameter configuration based on the parameter configuration information.

[0070] For example, when there is a slave control unit that fails the verification, the target slave control unit needs to be configured. At this time, the target slave control unit can be determined first, and then the parameter calibration instructions can be sent to each target slave control unit one by one according to the address number of the target slave control unit to ensure that each target slave control unit can receive specific parameter configuration instructions, thereby avoiding confusion or omission of instructions.

[0071] Among them, the parameter configuration instruction not only contains the correct parameter configuration information required by the target slave control unit, such as the correct number of single cell voltage / temperature collection, channel allocation, etc., but also includes a command to execute the configuration, which is used to instruct the target slave control unit to self-configure according to the correct parameter configuration information in the instruction after receiving the parameter configuration instruction. In this way, after the target slave control unit receives the parameter calibration instruction, it will update its internal parameter settings according to the configuration information in the instruction. After the update is completed, the target slave control unit can recalculate its checksum and re-check it with the master control unit to confirm the success of the configuration.

[0072] Through the above method, it is possible to effectively identify and process slave control units with inconsistent parameter configurations, and configure them one by one using address numbers, ensuring that each target slave control unit can accurately receive and execute the correct parameter configuration instructions, thereby improving the system's automation level and enhancing the system's reliability and flexibility, ensuring that the distributed battery management system can operate safely and efficiently.

[0073] Optionally, in a possible embodiment, determining the target slave control unit may include: determining that all slave control units are target slave control units.

[0074] For example, in some cases, such as when the total number of slave control units is small, the system is upgraded, the configuration policy is changed, or other reasons require a global update, all slave control units can be regarded as target slave control units, and the parameter configuration of the entire distributed battery management system can be uniformly updated. In this case, the master control unit can choose to send instructions to each slave control unit one by one, or send instructions to all slave control units at the same time by broadcasting. Sending one by one can ensure that each unit confirms receipt of the instruction, while broadcasting improves efficiency. After each slave control unit receives the parameter calibration instruction, it updates its internal parameter configuration. After the update is completed, the slave control unit can recalculate the check code and confirm with the master control unit to ensure the correctness of the configuration.

[0075] By assuming that all slave control units are target slave control units, the process of identifying and selecting the units that need to be configured is simplified. This is especially suitable for scenarios that require global updates. It can quickly and effectively configure parameters for all slave control units, ensuring the uniformity and reliability of the entire distributed battery management system.

[0076] Optionally, in a possible embodiment, determining the target slave control unit may include:

[0077] S111. Obtaining a proportion of slave control units whose first check code and second check code are inconsistent;

[0078] S112: If the proportion is greater than or equal to a preset threshold, determine that all slave control units are target slave control units;

[0079] S113 : If the proportion is less than a preset threshold, determine the slave control unit whose first verification code and second verification code are inconsistent as the target slave control unit.

[0080] For example, the need to reconfigure all slave control units can also be determined by analyzing the proportion of slave control units with inconsistent check codes. Specifically, after comparing the first check code and the second check code of each slave control unit, the master control unit counts the number of slave control units with inconsistent check codes and divides the number of slave control units with inconsistent check codes by the total number of slave control units to obtain the proportion of slave control units that failed the check. This proportion can be used to assess the severity of the parameter configuration inconsistency. The larger the proportion, the more serious the parameter configuration inconsistency.

[0081] In addition, the master control unit also pre-sets a preset threshold for determining whether all slave control units need to be reconfigured. If the proportion of inconsistent slave control units is greater than or equal to the preset threshold, it indicates that a large proportion of configuration errors exist in the slave control units. When the proportion exceeds or equals the threshold, it is determined that all slave control units are reconfigured, that is, all slave control units are determined to be target slave control units. If the proportion of inconsistent slave control units is less than the preset threshold, it indicates that the configuration error is limited to a few slave control units. In this case, only those slave control units with inconsistent check codes can be reconfigured, that is, only the slave control units that fail the check are determined to be target slave control units.

[0082] This embodiment flexibly determines the target slave control unit by checking the proportion of slave control units that fail, providing a flexible configuration strategy. Global configuration or local configuration can be selected according to actual conditions. This not only reduces unnecessary configuration operations and saves time and resources, but also improves the response speed and stability of the system, especially in the face of large-scale configuration errors, which helps to improve the efficient operation and reliability of the distributed battery management system.

[0083] Optionally, in a possible embodiment, sending parameter calibration instructions to the target slave control units in sequence according to the address numbers of the target slave control units may include:

[0084] S121, sequentially generating parameter calibration instructions for the target slave control units according to the order of the address numbers of the target slave control units;

[0085] S122 . Fill in the address number of the target slave control unit in the message of the parameter calibration instruction of the target slave control unit, and send the message through the CAN bus.

[0086] For example, each slave control unit has a unique address number, which can be used to indicate the actual physical location number of the battery module supervised by the slave control unit, usually starting from number 1 and accumulating to the total number of slave control units. In an embodiment of the present application, the target slave control units can be configured in sequence according to the order of these address numbers. For example, the master control unit can generate parameter calibration instructions for each target slave control unit in sequence according to the order of the address numbers, and fill the address number of the target slave control in the first byte of the CAN message information sent by the master control unit. In this way, after completing the information transmission of the current target slave control, the address number can be accumulated one by one according to the total number of slave control units and the operation can be repeated.

[0087] Through orderly instruction generation and sending, multiple slave control units in a distributed system can be effectively managed and configured, improving the accuracy and reliability of configuration.

[0088] Optionally, in a possible embodiment, the parameter calibration method provided in the embodiment of the present application may further include: if after a preset time period, there is still a slave control unit among multiple slave control units whose first verification code and second verification code are inconsistent, outputting an alarm message; wherein the alarm message is used to indicate that there is a fault in the slave control unit whose first verification code and second verification code are inconsistent.

[0089] For example, after the master control unit sends a parameter calibration instruction to the target slave control unit and reconfigures its parameters, the slave control unit will feedback information to the master control unit on whether the configuration is complete, and the master control unit will determine whether it has received the configuration completion feedback information reported by the slave control unit. If so, it will exit the configuration process and re-verify; if not, the master control unit can decide whether to reconfigure or report a fault based on whether the configuration has timed out. Specifically, a preset duration can be set for the parameter configuration process, which is a reasonable time range for completing the configuration and verification. It can be set based on factors such as the number of slave control units, communication and processing delays, and is not limited in the embodiments of the present application.

[0090] If after the preset time period, it is still detected that the first check code and the second check code of some slave control units are still inconsistent, it indicates that these slave control units may have communication failures, hardware failures, incorrect execution of configuration instructions, etc. The main control unit can generate and output an alarm message to indicate that the specific slave control unit has a check code inconsistency problem, so that relevant personnel can conduct troubleshooting, fault diagnosis and repair in a timely manner to ensure the normal operation of the system.

[0091] The above-mentioned fault detection and alarm mechanism not only enables the effective management and configuration of slave control units, but also enables timely detection and reporting of problems during the configuration process, helping relevant personnel to quickly locate problems, thereby reducing troubleshooting time and enhancing system reliability and security.

[0092] The parameter calibration method provided in the embodiment of the present application is applied to the main control unit of the distributed battery management system. During each power-on initialization process of the distributed battery management system, the main control unit actively verifies and calibrates the slave control according to the parameter configuration information of the internally stored slave control unit. This not only ensures the normal operation of the BMS system and significantly improves the reliability and safety of the distributed battery management system, but also facilitates the standardized production of the slave control unit and realizes automatic calibration of the slave control. At the same time, for situations such as the need to replace the battery pack (the parameter configuration information remains unchanged) or the battery pack specifications in the new project change (the parameter configuration information has changed), there is no need to repeatedly confirm the slave control configuration information. It is only necessary to modify and update the configuration information stored in the main control unit. By re-powering on the distributed battery management system, the main control unit can be triggered to actively calibrate the slave control unit. In addition, the present application utilizes the efficient communication capabilities of the CAN bus to ensure the real-time nature of parameter verification, and can quickly identify and handle configuration inconsistencies, reducing safety hazards that may be caused by configuration errors. In addition, the master and slave controllers each calculate a check code using their own stored parameter configuration information, and the master control unit determines whether they are consistent, rather than comparing the parameters one by one. This not only simplifies the verification steps, making the interaction process shorter and more efficient, and making it easier to implement, but also reduces the risk of parameter configuration information leakage. The automated parameter calibration method provided in the embodiment of the present application not only simplifies the calibration process but also improves the reliability and security of calibration.

[0093] Figure 3 A flow chart of another parameter calibration method provided in the embodiment of the present application. Figure 3 As shown, the parameter calibration method provided in this embodiment may include:

[0094] S301 . During power-on initialization of a distributed battery management system, a master control unit reads parameter configuration information of each slave control unit from a memory, and calculates a first check code of the slave control unit according to the parameter configuration information of the slave control unit.

[0095] S302: The master control unit wakes up all slave control units.

[0096] S303: The master control unit continuously receives the second verification code uploaded by the slave control unit via the CAN bus within a preset time period.

[0097] S304 : The master control unit determines, based on the calculated first check code and the second check code uploaded by the slave control unit, whether there is a slave control unit among the plurality of slave control units whose first check code is inconsistent with the second check code.

[0098] If yes, then execute step S305 within the preset time period, and execute step S308 outside the preset time period; if no, execute step S307 directly.

[0099] S305: The master control unit determines a target slave control unit.

[0100] S306 : The master control unit sends parameter calibration instructions to the target slave control units in sequence according to the address numbers of the target slave control units.

[0101] The parameter calibration instruction includes parameter configuration information for the target slave unit and is used to instruct the target slave unit to perform parameter configuration based on the parameter configuration information. After the target slave unit completes parameter configuration, it recalculates the second check code based on the updated parameter configuration information and uploads the second check code to the master unit. The master unit then executes step S303 again. If, after a preset period of time, any of the multiple slave units still have a first check code that is inconsistent with the second check code, the master unit executes step S308.

[0102] S307: The master control unit sends a collection instruction to each slave control unit.

[0103] S308: The main control unit outputs alarm information.

[0104] The alarm information is used to indicate that a fault exists in the slave control unit where the first check code and the second check code are inconsistent.

[0105] The parameter calibration method provided in the embodiment of the present application places the master-slave control verification process in the initialization process of each BMS system power-on, and confirms whether it can work normally and whether a fault needs to be reported based on the verification results, while avoiding the risk of abnormal storage and reading of parameter information in the slave control unit; at the same time, it can also match the parameter information of different power battery packs and write it into the master control unit. The slave control parameter configuration process is implemented by the master-slave control interaction, and there is no need to perform slave control unit parameter writing operation when production is offline. For situations such as the need to replace the battery pack or the battery pack specifications change in the new project, there is no need to repeatedly confirm the slave control configuration information. It is only necessary to modify and update the configuration information stored in the master control unit; the calibration reliability is significantly improved, and the problem of inaccurate calibration results due to parameter changes is avoided.

[0106] Figure 4 This is a structural diagram of a parameter calibration device provided in an embodiment of the present application. The parameter calibration device provided in an embodiment of the present application is applied to the master control unit of a distributed battery management system, and the master control unit is connected to multiple slave control units of the distributed battery management system via a CAN bus. Figure 4 As shown, the parameter calibration device 40 provided in the embodiment of the present application includes a first processing unit 401 , a second processing unit 402 and a third processing unit 403 .

[0107] The first processing unit 401 is configured to read parameter configuration information of each slave control unit from a memory during power-on initialization of the distributed battery management system, and calculate a first check code of the slave control unit based on the parameter configuration information of the slave control unit;

[0108] The second processing unit 402 is configured to wake up the slave control unit and receive a second verification code uploaded by the slave control unit; wherein the second verification code is a verification code calculated by the slave control unit according to its own parameter configuration information;

[0109] The third processing unit 403 is configured to calibrate the slave control unit according to the first check code and the second check code.

[0110] The device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effects are similar and will not be described in detail in this embodiment.

[0111] In a possible implementation, the third processing unit 403 is specifically configured to:

[0112] If it is determined that among the multiple slave control units, there is a slave control unit whose first check code and second check code are inconsistent, then configuration processing is performed on the target slave control unit; wherein the target slave control unit is the slave control unit that needs to be reconfigured;

[0113] After determining that the first check code and the second check code of each slave control unit are respectively consistent, a collection instruction is sent to each slave control unit; wherein the collection instruction is used to instruct the slave control unit to perform data collection.

[0114] In a possible implementation, the third processing unit 403 is specifically configured to:

[0115] Determine the target slave control unit;

[0116] According to the address number of the target slave control unit, parameter calibration instructions are sent to the target slave control unit in sequence; wherein the parameter calibration instructions include parameter configuration information of the target slave control unit, and the parameter calibration instructions are used to instruct the target slave control unit to perform parameter configuration based on the parameter configuration information.

[0117] In a possible implementation, the third processing unit 403 is specifically configured to:

[0118] Make sure all slave units are target slave units.

[0119] In a possible implementation, the third processing unit 403 is specifically configured to:

[0120] Obtaining a proportion of slave control units whose first check code and second check code are inconsistent;

[0121] If the proportion is greater than or equal to the preset threshold, it is determined that all slave control units are target slave control units;

[0122] If the proportion is less than a preset threshold, the slave control unit whose first verification code is inconsistent with the second verification code is determined to be the target slave control unit.

[0123] In a possible implementation, the third processing unit 403 is specifically configured to:

[0124] Generate parameter calibration instructions for the target slave control units in sequence according to the address number sequence of the target slave control units;

[0125] In the message of the parameter calibration instruction of the target slave control unit, the address number of the target slave control unit is filled in, and the message is sent through the CAN bus.

[0126] In a possible implementation, the third processing unit 403 is further configured to:

[0127] If after the preset time period, there is still a slave control unit among the multiple slave control units whose first verification code is inconsistent with the second verification code, an alarm message is output; wherein the alarm message is used to indicate that the slave control unit whose first verification code is inconsistent with the second verification code is faulty.

[0128] The device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effects are similar and will not be described in detail in this embodiment.

[0129] It should be noted that it should be understood that the division of the various modules of the above device is merely a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. Moreover, these modules can all be implemented in the form of software called by processing elements; they can also all be implemented in the form of hardware; some modules can also be implemented in the form of software called by processing elements, and some modules can be implemented in the form of hardware. In addition, they can also be stored in the memory of the above device in the form of program code, and called and executed by a processing element of the above device. The implementation of other modules is similar. In addition, these modules can all or partly be integrated together, or they can be implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules can be completed by the hardware integrated logic circuit in the processor element or by instructions in the form of software.

[0130] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 5As shown, the electronic device 50 provided in this embodiment includes: at least one processor 501 and a memory 502. Optionally, the device 50 further includes a communication component 503. The processor 501, the memory 502 and the communication component 503 are connected via a bus 504.

[0131] In a specific implementation process, at least one processor 501 executes the computer-executable instructions stored in the memory 502, so that the at least one processor 501 performs the above method.

[0132] The specific implementation process of the processor 501 can be found in the above method embodiment. Its implementation principle and technical effects are similar and will not be repeated here in this embodiment.

[0133] In the above embodiments, it should be understood that the processor may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASICs), etc. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the present invention may be directly executed by a hardware processor or by a combination of hardware and software modules within the processor.

[0134] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage.

[0135] A bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. Buses can be categorized as address buses, data buses, and control buses. For ease of illustration, the buses in the drawings of this application are not limited to just one bus or just one type of bus.

[0136] The present application also provides a computer program product, including a computer program, which implements the above method when executed by a processor.

[0137] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the above method is implemented.

[0138] The readable storage medium may be implemented by any type of volatile or non-volatile memory device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0139] An exemplary readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be an integral part of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the readable storage medium can also exist in the device as discrete components.

[0140] The division of units is merely a logical functional division; actual implementations may employ alternative divisions, such as combining or integrating multiple units or components into another system, or omitting or disabling certain features. Furthermore, any direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between devices or units, either through an interface, electrical, mechanical, or other means.

[0141] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0142] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0143] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the portion that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the method of the present invention. The aforementioned storage medium includes various media that can store program code, such as USB flash drives, mobile hard drives, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical disks.

[0144] Those skilled in the art will appreciate that all or part of the steps in the above-described method embodiments can be implemented using hardware associated with program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0145] Finally, it should be noted that those skilled in the art will readily identify other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present invention is intended to cover any variations, uses, or adaptations of the present invention that follow the general principles of the present invention and include common knowledge or customary techniques in the art not disclosed herein. The present invention is not limited to the precise structure described above and illustrated in the accompanying drawings, and various modifications and variations may be made without departing from the scope thereof. The scope of the present invention is limited solely by the appended claims.

Claims

1. A parameter calibration method, characterized in that: The method is applied to a master control unit of a distributed battery management system, wherein the master control unit is connected to a plurality of slave control units of the distributed battery management system via a CAN bus, and the method comprises: During the power-on initialization process of the distributed battery management system, parameter configuration information of each slave control unit is read from a memory, and a first check code of the slave control unit is calculated according to the parameter configuration information of the slave control unit; Waking up the slave control unit and receiving a second verification code uploaded by the slave control unit; wherein the second verification code is a verification code calculated by the slave control unit according to its own parameter configuration information; The slave control unit is calibrated according to the first check code and the second check code.

2. The method according to claim 1, characterized in that The calibrating the slave control unit according to the first check code and the second check code includes: If it is determined that among the plurality of slave control units, there is a slave control unit whose first check code is inconsistent with the second check code, performing configuration processing on the target slave control unit; wherein the target slave control unit is a slave control unit that needs to be reconfigured; After determining that the first check code and the second check code of each slave control unit are respectively consistent, a collection instruction is sent to each slave control unit; wherein the collection instruction is used to instruct the slave control unit to perform data collection.

3. The method according to claim 2, characterized in that The configuring process of the target slave control unit includes: Determine the target slave control unit; According to the address number of the target slave control unit, parameter calibration instructions are sent to the target slave control unit in sequence; wherein the parameter calibration instructions include parameter configuration information of the target slave control unit, and the parameter calibration instructions are used to instruct the target slave control unit to perform parameter configuration based on the parameter configuration information.

4. The method according to claim 3, characterized in that The determining of the target slave control unit includes: Make sure all slave units are target slave units.

5. The method according to claim 3, characterized in that The determining of the target slave control unit includes: Obtaining a proportion of slave control units whose first check code and second check code are inconsistent; If the proportion is greater than or equal to a preset threshold, it is determined that all slave-controlled units are target slave-controlled units; If the proportion is smaller than the preset threshold, the slave control unit whose first verification code and second verification code are inconsistent is determined to be the target slave control unit.

6. The method according to claim 3, characterized in that The sending parameter calibration instructions to the target slave control unit in sequence according to the address number of the target slave control unit includes: Generating parameter calibration instructions of the target slave control units in sequence according to the order of the address numbers of the target slave control units; The address number of the target slave control unit is filled in the message of the parameter calibration instruction of the target slave control unit, and the message is sent through the CAN bus.

7. The method according to any one of claims 2 to 6, characterized in that The method further comprises: If after a preset time period, there is still a slave control unit among the multiple slave control units whose first verification code is inconsistent with the second verification code, an alarm message is output; wherein the alarm message is used to indicate that the slave control unit whose first verification code is inconsistent with the second verification code is faulty.

8. A parameter calibration device, characterized in that: The device is applied to a master control unit of a distributed battery management system, wherein the master control unit is connected to a plurality of slave control units of the distributed battery management system via a CAN bus. The device comprises: a first processing unit, configured to read parameter configuration information of each slave control unit from a memory during power-on initialization of the distributed battery management system, and calculate a first check code of the slave control unit according to the parameter configuration information of the slave control unit; A second processing unit is configured to wake up the slave control unit and receive a second verification code uploaded by the slave control unit; wherein the second verification code is a verification code calculated by the slave control unit according to its own parameter configuration information; The third processing unit is configured to calibrate the slave control unit according to the first check code and the second check code.

9. An electronic device, characterized in that: include: Memory, processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 7 when executed by a processor.

Images