Energy storage system and method of addressing thereof

Abstract

The application discloses an energy storage system and an addressing method thereof, and belongs to the field of energy storage. The energy storage system comprises a plurality of slaves and a master. The plurality of slaves are cascaded through an addressing bus. The master is in communication connection with the plurality of slaves. The master is configured to: in response to the slaves satisfying an addressing condition, determine a first to-be-addressed slave based on a current state of an addressing bus interface of each slave, broadcast a first addressing instruction to the plurality of slaves to trigger addressing of the first to-be-addressed slave, and the first addressing instruction comprises a first device address of the first to-be-addressed slave; receive a first state packet fed back by the first to-be-addressed slave, and determine a next first to-be-addressed slave based on a current state of an addressing bus interface of each slave again. The energy storage system can quickly locate physical devices when combination changes or device maintenance, and improve the maintainability and networking efficiency of the energy storage system.

Description

Technical Field

[0001] This application relates to the field of energy storage technology, specifically to an energy storage system and its addressing method. Background Technology

[0002] In small-scale commercial energy storage scenarios, energy storage systems typically employ a stacked structure, comprising multiple levels such as battery clusters, battery stacks, and battery packs. Each battery cluster consists of multiple parallel energy storage units, each containing multiple battery modules. Each energy storage unit is equipped with a Battery Management Controller (BMC) for managing and communicating with the battery modules within its unit. In practical applications, users can flexibly configure the number of energy storage units and modules according to capacity requirements to adapt to different scales of energy storage scenarios.

[0003] During operation, each BMC needs a unique device address in the communication network to achieve reliable communication with the Cluster Management Unit (CMU) or other devices. The address allocation method for BMCs primarily employs a random competition mechanism, where each BMC randomly obtains an address through a competitive process. However, this method lacks a definite correspondence between the BMC's device address and its actual physical location. This makes it difficult to intuitively locate physical devices when the energy storage system's configuration changes flexibly, devices are added, or maintenance is required, affecting the maintainability and networking efficiency of the energy storage system. Summary of the Invention

[0004] This invention provides an energy storage system and its addressing method, aiming to improve the maintainability and networking efficiency of the energy storage system.

[0005] Firstly, an energy storage system is provided, comprising: Multiple slave devices, which are cascaded via an addressing bus; A host, which is communicatively connected to a plurality of slave devices; wherein the host is configured to perform the following steps: In response to the slave meeting the addressing conditions, a first slave to be addressed is determined based on the current state of the addressing bus interface of each slave, and a first addressing instruction is broadcast to multiple slaves to trigger the addressing of the first slave to be addressed. The first addressing instruction includes the first device address of the first slave to be addressed. Receive the first status message fed back by the first slave to be addressed, and re-determine the next first slave to be addressed based on the current status of the addressing bus interface of each slave.

[0006] In some embodiments, the host is configured to determine that the slave device meets addressing conditions, including any one of the following: Receives an address conflict message from any of the slave devices; Receive any of the aforementioned slave devices sending an address error message; It is determined that each of the slave devices is in non-operation mode.

[0007] In some embodiments, the slave device is configured to perform the following steps: The device periodically receives preset frame messages from other slave devices, the preset frame messages including a second device address corresponding to the slave device; If the second device address matches the device's own address, an address conflict message is sent to the host.

[0008] In some embodiments, the addressing bus interface of the slave device includes a first interface and a second interface, and the second interface of the slave device is connected to the first interface of the next adjacent slave device through the addressing bus; The initial state of each of the second interfaces is a first level state, the initial state of the first interface connected to the second interface is a second level state, and the initial state of the first interface not connected to the second interface is the first level state. The first level state is different from the second level state.

[0009] In some embodiments, the host is configured to determine a first slave to be addressed based on the current state of the addressing bus interface of each of the slaves, including: The slave device whose current state of the first interface is the first level state and which has not been addressed is identified as the first slave device to be addressed.

[0010] In some embodiments, the slave device is configured to perform the following steps: Receive the first addressing instruction broadcast by the host; When the current state of the first interface is the first level state and it is not addressed, the first device address is obtained in response to the first addressing instruction; After completing the addressing based on the first device address, the first status message is fed back, and the current status of the second interface is switched to the second level state, so that the current status of the first interface of the next slave device connected to the second interface is switched to the first level state.

[0011] In some embodiments, the host is further configured to perform the following steps: In response to the slave meeting the polling condition, the slave to be polled is determined based on the current state of the addressing bus interface of each slave, and a polling instruction is broadcast to each slave to trigger address polling of the slave to be polled, the polling instruction including the third device address of the slave to be polled; If no second status message is received from the slave device to be polled within a first preset time period, and the number of slave devices that have been successfully polled is not equal to the total number of slave devices, the polling is determined to have failed. If the number of consecutive polling failures does not reach the preset number and the slave device meets the polling conditions, the slave device to be polled is re-determined based on the current state of the address bus interface of each slave device, and the polling instruction is broadcast to multiple slave devices to trigger address polling of the slave device to be polled.

[0012] In some embodiments, the second status message includes an address matching message; the host is configured to determine the slave to be polled based on the current status of the addressing bus interface of each of the slaves, including: The slave device whose current state of the first interface is the first level state and which has not been polled is identified as the slave device to be polled; The host is also configured to perform the following steps: In response to receiving the address matching message from the slave device to be polled within the first preset time period, the next slave device to be polled is determined again based on the current state of the addressing bus interface of each slave device.

[0013] In some embodiments, the second status message further includes an address error message; the slave device is configured to perform the following steps: Receive the polling instruction broadcast by the host; When the current state of the first interface is the first level state and it is not polled, in response to the polling instruction, the third device address is compared with its own device address; If the third device address matches the device address, an address matching message is sent back; if the third device address does not match the device address, an address error message is sent back. Switch the current state of the second interface to the second level state, so that the current state of the first interface of the next slave device connected to the second interface is switched to the first level state.

[0014] In some embodiments, the host is further configured to perform the following steps: Before broadcasting the polling instruction and / or the first addressing instruction, the first reset instruction is broadcast to trigger the slave to restore the current state of the addressing bus interface to the initial state; If the duration of the first reset instruction reaches the second preset duration, the polling instruction and / or the first addressing instruction are broadcast.

[0015] In some embodiments, the host is further configured to perform the following steps: In response to not receiving the first status message from the first slave device to be addressed within a third preset time period, the current pressure difference between the first total pressure and the second total pressure is determined, and if the current pressure difference is less than a preset pressure difference threshold, the addressing is determined to be successful. Wherein, the first total voltage is the total voltage of the energy storage system, and the second total voltage is obtained by accumulating the voltage of the slave device to be addressed based on the first status message that has been fed back.

[0016] In some embodiments, the host is further configured to perform the following steps: If the current differential pressure is greater than or equal to the preset differential pressure threshold, addressing failure is determined. If the number of consecutive addressing failures does not reach a preset number, the first reset instruction is sent to trigger the slave device to restore the current state of the addressing bus interface to the initial state, and to re-determine the first slave device to be addressed based on the current state of the addressing bus interface of each slave device, and to broadcast the first addressing instruction to multiple slave devices to trigger the addressing of the first slave device to be addressed.

[0017] In some embodiments, the host is further configured to perform the following steps: After successful addressing, or if the number of consecutive addressing failures has reached the preset number, a second reset command is broadcast to trigger the slave device to restore the current state of the addressing bus interface to its initial state and restart it.

[0018] In some embodiments, the host is further configured to perform the following steps: Receive a second addressing instruction, the second addressing instruction including the fourth device address of the second slave device to be addressed; The second addressing instruction is transmitted to the second slave device to be addressed, so that the second slave device to be addressed responds to the second addressing instruction, saves the fourth device address to the configuration parameters, and updates the CAN filter based on the fourth device address.

[0019] In some embodiments, the master unit is a battery cluster management unit (CMU), and the slave unit is a battery management controller (BMC). Alternatively, the master unit is a storage converter (PCS), and the slave unit is a battery cluster management unit (CMU).

[0020] Secondly, an addressing method for an energy storage system is provided, applied to the host of the energy storage system, comprising: In response to the fact that each slave device in the energy storage system cascaded via the addressing bus meets the addressing conditions, a first slave device to be addressed is determined based on the current state of the addressing bus interface of each slave device, and a first addressing instruction is broadcast to multiple slave devices to trigger the addressing of the first slave device to be addressed. The first addressing instruction includes the first device address of the first slave device to be addressed. Receive the first status message fed back by the first slave to be addressed, and re-determine the next first slave to be addressed based on the current status of the addressing bus interface of each slave.

[0021] The energy storage system of this application embodiment sets up multiple slave devices cascaded via an addressing bus. When a slave device meets the addressing conditions, the master determines the first slave device to be addressed based on the current state of the addressing bus interface of the slave device, and broadcasts a first addressing instruction to multiple slave devices to trigger the addressing of the first slave device to be addressed. After broadcasting the first addressing instruction, the master receives a first status message fed back by the first slave device to be addressed, so that the device address of the slave device can be associated with the physical order on the addressing bus, thereby realizing the correspondence between the device address and the actual physical location. This facilitates the rapid location of physical devices during combination changes or equipment maintenance, and improves the maintainability and networking efficiency of the energy storage system. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0023] Figure 1 This is a schematic diagram of the energy storage system according to an embodiment of this application; Figure 2 This is a schematic diagram of an example structure of an energy storage system according to an embodiment of this application; Figure 3 This is a schematic diagram illustrating the cascading of multiple slave devices according to an embodiment of this application; Figure 4 This is a schematic diagram of the overall process of an addressing method for an energy storage system according to an embodiment of this application; Figure 5 A flowchart illustrating the automatic addressing steps performed by the host in an embodiment of this application; Figure 6 This is a flowchart illustrating the automatic addressing steps performed by the slave device in an embodiment of this application. Figure 7 This is a schematic diagram illustrating the interaction flow between the host and slave devices during the automatic addressing process in an embodiment of this application. Figure 8A flowchart illustrating the address anomaly detection steps performed by the host in an embodiment of this application; Figure 9 This is a flowchart illustrating the address anomaly detection steps performed by the slave device in an embodiment of this application. Figure 10 This is a schematic diagram of the address conflict detection process performed by the slave device in an embodiment of this application.

[0024] Explanation of reference numerals in the attached figures: 10-Battery cluster; 11-Energy storage unit; 111-BMC; 1111-First interface; 1112-Second interface; 112-Switch box; 113-Base; 114-Battery module; 12-CMU; 20-PCS; 30-Addressing bus; 40-Master; 50-Slave; 60-Communication line. Detailed Implementation

[0025] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0026] In the description of this application, it should be understood that the terms "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," and "outer," etc., indicating orientation or positional relationships based on the orientation or positional relationships shown in the accompanying drawings, are used only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of this application. Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, features defined with "first" and "second" may explicitly or implicitly include one or more of the stated features. In the description of this application, "a plurality of" means two or more, unless otherwise explicitly specified.

[0027] "A and / or B" includes the following three combinations: A only, B only, and a combination of A and B.

[0028] The use of "applies to" or "configured to" in this application implies open and inclusive language, which does not exclude the applicability to or configuration to devices performing additional tasks or steps. Additionally, the use of "based on" implies openness and inclusivity, because processes, steps, calculations, or other actions "based on" one or more of the stated conditions or values ​​may in practice be based on additional conditions or values ​​beyond those stated.

[0029] In this application, the term "exemplary" is used to mean "used as an example, illustration, or description." Any embodiment described as "exemplary" in this application is not necessarily to be construed as being more preferred or advantageous than other embodiments. The following description is provided to enable any person skilled in the art to make and use this application. Details are set forth in the following description for purposes of explanation. It should be understood that those skilled in the art will recognize that this application can be made without using these specific details. In other instances, well-known structures and processes are not described in detail to avoid obscuring the description of this application with unnecessary detail. Therefore, this application is not intended to be limited to the embodiments shown, but is consistent with the broadest scope of the principles and features disclosed in this application.

[0030] Please see Figure 1 , Figure 1 This is a schematic diagram of the energy storage system according to an embodiment of this application. The energy storage system includes a master unit 40 and multiple slave units 50, and the master unit 40 and the multiple slave units 50 are communicatively connected. Exemplarily, the master unit 40 and the multiple slave units 50 can be communicatively connected via a communication line 60. The communication connection can be CAN communication or other communication connection methods, which are not specifically limited in this embodiment of the application.

[0031] Energy storage systems can be applied to power storage scenarios of varying scales, including large-scale energy storage power plants and small-scale commercial energy storage scenarios. Large-scale energy storage power plants typically employ containerized or prefabricated structures, with relatively fixed equipment installation locations. The connections between energy storage units are determined at the factory, and on-site commissioning and maintenance are handled by professional engineering teams. Small-scale commercial energy storage scenarios target users such as small factories, commercial buildings, street-front shops, and communication base stations. The equipment is mostly installed in a stacked manner, allowing users to flexibly configure the number and capacity of energy storage units according to their actual power consumption needs.

[0032] Please see Figure 2 , Figure 2This is a schematic diagram illustrating an example structure of an energy storage system according to an embodiment of this application. In some scenarios, such as small-scale commercial energy storage, the energy storage system typically adopts a stacked structure. In this configuration, the energy storage system includes at least one battery cluster 10 and a PCS (Power Conversion System) 20, which is electrically connected to a CMU 12 in each battery cluster 10. The battery cluster 10 includes multiple parallel-connected energy storage units 11 and CMUs 12, each energy storage unit 11 including a BMC 111, and the CMU 12 is communicatively connected to multiple BMCs 111.

[0033] In some examples, the energy storage unit 11 is a battery stack. Each energy storage unit 11 also includes a switch box 112, a base 113, and multiple battery modules 114 stacked between the switch box 112 and the base 113. Each battery module 114 includes multiple battery packs, and each battery pack is equipped with a BMU (Battery Management Unit). The BMU includes an AFE (Analog Front End).

[0034] For example, the PCS20 is connected to the battery cluster 10 via an inter-cluster communication line 60 (CAN), the CMU12 is connected to multiple BMCs 111 via an inter-stall communication line 60 (CAN), and the BMCs 111 within each energy storage unit 11 are daisy-chained with multiple AFEs via an intra-stall communication line 60. The number of battery clusters 10 connected to the PCS20 can be set to any value from 1 to 4. The number of energy storage units 11 within each battery cluster 10 can be set to any value from 1 to 4. The number of battery modules 114 within each energy storage unit 11 can be set to any value from 3 to 5. In this way, a single energy storage unit 11 has at least 3 battery modules 114, thereby allowing the fuses within the energy storage unit 11 to better perform their protective function.

[0035] In this example of a multi-level management architecture, the master unit 40 is the battery cluster 10 management unit CMU12, and the slave unit 50 is the battery management controller BMC111; alternatively, the master unit 40 is the energy storage converter PCS20, and the slave unit 50 is the battery cluster 10 management unit CMU12. In other example architectures, the master unit 40 and the slave unit 50 may also be devices with corresponding control sequences. This application embodiment does not limit the specific types of the master unit 40 and the slave unit 50.

[0036] The battery clusters 10, battery stacks, and battery packs in the energy storage system need to be flexibly combined and configured according to capacity requirements, and the equipment is usually replaced rather than repaired. Therefore, the design of the energy storage system needs to support flexible automatic networking schemes. For example, each BMC111 needs to have a unique device address in the communication network to achieve reliable communication with CMU12 or other devices.

[0037] In related technologies, the address allocation method for BMC111 mainly adopts a random contention mechanism, where each BMC111 randomly obtains an address through contention. However, because the correspondence between the device ID and the actual physical location is unclear, it becomes difficult to intuitively locate physical devices when the energy storage system combination changes flexibly, devices are added, or maintenance is required. This affects the maintainability and networking efficiency of the energy storage system. In addition, because the BMC111 address is random, adding devices requires manually issuing ID contention configuration, which is cumbersome and affects networking efficiency.

[0038] In view of this, the present application provides an energy storage system that adds a ring-shaped addressing bus 30 between multiple slave devices 50, broadcasts a first addressing instruction to the multiple slave devices 50 to trigger the addressing of a first slave device to be addressed, and receives a first status message fed back by the first slave device to be addressed. This assists the software addressing strategy to achieve automatic and accurate addressing of the slave devices 50, realizes the correspondence between the device address and the actual physical location, facilitates the rapid location of physical devices when the energy storage system combination changes or the device is maintained, improves the maintainability and networking efficiency of the energy storage system, and thus solves at least some of the above-mentioned technical problems.

[0039] Please continue reading. Figure 1 In the energy storage system of this application embodiment, multiple slave devices 50 are cascaded via an addressing bus 30. That is, any two adjacent slave devices 50 are connected via the addressing bus 30. Thus, since the physical order of the slave devices 50 cannot be distinguished by the communication line 60, and automatic addressing cannot be achieved, the addressing bus 30 can be introduced to identify and distinguish physical layer information using hardware pin signals.

[0040] Please see Figure 3 , Figure 3This is a schematic diagram illustrating the cascading of multiple slave devices according to an embodiment of this application. In some examples, slave device 50 has an addressable bus interface, which includes a first interface 1111 and a second interface 1112. The second interface 1112 of slave device 50 is connected to the first interface 1111 of the next adjacent slave device 50 via an addressable bus 30. Taking four slave devices 50 as an example, the second interface 1112 of the first slave device 50 (identified as slave device 50#1) is connected to the first interface 1111 of the second slave device 50 (identified as slave device 50#2), the second interface 1112 of the second slave device 50 (identified as slave device 50#2) is connected to the first interface 1111 of the third slave device 50 (identified as slave device 50#3), and the second interface 1112 of the third slave device 50 (identified as slave device 50#3) is connected to the first interface 1111 of the fourth slave device 50 (identified as slave device 50#4), thus realizing a ring connection of four slave devices 50.

[0041] The initial state of each second interface 1112 is a first level state, the initial state of the first interface 1111 connected to the second interface 1112 is a second level state, and the initial state of the first interface 1111 not connected to the second interface 1112 is a first level state. The first level state is different from the second level state.

[0042] For example, the first interface 1111 is a DI (Digital Input) pin, and the second interface 1112 is a DO (Digital Output) pin. The first level state is high level, and the second level state is low level.

[0043] Taking four slave devices 50 as an example, the initialization of slave devices 50 will set all second interfaces 1112 to high level. The first interface 1111 of the first slave device 50 (identified as slave device 50#1) has no physical connection, and the internal hardware circuit will pull it high, presenting a high level. The first interfaces 1111 of the subsequent three slave devices 50 (identified as slave device 50#2, slave device 50#3, and slave device 50#4) are connected to the second interfaces 1112 respectively, and the internal hardware circuit will flip them to low level. So the initial state of the first interface 1111 of the four slave devices 50 is high, low, low, low, and the initial state of the second interface 1112 of the four slave devices 50 is high, high, high, high.

[0044] The software improvements of the energy storage system according to the embodiments of this application will be described below.

[0045] Please see Figure 4 , Figure 4 This is a schematic diagram illustrating the overall flow of an addressing method for an energy storage system according to an embodiment of this application. The addressing method is applied to a host 40, which is specifically configured to perform the following steps: Step S401: In response to the slave 50 meeting the addressing conditions, a first slave to be addressed is determined based on the current state of the addressing bus interface of each slave 50, and a first addressing instruction is broadcast to multiple slaves 50 to trigger the addressing of the first slave to be addressed. The first addressing instruction includes the first device address of the first slave to be addressed.

[0046] Specifically, after determining the first slave device to be addressed, the host 40 generates a first addressing instruction containing the first device address of the first slave device to be addressed, and broadcasts the first addressing instruction through the communication line 60 so that all slave devices 50 can receive the first addressing instruction. The first device address can be a pre-set starting address, such as address 1, or an address dynamically calculated according to the addressing order. The broadcast indicates that the first addressing instruction sent by the host 40 does not specify a specific receiving node, and all slave devices 50 connected to the communication line 60 can receive the first addressing instruction.

[0047] Please see Figure 5 , Figure 5 This is a flowchart illustrating the automatic addressing steps performed by the host in an embodiment of this application. In some examples, the host 40 is configured to determine that the slave 50 meets the addressing conditions, including any one of the following: Receives an address conflict message from any slave device 50; Receives an address error message from any slave device 50; Ensure that each slave device 50 is in non-operating mode.

[0048] Specifically, automatic addressing can be triggered in the event of an address conflict or address anomaly in slave device 50. However, slave device 50 does not perform automatic addressing in operating mode. This avoids the risks associated with performing addressing while charging and discharging are permitted. The transmission of address conflict and address anomaly messages will be detailed in subsequent embodiments and will not be elaborated upon here.

[0049] In some embodiments, step S401 may specifically determine the first slave device to be addressed based on the current state of the addressing bus interface of each slave device 50 in the following manner: The slave device 50 whose current state of the first interface 1111 is the first level state and which has not been addressed is identified as the first slave device to be addressed.

[0050] For example, slave device 50 can identify whether it has been addressed by using an addressing flag. For instance, if the addressing flag is cleared to zero, it indicates that it has not been addressed; if the addressing flag is set (i.e., the value is 1), it indicates that it has been addressed. Each slave device 50 can sequentially become the first slave device to be addressed. Taking a first level state as high and a second level state as low, with four slave devices 50 as an example, master device 40 can distinguish which is the first slave device 50 by the current state of the first interface 1111, and then subsequently send a first addressing instruction including the device address of the first slave device 50. For example, master device 40 can send a status query instruction to each slave device 50 through the inter-stack communication line 60, and each slave device 50 encodes the current state of its own first interface 1111 and reports it to master device 40. Based on this, master device 40 identifies the slave device 50 among all slave devices 50 whose first interface 1111 is high.

[0051] After receiving the first addressing instruction broadcast by the master 40, each slave device 50 can respond by checking the current state of its first interface 1111. Processing is only performed upon detecting a high level. After the first slave device 50 completes its processing, it internally sets the addressing flag to indicate that it has completed addressing, and simultaneously pulls the current state of its second interface 1112 low. At this time, the current state of the first interface 1111 of the second slave device 50 will switch to a high level. Thus, the current state of the first interfaces 1111 of the four slave devices 50 will be high, high, low, low. After the first slave device 50 completes its processing, it will send back a first status message. Then, the master 40 will perform addressing for the second slave device 50. At this time, the first interfaces 1111 of both slave devices 50 are high, but since the first slave device 50 has already indicated that it has been addressed via the addressing flag, it will not respond. The second slave device 50 will respond to the first addressing instruction and perform addressing, and this process is repeated for all slave devices 50.

[0052] Please see Figure 6 , Figure 6 This is a flowchart illustrating the automatic addressing steps performed by the slave device in an embodiment of this application. In some examples, the slave device 50 is configured to perform the following steps: Receive the first addressing instruction broadcast by host 40.

[0053] When the current state of the first interface 1111 is the first level state and it is not addressed, the first device address is obtained in response to the first addressing instruction.

[0054] After completing the addressing based on the first device address, a first status message is fed back, and the current status of the second interface 1112 is switched to the second level state, so that the current status of the first interface 1111 of the next slave device 50 connected to the second interface 1112 is switched to the first level state.

[0055] Specifically, after each slave device 50 receives the first addressing instruction broadcast, it decides whether to respond based on the current state of its own first interface 1111 and the addressing flag. Only the first slave device to be addressed, whose first interface 1111 is high and whose own addressing flag is set, will respond to the first addressing instruction.

[0056] For example, the first slave device to be addressed saves the first device address to the configuration parameters, updates the CAN filter, pulls the current state of the second interface 1112 low, sets the addressing flag, and thus completes the addressing. After the addressing is completed, the first slave device to be addressed sends a first status message to the host 40, which indicates that the first slave device to be addressed has completed the addressing.

[0057] Step S402: Receive the first status message fed back by the first slave to be addressed, and re-determine the next first slave to be addressed based on the current status of the addressing bus interface of each slave 50.

[0058] Specifically, in response to receiving a first status message from the first slave device to be addressed in response to the first addressing instruction within a third preset time period, the host 40 re-determines the next first slave device to be addressed based on the current status of the first interface 1111 of each slave device 50.

[0059] For example, the third preset duration can be set to 2 seconds, but the specific duration can be set according to actual needs. This application embodiment does not make specific limitations on this.

[0060] Specifically, when broadcasting the first addressing instruction, the host 40 records the time of the first addressing instruction. If the host 40 receives a first status message from the first slave device to be addressed within a first preset time period, it confirms that the first slave device to be addressed has been successfully addressed. Subsequently, the host 40 re-executes the above step S401 to determine the next first slave device to be addressed based on the current state of the first interface 1111 of each slave device 50. Since the first slave device 50 has switched its second interface 1112 from the first level state to the second level state after completing the addressing, this causes the first interface 1111 of the second slave device 50 connected to the second interface 1112 of the first slave device 50 to flip from the original second level state to the first level state. At the same time, the addressing flag of the first slave device 50 itself is set to addressed, so even if its first interface 1111 is still in the first level state, it will not be selected as the slave device to be addressed again. At this point, the host 40 queries the current status and addressing flag of the first interface 1111 of each slave 50 again. It will find that the first interface 1111 of the second slave 50 has changed to the first level state and has not been addressed. Therefore, the second slave 50 is identified as the new first slave to be addressed. In this way, the host 40 assigns the next device address (e.g., address 2) to the new first slave to be addressed, until all slaves 50 are addressed.

[0061] For different numbers of slave devices 50, the host 40 in this embodiment can automatically adapt. For example, when the energy storage system contains two slave devices 50, the host 40 sequentially completes the addressing of the first and second slave devices 50. After the second slave device 50 is addressed, when the host 40 re-determines the first slave device to be addressed, it will find that all slave devices 50 have been addressed, and there is no slave device 50 with its first interface 1111 high and not yet addressed, thus automatically ending the addressing process. In this way, the host 40 does not need to obtain the total number of slave devices 50 in advance, nor does it require manual intervention, which can greatly improve the flexibility of network configuration.

[0062] Through the above technical solution, the host 40 needs to re-acquire the current state of the first interface 1111 of each slave 50 each time it re-determines the first slave to be addressed. Since the state changes of the second interface 1112 of each slave 50 are propagated hierarchically, the voltage level distribution queried by the host 40 each time reflects the current addressing progress. For example, after the first slave 50 is addressed, the first interface 1111 of the second slave 50 becomes high, while the first interface 1111 of the third and subsequent slaves remains low; after the second slave 50 is addressed, the first interface 1111 of the third slave 50 becomes high, and so on. By utilizing the changes in voltage levels, the host 40 can automatically identify and sequentially address the physical order of the slaves 50, reducing the risk of address allocation conflicts and achieving a one-to-one correspondence between device addresses and physical locations.

[0063] In some embodiments, CMU12 is also configured to perform the following steps: Before broadcasting the first addressing instruction, a first reset instruction is broadcast to trigger slave 50 to restore the current state of the addressing bus interface to the initial state.

[0064] If the duration of the first reset instruction reaches the second preset duration, the first addressing instruction is broadcast.

[0065] Specifically, before broadcasting the first addressing instruction, the host 40 can perform a reset operation to ensure that the addressing process starts from a defined initial state. The first reset instruction is broadcast to all slaves 50 via communication line 60. The first reset instruction is used to trigger each slave 50 to restore the current state of its second interface 1112 to the initial state. The first reset instruction can also trigger the slaves 50 to reset their internal addressing flags. After the reset operation, the addressing flags of all slaves 50 are cleared, indicating that no addressing has been performed. When broadcasting the first reset instruction, the host 40 can clear the number of successfully addressed BMUs to zero, so as to facilitate the counting of the number of addressed BMUs during subsequent addressing.

[0066] When broadcasting the first reset command, the host 40 records the time of the first reset command's transmission and then sends the first addressing command after a second preset duration. The purpose of setting the second preset duration is to provide the slave 50 with sufficient time to complete the reset operation. The reset response time of different slave 50s may vary, and changes in the level state on the addressing bus 30 require a certain propagation and stabilization time. Therefore, the second preset duration can be set according to actual needs; for example, the second preset duration can be set to 1 second. This embodiment of the application does not specifically limit this.

[0067] The above scheme, through the timing design of resetting first and then addressing, can avoid the residual state of the previous addressing from interfering with the current addressing, thereby improving the reliability and repeatability of the addressing process.

[0068] In some embodiments, host 40 is further configured to perform the following steps: In response to not receiving a first status message from the first slave device to be addressed within a third preset time period, the current pressure difference between the first total pressure and the second total pressure is determined, and if the current pressure difference is less than a preset pressure difference threshold, the addressing is determined to be successful. The first total voltage is the total voltage of the energy storage system, and the second total voltage is obtained by accumulating the voltage of the slave devices to be addressed based on the feedback of the first status message.

[0069] Specifically, the first total voltage is the total voltage of the energy storage system, and the second total voltage can be accumulated based on the total voltage corresponding to different IDs uploaded by the slave devices to be addressed, which have already sent back the first status message. Using the voltage difference to determine whether addressing is successful can be applied to small-scale commercial energy storage scenarios. Automatic addressing involves executing a summary judgment logic on the master device 40. The number of slave devices 50 is unknown. To accommodate different combinations of slave devices 50, the master device 40 needs to address them one by one. If no first status message responding to the first addressing command is received from a slave device 50 within a third preset time period, the master device 40 cannot determine whether the addressing was successful because there are two possibilities: one is that all addresses were successful, so no response was given after the timeout; the other is that the wiring harness is faulty and communication is impossible. To determine the reason for the timeout failure to respond, the current voltage difference between the first and second total voltages is used. If all addressing was successful, the IDs of all slave devices 50 are separate and consecutive. In this case, the master device 40 can distinguish and accumulate the voltages of all slave devices 50. If the current voltage difference is less than a preset voltage difference threshold, it indicates that the timeout failure to respond was because all slave devices 50 were successfully addressed. For example, the preset voltage difference threshold can be set to 10V, but the specific value can be determined according to actual needs.

[0070] For example, the host 40 is connected to four slave devices 50. Each slave device 50 is addressed one by one. If the fourth slave device 50 replies with a first status message within a first preset time, the host 40 continues to send an address to the fifth slave device 50. However, the fifth slave device is not actually connected, so there may be a timeout and no reply. At this time, the host 40 determines the current voltage difference based on the total voltage of the battery cluster 10 and the sum of the voltages of the four slave devices 50. If the current voltage difference is less than 10V, it is determined that all addresses have been successfully assigned.

[0071] In some embodiments, CMU12 is also configured to perform the following steps: If the current differential pressure is greater than or equal to the preset differential pressure threshold, the addressing failure is determined. If the number of consecutive addressing failures does not reach the preset number, a first reset instruction is broadcast to trigger the slave 50 to restore the current state of the addressing bus interface to the initial state, and to re-determine the first slave to be addressed based on the current state of the addressing bus interface of each slave 50, and broadcast the first addressing instruction to multiple slaves 50 to trigger the addressing of the first slave to be addressed.

[0072] Specifically, after determining that addressing has failed, host 40 determines the number of consecutive addressing failures. Host 40 can internally set an addressing failure counter, which is reset to zero before each addressing process begins and incremented by one after each confirmed addressing failure. If the current number of consecutive failures has not reached a preset number (e.g., it can be set to 3), host 40 attempts to re-address.

[0073] During readdressing, the host 40 first sends a first reset command, triggering all slave devices 50 to restore the second interface 1112 to its initial state (i.e., the first level state) and reset the addressing flag. After waiting for a second preset time, the host 40 sends the first addressing command again, repeating the addressing process described in the previous embodiment, and performs differential pressure judgment again after a timeout. In this way, the cycle of reset, addressing, and differential pressure judgment continues until the addressing is successful or the number of consecutive failures reaches a preset number.

[0074] The above solution can address occasional anomalies such as communication interruptions, voltage sampling fluctuations, or slave device response delays, and automatically restore addressing without manual intervention, thereby improving the robustness of the system.

[0075] In some embodiments, host 40 is further configured to perform the following steps: After confirming successful addressing, or if the number of consecutive addressing failures has reached a preset number, a second reset command is broadcast to trigger the slave device 50 to restore the current state of the addressing bus interface to its initial state and restart it.

[0076] For example, if the master 40 determines that the addressing was successful, or if the number of consecutive addressing failures has reached a preset number (e.g., 3 times), a second reset instruction is sent. The second reset instruction triggers all slave devices 50 to restore their second interface 1112 to its initial state (i.e., the first level state) and triggers the slave devices 50 to perform a restart operation. The restart operation may include, for example, a software reset and a hardware reset, causing the slave devices 50 to reinitialize their internal registers, communication modules, and allocated address configurations. By restarting, it is possible to attempt to clear any possible abnormal states, restore the addresses to their default values, or make newly allocated addresses officially effective, allowing the slave devices 50 to enter normal operating mode.

[0077] Both the second reset instruction and the first reset instruction can trigger the restoration of the state of the second interface 1112 and reset the address flag. The difference is that the second reset instruction can also trigger the slave device 50 to restart.

[0078] Please see Figure 7 , Figure 7 This is a schematic diagram illustrating the interaction flow between the host and slave devices during the automatic addressing process according to an embodiment of this application. For example, taking two slave devices 50, the host 40 broadcasts a first reset command in response to the slave device 50 meeting the addressing conditions. The slave device 50, in response to the first reset command, resets the current state and addressing flag of the second interface 1112. After a second preset time period following the issuance of the first reset command, the host 40 broadcasts a first addressing command. The first slave device 50 (slave device 50#1), in response to the first addressing command, completes addressing, sets the addressing flag, switches the current state of the second interface 1112, and sends a first status message back to the host 40. Upon receiving the first status message within a third preset time period, the host 40 broadcasts a first addressing command containing the device address of the second slave device 50 (slave device 50#2). The second slave device 50 (slave device 50#2) executes the addressing steps and completes the addressing. If the host 40 does not receive the first status message within a third preset time period, it modifies the configuration parameters of the number of slave devices 50 and checks the current voltage difference between the first total voltage and the second total voltage. If the current voltage difference is less than a preset voltage difference threshold (e.g., 10V), it determines that the addressing is successful and broadcasts a second reset command to reset the status of the second interface 1112, reset the addressing flag, and restart the slave device 50. If the current voltage difference is greater than or equal to the preset voltage difference threshold (e.g., 10V), it determines that the addressing has failed, broadcasts a first reset command, and triggers re-addressing after a certain time interval. If the number of consecutive addressing failures reaches a preset number, a second reset command is broadcast.

[0079] Based on the hardware architecture improvements in this application embodiment, the above scheme forms a closed-loop control process through steps such as reset, sequential broadcast, conditional response, differential pressure verification, failure retry, and restart. This enables automatic allocation of slave 50 addresses, abnormal self-recovery, and correspondence with physical locations in the energy storage system, thereby improving the maintainability and operational stability of the system.

[0080] In other embodiments, in a large storage scenario, host 40 is also configured to perform the following steps: In response to the fact that the number of slave devices 50 that have been addressed is consistent with the preset number based on the preset configuration parameters, the addressing is confirmed to be successful; The number of slave devices that have been addressed is inconsistent with the preset number, indicating that the addressing has failed.

[0081] Specifically, in large-scale energy storage power station scenarios, the number of devices, connection topology, and communication addresses of the energy storage system are usually determined during the system design phase. The system integrator pre-configures the number of each energy storage unit 11 and the addresses of each communication node based on the power station's capacity planning and electrical design drawings. After the system is powered on, the host 40 (e.g., the battery cluster 10 management unit or the power station energy management system) checks whether the number of currently connected slave devices 50 matches the preset number according to the preset configuration parameters. If the detected number of slave devices 50 matches the preset number, it is considered that the addresses of each slave device 50 have been allocated, and the communication network has been successfully established. If the detected number of slave devices 50 does not match the preset number, it is determined that the addressing is incomplete, and the host 40 reports a configuration anomaly alarm, prompting engineers to check the device connections or re-verify the configuration parameters.

[0082] Please see Figure 8 , Figure 8 This is a flowchart illustrating the address anomaly detection steps performed by the host in an embodiment of this application. In some embodiments, the host 40 is further configured to perform the following steps: Step 1: In response to the slave 50 meeting the polling conditions, determine the slave to be polled based on the current state of the address bus interface of each slave 50, and broadcast a polling instruction to each slave 50 to trigger address polling of the slave to be polled. The polling instruction includes the third device address of the slave to be polled.

[0083] Specifically, after detecting the restart flag message uploaded by the slave device 50, the host 40 can determine that the slave device 50 has completed the restart. The slave device 50 can upload a restart flag message if it detects that it is in the poweron exit function. The slave device 50 can internally set an address error flag and a polling flag. The address error flag is used to indicate whether the address of the slave device 50 is abnormal, and the polling flag is used to indicate whether the slave device 50 has been polled. The slave device 50 meets the polling conditions as follows: the address error flag of the slave device 50 is reset, it is not in addressing, and the number of polling failures is less than a preset number. The preset number can be, for example, 3 times. The polling command is used to trigger the slave device to be polled to compare the address of the third device with its own device address.

[0084] In some examples, the second status message includes an address matching message. The master 40 is configured to determine the slave to be polled based on the current status of the address bus interface of each slave 50, including: The slave device 50 whose current state of the first interface 1111 is the first level state and which has not been polled is identified as the slave device to be polled.

[0085] Host 40 is also configured to perform the following steps: In response to receiving an address matching message from the slave device to be polled within a first preset time period, the next slave device to be polled is determined based on the current state of the address bus interface of each slave device 50.

[0086] Specifically, the second status message includes an address matching message and an address error message. The address matching message indicates that the address of the third device received by the slave device to be polled matches its own device address. The address error message indicates that the address of the third device received by the slave device to be polled does not match its own device address.

[0087] In some examples, host 40 is also configured to perform the following steps before broadcasting the polling command: Before sending the polling command, a first reset command is broadcast to trigger slave 50 to restore the current state of the address bus interface to the initial state; If the duration of the first reset instruction reaches the second preset duration, a polling instruction is broadcast.

[0088] Specifically, the first reset instruction is used to trigger each slave device 50 to restore the current state of its second interface 1112 to its initial state. The first reset instruction can also be used to trigger the address error flag to reset. For details, please refer to the description of the first reset instruction in the foregoing embodiments, which will not be repeated here.

[0089] Step 2: If no second status message is received from the slave device to be polled within the first preset time period, and the number of 50 slave devices that have been successfully polled is not equal to the total number of slave devices, then polling is determined to have failed.

[0090] For example, the first preset duration can be set to 2 seconds, or it can be set to other values, depending on the actual needs.

[0091] Step 3: If the number of consecutive polling failures does not reach the preset number and the slave 50 meets the polling conditions, the slave to be polled is re-determined based on the current state of the address bus interface of each slave 50, and a polling instruction is broadcast to multiple slaves 50 to trigger address polling of the slave to be polled.

[0092] Furthermore, if the number of consecutive polling failures reaches a preset number, the address polling mode is reset and the process returns to the step of checking whether the slave device 50 meets the polling conditions.

[0093] For example, if the host 40 does not receive an address matching message and an address matching message from the slave device responding to the polling instruction within a first preset time period, and the number of successful polling is not equal to the total number of slave devices 50, the host 40 determines that the polling has failed, increments the polling failure count by 1, and records the address polling failure location.

[0094] Please see Figure 9 , Figure 9 This is a flowchart illustrating the address anomaly detection steps performed by the slave device in an embodiment of this application. In some examples, the slave device 50 is configured to perform the following steps: Receive polling commands broadcast by host 40; When the current state of the first interface 1111 is the first level state and it is not polled, in response to the polling command, the third device address is compared with its own device address; If the address of the third device matches the address of the device itself, a matching address message is sent back; if the address of the third device does not match the address of the device itself, an address error message is sent back. Switch the current state of the second interface 1112 to the second level state so that the current state of the first interface 1111 of the next slave device 50 connected to the second interface 1112 is switched to the first level state.

[0095] Specifically, the host 40 first obtains the current state of the first interface 1111 of each slave 50. Before polling begins, the host 40 has restored the second interface 1112 of all slave 50s to the first level state via a first reset command, so that the first interface 1111 of the first slave 50 is in the first level state, and the first interfaces 1111 of the remaining slave 50s are in the second level state. The host 40 queries the current state of the first interface 1111 reported by each slave 50 through the communication line 60 and checks the polling flag bit of each slave 50. The host 40 determines the slave 50 whose current state of the first interface 1111 is in the first level state and has not been polled as the slave to be polled. The third device address is the address that the slave to be polled should have, such as address 1, address 2, etc., allocated according to physical order. The host 40 broadcasts the polling command through the communication line 60. The broadcast method ensures that all slave 50s can receive the command, but only the slave to be polled that meets the response conditions will process it. The polling command is used to trigger the slave device to be polled to compare the third device address in the command with its own stored device address. If the two match, the slave device to be polled sends an address match message to the master device 40; if they do not match, it sends an address error message and sets the address error flag.

[0096] After broadcasting the polling command, the host 40 records the time when the polling command was issued. If the host 40 receives an address matching message from the slave device to be polled within a first preset time period, it confirms that the address of the slave device 50 is normal, and the polling is successful. Subsequently, the host 40 re-executes the step of determining the slave device to be polled based on the current state of the first interface 1111 of each slave device 50. Since the currently polled slave device 50 switches its second interface 1112 from the first level state to the second level state after completing the response, the first interface 1111 of the next adjacent slave device 50 flips from the second level state to the first level state, and the polling flag of the current slave device 50 is set to polled. Therefore, when the host 40 queries again, the next slave device 50 will become the new slave device to be polled.

[0097] The above scheme ensures that the polling order is consistent with the addressing order, both based on hardware transmission links, eliminating the need for additional configuration or manual specification of the order and reducing system complexity. Polling can promptly detect anomalies such as address errors and loss, notifying the host 40 via address anomaly messages. Furthermore, resetting before polling ensures consistency of the initial polling state, improving the reliability of the polling results. In addition, the host 40 can automatically adapt to different numbers of slave devices 50 without prior knowledge of the specific number, further enhancing the networking flexibility of the energy storage system.

[0098] In some embodiments, host 40 is further configured to perform the following steps: Receive the second addressing instruction, which includes the fourth device address of the second slave device to be addressed; The second addressing instruction is transmitted to the second slave device to be addressed, so that the second slave device to be addressed responds to the second addressing instruction, saves the fourth device address to the configuration parameters, and updates the CAN filter based on the fourth device address.

[0099] Specifically, in addition to automatic addressing, the energy storage system of this application embodiment also supports manual addressing, which is used to directly allocate addresses when there is a hardware failure in the addressing bus 30 or when a specific address needs to be specified. The host 40 receives a second addressing instruction from an external device. The external device can be a host computer, a handheld terminal, or a local keypad input device. The second addressing instruction includes the identification information of the second slave device to be addressed and a fourth device address specified for the second slave device. The identification information of the second slave device to be addressed can be the serial number, factory serial number, or temporary communication address on the communication line 60 of the slave device 50. After receiving the second addressing instruction, the host 40 directly transmits it to the second slave device to be addressed. For example, the host 40 generates a CAN message based on the identification information of the second slave device to be addressed, with the destination address pointing to the second slave device to be addressed. The data field of the message contains the fourth device address and a command code, indicating that the operation is manual addressing. The host 40 sends the CAN message to the communication line 60.

[0100] After receiving the second addressing instruction, the second slave device to be addressed extracts the address of the fourth device and saves it to its own configuration parameters. These configuration parameters are typically stored in non-volatile memory (such as EEPROM or Flash) to ensure that the address is not lost after power failure. After saving, the second slave device to be addressed updates the CAN filter based on the fourth device address. The CAN filter is a configuration register of the slave device's internal CAN controller, used to filter received CAN messages. After updating the CAN filter, the slave device 50 only receives messages related to its new address, thereby improving communication efficiency and security.

[0101] With the above solution, when automatic addressing fails, manual addressing can be used to assign the slave 50 address one by one, thereby ensuring the basic communication function of the system.

[0102] Please see Figure 10 , Figure 10 This is a schematic diagram illustrating the address conflict detection process performed by the slave device in an embodiment of this application. In some embodiments, the slave device 50 is configured to perform the following steps: Periodically receive preset frame messages from other slave devices 50, the preset frame messages including the second device address of the corresponding slave device 50; If the address of the second device matches the address of its own device, an address conflict message is sent to host 40.

[0103] Specifically, messages sent by slave device 50 are typically only received by master device 40. By configuring the CAN filter of slave device 50, slave device 50 can receive a fixed preset frame message from any other slave device 50. The ID of each preset frame message will carry the ID information of the corresponding slave device 50. Each slave device 50 will parse whether the received ID matches its own ID. If they match, it indicates that there is a slave device 50 with the same ID as itself on the communication line 60, and there is an address conflict. At this time, it will report the address conflict to master device 40 through an address conflict message to trigger automatic addressing.

[0104] Through the above scheme, the energy storage system of this application embodiment adds a ring-shaped addressing bus 30 between the slave devices 50 in terms of hardware. In terms of software, it can realize the detection of slave device address conflicts or slave device address anomalies, and automatically trigger addressing, accurately identify the number of slave devices 50, and detect whether automatic addressing is completed. The slave devices 50 can complete the device addressing action according to the master 40 instructions and hardware addressing signals, and also support manual addressing function. The entire energy storage system can flexibly support various combinations of slave devices 50, and promptly identify various abnormal states, trigger the completion of accurate addressing of slave devices 50, ensure the stable operation of the system, and realize the correspondence between software address and actual physical address, greatly facilitating after-sales maintenance, saving labor costs, and improving the maintainability and networking efficiency of the energy storage system.

[0105] Accordingly, this application provides an energy storage unit 11, including multiple battery management systems (BMCs) 111. Each BMC 111 includes an addressable bus interface, which includes a first interface 1111 and a second interface 1112. The second interface 1112 is used to connect with the first interface 1111 of the next adjacent BMC 111 via an addressable bus 30. The BMC 111 is also used to communicate with the battery cluster management unit (CMU) 12 via a controller area network (CAN). The BMC 111 is configured to perform the following steps: Receive the first addressing instruction, which includes the first device address. The first addressing instruction is determined and broadcast by CMU12 based on the current state of the addressing bus interface of each BMC111 when the addressing conditions are met. When the current state of the first interface 1111 is the first level state and it is not addressed, the first device address is obtained in response to the first addressing instruction; After addressing is completed based on the first device address, a first status message is fed back, and the current status of the second interface 1112 is switched to the second level state, so that the current status of the first interface 1111 of the next BMC 111 connected to the second interface 1112 is switched to the first level state. The first level state is different from the second level state.

[0106] For details not specifically described in the energy storage unit 11, please refer to the corresponding descriptions in the foregoing embodiments, which will not be repeated here.

[0107] The energy storage unit 11 in this embodiment can be automatically addressed and associated with the physical order on the addressing bus 30, thereby realizing the correspondence between the device address and the actual physical location. This facilitates the rapid location of physical devices when the energy storage system combination changes or when the equipment is maintained, and improves the maintainability and networking efficiency of the energy storage system.

[0108] Accordingly, in the energy storage system of this application embodiment, the device address of the slave device 50 after addressing can be associated with the physical order on the addressing bus 30, thereby realizing the correspondence between the device address and the actual physical location. Therefore, the energy storage system can quickly locate physical devices when the combination changes or the equipment is maintained, and has good maintainability and networking efficiency.

[0109] Accordingly, this application also provides an addressing method for an energy storage system, applied to the host 40 of the energy storage system in this application embodiment, including: In response to the fact that each slave 50 cascaded through the addressing bus 30 in the energy storage system meets the addressing conditions, the first slave to be addressed is determined based on the current state of the addressing bus interface of each slave 50, and a first addressing instruction is broadcast to multiple slaves 50 to trigger the addressing of the first slave to be addressed. The first addressing instruction includes the first device address of the first slave to be addressed. Receive the first status message from the first slave to be addressed, and re-determine the next first slave to be addressed based on the current status of the addressing bus interface of each slave 50.

[0110] The addressing method of the energy storage system in this application embodiment sets up multiple slave devices 50 cascaded via an addressing bus 30. When the slave devices 50 meet the addressing conditions, the master device 40 determines the first slave device to be addressed based on the current state of the addressing bus interface of the slave device 50, and broadcasts a first addressing instruction to the multiple slave devices 50 to trigger the addressing of the first slave device to be addressed. After broadcasting the first addressing instruction, the master device 40 receives a first status message fed back by the first slave device to be addressed, so that the device address of the slave device 50 can be associated with the physical order on the addressing bus 30, thereby realizing the correspondence between the device address and the actual physical location. This facilitates the rapid location of physical devices during combination changes or equipment maintenance, and improves the maintainability and networking efficiency of the energy storage system.

[0111] This application also provides a computer-readable storage medium storing a computer program thereon, which is loaded by a processor to perform the steps of any of the methods described above.

[0112] In the embodiments of this application, the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM), etc.

[0113] It should be noted that, in the data processing stage, the technical solution of this application has strictly limited the scope of data collection to the minimum necessary to achieve the technical objectives, preventing the acquisition of irrelevant information. For any user information to be collected, the data subject will be clearly informed and their consent obtained. Furthermore, technologies such as encrypted storage and access control are employed to strengthen data security and ensure the security and compliance of the entire data processing process. The technical model and decision-making mechanism are based on objective technical parameters and do not introduce unnecessary parameters such as gender or age that may lead to discrimination, resolutely eliminating algorithmic discrimination and upholding public order and good morals. In addition, the specification fully describes the technical implementation methods, application scenarios, and compliance protection details. The claims are consistent with the content of the specification, key compliance designs are clear and verifiable, and the overall technical design is guided by the protection of public interests and adherence to social ethics, without any circumstances that harm public interests or violate public order and good morals.

[0114] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0115] The above provides a detailed description of an energy storage system and its addressing method provided by the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. An energy storage system, characterized in that, include: Multiple slave devices, which are cascaded via an addressing bus; A host, which is communicatively connected to a plurality of slave devices; wherein the host is configured to perform the following steps: In response to the slave meeting the addressing conditions, a first slave to be addressed is determined based on the current state of the addressing bus interface of each slave, and a first addressing instruction is broadcast to multiple slaves to trigger the addressing of the first slave to be addressed. The first addressing instruction includes the first device address of the first slave to be addressed. Receive the first status message fed back by the first slave to be addressed, and re-determine the next first slave to be addressed based on the current status of the addressing bus interface of each slave.

2. The energy storage system according to claim 1, characterized in that, The host is configured to determine that the slave device meets the addressing conditions, including any one of the following: Receives an address conflict message from any of the slave devices; Receive any of the aforementioned slave devices sending an address error message; It is determined that each of the slave devices is in non-operation mode.

3. The energy storage system according to claim 2, characterized in that, The slave device is configured to perform the following steps: The device periodically receives preset frame messages from other slave devices, the preset frame messages including a second device address corresponding to the slave device; If the second device address matches the device's own address, an address conflict message is sent to the host.

4. The energy storage system according to claim 1, characterized in that, The slave device's addressing bus interface includes a first interface and a second interface, and the second interface of the slave device is connected to the first interface of the next adjacent slave device through the addressing bus. The initial state of each of the second interfaces is a first level state, the initial state of the first interface connected to the second interface is a second level state, and the initial state of the first interface not connected to the second interface is the first level state. The first level state is different from the second level state.

5. The energy storage system according to claim 4, characterized in that, The master is configured to determine the first slave to be addressed based on the current state of the addressing bus interface of each of the slaves, including: The slave device whose current state of the first interface is the first level state and which has not been addressed is identified as the first slave device to be addressed.

6. The energy storage system according to claim 5, characterized in that, The slave device is configured to perform the following steps: Receive the first addressing instruction broadcast by the host; When the current state of the first interface is the first level state and it is not addressed, the first device address is obtained in response to the first addressing instruction; After completing the addressing based on the first device address, the first status message is fed back, and the current status of the second interface is switched to the second level state, so that the current status of the first interface of the next slave device connected to the second interface is switched to the first level state.

7. The energy storage system according to claim 4, characterized in that, The host is also configured to perform the following steps: In response to the slave meeting the polling condition, the slave to be polled is determined based on the current state of the addressing bus interface of each slave, and a polling instruction is broadcast to each slave to trigger address polling of the slave to be polled, the polling instruction including the third device address of the slave to be polled; If no second status message is received from the slave device to be polled within a first preset time period, and the number of slave devices that have been successfully polled is not equal to the total number of slave devices, the polling is determined to have failed. If the number of consecutive polling failures does not reach the preset number and the slave device meets the polling conditions, the slave device to be polled is re-determined based on the current state of the address bus interface of each slave device, and the polling instruction is broadcast to multiple slave devices to trigger address polling of the slave device to be polled.

8. The energy storage system according to claim 7, characterized in that, The second status message includes an address matching message; The master is configured to determine the slave to be polled based on the current state of the address bus interface of each slave, including: The slave device whose current state of the first interface is the first level state and which has not been polled is identified as the slave device to be polled; The host is also configured to perform the following steps: In response to receiving the address matching message from the slave device to be polled within the first preset time period, the next slave device to be polled is determined again based on the current state of the addressing bus interface of each slave device.

9. The energy storage system according to claim 8, characterized in that, The second status message also includes an address error message; the slave device is configured to perform the following steps: Receive the polling instruction broadcast by the host; When the current state of the first interface is the first level state and it is not polled, in response to the polling instruction, the third device address is compared with its own device address; If the third device address matches the device address, an address matching message is sent back; if the third device address does not match the device address, an address error message is sent back. Switch the current state of the second interface to the second level state, so that the current state of the first interface of the next slave device connected to the second interface is switched to the first level state.

10. The energy storage system according to claim 7, characterized in that, The host is also configured to perform the following steps: Before broadcasting the polling instruction and / or the first addressing instruction, a first reset instruction is broadcast to trigger the slave to restore the current state of the addressing bus interface to the initial state; If the duration of the first reset instruction reaches the second preset duration, the polling instruction and / or the first addressing instruction are broadcast.

11. The energy storage system according to claim 1, characterized in that, The host is also configured to perform the following steps: In response to not receiving the first status message from the first slave device to be addressed within a third preset time period, the current pressure difference between the first total pressure and the second total pressure is determined, and if the current pressure difference is less than a preset pressure difference threshold, the addressing is determined to be successful. Wherein, the first total voltage is the total voltage of the energy storage system, and the second total voltage is obtained by accumulating the voltage of the slave device to be addressed based on the first status message that has been fed back.

12. The energy storage system according to claim 11, characterized in that, The host is also configured to perform the following steps: If the current differential pressure is greater than or equal to the preset differential pressure threshold, addressing failure is determined. If the number of consecutive addressing failures does not reach a preset number, a first reset command is sent to trigger the slave device to restore the current state of the addressing bus interface to the initial state, and to re-determine the first slave device to be addressed based on the current state of the addressing bus interface of each slave device, and to broadcast the first addressing command to multiple slave devices to trigger the addressing of the first slave device to be addressed.

13. The energy storage system according to claim 12, characterized in that, The host is also configured to perform the following steps: After successful addressing, or if the number of consecutive addressing failures has reached the preset number, a second reset command is broadcast to trigger the slave device to restore the current state of the addressing bus interface to its initial state and restart it.

14. The energy storage system according to claim 1, characterized in that, The host is also configured to perform the following steps: Receive a second addressing instruction, the second addressing instruction including the fourth device address of the second slave device to be addressed; The second addressing instruction is transmitted to the second slave device to be addressed, so that the second slave device to be addressed responds to the second addressing instruction, saves the fourth device address to the configuration parameters, and updates the CAN filter based on the fourth device address.

15. The energy storage system according to claim 1, characterized in that, The master unit is a battery cluster management unit (CMU), and the slave unit is a battery management controller (BMC). Alternatively, the master unit is a storage converter (PCS), and the slave unit is a battery cluster management unit (CMU).

16. An addressing method for an energy storage system, characterized in that, The host computer used in the energy storage system includes: In response to the fact that each slave device in the energy storage system cascaded via the addressing bus meets the addressing conditions, a first slave device to be addressed is determined based on the current state of the addressing bus interface of each slave device, and a first addressing instruction is broadcast to multiple slave devices to trigger the addressing of the first slave device to be addressed. The first addressing instruction includes the first device address of the first slave device to be addressed. Receive the first status message fed back by the first slave to be addressed, and re-determine the next first slave to be addressed based on the current status of the addressing bus interface of each slave.

Images