Address allocation method and system for multiple battery systems and storage medium
By automatically allocating addresses based on the feature code after powering on the battery system, using the CAN bus for real-time communication, the problem of low address allocation efficiency when multiple battery systems are connected in parallel is solved, and fast and reliable address allocation and system identification are achieved, reducing the Hardware cost and complexity.
Patent Information
- Application Number
- CN202411385526.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-30
- Publication Date
- 2025-01-10
AI Technical Summary
In the prior art, when multiple battery systems are charged and discharged in parallel, address allocation efficiency is low and error-prone, and adding hardware or wiring harness to achieve address allocation increases cost, complexity and hardware costs.
After the battery system is powered on, the current address allocation status is obtained based on the number of address allocations and the characteristic code, and the address is automatically allocated. If there is a conflict, it will be reassigned. The CAN bus is used for real-time communication to ensure address uniqueness and system identification accuracy, and reduce the number of addresses. Hardware demand, reduce costs.
It realizes fast and reliable address allocation, avoids address conflicts, improves system identification accuracy and management efficiency, reduces system design complexity and hardware costs, and enhances system transparency and fault tolerance.
Smart Images
Figure CN119299422A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of address allocation, and in particular to an address allocation method, system and storage medium for multiple battery systems. Background Art
[0002] In energy storage systems, it is common to connect multiple energy storage battery systems in parallel to meet charging and discharging requirements. When multiple battery systems are used in parallel, each system must have a separate address to facilitate the superior control unit to monitor the status of the battery system and execute corresponding strategies.
[0003] Common methods for address allocation include: manually writing addresses, which is inefficient and prone to errors. Alternatively, by adding hardware and wiring harnesses, each battery system can achieve address allocation through different electrical signals detected on the wiring harness, but this requires additional hardware costs. Summary of the invention
[0004] In order to solve the above technical problems, the present application provides an address allocation method, system and storage medium for multiple battery systems.
[0005] Specifically, the present application provides an address allocation method for multiple battery systems, where the multiple battery systems are connected in parallel, and the address allocation method comprises the following steps: After each battery system is powered on, the current address allocation state is obtained based on the number of address allocations and the corresponding feature code.
[0006] If the address is already allocated, determine whether the address of the current battery system is repeated with the addresses of other battery systems. If it is repeated or the address is not allocated, enter the address allocation process; if it is not repeated, determine that the address allocation is completed.
[0007] In the above technical solution, after the system is powered on, the address can be automatically allocated according to the feature code, and the address allocation speed is fast; if there is an address conflict, the address allocation can be re-entered, and the reliability is high; and this application does not require the addition of other hardware or wiring harnesses, only all battery systems need to be connected in parallel, which reduces the complexity of system design and saves costs.
[0008] Furthermore, each battery system uniquely corresponds to a characteristic code; the characteristic code at least includes a battery serial number, a battery production date and a battery production batch.
[0009] In the above technical solution, the introduction of the feature code ensures that each battery system has a unique identity in the entire energy storage system, which can effectively avoid address conflicts and improve the accuracy of system recognition; the detailed information contained in the feature code can promote the standardized management of the battery system and facilitate the formulation of unified management specifications and procedures, thereby improving management efficiency; with the help of the feature code, users can remotely monitor the status of each battery system through the superior control unit, obtain relevant data in a timely manner and respond, thereby improving the level of intelligent management.
[0010] Further, the obtaining of the current address allocation state based on the corresponding feature code includes: Each battery system sends a corresponding feature code to the CAN bus, and uses the sent feature code as the first feature code; at the same time, it receives all feature codes on the current CAN bus, and uses each feature code on the current CAN bus as the second feature code.
[0011] In the above technical scheme, through the real-time communication of the CAN bus, each battery system can instantly send and receive feature codes, ensure real-time updating of the system status, and improve the system response speed; using the CAN bus as a communication medium, it can be compatible with a variety of devices and systems, and facilitate the connection and collaborative work of different types of hardware; each battery system can quickly detect whether there is an address conflict through the received second feature code, improve the accuracy of address allocation, and reduce the possibility of system failure; through the sending and receiving of feature codes, the address allocation logic can be simplified, complex algorithm design can be avoided, and the simplicity and maintainability of system implementation can be improved; when multiple battery systems work in parallel, if a system fails, other systems can still independently send feature codes and compare them, thereby improving the fault tolerance and stability of the overall system; the feature codes of all battery systems are shared on the bus, which improves the transparency of the system and helps to quickly obtain and analyze the address allocation of the system.
[0012] Furthermore, the obtaining of the current address allocation state based on the corresponding feature code further includes: Based on the second feature code, it is searched whether the first feature code exists on the CAN bus. If so, it is determined that the current battery system is in an address-allocated state; otherwise, it is determined that the current battery system is in an address-unallocated state.
[0013] In the above technical solution, by searching for the existence of the first feature code on the CAN bus, the address allocation status of the battery system can be determined efficiently and accurately, and the need for address allocation can be responded to quickly; in the judgment process, if the first feature code already exists on the CAN bus, the system can immediately determine it as an allocated address state to prevent potential conflicts caused by repeated allocation; through a clear search mechanism, the reliability of the system is improved to ensure the scientificity and accuracy of the address allocation of each system when multiple battery systems are used in parallel.
[0014] Furthermore, the address allocation includes: Based on the size of the feature code and the corresponding battery production date and battery production batch, an allocatable address table of each battery system is obtained, so that the battery system selects an address according to the corresponding allocatable address table.
[0015] In the above technical solution, by analyzing the characteristic code and its production information, a reasonable and effective assignable address can be provided for each battery system, thus avoiding waste of resources and address congestion, and improving the efficiency of address management; the assignable address table is automatically generated, and the battery system selects the address according to the preset form, which greatly reduces the error probability caused by manual input or selection of the address; by designing a reasonable assignable address table, data consistency in the address allocation process is ensured, reducing confusion and incorrect configuration caused by variable factors.
[0016] Furthermore, the address allocation further includes: It is determined whether the address selected according to the allocable address table is repeated with the addresses of other battery systems. If so, the address allocation is re-entered until the address allocation is completed; otherwise, it is determined that the address allocation is completed.
[0017] In the above technical solution, by detecting in advance whether the selected address is repeated, the address of each battery system is ensured to be unique, which effectively prevents communication errors or data confusion caused by address conflicts, improves the stability of the system, and avoids failures and system crashes caused by duplicate addresses; if a conflict occurs, the system automatically enters address reallocation, showing good adaptability, helping to solve problems in a timely manner, and continuously maintaining the normal operation of the system.
[0018] Furthermore, after the address allocation is completed, the method further includes: The battery system with completed address allocation broadcasts the corresponding feature code and address to the CAN bus.
[0019] In the above technical solution, by broadcasting characteristic codes and addresses, all other devices can obtain the identity information of the battery system in real time, promoting transparency and sharing of internal information of the system; the broadcast mechanism enables information to be received by multiple devices at the same time, reducing the communication overhead of individual requests and improving overall communication efficiency.
[0020] Furthermore, after the battery system is powered on, it also includes: Determine whether the current battery system has allocated addresses for the first time. If so, obtain the current address allocation status based on the corresponding feature code; otherwise, end the process.
[0021] In the above technical solution, after the battery system allocates addresses for the first time, the battery system is in the state of having addresses. The next time it is powered on again and enters the parallel mode, it needs to enter the step of whether it has addresses.
[0022] Based on the same concept, the present application also provides a battery system, which uses the address allocation method for multiple battery systems to complete address allocation.
[0023] Based on the same concept, the present application also provides a computer-readable storage medium storing a computer program, which implements the address allocation method for multiple battery systems when executed by the battery system.
[0024] Compared with the prior art, the beneficial effects of this application are: In this application, multiple battery systems are connected in parallel. After each battery system is powered on, the current address allocation status is obtained based on the number of address allocations and the corresponding feature code. If it is an allocated address state, it is determined whether the address of the current battery system is repeated with the addresses of other battery systems. If it is repeated or in an unallocated address state, the address allocation is entered; if it is not repeated, the address allocation is determined to be complete. After the system is powered on, this application can automatically allocate addresses according to feature codes, and the address allocation speed is fast. If there is an address conflict, the address allocation can be re-entered, and the reliability is high. In addition, this application does not require the addition of other hardware or wiring harnesses, and only requires all battery systems to be connected in parallel, which reduces the complexity of system design and saves costs. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] Figure 1 The present invention is a flowchart of a method for allocating addresses for multiple battery systems.
[0026] Figure 2 Schematic diagram of the connection status of multiple battery systems. DETAILED DESCRIPTION
[0027] The following is a further detailed description of an address allocation method, system and storage medium for multiple battery systems of the present application in conjunction with specific embodiments and drawings.
[0028] Embodiment 1: See also Figure 1 The present application provides an address allocation method for multiple battery systems, wherein the multiple battery systems are connected in parallel (such as Figure 2 As shown), the address allocation method comprises the following steps: After each battery system is powered on, the current address allocation state is obtained based on the number of address allocations and the corresponding feature code.
[0029] If the address is already allocated, determine whether the address of the current battery system is repeated with the addresses of other battery systems. If it is repeated or the address is not allocated, enter the address allocation process; if it is not repeated, determine that the address allocation is completed.
[0030] Furthermore, each battery system uniquely corresponds to a characteristic code; the characteristic code at least includes a battery serial number, a battery production date and a battery production batch.
[0031] In some embodiments, the battery serial number is a combination of numbers or letters that uniquely identifies each battery pack; the battery production date format is YYYY-MM-DD, which is used to record the production date of the battery; the battery production batch is usually a code or number used to identify the production batch for easy traceability and management.
[0032] For example, a feature code may be SN-2023002-2024-09-30-BATCH01.
[0033] Among them, SN-2023002 means that the battery serial number is 2023002; 2024-09-30 means that the production date of the battery is September 30, 2024; BATCH01 means that the production batch is BATCH01.
[0034] It should be noted that the composition of the feature code is not limited to the battery serial number, battery production date and battery production batch. Those skilled in the art may also add information such as device type and manufacturer to more efficiently generate a uniquely assignable address.
[0035] In the above technical solution, the introduction of the feature code ensures that each battery system has a unique identity in the entire energy storage system, which can effectively avoid address conflicts and improve the accuracy of system recognition; the detailed information contained in the feature code can promote the standardized management of the battery system and facilitate the formulation of unified management specifications and procedures, thereby improving management efficiency; with the help of the feature code, users can remotely monitor the status of each battery system through the superior control unit, obtain relevant data in a timely manner and respond, thereby improving the level of intelligent management.
[0036] Further, the obtaining of the current address allocation state based on the corresponding feature code includes: Each battery system sends a corresponding feature code to the CAN bus, and uses the sent feature code as the first feature code; at the same time, it receives all feature codes on the current CAN bus, and uses each feature code on the current CAN bus as the second feature code.
[0037] In some embodiments, each battery system will be initialized after power-on and read its own feature code; the structure of the feature code is as described above, including the battery serial number, battery production date and battery production batch.
[0038] Furthermore, each battery system sends its signature code to the CAN bus and uses this signature code as the "first signature code"; for example, the current battery system is battery system A, and the corresponding signature code is SN-2023002-2024-09-30-BATCH01. While sending the signature code, battery system A monitors all the signature codes sent on the current CAN bus, receives and stores these signature codes as the "second signature code", and each battery system will perform this operation.
[0039] For example, the characteristic code received by battery system A includes: Battery system B: SN-2023005-2024-09-15-BATCH01; Battery system C: SN-2023006-2024-09-20-BATCH02; and so on.
[0040] In other embodiments, the characteristic code received by the battery system A may also be: Battery system A: SN-2023002-2024-09-30-BATCH01; Battery system B: SN-2023005-2024-09-15-BATCH01; Battery system C: SN-2023006-2024-09-20-BATCH02; and so on.
[0041] In other embodiments, in order to reduce network bandwidth usage, information may be compressed to a certain extent during the process of sending and receiving the feature code to reduce the amount of data transmission.
[0042] In other embodiments, a multi-level confirmation mechanism can be designed to address possible network delays, that is, the battery system waits for confirmation within a certain period of time after sending the feature code, which can reduce the chance of misjudgment; a timeout retransmission mechanism can also be designed to ensure successful feature code sending.
[0043] In addition, technicians in this field can expand the CAN bus to wireless communication according to actual application requirements to support the access of more devices and increase flexibility and compatibility; design corresponding protocols for switching between different communication modes to ensure system compatibility.
[0044] In the above technical scheme, through the real-time communication of the CAN bus, each battery system can instantly send and receive feature codes, ensure real-time updating of the system status, and improve the system response speed; using the CAN bus as a communication medium, it can be compatible with a variety of devices and systems, and facilitate the connection and collaborative work of different types of hardware; each battery system can quickly detect whether there is an address conflict through the received second feature code, improve the accuracy of address allocation, and reduce the possibility of system failure; through the sending and receiving of feature codes, the address allocation logic can be simplified, complex algorithm design can be avoided, and the simplicity and maintainability of system implementation can be improved; when multiple battery systems work in parallel, if a system fails, other systems can still independently send feature codes and compare them, thereby improving the fault tolerance and stability of the overall system; the feature codes of all battery systems are shared on the bus, which improves the transparency of the system and helps to quickly obtain and analyze the address allocation of the system.
[0045] Furthermore, the obtaining of the current address allocation state based on the corresponding feature code further includes: Based on the second feature code, it is searched whether the first feature code exists on the CAN bus. If so, it is determined that the current battery system is in an address-allocated state; otherwise, it is determined that the current battery system is in an address-unallocated state.
[0046] In some embodiments, after receiving all feature codes, battery system A traverses the "second feature code" list to check whether there is a feature code consistent with SN-2023002-2024-09-30-BATCH01.
[0047] If it exists: If the same "first characteristic code" is found, the current battery system is determined to be in the "allocated address state". This means that battery A can continue to work normally and does not need to be allocated a new address.
[0048] If not present: If no identical feature code is found, it is determined to be in "unassigned address state"; this means that battery A may need to undergo an address reallocation process to ensure that all batteries in the system have unique identification.
[0049] In the above technical solution, by searching for the existence of the first feature code on the CAN bus, the address allocation status of the battery system can be determined efficiently and accurately, and the need for address allocation can be responded to quickly; in the judgment process, if the first feature code already exists on the CAN bus, the system can immediately determine it as an allocated address state to prevent potential conflicts caused by repeated allocation; through a clear search mechanism, the reliability of the system is improved to ensure the scientificity and accuracy of the address allocation of each system when multiple battery systems are used in parallel.
[0050] Furthermore, the address allocation includes: Based on the size of the feature code and the corresponding battery production date and battery production batch, an allocatable address table of each battery system is obtained, so that the battery system selects an address according to the corresponding allocatable address table.
[0051] In some embodiments, the feature code of the battery system A is parsed to obtain the battery production date and battery production batch, and the size range of the feature code is calculated according to the character length or complexity of the feature code.
[0052] Furthermore, an address range is defined according to the battery production date, battery production batch and feature code size of battery system A. For example, if the battery production date is 2024-09-30, the battery production batch is BATCH01, and the feature code size is calculated to be 10, an address range similar to ADDR-1000 to ADDR-1999 can be generated; and finally an allocatable address table such as ADDR-1000, ADDR-1001, ADDR-1002...ADDR-1999 is formed.
[0053] Among them, it is necessary to formulate clear address generation rules in advance to ensure the readability and consistency of the addresses, and the generation of the allocatable address table should take into account the maximum possible number of battery systems and calculate the range of allocatable addresses accordingly. The configuration file can be used to set the number of allowed addresses.
[0054] In the above technical solution, by analyzing the characteristic code and its production information, a reasonable and effective assignable address can be provided for each battery system, thus avoiding waste of resources and address congestion, and improving the efficiency of address management; the assignable address table is automatically generated, and the battery system selects the address according to the preset form, which greatly reduces the error probability caused by manual input or selection of the address; by designing a reasonable assignable address table, data consistency in the address allocation process is ensured, reducing confusion and incorrect configuration caused by variable factors.
[0055] Furthermore, the address allocation further includes: It is determined whether the address selected according to the allocable address table is repeated with the addresses of other battery systems. If so, the address allocation is re-entered until the address allocation is completed; otherwise, it is determined that the address allocation is completed.
[0056] In some embodiments, battery system A selects an available address such as ADDR-1000 from the generated allocatable address table; wherein battery system A can select based on a simple priority, such as selecting the first available address in the allocatable address table to reduce network latency and improve response speed, or randomly select according to a priority strategy.
[0057] It should be noted that the address selection method can be adaptively set by those skilled in the art, and is not limited to the above two address selection methods.
[0058] Furthermore, battery system A requests the CAN bus to query the list of currently allocated addresses, and compares the selected address ADDR-1000 with the currently allocated addresses one by one to check whether there is any duplication; if the same address already exists, it is determined to be an address duplication, and battery system A will register this situation to avoid selecting the same address again when selecting an address, and then return to the address selection process in the allocable list to reselect a new address such as ADDR-1001 from the allocable list, and perform address duplication detection again until the address allocation is successful.
[0059] Furthermore, if there is no identical address after one-by-one comparison, it is directly determined that the address allocation is completed.
[0060] In other embodiments, other error conditions may occur during the address selection process, such as network failure. A retry mechanism can be designed to prevent the system from getting stuck or crashing. In addition, an upper limit can be set for the number of repeated requests to avoid infinite loops. If the upper limit is reached, the error information can be recorded in the log to notify the operation and maintenance personnel.
[0061] In the above technical solution, by detecting in advance whether the selected address is repeated, the address of each battery system is ensured to be unique, which effectively prevents communication errors or data confusion caused by address conflicts, improves the stability of the system, and avoids failures and system crashes caused by duplicate addresses; if a conflict occurs, the system automatically enters address reallocation, showing good adaptability, helping to solve problems in a timely manner, and continuously maintaining the normal operation of the system.
[0062] Furthermore, after the address allocation is completed, the method further includes: The battery system with completed address allocation broadcasts the corresponding feature code and address to the CAN bus.
[0063] In some embodiments, the battery system A undergoes a series of address selections and repeated detections, ultimately confirming that the address selected by itself is unique, and then broadcasts the selected address and the corresponding feature code to the CAN bus.
[0064] Wherein, it is necessary to construct a broadcast data packet, and the broadcast data packet includes the address and the feature code.
[0065] Furthermore, on the CAN bus, all battery systems will monitor and receive this broadcast message.
[0066] In other embodiments, in order to improve reliability, a confirmation mechanism can be designed. For example, the CAN bus responds after successfully receiving the broadcast data packet, so that the battery system A can confirm whether the broadcast is successful based on the response; if no confirmation is received, a retransmission mechanism can be designed to try to retransmit the broadcast message within a certain number of times.
[0067] In the above technical solution, by broadcasting characteristic codes and addresses, all other devices can obtain the identity information of the battery system in real time, promoting transparency and sharing of internal information of the system; the broadcast mechanism enables information to be received by multiple devices at the same time, reducing the communication overhead of individual requests and improving overall communication efficiency.
[0068] Furthermore, after the battery system is powered on, it also includes: Determine whether the current battery system has allocated addresses for the first time. If so, obtain the current address allocation status based on the corresponding feature code; otherwise, end the process.
[0069] In some embodiments, after the battery system is powered on, it starts to execute the initialization process. It first checks whether there are previously registered addresses and feature codes in its own memory, and determines whether the address is allocated for the first time based on the address. If so, it enters the detection process and obtains the current address allocation status based on the feature code corresponding to the current battery system to detect whether the same address exists on the CAN bus.
[0070] It should be noted that in the final configuration of the battery system, the allocated address and its corresponding feature code are written into a persistent memory, such as EEPROM or Flash, and the previous allocation status is read each time the power is turned on; for example, a state variable can be set to indicate whether the address is the first allocated address through the state variable. When the address is successfully allocated for the first time, the state variable is set to true, and then the next time the power is turned on, the corresponding judgment can be made based on this state variable.
[0071] In the above technical solution, after the battery system allocates addresses for the first time, the battery system is in the state of having addresses. The next time it is powered on again and enters the parallel mode, it needs to enter the step of whether it has addresses.
[0072] Embodiment 2: The present application also provides a battery system, which uses the address allocation method for multiple battery systems described in Example 1 to complete address allocation.
[0073] In some embodiments, after the battery system is powered on, it sends its own feature code to the CAN bus and simultaneously receives all feature codes on the CAN bus to determine whether the current battery system has completed address allocation; wherein the feature code includes at least the battery serial number, battery production date and battery production batch.
[0074] It should be noted that the composition of the feature code is not limited to the battery serial number, battery production date and battery production batch. Those skilled in the art may also add information such as device type and manufacturer to more efficiently generate a uniquely assignable address.
[0075] Furthermore, if the current battery system has not completed address allocation, the allocatable address table of each battery system is further obtained based on the size of the feature code and the corresponding battery production date and battery production batch, so that the battery system selects an address according to the corresponding allocatable address table.
[0076] Further, it is determined whether the address selected according to the allocatable address table is repeated with the addresses of other battery systems. If so, the address allocation is re-entered until the address allocation is completed; otherwise, it is determined that the address allocation is completed.
[0077] Furthermore, the battery system after completing address allocation broadcasts the corresponding feature code and address to the CAN bus.
[0078] In addition, after the battery system completes address allocation for the first time, the battery system has its own address status. The next time it is powered on again and enters parallel mode, it needs to confirm its current address allocation status.
[0079] In the above technical solution, the automatic allocation of battery system addresses is realized, and the address allocation efficiency is high and the reliability is also high. At the same time, each battery system only needs to be connected in parallel to realize the above address allocation method, without the need for other hardware or wiring harnesses, etc., which reduces hardware costs and reduces the complexity of system design.
[0080] Embodiment three: The present application also provides a computer-readable storage medium storing a computer program, which, when executed by the battery system, implements the address allocation method for multiple battery systems described in the first embodiment.
[0081] In some embodiments, the storage medium stores several computer programs for enabling the battery system to execute all or part of the steps of the methods described in various embodiments of the present application.
[0082] The storage medium may include a U disk, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk, and other media that can store program codes.
[0083] In summary, the present application provides an address allocation method, system and storage medium for multiple battery systems; multiple battery systems are in parallel state, and after each battery system is powered on, the current address allocation state is obtained based on the number of address allocations and the corresponding feature code; if it is in the allocated address state, it is determined whether the address of the current battery system is repeated with the addresses of the remaining battery systems, if it is repeated or in the unallocated address state, the address allocation is entered; if it is not repeated, the address allocation is determined to be completed. After the system is powered on, the present application can automatically allocate addresses according to the feature code, and the address allocation speed is fast; if there is an address conflict, the address allocation can be re-entered, and the reliability is high; and the present application does not need to add other hardware or wiring harnesses, and only needs to connect all battery systems in parallel, which reduces the complexity of system design and saves costs.
[0084] Although example embodiments have been described herein with reference to the accompanying drawings, it should be understood that the above example embodiments are merely exemplary and are not intended to limit the scope of the present application to this. Those of ordinary skill in the art may make various changes and modifications therein without departing from the scope and spirit of the present application. All these changes and modifications are intended to be included within the scope of the present application as required by the appended claims.
[0085] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0086] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed.
[0087] The various component embodiments of the present application can be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. It should be understood by those skilled in the art that a microprocessor or digital signal processor (DSP) can be used in practice to implement some or all functions of some modules according to the embodiments of the present application. The application can also be implemented as a device program (e.g., computer program and computer program product) for executing a part or all of the methods described herein. Such a program implementing the present application can be stored on a computer-readable medium, or can have the form of one or more signals. Such a signal can be downloaded from an Internet website, or provided on a carrier signal, or provided in any other form.
[0088] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.
[0089] Although the description of the present application is carried out in conjunction with the above specific embodiments, it is obvious that those skilled in the art can make many substitutions, modifications and changes based on the above content. Therefore, all such substitutions, improvements and changes are included in the spirit and scope of the appended claims.
Claims
1. A method for allocating addresses for multiple battery systems, characterized in that: A plurality of battery systems are connected in parallel, and the address allocation method comprises the following steps: After each battery system is powered on, the current address allocation status is obtained based on the number of address allocations and the corresponding feature code; If the address is already allocated, determine whether the address of the current battery system is repeated with the addresses of other battery systems. If it is repeated or the address is not allocated, enter the address allocation process; if it is not repeated, determine that the address allocation is completed.
2. The address allocation method for multiple battery systems according to claim 1, characterized in that: Each battery system uniquely corresponds to a characteristic code; the characteristic code at least includes the battery serial number, the battery production date and the battery production batch.
3. The address allocation method for multiple battery systems according to claim 2, characterized in that: The obtaining of the current address allocation state based on the corresponding feature code includes: Each battery system sends a corresponding feature code to the CAN bus, and uses the sent feature code as the first feature code; at the same time, it receives all feature codes on the current CAN bus, and uses each feature code on the current CAN bus as the second feature code.
4. The address allocation method for multiple battery systems according to claim 3, characterized in that: The obtaining of the current address allocation state based on the corresponding feature code also includes: Based on the second feature code, it is searched whether the first feature code exists on the CAN bus. If so, it is determined that the current battery system is in an address-allocated state; otherwise, it is determined that the current battery system is in an address-unallocated state.
5. The address allocation method for multiple battery systems according to claim 4, characterized in that: The address allocation includes: Based on the size of the feature code and the corresponding battery production date and battery production batch, an allocatable address table of each battery system is obtained, so that the battery system selects an address according to the corresponding allocatable address table.
6. The address allocation method for multiple battery systems according to claim 5, characterized in that: The address allocation further includes: It is determined whether the address selected according to the allocable address table is repeated with the addresses of other battery systems. If so, the address allocation is re-entered until the address allocation is completed; otherwise, it is determined that the address allocation is completed.
7. The address allocation method for multiple battery systems according to claim 6, characterized in that: After the address allocation is completed, the following steps are also included: The battery system with completed address allocation broadcasts the corresponding feature code and address to the CAN bus.
8. The address allocation method for multiple battery systems according to claim 1, characterized in that: After the battery system is powered on, it also includes: Determine whether the current battery system has allocated addresses for the first time. If so, obtain the current address allocation status based on the corresponding feature code; otherwise, end the process.
9. A battery system, characterized in that: The battery system uses the address allocation method for multiple battery systems as described in any one of claims 1 to 8 to complete the address allocation work.
10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by the battery system, the address allocation method for multiple battery systems as described in any one of claims 1 to 8 is implemented.