Host fault processing method, system and charging pile

Abstract

The application provides a host fault processing method, system and charging pile. The method comprises the following steps: when detecting that a local machine receives an exception, the local machine closes a sending function of the local machine; after detecting that the host is lost, other machines select a slave machine from the other machines to serve as the host through host searching, and the other machines are charging modules connected to the same CAN bus as the host. The application can make the host that receives the exception quit the host election by closing the sending function of the host that receives the exception, and all the other machines perform the host searching operation to determine the unique host, so that the fault processing mode is simple and the system runs stably.

Description

Technical Field

[0001] This invention relates to the field of electric vehicle charging control technology, and in particular to a fault handling method, system and charging pile for a host. Background Technology

[0002] Electric vehicle charging stations typically have multiple charging modules to charge multiple electric vehicles, reducing queuing time and improving charging efficiency. Currently, multiple charging modules generally use a master-slave current sharing method, where the master module is accurately located, issues a current sharing command, and the slave modules output current according to the command.

[0003] Currently, when host duplication occurs, i.e., there are multiple hosts, if one of the hosts has a receiving abnormality, the charging module with the receiving abnormality will usually exit the host, and the other host will perform host duplication detection, exit the host, and re-find a host.

[0004] However, with the above-mentioned fault handling method, if other charging modules detect a low host serial number during the host acquisition process and assume they are not the host, it may result in the host never appearing on the bus, causing a host disconnection fault and paralyzing the entire charging system. Furthermore, the repeated host detection process is cumbersome, increasing the complexity of the detection. Summary of the Invention

[0005] This invention provides a method, system, and charging pile for handling host faults, in order to solve the problems of system paralysis and cumbersome operation caused by repeated host failures and abnormal host reception in the prior art.

[0006] In a first aspect, embodiments of the present invention provide a method for handling host faults, comprising:

[0007] When the host detects an abnormality in its own reception, it disables the host's transmission function.

[0008] After other machines detect that the host has lost connection, they select one of the other machines to act as the host through a master search. The other machine is a charging module connected to the same CAN bus as the host.

[0009] In one possible implementation, detecting a local reception anomaly includes:

[0010] No messages were received by this machine.

[0011] One possible implementation also includes: when the host receives a message sent by another machine, it performs a master search and uses the master search result of the host as the highest priority to determine the master-slave relationship of the host.

[0012] In one possible implementation, when the host receives a message from another machine, it performs a master-slave search and uses the master-slave search result as the highest priority for master-slave localization, including:

[0013] When a host receives a message from another machine, it determines the host's search result based on the message and its own identification information.

[0014] The master-slave operation is performed with the highest priority based on the master-slave search result of the local machine.

[0015] In one possible implementation, the identification information includes the machine number, and determining the master-finding result of the machine based on the message and the machine's identification information includes:

[0016] When the machine number of the local machine is the smallest or the machine number is the largest, the host search result of the local machine is determined based on the message and the machine number of the local machine, and the local machine is determined to act as the first host.

[0017] It also includes: the other machines select one machine from the other machines to serve as the second host through a master-finding process.

[0018] One possible implementation also includes:

[0019] The first host outputs current according to its own capacity, and the remaining current is distributed by the second host and all slaves.

[0020] In one possible implementation, the identification information includes the machine number, and determining the master-finding result of the machine based on the message and the machine's identification information includes:

[0021] When the machine number of the local machine is not the smallest or the largest, the master-slave result is determined based on the message and the machine number of the local machine, and the local machine is assigned to act as the slave machine.

[0022] It also includes: the other machines select one machine from the other machines to serve as the sole host through a master-finding process.

[0023] One possible implementation also includes:

[0024] The single master and all slaves are current-equalized according to the current.

[0025] Secondly, embodiments of the present invention provide a current sharing system for handling host failures, comprising: all machines connected to the same CAN bus, including a host and at least one slave machine;

[0026] The host is used to disable the sending function of the local machine when it detects an abnormality in local reception;

[0027] Each slave device is used to select one of the other slave devices to act as the master device after the other devices detect that the master device has lost connection. The other devices are charging modules connected to the same CAN bus as the master device.

[0028] Secondly, embodiments of the present invention provide a charging pile that applies the current sharing system for handling host failures described above.

[0029] This invention provides a fault handling method, system, and charging pile for a host. When the host detects an abnormality in its own reception, it shuts down its own transmission function, causing the host with the abnormal reception to withdraw from the host election. After each slave detects that the host has lost connection, it selects one slave to act as the host by searching for a master slave. This makes the fault handling method simple and the system runs stably. Attached Figure Description

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

[0031] Figure 1 This is a flowchart of a host fault handling method provided in an embodiment of the present invention;

[0032] Figure 2 This is a schematic diagram of the host provided in an embodiment of the present invention (where the host with the largest host number is receiving abnormally);

[0033] Figure 3 This is a schematic diagram of the host provided in an embodiment of the present invention (where the host with the smallest host number is receiving data abnormally);

[0034] Figure 4 This is a flowchart of a host fault handling method provided in another embodiment of the present invention;

[0035] Figure 5 This is a schematic diagram of the host provided in an embodiment of the present invention (where the host with the smallest host number sends an error);

[0036] Figure 6 This is a schematic diagram of the host provided in an embodiment of the present invention (where the host with the largest host number sends an abnormal message);

[0037] Figure 7 This is a schematic diagram of the structure of a host fault handling system provided in an embodiment of the present invention. Detailed Implementation

[0038] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of the invention. However, those skilled in the art will understand that the invention can be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods are omitted so as not to obscure the description of the invention with unnecessary detail.

[0039] To make the objectives, technical solutions, and advantages of the present invention clearer, specific embodiments will be described below in conjunction with the accompanying drawings.

[0040] Figure 1 A flowchart illustrating the implementation of a host fault handling method according to an embodiment of the present invention is described in detail below:

[0041] When the host detects an abnormality in its local reception, it disables its local transmission function.

[0042] After other machines detect that the master is disconnected, they select one of the other machines to act as the master through a master search. The other machines are charging modules connected to the same CAN bus as the master.

[0043] In one embodiment, when there is only one master unit among all the charging modules (i.e., all the units) in the charging pile, the master unit experiences a reception failure. After disabling its transmission function, the other slave units cannot receive messages from the master unit and assume that the master unit is disconnected. Upon detecting this disconnection, each slave unit initiates a master-finding operation. Since the receiving unit with the reception failure has disabled its transmission function, it does not participate in the master-finding operation. Therefore, the master-finding operation can determine a unique master unit from among the units other than the receiving unit with the reception failure. The remaining units are slave units, and the slave units obey the master unit, achieving current sharing between the master and slave units. Thus, the receiving unit with the reception failure can quickly select a unique master unit without affecting the master-finding operation of other units by simply disabling its transmission function, ensuring stable system operation.

[0044] Another scenario involves duplicate master modules, meaning other modules also have a master module. Let's first describe the operating scenario. Suppose that charging module 1 is the master module and is operating normally. However, a sudden event occurs, causing master module 1 to disconnect from the CAN bus. Here, all charging modules communicate through the CAN bus. When master module 1 disconnects from the CAN bus, there is no master module on the bus, so a master search operation is performed. If module 2 is selected as the new master module, communication with master module 1 will be restored after a period of time. However, either master module 1 or master module 2 will experience communication abnormalities again, only able to send messages but unable to receive messages.

[0045] In the prior art, in this situation, the host receiving the abnormality will exit the host, and then all other charging modules (including duplicate hosts and all slaves) will compete for the host again.

[0046] For example, such as Figure 2 As shown, if host 2 experiences a reception error, it will exit the host list. Host 1 will also exit the host list due to long-term host duplication. Host 1 and all slaves will then search for a new host. According to the host search rules, the charging module with the smallest serial number will become the host. Since the charging module with the smallest serial number is the charging module with the smallest serial number, it will gain the host status and become the new host when competing for the host again. It is also possible that the charging module with the smallest serial number did not detect the host duplication beforehand and did not exit the host list. In this case, host 1 will still maintain its host status after host 2 exits the host list.

[0047] For example, such as Figure 3 As shown, host 1 experiences a reception error, host 2 detects a duplicate host status and exits the host state. Host 1 detects its own communication error and automatically exits the host state. Host 2 and the remaining slaves then attempt to find a new host. According to the host search rules, host 2 finds host 1's information, and its own search result indicates it is a slave. Therefore, a new host can never be found on the bus, resulting in a host disconnection failure. Even with endless attempts to find a new host, the system will fail and paralyze. If the order in which host 2 and host 1 exit the host state is reversed (host 1 has already exited, but host 2 has not yet reached the timeout period for exiting after a duplicate host status), host 2 will remain the host, becoming the sole host on the bus. However, this method of combining host duplicate detection and reception error handling has a limitation: the host duplicate detection fault count time must be greater than the reception communication timeout delay. This ensures that modules with communication errors exit the host status promptly, making host duplicate detection meaningful.

[0048] Based on the above analysis, only by processing the host with reception anomalies first, and then detecting repeated host faults (i.e., the repeated fault detection counting time must be greater than the reception communication timeout delay), can a unique host be identified. Secondly, the above method for handling host faults is cumbersome in code and requires designing an appropriate host repeated fault repair time. Finally, we expect the remaining host to be a device with normal communication; that is, even if the device number is very low, a host with reception anomalies cannot be considered a host. Therefore, two principles can be set: 1. Ensure that there is only one and only one host on the bus; multiple hosts are not allowed, nor is the absence of a host; 2. The host is the dominant module; modules with communication anomalies cannot function as hosts.

[0049] Following the above principles and conventional practices: if a module with communication problems does not act as the host, the handling method is to remove it from the host role. However, in the process of other modules re-electing the host, if the local machine also participates, the result becomes uncertain; the local machine may ultimately still be elected as the host, resulting in an infinite loop. To ensure that a module with communication problems never becomes the host, it is prevented from ever participating in the election. That is, if the local machine experiences a reception problem, it actively stops its sending function, i.e., "real-time disconnection from communication." In other words, in this embodiment, if the host role is duplicated and one of the hosts experiences a reception problem, the sending function of the host with the reception problem is disabled, preventing it from ever participating in the election again. In this way, the normal host becomes the sole host, or the sole host is determined through a master-discovery process.

[0050] In this embodiment: 1. Since the host with abnormal reception disables its transmission function, it cannot send messages. Therefore, other charging modules on the bus will not be aware of the existence of this host with abnormal reception. All other charging modules that can be detected are those with normal reception and transmission functions. At this time, there is no need to design a complex host duplication detection. If host duplication occurs, the host can be determined directly based on the serial number. This greatly simplifies the operation process of host duplication detection in the prior art, and there is no need to design a host duplication detection fault counting time that must be greater than the reception communication timeout delay time, nor is there a need to design a suitable host duplication fault recovery time. 2. There are no hosts with abnormal reception and normal transmission on the bus. Once a host with abnormal reception occurs, it will naturally stop transmitting and will not interfere with the master search of other charging modules. In this way, a unique host can be quickly identified on the bus through simple operation, preventing system instability or paralysis.

[0051] It should be noted that the host reception error mentioned here refers to the charging module's inability to receive signals, not its inability to receive current sharing messages. The difference between peripheral reception error and current sharing reception error will be explained in detail below:

[0052] 1. Peripheral device reception error: This peripheral device is not receiving any messages, not just flow sharing messages, but also other messages. This indicates that the peripheral device reception may be interrupted, so disable the sending function.

[0053] 2. Current sharing reception error: This peripheral device cannot receive current sharing messages, and it is uncertain whether other messages can be received. In this case, reception is considered normal, and the sending function will not be disabled.

[0054] In this embodiment, the host reception error is a peripheral reception error, meaning the host cannot receive any messages.

[0055] The reason is as follows, taking current sharing between two charging modules as an example:

[0056] 1. Peripheral Device Reception Abnormality: If the first charging module experiences a complete peripheral device reception abnormality, it indicates a possible disconnection in peripheral device reception, and the transmission function will be disabled. The second charging module, if it cannot receive current sharing information but can receive other information, is considered to have normal reception and its transmission function will not be disabled. Once the first charging module regains its receiving capability, the transmission function can be reopened.

[0057] 2. Current Sharing Reception Abnormality: If the first charging module experiences a current sharing reception abnormality, its transmission function will be disabled. With only two charging modules on the bus, the second charging module, unable to receive current sharing information because the first module has disabled its transmission function, will also assume a communication abnormality and disable its transmission function. At this point, there is no current sharing information on the bus, and neither module can receive the other's current sharing information, thus preventing current sharing from ever occurring.

[0058] The above example uses two machines; the same principle applies to n machines. However, with n modules, the situation of perpetually uneven current distribution will only occur if the current distribution reception of the n-1th module is abnormal. Therefore, the reception abnormality mentioned here refers to the peripheral device reception abnormality. This ensures that when the host receives an abnormality, the transmission function is disabled, causing it to exit the master-finding operation, so as to quickly determine the unique host.

[0059] In one embodiment, when the master transmission fails, meaning the master cannot send messages but can still receive messages on the bus, neither the charging module itself nor any other module on the bus can detect the transmission failure. Under this premise, it can only be guaranteed that, regardless of whether the master or slave is involved, the master-slave lookup result of the master itself is given the highest priority in all circumstances. The master with the transmission failure uses its own master-slave lookup result for master-slave positioning. It should be noted that when the master transmission fails, other slaves consider the master to be disconnected and re-initiate the master-slave lookup. The master-slave lookup operation is real-time, meaning that in each loop, the master-slave lookup operation is performed first, followed by other operations.

[0060] Optional, see Figure 4 When the host receives a message from another device, it performs a master-slave search, prioritizing the master-slave result. The other devices are charging modules connected to the same CAN bus as the host. Each other device selects a master from the remaining devices through the master-slave search process.

[0061] The message here can be a master-finding message, the purpose of which is to re-find the master. The master-finding message includes the machine number of the machine sending the message. Each machine connected to the same CAN bus sends a master-finding message to the CAN bus. When the master receives a message sent by another machine, since a master-finding is performed again when a master exists, it can be determined that the master has experienced a transmission error. Of course, other errors may also occur. In this embodiment, the fault handling is described in detail based on a master transmission error. The master-slave determination of the local machine is given the highest priority. Other machines can be all slave machines or may include other masters.

[0062] The master-slave search result of the host can be determined based on the received message and the host's identification information. Therefore, when the host receives a message sent by another machine, it determines the master-slave search result of the host based on the message and the host's identification information; the master-slave operation is performed with the master-slave search result of the host as the highest priority.

[0063] The identification information for this machine can include all information used to identify the machine, such as its serial number. Generally, during the master-disciple search process, when determining the master, either the machine with the lowest serial number or the machine with the highest serial number can be designated as the master.

[0064] If other machines do not receive the current sharing message from the master within a preset time period, they consider the master to be disconnected and need to re-find the master. Here, the current sharing message includes current sharing information, i.e., the current information that the slaves should output, as instructed by the master. The master with the abnormal transmission and all slaves participate in the master-finding process. When the master receiving the message from another machine (i.e., the master with the abnormal transmission) has the smallest or largest machine number, it is still identified as the new master during the master-finding process; here, we define it as the first master. Among the other machines besides the master, one machine is selected from the others to serve as the second master through the master-finding process. In other words, when we prioritize the master-finding result of the master with the abnormal transmission, we determine that there are two masters connected to the same CAN bus: one master with an abnormal transmission and one normal master; the remaining machines are slaves. At this time, the first master, i.e., the master with the abnormal transmission, outputs current according to its own capacity, and the remaining current is distributed by the second master determined through the master-finding process and all slaves.

[0065] Here, the master-slave lookup result of the host that sent the abnormal message is given the highest priority. This means that a host other than the host that sent the abnormal message has determined a master through master-slave lookup, such as the second master. At this time, the host that sent the abnormal message will receive the flow sharing message sent by the second master. This flow sharing message includes the master-slave structure and flow sharing information. At this time, the host that sent the abnormal message needs to determine which one has the higher priority and then follow the instruction of that one. In this embodiment, the host that sent the abnormal message has the highest priority, so it is still the master, that is, the first master.

[0066] It should be noted that when all other machines are slaves, the operation is as follows: "When the machine number of the machine is the smallest or the machine number is the largest, the master search result of the machine is determined according to the message and the machine number of the machine, and the machine is determined to be the first master; the other machines select one machine from the other machines to be the second master."

[0067] When a host exists on another machine, host duplication occurs, for example, see [link to relevant documentation]. Figure 5 Application scenario where the host with the smallest machine number in the host fails to send data: There are more than 2 machines on the bus. Assume that machine 1 is the host and is running normally. However, a sudden situation occurs and machine 1 is disconnected from the bus. Then, the host competition is re-competed for, and machine 2 becomes the new host. After running for a period of time, communication of machine 1 is restored. However, machine 1 can only receive normally, but sending is abnormal.

[0068] The timing for resuming communication with Machine 1 is after the current master-slave search process is completed. Machine 1 remains the master. For machines 2-n, since Machine 1 re-enters and outputs current, the current output of machines 2-n becomes incorrect. However, machines 2-n cannot receive information from Machine 1 and therefore assume Machine 1 is non-existent. After resuming the master-slave search, machines 2-n send a master-slave message, and Machine 2 successfully competes for the master (the master is determined by the smallest machine number). Machine 1, upon receiving the master-slave message, also participates in the master-slave search. At this point, Machine 1's master-slave search result is still master, and its own result has the highest priority. Therefore, Machine 1 handles master-slave matters and does not comply with the control of Machine 2. Thus, Master 1 outputs current according to its own capacity, and the remaining current is distributed among Master 2 and all slave machines. In other words, machines 2 through n share the current, while machine 1 handles the main operation. However, if machine 1 fails to send information, it will not affect the current sharing of machines 2 through n. Ultimately, machine 1 outputs according to its own capacity, and the remaining current is handled by machines 2 through n through the current sharing mechanism. Therefore, although the main machine is not unique, it can simplify fault handling and ensure stable system operation even when there are duplicate main machines and one of them malfunctions.

[0069] In addition, the timing for the resumption of communication for Unit 1 is when the current master search process is not yet determined. In this case, Unit 1 will directly participate in the master search. Similarly, if the master search determines that Unit 1 is the master, it will output according to its own capacity. Among Units 2-n, Unit 2 is the master, and the remaining current will be handled by the current sharing of Units 2-n.

[0070] In one embodiment, when the machine number is neither the smallest nor the largest, based on the message and the machine number, the machine's master-slave assignment result is determined, and the machine performs the master-slave operation with the highest priority, i.e., the machine performs current sharing operation for the slaves according to the message. At this time, other machines can select one machine to act as the master through master-slave assignment; in this case, the master is determined to be the sole master. This sole master and all slaves are then current-sharing distributed according to current.

[0071] Other machines contain duplicate hosts; see [link to documentation]. Figure 6 Application scenario for the host with the largest serial number in the duplicate host to send abnormal messages: Host 1 is disconnected from the bus and then competes for the host again. Host 2 becomes the new host. After running for a period of time, communication of Host 1 is restored, but Host 2 has an abnormality. Only the transmission is abnormal, while the reception is normal.

[0072] If the host is duplicated and the host with the largest host number sends an abnormal message, the other hosts and all slaves will determine the host by searching for the master; the host with the largest host number that sent the abnormal message will be identified as the slave.

[0073] Since communication with machine 1 was restored, machine 2 experienced a transmission error during the master search process. Machines 1 and 3-n, unable to receive information from machine 2, assumed machine 2 did not exist. After the master search, machine 1 successfully competed for control and broadcast master control information, which machines 3-n obeyed. Machine 2 received information from machine 1 and considered it a duplicate master. Machine 2 then searched for a new master. Since machine 1 had the lowest machine number, machine 2 decided to withdraw from the master search and prioritized its own search result. Machine 2 obeyed machine 1's control and participated in the current sharing operation of machines 3-n, ultimately achieving current sharing for machines 1-n. The final master determined through the master search and all slaves were then distributed current according to current. Therefore, this system provides simple fault handling and stable operation even when there is a duplicate master and one of the masters experiences a transmission error.

[0074] This invention provides a fault handling method for a host machine. When the host detects a receiving anomaly, it disables its transmitting function, causing the host with the receiving anomaly to withdraw from the host election. Each slave machine, upon detecting the host's loss of connection, selects a new slave to act as the new host through a master-slave search. This simplifies fault handling and ensures stable system operation. When the host receives a message from another machine, it indicates a transmitting anomaly. The host then uses its own master-slave search result to determine its own master-slave position, ensuring that the master-slave search results of other machines are not affected. When the host with the transmitting anomaly is identified as the new host, it outputs current according to its capacity. The remaining current is distributed among the second host determined by the master-slave search and all slaves. When the host with the transmitting anomaly is identified as a slave, the current is distributed among the single new host determined by the master-slave search and all slaves. This method simplifies fault handling and ensures stable system operation.

[0075] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0076] The following are device embodiments of the present invention. For details not described in detail, please refer to the corresponding method embodiments described above.

[0077] Figure 7 A schematic diagram of a current sharing system for handling host failures according to an embodiment of the present invention is shown. For ease of explanation, only the parts related to the embodiment of the present invention are shown, and are described in detail below:

[0078] like Figure 7 As shown, a current sharing system for handling host failure includes: all devices connected to the same CAN bus, including host 701 and other devices 702;

[0079] Host 701 is used to disable the sending function of the local machine when an abnormality in receiving is detected.

[0080] Other units 702 are used to select a slave unit to act as the master unit after detecting that the master unit has lost connection. The other units are charging modules connected to the same CAN bus as the master unit.

[0081] In one possible implementation, the host 701 is used to detect local reception anomalies by detecting that the host 701 cannot receive any messages.

[0082] In one possible implementation, the host 701 is also used to perform a master search when it receives a message sent by another machine 702, and to perform master-slave positioning of the host with the master search result of the host as the highest priority.

[0083] In one possible implementation, the host 701 is configured to, upon receiving a message sent by another machine 702, determine the master-slave search result of the host based on the message and the host's own identification information; and perform master-slave operation with the master-slave search result of the host as the highest priority.

[0084] In one possible implementation, the identification information includes the machine number. When host 701 determines the master-finding result based on the message and its own identification information, it uses the information to:

[0085] When the machine number of the local machine is the smallest or the machine number is the largest, the host search result of the local machine is determined based on the message and the machine number of the local machine, and the local machine is determined to act as the first host.

[0086] Other machines 702 are used to select one of the other machines to serve as the second host through a master-finding process.

[0087] In one possible implementation, the host 701 is also used to output current according to its own capacity, and the remaining current is distributed by the second host and all slaves.

[0088] In one possible implementation, the identification information includes the machine number. When host 701 determines the master-finding result based on the message and its own identification information, it uses the information to:

[0089] When the machine number of the local machine is not the smallest or the largest, the master-slave result is determined based on the message and the machine number of the local machine, and the local machine is assigned to act as the slave machine.

[0090] Other machines 702 are used to select one machine from other machines to serve as the sole master through a master search.

[0091] One possible implementation also includes: a single master and all slaves sharing current according to the current.

[0092] The aforementioned host fault handling system includes: all devices connected to the same CAN bus, including the host and other devices; the host, used to disable its own transmission function when a receiving anomaly is detected, causing the host with the receiving anomaly to withdraw from the host election; and other devices, used to select a slave device to act as the host after detecting that the host has lost connection, through a master-slave search. This simplifies fault handling and ensures stable system operation. When the host receives a message from another device, it indicates a transmission anomaly. The host uses its own master-slave search result to determine its own master-slave position, ensuring that it does not affect the master-slave search results of other devices. When the host with the transmission anomaly is identified as the host, it outputs current according to its own capacity. The remaining current is distributed among the second host determined by the master-slave search and all slave devices. When the host with the transmission anomaly is identified as a slave, the current is distributed among the unique host determined by the master-slave search and all slave devices, achieving the effect of simple fault handling and stable system operation.

[0093] This invention also provides a charging pile that applies the current sharing system for handling host failures provided in any of the above embodiments, and has the beneficial effects of the current sharing system for handling host failures.

[0094] The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included within the protection scope of the present invention.

Claims

1. A method for troubleshooting a host computer, characterized in that, include: When the host detects an abnormality in its own reception, it disables the host's transmission function. The local reception error is a peripheral reception error; The detection of local reception anomalies includes: detecting that the local machine cannot receive any messages; After other machines detect that the host is disconnected, they select a slave machine from among the other machines to act as the host through a master search. The other machine is a charging module connected to the same CAN bus as the host. When the host resumes communication and receives data normally, but a transmission error occurs, upon receiving a message from another machine, the host performs a master lookup process, prioritizing the master lookup result for master-slave localization. This process includes: When the machine number of the local machine is the smallest or the largest, the master search result of the local machine is determined according to the message and the machine number of the local machine, and the local machine is determined to be the first master. Other machines select one machine from the other machines to be the second master through master search. When the machine number of the local machine is not the smallest or the largest, the master-slave result is determined based on the message and the machine number of the local machine, and the local machine is assigned to act as the slave machine; other machines select one machine from the other machines to act as the sole master machine through master-slave selection.

2. The host fault handling method according to claim 1, characterized in that, When the host receives a message from another machine, it performs a master-slave search, and uses the master-slave search result as the highest priority for master-slave localization, including: When a host receives a message from another machine, it determines the host's master-finding result based on the message and its own identification information. The master-slave operation is performed with the highest priority based on the master-slave search result of the local machine.

3. The host fault handling method according to claim 2, characterized in that, Also includes: The first host outputs current according to its own capacity, and the remaining current is distributed by the second host and all slaves.

4. The host fault handling method according to claim 2, characterized in that, Also includes: The single master and all slaves are current-equalized according to the current.

5. A current sharing system for handling host failures, characterized in that, include: All devices connected to the same CAN bus, including the master and at least one slave; The host is configured to disable the transmitting function of the host when a local receiving anomaly is detected; the local receiving anomaly is a peripheral receiving anomaly. The host is used to detect local reception abnormalities, specifically by detecting that the host cannot receive any messages. Other devices are used to select a slave device to act as the master device after detecting that the master device has lost connection. The other devices are charging modules connected to the same CAN bus as the master device. The host is also used to perform a master search when it receives a message sent by another machine after the host has resumed communication and the receiving is normal, but a transmission abnormality occurs. The host will then perform master-slave positioning with the master search result of the host as the highest priority. The host is further configured to determine, based on the message and the host's number, that the host will act as the first host when the host's number is the smallest or the host number is the largest. The other machines are also used to select one of the other machines to serve as the second host through a master-finding process; The host is also configured to determine, based on the message and the host's own number, that the host will act as a slave when the host's own number is not the smallest or not the largest. The other machines are also used to select one machine from the other machines to serve as the sole host through a master search.

6. A charging pile, characterized in that, The current sharing system for handling host failure described in claim 5 above is applied.

Images