Method for automatically distributing charging module address

Abstract

The invention relates to the technical field of electronic equipment control, in particular to a method for automatically distributing charging module addresses, which is applied to equipment comprising a main control unit, a plurality of charging modules, two independent CAN buses, a power supply unit, an alternating current output relay and a fault prompt unit. Comprising the following steps of demand judgment and initial communication detection, hardware state detection and power-off verification, parallelization setting of module addresses one by one and final verification and process ending. Before an address setting process is started, through initial communication detection and hardware state detection, potential problems such as CAN bus communication abnormity, power supply fluctuation, alternating current output relay faults and module power-off incapability are checked in advance, once faults are found, accurate prompting is carried out through a multi-color LED lamp, an operator can conveniently and rapidly position and solve the problems before address configuration, and the operation efficiency is improved. Therefore, flow interruption or module damage caused by hardware faults in the setting process is avoided, the invalid debugging time is shortened, and the loss risk in the equipment debugging stage is reduced.

Description

Technical Field

[0001] This invention relates to the field of electronic device control technology, specifically a method for automatically allocating charging module addresses. Background Technology

[0002] With the increasing popularity of electric vehicles, the demand for high-power DC charging piles is growing. To meet the high power output requirements, a common solution is to use multiple power modules connected in parallel and working together. Each power module acts as an independent control unit and needs to exchange data with the main control unit in the charging pile through communication buses such as controller area networks to achieve functions such as power distribution, status monitoring, and fault handling. In order for the main control unit to accurately identify and access each module, each charging module must have a unique logical address in the bus network. Currently, the industry generally uses a manual setting mode for charging module address configuration. The specific operation is as follows: the operator enters a preset unique address for each charging module one by one through the DIP switch, physical button or dedicated configuration software on the module. After the setting is completed, it is necessary to manually verify whether the address is correct. If the address is found to be duplicated, missing or entered incorrectly, the configuration needs to be readjusted. The existing operating method has the following shortcomings. Specifically, for large charging piles containing dozens of modules, operators need to spend a lot of time repeatedly setting up actions on each module. Furthermore, operators are prone to duplicate addresses and input errors due to fatigue, lack of concentration, and counting mistakes, which increases the industry's statistical error rate. Therefore, a method for automatically allocating charging module addresses is needed to improve the above problems. Summary of the Invention

[0003] To address the problem that operators need to spend a lot of time repeatedly setting up actions on each module, and that operators are prone to address duplication and input errors due to fatigue, lack of concentration, and counting mistakes, thus increasing the industry's statistical error rate, this invention provides a method for automatically allocating charging module addresses to solve the above problems.

[0004] To achieve the above objectives, the present invention provides the following technical solution: A method for automatically assigning charging module addresses, applied to a device including a main control unit, multiple charging modules, two independent CAN buses, a power supply unit, an AC output relay, and a fault indication unit, includes the following steps: Step S1: Demand Assessment and Initial Communication Detection After the device is powered on, all modules are powered on simultaneously. The system determines whether automatic setting is required by checking the address duplication status and the automatic setting execution flag. The modules are kept powered on for 30 seconds and the communication status is checked. If any module fails to communicate, it is determined to be an anomaly. If all modules communicate normally, the system proceeds to the next step.

[0005] Step S2: Hardware status detection and power-down verification The status of the two CAN buses, power supply unit, and AC output relay are checked sequentially. If all are normal, all modules are powered down for 30 seconds and the power-down status is checked. If any module fails to power down, the second abnormality is determined. If all modules power down normally, proceed to the next step.

[0006] Step S3: Parallelize and set module addresses one by one Initialize module number m=1, address allocation start value is 1, start two CAN buses to work in parallel, and cyclically check whether slot m is empty. If it is not empty, perform the following operations: power on alone for 2 seconds - send address configuration message - 2 seconds verification - power off alone for 15 seconds.

[0007] If the setting fails, record exception number three without interrupting the process. After m++, repeat the loop until m>21, and control all modules to power on for 30 seconds before proceeding to the next step. Step S4: Final Verification and Process Closure The system checks the online status of all modules. If any module is offline, it is identified as an anomaly of type four. If all modules are online, the system checks the fault status codes. If any non-zero fault codes are found, it is identified as an anomaly of type five. If all modules are online and fault-free, the system is set to automatic setting execution, indicating successful setting and restarting the device to complete automatic allocation. Anomalies one through five are all indicated by the fault prompt unit. After troubleshooting, the process is restarted.

[0008] As a preferred embodiment of the present invention, the determination method for the "address duplication state" in step S1 is as follows: the power module directly identifies the address duplication situation and generates a fault signal. The main control unit does not need to actively detect it; it only needs to read the fault signal from the power module to meet the triggering conditions for automatic setting. The automatic setting execution flag is stored in a non-volatile memory unit (such as EEPROM or Flash) built into the main control unit. The initial value is "not executed." The main control unit reads the flag through communication interfaces such as I2C and SPI to ensure that the flag state is not lost after the device is powered off, and the historical setting results can be directly reused when the device is powered on again.

[0009] As a preferred embodiment of the present invention, the first anomaly in step S1 is defined as "the existence of a single-channel anomaly in two CAN communication channels, or an anomaly in the module power supply". The fault indication unit indicates this by keeping a red LED constantly lit. The main control unit records the time of the anomaly and the location of the non-communication module. After the troubleshooting is completed, the device needs to be restarted to re-execute the process.

[0010] As a preferred embodiment of the present invention, the specific rules for hardware status detection in step S2 are as follows: (1) CAN bus detection: Send test messages containing preset check codes to two CAN buses to verify that there are no packet loss, no error codes and the communication rate is 250Kbps or 500Kbps. If so, it is considered normal.

[0011] (2) Power supply unit detection: The output voltage is detected by the voltage sampling circuit. If the fluctuation range is ≤ ±5%, it is considered normal.

[0012] (3) AC output relay detection: Send a energizing / disengaging command, and confirm through the status feedback interface that all relays can respond normally, and determine that it is normal.

[0013] As a preferred embodiment of the present invention, the second abnormality in step S2 is defined as "abnormal working state of the module power-off circuit". The fault indication unit indicates this by keeping a yellow LED light on. The main control unit records the time of the abnormality and the number of the module that was not powered off. After the investigation is completed, the equipment needs to be restarted and the process needs to be executed again.

[0014] As a preferred embodiment of the present invention, the method for determining the empty slot in step S3 is as follows: manually setting the slot to have no module, directly skipping the module, directly executing the m increment operation, skipping the slot address setting, speeding up the process, and reducing unnecessary failures.

[0015] As a preferred embodiment of the present invention, the parallel operation rule of the two CAN buses in step S3 is as follows: one CAN bus is responsible for processing the charging module with the lower number, and the other CAN bus is responsible for processing the charging module with the higher number. The address setting process of the two groups of modules is executed synchronously, which shortens the total setting time.

[0016] As a preferred embodiment of the present invention, the address configuration message in step S3 is a broadcast message. During address configuration, all modules identify the broadcast message and power on only one module at a time. Therefore, only the module with the corresponding number processes the message, while other power-off modules cannot process the broadcast message.

[0017] As a preferred embodiment of the present invention, the third exception in step S3 is defined as "module m failed to set the address successfully". The handling method is as follows: the main control unit only records the module number, the time of occurrence and the fault type, without interrupting the overall loop process, and the subsequent module address setting is executed normally.

[0018] As a preferred embodiment of the present invention, in step S4, the fourth anomaly is indicated by a flashing orange LED, the fifth anomaly by a flashing red LED and a simultaneous output of the message "Communication failed, please manually troubleshoot and restart". Successful setup is indicated by a constantly lit green LED. After troubleshooting the fourth and fifth anomalies, the device needs to be restarted and the method re-executed until the setup is successful.

[0019] Compared with existing technologies, this invention optimizes the address setting cycle of a single charging module. By adopting parallel processing technology of two CAN buses, the system can operate multiple modules simultaneously, which reduces the overall setting time by a factor of two and improves the efficiency of production assembly and on-site debugging.

[0020] Compared with existing technologies, this invention, before the address setting process begins, conducts initial communication detection and hardware status detection to preemptively identify potential problems such as CAN bus communication anomalies, power fluctuations, AC output relay failures, and module power failures. Once a fault is detected, it is precisely indicated by multi-color LEDs, making it easy for operators to quickly locate and resolve the problem before address configuration. This avoids process interruptions or module damage caused by hardware failures during the setting process, reduces ineffective debugging time, and lowers the risk of damage during the equipment debugging phase.

[0021] Compared with existing technologies, this invention eliminates the need for manual intervention in address input, counting, or verification. By continuously incrementing the address from 1 and performing multiple rounds of verification, it ensures that the address of each module is unique and accurate. This solves common problems in manual settings, such as address duplication, input errors, and count omissions, thereby reducing the address configuration error rate and avoiding equipment failures such as module communication failures and power allocation disorder caused by address errors. This significantly improves the operational reliability of charging equipment.

[0022] Compared with existing technologies, the present invention allows only one module to be in working state at a time when powered on individually. At this time, the address configuration message is broadcast and only that module can receive and respond to it, avoiding the situation where multiple modules compete for the address and receive the wrong message when powered on at the same time, thus ensuring accurate and unique address allocation from a physical level. Attached Figure Description

[0023] Figure 1 This is an overall flowchart of the present invention; Figure 2 This is a flowchart of the requirement determination and initial communication detection process of the present invention; Figure 3 This is a flowchart of the hardware status detection and power-down verification process of the present invention; Figure 4 This is a flowchart illustrating the parallelization of setting module addresses one by one in this invention. Figure 5 This is a flowchart for the final verification and process completion of the present invention. Detailed Implementation

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

[0025] Example: Please refer to Figure 1-5 The method for automatically assigning charging module addresses, as shown, includes the following steps: Step S1: Requirements Assessment and Initial Communication Testing Process The core of this process is to determine whether to initiate automatic address allocation and to perform a preliminary test of module communication availability. The specific steps are as follows: Step S1.1: After the device is powered on, the main control unit starts up and controls the power supply unit to power on all charging modules simultaneously to ensure that the modules start up synchronously.

[0026] Step S1.2: The main control unit reads two key pieces of information from the storage unit to determine whether automatic settings are required: Address duplication detection: This is directly identified by the power module. The main control unit only needs to read the fault signal from the power module to meet the triggering conditions.

[0027] Automatic setup status detection: The initial value of the "automatic setup completion flag" in the storage unit is 0 (not executed). If it is 0, it is determined that "automatic setup has not been executed". Only when both "address duplication" and "automatic setup has not been executed" are met is it determined that "automatic setup is required". Otherwise, the process ends and the device operates according to the existing address.

[0028] Step S1.3: If automatic setup is required, perform the following operations: Keep all modules powered on for 30 seconds to ensure stable startup.

[0029] Initial communication detection: The main control unit sends a heartbeat message (100ms period, lasting 5 seconds). The main control unit synchronously judges whether the module power supply is stable by the communication status of the two CAN buses (such as message response rate and bit error rate). If there is no module response on either CAN bus, it is determined that there is a CAN bus fault or abnormal module power supply, and it is included in "abnormality handling".

[0030] First fault handling: If there is a communication failure in CAN1 or CAN2 or an abnormal power supply to the module (e.g., wiring error causing CAN bus communication to be interrupted with all modules), the red LED will stay on, and the fault information (time, location of the uncommunicated module) will be recorded. The module will remain in its current state. After troubleshooting, the device needs to be restarted to re-execute the process.

[0031] If CAN1 and CAN2 communicate normally, proceed to the next step.

[0032] It should be noted that the status of each module cannot be known without setting the module address.

[0033] Step S2: Hardware Status Detection and Power-Down Verification Process The core of this process is to check whether the hardware required for address allocation is functioning correctly and to verify the power-down controllability of the module. Specific steps include: Step S2.1: Hardware Status Detection: The main control unit sequentially detects three key hardware components: CAN bus detection: Send a test message containing a checksum to verify that there are no packet loss or error codes in the message and that the communication rate meets the preset requirements (250Kbps / 500Kbps).

[0034] Power supply unit detection: Determines whether the power supply is normal by checking whether the charging module is powered on.

[0035] It should be noted that this method cannot determine the status of a single charging power module, but can only obtain the overall status (such as the circuit breaker not being powered on, abnormal communication of the relay control board, etc., which will trigger this abnormality). If an individual module has an AC input abnormality (such as phase loss, abnormal voltage, etc.), it will be processed in the subsequent step S3 (parallel address setting process), that is, when the module is powered on and communicates individually, it will be judged and processed.

[0036] AC output relay detection: Send a energizing / disengaging command, and confirm that all relays are responding normally through the status feedback interface. If a hardware abnormality is detected, the yellow LED will flash. Restart after troubleshooting.

[0037] Step S2.2: Module power-down control: After the hardware detection is passed, control all modules to power down and maintain for 30 seconds to ensure that the modules are completely powered off.

[0038] Step S2.3: Power-down communication test: After power-down, send a heartbeat message. All modules should not respond (normal power-down).

[0039] Second fault handling: If there is a module response ("Module power-off circuit working status abnormal"), the yellow LED light will be constantly on. Record the fault information (time, module number that was not powered off), check the power control circuit and restart the equipment.

[0040] When all modules are powered down normally, proceed to the next step.

[0041] Step S3: Parallel address-by-address setting process The core of this process is to achieve precise address allocation through a "separate power-on - message broadcast - separate power-off" mode, combined with the parallel operation of two CAN buses. Specific steps are as follows: Step S3.1: Initialize parameters: Module number counter m=1, address allocation start value=1, start two CAN buses, grouping rules: CAN1 is responsible for modules 1-20, CAN2 is responsible for modules 21-40, to achieve parallel settings.

[0042] Step S3.2: Repeatedly execute the settings for a single module (until m > 21): Step S3.2.1: Set empty slot: (meaning that there is no charging module in this slot). Skip this module during execution and directly increment m++ to speed up the process and reduce unnecessary failures.

[0043] Step S3.2.2: Power on separately: Power on only module m for 2 seconds (to ensure stable startup of the module).

[0044] Step S3.2.3: Address setting: Send an address configuration message (broadcast message) through the corresponding CAN bus to ensure that only module m responds.

[0045] Step S3.2.4: Set verification: Wait 2 seconds to receive the module's "Set successful" feedback. If no feedback is received, it is judged as an error number 3.

[0046] Step S3.2.5: Exception handling for No. 3: Only record the fault information (module number, time), do not interrupt the process, and directly perform the power-down operation.

[0047] Step S3.2.6: Power off separately: Control module m to power off for 15 seconds (to ensure that the module is completely powered off and will not be repeatedly set to the module address).

[0048] Step S3.2.7: Parameter update: m++, address allocation start value +1, if m≤21, return to step S3.2.1, otherwise control all modules to power on for 30 seconds and proceed to the next process.

[0049] Step S4: Final Verification and Process Closure The core of this process is to comprehensively verify the address settings to ensure that all modules are working properly. Specific steps include: S4.1: Online status verification: The main control unit sends an online query message (50ms period, lasting 10 seconds) to count the number of response modules.

[0050] Fourth type of exception handling: When a module is offline, the orange LED light flashes, the offline module number is recorded, automatic setting fails, and the module is restarted after troubleshooting.

[0051] S4.2 Fault Status Verification: When all modules are online, send a fault query message and receive the module fault status code.

[0052] Fifth fault handling: When a non-zero fault code is present, the red LED flashes, indicating "Communication failed, please manually troubleshoot the fault and restart", and the fault module number and fault code are recorded.

[0053] S4.3 Process Closure: When all modules are online and fault-free, the "Automatic Setup Complete Flag" is set to 1, the green LED light stays on, the control device restarts, and the address allocation process is completed.

[0054] In the above embodiments: Normal state: Green LED is always on; Error #1: Red LED remains constantly lit (module failed to communicate).

[0055] Second anomaly: Yellow LED remains constantly lit (module cannot be powered off).

[0056] Anomaly No. 3: No individual light (events are recorded only).

[0057] Error #4: Orange LED flashing (module offline).

[0058] Error #5: Red LED flashing (module malfunction).

[0059] Based on the above embodiment, taking the automatic address allocation of 30 modules (fully configured with no empty slots) as an example, the following further explanation is provided: Equipment configuration: Charging modules: 30 (numbered 1-30), no empty slots.

[0060] Main control unit: Two CAN buses, communication rate 500Kbps; Grouping rules: CAN 1 is responsible for numbers 1-15, and CAN 2 is responsible for numbers 16-30.

[0061] Implementation process: Step S1: Power on the device → Power on all modules → Addresses are duplicated (default addresses are all 0) and no automatic settings have been performed → Power on all modules for 30 seconds → All 30 modules communicate normally → Proceed to Step S2.

[0062] Step S2: CAN bus, power supply, and relay detection are all normal → Power off all modules for 30 seconds → No module response (normal power off) → Proceed to Step S3.

[0063] Step S3: Initialize m=1, address=1 → CAN1 and CAN2 work in parallel: CAN1: Module 1 powers on for 2 seconds → sends address 1 → verification successful → powers off for 15 seconds → m=2 → … → Module 15 setup complete.

[0064] CAN2: Module 16 powers on for 2 seconds → sends address 16 → verification successful → powers off for 15 seconds → m=17 → … → Module 30 setup complete.

[0065] m=31>21→Power on all modules for 30 seconds→Proceed to process 4.

[0066] Step S4: All modules online → No faults → Green LED stays on → Set to completion indicator → Restart → Process complete.

[0067] Total time: 19 seconds × 15 = 285 seconds.

[0068] Further explanation can be given using the automatic address allocation of 18 modules (including 3 empty slots): Equipment configuration: Charging modules: 18 (numbered 1-18), slots 19-21 are empty.

[0069] Grouping rules: CAN1 is responsible for numbers 1-11, and CAN2 is responsible for numbers 12-21.

[0070] Implementation process: Steps S1-S2: Completed successfully without any issues; Step S3: Initialize m=1, address=1: m=1-18: Non-empty slots, set addresses 1-18 according to the process.

[0071] m=19-21: Empty slots → directly increment m.

[0072] m=22>21→Power on all modules for 30 seconds.

[0073] Step S4: All 18 modules are online and functioning without faults → Setup successful.

[0074] Total time: 19 seconds × 11 = 209 seconds, which is more efficient than manual labor.

[0075] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A method for automatically assigning charging module addresses, applied to a device comprising a main control unit, multiple charging modules, two independent CAN buses, a power supply unit, an AC output relay, and a fault indication unit, characterized in that, Includes the following steps: Step S1: Demand Assessment and Initial Communication Detection After the device is powered on, all modules are powered on simultaneously. The system determines whether automatic setting is required by the address duplication status and the automatic setting execution flag. The modules are kept powered on for 30 seconds and the communication status is checked. If any module fails to communicate, it is determined to be an abnormality. If all modules communicate normally, the system proceeds to the next step. Step S2: Hardware status detection and power-down verification The status of the two CAN buses, power supply unit and AC output relay are checked in sequence. If all are normal, all modules are powered down for 30 seconds and the power-down status is checked. If any module fails to power down, the second abnormality is determined. If all modules are powered down normally, proceed to the next step. Step S3: Parallelize and set module addresses one by one Initialize module number m=1, address allocation start value is 1, start two CAN buses to work in parallel, and cyclically check whether slot m is empty. If it is not empty, perform the following operations: power on alone for 2 seconds - send address configuration message - 2 seconds verification - power off alone for 15 seconds. If the setting fails, record exception number three without interrupting the process. After m++, repeat the loop until m>21, and control all modules to power on for 30 seconds before proceeding to the next step. Step S4: Final Verification and Process Closure The system checks the online status of all modules. If any module is offline, it is identified as an anomaly of type four. If all modules are online, the system checks the fault status codes. If any non-zero fault codes are found, it is identified as an anomaly of type five. If all modules are online and fault-free, the system is set to automatic setting execution, indicating successful setting and restarting the device to complete automatic allocation. Anomalies one through five are all indicated by the fault prompt unit. After troubleshooting, the process is restarted.

2. The method for automatically allocating charging module addresses according to claim 1, characterized in that, The determination method for "address duplication status" in step S1 is as follows: the power module directly identifies the address duplication situation and generates a fault signal. The main control unit does not need to actively detect it; it only needs to read the fault signal from the power module to meet the trigger conditions for automatic setting. The automatic setting execution flag is stored in the non-volatile memory unit (such as EEPROM or Flash) built into the main control unit. The initial value is "not executed." The main control unit reads the flag through communication interfaces such as I2C and SPI to ensure that the flag status is not lost after the device is powered off, and the historical setting results can be directly reused when the device is powered on again.

3. The method for automatically allocating charging module addresses according to claim 1, characterized in that, In step S1, the first anomaly is defined as "a single CAN communication failure exists in two channels, or a module power supply failure exists". The fault indication unit indicates this by keeping a red LED lit. The main control unit records the time of the anomaly and the location of the non-communication module. After troubleshooting, the equipment needs to be restarted and the process needs to be executed again.

4. The method for automatically allocating charging module addresses according to claim 1, characterized in that, The specific rules for hardware status detection in step S2 are as follows: (1) CAN bus detection: Send test messages containing preset check codes to two CAN buses to verify that there are no packet loss, no error codes and the communication rate is 250Kbps or 500Kbps. If so, it is considered normal. (2) Power supply unit detection: The output voltage is detected by the voltage sampling circuit. If the fluctuation range is ≤±5%, it is considered normal. (3) AC output relay detection: Send a energizing / disengaging command, and confirm through the status feedback interface that all relays can respond normally, and determine that it is normal.

5. The method for automatically allocating charging module addresses according to claim 1, characterized in that, In step S2, the second abnormality is defined as "abnormal working status of the module power-off circuit". The fault indication unit indicates this by keeping a yellow LED light on. The main control unit records the time of the abnormality and the number of the module that was not powered off. After troubleshooting, the equipment needs to be restarted and the process needs to be executed again.

6. The method for automatically allocating charging module addresses according to claim 1, characterized in that, The method for determining empty slots in step S3 is as follows: manually set the slot to have no module, skip the module, directly execute the m increment operation, skip the slot address setting, speed up the process, and reduce unnecessary failures.

7. The method for automatically allocating charging module addresses according to claim 1, characterized in that, In step S3, the parallel operation rule of the two CAN buses is as follows: one CAN bus is responsible for processing the charging module with the lower number, and the other CAN bus is responsible for processing the charging module with the higher number. The address setting process of the two groups of modules is executed synchronously, which shortens the total setting time.

8. The method for automatically allocating charging module addresses according to claim 1, characterized in that, In step S3, the address configuration message is a broadcast message. During address configuration, all modules recognize this broadcast message and only power on the current module. Therefore, only the module with the corresponding number processes the message, while other power-off modules cannot process the broadcast message.

9. The method for automatically allocating charging module addresses according to claim 1, characterized in that, In step S3, the third exception is defined as "module m failed to set address successfully". The handling method is: the main control unit only records the module number, the time of occurrence and the fault type, without interrupting the overall loop process, and the subsequent module address setting is executed normally.

10. The method for automatically allocating charging module addresses according to claim 1, characterized in that, In step S4, anomaly number four is indicated by a flashing orange LED, and anomaly number five is indicated by a flashing red LED, along with the message "Communication failed, please manually troubleshoot and restart"; successful setup is indicated by a solid green LED. After troubleshooting anomalies number four and five, the device must be restarted and this method re-executed until the setup is successful.

Images