A multi-stage ID calibration method for a BMS

Abstract

A multi-stage ID calibration method of a BMS relates to the technical field of ID calibration of a multi-stage architecture of a vehicle, and calibrates a master control ID through a wake-up line cascade and a hierarchical communication cascade. If a device is installed incorrectly, the problem of incorrect device installation can be handled by recalibrating the master control ID through a host computer without disassembling the device. The BMS comprises a host computer, at least one primary control and at least one secondary control. Each secondary control only belongs to one primary control. The host computer is in communication connection with each primary control, and the secondary control is in communication connection with the primary control to which it belongs. The at least one primary control is the first primary control to the Nth primary control arranged in natural numbers. The host computer is connected to the first primary control through a wake-up line. The first primary control and the Nth primary control are connected in turn through a wake-up line, and N is greater than or equal to 1. The secondary control belonging to the primary control comprises the first secondary control to the Mth secondary control arranged in natural numbers.

Description

Technical Field

[0001] This application relates to the field of ID calibration technology for multi-level vehicle architecture, and more particularly to a multi-level ID calibration method for BMS. Background Technology

[0002] When the system adopts a multi-level master control scheme, the traditional approach requires each master control device in the system to develop corresponding BOOT software and assign a unique communication ID. During installation, the devices need to be installed sequentially according to the labels on the motherboard. If the installation is incorrect, the system will not work properly and the devices need to be removed from the system. The devices can only be used after the BOOT and APP software are updated. Summary of the Invention

[0003] This application provides a multi-level ID calibration method for BMS, which calibrates the master control ID through wake-up line cascading and hierarchical communication cascading. If the device is installed incorrectly, the problem of device installation error can be handled by recalibrating the master control ID through the host computer without removing the device.

[0004] This application provides a multi-level ID identification method for a BMS. The BMS includes a host computer, at least one primary master controller, and at least one secondary master controller. Each secondary master controller is subordinate to only one primary master controller. The host computer is communicatively connected to each primary master controller, and the secondary master controller is communicatively connected to the primary master controller to which it belongs. The at least one primary master controller is arranged in a continuous sequence of natural numbers from the first primary master controller to the Nth primary master controller. The host computer is connected to the first primary master controller via a wake-up line, and the first primary master controller to the Nth primary master controller are connected in pairs via wake-up lines, where N≥1.

[0005] The secondary controllers subordinate to the primary controller include the first secondary controller to the Mth secondary controller, which are arranged consecutively by natural numbers. The first and second secondary controllers subordinate to the primary controller are connected to it through a wake-up line. The first secondary controller to the Mth secondary controller are connected in pairs through wake-up lines, where M≥0.

[0006] The multi-level calibration process includes a first calibration route and a second calibration route, which are calibrated sequentially.

[0007] The first calibration route is to sequentially wake up the first-level master controller to the Nth-level master controller via the wake-up line. After each master controller is woken up, its master controller type and ID are saved to form the first data group. The master controller feeds the first data group back to the host computer via the communication line. The host computer saves the first data group and forms the calibration ID of each master controller.

[0008] The second calibration route is to sequentially follow the first-level master controller to the Mth-level master controller via the wake-up line. After each master controller is woken up, it saves its master controller type and ID to form a second data group. The master controller feeds back the second data group to the master controller it belongs to via the communication line to form the calibration ID of each master controller.

[0009] In this application, the wake-up lines of each master controller are connected in a cascaded manner, and the wake-up lines of the upper and lower level master controllers are independent of each other; each level master controller is connected in parallel to the same communication line, and the communication lines of the upper and lower level master controllers are independent of each other, thus constructing a tree-shaped master-slave control architecture with clear hierarchy and unique ownership.

[0010] The wake-up line enables independent daisy-chain networking of primary and secondary master controllers, while the communication line enables hierarchical point-to-point communication between upper and lower levels. This ensures that each lower-level master controller belongs to only one upper-level master controller, completely avoiding the problems of multiple upper-level controllers competing for communication channels and chaotic device ID ownership.

[0011] Simultaneously, a dual-line coordination mode is adopted, in which the wake-up line is used for sequential wake-up at each level and the communication line is used for hierarchical feedback of calibration data. This distinguishes the wake-up link from the data transmission link. The wake-up line is only responsible for forwarding wake-up and calibration instructions at each level, while the communication line is only responsible for transmitting the master control ID and type data back. This achieves physical isolation of signal functions and avoids mutual interference between the wake-up level signal and the communication data message.

[0012] The system employs a two-stage calibration approach, following a top-down calibration sequence. First, it completes the calibration of the top-level master controller across the entire domain, and then proceeds with the calibration of the lower-level master controllers. This aligns with the top-down power-on and control logic of the BMS system, ensuring a complete match between the multi-level master controller calibration sequence and the overall system runtime sequence. It eliminates the need for the host computer to issue independent wake-up commands for each master controller, significantly simplifying the host computer's calibration control logic and reducing the occupancy of host computer hardware I / O ports and communication resources. This approach is suitable for batch automatic ID calibration scenarios in multi-node, multi-level BMS battery management systems. Furthermore, by relying on a device numbering method that uses consecutive natural numbers, it ensures consistency in the physical wiring sequence, wake-up serial connection sequence, and calibration ID sequence, thereby mitigating system communication anomalies caused by manual wiring errors from the ground up.

[0013] In some embodiments of this application, during multi-level calibration, in the first calibration route, the host computer sends a calibration instruction to the first-level master controller via a wake-up line, and the first-level master controller to the Nth-level master controller sequentially sends calibration instructions to the next-next-level master controller via a wake-up line; in the second calibration route, each first-level master controller receives a calibration instruction sent by its subordinate master controller via a wake-up line, and the first-level master controller to the Mth-level master controller sequentially sends calibration instructions to the next-next-level master controller via a wake-up line.

[0014] By limiting the calibration instructions to be forwarded step by step within the chain via the wake-up line, unlike the traditional method of broadcasting all calibration instructions from the host computer, the calibration instructions are transmitted synchronously and serially along the wake-up link.

[0015] In the primary master control calibration link, the host computer only needs to send a calibration command to the first primary master control once. All subsequent primary master controls automatically forward commands through the front-end wake-up line, without the host computer having to address and send commands one by one. In the secondary master control calibration link, each subordinate primary master control autonomously sends a calibration command to the first secondary master control at the next lower level. Automatic forwarding is also completed within the secondary master control link, completely relieving the host computer of the command scheduling pressure.

[0016] This system completely binds the order of instruction transmission to the physical serial wiring sequence of the devices. If the wiring sequence is disordered, the instructions cannot be forwarded normally. The system can automatically identify wiring faults in advance through the calibration process, realizing self-detection of wiring errors without the need for additional hardware detection circuits. This reduces the overall hardware detection cost and further strengthens the constraint logic of the uniqueness of the system wiring sequence, ensuring the reliability of multi-level master control networking.

[0017] In some embodiments of this application, the first calibration route includes the following process.

[0018] The first-level master controller receives the calibration command from the host computer; wakes up, and sets the wake-up output to 0; saves, and saves the CNC type and ID to form the first data group; calibrates, and sets the calibration completion flag to 1; and provides feedback, sending calibration completion information to the host computer in the format of data length + calibration command + first data group + total number of master controllers. The second-level master controller to the Nth-level master controller sequentially receive the calibration command forwarded by the previous-level master controller. Each master controller repeats the above wake-up, save, calibration, and feedback steps before forwarding the calibration command to the next-level master controller.

[0019] The four fixed steps for each primary controller to uniformly execute are: wake-up output reset to 0, data saving, calibration flag setting, and formatted feedback. This standardizes and unifies the calibration actions of all primary controllers, avoiding timing sequence errors caused by differences in the program logic of different controllers.

[0020] At the same time, a fixed feedback message format is specified, uniformly adopting a message structure of data length + calibration instruction + first data group + total number of master controllers. On the one hand, this facilitates the host computer to directly parse the device type, its own ID, and the total number of master controllers in the chain reported by each primary master controller, without the need to adapt multiple parsing programs for different devices, thus simplifying the host computer's message parsing logic. On the other hand, by reporting the total number of master controllers, the host computer can automatically verify whether the actual number of connected primary master controllers is consistent with the preset number, and quickly identify faults such as missing devices, offline, and hardware damage in the chain.

[0021] In some embodiments of this application, the second calibration route includes the following process.

[0022] The first and second-level master controllers receive calibration instructions from their subordinate first-level master controllers; wake up, setting the wake-up output to 0; save, saving the CNC type and ID to form a second data group; calibrate, setting the calibration completion flag to 1; feedback, feeding back calibration completion information to their subordinate first-level master controllers, with the feedback format being data length + calibration instruction + second data group + total number of master controllers; the second to Mth second-level master controllers sequentially receive calibration instructions forwarded by the previous first and second-level master controllers, and each second-level master controller repeats the above wake-up, save, calibration, and feedback steps before forwarding the calibration instructions to the next second-level master controller; when the Mth second-level master controller completes calibration, its subordinate first-level master controller feeds back all information to the host computer through the communication line.

[0023] It inherits the calibration sequence of the primary master controller and realizes automatic serial calibration within the lower secondary master controller chain. At the same time, it establishes a two-level hierarchical reporting mechanism for secondary master controllers to their respective primary master controllers, and for primary master controllers to uniformly summarize data to the host computer. This eliminates the need for secondary master controllers to directly establish communication and interaction with the host computer, which is in line with the hierarchical management logic of BMS and reduces the communication node pressure on the host computer.

[0024] The secondary master controller adopts the same calibration procedure and standardized feedback message format as the primary master controller. The software and hardware calibration programs can be developed universally, reducing software development and program maintenance costs. After all secondary master controllers have completed serial calibration, the primary master controller will collect all secondary master controller calibration information and upload it to the host computer, reducing the frequency and number of messages received by the host computer and reducing the load on the host computer's communication bus.

[0025] Meanwhile, this process ensures that the calibration of the secondary master control is strictly delayed until the calibration of its primary master control, following the hierarchical control logic of first the upper level and then the lower level, avoiding hierarchical control disorder caused by the lower master control being powered on or reporting data in advance, and adapting to the inherent control logic of the upper master control of the BMS system to control the lower master control.

[0026] In some embodiments of this application, the BMS further includes at least one third-level master controller, each third-level master controller being subordinate to only one second-level master controller. The third-level master controllers subordinate to the second-level master controllers include the first third-level master controller to the Lth third-level master controller, which are arranged consecutively by natural numbers. The second-level master controllers are connected to the first third-level master controllers to which they belong via wake-up lines. The first third-level master controllers to the Lth first-level master controllers are connected in pairs via wake-up lines, where L≥0. The second-level master controllers are communicatively connected to the third-level master controllers to which they belong.

[0027] The multi-level calibration process also includes a third calibration route. After the second calibration route of the second-level master controller under the first third-level master controller is completed, the third calibration route is started. The third calibration route is to wake up the first third-level master controller to the Lth third-level master controller in sequence through the wake-up line. After each third-level master controller is woken up, it saves its master controller type and ID to form a third data group. The third-level master controller feeds back the third data group to the second master controller under its jurisdiction through the communication line. The second master controller saves the third data group and forms the calibration ID of each third-level master controller.

[0028] Continuing with the consistent daisy-chain wake-up serial topology and top-down calibration sequence, the calibration of the third-level master control is started only after the calibration of the second-level master control is completed, ensuring that the calibration sequence of the entire system progresses step by step. At the same time, the dual-line working logic of forwarding calibration instructions step by step through the wake-up line and feeding back calibration data layer by layer through the communication line is adopted. The hardware wiring method and calibration process of the third-level master control are completely unified with the upper-level first-level and second-level master controls, without the need to redesign the hardware circuit and software calibration logic, and the solution has strong compatibility.

[0029] In addition, the three-level master controllers still maintain the topology rule of a single superior, with each three-level master controller belonging only to a single two-level master controller. All calibration data is aggregated upwards layer by layer, and there will be no data chaos across levels or branches. This enables automatic, orderly, and hierarchical ID calibration of multi-level BMS systems, improving the versatility of networking and calibration of large-scale BMS systems.

[0030] In some embodiments of this application, the third calibration route includes the following process.

[0031] The first and third level master controllers receive calibration instructions from their subordinate second level master controllers; wake up, and set the wake-up output to 0; save, and save the CNC type and ID to form the third data group; calibrate, and set the calibration completion flag to 1; feedback, and feed back calibration completion information to its subordinate second level master controllers. The feedback format is data length + calibration instruction + second data group + total number of master controllers.

[0032] The second-level master controller to the Lth-level master controller sequentially receive the calibration instructions forwarded by the previous level-three master controller. Each level-three master controller repeats the above wake-up, save, calibration, and feedback steps before forwarding the calibration instructions to the next level-three master controller. When the Lth-level master controller completes the calibration, its subordinate second-level master controller feeds back all information to its subordinate first-level master controller through the communication line, and the first-level master controller then feeds it back to the host computer.

[0033] The three-level master control step-by-step calibration process and the three-level hierarchical data reporting link are refined. The three-level master control reuses the same wake-up, save, calibration and feedback standardized steps as the upper-level master control. The generalization of the master control calibration program at all levels is further improved, effectively reducing the cost of overall software development, program burning and later debugging and maintenance of multi-level systems.

[0034] At the same time, it is clarified that the calibration data of the three-level master control needs to be transferred through the second-level master control and the first-level master control layer by layer before being uploaded to the host computer, thus constructing a complete three-level hierarchical reporting link. The host computer only needs to receive all the branch calibration data after being summarized by each first-level master control, without having to directly connect to the lower-level second-level and third-level master control, which greatly reduces the communication interaction pressure of the host computer.

[0035] Within the three-level master control chain, the logic of serial calibration and instruction forwarding per device is still executed to maintain the consistency of calibration sequence throughout the entire link. Relying on the natural sequence constraints of the wake-up daisy chain, it ensures that the physical wiring sequence, device ID sequence, and calibration sequence are completely consistent, further improving the automatic identification capability of multi-level master control wiring errors and device missing faults, and enhancing the fault tolerance and reliability of the entire calibration system.

[0036] In some embodiments of this application, the BMS further includes at least one slave controller, each slave controller belonging to only one level 3 master controller, and each slave controller is communicatively connected to the level 3 master controller to which it belongs.

[0037] Further expanding the level of end-control devices, this solution covers all hardware nodes of the complete BMS system, from the top-level host computer and multi-level master control to the bottom-level acquisition slave control. It fills the technical gap in the automatic ID calibration of all devices in the entire BMS system, enabling the calibration scheme to cover all control nodes and acquisition nodes of the BMS system. This allows for one-click automatic calibration of all electrical control devices in the entire system, eliminating the need for manual DIP code setting and ID burning for the bottom-level slave control. This completely solves the industry pain points of low efficiency and high human error rate in traditional manual calibration of bottom-level slave control.

[0038] At the same time, the topology rule of limiting the bottom slave control to a single three-level master control is defined, and the overall tree-shaped hierarchical networking architecture is continued. This ensures that the calibration process of the bottom slave control can be seamlessly connected to the calibration sequence of the upper three-level master control. The topology logic and timing logic of the whole system remain unified. The bottom slave control can be accessed without modifying any upper-level software or hardware architecture, and the solution has stronger scalability and adaptability.

[0039] In some embodiments of this application, the slave controllers belonging to the three-level master controller include the first slave controller to the Kth slave controller arranged consecutively in natural numbers. The three-level master controller and its subordinate first slave controller are connected through a wake-up line. The first slave controller to the Kth slave controller are connected in pairs through a wake-up line, and K≥0.

[0040] The multi-level calibration process also includes a fourth calibration route. After the third calibration route of the three-level master controller to which the first slave controller belongs is completed, the fourth calibration route is started. The fourth calibration route is to wake up the first slave controller to the Kth slave controller in sequence through the wake-up line. After each slave controller is woken up, it saves its master controller type and ID to form a fourth data group. The slave controller feeds back the fourth data group to the third master controller to which it belongs through the communication line. The third master controller saves the fourth data group and forms the calibration ID of each slave controller.

[0041] The bottom-level slave controllers use the same daisy chain wake-up line serial topology as the upper-level master controllers. The first slave controller is connected to the third-level master controller, and the wake-up lines of subsequent slave controllers are connected in series to form a complete bottom-level serial wake-up link. At the same time, it matches the fourth calibration route. After the third-level master controller is calibrated, all slave controllers are woken up serially level by level and the calibration instructions are forwarded level by level.

[0042] To ensure complete uniformity in the topology and calibration logic of all devices across the entire system, from the top-level master controller, second-level master controller, third-level master controller, to the bottom-level slave controllers, all adopt the same wake-up daisy chain connection method, the same hierarchical instruction forwarding logic, and the same step-by-step calibration process. The software and hardware programs of the entire system can be used to the greatest extent, without the need to develop dedicated calibration programs and hardware wiring logic for the bottom-level slave controllers. The cost of program development, production wiring, and after-sales maintenance is minimized. At the same time, relying on the serial calibration mode, the calibration status of each slave controller can be identified by the upper-level node in sequence, accurately locating the offline or fault location of a single slave controller in the chain. The fault location accuracy is high, which is suitable for BMS bottom-level acquisition array scenarios with a large number of slave controllers and concentrated arrangement.

[0043] In some embodiments of this application, the slave controller is connected to its subordinate third-level master controller via a wake-up line. When the third calibration route of the third-level master controller is completed, the third-level master controller sends a calibration instruction to each slave controller. After the slave controller is woken up, it saves its master controller type and ID to form a fourth data group. The slave controller feeds back the fourth data group to its subordinate third master controller via a communication line. The third master controller saves the fourth data group and forms the calibration ID of each slave controller.

[0044] It adopts a parallel calibration mode in which the three-level master control directly issues calibration instructions to all subordinate slave control units point-to-point, eliminating the need for slave control units to forward instructions in series via wake-up lines, thus simplifying the wiring of wake-up harnesses between underlying slave control units.

[0045] This solution eliminates the need to build a wake-up forwarding link within the slave control chain, reducing the amount of wake-up harnesses used between underlying slave controls, simplifying the internal wiring structure of the device, and reducing the probability of underlying harness failure. At the same time, it supports multiple slave controls to receive calibration instructions synchronously and complete ID calibration in parallel without waiting for each slave control to complete the calibration serially, which greatly shortens the overall calibration time of all slave controls at the underlying level and improves the calibration efficiency of all nodes of the whole machine.

[0046] This solution is suitable for BMS underlying data acquisition scenarios with a small number of slave controllers, dispersed devices, and no need for strict sequential binding. The serial solution is more flexible and can freely adapt the wiring method according to the actual layout of the underlying slave controllers, thereby improving product compatibility.

[0047] Compared with the prior art, this application has the following beneficial effects:

[0048] Addressing the inherent shortcomings of existing multi-level BMS master control schemes, this application's complete multi-level ID calibration scheme relies on a top-down wake-up line daisy chain hierarchical instruction forwarding architecture, coupled with a dual-line independent transmission mode for transmitting calibration instructions via wake-up lines and hierarchical return of calibration data via communication lines. This constructs a complete tree-shaped hierarchical calibration link from the first, second, and third level master controls to the bottom-level slave controls. Based on the hardware serial wiring sequence, it automatically completes hierarchical wake-up and automatic ID calibration, eliminating the need for pre-fixing of dedicated communication IDs at the factory and the need to develop multiple BOOT programs for different levels of master and slave controls. This enables universal BOOT software for all levels of devices, fundamentally reducing software version development and management costs.

[0049] Meanwhile, this solution strictly follows the step-by-step calibration sequence from top to bottom, and summarizes and reports calibration data layer by layer. It can automatically identify wiring errors, equipment disconnections, and installation misalignments by relying on the wake-up chain, without the need for manual verification of motherboard label numbers. Even if equipment is misinstalled on site, the system can automatically identify the anomaly through the calibration process, and can complete adaptive matching and repair without removing the equipment or re-burning the BOOT and APP programs, which greatly reduces the on-site assembly threshold and the difficulty of after-sales maintenance.

[0050] This application sets up two independent underlying slave control calibration paths, which are adapted to serial daisy chain centralized slave control networking and parallel point-to-point distributed slave control networking scenarios, respectively. It is compatible with different BMS hardware topologies and covers more industrial and energy storage BMS application conditions. While simplifying the difficulty of system software and hardware development, relaxing the restrictions on the field installation sequence, and improving the system's fault self-healing capability, it also takes into account the adaptation requirements of different underlying hardware layouts. It comprehensively makes up for the shortcomings of traditional multi-level BMS master control calibration schemes, such as strict assembly, complex repair, poor versatility, and high software and hardware redundancy. Attached Figure Description

[0051] The accompanying drawings are provided to further understand the technical solutions of the present invention and constitute a part of the specification. They are used together with the embodiments of this application to explain the technical solutions of the present invention and do not constitute a limitation on the technical solutions of the present invention.

[0052] Figure 1 This is one of the schematic diagrams of a multi-level ID identification method for BMS provided in the embodiments of this application.

[0053] Figure 2 This is a second schematic diagram of the multi-level ID identification method for BMS provided in the embodiments of this application.

[0054] Figure 3 This is the third schematic diagram of the multi-level ID identification method for BMS provided in the embodiments of this application.

[0055] Figure 4This is a schematic diagram of another embodiment of the multi-level ID identification method for BMS provided in the embodiments of this application. Detailed Implementation

[0056] 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.

[0057] It should be noted that all directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of the present invention are only used to explain the relative positional relationship and movement of each component in a certain specific posture (as shown in the figure). If the specific posture changes, the directional indication will also change accordingly.

[0058] 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 technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0059] In the description of this application, it should be noted that, unless otherwise expressly specified and limited, the terms "connected" and "linked" should be interpreted broadly, for example, as a fixed connection, a detachable connection, or an integral connection. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances. Furthermore, when describing pipelines, the terms "connected" and "linked" as used in this application have the meaning of establishing electrical connection. The specific meaning needs to be understood in conjunction with the context.

[0060] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0061] New energy vehicle power battery systems and large energy storage battery clusters both adopt a hierarchical multi-level master-slave electronic control architecture. The entire battery management system includes a host computer, a first-level master controller, a second-level master controller, a third-level master controller, and a bottom-level data acquisition slave controller. The master controllers at different levels have clear division of labor. The first-level master controller is responsible for the high-voltage safety management and command scheduling of the whole machine. The second-level master controller is responsible for the zone management and command relay of a single battery cluster. The third-level master controller is responsible for the fine management of battery modules. The bottom-level slave controller is responsible for the acquisition of raw data such as cell voltage, temperature, and insulation resistance. Multi-level collaboration realizes the monitoring and safety protection of the power battery throughout its entire life cycle.

[0062] The current industry-standard multi-level BMS master control ID configuration scheme has many unavoidable technical defects. Specifically, in the current traditional multi-level BMS system, each master control device and each underlying slave control device within the system requires the development of a dedicated matching BOOT boot program and APP application. Different levels and different serial numbers of electrical control hardware cannot use the same version of BOOT software. There are many software versions, the development cycle is long, the version management is difficult, and the later firmware maintenance cost is high. At the same time, all electrical control devices must be pre-programmed with a fixed and unique communication ID before leaving the factory. The communication ID cannot be changed adaptively on site, and device communication addressing relies entirely on the factory-fixed ID.

[0063] During the assembly and on-site maintenance of the complete equipment, staff must strictly follow the paper and electronic coding labels affixed to the surface of each main control motherboard and complete the wiring and assembly in a fixed natural number order. The assembly order cannot be changed and the equipment positions cannot be interchanged. If there is a manual assembly error or the wiring order is disordered, the entire BMS system will directly experience serious faults such as communication addressing failure, link wake-up interruption, inability to power on and run the entire machine, and failure of battery protection function. The system has no fault tolerance or adaptive repair capabilities.

[0064] After a misinstallation failure occurs, the repair work cannot be completed on-site. The staff must completely remove the incorrectly assembled main control equipment from the electrical control cabinet and vehicle electrical control compartment, and return it to the factory or use a special programming tool to rewrite the hardware's underlying BOOT program and the upper-level APP application. Only after reprogramming the new communication ID that matches the current wiring position can the equipment be reinstalled and put into use. The entire fault repair process is complex, time-consuming, and requires a high level of professional skills from the on-site maintenance personnel.

[0065] Furthermore, with the intelligent upgrade of new energy vehicles and the continuous iteration of in-vehicle intelligent driving hardware, peripherals such as in-vehicle millimeter-wave radar, vision cameras, temperature and humidity acquisition sensors, and battery safety monitoring sensors need to be flexibly added or removed according to the configuration of the vehicle model. The traditional BMS calibration scheme with fixed ID and fixed software version cannot adapt to the scenario of dynamic addition and removal of hardware. Every time the in-vehicle function is upgraded or hardware is added or removed, the main control program of the whole machine needs to be refreshed and the entire network communication ID table needs to be re-planned. The cost of upgrading the vehicle's electronic control is extremely high and cannot adapt to the development trend of modular and expandable electronic control in vehicles.

[0066] Therefore, please refer to Figures 1-3 This application provides a multi-level ID calibration method for BMS, which addresses the problem of device installation errors by recalibrating the master control ID and updating the APP software via a host computer without removing the device through wake-up line cascading and hierarchical communication cascading.

[0067] For details, please refer to Figures 1-3 The BMS system includes a host computer, a primary master controller, a secondary master controller, a tertiary master controller, and slave controllers. All electronic control hardware can adopt the standard automotive industrial structure design, adapting to the complex working conditions of high and low temperatures, vibration, and electromagnetic interference in the vehicle's electronic control cabin.

[0068] Please refer to Figures 1-3 The host computer can serve as the top-level scheduling and control device for the entire BMS system. It has excellent electromagnetic shielding and heat dissipation performance, and can isolate electromagnetic interference generated by the vehicle power motor and high-voltage wiring harness. The host computer integrates a main control MCU, a wake-up signal driver chip, a multi-channel communication transceiver chip, a data storage unit, and a calibration and scheduling unit, and belongs to the top-level control node of the entire system.

[0069] The host computer can have two types of external interfaces: a wake-up line interface and a communication line interface. The host computer establishes a single-line wake-up connection with the first primary master controller in the link only through its own wake-up line interface, and at the same time establishes a bidirectional communication connection with all primary master controllers through its own communication line interface. It is responsible for issuing the first round of global calibration instructions, receiving the calibration data summarized by all levels of master controllers, and storing the final calibration ID of all electronic control devices in the network. It does not forward wake-up signals and communication data between lower-level master controllers. It is the only overall scheduling terminal for the entire multi-level calibration process.

[0070] Please refer to Figure 1The primary controller is the first-level partition controller of the system. It has onboard wake-up input pins, wake-up output pins, bidirectional communication pins, local data storage units, and instruction forwarding units. All primary controllers are completely identical in size, hardware circuitry, underlying BOOT program, and upper-level APP program, with no hardware design differences. The connection methods are divided into two types: wake-up link and communication link. The wake-up link adopts a single-wire daisy-chain serial configuration. The wake-up output terminal of the host computer is connected to the wake-up input terminal of the first-level controller, and the wake-up output terminal of the first-level controller is connected to the wake-up input terminal of the second-level controller. Subsequent primary controllers are connected in series with their wake-up lines connected end to end. The entire process uses a unidirectional single-wire wake-up harness with no redundant wake-up loop harnesses. The communication link adopts a full-domain parallel bidirectional communication method. All primary controller communication interfaces are directly connected in parallel to the host computer communication bus, and each primary controller can independently complete bidirectional data interaction with the host computer.

[0071] The higher-level master controller receives the original calibration instructions issued by the host computer, completes its own ID calibration, and then forwards the wake-up calibration instructions to the next level master controller. At the same time, it receives the calibration data summarized by all its subordinate secondary master controllers, packages it in layers, and uploads it to the host computer. The first-level master controller is the relay hub between the top-level scheduling terminal and the lower-level partition master controllers, and manages the calibration timing and data reporting logic of all secondary master controllers, tertiary master controllers and slave controllers under its own branch.

[0072] Please refer to Figure 2 The secondary master controller is the second-level partition sub-master controller of the system. The PCB board material and onboard circuit structure can be exactly the same as the primary master controller, realizing the generalization of software and hardware structure, and eliminating the need for separate mold design of hardware structure.

[0073] The connection method also distinguishes between the wake-up link and the communication link. The wake-up link still adopts an independent grouped daisy chain single-line serial structure. Each primary master controller is individually connected to the wake-up input terminal of the primary and secondary master controllers under its own branch. Within the same branch, the wake-up lines of the primary and secondary master controllers to the Mth secondary master controller are connected in series. The wake-up links of secondary master controllers in different branches are independent of each other and are not connected to each other. The communication link adopts a hierarchical point-to-point communication mode. The secondary master controller does not directly connect to the upper computer communication bus, but only establishes a bidirectional communication connection with its own directly subordinate primary master controller. There is no communication interaction channel between secondary master controllers across branches.

[0074] The secondary master controller receives the calibration wake-up command forwarded by the primary master controller above it. After completing its own calibration, it forwards the command downwards. At the same time, it summarizes the calibration data of all its subordinate tertiary master controllers, packages it, and uploads it to the directly subordinate primary master controller. The secondary master controller realizes the timing control of calibration and the hierarchical transfer of data within a single branch.

[0075] Please refer to Figure 2The Level 3 master controller is the third-level module-level master controller of the system. The wake-up link adopts the same single-line daisy chain topology. The direct subordinate Level 2 master controller connects to the wake-up input of the first and third level master controllers in the branch. The wake-up lines of all Level 3 master controllers in the branch are connected in series. The communication link only establishes bidirectional point-to-point communication with the direct subordinate Level 2 master controller. There is no cross-level or cross-branch communication path. In terms of functional relationship, the Level 3 master controller completes its own ID calibration and instruction forwarding. At the same time, it manages the calibration sequence of the lowest level slave controller. After summarizing all the calibration data of the lowest level slave controller, it feeds it up to the Level 2 master controller. It is a key relay node between the upper-level master controller and the lower-level acquisition slave controller.

[0076] Please refer to Figure 3 The slave controller can be the lowest-level data acquisition and execution node in the system, and can include battery cell data acquisition slave controllers, vehicle temperature sensors, vehicle pressure sensors, intelligent driving radar peripheral data acquisition nodes, etc.

[0077] The slave controllers can be divided into two connection topologies. The first topology is a daisy chain structure in which wake-up lines between slave controllers are connected end to end. The second topology is a parallel topology in which all slave controllers independently connect to the superior three-level master controller and there are no wake-up lines between slave controllers. The communication link is unified so that the slave controllers only communicate bidirectionally with the directly subordinate three-level master controllers, and there is no independent communication channel between slave controllers.

[0078] The slave controller is responsible for receiving calibration instructions from the superior, completing the storage of its own master controller type and ID data, reporting its own calibration information, and routinely collecting battery operating parameters and intelligent driving perception data. It is the last data acquisition unit in the entire system.

[0079] Please refer to Figures 1-3 The functional lines are the wake-up line and the communication line (the line with the black arrow in the diagram is the wake-up line). These two types of lines are physically independent, arranged in parallel, and completely isolated in function, with no inclusion or signal multiplexing relationship. The wake-up line can be a single-core shielded copper wire, transmitting the wake-up signal and calibration command in a single direction. It is only used to transmit the wake-up signal and calibration forwarding command level by level, and does not transmit any data packets such as device ID, device type, or operating status. The communication line can be a dual-core differential shielded communication harness, supporting bidirectional differential data transmission. It is only used for hierarchical return of calibration data groups and device response signals, and does not transmit wake-up signals or trigger commands. The physical isolation between the two lines completely eliminates mutual interference between command signals and data signals, ensuring the stable operation of the multi-level calibration process.

[0080] The overall system timing logic strictly follows the top-down step-by-step calibration principle, executing in the order of first-level master control calibration, second-level master control calibration, third-level master control calibration, and bottom-level slave control calibration. The next level calibration process is only started after the previous level calibration process is completed. The timing logic is irreversible, non-parallel, and non-preemptive.

[0081] In some examples, please refer to Figure 1The BMS includes a host computer, at least one primary master controller, and at least one secondary master controller. Each secondary master controller is subordinate to only one primary master controller. The host computer communicates with each primary master controller, and each secondary master controller communicates with its subordinate primary master controller. The at least one primary master controller is arranged in a consecutive natural number sequence from the first to the Nth primary master controller. The host computer is connected to the first primary master controller via a wake-up line, and each of the first to the Nth primary master controllers is connected to each other via a wake-up line, where N ≥ 1. N can be 1, 2, 3, 5, 7, ..., 99.

[0082] Secondary master controllers subordinate to the primary master controller include the first to the Mth secondary master controllers, arranged consecutively by natural numbers. Each primary master controller is connected to the first or Mth secondary master controller via a wake-up line. Each pair of primary master controllers is connected via a wake-up line, where M ≥ 0. M can be 0, 1, 2, 3, 5, 7, ..., 99. Different primary master controllers may have different numbers of secondary master controllers, or some may be the same.

[0083] The multi-level calibration process includes a first calibration route and a second calibration route, which are calibrated sequentially.

[0084] The first calibration route involves sequentially waking up the first-level master controller (up to the Nth level) via a wake-up line. After each master controller is woken up, its master controller type and ID are saved to form a first data group. The first-level master controller then feeds this first data group back to the host computer via a communication line. The host computer saves the first data group and generates a calibration ID for each master controller. The contents of the first data group differ for different master controllers (from the first to the Nth level) to distinguish them, thus generating different encoded IDs.

[0085] The second calibration route involves sequentially assigning secondary master controllers (from the first to the Mth secondary master controller) to each primary master controller via wake-up lines. Upon wake-up, each secondary master controller saves its master controller type and ID to form a second data group. This second data group is then fed back to its subordinate primary master controller via a communication line, forming the calibration ID for each secondary master controller. The contents of the second data group differ between different secondary master controllers (from the first to the Mth secondary master controller) to distinguish them and thus generate different encoded IDs.

[0086] The first and second data groups are different to avoid failures caused by encoding conflicts.

[0087] Please refer to Figure 1 In this application, the wake-up lines of each master controller are connected in a cascaded manner, and the wake-up lines of the upper and lower level master controllers are independent of each other; each master controller is connected in parallel to the same communication line, and the communication lines of the upper and lower level master controllers are independent of each other, thus constructing a tree-shaped master-slave control architecture with clear hierarchy and unique ownership.

[0088] Please refer to Figure 1 For example, a BMS system includes a host computer, at least one primary master controller, and at least one secondary master controller. At the same time, each secondary master controller is strictly constrained to only be subordinate to one primary master controller. There is no topology chaos such as one secondary master controller simultaneously connecting to two primary master controllers or multiple upper-level controllers competing for lower-level links. This eliminates the problems of chaotic communication ID addressing and wake-up signal conflicts of lower-level devices from the hardware connection level, and is compatible with the native control logic of the BMS system with one master and multiple slaves and hierarchical management.

[0089] At the communication connection level, the host computer establishes a direct bidirectional communication connection with all first-level master controllers. The first-level master controllers only establish point-to-point communication with their subordinate second-level master controllers. Subordinate master controllers cannot communicate directly with the host computer, thus achieving hierarchical isolation of communication data.

[0090] At the wake-up connection level, the first-level master controllers of the entire domain form a complete serial daisy chain link based on the wake-up line. The wake-up port of the host computer is individually connected to the first first-level master controller of the link. The remaining first-level master controllers are connected to each other in turn by the start and end of the wake-up line to form a pure serial wake-up link without branches or parallel connections. Regardless of whether the number of first-level master controllers N is 1 or greater than 1, this serial wake-up topology remains unchanged.

[0091] Please refer to Figure 1 Each secondary master controller under a primary master controller replicates the same wake-up daisy chain topology. The first and second secondary master controllers within a single branch connect to the wake-up port of the primary master controller above. The wake-up lines of the remaining secondary master controllers within the branch are connected in series. The number of secondary master controllers M can be 0, meaning that the primary master controller can run independently without any subordinate secondary master controllers. This adapts to simple BMS systems without secondary branches, thus improving the solution's compatibility.

[0092] At the calibration process level, a first calibration route and a second calibration route are set with a fixed order and cannot be executed in parallel. The first calibration route always has a higher priority than the second calibration route. The second calibration route can only be started after the first calibration route has been fully executed, which is in line with the top-down power-on and control logic of the electronic control system.

[0093] The first calibration route performs serial automatic wake-up and ID calibration for all primary master controllers. The wake-up line completes the sequential wake-up of primary master controllers level by level. Each primary master controller that has been woken up automatically saves its own master controller hardware type and unique ID corresponding to the current link position in its local storage unit, generating a first data group in a fixed format. After completing the local data storage, all primary master controllers rely on bidirectional communication lines to feed their own first data groups up layer by layer, and finally all of them are summarized and uploaded to the host computer. The host computer uniformly receives, parses, and stores all first data groups, and automatically matches and generates a unique calibration ID corresponding to each primary master controller. The entire process does not require the host computer to issue addressing commands one by one, nor does it require manual preset of ID parameters.

[0094] Please refer to Figure 1 The second calibration route performs serial wake-up and ID calibration for each branch's subordinate secondary master controllers. Relying on the wake-up signal forwarded by the corresponding primary master controller, it wakes up all secondary master controllers within the branch one by one. The secondary master controllers locally save the master controller type and their own ID to generate a second data group. Unlike the primary master controllers which directly upload to the host computer, the secondary master controllers only feed back their communication data to their directly subordinate primary master controllers. The primary master controllers then complete the branch data aggregation and upload it uniformly. Finally, the second data group is used to complete the automatic allocation of calibration IDs for all secondary master controllers.

[0095] Compared to traditional solutions, the principle lies in binding the physical installation order and calibration ID order of the devices through a fixed serial wake-up link in hardware, eliminating the need for pre-programming fixed communication IDs at the factory. At the same time, the main control hardware structure is consistent across all levels, and the BOOT software is universal. The dual-line separation design ensures that wake-up commands and communication data do not interfere with each other, and the layered calibration logic conforms to the original timing of the electronic control system. This solves the core defects of traditional solutions that require differentiated BOOT software and manual pre-programming of IDs from the bottom layer. Meanwhile, the layered communication architecture reduces the communication load on the host computer.

[0096] Please refer to Figure 1 In some examples, during multi-level calibration, in the first calibration path, the host computer sends calibration instructions to the first-level master controller via a wake-up line. The first-level master controller to the Nth-level master controller then sequentially sends calibration instructions to the next-next-level master controller via the wake-up line. In the second calibration path, each first-level and second-level master controller receives calibration instructions sent by its subordinate first-level master controller via a wake-up line. The first-level and second-level master controllers to the Mth-level master controllers then sequentially send calibration instructions to the next-next-level master controller via the wake-up line. M can be 0, 1, 2, 3, 5, 7, ..., 99.

[0097] For example, during the operation of the first calibration route, the host computer only needs to send one original calibration instruction to the first-level master controller at the beginning of the link once. There is no need to issue instructions separately for each master controller. In the subsequent daisy chain of master controllers, all subsequent master controllers rely on the previous master controllers to directly forward the calibration instructions through the wake-up line. The instructions are transmitted synchronously with the wake-up level signal. The instruction transmission path and the wake-up signal transmission path are completely overlapped. The instruction forwarding sequence and the wake-up sequence are completely synchronized.

[0098] During the operation of the second calibration route, the first and second level master controllers at the beginning of each branch receive the branch-specific calibration instructions sent by the direct first level master controller through the wake-up line. Subsequently, all second level master controllers within the same branch also rely on the wake-up lines connected to the front and back to obtain the forwarded calibration instructions from the previous first level second level master controller, realizing the autonomous serial forwarding of instructions within a single branch without the participation of a host computer.

[0099] The existing wake-up harness is reused to transmit commands, eliminating the need for additional dedicated command transmission harnesses. This maximizes the use of existing hardware harness resources and reduces the overall wiring cost. At the same time, the calibration command transmission sequence is strictly bound to the hardware wake-up line wiring sequence. If the manual wiring sequence is reversed or the equipment is incorrectly installed on-site, the calibration command cannot be forwarded to the next level device, and the entire calibration link will stop. The system can automatically identify wiring faults and achieve automatic diagnosis of wiring errors without the need for additional hardware detection circuits.

[0100] Simultaneously, the instructions are forwarded synchronously with the wake-up signal, ensuring that the calibration instructions can be received the instant the device is woken up. The wake-up action and the issuance of calibration instructions are seamlessly connected, reducing the overall calibration waiting time and improving the overall calibration efficiency.

[0101] Please refer to Figure 1 In some examples, the first calibration route includes the following process.

[0102] The first-level master controller receives the calibration command from the host computer; wakes up, and sets the wake-up output to 0; saves, and saves the CNC type and ID to form the first data group; calibrates, and sets the calibration completion flag to 1; and provides feedback, sending calibration completion information to the host computer in the format of data length + calibration command + first data group + total number of master controllers. The second-level master controller to the Nth-level master controller sequentially receive the calibration command forwarded by the previous-level master controller. Each master controller repeats the above wake-up, save, calibration, and feedback steps before forwarding the calibration command to the next-level master controller.

[0103] For example, the complete calibration process for a first-level master controller consists of six interconnected steps: receiving instructions, wake-up reset, data saving, setting calibration flags, data feedback, and instruction forwarding. First, the first-level master controller receives the original calibration instruction sent from the host computer's wake-up line. It then performs a wake-up reset, setting its own wake-up output port level to 0, completing the initialization of the local wake-up circuit, eliminating residual calibration signals from the previous round, and preventing historical signals from interfering with the current calibration process. Subsequently, the local non-volatile storage unit automatically saves the local master controller hardware type and link location matching ID, generating a standardized first data group. Next, the local calibration completion flag is forcibly set to 1, marking that the local controller has completed the entire calibration process, preventing repeated instruction reception and calibration. Then, a calibration response message is fed back to the host computer in a fixed and unified format. The feedback message is composed of four parts: data length, original calibration instruction code, first data group, and the total number of first-level master controllers in the link, concatenated sequentially. The message format is uniform across the entire domain, allowing the host computer to directly parse the message content without adapting to multiple parsing logics. Finally, after completing the feedback, the local controller automatically forwards the calibration instruction to the next adjacent first-level master controller.

[0104] The second-level master controller to the Nth-level master controller completely replicates the above calibration steps without any program logic differences. The calibration, feedback, and instruction forwarding actions are completed serially for each unit until the entire first-level master controller link is fully calibrated.

[0105] Serial calibration feedback can avoid multiple primary controllers simultaneously uploading messages to the host computer, eliminating communication bus message conflicts and bus congestion. At the same time, reporting the total number of controllers allows the host computer to automatically compare the actual number of online devices with the preset number of devices, quickly identifying link device disconnection, hardware damage, and device missing faults. The unified message format greatly simplifies the host computer software parsing logic and reduces the difficulty of host computer software development.

[0106] Please refer to Figure 1 In some examples, the second calibration route includes the following process.

[0107] The first and second-level master controllers receive calibration instructions from their subordinate first-level master controllers; wake up, setting the wake-up output to 0; save, saving the CNC type and ID to form a second data group; calibrate, setting the calibration completion flag to 1; feedback, feeding back calibration completion information to their subordinate first-level master controllers, with the feedback format being data length + calibration instruction + second data group + total number of master controllers; the second to Mth second-level master controllers sequentially receive calibration instructions forwarded by the previous first and second-level master controllers, and each second-level master controller repeats the above wake-up, save, calibration, and feedback steps before forwarding the calibration instructions to the next second-level master controller; when the Mth second-level master controller completes calibration, its subordinate first-level master controller feeds back all information to the host computer through the communication line.

[0108] For example, after the first and second-level master controllers within a single branch receive the calibration instruction forwarded by the wake-up line of the directly subordinate first-level master controller, they sequentially execute the following actions: setting the wake-up output to 0, saving the second data group locally, setting the calibration completion flag to 1, and feeding back the calibration information to the superior first-level master controller. The format of the feedback message is completely consistent with that of the first-level master controller, except that the data group inside the message is replaced with the second data group. Subsequently, the second and second-level master controllers up to the Mth second-level master controller receive the forwarded instruction from the previous level one by one and repeat the entire calibration process until the calibration of the Mth second-level master controller at the very end of the single branch is completed.

[0109] The most critical hierarchical reporting logic is as follows: all secondary master controllers do not directly communicate with the host computer. After all secondary master controllers in the entire branch have been calibrated, the primary master controller corresponding to that branch will uniformly summarize all secondary master controller calibration data in the branch, package and integrate it, and upload it to the host computer in one go.

[0110] Adhering to a hierarchical tree-like management architecture, this significantly reduces the frequency and number of messages received by the host computer, lowering the load on the host computer's communication bus. Simultaneously, the calibration processes, message formats, and program logic are completely consistent across all levels. Developers only need to develop one universal calibration program to adapt to all primary and secondary master controllers, eliminating the need for differentiated software development at each level and drastically reducing software development cycles and maintenance costs. Furthermore, secondary calibration lags behind primary calibration throughout, ensuring that lower-level calibration only begins after all upper-level master controllers are ready, preventing timing issues caused by lower-level controllers prematurely powering on and preempting communication links.

[0111] Please refer to Figure 2 In some examples, the BMS also includes at least one tertiary master controller. Each tertiary master controller is subordinate to only one tertiary master controller. The tertiary master controllers subordinate to the tertiary master controllers include the first tertiary master controller to the Lth tertiary master controller, which are consecutively arranged by natural numbers. The tertiary master controllers are connected to their subordinate first tertiary master controllers via wake-up lines. The first tertiary master controllers to the Lth tertiary master controllers are connected in pairs via wake-up lines, where L≥0. The tertiary master controllers are communicatively connected to their subordinate tertiary master controllers. L can be 0, 1, 2, 3, 5, 7, ..., 99.

[0112] The multi-level calibration process also includes a third calibration route. After the second calibration route of the second-level master controller under the first third-level master controller is completed, the third calibration route is started. The third calibration route is to wake up the first third-level master controller to the Lth third-level master controller in sequence through the wake-up line. After each third-level master controller is woken up, it saves its master controller type and ID to form a third data group. The third-level master controller feeds back the third data group to the second master controller under its jurisdiction through the communication line. The second master controller saves the third data group and forms the calibration ID of each third-level master controller.

[0113] Please refer to Figure 2 For example, each Level 3 master controller is uniquely subordinate to one Level 2 master controller, with no cross-branch affiliation; the wake-up topology still replicates the unified daisy chain single-line serial structure of the upper layer, with the directly subordinate Level 2 master controller connecting to the wake-up input of the first and third level master controllers within the branch, and the wake-up lines of all Level 3 master controllers within the branch connected in series; the communication topology maintains hierarchical point-to-point communication, with Level 3 master controllers only communicating bidirectionally with their directly subordinate Level 2 master controllers, without cross-level communication.

[0114] The calibration sequence is strictly enforced to be sequential. The third calibration route can only be started after all the second calibration routes of the secondary master control have been executed and the calibration of the entire secondary master control has been completed. The timing is irreversible.

[0115] The working principle of the third calibration route is completely the same as that of the upper two-level calibration routes. It relies on the wake-up line to wake up all three-level master controllers in sequence. The machine automatically saves the master controller type and the corresponding link ID to generate the third data group. The communication data of the three-level master controllers is relayed upward layer by layer. First, it is fed back to the direct second-level master controller, then it is summarized by the second-level master controller and fed back to the first-level master controller. Finally, it is uniformly uploaded to the host computer to complete the matching of the three-level master controller calibration IDs.

[0116] It continues the entire hardware topology, dual-line connection method, and software calibration logic of the upper layer, and can expand to the third layer main control without changing the original hardware and software architecture. The solution has strong expansion compatibility and can meet the networking and calibration requirements of large, complex, multi-level BMS systems.

[0117] Please refer to Figure 2 In some examples, the third calibration route includes the following process.

[0118] The first and third level master controllers receive calibration instructions from their subordinate second level master controllers; wake up, and set the wake-up output to 0; save, and save the CNC type and ID to form the third data group; calibrate, and set the calibration completion flag to 1; feedback, and feed back calibration completion information to its subordinate second level master controllers. The feedback format is data length + calibration instruction + second data group + total number of master controllers.

[0119] The second-level master controller to the Lth-level master controller sequentially receive the calibration instructions forwarded by the previous level-three master controller. Each level-three master controller repeats the above wake-up, save, calibration, and feedback steps before forwarding the calibration instructions to the next level-three master controller. When the Lth-level master controller completes the calibration, its subordinate second-level master controller feeds back all information to its subordinate first-level master controller through the communication line, and the first-level master controller then feeds it back to the host computer.

[0120] Please refer to Figure 2 Specifically, the steps of receiving instructions, waking up and resetting, saving data, setting flags, providing data feedback, and forwarding instructions executed by each of the three-level master controllers are exactly the same as those of the first-level and second-level master controllers. This achieves 100% universality of the calibration program for all levels of master controllers. The entire machine only needs one universal BOOT program to adapt to all levels of master controllers, completely eliminating the drawbacks of traditional solutions with multiple versions of BOOT software.

[0121] At the data reporting link level, it is clear that the calibration data of the three-level master control needs to go through a complete three-level relay link: the three-level master control → the directly subordinate two-level master control → the directly subordinate one-level master control → the host computer. All terminal three-level data are not directly uploaded to the host computer. All lower-level data in the entire domain are aggregated by the corresponding superior node branches and then uploaded uniformly.

[0122] On the one hand, it continuously reduces the communication pressure on the host computer; the more layers there are, the more significant the burden reduction effect of hierarchical aggregation and reporting. On the other hand, it ensures a unified serial wake-up across the entire link, always guaranteeing that the hardware wiring sequence, wake-up sequence, and calibration ID allocation sequence are completely bound together. The system can accurately locate any single-point device disconnection or line breakage fault in the multi-level link, with fault location accuracy covering every main control node, improving the convenience of system operation and maintenance.

[0123] Please refer to Figure 3 In some examples, the BMS also includes at least one slave controller, each slave controller belonging to only one level 3 master controller, and each slave controller is communicatively connected to the level 3 master controller to which it belongs.

[0124] For example, the slave controller can include all end-of-line acquisition hardware such as battery acquisition slave controller, vehicle temperature sensor, pressure sensor, intelligent driving radar perception peripheral, etc., so that the solution of the present invention covers all categories of BMS electronic control hardware from the top-level host computer to the bottom-level perception peripheral, and realizes full coverage automatic calibration of all electronic control hardware of the entire battery and vehicle intelligent driving system.

[0125] Please refer to Figure 3 The topology rules continue the principle of a single subordinate across the entire domain. Each underlying slave controller is only subordinate to one third-level master controller, and there is no issue of slave controllers being attached to multiple third-level master controllers or multiple superiors controlling slave controllers. At the communication level, all slave controllers only establish bidirectional communication connections with their directly subordinate third-level master controllers. There are no independent communication channels between slave controllers, ensuring that the underlying communication links are clean and free from interference. All data collected and calibrated by the slave controllers are controlled by the superior third-level master controllers.

[0126] It addresses the shortcomings of traditional solutions that require manual DIP switches to set IDs and separate program burning for the slave controller at the bottom level, and achieves automatic calibration of the master and slave controller hardware across the entire domain, fully covering all electrical control nodes of the BMS system.

[0127] Please refer to Figure 3 In some examples, the slave controllers belonging to the third-level master controller include the first slave controller to the Kth slave controller arranged in consecutive natural numbers. The third-level master controller and its subordinate first slave controller are connected through a wake-up line. The first slave controller to the Kth slave controller are connected in pairs through wake-up lines, and K≥0.

[0128] Please refer to Figure 3 The multi-level calibration process also includes a fourth calibration route. After the third calibration route of the three-level master controller to which the first slave controller belongs is completed, the fourth calibration route is started. The fourth calibration route is to wake up the first slave controller to the Kth slave controller in sequence through the wake-up line. After each slave controller is woken up, it saves its master controller type and ID to form a fourth data group. The slave controller feeds back the fourth data group to the third master controller to which it belongs through the communication line. The third master controller saves the fourth data group and forms the calibration ID of each slave controller.

[0129] For example, all slave controllers under the third-level master controller are arranged in natural number order as slave controller 1 to slave controller K. The wake-up output port of the third-level master controller is directly connected to the wake-up input port of the first slave controller in the branch. The wake-up lines of the first slave controller to the Kth slave controller are connected in series from beginning to end. The slave controller wake-up link structure is completely consistent with the wake-up link structure of the upper-level first-level, second-level, and third-level master controllers.

[0130] A fourth calibration route is added accordingly. In terms of timing, it must wait for the third calibration route of the three-level master control to be completed before starting. It cannot be executed in parallel in advance. During the calibration process, the wake-up line forwards the calibration command level by level, wakes up all slave controllers one by one, and the slave controllers locally save their own hardware type and matching ID to generate the fourth data group, which is fed back to the direct third-level master control level by level. Finally, it is summarized and uploaded to the host computer by the third-level, second-level and first-level master control levels.

[0131] The entire domain has a completely unified hardware wake-up topology, calibration process, and software program. The whole machine software development, hardware wiring, and after-sales maintenance have no different logic, resulting in the lowest cost. At the same time, serial calibration can accurately locate the fault location of each end slave controller, which is suitable for battery pack internal acquisition scenarios with a large number of slave controllers and centralized array arrangement.

[0132] Please refer to Figure 4 In some other examples, the slave controller is connected to its subordinate third-level master controller via a wake-up line. When the third calibration route of the third-level master controller is completed, the third-level master controller sends a calibration instruction to each slave controller. After the slave controller is woken up, it saves its master controller type and ID to form a fourth data group. The slave controller feeds back the fourth data group to its subordinate third master controller via the communication line. The third master controller saves the fourth data group and forms the calibration ID of each slave controller.

[0133] Please refer to Figure 4 Specifically, the wake-up serial wiring harness between slave controllers is eliminated, and there are no wake-up lines connecting all slave controllers. Only the point-to-point independent wake-up line between each slave controller and its direct third-level master controller is retained. After the third-level master controller completes its own calibration, it directly sends calibration instructions to all subordinate slave controllers through its own multi-way wake-up port. All slave controllers receive the instructions synchronously and complete the ID calibration in parallel without having to wait serially for each slave controller.

[0134] Please refer to Figure 4 After the slave controller completes calibration, it still feeds back the fourth data group to the directly subordinate level 3 master controller. The subsequent hierarchical reporting logic is completely consistent with the previous solution. This solution eliminates the need for a large number of serial wake-up harnesses between slave controllers, simplifies the wiring difficulty in the narrow space inside the battery pack, and reduces the number of fault points in the underlying harness. The parallel calibration mode significantly shortens the overall calibration time of the underlying slave controllers, making it suitable for vehicle electronic control scenarios with a small number of slave controllers, dispersed hardware layout, and scattered installation of intelligent driving peripherals.

[0135] Please refer to Figure 3 and Figure 4The two slave control solutions can complement each other to adapt to more vehicle and energy storage BMS underlying hardware layouts and improve the product adaptability of the solutions.

[0136] In some embodiments, there is one host computer and one primary master controller, i.e., N=1, with no second or subsequent primary master controllers; each primary master controller is connected to three secondary master controllers, namely the first secondary master controller, the second secondary master controller, and the third secondary master controller, i.e., M=3; each secondary master controller is connected to three tertiary master controllers, with L=3 tertiary master controllers per branch; each tertiary master controller is connected to two lower-level slave controllers, with K=2 slave controllers per tertiary master controller. All master controllers in the entire domain share the same version of general-purpose BOOT software, without the need to distinguish between different levels and burn different programs.

[0137] The wake-up connection is as follows: the host computer's wake-up output is connected to the wake-up input of a single primary master controller. Since there is only one primary master controller, there are no subsequent connected devices in the primary master controller wake-up link, and the primary master controller wake-up output is idle. The primary master controller wake-up output port branches into three independent wake-up branches, which are connected to the wake-up inputs of the first, second, and third secondary master controllers, respectively. The three secondary master controller wake-up links are independent of each other. Each secondary master controller wake-up output is connected in series with its three subordinate tertiary master controllers. That is, the wake-up port of the first and second secondary master controllers is connected in series with the first, second, and third tertiary master controllers. The second and third secondary master controllers replicate the same tertiary master controller series topology. For the slave control link, each tertiary master controller wake-up port is connected in series with two slave controllers, and the wake-up lines between the slave controllers are connected end-to-end.

[0138] The communication lines connect the host computer's communication port to a single primary master controller for bidirectional communication; each primary master controller establishes independent bidirectional point-to-point communication with three secondary master controllers; each secondary master controller communicates bidirectionally with its three subordinate tertiary master controllers; each tertiary master controller communicates bidirectionally with its two subordinate slave controllers; all lower-level hardware does not communicate across levels, and all communication data is relayed in a hierarchical manner.

[0139] Specifically, after the host computer powers on, it initiates a global calibration process, sending a calibration command to the only primary master controller via the wake-up line. Upon receiving the command, the primary master controller sets its wake-up output to 0, initializes its local wake-up circuit, saves the primary master controller's hardware type and link matching ID in its local storage unit, generates the first data group, and sets the calibration completion flag to 1. Subsequently, it sends data length + calibration command + first data group + total number of master controllers (total number of master controllers is set to 1) back to the host computer according to a fixed message format. After receiving the message, the host computer parses the data and completes the binding of the primary master controller's calibration ID. Since there is only one primary master controller, there are no subsequent primary master controllers to forward commands, so the first calibration route ends directly, and the calibration of all primary master controllers is completed.

[0140] After the first calibration route of the primary master controller is completed, the second calibration route is started simultaneously. Branch calibration instructions are sent to the first, second, and third secondary master controllers via three independent wake-up lines. The three secondary master controller links execute the same calibration actions in parallel, while each link itself is executed serially. Taking the first and second-level master controller links as an example, after receiving the instruction, the first and second-level master controllers set their wake-up output to 0, save the secondary master controller type and ID to generate the second data group, set the calibration flag to 1, and feed the data back to the primary master controller. The instructions are then forwarded to the second and second-level master controllers, and then forwarded to the third secondary master controller. After the three secondary master controllers complete their calibration sequentially, the primary master controller aggregates all the second data groups from the three secondary master controllers, packages them, and uploads them to the host computer. The host computer completes the ID calibration of the three secondary master controllers, and the second calibration route is completed.

[0141] After all secondary master controllers are calibrated, the third calibration route is initiated. Each secondary master controller wakes up its three subordinate tertiary master controllers one by one via the wake-up line. The tertiary master controllers replicate the unified calibration steps, generate the third data set, and feed it back upwards. After all three tertiary master controllers in a single branch are calibrated, the secondary master controllers summarize the data of the three tertiary master controllers in the branch and upload it to the primary master controller. The primary master controller then summarizes all the tertiary master controller data again and uploads it to the host computer, completing the automatic ID calibration of all 9 tertiary master controllers. The third calibration route then ends.

[0142] Each level 3 master controller wake-up port connects two slave controllers in series. After the first slave controller receives the instruction and completes the calibration, it forwards the instruction to the second slave controller. The two slave controllers are calibrated serially and reported to the fourth data group level by level. Finally, the data is summarized in layers and sent to the host computer.

[0143] A total of 18 underlying slave controllers across the entire domain completed automatic ID calibration without any manual intervention, ID pre-burning, or verification of motherboard labeling order.

[0144] In the actual mass production and deployment of vehicle-mounted BMS and energy storage BMS, a unified hardware motherboard, unified BOOT program, and unified calibration program are directly adopted. The assembly of the whole machine does not require distinguishing the equipment serial number or checking the motherboard label. After the whole machine is powered on, it automatically completes the automatic calibration of the ID of all devices in the whole domain according to the top-down four-level calibration route. During daily use, the underlying perception sensors and intelligent driving peripherals can be added or removed at will, and the system will adaptively complete the ID update. After the equipment is inspected and moved, the corresponding ID will be automatically rematched during the next power-on calibration. No manual intervention is required throughout the process. It can be directly applied to the power battery management system of the entire new energy passenger vehicle and the battery cluster management system of the energy storage station.

[0145] For example, the primary master controller, secondary master controller, and slave controller mentioned above can also be directly configured, or the host computer, primary master controller, and slave controller can be directly configured.

[0146] In the description of this specification, specific features, structures, materials, or characteristics may be combined in any suitable manner in one or more embodiments or examples.

[0147] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A multi-level ID identification method for a BMS, characterized in that, The BMS includes a host computer, at least one primary master controller and at least one secondary master controller. Each secondary master controller is subordinate to only one primary master controller. The host computer is communicatively connected to each primary master controller, and the secondary master controller is communicatively connected to the primary master controller to which it is subordinate. At least one of the primary controllers is a first-level primary controller to an Nth-level primary controller arranged in a continuous natural number sequence. The host computer is connected to the first-level primary controller via a wake-up line. The first-level primary controller to the Nth-level primary controller are connected in pairs via wake-up lines, where N≥1. The secondary master controllers subordinate to the primary master controller include the first secondary master controller to the Mth secondary master controller, which are arranged consecutively by natural numbers. The first secondary master controller subordinate to the primary master controller is connected to it via a wake-up line. The first secondary master controller to the Mth secondary master controller are connected in pairs via wake-up lines, where M≥0. The multi-level calibration process includes a first calibration route and a second calibration route, which are calibrated sequentially. The first calibration route is to sequentially wake up the first level master controller to the Nth level master controller via the wake-up line. After each level master controller is woken up, its master controller type and ID are saved to form a first data group. The level master controller feeds back the first data group to the host computer through the communication line. The host computer saves the first data group and forms the calibration ID of each level master controller. The second calibration route is to sequentially follow the first to Mth secondary master controllers belonging to each of the primary master controllers via the wake-up line. After each secondary master controller is woken up, it saves its master controller type and ID to form a second data group. The secondary master controller feeds back the second data group to the primary master controller to which it belongs via the communication line to form the calibration ID of each secondary master controller.

2. The multi-level ID identification method for BMS according to claim 1, characterized in that, In the aforementioned multi-level calibration In the first calibration route, the host computer sends a calibration command to the first-level master controller through the wake-up line, and the first-level master controller to the Nth-level master controller sequentially sends calibration commands to the next level master controller through the wake-up line. In the second calibration route, each of the first secondary master controllers receives a calibration instruction sent by its subordinate primary master controller through the wake-up line, and the first secondary master controller to the Mth secondary master controller sequentially send calibration instructions to the next secondary master controller through the wake-up line.

3. The multi-level ID identification method for BMS according to claim 2, characterized in that, The first calibration route includes: The first-level master controller receives the calibration instructions from the host computer; Wake up, wake-up output is set to 0; Save the CNC type and ID to form the first data group; Calibration is complete; set the calibration completion flag to 1. Feedback is provided to the host computer to indicate that the calibration is complete. The feedback format is: data length + calibration instruction + first data group + total number of main controllers. The second-level master controller to the Nth-level master controller sequentially receive the calibration instructions forwarded by the previous level master controller. Each level master controller repeats the above wake-up, save, calibration, and feedback steps before forwarding the calibration instructions to the next level master controller.

4. The multi-level ID identification method for BMS according to claim 2, characterized in that, The second calibration route includes: The first and second level master controllers receive the calibration instructions from the first level master controller to which they belong; Wake up, wake-up output is set to 0; Save the CNC type and ID to form a second data group; Calibration is complete; set the calibration completion flag to 1. Feedback is provided to the primary master controller to which it belongs, with the feedback format being data length + calibration instruction + second data group + total number of master controllers. The second to Mth secondary master controllers sequentially receive the calibration instructions forwarded by the previous primary and secondary master controllers. Each secondary master controller repeats the above wake-up, save, calibration, and feedback steps before forwarding the calibration instructions to the next secondary master controller. Once the Mth secondary master controller is calibrated, the primary master controller to which it belongs will send all information back to the host computer via the communication line.

5. The multi-level ID identification method for BMS according to any one of claims 1 to 4, characterized in that, The BMS also includes at least one tertiary master controller, each of which is subordinate to only one tertiary master controller. The tertiary master controllers subordinate to the tertiary master controller include a first tertiary master controller to an Lth tertiary master controller arranged consecutively by natural numbers. Each tertiary master controller is connected to its subordinate first tertiary master controller via a wake-up line. The first tertiary master controllers to the Lth tertiary master controller are connected in pairs via wake-up lines, where L≥0. Each tertiary master controller has a communicative connection with its subordinate tertiary master controller. The multi-level calibration process also includes a third calibration route, which is initiated after the second calibration route of the second-level master controller to which the first third-level master controller belongs is completed. The third calibration route involves sequentially waking up the first to the Lth level master controllers via the wake-up line. After each level master controller is woken up, its master controller type and ID are saved to form a third data group. The level master controller feeds back the third data group to its subordinate second master controller via the communication line. The second master controller saves the third data group and forms the calibration ID of each level master controller.

6. The multi-level ID identification method for BMS according to claim 5, characterized in that, The third calibration route includes: The first and third level master controllers receive the calibration instructions from the second level master controllers to which they belong; Wake up, wake-up output is set to 0; Save the CNC type and ID to form a third data group; Calibration is complete; set the calibration completion flag to 1. Feedback is provided to the subordinate secondary master controller, and the feedback format is: data length + calibration instruction + second data group + total number of master controllers. The second and third level master controllers, up to the Lth level master controller, sequentially receive the calibration instructions forwarded by the previous level master controller. Each level master controller repeats the above wake-up, save, calibration, and feedback steps before forwarding the calibration instructions to the next level master controller. Once the Lth level master controller is calibrated, its subordinate secondary master controller will feed back all information to its subordinate primary master controller via the communication line, and the primary master controller will then feed it back to the host computer.

7. The multi-level ID identification method for BMS according to claim 5, characterized in that, The BMS also includes at least one slave controller, each slave controller belonging to only one of the three-level master controllers, and each slave controller is communicatively connected to the three-level master controller to which it belongs.

8. The multi-level ID identification method for BMS according to claim 7, characterized in that, The slave controllers belonging to the three-level master controller include the first to the Kth slave controllers, arranged consecutively by natural numbers. The three-level master controller is connected to its subordinate first slave controller via a wake-up line. The first to the Kth slave controllers are connected in pairs via wake-up lines, where K ≥ 0. The multi-level calibration process also includes a fourth calibration route, which is initiated after the third calibration route of the three-level master controller to which the first slave controller belongs is completed. The fourth calibration route involves sequentially waking up the first to the Kth slave controllers via the wake-up line. After each slave controller is woken up, it saves its master controller type and ID to form a fourth data group. The slave controller feeds back the fourth data group to the third master controller it belongs to via the communication line. The third master controller saves the fourth data group and forms the calibration ID of each slave controller.

9. The multi-level ID identification method for BMS according to claim 7, characterized in that, The slave controller is connected to its subordinate third-level master controller via a wake-up line. When the third calibration route of the third-level master controller is completed, the third-level master controller sends a calibration instruction to each slave controller. After the slave controller is woken up, it saves its master controller type and ID to form a fourth data group. The slave controller feeds back the fourth data group to its subordinate third-level master controller via the communication line. The third-level master controller saves the fourth data group and forms the calibration ID of each slave controller.

Images