Patent Application
20230286403
The information provided in this section is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.
The present disclosure relates to charging systems for electric vehicles, and more particularly to systems for detecting DC arc faults in charging systems for electric vehicles.
Electric vehicles such as plug-in hybrid vehicles, battery electric vehicles and fuel cell vehicles include a battery system including one or more battery cells, modules and/or packs. The battery system needs to be charged using a charging system. Some charging systems for battery systems require 4-10 hours to recharge the electric vehicle. Fast charging systems are being developed to charge the electric vehicles at higher voltage levels such as 400 V or 800 V to reduce the amount of time required to charge the battery systems of the electric vehicles.
DC Fast Charging (DCFC) systems use a standard set of connectors that are adapted by different original equipment manufacturers (OEMs) in various countries. The connectors are designed to meet the electrical, mechanical and environmental requirements to ensure safe operation during charging at high voltage levels.
A charging system for an electric vehicle comprises a charger connector configured to connect to a charge port on the electric vehicle and includes a housing, a first conductor passing through the housing, a second conductor passing through the housing, and a current sensor configured to sense current flowing through at least one of the first conductor and the second conductor to a battery system of the electric vehicle. A charger-side controller includes an arc fault detection module configured to selectively identify a DC arc fault in response to measured current sensed by the current sensor and to stop charging the electric vehicle in response to detecting the DC arc fault.
In other features, the current sensor has a bandwidth greater than 100 KHz. The current sensor comprises a point field detector (PFD). The current sensor is selected from a group consisting an anisotropic magneto-resistive (AMR) sensor, a giant magneto-resistive (GMR) sensor, a tunnel magneto-resistive (TMR) sensor, and a Hall effect sensor. When stopping charging, the charger-side controller is configured to decrease current output to the electric vehicle to zero and send a message to a vehicle-side controller to cause the vehicle-side controller to open a first contactor and a second contactor connecting the first conductor and the second conductor to the battery system after the measured current is less than a predetermined current threshold.
In other features, the current sensor is arranged in the housing. The current sensor is arranged between the first conductor and the second conductor in the housing. An insulation layer surrounds the first conductor and the second conductor. The current sensor is arranged around the insulation layer. A voltage sensor is configured to sense voltage across the first conductor and the second conductor.
In other features, the charger-side controller receives a second measured current and a second measured voltage from a vehicle-side controller. The arc fault detection module is configured detect the DC arc fault by comparing the measured current and the measured voltage to the second measured current and the second measured voltage, respectively.
A charging system for an electric vehicle includes a charge port on the electric vehicle configured to connect to a charger connector, a first conductor configured to connect power from the charge port to a first terminal of a battery system, and a second conductor configured to connect power from the charge port to a second terminal of the battery system. A current sensor is configured to sense current flowing through at least one of the first conductor and the second conductor to the battery system. A vehicle-side controller includes an arc fault detection module configured to selectively identify a DC arc fault in response to measured current output by the current sensor and to cause charging to stop in response to detecting the DC arc fault.
In other features, the current sensor has a bandwidth greater than 100 KHz. The current sensor comprises a point field detector (PFD). The current sensor is selected from a group consisting an anisotropic magneto-resistive (AMR) sensor, a giant magneto-resistive (GMR) sensor, a tunnel magneto-resistive (TMR) sensor, and a Hall effect sensor. A first contactor connects the first conductor to the first terminal of the battery system. A second contactor connects the second conductor to the second terminal of the battery system. When causing the charging to stop, the vehicle-side controller is configured to send a message to a charger-side controller to decrease current output to the electric vehicle to zero and open the first contactor and the second contactor after the measured current is less than a predetermined current threshold.
In other features, a voltage sensor configured to sense voltage across the first conductor and the second conductor. The vehicle-side controller receives a second measured current and a second measured voltage from a vehicle-side controller. The arc fault detection module is configured detect the DC arc fault by comparing the measured current and the measured voltage to the second measured current and the second measured voltage, respectively.
Further areas of applicability of the present disclosure will become apparent from the detailed description, the claims and the drawings. The detailed description and specific examples are intended for purposes of illustration only and are not intended to limit the scope of the disclosure.
The present disclosure will become more fully understood from the detailed description and the accompanying drawings, wherein:
In the drawings, reference numbers may be reused to identify similar and/or identical elements.
Charging stations include a plurality of charging systems that are typically located outdoors and are therefore not in temperature and humidity-controlled environments. The charging stations supply DC power from a DC source (e.g. utility power). In coastal areas, the charger connectors are also vulnerable to build up moisture and salt, which may compromise a creepage distance and cause DC arc faults to occur. Since DC arc faults do not cause over-current or over-voltage conditions, DC arc faults go undetected by the standard protection devices used in the charging systems.
Charging systems and methods according to the present disclosure monitor current flowing from a charging system to an electric vehicle via a charge connector. The charging systems detect DC arc faults during charging of the electric vehicle. Examples of DC arc faults include series or parallel DC arc faults. Both types of DC arc faults have unique current signatures that can be detected by processing current and/or voltage waveforms measured using the current or voltage sensors. In some examples, the current sensors are high bandwidth sensors. As used herein, high bandwidth refers to bandwidths greater than 100 kHz.
In some examples, a current sensor is arranged in the charger connector on the charger side. An arc fault detection module of a charger-side controller detects the DC arc faults based on the current sensed by the current sensor. When a DC arc fault is detected, the charger-side controller reduces the charging current to zero within a predetermined period. The charger-side controller sends a message to vehicle-side controller to open the battery contactor after the charging current falls below a predetermined threshold.
In some examples, the current sensor is located on the vehicle side. When the DC arc fault is detected, the vehicle-side controller sends a request to the charger-side controller reduce the charging current to zero within a predetermined period. The vehicle-side controller opens the battery contactors after the charging current falls below a predetermined current threshold.
In some examples, both current and voltage sensors monitor current and voltage levels on one or both of the charger side and the vehicle side. The charger-side controller and/or the vehicle-side controller compare the two sets of voltages and currents. Under normal operating conditions, the two voltages and currents will be within predetermined ranges of one another. Any deviation beyond the predetermined ranges indicates a potential fault and charging is stopped.
Referring now to
Referring now to
Referring now to
Referring now to
The electric vehicle 116 includes a battery system 118. The battery system 118 includes contactors CON1 and CON2 and a battery BATT including one or more battery cells, battery modules, and/or battery packs connected in series, parallel, and/or combinations thereof. The charger-side controller 112 communicates with the vehicle-side controller 120 via a conductor 126 such as a controller area network (CAN) bus.
With the current sensor 124 located on the charger side, an arc fault detection module 125 resides in the charger-side controller 112. The arc fault detection module 125 detects DC arc faults based on the measured current. When a DC arc fault is detected, the charger-side controller 112 reduces the charging current to zero within a predetermined period and sends a command to the vehicle side controller 120 to open the battery contactors when the charging current falls below a predetermined current threshold.
In
In
In
Referring now to
In some examples, the current sensor 186 comprises a point field detector (PFD) such as an anisotropic magneto-resistive (AMR) sensor, a giant magneto-resistive (GMR) sensor, a tunnel magneto-resistive (TMR) sensor, a Hall effect sensor, or other suitable sensors. In some examples, the PFD sensor is a submillimeter high bandwidth PFD that is positioned in between the first connection 182 and the second connection 184 to detect the field and the current in the charge loop. Though a PFD sensor is shown, any low-cost, high-bandwidth field sensor can be used for sensing the current.
Referring now to
In some examples, the current sensor 198 comprises a zero current core-based annular sensor arranged around the outer insulation layer 197 of the plug 190. The annular magnetic core around the positive and negative current experiences field cancellation from the regular charging currents. However, only the fault currents with unbalance fields will generate magnetic field inside the core. Due to this, the core can be very thin with low cross-sectional area. The current sensor 198 is very low cost and tightly integrated with the outer insulation layer 197 due to field nulling. With no loss of isolation or parallel fault issues, the low-field detector output will be close to zero. When a DC arc fault is detected, the charging system ramps down current and the vehicle-side controller opens the contactors after the current falls below a predetermined current threshold. While specific types of current sensors are shown and described, other types of current sensors can be used.
Referring now to
If 242 is true, the method determines if an arc fault is detected. If 246 is true, the charging current is ramped down to zero and the contactors are opened, the charging process is terminated, and the connector is unlocked. A message is sent to the vehicle-side controller at 248. If 246 is false, the battery is charged in constant charge (CC) or constant voltage (CV) mode depending upon the charge request.
Referring now to
The foregoing description is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. The broad teachings of the disclosure can be implemented in a variety of forms. Therefore, while this disclosure includes particular examples, the true scope of the disclosure should not be so limited since other modifications will become apparent upon a study of the drawings, the specification, and the following claims. It should be understood that one or more steps within a method may be executed in different order (or concurrently) without altering the principles of the present disclosure. Further, although each of the embodiments is described above as having certain features, any one or more of those features described with respect to any embodiment of the disclosure can be implemented in and/or combined with features of any of the other embodiments, even if that combination is not explicitly described. In other words, the described embodiments are not mutually exclusive, and permutations of one or more embodiments with one another remain within the scope of this disclosure.
Spatial and functional relationships between elements (for example, between modules, circuit elements, semiconductor layers, etc.) are described using various terms, including “connected,” “engaged,” “coupled,” “adjacent,” “next to,” “on top of,” “above,” “below,” and “disposed.” Unless explicitly described as being “direct,” when a relationship between first and second elements is described in the above disclosure, that relationship can be a direct relationship where no other intervening elements are present between the first and second elements, but can also be an indirect relationship where one or more intervening elements are present (either spatially or functionally) between the first and second elements. As used herein, the phrase at least one of A, B, and C should be construed to mean a logical (A OR B OR C), using a non-exclusive logical OR, and should not be construed to mean “at least one of A, at least one of B, and at least one of C.”
In the figures, the direction of an arrow, as indicated by the arrowhead, generally demonstrates the flow of information (such as data or instructions) that is of interest to the illustration. For example, when element A and element B exchange a variety of information but information transmitted from element A to element B is relevant to the illustration, the arrow may point from element A to element B. This unidirectional arrow does not imply that no other information is transmitted from element B to element A. Further, for information sent from element A to element B, element B may send requests for, or receipt acknowledgements of, the information to element A.
In this application, including the definitions below, the term “module” or the term “controller” may be replaced with the term “circuit.” The term “module” may refer to, be part of, or include: an Application Specific Integrated Circuit (ASIC); a digital, analog, or mixed analog/digital discrete circuit; a digital, analog, or mixed analog/digital integrated circuit; a combinational logic circuit; a field programmable gate array (FPGA); a processor circuit (shared, dedicated, or group) that executes code; a memory circuit (shared, dedicated, or group) that stores code executed by the processor circuit; other suitable hardware components that provide the described functionality; or a combination of some or all of the above, such as in a system-on-chip.
The module may include one or more interface circuits. In some examples, the interface circuits may include wired or wireless interfaces that are connected to a local area network (LAN), the Internet, a wide area network (WAN), or combinations thereof. The functionality of any given module of the present disclosure may be distributed among multiple modules that are connected via interface circuits. For example, multiple modules may allow load balancing. In a further example, a server (also known as remote, or cloud) module may accomplish some functionality on behalf of a client module.
The term code, as used above, may include software, firmware, and/or microcode, and may refer to programs, routines, functions, classes, data structures, and/or objects. The term shared processor circuit encompasses a single processor circuit that executes some or all code from multiple modules. The term group processor circuit encompasses a processor circuit that, in combination with additional processor circuits, executes some or all code from one or more modules. References to multiple processor circuits encompass multiple processor circuits on discrete dies, multiple processor circuits on a single die, multiple cores of a single processor circuit, multiple threads of a single processor circuit, or a combination of the above. The term shared memory circuit encompasses a single memory circuit that stores some or all code from multiple modules. The term group memory circuit encompasses a memory circuit that, in combination with additional memories, stores some or all code from one or more modules.
The term memory circuit is a subset of the term computer-readable medium. The term computer-readable medium, as used herein, does not encompass transitory electrical or electromagnetic signals propagating through a medium (such as on a carrier wave); the term computer-readable medium may therefore be considered tangible and non-transitory. Non-limiting examples of a non-transitory, tangible computer-readable medium are nonvolatile memory circuits (such as a flash memory circuit, an erasable programmable read-only memory circuit, or a mask read-only memory circuit), volatile memory circuits (such as a static random access memory circuit or a dynamic random access memory circuit), magnetic storage media (such as an analog or digital magnetic tape or a hard disk drive), and optical storage media (such as a CD, a DVD, or a Blu-ray Disc).
The apparatuses and methods described in this application may be partially or fully implemented by a special purpose computer created by configuring a general purpose computer to execute one or more particular functions embodied in computer programs. The functional blocks, flowchart components, and other elements described above serve as software specifications, which can be translated into the computer programs by the routine work of a skilled technician or programmer.
The computer programs include processor-executable instructions that are stored on at least one non-transitory, tangible computer-readable medium. The computer programs may also include or rely on stored data. The computer programs may encompass a basic input/output system (BIOS) that interacts with hardware of the special purpose computer, device drivers that interact with particular devices of the special purpose computer, one or more operating systems, user applications, background services, background applications, etc.
The computer programs may include: (i) descriptive text to be parsed, such as HTML (hypertext markup language), XML (extensible markup language), or JSON (JavaScript Object Notation) (ii) assembly code, (iii) object code generated from source code by a compiler, (iv) source code for execution by an interpreter, (v) source code for compilation and execution by a just-in-time compiler, etc. As examples only, source code may be written using syntax from languages including C, C++, C#, Objective-C, Swift, Haskell, Go, SQL, R, Lisp, Java®, Fortran, Perl, Pascal, Curl, OCaml, Javascript®, HTML5 (Hypertext Markup Language 5th revision), Ada, ASP (Active Server Pages), PHP (PHP: Hypertext Preprocessor), Scala, Eiffel, Smalltalk, Erlang, Ruby, Flash®, Visual Basic®, Lua, MATLAB, SIMULINK, and Python®.
