System and method for performing charging diagnostics at charging station by scheduling

Abstract

The present disclosure provides a system and method for performing charging diagnostics at a charging station by scheduling. A control system controls a charging operation of an electric vehicle (EV) using a plurality of electric vehicle power supply equipments (EVSEs). The control system includes a processor programmed to generate a first charging message to assign a first EVSE to perform a charging operation on the EV, and to generate a second charging message to assign a second EVSE to perform the charging operation on the EV, such that the second EVSE performs the charging operation in response to the first EVSE unsuccessful charging of the EV after an operator's plug-in attempt and a previous charging operation having an unsuccessful charging in combination with an operation including the operator, the EV, or the first EVSE.

Description

Technical Field

[0001] This disclosure generally relates to a system or method for controlling charging operations in a charging station having multiple electric vehicle power supply devices for charging electric vehicles. Background Technology

[0002] Electric vehicles (EVs) (such as plug-in hybrids or pure EVs) typically use electric vehicle power supply equipment (EVSEs) to charge their battery packs. Charging stations provide multiple EVSEs available for charging EVs, and in some instances, trained operators manage and facilitate the charging of EVs. For example, during a charging operation, the operator connects the EVSE's EVSE connector to the EV's charging port and can then leave the EV to perform other duties. Summary of the Invention

[0003] In one form, this disclosure relates to a control system for controlling the charging operation of an electric vehicle (EV) using multiple electric vehicle power supply units (EVSEs). The control system includes a processor programmed to generate a first charging message to allocate a first EVSE to perform the charging operation on the EV, and to generate a second charging message to allocate a second EVSE to perform the charging operation on the EV, such that the second EVSE performs the charging operation in response to an unsuccessful charging attempt by the first EVSE to the EV following an operator's plug-in attempt and a previous charging operation having a combination of unsuccessful charging with operations involving the operator, the EV, or the first EVSE.

[0004] In one form, this disclosure relates to a non-transitory computer-readable storage medium including programming instructions configured to cause a processor to control charging operations of an electric vehicle (EV) in a charging station. The programming instructions include instructions to instruct a second electric vehicle power supply unit (EVSE) to perform a charging operation on the EV in response to a first EVSE failing to charge the EV and an operator having an unsuccessful charging operation associated with the first EVSE, the first EVSE having an unsuccessful charging operation associated with the EV, or an operator having an unsuccessful charging operation associated with the EV.

[0005] In one form, this disclosure relates to a method for controlling the charging operation of an electric vehicle (EV) at a charging station having multiple electric vehicle power supply units (EVSEs). The method includes transmitting a first charging message to allocate a first EVSE to perform the charging operation on the EV, and transmitting a second charging message to allocate a second EVSE to perform the charging operation on the EV, such that the second EVSE performs the charging operation in response to the first EVSE failing to charge the EV after an operator's plug-in attempt and a previous charging operation having an unsuccessful charging operation associated with the EV or the first EVSE, or the first EVSE having an unsuccessful charging operation associated with the EV. Attached Figure Description

[0006] Figure 1 A charging station for charging electric vehicles is shown.

[0007] Figure 2 This is an example block diagram of a pure electric vehicle.

[0008] Figure 3 This is a sample block diagram of EVSE.

[0009] Figure 4 This is an example block diagram of a station control system used in charging stations.

[0010] Figure 5 This is a flowchart of an example charging error diagnosis routine. Detailed Implementation

[0011] Detailed embodiments of the invention are disclosed herein as needed; however, it should be understood that the disclosed embodiments are merely examples of the invention that can be embodied in various forms and alternative forms. The drawings are not necessarily drawn to scale; some features may be enlarged or minimized to show details of specific components. Therefore, the specific structural and functional details disclosed herein are not to be construed as limiting, but only as representative bases for teaching those skilled in the art to employ the invention in various ways.

[0012] Charging stations are configured to charge multiple EVs simultaneously using multiple EVSEs, and are designed to reduce the time and resources spent resolving charging issues or rescheduling charging events by ensuring a successful first plug-in from the EVSE to the EV. The first successful plug-in can be intermittent, and the solution goes beyond simply identifying potential hardware problems (e.g., hardware issues with the EVSE or EV) and can be extended to problems related to a combination of hardware and human actions (e.g., operator actions).

[0013] In one form, this disclosure relates to a system and / or method for identifying potential causes of plugging-in errors and scheduling charging operations for an EV based on previous charging operations. In a non-limiting example, the system / method of this disclosure is configured to generate a first charging message to assign a first EVSE to perform the charging operation for the EV. In some applications, a historical charging operation record is used to select the first EVSE, the historical charging operation record indicating successful and / or unsuccessful charging operations and identifying the operator, EV, and EVSE involved in the charging operation. The system / method is also configured to generate a second charging message to assign a second EVSE to perform the charging operation for the EV in response to the first EVSE failing to charge the EV after an operator's plugging-in attempt and at least one previous charging operation having an unsuccessful charging combination including at least two of the operator, EV, or first EVSE. That is, the system / method evaluates the previous unsuccessful charging operations associated with the first EVSE, EV, and operator to determine potential causes of plugging-in errors and provide further instructions to advance the charging of the EV.

[0014] refer to Figure 1 Charging station 100 includes multiple electric vehicle power supply units (EVSEs) 102 for charging multiple electric vehicles (EVs) 104. In some aspects, charging station 100 includes a station control system 106 configured to schedule charging operations for selected EVs 104 with the assistance of an operator 108. In a non-limiting example, station control system 106 obtains information related to EVs 104, such as, but not limited to, identification and state of charge. Using this information, station control system 106 assigns EVs 104 to selected EVSEs 102, and operator 108 connects EVSEs 102 to EVs 104.

[0015] EV 106 can be a pure electric vehicle, a plug-in hybrid vehicle, or any other vehicle having a battery pack 204 that can be recharged using EVSE 102. In a non-limiting example, refer to... Figure 2 The EV 106 includes a powertrain 202, a battery pack 204, and a power electronics module (PEM) 206. The EV 106 disclosed herein does not include an engine, and therefore, the battery pack 204 provides all propulsion power.

[0016] The powertrain 202 includes an electric motor (not shown) that provides power movement to the EV 106 via a transmission system. A battery pack 204 provides a high-voltage (HV) direct current (DC) output for driving the powertrain 202 via a PEM 206. In one embodiment, the PEM 206, including an inverter, provides bidirectional energy transfer between the battery pack 204 and the powertrain's electric motor.

[0017] EV 104 may also include a power conversion module (PCM) 208, which is an on-board charger with a DC / DC converter to regulate power supplied from an external power source (e.g., a power grid / network) via charging port 210 and to provide the correct voltage and current levels to battery pack 204. Charging port 210 is configured to connect to EVSE 102, which draws power from the power source and supplies power to EV 104 through charging port 210 and PCM 208. In a non-limiting example, charging port 210 is configured according to a defined protocol (such as Type 1 - SAE J1772, Type 2 - Mannekes, CHAdeMO, or a combined charging system).

[0018] In one embodiment, EV 104 includes a control system 212 to coordinate the operation of various components. Control system 212 includes electronics and software to perform necessary control functions for operating EV 104. Control system 212 may be a combined vehicle control system and powertrain control module (VSC / PCM). In one embodiment, control system 212 is configured to control the operation of battery pack 204 (e.g., controlling the charging / discharging of battery pack 204) using, for example, state of charge (SOC) or electrical limits defined by the SOC of battery pack 204. In a non-limiting example, during driving operation, control system 212 determines how much power to draw from battery pack 204, and during charging operation, control system 212 determines how much power is needed to charge battery pack 204.

[0019] Although the control system 212 is shown as a single device, it may also include multiple controllers in the form of multiple hardware devices, or multiple software controllers with one or more hardware devices. In this regard, the reference to "controller" herein may refer to one or more controllers.

[0020] In addition to the components / systems for controlling the propulsion of EV 106, EV 106 also includes other systems for performing other supporting functions. In a non-limiting example, EV 106 includes a communication module 214 (also referred to as the "EV communication module") configured to exchange information with external devices or systems using wired / wireless communication (e.g., Bluetooth, ultra-wideband, cellular, and / or Wi-Fi). In one form, communication module 214 exchanges messages with the station control system 106 and / or EVSE 102. Therefore, communication module 214 may include communication devices for supporting wireless and wired communication, such as routers, modems, antennas, input-output interfaces, universal serial bus (USB) ports, and / or other suitable devices.

[0021] The EVSE 102 at charging station 100 can be of the same type or different types to provide charging for EVs with different charging ports. (Reference) Figure 3 In one configuration, the EVSE 102 is configured to include a communication (Comm.) module 302, a human-machine interface (HMI) 304, a power control module 306, and an EVSE connector 308 for connection to the charging port 210 of the EV 104.

[0022] The communication module 302 is configured to communicatively connect the EVSE 102 to the site control system 106, EV 104, and / or other devices / systems using a wired or wireless communication network supported by one or more wireless communication protocols. In a non-limiting example, the communication module 302 may employ wireless communication protocols such as Wi-Fi, cellular, Bluetooth, and / or ultra-wideband (UWB), and may include communication devices such as, but not limited to, antennas, transceivers, routers, and / or software protocols executed by a processor.

[0023] HMI 304 is configured to provide information to a user (such as operator 108) about the charging operation being performed, and also to receive input from operator 108. In a non-limiting example, HMI 304 includes a touchscreen display, one or more buttons, a speaker, and / or a microphone. In some aspects, HMI 304 is configured to provide information provided by EVSE 102 itself, or to provide information from the site control system 106. For example, EVSE 102 may indicate whether a charging operation is active. In another example, site control system 106 uses HMI 304 to provide notifications or requests for additional information, such as, but not limited to: requesting operator 108 to provide identification information of a charging operation, providing notification that EV 104 will be charged at another EVSE 102, and / or providing instructions on how to connect EVSE connector 308 to EV 104.

[0024] Power control module 306 is configured to manage the transfer of electrical energy between an external power source (e.g., a power grid) and EV 104. In other electrical devices such as power inverters and DC-DC converters, power control module 306 includes an EVSE connector 308 for connection to EV 104. In some aspects, EVSE 102 communicates with EV 104 using the EVSE connector 308 of EVSE 102 and a physical communication port at charging port 210 (e.g., control pilot) of EV 106 to exchange information related to charging operations, such as, but not limited to, the state of charge (SOC) of battery pack 204.

[0025] In an example operation for charging EV 104, operator 108 and selected EVSE 102 receive instructions to perform a charging operation on EV 104. Operator 108 can log in to the selected EVSE 102 to confirm that they will perform the charging operation, thereby associating the charging operation with a unique identifier associated with operator 108. In a non-limiting example, the operator can log in by using the HMI 304 of EVSE 102 to enter an identification code, scanning an RFID card associated with operator 108, and / or providing biometric input (such as a facial scan or fingerprint).

[0026] Once logged in, operator 108 can attempt to connect EVSE connector 308 to charging port 210 of EV 106, and once connected, EVSE 102 should begin charging EV 106. However, in some instances, EVSE 102 does not charge EV 106, possibly because EVSE connector 308 does not properly engage with charging port 210. For example, operator 108 may not apply sufficient force to connect EVSE connector 308 to charging port 210 to engage the pins of EVSE connector 308 with the port of charging port 210. In another example, EVSE connector 308 / charging port 210 may have physical features that could interfere with charging port 210 / EVSE connector 102 (e.g., bumps or convex surfaces on EVSE connector 102 / charging port 210). If charging does not begin, EVSE 102 and / or EV 104 may transmit a message to the station control system 106 indicating an error in the charging operation, which may be provided as a plugging-in error. In addition to EVSE 102 and / or EV 104, operator 108 may also notice that power is not being drawn or that EVSE connector 308 is not connected to charging port 210 based on information provided on HMI 304 of EVSE 102. Using HMI 304, operator 108 notifies the site control system 106 of the error. In some forms, EVSE 102, EV 104, and / or operator 108 may notify the site control system after the first plug-in attempt to reduce charging delays. As described in detail herein, site control system 106 is configured to determine the potential cause of a plug-in error and take additional steps to advance the charging process.

[0027] Although operator 108 is described as communicating with the station control system 106 using the HMI 304 of EVSE 102, operator 108 may also communicate using other devices, such as, but not limited to, portable computing devices configured to communicate with the station control system 106.

[0028] The station control system 106 is configured to assign EVSE 102 to the EV 104 to be charged using historical information related to the charging operation. This historical information may include: the EV, EVSE, and operator identification of the charging operation; any errors associated with the charging operation; and / or whether the charging operation was successful or unsuccessful; and other information (e.g., date, SOC of the EV 104 before charging, and charging duration). In one form, reference... Figure 4 The station control system 106 includes a station communication module 402, a charging operation history module 404, and a charging operation module 406.

[0029] The site communication module 402 is configured to communicate with external devices / systems (e.g., EVSE 102, EV 104, and / or a portable computing device associated with operator 108) via wireless / wired communication. In a non-limiting example, the site communication module 402 includes communication devices for supporting wireless and wired communication, such as, but not limited to, routers, modems, antennas, input-output interfaces, universal serial bus (USB) ports, and / or other suitable devices.

[0030] The charging operation history module 404 is configured to store information related to charging operations performed at the charging station 100. In a non-limiting example, the charging operation history module 404 is configured to generate and update historical charging records to be stored in the station charging record data storage area 408. Historical charging records can be provided for each EVSE 102, each operator 108, and in some variations, for each EV 104.

[0031] In one form, each charging operation employs EVSE 102, operator 108, and EV 104, which can be referred to as variables influencing the charging operation and potential causes of plugging errors. Historical charging records can be configured in various suitable ways to easily correlate the three variables with each other for charging operations. In a non-limiting example, the historical charging record for selected EVSE 102 may include identification information associated with operator 108 and EV 104 for each charging operation, as well as whether charging was successful or involved an error event (e.g., plugging error). Thus, the historical charging record for selected operator includes identification information associated with EVSE 102 and EV 104 for each charging operation, and the historical charging record for selected EV includes identification information associated with EVSE 102 and operator 108 for each charging operation.

[0032] The charging operation module 406 is configured to control and manage the charging operations of EVSE 102 and EV 106 by: tracking the availability of EVSE 102, directing incoming EV 106 to a designated EVSE 102 for charging, and monitoring the charging operations based on data from EVSE 102, EV 104, and / or a portable computing device associated with operator 108. In a non-limiting example, the charging operation module 406 may operate as an EVSE monitor 410 and an EVSE-operator scheduler 412.

[0033] In one embodiment, the EVSE monitor 410 is configured to store EVSE information associated with each EVSE 102 in relation to its operational status. In a non-limiting example, the EVSE information may include the location of the EVSE 102, a unique identifier associated with the EVSE 102, the type of the EVSE connector 308 provided with the EVSE 102, and / or the maintenance schedule of the EVSE 102. Additionally, the operational status of the EVSE 102 may include: a standby state, indicating that the EVSE 102 is available to perform charging operations; a charging in progress state, indicating that the EVSE 102 is in the process of charging the assigned EV 104; a charging error state, indicating that power has not been delivered to the EV 106 even though the EVSE 102 has not detected a system / device level error; and / or an offline operation state, indicating that the EVSE 102 is unavailable for charging due to, for example, maintenance or the need for repair.

[0034] The EVSE-operator scheduler 412 is configured to assign EV 106 to EVSE 102 based on the type of charging port 210 (also known as charging port type), the type of EVSE connector 308, and charging history data of EV 106, EVSE 102, and / or operator 108 (if available). For example, when EV 106 enters charging station 100, station control system 106 may transmit a message to EV 106 requesting charging status information (such as the charging port type and SOC of battery pack 204) for performing charging operations. In another example, when EV 104 enters charging station 100, operator 108 obtains the charging status information from EV 104 by, for example, manually entering the charging status information via a portable computing device, connecting a dongle to EV 104, and other methods.

[0035] Once the charging status information is obtained, it is provided to the site control system 106. The EVSE-operator scheduler 412 selects a specified EVSE 102 from a plurality of available EVSE 102s, wherein the available EVSE 102 may include an EVSE 102 in a standby operating state and having an EVSE connector 308 compatible with the type of charging port 210 on the EV 106. When multiple available EVSE 102s exist for the EV 106, the EVSE-operator scheduler 412 may employ one or more rules to select a specified EVSE 102. For example, the EVSE-operator scheduler 412 selects a first available EVSE 102 based on the location of the available EVSE 102 and / or the state of charge of the EV 106.

[0036] In the presence of multiple operators 108 at charging station 100, the EVSE-operator scheduler 412 is configured to assign operators 108 based on their availability and charging history data associated with them (if available). In a non-limiting example, the EVSE-operator scheduler 412 tracks the operators 108 at station 100 and whether they have checked in to EVSE 102 to connect EVSE 102 to EV 104. Therefore, the EVSE-operator scheduler 412 selects an operator from one or more operators 108 that are not associated with EVSE (e.g., not checked in or logged into EVSE 102 to perform charging operations).

[0037] Using the charging history data provided in the site charging record 408, the EVSE-operator scheduler 412 is configured to view charging records associated with at least one of EV 106, available EVSE 102, or available operator 108. As detailed below, the charging history data provides information on successful and / or unsuccessful charging operations. In a non-limiting example, if the charging history data is available to operator 108, the EVSE-operator scheduler 412 is configured to evaluate the number of unsuccessful charging operations associated with operator 108 and one or more of the plurality of EVSEs 102. The EVSE-operator scheduler 412 selects for operator 108 an EVSE 102 with fewer unsuccessful charging operations than at least one of the other EVSEs 102. In yet another example, if charging history data is available for the EV 104 to be charged, the EVSE-operator scheduler 412 selects an available EVSE 102 that is not associated with a previously unsuccessful charging operation or has fewer unsuccessful charging operations than another available EVSE 102. Therefore, the EVSE-operator scheduler 412 selects the EVSE 102 and / or operator 108 that may provide a lower probability of unsuccessful charging operations.

[0038] Once EVSE 102 and / or operator 108 are selected, EVSE-operator scheduler 412 notifies the selected EVSE 102 and operator 108. In a non-limiting example, EVSE-operator scheduler 412 generates a charging allocation message to transmit to the selected EVSE 102 and provides it to operator 108 via a portable computing device associated with operator 108, displaying an allocation indicating that EV 104 and EVSE 102 have been allocated to operator 108.

[0039] In some applications, the EVSE-operator scheduler 412 can also transmit charging instructions to the EV 104 to provide a selected EVSE 102 for performing the charging operation. The instructions may include a unique identifier associated with the EVSE 102 and a map / instructions for locating the EVSE 102. In a non-limiting example, if the EV 104 is a fully autonomous vehicle, the EV 104 can autonomously move to the selected EVSE 102, where the operator 108 then connects the EVSE 102 to the EV 104. In another example, if the EVSE 102 is not a fully autonomous vehicle, the operator 108 of the EV 104 (e.g., the operator 108 selected for the charging operation or another operator 108) or the original driver drives the EV 104 to the EVSE 102.

[0040] With EV 104 at the selected EVSE 102, the selected operator 108 can log in to EVSE 102 and connect EVSE connector 308 to charging port 210. In some instances, EVSE connector 308 may not be properly connected to charging port 210 of EV 104, and therefore, power may not be supplied to battery pack 204 of EV 104. In a non-limiting example, when EVSE connector 308 is disconnected from EVSE 102 and not connected to charging port 210 for a selected period of time, EVSE 102 can detect a plugging-in error, where the connection is detected using known techniques. In another example, the plugging-in error is detected based on an error input by operator 108. In some applications, EVSE 102 can notify the site control system 106 of a plugging-in error. In addition to the site control system 106, EVSE 102 can also immediately provide notification on HMI 304 to inform operator 108 of the error.

[0041] If no errors occur and the charging operation is completed, the charging operation history module 404 updates the historical charging records for the corresponding selected EVSE 102, operator 108, and EV 104 (if applicable). In a non-limiting example, the charging operation history module 404 includes information indicating that the combination of selected EVSE 102, selected operator, and EV 104 was successful.

[0042] In one form, the EVSE-operator scheduler 412 includes a charging error diagnosis 414, which is configured to diagnose potential causes of plugging errors using information, for example, provided in the site charging record data storage area 408, related to the EV 104 being charged, the selected EVSE 102, and / or the operator 108.

[0043] In the non-restrictive example, Figure 5 Example charging error diagnosis routine 500 is provided for charging error diagnosis 414. At operation 502, charging error diagnosis 414 obtains charging event information related to the charging operation, including but not limited to: identifiers associated with the EVSE 102, operator 108, and EV 104 that are being charged; the date of the charging operation; the time of the plugging error detection; the state of charge of the EV; and / or external factors (e.g., weather information, possible communication network outage information, and / or power outage information).

[0044] Using the charging event information, at operation 504, charging error diagnosis 414 determines whether EV 104 and the selected EVSE 102 have previous charging operation history data. In a non-limiting example, using the charging event information and historical charging records (e.g., records associated with EVSE 102 and / or EV 104), charging error diagnosis 414 determines whether the selected EVSE 102 has had unsuccessful charging operations with EV 104 from one or more previous charging operations.

[0045] If historical data exists between EV 104 and the selected EVSE 102, at operation 506, charging error diagnosis 414 recommends assigning EV 104 to a different EVSE 102 based on the charging history data of EV 104 or EVSE 102. In a non-limiting example, charging error diagnosis 414 determines whether there is at least one alternative EVSE 102 compatible with EV 104 that has a successful charging operation with EV 104, or whether there is an EVSE 102 that does not have charging history data with EV 104. Using one or more alternative EVSE 102s, EVSE-operator scheduler 412 selects an alternative EVSE 102 that can be used to charge EV 104 and provides a charging assignment message to the selected alternative EVSE 102. In some variations, EVSE-operator scheduler 412 also provides notification to the EVSE 102 with charging problems, instructing operator 108 that EV 104 will be charged at the selected alternative EVSE 102.

[0046] If there is no historical data between the selected EVSE 102 and EV 104, the charging error diagnosis 414 determines at 508 whether the selected EVSE and operator 108 have previous charging history data. In a non-limiting example, using charging event information and historical charging records (e.g., records associated with EVSE 102 and / or operator 108), the charging error diagnosis 414 determines whether the selected EVSE 102 has had unsuccessful charging operations with operator 108 from one or more previous charging operations.

[0047] If historical data exists between the selected EVSE 102 and operator 108, at operation 510, charging error diagnosis 414 recommends assigning EV 104 to a different EVSE 102 based on the operator 108 / EVSE 102 historical data. In a non-limiting example, charging error diagnosis 414 determines whether there is at least one alternative EVSE 102 compatible with EV 104 that has a successful charging operation with operator 108, or does not have historical charging data with operator 108. Using one or more alternative EVSE 102s, EVSE-operator scheduler 412 selects an alternative EVSE 102 that can be used to charge EV 104 and provides a charging assignment to the selected alternative EVSE 102 and / or operator 108. In some variations, EVSE-operator scheduler 412 also provides notification to EVSE 104 with charging problems, instructing operator 108 that EV 104 will be charged at the selected alternative EVSE 102.

[0048] If there is no historical data between the selected EVSE 102 and operator 108, charging error diagnosis 414 determines at 512 whether EV 104 and operator 108 have previous charging history data. In a non-limiting example, using charging event information and historical charging records (e.g., records associated with operator 108 and / or EV 104), charging error diagnosis 414 determines whether operator 108 has had unsuccessful charging operations with EV 104 from one or more previous charging operations.

[0049] If there is a history of unsuccessful charging with operator 108 and EV 104, at operation 514, charging error diagnosis 414 assists operator 108 or may request assistance from another operator 108. In a non-limiting example, charging error diagnosis 414 provides operator 108 with instructions on how to connect the selected EVSE 102 to EV 104 via HMI 304, wherein the instructions for operating EVSE 102 may be stored by EVSE 102. In addition to providing instructions, or instead of providing instructions, charging error diagnosis 414 is configured to notify another operator 108 that there are no unsuccessful charging operations with EV 104 and no unsuccessful charging operations with the selected EVSE 102 (if available). At operation 514, charging error diagnosis 414 may assign different EVSEs based on the history data of operator 108 and / or EV 104.

[0050] If there is no historical data between EV 104 and operator 108, at operation 516, charging error diagnosis 414 causes the EVSE-operator scheduler 412 to select another available EVSE 102 to perform the charging operation. If no association is detected between different combinations of EVSE 102, operator 108, and EV 104, a different EVSE 102 is selected to avoid further delays in the charging operation. Additionally, at operation 518, charging error diagnosis 414 records a new charging event with a plugging-in error via charging operation history module 406. As detailed above, charging operation history module 406 is configured to record charging event information using records associated with EVSE 104, operator 108, and / or EV 104.

[0051] In some applications, at operation 518, charging error diagnosis 414 is configured to define a test plan for a new charging event by defining multiple subsequent charging operations for EV 104, operator 108, and EVSE 102, to establish charging operation history data that can be used to identify one or more causes of plug-in errors. In other words, if EVSE 102, EV 104, and operator 108 are considered variables of the plug-in error charging event, the test plan is defined as changing at least one of the variables of the subsequent charging operations. In a non-limiting example, the subsequent charging operations used for the test plan include: assigning one or more other EVSE 102s from the plurality of EVSE 102s to charge EV 104 together with the operator; assigning operator 108 to charge one or more different EVs from the plurality of EVSE 102s with the selected EVSE 102; or assigning EVSE 102 to charge EV 104 with a different operator. Therefore, the EVSE-operator scheduler 412 is configured to further select EVSE 102 and / or operator 108 based on the test plan of EV 104 (if available).

[0052] It should be readily understood that the charging error diagnosis 414 can be configured in a variety of suitable ways and should not be limited to the examples provided herein. The following examples of the charging error diagnosis 414 can be incorporated into or combined with each other.

[0053] In some variations, the charging error diagnosis 414 is configured to track the number of plug-in attempts made to EV 104. Therefore, instead of assigning EV 104 to a different EVSE 104 after a first plug-in error caused by operator 108 or EVSE 102, the charging error diagnosis 414 can be configured to provide operator 108 with instructions on how to connect the selected EVSE 102 to EV 104 via HMI 304. If a plug-in error still occurs, the alternative EVSE 102 is assigned to EV 104.

[0054] In another variant, if operator 108 has historical data on plug-in errors, charging error diagnosis 414 is configured to recommend training to operator 108.

[0055] In another variation, the charging error diagnosis 414 is configured to determine whether the plugging error is caused by a system error in EVSE 102 or EV 104. That is, EVSE 102 and / or EV 104 may have hardware or software problems preventing battery pack 204 from being charged, and therefore may not be a problem with the actual connection between EVSE connector 308 and charging port 210. The corresponding EVSE 102 or EV 104 may report the possible system error automatically or after being queried by the site control system 106.

[0056] In one variant, the charging error diagnosis 414 can be configured to record charging events, but may not generate a charging schedule.

[0057] In another variation, the charging error diagnosis 414 may evaluate only the previous charging history data associated with operator 108 (e.g., only...). Figure 5 Operations 508 and 512).

[0058] Unless otherwise expressly indicated herein, all numerical values ​​indicating mechanical / thermal properties, percentage of composition, dimensions and / or tolerances or other characteristics should be understood as being modified by the words “about” or “approximately” when describing the scope of this disclosure. Such modification is desired for a variety of reasons, including: industrial practice; material, manufacturing and assembly tolerances; and testing capabilities.

[0059] In this application, the term "module" may refer to, be part of, or include the following: application-specific integrated circuit (ASIC); digital, analog, or mixed analog / digital discrete circuit; digital, analog, or mixed analog / digital integrated circuit; composable logic circuit; field-programmable gate array (FPGA); processor circuitry (shared, dedicated, or grouped) that executes code; memory circuitry (shared, dedicated, or grouped) that stores code executed by the processor circuitry; other suitable hardware components that provide the described functionality; or combinations of some or all of the foregoing, such as in a system-on-a-chip.

[0060] The term memory is a subset of the term computer-readable medium (e.g., non-transitory computer-readable storage medium). As used herein, the term computer-readable medium does not cover transient electrical or electromagnetic signals propagated through a medium (such as on a carrier wave); therefore, the term computer-readable medium can be considered tangible and non-transitory. Non-limiting examples of non-transitory tangible computer-readable media include non-volatile memory circuits (such as flash memory circuits, erasable programmable read-only memory circuits, or mask read-only circuits), volatile memory circuits (such as static random access memory circuits or dynamic random access memory circuits), magnetic storage media (such as analog magnetic tape or digital magnetic tape or hard disk drives), and optical storage media (such as USB, CD, DVD, or Blu-ray discs).

[0061] The apparatus and methods described in this application can be implemented, in part or in whole, by a dedicated computer created by configuring a general-purpose computer (e.g., a computing device) to perform one or more specific functions embodied in a computer program. Function blocks, flowchart components, and other elements described above serve as software specifications that can be translated into computer programs through the routine work of a technician or programmer.

[0062] The description in this disclosure is merely exemplary in nature, and therefore, variations without departing from the spirit and scope of this disclosure are intended to be made within its scope. Such variations should not be considered as departing from the spirit and scope of this disclosure.

[0063] According to the present invention, a control system is provided that uses multiple electric vehicle power supply units (EVSEs) to control the charging operation of an electric vehicle (EV), comprising: a processor programmed to generate a first charging message to allocate a first EVSE to perform a charging operation on the EV, and to generate a second charging message to allocate a second EVSE to perform the charging operation on the EV, such that the second EVSE performs the charging operation in response to an unsuccessful charging of the EV by the first EVSE after an operator's plug-in attempt and a previous charging operation having an unsuccessful charging combination including the operator, the EV, or the first EVSE.

[0064] According to an embodiment, the operation combination includes: the operator having an unsuccessful charging operation associated with the first EVSE, the first EVSE having an unsuccessful charging operation associated with the EV, or the operator having an unsuccessful charging operation associated with the EV.

[0065] According to an embodiment, before generating the second charging message, the processor is further programmed to provide a connection instruction to connect the first EVSE to the EV in response to the previous charging operation including the operator having an unsuccessful charging operation associated with the EV as a combination of operations.

[0066] According to an embodiment, the processor is also programmed to select the second EVSE in response to either: the second EVSE having fewer unsuccessful charging operations to the operator than the other EVSE, or the second EVSE having fewer unsuccessful charging operations to the EV than the other EVSE.

[0067] According to an embodiment, the processor is also programmed to store identification data associated with the EV, the first EVSE, and the operator in relation to each other in response to the first EVSE failing to charge the EV after the plug-in attempt.

[0068] According to an embodiment, the processor is further programmed to select the first EVSE based on historical charging operation records, the historical charging operation records indicating that: the first EVSE or the operator has not yet participated in a charging operation with the EV, the EV has had one or more successful charging operations with the first EVSE, or the operator has had a successful charging operation with the first EVSE.

[0069] According to an embodiment, the plug-in attempt is the operator's first plug-in attempt, and the processor is also programmed to generate a second charging message in response to the first plug-in attempt failing.

[0070] According to an embodiment, the invention is further characterized by a communication device configured to communicate with the plurality of EVSEs, including transmitting a charging message to a selected EVSE, wherein the charging message includes a first charging message and a second charging message.

[0071] According to the present invention, a non-transitory computer-readable storage medium having programming instructions configured to cause a processor to control charging operations of an electric vehicle (EV) in a charging station is provided, wherein the programming instructions include instructions for performing the following operations: in response to a first EVSE failing to charge the EV and an operator having an unsuccessful charging operation associated with the first EVSE, the first EVSE having an unsuccessful charging operation associated with the EV, or the operator having an unsuccessful charging operation associated with the EV, instructing a second electric vehicle power supply equipment (EVSE) to perform a charging operation on the EV.

[0072] According to an embodiment, the programming instructions further include instructions for performing the following operations: providing a connection instruction to connect the first EVSE to the EV in response to the operator having an unsuccessful charging operation associated with the EV before instructing the second EVSE.

[0073] According to an embodiment, the programming instructions further include instructions for performing the following operations: selecting the second EVSE in response to the second EVSE having fewer unsuccessful charging operations to the operator than another EVSE or the second EVSE having fewer unsuccessful charging operations to the EV than another EVSE.

[0074] According to an embodiment, the programming instructions further include instructions for performing the following operations: in response to the first EVSE failing to charge the EV, storing identification data associated with the EV, the first EVSE, and the operator in relation to each other.

[0075] According to an embodiment, the programming instructions further include instructions for performing the following operations: selecting the first EVSE based on historical charging operation records, the historical charging operation records indicating that: the first EVSE or the operator has not yet participated in a charging operation with the EV, the EV has had one or more successful charging operations with the first EVSE, or the operator has had a successful charging operation with the first EVSE.

[0076] According to an embodiment, the second EVSE is instructed in response to a first unsuccessful plug-in attempt.

[0077] According to the present invention, a method for controlling the charging operation of an electric vehicle (EV) at a charging station having a plurality of electric vehicle power supply equipment (EVSEs) includes: transmitting a first charging message to allocate a first EVSE to perform a charging operation on the EV; transmitting a second charging message to allocate a second EVSE to perform the charging operation on the EV, such that the second EVSE performs the charging operation in response to the first EVSE failing to charge the EV after an operator's plug-in attempt and a previous charging operation having an unsuccessful charging operation associated with the EV or the first EVSE, or the first EVSE having an unsuccessful charging operation associated with the EV.

[0078] In one aspect of the invention, the method includes: transmitting a connection instruction to connect the first EVSE to the EV in response to the previous charging operation including the operator having an unsuccessful charging operation associated with the EV before transmitting the second charging message, wherein the second charging message is transmitted after a second plug-in attempt in response to providing the connection instruction.

[0079] In one aspect of the invention, the method includes selecting a second EVSE in response to either: the second EVSE having fewer unsuccessful charging operations to the operator than another EVSE, or the second EVSE having fewer unsuccessful charging operations to the EV than another EVSE.

[0080] In one aspect of the invention, the method includes storing identification data associated with the EV, the first EVSE, and the operator in relation to each other in response to the first EVSE failing to charge the EV after the plugging attempt.

[0081] In one aspect of the invention, the method includes selecting a first EVSE based on historical charging operation records, the historical charging operation records indicating that: the first EVSE or the operator has not yet participated in a charging operation with the EV, the EV has had one or more successful charging operations with the first EVSE, or the operator has had a successful charging operation with the first EVSE.

[0082] In one aspect of the invention, the plug-in attempt is the operator’s first plug-in attempt, and the second charging message is transmitted in response to the first plug-in attempt failing.

Claims

1. A control system for controlling charging operations of an electric vehicle (EV) using a plurality of electric vehicle supply equipment (EVSE), comprising: a processor programmed to generate a first charge message to assign a first EVSE to perform a charging operation on the EV and to generate a second charge message to assign a second EVSE to perform the charging operation on the EV such that the second EVSE performs the charging operation in response to the first EVSE being unsuccessful in charging the EV after a plug-in attempt by an operator and a previous charging operation having an unsuccessful charge comprising an operational combination of the operator, the EV, or the first EVSE.

2. The control system of claim 1, wherein the operational combination comprises: the operator having an unsuccessful charge operation associated with the first EVSE, the first EVSE having an unsuccessful charge operation associated with the EV, or the operator having an unsuccessful charge operation associated with the EV.

3. The control system of claim 2, wherein prior to generating the second charge message, the processor is further programmed to provide connection instructions to connect the first EVSE to the EV in response to the previous charging operation comprising the operator having an unsuccessful charge operation associated with the EV as the operational combination.

4. The control system of claim 1, wherein the processor is further programmed to select the second EVSE in response to: the second EVSE having fewer unsuccessful charge operation times with the operator than the other EVSE, or the second EVSE having fewer unsuccessful charge operation times with the EV than the other EVSE.

5. The control system of claim 1, wherein the processor is further programmed to store identification data related to the EV, the first EVSE, and the operator in association with each other in response to the first EVSE being unsuccessful in charging the EV after the plug-in attempt.

6. The control system of claim 1, wherein the processor is further programmed to select the first EVSE based on a historical charging operation record indicating: the first EVSE or the operator has not participated in a charging operation with the EV, the EV has one or more successful charge operations with the first EVSE, or the operator has a successful charge operation with the first EVSE.

7. The control system of claim 1, wherein the plug-in attempt is a first plug-in attempt by the operator and the processor is further programmed to generate the second charge message in response to the first plug-in attempt being unsuccessful.

8. The control system of claim 1, further comprising a communication device configured to communicate with the plurality of EVSEs, including transmitting charge messages to selected EVSEs, wherein the charge messages include the first charge message and the second charge message.

9. A method for controlling charging operations of an electric vehicle (EV) at a charging field station having a plurality of electric vehicle supply equipment (EVSE), comprising: transmitting a first charging message to assign a first EVSE to perform a charging operation on the EV; transmitting a second charging message to assign a second EVSE to perform the charging operation on the EV, such that the second EVSE performs the charging operation in response to the first EVSE being unsuccessful in charging the EV after a plug-in attempt by an operator and a previous charging operation having an unsuccessful charging operation associated with the EV or the first EVSE or the first EVSE having an unsuccessful charging operation associated with the EV.

10. The method of claim 9, further comprising: transmitting connection instructions to connect the first EVSE to the EV in response to the previous charging operation including the operator having an unsuccessful charging operation associated with the EV prior to transmitting the second charging message, wherein the second charging message is transmitted after a second plug-in attempt in response to providing connection instructions.

11. The method of claim 9, further comprising selecting the second EVSE in response to: the second EVSE having fewer unsuccessful charging operation times with the operator than the other EVSE, or the second EVSE having fewer unsuccessful charging operation times with the EV than the other EVSE.

12. The method of claim 9, further comprising storing identification data related to the EV, the first EVSE, and the operator in association with each other in response to the first EVSE being unsuccessful in charging the EV after the plug-in attempt.

13. The method of claim 9, further comprising selecting the first EVSE based on historical charging operation records indicating: the first EVSE or the operator not having been involved in a charging operation with the EV, the EV having one or more successful charging operations with the first EVSE, or the operator having a successful charging operation with the first EVSE.

14. The method of claim 9, wherein the plug-in attempt is a first plug-in attempt by the operator and the second charging message is transmitted in response to the first plug-in attempt being unsuccessful.

Images