Automatic charging control method based on charging robot, charging robot and system
By using a charging robot in a home charging scenario, which uses a robotic arm to control the insertion and removal of the charging gun, the burden and safety hazards caused by manual operation by users are solved, and the charging process is automated and continuous.
Patent Information
- Application Number
- CN202611421630.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-14
- Publication Date
- 2026-11-17
AI Technical Summary
In existing technologies, home charging relies on manual operation by the user, which has problems such as heavy operational burden, high risk of arcing when plugging and unplugging under load, and low degree of automation in the charging process.
A charging robot is used to fix the charging gun of the DC charging pile to the end of the robotic arm. The robotic arm controls the insertion, locking and pulling out of the charging gun. The system combines the status of the DC charging pile, vehicle data and the status of the charging robot to determine whether the conditions for starting charging are met, and collects images of the vehicle's charging port for precise docking.
It automates the charging connection process, eliminating the burden of manual operation for users, reducing the risk of electric arcs, and ensuring the safety and continuity of the charging process.
Smart Images

Figure CN123104444A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of automatic charging control technology, specifically to an automatic charging control method, charging robot, and system based on a charging robot. Background Technology
[0002] With the development of the new energy vehicle industry and the growth of market share, the convenience and intelligence of charging infrastructure are increasingly becoming key factors affecting user experience.
[0003] Currently, in home charging environments, existing technologies primarily employ manual charging, requiring users to manually handle the movement, positioning, insertion, removal, and termination of charging. During manual charging, users bear the burden of heavy charging cables, and manual insertion and removal under load may generate risks such as electric arcing and overheating. Furthermore, in adverse weather conditions such as rain, snow, high temperatures, and extreme cold, it is inconvenient for users to participate in the entire charging process, making it difficult to guarantee the safety and continuity of the charging process. Summary of the Invention
[0004] In view of this, this application aims to provide an automatic charging control method, charging robot and system based on a charging robot, so as to solve the problem that it is difficult to guarantee the safety and continuity of the charging process in traditional related technologies.
[0005] The first aspect of this application provides an automatic charging control method based on a charging robot, applied to a charging robot, wherein the charging gun of a DC charging pile is fixed to the end of the robotic arm of the charging robot; the method includes: receiving the DC charging pile status and vehicle data, and obtaining the vehicle parking position; upon receiving a charging request, determining whether the charging start conditions are met by combining the DC charging pile status, vehicle data, vehicle parking position, and charging robot status; if the charging start conditions are met, acquiring an image of the vehicle charging port; based on the vehicle charging port image, controlling the robotic arm to insert the charging gun into the vehicle charging port and locking the charging gun head; upon receiving a request to remove the charging gun, releasing the locking of the charging gun head, controlling the robotic arm to remove the charging gun from the vehicle charging port, and controlling the robotic arm to reset to the initial position.
[0006] In one possible implementation of this application, the vehicle data includes at least the charging port cover status and the vehicle gear position status; determining whether the charging start conditions are met includes: obtaining the sending end of the charging request; when the sending end is a vehicle, if preset conditions are met, it is determined that the charging start conditions are met; wherein, the preset conditions are: the charging port cover status is open, the charging request carries the plug-in command, the charging robot status is normal, the vehicle parking position is within the preset range of the robotic arm, the DC charging pile status is normal, and the vehicle gear position is P gear.
[0007] In one possible implementation of this application, the vehicle data also includes a vehicle identification number (VIN) and vehicle operating condition; the method further includes: when the sending end is the cloud, if the vehicle operating condition is a wake-up condition, and if the preset conditions are met, and the VIN carried in the charging request is consistent with the VIN in the vehicle data, then it is determined that the charging start condition is met; when the sending end is the cloud, if the vehicle operating condition is a sleep condition, and if the charging request carries a plug-in command, the charging robot is in a normal state, and the DC charging pile is in a normal state, then it is determined that the charging start condition is met.
[0008] In one possible implementation of this application, the vehicle charging port image includes a first vehicle charging port image and a second vehicle charging port image; correspondingly, according to the vehicle charging port image, controlling the robotic arm to insert the charging gun into the vehicle charging port includes: determining the three-dimensional coordinates of the vehicle charging port in the charging robot coordinate system according to the first vehicle charging port image; controlling the robotic arm to move to a preset distance from the vehicle charging port according to the three-dimensional coordinates; determining the position and orientation of the vehicle charging port according to the second vehicle charging port image; and controlling the robotic arm to insert the charging gun into the vehicle charging port according to the position and orientation.
[0009] In one possible implementation of this application, determining the position and orientation of the vehicle charging port based on the second vehicle charging port image includes: extracting the contour features of the vehicle charging port from the second vehicle charging port image; obtaining the similarity between the contour features and a preset standard vehicle charging port contour template; and if the similarity exceeds a preset threshold, determining the position and orientation of the vehicle charging port based on the contour features.
[0010] In one possible implementation of this application, controlling a robotic arm to insert a charging gun into a vehicle charging port based on position and orientation includes: determining multiple spatial key points for the movement of the robotic arm based on position and orientation; wherein the robotic arm includes multiple linear axes and multiple rotational axes; determining target motion parameters for each axis of the robotic arm based on the multiple spatial key points; and controlling the robotic arm to insert the charging gun into the vehicle charging port according to the target motion parameters for each axis.
[0011] In one possible implementation of this application, the target motion parameters of each axis of the robotic arm are determined based on multiple spatial key points, including: determining the target linear displacement value and uniform interpolation sequence of each linear axis, and the target angle value and smooth angle transition sequence of each rotation axis based on multiple spatial key points; generating the initial motion parameters of each axis based on the target linear displacement value, uniform interpolation sequence, target angle value and smooth angle transition sequence; and correcting the initial motion parameters of each axis according to the preset motion constraints of the robotic arm to obtain the target motion parameters of each axis.
[0012] In one possible implementation of this application, the method further includes: monitoring message data between the vehicle and the DC charging pile; identifying whether fault information exists based on the message data, the DC charging pile status, the vehicle data, and the charging robot status; if fault information is identified, obtaining the risk level of the fault information; and responding to the fault according to the response measures corresponding to the risk level.
[0013] In one possible implementation of this application, the method further includes: when fault information is detected, obtaining the fault stage in which the fault information occurred; and sending the fault information, fault stage, and risk level to the cloud so that the cloud can provide operation and maintenance management notifications.
[0014] The second aspect of this application provides a charging robot, comprising: a robot body, a robotic arm, and a controller; wherein the robotic arm is mounted on top of the robot body; cameras are mounted on the top of the robot body and at the end of the robotic arm; an adapter socket is provided inside the robot body; a DC charging gun is fixed to the end of the robotic arm via the adapter socket; and the controller is electrically connected to the robotic arm and the camera respectively, for executing an automatic charging control method based on the charging robot as described in the first aspect and possible implementations thereof.
[0015] A third aspect of this application provides a charging robot, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, the computer program being executed by the at least one processor to cause the at least one processor to perform an automatic charging control method based on the charging robot, as described in the first aspect and possible implementations thereof.
[0016] A fourth aspect of this application also provides an automatic charging control system based on a charging robot, comprising: a DC charging pile, a cloud platform, and a charging robot; the cloud platform is communicatively connected to both the DC charging pile and the charging robot; wherein the charging gun of the DC charging pile is fixed to the end of the robotic arm of the charging robot; the DC charging pile is used to send its status to the cloud platform and to interact with a vehicle for charging; wherein the vehicle is an external device that interacts with the DC charging pile and the charging robot, rather than a component of the system; the cloud platform is used to receive the DC charging pile status sent by the DC charging pile and to send the DC charging pile status, charging request, and gun removal request to the charging robot; the charging robot is used to execute the automatic charging control method based on the charging robot as described in the first aspect and possible implementations thereof.
[0017] In one possible implementation of this application, the cloud is used to send a stop charging command to the DC charging pile when it receives a stop charging request from the user terminal; and only after receiving a stop charging status from the DC charging pile will it send a gun removal request to the charging robot; the DC charging pile is used to cut off the output current and send a charging stop message to the vehicle after receiving the stop charging command; and send a stop charging status to the cloud after receiving a confirmation message from the vehicle.
[0018] The fifth aspect of this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement an automatic charging control method based on a charging robot, as described in the first aspect and possible implementations thereof.
[0019] The sixth aspect of this application provides a computer program product, comprising: a computer program that, when executed by a processor, implements an automatic charging control method based on a charging robot, as described in the first aspect and possible implementations thereof.
[0020] This application provides an automatic charging control method, charging robot, and system based on a charging robot. In this method, upon receiving a charging request, the system combines the DC charging pile status, vehicle data, vehicle parking position, and charging robot status to determine if the conditions for starting charging are met. If the conditions are met, an image of the vehicle's charging port is acquired. Based on the image, a robotic arm with a fixed charging gun is controlled to insert the charging gun into the vehicle's charging port and lock the charging gun's nozzle, establishing a physical charging connection between the vehicle and the DC charging pile. Upon receiving a request to remove the charging gun, the locking of the charging gun's nozzle is released, and the robotic arm is controlled to remove the charging gun from the vehicle's charging port and return it to its initial position. This allows the charging robot to handle the insertion and removal of the charging gun and the locking of the nozzle, avoiding the risks of manual operation of the heavy DC charging cable and the arcing caused by manual insertion and removal under load. It achieves automated charging operations from charging request to charging completion and gun removal / reset, ensuring the safety and continuity of the charging process. Attached Figure Description
[0021] To more clearly illustrate the technical solutions in the specific embodiments or related technologies of this application, the drawings used in the description of the specific embodiments or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0022] Figure 1 This is a schematic diagram illustrating an application scenario of the automatic charging control method based on a charging robot provided in the embodiments of this application.
[0023] Figure 2 A flowchart illustrating the automatic charging control method based on a charging robot provided in this application embodiment. Figure 1 .
[0024] Figure 3 A flowchart illustrating the automatic charging control method based on a charging robot provided in this application embodiment. Figure 2 .
[0025] Figure 4 This is a schematic diagram of the hardware structure of the charging robot provided in an embodiment of this application. Detailed Implementation
[0026] 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.
[0027] In home charging scenarios for new energy vehicles, the commonly used technical solution for establishing a charging connection between the vehicle and a DC charging station is manual operation of the DC charging gun by the user. Specifically, this solution involves the user removing the charging gun from the DC charging station, aligning the nozzle with the vehicle's charging port, and inserting it. Once a physical connection is established, the DC charging station and vehicle negotiate and begin charging. After charging is complete, the user removes and replaces the charging gun. Its basic working principle relies on the user's manual operation to complete the actions of removing, aligning, inserting, and removing the charging gun. This method is widely adopted because it eliminates the need for additional automatic actuators between the charging station and the vehicle, resulting in a relatively simple system structure that is easy to implement in limited spaces such as home parking spaces.
[0028] However, this solution's performance is less than ideal when applied to scenarios such as underground parking spaces, rainy or snowy weather, or when users have limited physical strength. A major contradiction lies in the fact that, to maintain the simplicity of the charging facility structure, the solution omits the automatic plugging and unplugging mechanism, but the operation of the charging gun still requires direct user intervention. This inevitably creates the risk of arcing during plugging and unplugging under load and increases the user's operational burden. For example, in a home charging scenario, when a user removes the DC charging gun from the charging station and inserts it into the vehicle's charging port, due to the weight of the charging cable and its high bending stiffness, the user needs to simultaneously overcome cable resistance and keep the gun head aligned. At the moment the charging gun contacts or separates from the vehicle's charging interface, if there is voltage or current in the circuit, an arc will be generated, manifesting as interface terminal burning or charging interruption.
[0029] Through in-depth analysis, the inventors discovered that the root cause of the above contradictions lies in the fact that the charging operation in the relevant technologies relies on manual completion by the user and lacks continuous control over the automatic alignment, insertion, locking, and removal of the charging gun. At the same time, before starting charging, there is a lack of coordinated judgment on the status of the vehicle's charging port cover, gear position, vehicle identification number, vehicle location, and the status of the DC charging pile and charging robot, making it impossible to eliminate unsafe conditions before performing the insertion action.
[0030] To overcome the aforementioned contradictions, this application proposes the following technical concept: The charging gun of the DC charging station is fixed to the end of the robotic arm of a charging robot, with the robotic arm controlling the insertion and removal of the charging gun. Upon receiving a charging request, the system determines whether the conditions for initiating charging are met by considering the DC charging station status, vehicle data, vehicle parking position, and the charging robot status. If the conditions are met, an image of the vehicle's charging port is captured. Based on this image, the robotic arm is controlled to insert the charging gun into the vehicle's charging port and lock the charging gun head, establishing a physical charging connection between the vehicle and the DC charging station for charging negotiation and charging. Upon receiving a request to remove the charging gun, the locking of the charging gun head is released, and the robotic arm is controlled to remove the charging gun from the vehicle's charging port and return it to its initial position. This solves the problems of high user workload, safety hazards associated with plugging and unplugging under load, and low automation in home charging scenarios, achieving automatic execution of charging connection establishment and termination.
[0031] Figure 1 This diagram illustrates an application scenario of the automatic charging control method based on a charging robot provided in this application. (Reference) Figure 1 The scenario includes: cloud platform 10, charging robot 20, vehicle 30, and DC charging pile 40. Cloud platform 10 is communicatively connected to charging robot 20 and DC charging pile 40, and vehicle 30 is communicatively connected to charging robot 20 and DC charging pile 40.
[0032] In a real-world deployment environment, the cloud platform 10 receives the DC charging pile status reported by the DC charging pile 40 and forwards the DC charging pile status to the charging robot 20. The cloud platform 10 is also used to send charging requests and gun removal requests to the charging robot 20.
[0033] Vehicle 30 is used to open the vehicle charging port cover and send charging requests and vehicle data to the charging robot 20. Vehicle 30 also communicates with the DC charging station 40 via CAN to negotiate charging and exchange charging status.
[0034] The charging robot 20 includes a robot body 201, a robotic arm 202, and a controller 203. The robotic arm 202 is mounted on top of the robot body 201. A camera 204 is mounted on the top of the robot body 201 and at the end of the robotic arm 202. An adapter socket 205 is provided inside the robot body 201. The charging gun of the DC charging station is fixed to the end of the robotic arm 202 through the adapter socket 205. The controller 203 is electrically connected to the robotic arm 202 and the camera 204.
[0035] In this embodiment, an adapter-type charging gun connection scheme is adopted. The charging gun body of the DC charging pile 40 is housed inside the robot body 201, and power transfer is achieved through the adapter socket 205. The cable from the adapter socket 205 to the charging gun at the end of the robotic arm 202 is led out to the robotic arm through the cable channel.
[0036] In this embodiment, when the robotic arm 202 moves, it can carry the charging gun from its initial position to the vicinity of the vehicle charging port, and complete the docking and disconnection of the charging gun within the operating space in front of the vehicle charging port.
[0037] The system uses camera 204 to capture images of the vehicle's charging port. Controller 203, based on received vehicle data and the DC charging pile status obtained from the cloud 10, combined with its own status and the vehicle's parking position, controls the robotic arm 202 to perform the insertion, locking, removal, and reset actions of the charging gun. Controller 203 is used to implement an automated charging control method based on the charging robot.
[0038] DC charging pile 40 outputs DC charging current to vehicle 30 based on the charging negotiation result between vehicle 30 and DC charging pile 40.
[0039] The communication links between the aforementioned terminals can be wired or wireless, depending on the deployment conditions of the charging site. The connections between the cloud platform 10, the charging robot 20, the vehicle 30, and the DC charging pile 40 constitute the implementation environment for the automatic charging control method.
[0040] Figure 2 A flowchart illustrating the automatic charging control method based on a charging robot provided in this application embodiment. Figure 1 The execution entity in this embodiment can be... Figure 1 The charging robot in the illustrated embodiment has a DC charging gun fixed to the end of its robotic arm. Figure 2 As shown, the method includes: S201: Receives DC charging pile status and vehicle data, and obtains the vehicle's parking location.
[0041] The status of the DC charging pile is reported to the cloud at regular intervals, and then sent to the charging robot at regular intervals from the cloud; vehicle data can be sent to the charging robot from the vehicle via Bluetooth.
[0042] The vehicle data may include information such as vehicle type, gear position, and vehicle identification number (VIN).
[0043] In this embodiment, during the preparation stage before charging, the charging robot acquires the status of the DC charging pile and vehicle data, providing a data basis for subsequent judgment on whether the conditions for starting charging are met. This ensures that the charging process is started only when sufficient information is available, avoiding safety risks caused by blind operation.
[0044] In this embodiment, after parking is completed by a driver or autonomous driving system, a camera mounted on top of the charging robot captures an image of the vehicle from the charging port side. Based on this image, the parking position is determined. The parking position is used to determine whether the vehicle is within the operable range of the robotic arm, preventing mechanical damage or docking failure caused by the robotic arm forcibly moving beyond its travel range.
[0045] Optionally, the charging robot can feed back the status of the robotic arm and vehicle data to the cloud for monitoring or display.
[0046] S202: Upon receiving a charging request, determine whether the conditions for starting charging are met by combining the status of the DC charging pile, vehicle data, vehicle parking position, and charging robot status.
[0047] In this embodiment, charging requests can originate from the vehicle (local control) or from the cloud (remote control). Charging requests sent by the vehicle are initiated by the user through the in-vehicle system after the charging robot and vehicle have successfully completed Bluetooth pairing and authentication. Charging requests sent from the cloud can be initiated remotely by the user through a mobile application. Supporting charging requests from multiple sources allows users to initiate charging locally near the vehicle via the in-vehicle system or remotely via a mobile application, improving the flexibility and convenience of charging operations.
[0048] Optionally, if the charging robot and vehicle authentication fails, an abnormal fault handling process will be initiated, which will be described in subsequent embodiments.
[0049] The charging robot's status can include the status of each joint of the robotic arm, the working status of sensors, and the status of communication links. The charging robot confirms that its subsystems are working properly through self-checking, ensuring that the robotic arm has complete motion and perception capabilities before performing the gun insertion action, and avoiding secondary damage caused by performing the operation when it has a malfunction.
[0050] The vehicle data includes at least the status of the charging port cover, the vehicle identification number, the vehicle gear status, and the vehicle operating condition.
[0051] In this embodiment, if the conditions for starting charging are not met, an abnormal fault handling process will be initiated. The fault handling process will be described in subsequent embodiments.
[0052] Specifically, the sender of the charging request is obtained; if the sender is a vehicle, and the preset conditions are met, it is determined that the conditions for starting charging are met.
[0053] In this embodiment, after receiving a charging request, the charging robot first obtains the sender of the charging request to distinguish whether the source of the charging request is a vehicle or the cloud, so as to adopt different judgment logic for different sources, taking into account both operational convenience and safety.
[0054] In this embodiment, when the sending end is a vehicle, i.e. in a local control scenario, the charging robot makes a judgment based on preset conditions without the need for additional identity verification steps, thus balancing ease of operation and safety.
[0055] Optionally, when the sending end is the cloud, if the vehicle is in a wake-up state and the preset conditions are met, and the vehicle identification number carried in the charging request is consistent with the vehicle identification number in the vehicle data, then the charging start conditions are determined to be met.
[0056] In this embodiment, when a charging request is initiated remotely in the cloud and the vehicle is in a wake-up state, in addition to meeting preset conditions, it is also necessary to verify whether the VIN code carried in the charging request is consistent with the VIN code actually returned by the vehicle, so as to prevent the wrong vehicle from being charged in the remote control scenario and improve the security and accuracy of remote control.
[0057] Optionally, when the sending end is the cloud, if the vehicle is in a dormant state, and the charging request carries a plug-in command, the charging robot is in a normal state, and the DC charging pile is in a normal state, then the conditions for starting charging are determined to be met.
[0058] In this embodiment, when a charging request is remotely initiated from the cloud and the vehicle is in a dormant state, since the vehicle is not awakened and Bluetooth is not connected, information such as the charging port cover status and vehicle gear position cannot be obtained. Therefore, the charging gun operation can be started by verifying only the charging gun command, robot status, and DC charging pile status. After the vehicle is awakened by the charging gun, subsequent identity verification is performed, which balances operability and security in the dormant scenario.
[0059] The preset conditions mentioned above are: the charging port cover is open, the charging request carries the plug-in command, the charging robot is in normal condition, the vehicle is parked within the preset range of the robotic arm, the DC charging pile is in normal condition, and the vehicle is in P gear.
[0060] Among them, the preset conditions comprehensively verify multiple dimensions such as the physical state of the charging port, the validity of the command, the health status of the device, the spatial accessibility, and the safety status of the vehicle, so as to fully ensure the safety of charging start-up.
[0061] In this embodiment, if the vehicle's parking position is not within the preset range of the robotic arm, the vehicle's relative position can be fed back to the vehicle so that the vehicle can adjust its parking position.
[0062] S203: If the conditions for starting charging are met, then acquire an image of the vehicle's charging port.
[0063] In this embodiment, the image of the vehicle charging port can be obtained by capturing images of the vehicle charging port using a camera mounted on the charging robot. By capturing images of the vehicle charging port, the camera provides data for subsequent image-based charging port identification and localization, enabling the charging robot to accurately locate and dock with the vehicle's charging port.
[0064] S204: Based on the image of the vehicle charging port, control the robotic arm to insert the charging gun into the vehicle charging port and lock the head of the charging gun.
[0065] Once the charging gun is locked, a physical charging connection is established between the vehicle and the DC charging pile, allowing the DC charging pile and the vehicle to negotiate and charge.
[0066] The vehicle charging port image includes a first vehicle charging port image and a second vehicle charging port image.
[0067] Among them, the first vehicle charging port image is an image of the vehicle charging port area captured by the charging robot at a relatively long distance through a camera mounted on the top of the robot body, with a wide-angle lens (field of view ≥120°) and a resolution ≥1 million pixels. It is used to quickly search and roughly locate the vehicle charging port within a 1.5m range around the charging robot. The second vehicle charging port image is a close-up image captured by a camera mounted at the end of the robotic arm after the charging port location has been roughly determined. The robotic arm moves to a position 30cm in front of the charging port. Compared to the first vehicle charging port image, this image has higher resolution and less angular distortion, enabling more precise extraction of the charging port's contour features and posture information, providing high-precision positioning data for accurate charging port insertion.
[0068] In this embodiment, the three-dimensional coordinates of the charging port can be determined first through the first vehicle charging port image, and the robotic arm can be moved to a preset distance. Then, the position and orientation of the charging port can be accurately determined through the second vehicle charging port image to complete the precise insertion of the charging gun. The two-stage visual positioning strategy of "coarse positioning first, then fine docking" improves the accuracy and success rate of docking between the charging gun and the vehicle charging port.
[0069] In this embodiment, the charging robot continuously monitors the docking status (including insertion force feedback, position deviation, robotic arm movement progress, etc.) to ensure that the charging gun and charging interface can be safely and reliably connected physically, and sends a docking completion signal back to the cloud and the vehicle.
[0070] Specifically, step S204 includes Sa1~Sa4: Sa1: Determine the three-dimensional coordinates of the vehicle charging port in the charging robot coordinate system based on the first vehicle charging port image.
[0071] In this embodiment, the three-dimensional spatial coordinates of the vehicle charging port relative to the charging robot can be calculated based on the standard-sized similar triangle ranging principle, combined with the known standard size of the vehicle charging port and the imaging size in the image. This allows the charging robot to convert the image information into a spatial target position that the robotic arm can execute, providing a precise coordinate reference for the subsequent directional movement of the robotic arm.
[0072] Sa2: Based on the three-dimensional coordinates, control the robotic arm to move to the preset distance of the vehicle's charging port.
[0073] In this embodiment, the robotic arm moves to a preset distance before inserting itself, leaving room for adjustment for precise positioning at close range and avoiding the risk of collision caused by positioning errors at long distance. At the same time, it enables the second image acquisition to obtain a higher resolution image of the charging port at a closer distance.
[0074] Optionally, the preset distance can be 30cm, or it can be adjusted according to the actual situation.
[0075] Sa3: Determine the position and orientation of the vehicle charging port based on the second vehicle charging port image.
[0076] Specifically, the contour features of the vehicle charging port are extracted from the second vehicle charging port image; the similarity between the contour features and the preset standard vehicle charging port contour template is obtained; if the similarity exceeds the preset threshold, the position and orientation of the vehicle charging port are determined based on the contour features.
[0077] In this embodiment, before extracting contour features, the second vehicle charging port image can be preprocessed, including image grayscale conversion, Gaussian filtering for noise reduction, and adaptive threshold segmentation, to enhance the grayscale difference between the target and the background and mitigate the unevenness of the image caused by strong light, dark light, and shadows. Subsequently, an edge detection algorithm captures the target edge lines, and a contour filtering mechanism selects closed contours that meet the conditions based on geometric constraints such as the perimeter, area, aspect ratio, and closure degree of the vehicle charging port. Through image preprocessing and contour filtering based on geometric constraints, effective contour features of the vehicle charging port can be stably extracted even in complex environments with uneven lighting and noise, filtering out fragmented interference edges and invalid contour segments, providing high-quality input data for subsequent template matching.
[0078] Then, a pre-set standard vehicle charging port outline template is used. This template can be a built-in national standard DC charging port outline template, storing standardized outline geometric parameters, internal and external structural proportions, relative positions of holes, and other core feature parameters. It enables accurate verification based on the fixed geometric features of the national standard charging port, ensuring the standardization and consistency of the recognition results. Similarity assessment can be performed comprehensively across multiple dimensions, including outline shape similarity, geometric proportion deviation, and structural correspondence. Compared to single-dimensional matching, this multi-dimensional similarity assessment provides a more comprehensive verification of whether the target outline conforms to the standard charging port characteristics, reducing the probability of false recognition and improving the robustness of the recognition.
[0079] In this embodiment, a similarity threshold is set as the criterion for successful recognition. This ensures that subsequent position and pose calculations are only performed when the contour features highly match the standard template, avoiding incorrect gun insertion actions in cases of incomplete contours, occlusion, or false detections, thus ensuring operational safety. When the similarity does not exceed the preset threshold, target recognition can be determined as a failure, and repositioning or reporting an anomaly can be performed.
[0080] Furthermore, for incomplete, occluded, deformed, or blurred contours due to reflections, contour completion algorithms and feature interpolation verification can be used to repair them before matching, adapting to unconventional working conditions such as slight occlusion and uneven lighting. The contour completion algorithm and feature interpolation verification enable stable target recognition even under non-ideal conditions such as slight occlusion or blurred reflections at the charging port, expanding the range of applicable scenarios and solving the problem of missed or false detections by ordinary recognition algorithms under unconventional conditions.
[0081] Sa4: Based on position and orientation, control the robotic arm to insert the charging gun into the vehicle's charging port.
[0082] Specifically, based on position and orientation, multiple spatial key points for the movement of the robotic arm are determined; the robotic arm includes multiple linear axes and multiple rotational axes; based on the multiple spatial key points, the target motion parameters of each axis of the robotic arm are determined; according to the target motion parameters of each axis, the robotic arm is controlled to insert the charging gun into the vehicle's charging port.
[0083] In this embodiment, the charging robot determines multiple spatial key points for the movement of the robotic arm based on the position and orientation of the vehicle's charging port, and determines the target motion parameters for each axis accordingly. The position and orientation information of the vehicle's charging port is converted into coordinated motion commands for each axis of the multi-degree-of-freedom robotic arm, enabling the charging gun to be accurately inserted into the charging port along the planned path, ensuring the accuracy and stability of the insertion action.
[0084] Among them, multiple spatial key points can include the Cartesian coordinates and attitude information of the starting point, intermediate transition points and the ending point, which are used to define the motion trajectory of the robotic arm from the current position to the vehicle charging port, so that the motion trajectory of the robotic arm has a clear path planning, avoiding the collision risk that may be caused by the robotic arm making unconstrained motion directly from the current position to the target position, and providing a discretized trajectory reference for subsequent kinematic calculation and smooth interpolation.
[0085] The robotic arm can be a five-degree-of-freedom robotic arm, including two linear degrees of freedom (such as a vertical lifting guide and a horizontal translation guide) and three rotational degrees of freedom (such as two horizontal rotary joints and one pitch joint). The linear axis enables the end effector to translate and position itself in space, while the rotary axis enables flexible adjustment of the end effector's posture. Together, they allow the charging gun to reach the spatial location of the vehicle's charging port and dock with the correct posture, meeting the requirements of positioning accuracy and posture flexibility in automatic charging scenarios.
[0086] In this embodiment, the charging robot uses kinematic calculations to decompose the Cartesian coordinates and orientation of multiple spatial key points into target motion quantities for each axis, thereby determining the target motion parameters for each axis of the robotic arm. This process realizes the mapping from the task space (Cartesian coordinates) to the joint space (motion parameters for each axis), enabling the robotic arm controller to directly drive the joints to move in coordination according to the motion parameters for each axis.
[0087] In this embodiment, the process of determining the target motion parameters for each axis can be further refined.
[0088] Specifically, based on multiple spatial key points, the target linear displacement value and uniform interpolation sequence of each linear axis, as well as the target angle value and smooth angle transition sequence of each rotation axis, are determined; based on the target linear displacement value, uniform interpolation sequence, target angle value, and smooth angle transition sequence, the initial motion parameters of each axis are generated; according to the preset motion constraints of the robotic arm, the initial motion parameters of each axis are corrected to obtain the target motion parameters of each axis.
[0089] In this embodiment, the uniform interpolation sequence can be a position sequence generated by high-density uniform interpolation of linear axis displacement. This ensures uniform motion of the linear axis, avoids mechanical vibration caused by sudden speed changes, and ensures smooth and vibration-free movement of the charging gun during translation. The smooth angle transition sequence can be an angle sequence generated by smoothing the angle change of the rotary axis. This eliminates the jitter and impact during the start and stop of the rotary axis, allowing the angular velocity of the rotary axis to change smoothly during start and stop, eliminating start-stop impact and jitter, and preventing positional deviation of the charging gun end due to sudden acceleration and deceleration of the rotary axis. Alternatively, the linear axis and the rotary axis adopt differentiated interpolation processing strategies: the linear axis focuses on uniform speed and no jitter, while the rotary axis focuses on smooth start and stop without impact. This allows each axis to work in its optimal motion mode, achieving high precision and no jitter in the trajectory of the robotic arm end effector as a whole, and improving the success rate of charging gun docking.
[0090] Subsequently, the charging robot integrates the interpolation results of the linear and rotation axes into a set of initial motion parameters for each axis based on the target linear displacement value, uniform interpolation sequence, target angle value, and smooth angle transition sequence, thereby generating the initial motion parameters for each axis.
[0091] After generating the initial motion parameters for each axis, the charging robot corrects these parameters according to the pre-defined motion constraints of the robotic arm to obtain the target motion parameters for each axis. These pre-defined motion constraints may include speed limits, acceleration limits, and travel limits for each axis. Correcting the initial motion parameters according to these pre-defined constraints ensures that the speed, acceleration, and travel of each axis are within safe ranges, preventing mechanical damage or safety accidents caused by overspeed, over-acceleration, or over-travel, while also eliminating speed jumps and acceleration shocks.
[0092] Optionally, for a robotic arm containing multiple similar rotary axes (such as two horizontal rotary joints), preset motion constraints may also include angle distribution and rate coordination constraints among the multiple similar rotary axes to avoid overloading of a single joint. Coordination constraints among multiple similar rotary axes ensure that angle changes are reasonably distributed among the multiple joints, preventing a single joint from bearing excessive rotation angles or angular velocities that could lead to overload, thus extending joint lifespan and improving motion smoothness.
[0093] In this embodiment, the target motion parameters of each axis are verified (accuracy, consistency and compliance). After the verification is passed, the target motion parameters of each axis are converted into pulse commands and synchronously sent to each axis driver to drive each axis to move synchronously and collaboratively according to the target motion parameters. This ensures that the end effector of the robotic arm (charging gun) moves smoothly along the planned trajectory and is accurately inserted into the charging port, avoiding trajectory deviation or jitter caused by uncoordinated movement of each axis.
[0094] In this embodiment, after the charging gun is inserted into the vehicle's charging port, the charging robot locks the gun head. The gun head locking can be achieved through an electric cylinder locking mechanism. After the gun head is locked, a physical charging connection is established between the vehicle and the DC charging station, allowing for charging negotiation and charging between the DC charging station and the vehicle. The charging negotiation can be based on the communication protocols specified in national standards GB / T 18487.1-2023 and GB / T 27930-2023 for DC charging parameters. This enables the vehicle and the DC charging station to negotiate charging parameters and initiate charging according to the standard communication protocol, achieving an orderly connection between the robotic arm operation and the charging protocol process, ensuring the standardization and compatibility of the charging process.
[0095] In this embodiment, the charging robot can feed back the status of its robotic arm to the cloud, reporting status code 01: plugging in, and the cloud can simultaneously display that the robotic arm is plugging in, for background monitoring, user APP status display, etc.; it can also feed back the status of its robotic arm to the vehicle: reporting status code 01: plugging in, informing the vehicle that it is currently performing the plugging action; and sending the progress of the robotic arm's movement, the position and posture of the vehicle's charging port, and the dust plug recognition status to the vehicle.
[0096] S205: Upon receiving a request to remove the charging gun, release the locking mechanism of the charging gun head, control the robotic arm to remove the charging gun from the vehicle's charging port, and control the robotic arm to return to its initial position.
[0097] In this embodiment, the request to unplug the charging gun can be sent from the cloud after charging is completed. After charging is completed, the gun head lock is automatically released, the charging gun is unplugged, and the robotic arm is reset to the initial position, completing the final step of the entire charging process. This makes the entire charging service, from plugging in the gun to unplugging and returning it to its original position, completely automated without user intervention.
[0098] In this embodiment, the vehicle and the DC charging station communicate via a Direct Current Controller Area Network (DC CAN) bus. An adapter cable is added to the DC CAN bus, and the charging robot obtains DC CAN message data through this adapter cable. Upon receiving a disconnect request, the robot checks the DC CAN message data to confirm that charging has truly stopped and the high voltage has been released, then controls the CC1 pin to disconnect. CC1 is the connection confirmation signal pin on the charging gun. The charging robot will only disconnect CC1 after the high voltage has been completely de-energized.
[0099] As described above, upon receiving a charging request, the system combines the DC charging pile status, vehicle data, vehicle parking position, and charging robot status to determine if the conditions for starting charging are met. If the conditions are met, an image of the vehicle's charging port is captured. Based on this image, a robotic arm with a fixed charging gun is controlled to insert the charging gun into the vehicle's charging port and lock the gun's nozzle, establishing a physical charging connection between the vehicle and the DC charging pile. Upon receiving a request to remove the charging gun, the locking of the gun's nozzle is released, and the robotic arm is controlled to remove the charging gun from the vehicle's charging port and return it to its initial position. This automated charging process, from requesting a charging request to completion and resetting the gun, is handled by the charging robot, eliminating the need for manual operation of the heavy DC charging cable and the risk of arcing from manual insertion / removal under load. This ensures the safety and continuity of the charging process.
[0100] Figure 3 A flowchart illustrating the automatic charging control method based on a charging robot provided in this application embodiment. Figure 2 Based on the above embodiments, this embodiment describes the faults and fault handling during the automatic charging process, as detailed below: S301: Monitors message data between vehicles and DC charging piles.
[0101] In this embodiment, the charging robot monitors the signals of the DC controller local area network bus between the DC charging pile and the vehicle in real time, and obtains information such as charging status, charging voltage, and charging current. It can obtain real-time status information during the charging process in a timely manner, providing a data source for fault identification and ensuring that abnormal situations can be detected in a timely manner.
[0102] S302: Identify whether there is fault information based on message data, DC charging pile status, vehicle data, and charging robot status.
[0103] In this embodiment, fault information may include, but is not limited to: communication timeout or interruption, robot docking failure, insulation detection anomaly, charging overvoltage / overcurrent / overtemperature, charging gun not properly returned to its position, charging port obstruction or the presence of a dust plug, and vehicle parking outside the docking range. Comprehensive fault identification using multi-terminal status information can cover various abnormal operating conditions that may occur throughout the entire charging process, ensuring the comprehensiveness and timeliness of fault detection.
[0104] Specifically, it checks whether fault codes are carried in the message data, DC charging pile status, vehicle data, and charging robot status.
[0105] In this embodiment, a 4-digit code is used to uniformly identify faults, with the encoding format being XYAB. X (thousands digit) represents the fault category: divided by module / fault type, with values from 1 to 5; Y (hundreds digit) represents the fault level: 0 = warning, 1 = level 1 alarm, 2 = level 2 alarm; AB (tens digit + units digit) represents the fault sequence number: 01-99, the fault number under the same fault level or fault category.
[0106] Among them, fault category 1 corresponds to hardware faults, including joint drive, end effector, and auxiliary equipment (joints, motors, gun heads, electronic locks, automatic doors, emergency stops, and limit switches, etc.); fault category 2 corresponds to motion control faults, including abnormal movement, alignment, patrol, aiming, protection position, and inability to reach motion commands, etc.; fault category 3 corresponds to charging system faults, including charging pile faults, abnormal CC1 charging signals, and abnormal charging start / stop, etc.; fault category 4 corresponds to communication and system faults, including abnormal communication of drive boards, robotic arms, Bluetooth, and ultrasound, as well as abnormal system status of power supply, battery, heating, start / stop, and self-recovery, etc.; fault category 5 corresponds to perception and recognition faults, including abnormalities in charging port or gun head recognition, image recognition, and vehicle detection.
[0107] S303: If fault information is detected, obtain the risk level of the fault information.
[0108] In this embodiment, if a fault code is detected, it indicates that fault information exists.
[0109] In this embodiment, the fault level directly maps to the risk level. A warning corresponds to low risk, and the response is: no action is taken, only the alarm information is recorded, and no operational restrictions are imposed; a level 1 alarm corresponds to medium risk, and the response is: the current action is suspended, and operation can continue after manual confirmation or fault recovery; a level 2 alarm corresponds to high risk, and the response is: operation is stopped immediately, and no action is allowed to be performed until the fault is recovered.
[0110] For example, the fault codes for low risk (warning, Y=0) are: 1001 (abnormal tension of robotic arm rope), 1002 (malfunction of insulated cabin door), 2001 (instability during inspection), 2002 (excessive number of robotic arm inspection movements), 2003 (excessive number of robotic arm inspection photos), 2004 (robotic arm inspection cannot find target), 2011 (instability during aiming), 2012 (excessive number of pre-aiming photos, unable to locate), 2013 (unable to find target during aiming), 2021 (...). The following are some of the following alarm codes: 1) Robotic arm not in standby position before returning to protection position; 2) Robotic arm not in protection position before exiting protection position; 3) Charging pile door opening alarm; 4) Abnormal charging start; 5) Abnormal charging end; 6) Abnormal manual stop by user; 7) Incorrect plug / unplug gun command; 8) Loss of self-reset inspection angle; 9) Self-recovery completed after fault; 10) Parking angle too large; 11) Distance between vehicles too far; 2) Distance between vehicles too close; and 3) Distance between vehicles too close.
[0111] For example, the fault codes for medium risk (Level 1 alarm, Y=1) are: 1101 (abnormal temperature of the first joint), 1102 (abnormal temperature of the second joint), 1103 (abnormal temperature of the third joint), 1104 (abnormal temperature of the fourth joint), 1105 (abnormal temperature of the fifth joint), 1111 (robotic arm emergency stop triggered), 1112 (electronic lock unlocking failure), 1113 (electronic lock cancellation unlocking failure), 1114 (tool center point) Point (TCP) not engaged), 1115 (gun head not disconnected from TCP), 2101-2104 (unable to reach limit / travel position during inspection), 2111-2117 (cannot reach pre-aiming position / touches limit), 2121-2124 (cannot reach or touch limit position for alignment estimation), 2131 (abnormal self-test before gun insertion), 2132-2136 (gun insertion lateral movement not in place / insertion position not reached), 2141-2146 (abnormal self-test before gun removal / removal position not reached), 2151-2157 (abnormal steps in returning to protection position), 2161-2165 (abnormal steps in leaving protection position), 2171 (unable to move to target position), 2172 (abnormal standby position), 3101 (charging pile insulation alarm), 3102 (charging pile surge arrester abnormal), 3103 (CC1 charging signal) The following are some of the error codes: 12V detection abnormality, 3104 (charging pile input overvoltage), 3105 (charging pile input overcurrent), 3106 (CC1 charging signal 6V detection abnormality), 3107 (CC1 charging signal 4V detection abnormality), 4101-4104 (drive 1-4 communication failure), 4105 (robotic arm power off), 4106 (robot battery too low), 4107 (robot heating system failure), 4108 (charging cover Bluetooth signal communication abnormality), 4109 (ultrasonic reading failure), 5101 (charging port 1 not recognized), 5102 (charging port 2 not recognized), 5103 (gun head 1 not recognized), 5104 (gun head 2 not recognized), 5105 (parking angle too large), 5106 (image recognition error during aiming), 5107 (charging port height abnormality), and 5108 (charging port distance from rear wheel abnormality).
[0112] For example, the fault codes for high-risk (Level 2 warning, Y=2) are: 1201-1205 (abnormal position of the first to fifth joints), 1211-1215 (abnormal motor current of the first to fifth joints), 1221-1226 (excessive torque of motors in each joint), 1231-1232 (abnormal return of the gun mount to its half position), 1233 (gun head not in the correct position), 1241 (abnormal current of the robotic arm), 1242 (obstruction in the route), 2201-2204 (abnormal movement command when moving backward), 2211-2216 (abnormal movement command), 2221 (movement timeout), 2222 (abnormal free command), 2223 (abnormal manual operation or failure to perform manual operation). Errors include: 2224 (Incorrect posture during inspection), 2225 (Unsafe posture of robotic arm preventing movement), 3201 (Internal communication abnormality of charging pile), 3202 (DC power supply tripping of charging pile), 3203 (Emergency stop fault of charging pile), 3204 (DC output overcurrent of charging pile), 3205 (DC output overvoltage of charging pile), 4201 (Communication fault of drive board), 4202 (System exit or user stop), 4203 (Communication abnormality of robotic arm), 4204 (Robotic arm start failure), 4205 (Abnormal stop of robotic arm), 4206 (Emergency braking of robotic arm), 4207 (Robot battery fault), 4208 (Serial communication fault of drive board), etc.
[0113] In this embodiment, fault information is classified by risk level, which enables differentiated response measures to be taken according to the severity of the fault, avoiding over-response or under-response caused by using a uniform treatment method for all faults.
[0114] S304: Respond to the fault according to the response measures corresponding to the risk level.
[0115] In this embodiment, the response measures corresponding to the risk level may include, for example: low risk, only recording the fault condition; medium risk, suspending operation and waiting for confirmation of recovery; high risk, immediately triggering emergency power outage protection and stopping operation.
[0116] In other embodiments, when fault information is detected, the fault stage in which the fault information occurred is also obtained; the fault information, fault stage, and risk level are sent to the cloud so that the cloud can provide operation and maintenance management notifications.
[0117] The fault stages correspond to different stages of the charging process, including the pre-charging preparation stage (S1), the automatic robot alignment and gun docking stage (S2), the charging parameter negotiation and charging start stage (S3), and the charging end stage (S4).
[0118] For example, the pre-charging preparation stage is characterized by: Bluetooth connection and authentication between the charging robot and the vehicle, self-testing of the charging robot, path planning by the robotic arm, and preliminary visual recognition. The fault handling strategy focuses on rapid recovery from perceived faults and self-test anomalies to ensure the robot is ready to start.
[0119] For example, the characteristics of the robot's automatic alignment and charging gun docking phase are: precise visual positioning, robotic arm movement, charging gun insertion and locking. The fault handling strategy focuses on real-time response to motion control failures and hardware anomalies to ensure safe and reliable docking.
[0120] For example, the characteristics of the charging parameter negotiation and charging start phase are: charging parameter negotiation is completed, and DC charging continues to output. The fault handling strategy focuses on emergency protection against electrical and communication anomalies to ensure the safety of the charging process.
[0121] For example, the characteristics of the charging completion phase are: current and voltage reduction, gun removal, and robotic arm return to its original position. The fault handling strategy focuses on the orderly recovery of motion control and hardware faults to ensure the safe return of the equipment.
[0122] The fault codes that may occur in stage S1 are: 1001, 1002, 2022, 5001, 1111, 2161-2165, 2172, 4105, 4106, 4107, 4108, 5105, 5107, 5108, 2222, 2223, 4202, 4204, and 4207; the fault codes that may occur in stage S2 are: 2001, 2002, 2003, 2004, 2 011, 2012, 2013, 1101, 1102, 1103, 1104, 1105, 1111, 1114, 2101-2104, 2111-2117, 2121-2124, 2131, 2132-2136, 2171, 4101-4104, 4105, 4106, 4109, 5101, 5102, 5103, 5104, 5106, 1201-120 5. 1211-1215, 1221-1226, 1233, 1241, 1242, 2211-2216, 2221, 2222, 2223, 2224, 2225, 4201, 4202, 4203, 4205, 4206, 4207, and 4208; Fault codes that may appear in the S3 stage include: 3001, 3002, 1101, 1102, 1103, 1104, and 110. 5, 1111, 3101, 3102, 3103, 3104, 3105, 3106, 3107, 4101-4104, 4105, 1201-1205, 1211-1215, 1221-1226, 1241, 2222, 2223, 3201, 3202, 3203, 3204, 3205, 4201, 4202, 4203, 4205, 4206, and 4208. The fault codes that may occur in the S4 stage are: 1001, 2021, 3003, 1111, 1112, 1113, 1115, 2141-2146, 2151-2157, 2172, 4105, 1231-1232, 1233, 2201-2204, 2221, 2222 and 2223.
[0123] The operation and maintenance management notifications can include remote diagnostic information push and operation and maintenance personnel dispatch notifications. Reporting complete fault information to the cloud supports remote diagnostics and allows operation and maintenance personnel to quickly locate problems, enabling remote maintainability of the charging system and reducing on-site operation and maintenance costs.
[0124] In this embodiment, the handling of the same fault code differs at different charging stages. The operation and maintenance strategy is flexibly adjusted based on the characteristics of each stage to maximize the charging success rate while ensuring safety.
[0125] In this embodiment, all fault information is persistently stored in the cloud, forming a complete anomaly handling log for subsequent reliability analysis and optimization iterations. After fault recovery, it possesses the ability to resume charging from where it left off, allowing it to continue from the last interrupted charging state without restarting the entire charging process.
[0126] Optionally, if a fault is detected, control of the charging robot is stopped and switched to manual charging mode.
[0127] Stopping control of the charging robot means immediately halting the automatic movement control of the robotic arm upon detecting a fault. This prevents secondary damage caused by continued automatic operation under abnormal conditions and ensures the robot remains safely stationary after a malfunction. Switching to manual charging mode means changing the charging robot from automatic charging mode to manual emergency charging mode, allowing users to manually operate the charging gun to complete the charging process. Providing a manual charging mode as an emergency backup for the automatic charging mode ensures that charging capabilities are still available when the robot malfunctions, preventing a complete interruption of charging services due to a single mode failure and improving the overall reliability and availability of the system.
[0128] As described above, the system monitors the message data between the vehicle and the DC charging pile, and identifies whether there is fault information based on the message data, the status of the DC charging pile, the vehicle data, and the status of the charging robot. When fault information is identified, the system obtains the risk level of the fault information and responds to the fault according to the corresponding response measures. This allows for differentiated response measures based on the severity of the fault, avoiding over-response or under-response caused by using a uniform treatment method for all faults.
[0129] The following further describes the automatic charging control system involving multi-terminal collaboration. This application provides an automatic charging control system based on a charging robot. The automatic charging control system based on a charging robot includes: a DC charging station, a cloud platform, and a charging robot; the cloud platform is communicatively connected to both the DC charging station and the charging robot; wherein the charging gun of the DC charging station is fixed to the end of the robotic arm of the charging robot.
[0130] In this embodiment, the DC charging station is used to send its status to the cloud and interact with the vehicle during charging; the vehicle is an external device that interacts with the DC charging station and the charging robot, rather than a system component. The cloud is used to receive the DC charging station's status and to send the DC charging station status, charging requests, and gun unplugging requests to the charging robot. The charging robot is used to execute an automatic charging control method based on the charging robot.
[0131] In this embodiment, the vehicle can be configured to open the vehicle charging port cover and send charging requests and vehicle data to the charging robot. Specifically, the vehicle is configured to open the charging port cover, providing the physical conditions for the robotic arm to insert the charging gun; simultaneously, it sends charging requests and vehicle data to the charging robot, providing information support for determining the charging conditions, thus enabling the vehicle to actively cooperate in the charging process.
[0132] In this embodiment, the communication connection may include a wired communication link and / or a wireless communication link. The interaction and communication between the vehicle and the charging robot can be achieved via Bluetooth. Establishing communication connections between the various terminals enables the real-time transmission of status data and control commands, providing a communication foundation for multi-terminal collaborative operation and ensuring that each terminal can obtain the necessary information and perform corresponding operations in a timely manner throughout the entire charging process.
[0133] In this embodiment, the cloud can also be used to continuously monitor the charging status (including charging power, battery temperature, SOC changes, etc.) and forward key information to the charging robot and the user's mobile device in real time. As the system's scheduling hub, the cloud is responsible for aggregating and forwarding status data and issuing charging / unplugging requests, realizing full visualization and traceability of the charging process, while providing platform support for remote control and operation and maintenance management.
[0134] In this embodiment, the charging robot is used to execute the aforementioned automatic charging control method based on the charging robot. That is, the charging robot is the main executor of the entire automatic charging process, responsible for core operations such as receiving data, judging conditions, visual positioning, robotic arm control, and fault handling. As the main executor of the automatic charging process, the charging robot integrates perception, decision-making, and execution functions, autonomously completing the entire charging process under cloud scheduling and vehicle-side cooperation, achieving full automation of the charging operation.
[0135] In this embodiment, the DC charging station and the charging robot are not an integrated unit; the DC charging station is an independent device, and the charging robot (with a robotic arm) is another independent device. They are physically separate, connected by cables and communication, and their responsibilities are independent and not bound to each other. The DC charging station only handles the basic functions of charging, such as power output, national standard charging negotiation, insulation protection, and power output. Even without the charging robot, the DC charging station can still be manually charged. The charging robot only handles visual recognition, trajectory planning, robotic arm insertion and removal of the charging gun, and anomaly monitoring; the charging robot itself does not perform power conversion. The same charging robot can be paired with charging stations of different power specifications: 7kW / 11kW / 22kW AC charging stations, or DC charging stations. No large-scale hardware modifications to the robot are required, thus enabling platform-based development, modular configuration, and serialized promotion of the charging robot product system.
[0136] As described above, the DC charging pile is used to send its status to the cloud and interact with the vehicle during charging. The cloud receives the DC charging pile's status and sends the status, charging requests, and gun disconnection requests to the charging robot. The charging robot executes the automatic charging control method based on its own capabilities. The vehicle is an external device that interacts with the DC charging pile and the charging robot, not a component of the system. Through the collaborative control of the cloud, the DC charging pile, the charging robot, and the external vehicle, a fully coordinated process from the user initiating a charging request to charging completion is achieved. This ensures the safety and continuity of the charging process, while also providing clear functional boundaries and responsibilities for each component, allowing for flexible expansion of system functionality without requiring additional hardware development.
[0137] In some embodiments, an orderly shutdown process is adopted at the end of the charging phase. Specifically, the cloud is used to send a stop charging command to the DC charging pile when it receives a stop charging request from the user; and only after receiving a charging stop status from the DC charging pile will it send a gun removal request to the charging robot; the DC charging pile is used to cut off the output current and send a charging stop message to the vehicle after receiving the stop charging command; and after receiving a confirmation message from the vehicle, it sends a charging stop status to the cloud.
[0138] In this embodiment, the vehicle can also be configured to send a stop charging command to the DC charging pile when it detects that the battery state of charge has reached a preset target value, and after receiving the charging stop message from the DC charging pile, disconnect the charging relay and send a confirmation message of the charging stop message to the DC charging pile. After receiving the charging stop message, the vehicle disconnects the charging relay, cutting off the charging circuit from the vehicle side, ensuring that the charging circuit is disconnected on both the vehicle side and the charging pile side; sending the confirmation message enables the DC charging pile to confirm that the disconnection operation has been completed on the vehicle side, providing a safety confirmation for subsequent processes.
[0139] In this embodiment, charging completion can be triggered either by the user or automatically by the vehicle. In the case of user-triggered completion, the cloud sends a stop-charging command to the DC charging station after receiving a stop-charging request from the user. That is, the user can actively terminate charging via a mobile application, and the cloud, upon receiving the user's stop-charging request, sends a stop-charging command to the DC charging station. Alternatively, when the vehicle detects that the battery's SOC has reached a preset target value, the vehicle automatically sends a stop-charging command to the DC charging station, achieving automated determination of charging completion. This eliminates the need for the user to continuously monitor the charging progress and avoids overcharging that could damage the battery.
[0140] In this embodiment, after receiving a stop charging command, the DC charging pile cuts off the output current and sends a charging stop message to the vehicle. Cutting off the output current may include performing current reduction and voltage reduction operations according to the protocol, gradually reducing the charging current to a safe range before cutting off the output. After receiving the stop charging command, the DC charging pile first performs current reduction and voltage reduction before cutting off the output, avoiding sudden interruption of large current that could impact the battery and vehicle charging port, thus protecting the safety of the battery and charging equipment.
[0141] In this embodiment, after receiving the vehicle confirmation message, the DC charging pile reports to the cloud that charging has stopped, so that the cloud can confirm that the charging circuit has been safely disconnected on both the pile side and the vehicle side, providing a safe premise for issuing a subsequent request to unplug the charging gun.
[0142] In this embodiment, the cloud must issue the gun-removal command only after confirming that charging has completely stopped. Only after confirming that charging has completely stopped does the cloud send the gun-removal request to the charging robot, ensuring that the gun-removal operation is performed in a safe state where the charging circuit is completely disconnected and no current flows. This completely avoids the safety hazard of arcing during gun removal under load and ensures the safety of personnel and equipment during the removal process.
[0143] As described above, when the cloud receives a stop charging request from the user, it sends a stop charging command to the DC charging pile. After receiving the stop charging command, the DC charging pile cuts off the output current and sends a charging stop message to the vehicle. After receiving a confirmation message from the vehicle, it sends a status message to the cloud indicating that charging has stopped. Only after the cloud receives the status message indicating that charging has stopped does it send a gun removal request to the charging robot. This ensures that the gun removal operation is only performed after charging has completely stopped and the circuit has been safely disconnected, avoiding arcing during gun removal under load and further ensuring the safety of the gun removal process.
[0144] Figure 4 This is a schematic diagram of the hardware structure of the charging robot provided in an embodiment of this application. Figure 4 As shown, the charging robot of this embodiment includes a processor 401 and a memory 402.
[0145] The memory 402 stores computer execution instructions; the processor 401 executes the computer execution instructions stored in the memory to implement the various steps performed by the charging robot in the above embodiments. For details, please refer to the relevant descriptions in the foregoing method embodiments.
[0146] Alternatively, the memory 402 can be either standalone or integrated with the processor 401.
[0147] When the memory 402 is set up independently, the charging robot also includes a bus 403 for connecting the memory 402 and the processor 401.
[0148] This application also provides a computer-readable storage medium storing computer-executable instructions. When the processor executes the computer-executable instructions, the above-described automatic charging control method based on a charging robot is implemented.
[0149] This application also provides a computer program product, including a computer program, which, when executed by a processor, implements the above-described automatic charging control method based on a charging robot.
[0150] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or modules, and may be electrical, mechanical, or other forms.
[0151] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to implement the solution of this embodiment according to actual needs.
[0152] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The unit integrating the above modules can be implemented in hardware or in the form of hardware plus software functional units.
[0153] The integrated modules described above, implemented as software functional modules, can be stored in a computer-readable storage medium. These software functional modules, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods of the various embodiments of this application.
[0154] It should be understood that the aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly manifested as execution by a hardware processor, or execution by a combination of hardware and software modules within the processor.
[0155] The memory may include high-speed RAM, and may also include non-volatile storage (NVM), such as at least one disk storage device, and may also be a USB flash drive, external hard drive, read-only memory, disk or optical disc, etc.
[0156] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.
[0157] The aforementioned storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.
[0158] An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Alternatively, the storage medium can be an integral part of the processor. Both the processor and the storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and storage medium can exist as discrete components in an electronic device or host device.
[0159] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.
[0160] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application 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 or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.
Claims
1. An automatic charging control method based on a charging robot, characterized by, The method, applied to a charging robot, involves fixing the charging gun of a DC charging station to the end of the robot's robotic arm; the method includes: Receive DC charging pile status and vehicle data, and obtain the vehicle parking location; Upon receiving a charging request, the system combines the status of the DC charging pile, the vehicle data, the vehicle parking position, and the charging robot status to determine whether the conditions for starting charging are met. If the charging start conditions are met, an image of the vehicle's charging port is captured. Based on the image of the vehicle charging port, the robotic arm is controlled to insert the charging gun into the vehicle charging port and lock the head of the charging gun. Upon receiving a request to remove the charging gun, the gun head lock is released, the robotic arm is controlled to remove the charging gun from the vehicle's charging port, and the robotic arm is controlled to return to its initial position.
2. The method of claim 1, wherein, The vehicle data includes at least the charging port cover status and the vehicle gear status; The determination of whether the charging start condition is met includes: Obtain the sender of the charging request; When the transmitting end is a vehicle, if the preset conditions are met, it is determined that the charging start condition is met. The preset conditions are as follows: the charging port cover is in the open state, the charging request carries the plug-in command, the charging robot is in the normal state, the vehicle parking position is within the preset range of the robotic arm, the DC charging pile is in the normal state, and the vehicle gear is in P gear.
3. The method of claim 2, wherein, The vehicle data also includes vehicle identification number and vehicle operating condition; the method further includes: When the sending end is the cloud, and the vehicle is in a wake-up state, if the preset conditions are met and the vehicle identification number carried in the charging request is consistent with the vehicle identification number in the vehicle data, then it is determined that the charging start condition is met. When the sending end is the cloud, and the vehicle is in a dormant state, if the charging request carries a plug-in command, the charging robot is in a normal state, and the DC charging pile is in a normal state, then the charging start conditions are determined to be met.
4. The method of claim 1, wherein, The vehicle charging port image includes a first vehicle charging port image and a second vehicle charging port image. Accordingly, controlling the robotic arm to insert the charging gun into the vehicle charging port based on the vehicle charging port image includes: Based on the first vehicle charging port image, determine the three-dimensional coordinates of the vehicle charging port in the charging robot coordinate system; Based on the three-dimensional coordinates, the robotic arm is controlled to move to a preset distance from the vehicle charging port; Based on the second vehicle charging port image, determine the position and orientation of the vehicle charging port; Based on the position and the posture, the robotic arm is controlled to insert the charging gun into the vehicle's charging port.
5. The method of claim 4, wherein, The step of determining the position and orientation of the vehicle charging port based on the second vehicle charging port image includes: Extract the contour features of the vehicle charging port from the second vehicle charging port image; Obtain the similarity between the contour features and a preset standard vehicle charging port contour template; If the similarity exceeds a preset threshold, the position and orientation of the vehicle charging port are determined based on the contour features.
6. The method of claim 4, wherein, The step of controlling the robotic arm to insert the charging gun into the vehicle charging port based on the position and the posture includes: Based on the position and the posture, multiple spatial key points for the movement of the robotic arm are determined; wherein, the robotic arm includes multiple linear axes and multiple rotational axes; Based on the multiple spatial key points, the target motion parameters of each axis of the robotic arm are determined; According to the target motion parameters of each axis, the robotic arm is controlled to insert the charging gun into the vehicle's charging port.
7. The method of claim 6, wherein, The step of determining the target motion parameters of each axis of the robotic arm based on the plurality of spatial key points includes: Based on the multiple spatial key points, determine the target linear displacement value and uniform interpolation sequence for each linear axis, as well as the target angle value and smooth angle transition sequence for each rotation axis; Initial motion parameters for each axis are generated based on the target linear displacement value, the uniform interpolation sequence, the target angle value, and the smooth angle transition sequence. According to the preset motion constraints of the robotic arm, the initial motion parameters of each axis are corrected to obtain the target motion parameters of each axis.
8. The method of claim 1, wherein, Also includes: Monitor the message data between the vehicle and the DC charging pile; Based on the message data, the status of the DC charging pile, the vehicle data, and the status of the charging robot, identify whether there is any fault information; If fault information is detected, the risk level of the fault information is obtained; Fault response shall be carried out according to the response measures corresponding to the risk level.
9. The method of claim 8, wherein, Also includes: When the fault information is detected, the fault stage in which the fault information occurred is also obtained; The fault information, the fault stage, and the risk level are sent to the cloud so that the cloud can provide operation and maintenance management notifications.
10. A charging robot characterized by, include: The robot body, the robotic arm, and the controller; wherein the robotic arm is mounted on top of the robot body; Cameras are installed on the top of the robot body and at the end of the robotic arm; An adapter socket is provided inside the robot body; the charging gun of the DC charging station is fixed to the end of the robotic arm through the adapter socket; The controller is electrically connected to the robotic arm and the camera respectively, and is used to execute the automatic charging control method based on the charging robot according to any one of claims 1 to 9.
11. A charging robot characterized by, include: At least one processor; The system includes a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, the computer program being executed by the at least one processor to cause the at least one processor to perform the automatic charging control method based on a charging robot as described in any one of claims 1 to 9.
12. An automatic charging control system based on a charging robot, characterized by, include: The system includes a DC charging station, a cloud platform, and a charging robot. The cloud platform is communicatively connected to both the DC charging station and the charging robot. The charging gun of the DC charging station is fixed to the end of the robotic arm of the charging robot. The DC charging pile is used to send its status to the cloud and to interact with the vehicle during charging; wherein, the vehicle is an external device that interacts with the DC charging pile and the charging robot, rather than a system component. The cloud is used to receive the DC pile status sent by the DC pile, and to send the DC pile status, charging request and gun removal request to the charging robot; The charging robot is used to execute the automatic charging control method based on the charging robot as described in any one of claims 1 to 9.
13. The system according to claim 12, characterized in that, The cloud is used to send a stop charging command to the DC charging pile when it receives a stop charging request from the user terminal; and only after receiving a stop charging status from the DC charging pile will it send the gun removal request to the charging robot. The DC charging pile is used to cut off the output current and send a charging stop message to the vehicle after receiving the charging stop command; and after receiving the confirmation message sent by the vehicle, it sends a status message to the cloud indicating that charging has stopped.
